• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 491 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.

TMS570LS0432: Debugging Error

John Lodi
Prodigy 30 points
Part Number: TMS570LS0432
Other Parts Discussed in Thread: LAUNCHXL-TMS57004, TMDSEMU200-U, TMDSEMU110-U

Hi!

I'm using CCS v8.3.0, and Windows 10 (x64)...

I've been working with the TMS570LS04 (Hercules Launchpad) for about a month, and recently I plugged it in and the module can't connect. I didn't do anything in particular to brick the module (that I know of)...

I last remember, I flashed it, saw my code worked in the debugger, and then unplugged the module. I returned to it the next day and couldn't connect (getting that 'SC_ERR_FTDI_OPEN' error). A windows 10 pop-up would gives the "USB device not recognized" pop-up every time I plug it in; also, I've tried uninstalling and reinstalling CCS/the hercules drivers, and am unable to see XDS100v2 in Window's control panel. I've even tried a different USB cable.

The SCI1RX and SCI1TX LEDs (D5 & D6) are dim, and stay dimly lit as long as power is supplied to the module (in my case, through the micro-usb to my computer). D1 is the only LED on all the way.The ERR LED (D10) flashes on reset. I've tried using the xdsdfu utility in "..\ccsv8\ccs_base\common\uscif\xds110"; however, I'm unable to recover the device. I checked the voltages on the 5V & 3.3V pins, and they're at the correct voltages. In fact, my application still runs fine... I have the controller outputting CAN messages, and it looks like the program is acting just as it had last I was able to flash the controller.

I'm unsure how to proceed with debugging this issue. Any help is greatly appreciated!

Thanks, 
John Lodi

  • 0
    TI__Guru**** 171044 points
    John,

    As you mentioned, the LAUNCHXL-TMS57004 has a XDS100v2 Debug Probe, therefore the xdsdfu utility is not applicable.

    However, there is the utility \ccsv8\ccs_base\common\uscif\xds100serial.exe that identifies the probes connected to the host.

    However, since you mentioned that Windows Control Panel does not acknowledge the XDS100v2, I suspect the FTDI device itself may either be damaged or lost its VID/PID configuration.

    The section "Troubleshooting" of the XDS100 Wiki page links to the VID/PID programming and has additional tips to troubleshoot this scenario.

    processors.wiki.ti.com/.../XDS100

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 30 points
    Hi Rafael,

    Thanks for your response! Sorry, I haven't had any experience using these kinds of tools. I used the xds100serial.exe and no device was found. Since I cannot find the device, reprogramming the VID/PID /EEPROM won't work.

    Should the D7 LED (3.3v indicator) be on when the device is running? Also, what would cause a failure like this to happen?

    Thanks,
    John
  • 0 in reply to John Lodi
    Prodigy 30 points
    After looking into this a little bit more, it's becoming more and more apparent that the FTDI chip (FT2232H) has gone bad. I'm just not sure why that would have happened
  • 0 in reply to John Lodi
    TI__Guru**** 171044 points
    John,

    Thank you for reporting back your findings. The D7 LED is just a 3.3V after the voltage regulator; it does not indicate any specific state the processor is in.

    You could try to use FTDI's FT-Prog software and try to detect your board - perhaps it can go a level deeper than our xds100serial utility.

    If you have a standalone JTAG Debug Probe such as the TMDSEMU110-U or the TMDSEMU200-U, one suggestion is to populate the 14-ín connector on the launchpad and use the standalone Debug Probe on it.

    At any rate, good luck in trying to recover your board.

    Regards,
    Rafael