Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

superher0 · 2016-04-23 09:24:52

Hi both Windows 7 64bit and Ubuntu 14.04.5 LTS are not recognizing my proxmark3.

I flashed the fullimage and bootloader as written in the wiki via JTAG.

If I connect the pm3 to the usb I hear the relay clicking, red and orange led lighting up, turning off and the the other red led is lighting up for 1 second then all leds are off. If I press the button 3 seconds the red, orange, green leds are running one after another and then the two red leds are lighting up.

In Ubuntu it says it cannot enumerate the usb_ehci device. I will update the post from Ubuntu in a few seconds.

Can anybody help please? Latest firmware from Github compiled without errors. modemmanager is unistalled. User added to dialout group as well.

iceman · 2016-04-23 09:47:29

Whats the output from tail | dmesg?

superher0 · 2016-04-23 09:52:03

[ 221.834977] usb 1-2: new full-speed USB device number 23 using xhci_hcd
[ 221.835179] usb 1-2: Device not responding to setup address.
[ 222.039325] usb 1-2: Device not responding to setup address.
[ 222.243346] usb 1-2: device not accepting address 23, error -71
[ 222.243425] usb usb1-port2: unable to enumerate USB device

iceman · 2016-04-23 10:37:41

Where did I read about linux and xhci_hcd is not good with the proxmark3?

Here is the ref post:
http://www.proxmark.org/forum/viewtopic … 7676#p7676

superher0 · 2016-04-23 10:45:39

Thanks but still same error:
[ 100.870051] usb 3-1.2: device not accepting address 6, error -32
[ 100.942226] usb 3-1.2: new full-speed USB device number 7 using ehci-pci
[ 101.350519] usb 3-1.2: device not accepting address 7, error -32
[ 101.350799] usb 3-1-port2: unable to enumerate USB device

iceman · 2016-04-23 10:52:55

What kind of OS are you running?

superher0 · 2016-04-23 10:54:14

superher0 wrote:

Windows 7 64bit and Ubuntu 14.04.5 LTS

iceman · 2016-04-23 11:19:00

well, thats two different OS, since you are not using both at the same time, shall I assume you are running Ubuntu with these errors? Or do you have the same error on Win7?

superher0 · 2016-04-23 11:21:16

iceman wrote:

well, thats two different OS, since you are not using both at the same time, shall I assume you are running Ubuntu with these errors? Or do you have the same error on Win7?

Windows gives unknow device as written in the topic.
When I run Ubuntu it gives the error as posted.

iceman · 2016-04-23 11:32:39

ok, I see. two different errors in same thread. Would been easier if you started two threads instead.

Anyway, You device seems to send vid000,pid000 which is quite wrong. Is it an old model or new?
JTAG, did you clone and compile the latest source from github as base for your jtag writing?
Have you tried unconnect usb, press and keep pressing the button, connect the usb, then flash bootrom and fullimage in one go?

superher0 · 2016-04-23 11:34:04

Yes, I did all that it is the 4 layer pcb from JW.

iceman · 2016-04-23 11:36:16

what arm does it use?

superher0 · 2016-04-23 11:38:20

iceman wrote:

what arm does it use?

AT91SAM7S256D AU

iceman · 2016-04-23 11:41:12

hm, you have 256kb then, it should fit.

superher0 · 2016-04-23 11:44:14

Chip looks fine through OpenOCD with Buspirate:

> flash info 0
#0 : at91sam7 at 0x00100000, size 0x00040000, buswidth 4, chipwidth 0
	#  0: 0x00000000 (0x4000 16kB) not protected
	#  1: 0x00004000 (0x4000 16kB) not protected
	#  2: 0x00008000 (0x4000 16kB) not protected
	#  3: 0x0000c000 (0x4000 16kB) not protected
	#  4: 0x00010000 (0x4000 16kB) not protected
	#  5: 0x00014000 (0x4000 16kB) not protected
	#  6: 0x00018000 (0x4000 16kB) not protected
	#  7: 0x0001c000 (0x4000 16kB) not protected
	#  8: 0x00020000 (0x4000 16kB) not protected
	#  9: 0x00024000 (0x4000 16kB) not protected
	# 10: 0x00028000 (0x4000 16kB) not protected
	# 11: 0x0002c000 (0x4000 16kB) not protected
	# 12: 0x00030000 (0x4000 16kB) not protected
	# 13: 0x00034000 (0x4000 16kB) not protected
	# 14: 0x00038000 (0x4000 16kB) not protected
	# 15: 0x0003c000 (0x4000 16kB) not protected

 at91sam7 driver information: Chip is AT91SAM7S256
 Cidr: 0x270b0943 | Arch: 0x0070 | Eproc: ARM7TDMI | Version: 0x003 | Flashsize: 0x00040000
 Master clock (estimated): 55296 KHz | External clock: 18432 KHz
 Pagesize: 256 bytes | Lockbits(16): 0 0x0000 | Pages in lock region: 0
 Securitybit: 0 | Nvmbits(2): 0 0x0

