cancel
Showing results for 
Search instead for 
Did you mean: 

USB Low-Full-High Speed Peripherals

Anonymous
Not applicable

Hi all,

I have two boards with CY7C68013A which fail to enumerate. When I attach the boards to USB on the PC I can not see

Bus 001 Device 003: ID 04b4:8613 Cypress Semiconductor Corp. CY7C68013 EZ-USB FX2 USB 2.0 Development Kit

when running lsusb command on Linux.

In the dmesg I only see:

[root@ftrn-test-box chamber_test]# dmesg --follow

[22130.828634] usb 2-1.7: new full-speed USB device number 52 using ehci-pci

[22130.902630] usb 2-1.7: device descriptor read/64, error -32

[22131.077608] usb 2-1.7: device descriptor read/64, error -32

[22131.251608] usb 2-1.7: new full-speed USB device number 53 using ehci-pci

[22131.325604] usb 2-1.7: device descriptor read/64, error -32

[22131.500553] usb 2-1.7: device descriptor read/64, error -32

[22131.674549] usb 2-1.7: new full-speed USB device number 54 using ehci-pci

[22132.076527] usb 2-1.7: device not accepting address 54, error -32

[22132.149534] usb 2-1.7: new full-speed USB device number 55 using ehci-pci

[22132.551505] usb 2-1.7: device not accepting address 55, error -32

[22132.551630] usb 2-1-port7: unable to enumerate USB device

I see this response when I connect the board with USB cable or when I reset Cypress (once the board is connected via USB).

And it makes no difference if I2C EEPROM is connected or not.

Thing here is that that up until previous week I had no such issue with many boards in the past three years. Usually only one board would be connected to the PC, maybe two when test were done.

But I need to test many boards and for that I would like to connect 8-10 boards to one PC via USB hub.

Therefore I tried to connect 8 boards using two USB hubs. And after that inital test two boards fail to enumerate.

My questions are:

1. Could USB hub damage Cypress IC in a way that it would not enumerate even with default Cypress IDs?

2. Is there a way to restore IC back to factory settings?

Thanks!

Schematic (page 7, bottom left):

https://www.ohwr.org/projects/tr-pmc/repository/revisions/master/entry/PMC_REVB/FTRN_PMC_REVB_SCH/ft...

USB micro sources:

https://www.ohwr.org/projects/etherbone-core/repository/hdl/eb_usb_core?utf8=%E2%9C%93&rev=ba955bc&b...

Essentialy USB micro is erased by:

fxload -D "$dev" -tfx2lp -I erase_eeprom.ihx -v

and then flashed by

fxload -D "$dev" -tfx2lp -I cdc_acm.ihx -s vend_ax.hex -c 0x41 -v

0 Likes
1 Solution
SrinathS_16
Moderator
Moderator

The root cause of the failure was identified to be EOS (Electrical Over Stress) on the ICs.

View solution in original post

0 Likes
3 Replies
SrinathS_16
Moderator
Moderator

Hello,

- Please connect the failed devices on a Windows host and check if there are any error messages displayed. If yes, please share the screenshot of the errors along with the USB traces captured during enumeration.

Best regards,

Srinath S

0 Likes
Anonymous
Not applicable

Hi Srintah,

It was the same on the Windows 10:FTRN_revC_USB_uC_enumeration_issue_WIN10.PNGFTRN_revC_USB_uC_enumeration_issue_WIN10_device_manager.PNG

But my colleague already opened a case (#00474505) and the two microcontrolles were sent to Cypress for analysis.

Best regards,

Dusan Slavinec

0 Likes
SrinathS_16
Moderator
Moderator

The root cause of the failure was identified to be EOS (Electrical Over Stress) on the ICs.

View solution in original post

0 Likes