Hi John,
I did manage to get the code to build for the OMAP5 CortexM4.
- From TI Resource Explorer I click on Examples
- Select SYS/BIOS – ARM – OMAP5 – OMAP5430 – General Examples – Hello World
- Click on "Import the example project into CCS"
- On the first dialog, I select "Blackhawk USB560-M Emulator"
- Click Next
- The Target is already populated with "ti.targets.arm.elf.M4"
- For Platform I select "ti.platforms.sdp5430" (Don't click on "ti.platform.Stellaris"OMAP5432" as this does not exist in XDCTools)
- Click Finish
- I get two green check marks, one for Step 1 and one for Step 3
- When I click on "Build the imported project" and everything builds successfully.
- When I click on click on "Debug the imported project", the debugger will launch and throw and error "Device is held in rest". All you can do is cancel which exits the debugger.
- Edit the Debug Configuration in the "Target" tab, select the "Cortex_M4_0" Device
- Select Auto Run and Launch Options. Unselect all "Auto Run Options" and all "Launch Options"
- Click Apply and Launch Debugger
- Show Debug "Control Panel" and select GEL Files
- Connect Target CortexA15_0 and in the GEL panel, Load GEL file "omap5430_cortexA15_reset.gel"
- Under Scripts menu select RESET - reset_miniC64, reset_ipu_cortexM4_RTOS_board, reset_ipu_cortexM4_SIMCOP_board
- Connect Target CortexM4_0
IcePick_D: GEL Output: Ipu RTOS is released from Wait-In-Reset.
IcePick_D: GEL Output: Ipu SIMCOP is released from Wait-In-Reset.
IcePick_D: GEL Output: IVAHD C64 is released from Wait-In-Reset.
IcePick_D: GEL Output: IVAHD ICONT1 is released from Wait-In-Reset.
IcePick_D: GEL Output: IVAHD ICONT2 is released from Wait-In-Reset.
CS_DAP_DebugSS: GEL Output: --->>> CONFIGURE DEBUG DPLL settings to 1.6 GHZs <<<---
CS_DAP_DebugSS: GEL Output: > Setup DebugSS Clocking 1.6GHz M4_3
CS_DAP_DebugSS: GEL Output: > Setting STM output clock to 50MHz
CS_DAP_DebugSS: GEL Output: < Done with Setup DebugSS Clocking 1.6GHz
CS_DAP_DebugSS: GEL Output: --->>> TURNING ON L3_INSTR and L3_3 clocks required for debug instrumention <<<<<<----
CS_DAP_DebugSS: GEL Output: ---<<< L3 instrumentation clocks are enabled >>>> ---
CS_DAP_DebugSS: GEL Output: --->>> GP device, no FW settings needed. <<<---
CS_DAP_DebugSS: GEL Output: ---<<< Firewalls settings >>>---
CS_DAP_PC: GEL Output: --->>> GP device <<<---
CS_DAP_PC: GEL Output: Cortex-A15 1 is not in WIR mode so nothing to do.
CortexA15_0: Breakpoint Manager: Retrying with a AET breakpoint
CortexA15_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x80003862: (Error -1066 @ 0x3340) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.1.73.0)
CortexA15_0: Breakpoint Manager: Retrying with a AET breakpoint
CortexA15_0: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x80003fa4: (Error -1066 @ 0x3340) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.1.73.0)
CortexA15_0: Breakpoint Manager: Retrying with a AET breakpoint
CortexA15_0: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x8000481c: (Error -1066 @ 0x3340) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Writing Memory Block at 0x8000806c on Page 0 of Length 0x1cf1: (Error -2130 @ 0x80009D5C) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: GEL: File: /home/jsynesio/workspace_v5_4/hello_OMAP5430_CortexM/Debug/hello_OMAP5430_CortexM.out: Load failed.
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -1003 @ 0x2BC5) Internal error: Invalid parameter passed to function. Restart the application. If error persists, please report the error. (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
CortexA15_0: Trouble Reading Register CPSR: (Error -1066 @ 0x3340) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.1.73.0)
CortexA15_0: GEL Output: --->>> omap5430_memory_map_init DONE !!! <<<---
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
Cortex_M4_0: Trouble Reading Memory Block at 0xfffffffa on Page 0 of Length 0x6: (Error -2130 @ 0xFFFFFFF8) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.73.0)
When I try to load the CortexM4 Hello World Example, I get a memory access violations, so my guess is the Memory Map isn't correct. Can someone show me the correct way to setup the debugger and the correct sequence of running the GEL files.
Regards,
John