J722SXH01EVM: Built-in XDS110 does not work

Tyler Middleton

Hello,
I'm having an issue with the XDS110 on the J722SXH01EVM.

When I plug in our external XDS110, I get the following log in `dmesg`, and the probe is visible in CCS:

```
[ 540.910161] usb 1-6.2.1: new high-speed USB device number 10 using xhci_hcd
[ 541.011173] usb 1-6.2.1: New USB device found, idVendor=0451, idProduct=bef3, bcdDevice= 1.00
[ 541.011184] usb 1-6.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 541.011188] usb 1-6.2.1: Product: XDS110 (03.00.00.29) Probe with CMSIS-DAP
[ 541.011191] usb 1-6.2.1: Manufacturer: Texas Instruments
[ 541.011193] usb 1-6.2.1: SerialNumber: NOserial
[ 541.117204] cdc_acm 1-6.2.1:1.0: ttyACM0: USB ACM device
[ 541.217977] cdc_acm 1-6.2.1:1.3: ttyACM1: USB ACM device
[ 541.219386] hid-generic 0003:0451:BEF3.0007: hiddev2,hidraw6: USB HID v1.11 Device [Texas Instruments XDS110 (03.00.00.29) Probe with CMSIS-DAP] on usb-0000:00:14.0-6.2.1/input5
```

However, when I plug in the J722SXH01EVM I get the following:
```

[ 541.219386] hid-generic 0003:0451:BEF3.0007: hiddev2,hidraw6: USB HID v1.11 Device [Texas Instruments XDS110 (03.00.00.29) Probe with CMSIS-DAP] on usb-0000:00:14.0-6.2.1/input5
[ 613.644049] usb 1-6.2.1: USB disconnect, device number 10
[ 619.757306] usb 1-6.2.1: new full-speed USB device number 11 using xhci_hcd
[ 619.858989] usb 1-6.2.1: New USB device found, idVendor=0000, idProduct=0000, bcdDevice= 1.00
[ 619.859001] usb 1-6.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 619.859004] usb 1-6.2.1: Product: XDS110 (03.00.00.29) Embed with CMSIS-DAP
[ 619.859007] usb 1-6.2.1: Manufacturer: Texas Instruments
[ 619.859010] usb 1-6.2.1: SerialNumber: 12240201
[ 619.867283] cdc_acm 1-6.2.1:1.0: ttyACM0: USB ACM device
```

And the device does not function in TI tools, and the DFU flasher is also unable to detect it. The idVendor=0000 and idProduct=0000 leads me to believe the firmware is corrupt on the microcontroller.

Unfortunately, due to the nonstandard MIPI-60 debug connector on the J722SXH01EVM, I am not able to use our external debugger.

over 2 years ago

0 Tyler Middleton over 2 years ago

Prodigy 120 points

A bit more info:

The device enumerates incorrectly even on other computers

I was able to get the device into DFU mode by shorting the TDO pin to ground during boot. I can then flash the firmware with xdsdfu, but upon reboot the idVendor is still 0000 and the device is still not detected.

0 Ki over 2 years ago in reply to Tyler Middleton

TI__Guru**** 486311 points

Tyler Middleton said:
I was able to get the device into DFU mode by shorting the TDO pin to ground during boot. I can then flash the firmware with xdsdfu, but upon reboot the idVendor is still 0000 and the device is still not detected.

I assume you tried flashing the bootloader first and then the firmware to no avail?

In any case, we have heard of a similar issue with the onboard XDS110 of the same EVM. Hence this is not an isolated incident. We are investigating.

0 Tyler Middleton over 2 years ago in reply to Ki

Prodigy 120 points

as far as I can tell, you can't update the bootloader with xdsdfu tool. That, or the functionality is undocumented

I was able to get it running again with this hail-mary command : `./xdsdfu -c 1 -s 0451bef3 -f firmware_3.0.0.29.bin -r`
Just updating the firmware didn't work, so I assume the `-c 1` or the `-s 0451bef3` is what got it running

0 Ki over 2 years ago in reply to Tyler Middleton

TI__Guru**** 486311 points

Tyler Middleton said:
as far as I can tell, you can't update the bootloader with xdsdfu tool. That, or the functionality is undocumented

It is documented in section 3.7.3.2 of: https://www.ti.com/lit/ug/sprui94/sprui94.pdf

And also the "Flashing the bootloader" section of: https://dev.ti.com/tirex/explore/node?node=A__ALFqIj4dX6S.TZRERoSphA__xdsdebugprobes__FUz-xrs__LATEST

Tyler Middleton said:
-s 0451bef3

This would be just flashing the serial number.

Tyler Middleton said:
-c 1

This is just setting the probe to the standard configuration.

Not sure why the above would help.

In any case I'm glad that it is working for you now. Thank you for sharing your solution.

0 Tyler Middleton over 2 years ago in reply to Ki

Prodigy 120 points

I guess I got unlucky with the docs. It is missing from the `./xdsdfu -h` description and also from the `XDS110SupportReadMe.pdf` provided with CCS.
I agree it doesn't make sense, but it did work so I figured I'd post it.