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/TMS320C6657: Issue with target behavior- Error 0x00000002/-1176 when browsing memory using XDS510USB Plus emulator pod

Part Number: TMS320C6657

Tool/software: Code Composer Studio

We have a custom board using C6657 2-core processor.

I have connected JTAG via a SD  XDS510 USB Plus emulator pod.

I have a simple test program, linked to run from MSMC, that configures  PLL's, then runs a L2 SRAM memory test.

Every time I browse any memory, whether SRAM,  or MMR space, the following immediately appears in the CC7 Console:

As you can see- this memory was the GPIO configuration MMRs.   If i go back and look at the memory window, it seems to show proper values in the MMRs:

Same happens with L2 SRAM.  I ran at test to program values into it.  The test then Writes back from L1D, invalidates the test region, then reads back from L2 and all values match.   If I  browse the L2 SRAM, I immediately get the console message    Error ....  0x   002/-1176 ...   .    But going back to the memory browser  I see the proper results....

However if I Uncheck  L1 Cache...  (after getting more  Error messages)  the memory only shows  ????  ????-   this applies for anything  in  L1   or  MSMC.

My link command does not specify any memory other than MSMC and L2 for any sections.

I've tried with and without the GEL executing.   No difference.

Any thoughts what this is?

  • My colleague just walked into the lab with a brand new XDS110 Debug probe recommending I try it. I down loaded & installed the latest driver for XDS110 from T.I. and plugged this in. After a few hiccups, it connected to my custom C6657-based PCB.

    Debugging with this probe, the memory problems are gone! I can inspect all memory without the running list of cryptic errors filling up the console. In the memory browsers, I can un-check L1D and see accurate representations of all memory resources, rather than "???? ????".

    So looks like the problem was one of two things:
    - The XDS 510 USB selection in the Target Configuration should not have given a drop-down choice to use with C6657
    - or perhaps there's a new device driver + F/W needed for this older XDS 510.
  • David,

    Thank you for sharing the solution.

    BR
    Tsvetolin Shulev