iceman · 2016-04-23 11:48:09

Tried swapping to a high power usb port?

superher0 · 2016-04-23 11:51:00

iceman wrote:

Tried swapping to a high power usb port?

yes, tried also another windows machine, even with y-cable and external power no change

superher0 · 2016-04-23 11:53:26

I thought maybe trying to connect the AT91SAM7S256 to USB directly to see if it is a pcb or mc issue.

Last edited by superher0 (2016-04-23 11:56:39)

superher0 · 2016-04-23 12:02:29

Just found this information which is the reason:

[ 4594.636116] usb 3-1.2: device descriptor read/64, error -32

Don't know where it comes from. Connection to USB D- and USB D+ seem ok also values of R4 and R5.

superher0 · 2016-04-23 12:03:42

According to this external post this is a hardware error. So I started a thread in the Hardware section.

Last edited by superher0 (2016-04-23 12:32:37)

ntk · 2016-04-23 12:50:12

I am not expert on HW fault. But have you tried post#1 of this thread
http://www.proxmark.org/forum/viewtopic.php?id=1562

concentrate on the part changing your port to CDC serial? It may help

superher0 · 2016-04-23 12:59:52

ntk wrote:

I am not expert on HW fault. But have you tried post#1 of this thread
http://www.proxmark.org/forum/viewtopic.php?id=1562
concentrate on the part changing your port to CDC serial? It may help

Thank you unfortunately I cannot connect to the proxmark3 via USB at all.

iceman · 2016-04-23 13:16:49

Is it a usb3.0 port?

superher0 · 2016-04-23 13:20:00

iceman wrote:

Is it a usb3.0 port?

No.

ntk · 2016-04-23 14:55:52

can you disconnect all USB devices; check in device manager under USB controller, double click to open each strain make sure all "ghost" USB\serial connections are deleted\uninstalled, reboot the machine properly, (=with power off then ON). Since win7 this error happen, appeared when you can not set COM 2,3,4,5 etc manually. In XP when a device is unattached the driver and the COM is cleared; in later win versions it remembers somehow cause connection problem.

After checking the device manager reboot and win still not sees proxmark, you can use this http://www.libusb.org/wiki/libusb-win32it is reported to fix a lot of USB device connection problem

Last edited by ntk (2016-04-23 15:03:48)

superher0 · 2016-04-23 15:37:03

ntk wrote:

can you disconnect all USB devices; check in device manager under USB controller, double click to open each strain make sure all "ghost" USB\serial connections are deleted\uninstalled, reboot the machine properly, (=with power off then ON). Since win7 this error happen, appeared when you can not set COM 2,3,4,5 etc manually. In XP when a device is unattached the driver and the COM is cleared; in later win versions it remembers somehow cause connection problem.
After checking the device manager reboot and win still not sees proxmark, you can use this http://www.libusb.org/wiki/libusb-win32it is reported to fix a lot of USB device connection problem

Thank you I already installed the libusb for Windows, since it happens on both Windows and Linux this is no OS issue.

superher0 · 2016-04-25 09:08:58

Solution can be found in this post

Proxmark3 community

Announcement

#1 2016-04-23 09:24:52

Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#2 2016-04-23 09:47:29

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#3 2016-04-23 09:52:03

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#4 2016-04-23 10:37:41

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#5 2016-04-23 10:45:39

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#6 2016-04-23 10:52:55

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#7 2016-04-23 10:54:14

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#8 2016-04-23 11:19:00

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#9 2016-04-23 11:21:16

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#10 2016-04-23 11:32:39

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#11 2016-04-23 11:34:04

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#12 2016-04-23 11:36:16

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#13 2016-04-23 11:38:20

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#14 2016-04-23 11:41:12

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#15 2016-04-23 11:44:14

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#16 2016-04-23 11:48:09

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#17 2016-04-23 11:51:00

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#18 2016-04-23 11:53:26

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#19 2016-04-23 12:02:29

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#20 2016-04-23 12:03:42

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#21 2016-04-23 12:50:12

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#22 2016-04-23 12:59:52

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#23 2016-04-23 13:16:49

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#24 2016-04-23 13:20:00

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#25 2016-04-23 14:55:52

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#26 2016-04-23 15:37:03

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

#27 2016-04-25 09:08:58

Re: Not recognized VID_0000&PID_0000\5&1E41AFF0&0&1

Board footer