Part Number:LAUNCHXL-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!!