• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 54 subscribers
  • Views 7106 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LAUNCHXL-CC1350: XDS110 bricked? Cannot enter DFU Mode and consequently update firmware | EDIT: Images added

user4961586
Prodigy 70 points
Part Number: LAUNCHXL-CC1350
Other Parts Discussed in Thread: CODECOMPOSER, TM4C1294NCPDT, CC1350

Hello,

I have two LAUNCHXL-CC1350 to which I'm not able to update firmware due to the impossibility of entering in DFU mode. I've been using them without problems for months, but now Code Composer Studio asks me to update XDS110 firmware if I want to enter in Debug mode as shown in the next picture:

I've tried clicking update in both pop-up windows and clicking cancel in one and update in other to no avail. CodeComposer Studio gets frozen after a while.

I then started to try to update both firmwares via command prompt, the problem is that I don't get any of the boards to DFU mode.

The device is no longer recognized unless I disconnect and plug it in again.

This is what can be seen in hardware devices window:

  • LAUNCHXL-CC1350 connected in runtime mode

  • LAUNCHXL-CC1350 connected, xdsdfu -m instruction entered in command prompt

The next thing I tried, was uninstalling highlighted drivers, but this has been even worse, now the device appears as unknown in command prompt and never leaves Runtime mode:

And I get this in hardware devices window:

As I just uninstalled drivers from one of the boards, I then have tried the following instructions (from ReadMe.txt inside XDS110 folder) with the other one:

*** Recovering a Bricked XDS110 Without JTAG ***

In the case that your XDS110 fails to enumerate as a USB device, or it
fails to enter DFU programming mode, you can attempt the following steps
to force it into DFU mode to recover:

1) Ground the JTAG TDO pin of the XDS110's Tiva CPU.  This is pin 97
on the 128 pin device.  This is a JTAG pin for flashing the XDS110 via
JTAG; it is not the JTAG TDO pin of the debug target. If the board has
a JTAG header for flashing the XDS110 you may use that, otherwise you
can ground the pin on the device. (Check the TM4C1294NCPDT datasheet
for the pin location; it is located on a corner and easy to access.)

2) Unplug and re-plug the XDS110 into the host PC while the pin is grounded.

3) The XDS110 should now be in DFU programming mode and you can flash it
using the xdsdfu utility as detailed above.

Note that this feature is currently only implemented in the XDS110 boot
loader that was first available in emupack 6.0.15.0. If your XDS110's
boot loader is an earlier version, this procedure won't work. In the boot
loaders from emupack 5.1.537.0, the target JTAG TCK pin was used instead.
If your device used that version of the boot loader, try the procedure
by grounding the target TCK pin. If your XDS110's boot loader is an even
earlier version, this procedure won't work at all, and you'll need to use
JTAG to recover.

This means I have tried the following connections:

  • Shorting ITDO to Ground.

  • Shorting ITDI to Ground

  • Shorting ITCK to Ground

  • Shorting XDS_TDO_LS to Ground

  • The same with XDS_TDI_LS and XDS_TDI_TCK in P7.

All these trials haven't worked for me. Does anyone please have any guess about what I may be doing wrong? Or what else can I try to make both XDS110 work?

I forgot, I also downloaded and installed XDS Emulation 7.0.48.0 Windows package from http://processors.wiki.ti.com/index.php/XDS_Emulation_Software_Package

