Broken USB conncetion: device descriptor read/64, error -32

superher0 · 2016-04-23 12:31:24

Hi as follow up to this post it seems a hardware issue.

Maybe someone can tell me which parts to check...

Output from dmesg (Ubuntu 14.04.5 x64)

[ 4592.251008] usb 3-1.2: new full-speed USB device number 43 using ehci-pci
[ 4593.963807] usb 3-1.2: new full-speed USB device number 44 using ehci-pci
[ 4594.035845] usb 3-1.2: device descriptor read/64, error -32
[ 4594.211922] usb 3-1.2: device descriptor read/64, error -32
[ 4594.387955] usb 3-1.2: new full-speed USB device number 45 using ehci-pci
[ 4594.459985] usb 3-1.2: device descriptor read/64, error -32
[ 4594.636116] usb 3-1.2: device descriptor read/64, error -32
[ 4594.812177] usb 3-1.2: new full-speed USB device number 46 using ehci-pci
[ 4595.220305] usb 3-1.2: device not accepting address 46, error -32
[ 4595.292376] usb 3-1.2: new full-speed USB device number 47 using ehci-pci
[ 4595.700607] usb 3-1.2: device not accepting address 47, error -32
[ 4595.700863] usb 3-1-port2: unable to enumerate USB device

Flashing with OpenOCD and Buspirate over JTAG works fine.
But USB connection to the AT91SAM7S256 is broken.

Thanks

iceman · 2016-04-23 13:17:25

Is this a usb3.0 port?

superher0 · 2016-04-23 13:21:01

iceman wrote:

Is this a usb3.0 port?

No.

iceman · 2016-04-23 14:11:04

So, you tried different usbports, tried different usbcables, made sure the usbcontact is not loose on the pm3 pcb board?.

superher0 · 2016-04-23 15:38:27

Yes all check. Still doesn't work. I guess I will try connecting the AT91 directly and see what happens.

iceman · 2016-04-23 16:30:35

If you bought the pm3 recently? You may consider RMA it..

Or try it on a different computer...

superher0 · 2016-04-25 09:07:41

I recently figured out the reason:

As you can see here on the pinout and in the documentation of the AT91SAM7S256:

XT2 is responsible for the USB to work. I had trouble with the crystals. New crystals are arriving today. It should fix the issue.

iceman · 2016-04-25 09:13:45

You seem to be well versed on hardware. Good that you figured the reason out, maybe you can explain how to program the FPGA

superher0 · 2016-04-25 09:16:19

iceman wrote:

You seem to be well versed on hardware. Good that you figured the reason out, maybe you can explain how to program the FPGA

Thank you, just digging into the pm3. I built it myself, ordered the parts 2 months ago. So if there is anything I can answer I am glad to help

iceman · 2016-04-25 09:19:09

It just me who has a hard time understanding the electronic part becoming a digital signal. The whole verilog part where things happens all at the same time which doesn't make sense to me.

superher0 · 2016-04-25 09:22:02

iceman wrote:

It just me who has a hard time understanding the electronic part becoming a digital signal. The whole verilog part where things happens all at the same time which doesn't make sense to me.

Yes for me it's too much at the moment too. I was just sad spending so much money on the parts and time for soldering and I did not know what the root cause was for the bad usb when the pm3 itsself seemed working. So after UPS arrives I can solder the crystals.

iceman · 2016-04-25 09:41:07

great project, but myself I wouldn't have managed to make one. Soldering and all. I buy it instead.

superher0 · 2016-04-25 12:57:32

Prox/RFID mark3 RFID instrument          
bootrom: /-suspect 2015-11-19 10:08:02
os: /-suspect 2015-11-19 10:08:09
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at  9: 8: 8
uC: AT91SAM7S256 Rev D          
Embedded Processor: ARM7TDMI          
Nonvolatile Program Memory Size: 256K bytes. Used: 169916 bytes (65%). Free: 92228 bytes (35%).          
Second Nonvolatile Program Memory Size: None          
Internal SRAM Size: 64K bytes          
Architecture Identifier: AT91SAM7Sxx Series          
Nonvolatile Program Memory Type: Embedded Flash Memory

Yeah

ntk · 2017-04-08 14:20:18

Hi, I have to revival this thread. Could you tell me on the board where is the crystal XT2? And is there anyway to check that the crystal is working or not. I have similar fault on my PM3 bought 2 yrs ago "USB device not recognised"

edit:
Tourned out that my board has not got the same HW fault with the crystal XT2.

The history was: Proxmark will no longer boot; connect to PC I got fault report "USB device not recognised"; 4 LED lights constantly lit.

Using the Segger Jlink and following the setup in the thread
"Play with JTAG" by Asper

AND the recovery procedure on GIT
https://github.com/Proxmark/proxmark3/wiki/Compiling#jtag-recovery-procedure,

I have been able to recover my proxmark

Last edited by ntk (2017-04-08 18:10:26)

Proxmark3 community

Announcement

#1 2016-04-23 12:31:24

Broken USB conncetion: device descriptor read/64, error -32

#2 2016-04-23 13:17:25

Re: Broken USB conncetion: device descriptor read/64, error -32

#3 2016-04-23 13:21:01

Re: Broken USB conncetion: device descriptor read/64, error -32

#4 2016-04-23 14:11:04

Re: Broken USB conncetion: device descriptor read/64, error -32

#5 2016-04-23 15:38:27

Re: Broken USB conncetion: device descriptor read/64, error -32

#6 2016-04-23 16:30:35

Re: Broken USB conncetion: device descriptor read/64, error -32

#7 2016-04-25 09:07:41

Re: Broken USB conncetion: device descriptor read/64, error -32

#8 2016-04-25 09:13:45

Re: Broken USB conncetion: device descriptor read/64, error -32

#9 2016-04-25 09:16:19

Re: Broken USB conncetion: device descriptor read/64, error -32

#10 2016-04-25 09:19:09

Re: Broken USB conncetion: device descriptor read/64, error -32

#11 2016-04-25 09:22:02

Re: Broken USB conncetion: device descriptor read/64, error -32

#12 2016-04-25 09:41:07

Re: Broken USB conncetion: device descriptor read/64, error -32

#13 2016-04-25 12:57:32

Re: Broken USB conncetion: device descriptor read/64, error -32

#14 2017-04-08 14:20:18

Re: Broken USB conncetion: device descriptor read/64, error -32

Board footer