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.

TMS570LS31 .gel file memory map switch function doesn't work when connected to target through J-Link in CCSv5.2 beta version or any other external emulator

Other Parts Discussed in Thread: TMS570LS3137

Hi,

When I try to execute .gel files memory switch function after connecting to the TMS570LS31x through J-Link in CCSv5.2 I get the following error:

CortexR4: Trouble Writing Memory Block at 0xffffffcc on Page 0 of Length 0x4: WriteMem failed!
Target_RAM_to_0x0() cannot be evaluated.
target access failed
    at *((int *) 0xffffffcc)=0x00000001 [tms570ls3137.gel:224]
    at swap_mem(1) [tms570ls3137.gel:277]
    at Target_RAM_to_0x0()


Probably .gel file can only work with built-in XDS100v2 USB emulators?? I tried memory switching steps in the script file of RealView ICE (or some other emulator) but target connection is lost when CPU is reset as part of memory switching requirement. Is it possible to successfully incorporate memory switching code in the script file of an external emulator such as RealView ICE or J-Link?? and how possibly built-in emulator differs from external emulator in this regard? How this CPU resetting issue is handled when connected through built-in XDS100v2 USB emulator?

I want to use external emulator because debugging is very slow if I use XDS100v2 usb stick in CCSv4. How can I achieve better debugging performance on built in emulator or alternatively how can I handle this memory switching issue with external emulators?

Preferably how can I improve speed with XDSv100 usb stick?

Your help is extremely appreciated.

Regards.

  • Zeeshan,

    Try ignoring the failure ("Cancel") and then see if the emulator recovers. You have issued a CPU reset, and this temporarily scrambles the CPU's ability to respond through the debugger. If this approach does not work, please re-post.

    Regards,

    TI Forum Support