TDA4VM: xds110 with custom board - doesn't connect

Hiren Vora

Part Number: TDA4VM

We followed the steps and install the CCS and drivers on Linux PC to connect to XDS110 debug target. We have some issues connecting XDS110 debugger. The usb product shows as TIVA Device Firmware Update. We have updated XDS110 firmware. The device is not getting out of the DFU mode. software-dl.ti.com/.../emu_xds110.html

adas@adas:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 2357:0601
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 27c6:5395
Bus 001 Device 003: ID 0cf3:e301 Atheros Communications, Inc.
Bus 001 Device 002: ID 1cbe:00ff Luminary Micro Inc. Stellaris ROM DFU Bootloader
Bus 001 Device 005: ID 0c45:671d Microdia
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
adas@adas:~$ usb-devices

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=16
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=04.15
S: Manufacturer=Linux 4.15.0-136-generic xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:00:14.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=01 Lev=01 Prnt=01 Port=11 Cnt=01 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0c45 ProdID=671d Rev=81.31
S: Manufacturer=CN0VGCNHLOG008CVAD1BA00
S: Product=Integrated_Webcam_HD
C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo
I: If#= 1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo

T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1cbe ProdID=00ff Rev=00.01
S: Manufacturer=Texas Instruments Incorporated
S: Product=Tiva Device Firmware Update
S: SerialNumber=00000000
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=02 Driver=(none)

T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=03 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=e301 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=04 Dev#= 4 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=27c6 ProdID=5395 Rev=01.00
S: Manufacturer=HTMicroelectronics
S: Product=Goodix Fingerprint Device
S: SerialNumber=HTK32
C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=10000 MxCh=10
D: Ver= 3.10 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev=04.15
S: Manufacturer=Linux 4.15.0-136-generic xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:00:14.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
D: Ver= 3.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 2
P: Vendor=2357 ProdID=0601 Rev=30.00
S: Manufacturer=TP-LINK
S: Product=USB 10/100/1000 LAN
S: SerialNumber=000001000000
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=256mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=r8152

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=04.15
S: Manufacturer=Linux 4.15.0-136-generic xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:3a:00.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub

T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=10000 MxCh= 2
D: Ver= 3.10 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1
P: Vendor=1d6b ProdID=0003 Rev=04.15
S: Manufacturer=Linux 4.15.0-136-generic xhci-hcd
S: Product=xHCI Host Controller
S: SerialNumber=0000:3a:00.0
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
adas@adas:~$

over 4 years ago

0 Karan Saxena over 4 years ago

TI__Guru* 77854 points

Hi Hiren,

One quick thing to check would be, if you have the same issue on a windows machine too. Can you please confirm?

Regards,

Karan

0 Hiren Vora over 4 years ago

Intellectual 260 points

Hi Karan,

Same results on the Windows based CCS. We have tried windows machine as well.

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

Hello,

You may need to re-flash the bootloader:

https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#flashing-the-bootloader

Are you using a standalone XDS110 or one that is integrated with a board?

Thanks

0 Hiren Vora over 4 years ago

Intellectual 260 points

@Ki - We are using integrated XDS110 on board. We will try the bootloader flashing.

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

Since the probe is already in DFU mode, you should be able to execute step 5 to flash the boot loader. Let me know if that resolves the issue.

Thanks

0 Hiren Vora over 4 years ago in reply to Ki

Intellectual 260 points

In my original post, I have mentioned the same link and updated that we've flashed the firmware/bootloader of XDS110. The result was not different. XDS110 was not able to out from this DFU mode even after flashing. We will reattempt the same.

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

In the original post, you mentioned flashing the firmware. It was unclear if you tried flashing the bootloader. When you flash boot_loader.bin, is it successful? How does the XDS110 appear in Windows Device Manager? Does it show up as "Stellaris Device Firmware Upgrade"?

0 Hiren Vora over 4 years ago in reply to Ki

Intellectual 260 points

Pic# 1: Windows Device manager with Stellaris Device Firmware Upgrade

Pic#2 : Output of xdsdfu.ext -e

0 Hiren Vora over 4 years ago in reply to Hiren Vora

Intellectual 260 points

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>dir
Volume in drive C has no label.
Volume Serial Number is 4C18-29FD

Directory of C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110

02/01/2021 06:43 PM <DIR> .
02/01/2021 06:43 PM <DIR> ..
11/25/2019 07:58 PM 73,148 boot_loader.axf
11/25/2019 07:58 PM 6,182 boot_loader.bin
11/25/2019 07:58 PM 3,227 eZ_FetDcdcController.txt
11/25/2019 07:58 PM 251,880 firmware.bin
11/25/2019 07:58 PM 141,824 xds110reset.exe
11/25/2019 07:58 PM 118,438 XDS110SupportReadMe.pdf
11/25/2019 07:58 PM 177,152 xdsdfu.exe
7 File(s) 771,851 bytes
2 Dir(s) 27,567,374,336 bytes free

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdful.exe -e
'xdsdful.exe' is not recognized as an internal or external command,
operable program or batch file.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu -b boot_loader.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Replacing the bootloader may render the XDS110 unusable.
Do you want to continue (Y/N) ? Y
Scanning USB buses for supported XDS110 devices...

