• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 351 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.

TMS320F28379D: Reprogramming using loadti

Ratul Das
Prodigy 10 points

Part Number: TMS320F28379D

Hi,

I am facing difficulties using the loadti to load TMS320F28379D. I am loading the device using the following command:

.\loadti -c NewTargetConfiguration.ccxml HTOL_auto_measurement_1p2.out

It works fine. The problem is that the next time I try the same command it shows the following error:

Configuring Debug Server for specified target...
Done
TARGET: Texas Instruments XDS100v2 USB Debug Probe_0
Connecting to target...
SEVERE: IcePick_C_0: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may be one or more of: no XDS100 is plugged in, invalid XDS100 serial number, blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the XDS100 can be located. (Emulation package 9.12.0.00150)

SEVERE: emulation failure occurred
SEVERE: Error connecting to the target: emulation failure occurred
Error code #4

In short, I have to load the program from cmd and load multiple times.

What is the best way of doing this?

Best

Ratul

  • 0
    TI__Guru**** 481471 points

    Hello,

    Ratul Das said:
    SEVERE: IcePick_C_0: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may be one or more of: no XDS100 is plugged in, invalid XDS100 serial number, blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the XDS100 can be located. (Emulation package 9.12.0.00150)

    For some reason, the debugger is unable to detect the XDS100 debug probe used to communicate with the device. It appears that the after programming successfully the first time, the XDS100 is no longer detected by the system,

    After this happens, can you recover for it?

  • 0 in reply to Ki
    Prodigy 10 points

    If I load using option -a I can load multiple times. The program is supposed to write something while running. That does not happens.

    No, I can not recover. I have to either use CCS or unplug-plug the communication cable.

  • 0 in reply to Ratul Das
    TI__Guru**** 481471 points
    Ratul Das said:
    If I load using option -a I can load multiple times.

    -a would simply do an asynchronous run, meaning it would run the target and loadti would then immediately exist. Without the -a, it would block (wait until the target halts). When you run without -a, does loadti eventually exit on its own? Basically does your program self terminate or does it just run forever and you forcible shut down loadti?

  • 0 in reply to Ki
    Prodigy 10 points

    Using option -t  actually solved my previous problem that I can load the uC after some time multiple time times. However, I realized that I needed a different strategy. Can I use any command using loadti to read register values when the uC in running?

  • 0 in reply to Ratul Das
    TI__Guru**** 481471 points
    Ratul Das said:
    Using option -t  actually solved my previous problem that I can load the uC after some time multiple time times.

    With -t, you are simply setting the timeout so that the synchronous run action returns after some time despite the target not halting. It is basically the same behavior as -a except that -a would return immediately. 

    Ratul Das said:
    Can I use any command using loadti to read register values when the uC in running?

    No, not with loadti. You would need to create your own DSS script or make custom modifications to loadti.

    Thanks

    ki