TMDSEMU110-U: Firmware Update

Hi Mark,

Is this a problem with only the xdsdfu firmware update utility? Can you see the debugger in Device Manager > Ports on your computer (assuming Windows)?

Best Regards,

Ben Collier

Hi Ben, 

could see the debugger in the windows device manager before IAR forced to update its firmware. 

Hi Mark,

This page has instructions for debugging XDS110 when the device is not visible to your computer in normal operation mode. The instructions are near the bottom under the 'Flashing the bootloader' title. 

Best Regards,

Ben Collier

Hi Ben, here is the response of my customer.

Like which are in the XDS110SupportReadMe.pdf file.  Shorting JTAG TDO pin 97 to ground, powering up, and then removing the short does not show the XDS110 on the USB port and does not put it in DFU mode.

Hoping for further support.

Thank you

-Mark

Hi Mark,

Unfortunately I am not aware of another way to troubleshoot the XDS110. Could you reach out to IAR and ask what the firmware update did to the device? 

Best Regards,
Ben Collier

Hi Ben, can you assist us redirect this post for further support?

Thank you

Hi Mark,

I am reaching out to another expert on this topic, I would expect a response tomorrow.

Best Regards,

Ben Collier

Hi Mark,

I have a few additional questions:

-Are you working with the standalone XDS110 debug probe?

-How exactly was the firmware update done? Was it does from the command-line using xdsdfu? If so, what version of xdsdfu and firrmware.bin file was used?

-Is the debug probe no longer being detected if you run xdsdfu -e?

-What does Windows Device Manager display? Does it show any XDS110 information? Does it even show "Stellaris Device Firmware Upgrade"? Or does it not show anything related to it at all?

-Did you try using the probe on a different PC?

Thanks

ki

Hi Ki,

-Are you working with the standalone XDS110 debug probe? -YES

-How exactly was the firmware update done? Was it does from the command-line using xdsdfu? If so, what version of xdsdfu and firrmware.bin file was used? - It was updated by IAR Workspace 7.5

-Is the debug probe no longer being detected if you run xdsdfu -e?

No its not

-What does Windows Device Manager display? Does it show any XDS110 information? Does it even show "Stellaris Device Firmware Upgrade"? Or does it not show anything related to it at all? 

-  The first time I plugged it in, it was recognized in Windows Device Manager as a TI Debug Probe. After the attempted firmware upgrade, it was never recognized and never showed the Stellaris message. When plugged in to a Windows computer, nothing happens, meaning no audio tone indicating a device was plugged in and nothing related to it is shown in the Windows Device Manager. I have attempted the documented unbricking procedure several times.

-Did you try using the probe on a different PC?

- Yes, and with different known good USB cables

Thank you.

Mark Philip Felipe said:

-Did you try using the probe on a different PC?

- Yes, and with different known good USB cables

I assume the result on the differnt PC was the same (probe was not detected).

I'm afraid that the debug probe may have been "bricked" during the attempted firmware update without an option for recovery.

The customer can try taking apart the XDS110 pod. There should be a 10-pin JTAG header on the PCB that they can try connecting another JTAG probe to and then use CCS to debug the TM4C1294NCPDT on the PCB. See if CCS can connect and then download the boot_loader.axf file.

Note that I had issues using another XDS110 to debug the broken XDS110. I found that using a different class probe like XDS100v2 or XDS200 worked better.

Thanks

ki

Hi Ki, here is their response

Already done that using the Keil MDK5 tools and Keil ULINK2 JTAG adapter. It doesn't recognize the presence of the XDS110. I verified the cabling matches up between the header connector on the ULINK2 and the XDS110. I had to take both of them apart to do it. I installed the TM4C1294NCPDT package on the Keil MDK5 tools to make sure it could support that processor.  Also used that header connector in the XDS110 to ground the processor JTAG TDO pin while unplugging and reattaching the XDS110 to the computer's USB port, per the "debricking" instructions in XDS110 support readme file. I verified that the signal in the JTAG header was actually connected to the CPU pin 97.

Thank you.

Unfortunately I don't have any more suggestions to provide. They may have to look at replacing the debug probe.