• State Resolved
  • +1 person also asked this people also asked this
  • Replies 12 replies
  • Subscribers 30 subscribers
  • Views 507 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

LP-AM263P: XDS 110 firmware update failure

Yuting Huang
Prodigy 20 points
Part Number: LP-AM263P
Other Parts Discussed in Thread: LP-AM263

Tool/software:

Hello TI support,

I purchased a Launchpad LP-AM263P, and tried to run the hello_world example. When starting the debug session, CCS prompted me to update the XDS110 firmware. The update failed and the board is no longer recognized as a XDS 110 debug probe. The detailed process is below:

1. When I first plug the board into the computer, it shows up correctly in device manager

2. I started a debug session in CCS for the example hello_world

3. CCS prompted me that a firmware update is required for the XDS110 probe, and I clicked update

4. The update started

5. Then the update failed with this error message

6. Following the prompt, I unplugged and re-plugged the launchpad, yet it always shows up as USB serial device and can no longer be recognized by CCS.

The screenshots are in fact from a second LP-AM263P. The first one suffered from the exact same issue (which I do not have screenshots of each step). I initially suspected that the first one failed due to a bad USB cable (I was using an extension cable), so I purchased this second launch pad. This time I tried it on a different computer, used the USB cable from TI with no extension, and this same error occurred.

On the first launch pad, I already attempted the procedure in the troubleshoot of this page: https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#troubleshooting, I performed

Option 1: Flash the bootloader from the command-line using the XDSDFU utility

by shorting the TDO pin to ground, yet the launch pad is still not recognized, xdsdfu -e show "Found 0 devices."

I did not try option 2 as I do not have a functioning XDS110, and there are no easy JTAG connections available on the launchpad.

  • 0
    TI__Guru**** 427590 points

    Hmm... for some reason the firmware update failed and likely corrupted the bootloader.

    Yuting Huang said:
    by shorting the TDO pin to ground, yet the launch pad is still not recognized, xdsdfu -e show "Found 0 devices."

    This should have put the XDS110 in DFU mode.

    What is the CCS version and host OS? Based on some of your screenshots, it looks like CCS 12.7.x. Is it 12.7.0 or 12.7.1? And some version of Windows.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    CCS is version 12.7.1. The first trial was on windows 10, the second on windows 11, both resulting in the same error.

  • 0 in reply to Yuting Huang
    TI__Guru**** 427590 points

    I will need to take a closer look with my LP-AM263P. I hope to have an update tomorrow.

  • 0 in reply to Ki
    TI__Guru**** 427590 points
    Yuting Huang said:
    by shorting the TDO pin to ground

    Just want to confirm that this is the pin you grounded when you reconnected the USB cable for the XDS110.

    Also, when trying to connect to the board with CCS, make sure that you connect the board power cable FIRST and then the XDS100 cable SECOND

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    Yes, that is the pin I grounded. I tried again making sure to ground the pin -> connect power -> connect USB -> remove grounding, it is still not working and xdsdfu -e shows 0 device. 

  • 0 in reply to Yuting Huang
    TI__Guru**** 427590 points

    Sorry for the delay. We have not been successful in reproducing this issue. However, we have been trying with an LP-AM263. I am looking to secure an LP-AM263P in case that makes a difference.

  • 0 in reply to Ki
    Prodigy 20 points

    Thanks for letting me know!

  • 0 in reply to Yuting Huang
    TI__Guru**** 427590 points

    Just FYI, I heard from another user who had the same issue with LP-AM263P. He also said he had no issue with LP-AM263. So perhaps it is specific to AM263P LaunchPads. I will get mine in a few days and will try it out myself.

  • +1 in reply to Ki
    TI__Guru**** 427590 points
    Ki said:
    So perhaps it is specific to AM263P LaunchPads.

    This appears to be the case. I was able to reproduce the issue with an LP-AM263P.

    We will need to investigate further on why this is happening with this launchpad.

    In the meantime, I was able to resolve the issue with the following steps:

    1. disconnect all cables

    2. ground pin 97 of the TMD41294NCPDT device on the bottom side of the launchpad

    3. plug in the micro-USB cable for the XDS110 while keeping TDO pin grounded.

    4. After ~5 seconds, remove ground from TDO pin

    See this video for example:

    5. Browse to <CCS 12.7 INSTALL DIR>/ccs/ccs_base/common/uscif/xds110 and run xdsdfu -e in the system terminal. You should see:

    6. The next step I am unsure. What worked for me is the below command:

    > xdsdfu -c 1 -s 0451bef3 -f firmware_3.0.0.29.bin -r

    EDIT: the -s option is not needed. Hence the below command would work too:

    > xdsdfu -c 1 -f firmware_3.0.0.29.bin -r

    7. Then run xdsdfu -e again and it should look like:

    This means that the xds110 is now correctly detected with the latest firmware and you should be good to go.

    One note regarding #6. I'm not 100% sure if you need the -c and -s options to change the mode and serial number. Perhaps you just need to flash the firmware only. However, we had another user who ran into the same issue and the said that just flashing the firmware didn't work and adding those additional options did. My one issue is using the -s option is that it changed the serial number. Autodetect needs the first four characters to be a specific value to it to properly detect the launchpad. For AM263P, it is S26E. So after you confirmed that everything is working well you can change the serial number back via something like:

    > xdsdfu -m

    > xdsdfu -s S26E0001 -e

    EDIT: instead of -e at the end, it should be -r

    This will change the serial number to S26E0001. Note the last four characters can be anything. Just the first four should be S26E.

    EDIT: the -s option is not needed. But the -c 1 option is needed.

    > xdsdfu -c 1 -f firmware_3.0.0.29.bin -r

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    Thank you very much, this was really helpful!

    Just a few notes:

    Ki said:
    2. ground pin 97 of the TMD41294NCPDT device on the bottom side of the launchpad

    The mistake I made was I was grounding pin 97 to one of the ground pins on the BoosterPack headers. It turns out that due to the power separation design, the ground of the USB and the rest of the board is separate. Grounding pin 97 to the outer casing of the USB connector worked, and was successful in setting the device into DFU mode.

    Ki said:

    6. The next step I am unsure. What worked for me is the below command:

    > xdsdfu -c 1 -s 0451bef3 -f firmware_3.0.0.29.bin -r

    For me, I did not need the "-c 1 -s 0451bef3" part,

    > xdsdfu -f firmware_3.0.0.29.bin -r

    worked for me.

    Ki said:
    > xdsdfu -s S26E0001 -e

    I believe this should be -r instead of -e:

    > xdsdfu -s S26E0001 -r

  • 0 in reply to Yuting Huang
    TI__Guru**** 427590 points
    Yuting Huang said:

    For me, I did not need the "-c 1 -s 0451bef3" part,

    > xdsdfu -f firmware_3.0.0.29.bin -r

    Thank you for confirming!

    Yuting Huang said:

    I believe this should be -r instead of -e:

    > xdsdfu -s S26E0001 -r

    Yes, you are correct. Thank you for noting this.

  • 0 in reply to Ki
    TI__Guru**** 427590 points

    I tried with another new LP-AM263P and reproduced the issue. But I needed the -c 1 option when I flashed the firmware the first time. Without the -c 1, I could not get the XDS110 working after flashing. I did confirm the I don't need the -s however.