I would like to use CCS & SYS/BIOS for development/debugging an application to run on DM3730. Here is my setup:
Target IC: DM3730
Target Board: BeagleBoard xM
JTAG Emulator: XDS100v2 USB Emulator
CCS 5.5.0.00077
BIOS 6_37_02_27
xdctools 3_25_05_94.
Upon starting the debugger, it does not stop at main, even though it is set to run to symbol main in 'Auto Run and Launch Options'.
Here is what actually happens:
- SYS/BIOS and non-SYS/BIOS examples provided by TI (“hello world” and others) build without errors with CCS
- F11 begins a debug session for both SYS/BIOS and non-SYS/BIOS build examples
- Upon starting, the debugger reports that Cortex_A8 core is Running
- The execution does not stop at main, even though it is set to run to symbol main in 'Auto Run and Launch Options'
- If the running example is suspended (Alt+F8), debugger stops running and reports that Cortex A8 core is 'Suspended'. This works for both SYS/BIOS and non-SYS/BIOS examples.
- At this point Run>Load>Verify Program verifies that the program is loaded correctly, again for both SYS/BIOS and non-SYS/BIOS examples.
- At this point, for non-SYS/BIOS examples, pressing 'Restart' restarts and runs to main; and debugging (single stepping, etc.) seem to work properly. Subsequent pressing of 'Restart' again runs to main and again debugging seems to work.
- But for SYS/BIOS examples, pressing 'Restart' does not run to main, instead it just runs non-stop. If suspended (Alt+F8), 'Verify Program' reports a verify error.
Some more observations:
When a SYS/BIOS example is first suspended, it stops at 0x14080, with a message: No source available for “0x14080”
When a non-SYS/BIOS example is first suspended, it stops at 0x1408c, with a message: No source available for “0x1408c”
If the Cortex A8 core is suspended, it is possible to run a script Scrips>IVA2200_Startup>IVA22_GEM_startup. This connects and suspends C64xP core for both SYS/BIOS and non-SYS/BIOS examples
Is it possible that the example programs load and/or start at wrong memory locations?
What do I need to do to get the debugger run to main (as it is supposed to) when it starts up? (Especially for SYS/BIOS, as I have to use it in the product)
What (settings, etc.) causes the improper operation?