Downloading boot_loader.bin to device...

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu -b boot_loader.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Replacing the bootloader may render the XDS110 unusable.
Do you want to continue (Y/N) ? Y
Scanning USB buses for supported XDS110 devices...

Downloading boot_loader.bin to device...
Error DFU_ERR_VERIFY_FAIL (-14) reported during file download

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>

0 Hiren Vora over 4 years ago in reply to Hiren Vora

Intellectual 260 points

Error DFU_ERR_VERIFY_FAIL (-14) reported during file download

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

Hiren Vora said:
Error DFU_ERR_VERIFY_FAIL (-14) reported during file download

Interesting. It is failing the file verification of the boot loader bin.

And if you run xdsdfu -f firmware.bin -r what does the results look lile?

0 Ki over 4 years ago in reply to Ki

TI__Guru**** 466071 points

Ki said:
And if you run xdsdfu -f firmware.bin -r what does the results look lile?

does it appear successful but still stuck in DFU mode I assume?

0 Hiren Vora over 4 years ago in reply to Ki

Intellectual 260 points

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu -f firmware.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

Downloading firmware.bin to device...
Error DFU_ERR_VERIFY_FAIL (-14) reported during file download

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

Thanks. Same file verification error. This likely points to a more complex issue.

You mentioned that this is a custom board with an on-board XDS110. Did the XDS110 ever work on this board or this is the first attempt to get it working? Are there any other similar boards you have where the XDS110 is working?

0 Hiren Vora over 4 years ago in reply to Ki

Intellectual 260 points

Ki - I am trying to operate XDS110 the first time. One of my colleagues has XDS110 working on the same custom board.

Do you like me to try something else now on XDS110?

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

Hiren Vora said:
I am trying to operate XDS110 the first time. One of my colleagues has XDS110 working on the same custom board.

Your colleague was able to get everything working on the SAME board? If so, can your colleague see if they can still get it to work in their environment?

0 Hiren Vora over 4 years ago in reply to Ki

Intellectual 260 points

Ki - we have tried that environment ( Linux based), but there is no luck on this board. My colleague has recommended to work to update firmware, but that doesn't work. ( As he faced some error when he brought up the XDS110 for the custom board) . Colleague works remotely so trying the environment from that PC is not possible.

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

Ok, so if I understand correctly, it sounds like it once worked fine but something went awry and it is no longer working. The verification error is an uncommon one. I will need to follow up with engineering for more details

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

When looking at:

Hiren Vora said:
<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu -b boot_loader.bin -r

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Replacing the bootloader may render the XDS110 unusable.
Do you want to continue (Y/N) ? Y
Scanning USB buses for supported XDS110 devices...

Downloading boot_loader.bin to device...

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x1cbe PID: 0x00ff
Device Name: Tiva Device Firmware Update
Manufacturer: Texas Instruments Incorporated
Serial Num: 00000000
Mode: DFU

Found 1 device.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -e

USB Device Firmware Upgrade Utility
Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

Scanning USB buses for supported XDS110 devices...

It looks like the first time you flashed the boot loader, it was successful (no verification error). Then I see you ran xdsdfu -e right after. The troubleshooting guide says to wait a few minutes to give the flashing operation time to flash the boot loader, and then unpluf and replug in the USB cable before issuing the xdsdfu -e command. Can you confirm that you did those steps for running the xdsdfu -e command after flashing the boot loader?

0 Hiren Vora over 4 years ago in reply to Ki

Intellectual 260 points

I waited for 10 to 15 mins after xdsdfu -b boot_loader.bin -r ( before running xdsdfu -e.). And I didn't do USB plug and unplug.

0 Hiren Vora over 4 years ago in reply to Hiren Vora

Intellectual 260 points

Ki -

Looks like the Power cycle of the PC and Target made the XDS110 working.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>xdsdfu.exe -e

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3
Device Name: XDS110 Embed with CMSIS-DAP
Version: 3.0.0.7
Manufacturer: Texas Instruments
Serial Num: 00000000
Mode: Runtime
Configuration: Standard

Found 1 device.

C:\ti\ccs930\ccs\ccs_base\common\uscif\xds110>

################################################################################

TEST CONNECTION on CCS Studio

TEST CONNECTION Logs:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\hvora1\AppData\Local\TEXASI~1\CCS\
ccs930\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Nov 25 2019'.
The library build time was '16:55:29'.
The library package version is '8.4.0.00006'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe_0]

0 Ki over 4 years ago in reply to Hiren Vora

TI__Guru**** 466071 points

Hiren Vora said:
Looks like the Power cycle of the PC and Target made the XDS110 working.

Great to hear! Thanks for the update!

Processors

Processors forum

TDA4VM: xds110 with custom board - doesn't connect