• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 934 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/CC1352P: XDS110 firmware upgrade is causing power up failures on CC1352 launchpads

Ki
Guru**** 467201 points
Part Number: CC1352P


Tool/software: Code Composer Studio

Posting on behalf of a customer:

I'm having a very unfortunate problem with DSS. I just upgraded to a new version of CCS (CCS 9.1.0) which probably comes with a new FW for the XDS110 debugger. When our regression spins up the debug servers it seems to be automatically updating the XDS110 FW (if a new FW version is available). I have now seen twice that a LaunchPad dies (both are CC1352) and doesn't power up again. I suspect that this is caused by the FW update when we start multiple debug servers at the same time. 

When I try on my own PC I see the green power LED on the LP turn off briefly the first time I spin up the debug server with a new version of CCS. I believe this is because a FW update happens in the background?

  • 0
    TI__Guru**** 467201 points

    Martin,

    If I understand correctly, this issue has only been observed in your automated DSS test environment but not when you perform the steps manually in CCS. Is that correct?

    For the LaunchPads that have been affected, if you run a JTAG connectivity test, what is the result?

    Thanks

    ki

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

    Just a check in to see if you have been able to try the steps in CCS.

  • 0 in reply to JohnS
    TI__Guru**** 162435 points

    Martin have you been able to try the steps that Ki suggested.

  • 0 in reply to JohnS
    TI__Guru**** 467201 points

    Martin - I will follow up with you privately

  • 0 in reply to Ki
    TI__Prodigy 10 points

    Yes, this issue is only seen when we start multiple debug servers at (roughly) the same time. It seems like the upgrade of XDS FW conflicts when invoking "the tool" while it is already running. This effectively bricked the XDS debugger as it didn't boot and turned on the power LED. It didn't show up in the list of connected debuggers when using xdsdfu.exe. 

    A TI colleague confirmed it was semi-bricked but could bring it back to life through the XDS JTAG port using a special connector. He had to re-program the boot loader (I think) and then program the FW.

    In other words, programming XDS FW on multiple devices in parallel is likely to brick one or more debuggers (and thus the LaunchPad).

  • 0 in reply to Martin Dj
    TI__Guru**** 467201 points

    Martin Dj said:
    Yes, this issue is only seen when we start multiple debug servers at (roughly) the same time. It seems like the upgrade of XDS FW conflicts when invoking "the tool" while it is already running.

    Thanks for confirming. This is likely a scenario that is not part of our standard testing. We will need to investigate this scenario more often and guard against this case.