• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 528 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.

XDS100v2 Debug Program Load Timeout - Every Other Time

Erik Stafl
Prodigy 130 points


Hi,

I am developing an application using the LM3S5G51 on a custom board and have been using the XDS100v2 debugger to load and debug my code.  It has mostly been working well, but when I click "Debug" to load the program and start debugging, the program load fails due to a timeout every other time.  If after the timeout, I click "Debug" again, it loads properly and doesn't seem to have a problem. 

After the first try, the debug console shows:

CORTEX_M3_0: GEL Output:
Memory Map Initialization Complete
CORTEX_M3_0: GEL Output: Watchdog Timer Enabled
CORTEX_M3_0: GEL Output: UARTs Enabled
CORTEX_M3_0: Flash Programmer: Timed out while writing to Flash memory

When I run the "Test Connection" in the .ccxml target file, it seems to work fine every time. 

I also see this same behavior on the IDM-SBC evaluation board. 

My development environment is the latest version of CCS (5.3.0.00090).

Has anyone else seen this before?  It's not a huge problem, as it's pretty easy to workaround, but I am curious as to why it would happen and it would be nice to fix.

Thanks!

Erik

  • 0
    Guru 56073 points

    Many others but not flash so often, that's when I erase flash during debug prior to loading. Setting a few software switches to alter xds100 debugger load run behavior can calm things down unless it is a hardware issue such as 3.3 VDC power on the JTag port or a USB voltage issue. Don't laugh a low 5 VDC around 4.85 VDC on PCAT-USB port can cause strange issues on some peripherals. My xds100v2 had a bad 12Mhz crystal and would not work at all - noticed the top fell off of it like maybe the glue was eaten by MEK during the fux removal process after reflow.

  • 0 in reply to Genatco
    TI__Intellectual 2790 points

    Hi Erik,

    I don't see any evidence that this is a known issue. You might try slowing the JTAG TCLK in the XDS100 settings dialog. You can also try turning on the CCSv5 DebugServer logging to see if it provides any additional information (http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#Debug_Server_Logging).

    Is this an issue that started after a CCS upgrade or has this always happened?

  • 0 in reply to Stellaris Mitch
    Prodigy 130 points

    Hi Mitch,

    Thanks for the suggestions.  I tried slowing down the JTAG TCLK to 800 kHz and 500 kHz (from the default 1 MHz), but I kept seeing the same problem.  The first time I try to debug, it always fails, and the second time, it always works.  The cycle then repeats.

    I've attached the CCS debug log here from the first failed attempt - perhaps it shows something?

    Come to think of it, I do think this issue started when I updated to CCS 5.3 from 5.2...

    4011.debug_log.txt

    Thanks,

    Erik

  • 0 in reply to Erik Stafl
    TI__Intellectual 2790 points

    Hi Erik,

    Unfortunately, I don't see any obvious reason for the failure in the log. I'm going to move this thread over to the CCS forums as I believe they can better help narrow this down.