Thank's a lot in advance!!

  • 0
    TI__Expert 4860 points

    Seems you have tried all the options that there is to resolve this. There is one thing I would like you to try though. The Launchpad is programmed with SW from an older EMU pack and maybe there is a mismatch with the programmed bootloader and the new FW. Need to verify this with another group within TI but for now you could try to install SmartRF Studio. It will reinstall the XDS110 drivers and the tool will require an older version of the FW than CCS. This is just to see if you can get a connection again. SmartRF Studio can be downloaded from here: www.ti.com/.../smartrftm-studio

    Best Regards,

    Øyvind

     

  • 0 in reply to Øyvind K
    Prodigy 70 points

    I forgot to mention that I already have SmartRF Studio. I had never tried it before, and it is after I installed it that I had the problem with CCS entering in Debug Mode, maybe it is related? As there have been two or three weeks since I don't use CC1350 LaunchPads I'm not sure if the problem is because of SmartRF Studio or new XDS110 firmware  version of late July.

    Anyway, I have opened SmartRf Studio and it recognizes both boards, but with the one that I unistalled drivers I cannot enter Device Control Panel.

    I have no problem entering Device Control Panel with the other one.

    I will uninstall SmartRf Studio and reinstall it, maybe the new driver installation solves anything?

    EDIT: I have uninstalled and reinstalled SmartRF Studio, but there are no changes related to what I previously posted.

    Thank's again!!

  • 0 in reply to user4961586
    TI__Expert 4860 points
    You could also try to reinstall the drivers manually. The drivers can be found together with SmartRF Studio here: ..\SmartRF Tools\Drivers\xds110
  • 0 in reply to Øyvind K
    Prodigy 70 points

    I tried what you told me. But Windows doesn't install them. This is what I get:

    Typical "Windows encountered a problem installing the driver software for your device" window.

    What else can I try? Maybe uninstall and reinstall CodeComposer Studio too?

  • 0 in reply to user4961586
    TI__Expert 4860 points

    I have got a confirmation that there should normally not be any problem with FW update from 7.0.48.0 of the Launchpad.

    From the Device Manager I can see 4 entries under "Otros dispositivos". Shouldn't that have been just two? (For the L40000V8)

    I understood that one card was working fine with SmartRF Studio? (L400016H) That means the device should be listed in Device Manager without a warning about the driver.

    If you installed SmartRF Studio after the installation of the EMU pack, you could try to reinstall the EMU pack again.

    Best Regards,

    Øyvind

  • 0 in reply to Øyvind K
    Prodigy 70 points

    Sorry for the late reply.

    Øyvind K said:

    I have got a confirmation that there should normally not be any problem with FW update from 7.0.48.0 of the Launchpad.

    How can I see my version? I know I've downloaded 7.0.48.0 emupack, but when typing xdsdu -e the version that appears is 2.3.0.7 as you can see at the previous screens.

    Øyvind K said:

    From the Device Manager I can see 4 entries under "Otros dispositivos". Shouldn't that have been just two? (For the L40000V8)

    There are no longer 2 devices for the L40000V8 since I tried uninstalling its drivers, and I'm not able to reinstall them again.

    Øyvind K said:

    I understood that one card was working fine with SmartRF Studio? (L400016H) That means the device should be listed in Device Manager without a warning about the driver.

    If you installed SmartRF Studio after the installation of the EMU pack, you could try to reinstall the EMU pack again.

    Best Regards,

    Øyvind

    Although one card works fine with SmartRf Studio, there is a warning on two drivers in Device Manager as shown in previous screens.

    I've tried uninstalling all TI related software and drivers: CCS, Emupack, RFStudio, CloudManager, etc. and then reinstalled again to no avail. I keep on with the same problem.

    I've also tried again to ground first TDO, and then TCK, but there is no way to enter in DFU mode.

    Please, is there anything else I can try? I bought both LaunchPads at Mouser, should I request for warranty there or I must do it here?

    Thank's a lot again!

  • 0 in reply to user4961586
    TI__Expert 4860 points

    A request for the warranty must be done through Mouser.

    The version that you see using xdsdfu -e is the FW version. "2.3.0.7" is a FW version that was included in a EMU pack prior to version 7.0.48.0. If the xds110 debugger is programmed with the FW version following the latest EMU pack you should see version "2.3.0.8".

    Don't know if I have already mentioned it, but when doing the FW update it is recommended to have just one board connected. I have seen cases where the FW updated have failed when more than one board has been connected.

    You should also try to do the manual driver installation with only one board connected. From the last screenshot it seems that both are connected. Very strange though that the board should work in SmartRF Studio even if indicated with a not functional driver in the Device Manager. 

    Regards,

    Øyvind

  • 0 in reply to Øyvind K
    Prodigy 70 points

    Hello,

    I've just had one board connected everytime I've tried to update firmware, so already tried manual driver with just one board.

    The last screenshot belongs to the board whose drivers I uninstalled.

    This is device manager for the board that works with SmartRF Studio (also was the same for the other one before I tried uninstalling drivers):

    This is device manager for the board with uninstalled XDS110 Class drivers (I am not able to install them again):

    I have contacted Mouser and they have told me to facilitate them this url so they can dig into what it's happening.

    I hope I can get a solution soon as I need both boards for an ongoing project.

    Thank's a lot for your help!

  • 0 in reply to Øyvind K
    Prodigy 70 points

    Hi,

    I've received 2 new boards from Mouser. I would like to know if there is a recommended way or order to install software and update firmware in order to not have the previous problem.

    Thank's!

  • 0 in reply to user4961586
    TI__Expert 4860 points

    Normally this should work fine the way you did it. The most important thing is to have only one board connected at the time of FW update. The second thing, and that is a bit confusing using CCS, it is important to keep the board connected until the process is finished. The dialog with the update button does not disappear when the process is finished. You have to follow the messages given in the console window and when it says it is finished you can click the "cancel" button to remove the dialog. I think the "finish" message is even given as a warning. Not sure why that is though.

    Regards,
    Øyvind

  • 0 in reply to Øyvind K
    Prodigy 70 points

    Hi,

    There has been no problem with these new boards that I got.

    Thank's a lot for your help!