• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 2387 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.

CCS/TMDSEMU110-U: Uniflash Reset Issue, XDS110

Daniel Rush
Intellectual 585 points
Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: UNIFLASH, TM4C129CNCPDT

Tool/software: Code Composer Studio

I'm using the Uniflash GUI and the Standalone command line tool with an XDS110 debug probe, and a TM4C129CNCPDT chip. When I flash new firmware to the board using the debugger and uniflash the board isn't reset upon completion. I have used the same workflow with the XDS200 and after the download completes the board is reset and can continue. However, when I use CCS to debug, flashing is not a problem, board is reset and ready to run code.

  • 0
    TI__Guru**** 171104 points

    Hi,

    I can't necessarily reproduce this in my environment. I am using a TM4C1294 Launchpad connected to a XDS110 and the device is reset properly - well, at least the example code usb_dev_cserial properly instantiates the USB interface immediately after the code is loaded to the target, which indicates it is properly reset and running.

    In the Uniflash interface I have the option Reset target during program load to Flash memory set.

    Does this issue happen with an example code?  

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 585 points
    The software which I am loading has been successfully uploaded with an XDS200 probe, and will function after probe is unplugged from the board, and manually reset.
  • 0
    Intellectual 585 points
    Still having trouble with this, Same code can be loaded using an XDS200, code is loaded board is reset then code runs as expected. When using XDS110, code is loaded then hangs after load completes, code will only run if probe is disconnected and hardware reset button is pressed.