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.

CCS/TMDSEMU110-U: What can cause 0xBAD0 to returned as the memory value from a Cortex-R4 while the target is running?

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: TMS570LS0432

Tool/software: Code Composer Studio

In the referenced thread a user is having the issue whereby when a TMS570LS0432 target is running, connected to a XDS110, that continuous refresh in the CSS Expression view displays the values in the variables as 0xBAD0.

Whereas using a XDS100v2 shows the expected values when continuous refresh is used while the target is running.

From a search I have seen that 0xBAD0 can be returned to indicate that an "error" has occurred reading the target, but am unsure what the root cause is.

I attempted to repeat the issue, albeit with a different Cortex-R4 device, but so far have been unable to repeat the problem.

  • Chester,

    BAD0 is a condition where the CCS Debugger configures the memory as valid but the Debug Probe returns an error condition. 

    That is highly dependent on the device itself and how its debug subsystem and/or its cores handle memory accesses to invalid or non-existent memory. It can be quite difficult to reproduce as you can imagine, unless there is a clear testcase for it. 

    Other conditions that you probably already saw are a sequence of dashes -------- (when the memory map sets the address to NONE) or a sequence of zeros 00000000 (where the memory map is valid but the device's debug subsystem does not return any error condition).

    Regards,

    Rafael