• Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 234 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM814x : CCS loading M3VPSS symbol issue

Eason Wang
Genius 13460 points

Hi I am using CCSv5.5 _ xds 560v2 use emulator, trying to run HDVPSS standalone.

when I load M3VPSS firmware(xem3 symbol, pre build and newly build), it will return error as below:

Cortex_M3_ISS: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_M3_ISS: Breakpoint Manager: Error enabling this function: Address exceeds the allowed range
Cortex_M3_ISS: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x8c8447e4: (Error -1170 @ 0x8C8447E4) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.232.0)

I have checked the breakpoint window but there is no break point set.

Could you give me some idea what might cause this issue?

BR,

Eason

  • TI__Guru**** 171729 points

    Eason,

    Sorry for the delay in your reply. Unfortunately I am not very familiar with this coprocessor, but does this happen just after you load the code to the coprocessor or when you run after loading?

    If the first case, the CCS debugger by default tries to run and stop at main() after loading the code (and it needs to set a breakpoint at this address). In this case for some reason it is unable to set it at this address and is retrying a few times. The second error message regarding the address range is a consequence of trying to set the breakpoint - since it says the address is out of range, I imagine that either the coprocessor is misconfigured (thus the memory is not accessible) or the .xem3 executable file has an error when it was compiled/linked. The third message is more or less a summary to what happened and it shows the address where the problem happened.

    If the second case, your code may be halting the coprocessor or causing the entire device to crash or reset.

    All that said, it is possible the coprocessor is not meant to be run as a standalone core, requiring that peripherals are such as EMIF and others are set by the main ARM core. But, as I mentioned before, this is something out of my realm of knowledge.

    Hope this helps,

    Rafael