• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 237 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.

MSP430F5528: ezFET USB enumeration error after firmware upgrade

Tanguy Serrat
Prodigy 10 points
Part Number: MSP430F5528
Other Parts Discussed in Thread: UNIFLASH, TUSB4020BI,

Hello, 

I've integrated an ezFET debugger on a custom PCB following design guidelines v1.10 available here. 

Here are the steps: 

1) Flash the debugger with the provided firmware using uniFlash. 
BSL: EZFET_LITE_Rev1_1_BSL_1_1.txt
FW: EZFET_LITE_Rev1_1_FW_3_3_0_6.txt

This step is successful, after reset the debugger enumerates : 

Fullscreen
1
2
3
4
5
6
7
8
[17479.096854] usb 1-4.1: new full-speed USB device number 46 using xhci_hcd
[17479.199181] usb 1-4.1: New USB device found, idVendor=2047, idProduct=0013, bcdDevice= 2.00
[17479.199184] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[17479.199186] usb 1-4.1: Product: MSP Tools Driver
[17479.199187] usb 1-4.1: Manufacturer: Texas Instruments
[17479.199188] usb 1-4.1: SerialNumber: EB30816E1D001200
[17479.213854] cdc_acm 1-4.1:1.0: ttyACM0: USB ACM device
[17479.214344] cdc_acm 1-4.1:1.2: ttyACM1: USB ACM device
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

2) Open CCS v12.2.0 and start a debugging session. CCS requires FW upgrade which I run. 
- FW upgrade is sucessful. 
- Debugging session starts. So connection to the target works correctly. 

3) Unplugging and replugging / powering off the board leads to USB enumeration errors with the upgraded firmware. 
On linux (tried also on windows) the enumeration of the device fails with the following errors :

 

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
[ 3864.797268] usb 1-4: new high-speed USB device number 20 using xhci_hcd
[ 3864.945544] usb 1-4: New USB device found, idVendor=0451, idProduct=8027, bcdDevice= 1.10
[ 3864.945559] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[ 3864.945565] usb 1-4: SerialNumber: C401085137E9
[ 3864.946511] hub 1-4:1.0: USB hub found
[ 3864.946544] hub 1-4:1.0: 2 ports detected
[ 3865.233256] usb 1-4.1: new full-speed USB device number 21 using xhci_hcd
[ 3865.313349] usb 1-4.1: device descriptor read/64, error -32
[ 3865.501369] usb 1-4.1: device descriptor read/64, error -32
[ 3865.689221] usb 1-4.1: new full-speed USB device number 22 using xhci_hcd
[ 3865.773364] usb 1-4.1: device descriptor read/64, error -32
[ 3865.961306] usb 1-4.1: device descriptor read/64, error -32
[ 3866.069434] usb 1-4-port1: attempt power cycle
[ 3866.673270] usb 1-4.1: new full-speed USB device number 23 using xhci_hcd
[ 3866.673426] usb 1-4.1: Device not responding to setup address.
[ 3866.881405] usb 1-4.1: Device not responding to setup address.
[ 3867.089265] usb 1-4.1: device not accepting address 23, error -71
[ 3867.173263] usb 1-4.1: new full-speed USB device number 24 using xhci_hcd
[ 3867.173404] usb 1-4.1: Device not responding to setup address.
[ 3867.381421] usb 1-4.1: Device not responding to setup address.
[ 3867.589276] usb 1-4.1: device not accepting address 24, error -71
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

The ez-FET 5528 MCU is behind an USB hub : TUSB4020BI. There is another STLINKV3 debugger (using high-speed usb) that works without issues.
So the USB cable doesn't seem to be the issue here. 

In the end, with the original old ezFET firmware I have no enumeration errors. I can unplug and reset the board without issues. 
However, once the firmware is upgraded, the ezFET can be used while still in the debugging session after the CCS FW upgrade. But after unplugging / resetting enumeration ends up broken. 

Can someone help me out on that issue ? 

Attached schematics of the ez-FET

Thank you 

. 

  • 0
    TI__Guru 56685 points

    Hello,

    Sorry for the late reply here. First, do you have an MSP430F5528 Launchpad handy (or any MSP430 Launchpad really) that you can try out in your environment ? This step will help narrow down the issue. 

**Attention** This is a public forum