Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
Hello folks,
I have a Proxmark3 that I purchased a few years ago. The device works fine reading and replaying tags by itself. I have not been successful with getting the device recognized in Win 7, Win XP, or Ubuntu. I assume that I am using an old firmware. In Windows XP, I can see the Proxmark recognized in the Device Manager using the proxmark drivers. When I use the ProxSpace environment, I am not able to connect to the Proxmark because no COM port is assigned in the Device Manager:
pm3 ~$ ./client/proxmark3.exe
syntax: C:\ProxSpace\pm3\client\proxmark3.exe <port>
Linux example:'C:\ProxSpace\pm3\client\proxmark3.exe /dev/ttyACM0'
pm3 ~$
When I tried to update the firmware on XP, I get the following error:
============================================
FLASHING new CDC bootrom.elf, please wait...
============================================
Loading ELF file '..\firmware_win\bootrom\bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000b60->0x00000b60) [RWX] @0x298
Attempted to write bootloader but bootloader writes are not enabled
Error while loading ..\firmware_win\bootrom\bootrom.elf
Press any key to continue . . .
I've had no luck on Ubuntu or Win 7 either.
Is there something that I am overlooking? After browsing some of the forum posts, I thought that I was performing the correct steps.
Any help would be appreciated!
Thank you much.
Offline
Just as a followup to my original post, I am using the "FLASH - NEW Bootrom (uses old flasher exe).bat" from pm3-bin-672 and still get the "Attempted to write bootloader but bootloader writes are not enabled" message.
In the Device Manager, the Proxmark3 is coming up as a USB HID at Location 0.
In Ubuntu, when I plug the Promark3 in, the dmesg output is:
[20543.544058] usb 5-1: new full-speed USB device number 9 using uhci_hcd
[20543.608098] hub 5-0:1.0: unable to enumerate USB device on port 1
[20544.512091] usb 5-1: new full-speed USB device number 10 using uhci_hcd
[20549.707315] generic-usb 0003:9AC4:4B8F.0012: hiddev0,hidraw0: USB HID v1.00 Device [J. Westhues ProxMark-3 RFID Instrument] on usb-0000:00:1d.0-1/input0
Not sure if that helps in debugging my issue, but it's a few more data points.
Thank you much!
Dan
Offline
You need to edit the "FLASH - NEW Bootrom (uses old flasher exe).bat" and add the -b option to the flasher command.
See http://www.proxmark.org/forum/viewtopic.php?id=1557
Offline
I added the -b to the command line and saw the following behavior on a Windows 7 machine:
============================================
FLASHING new CDC bootrom.elf, please wait...
============================================
Loading ELF file '..\firmware_win\bootrom\bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000b60->0x00000b60) [RWX] @0x298
Waiting for Proxmark to appear on USB...
Connected units:
1. SN: ChangeMe [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
Found.
Flashing...
Writing segments for file: ..\firmware_win\bootrom\bootrom.elf
0x00100000..0x001001ff [0x200 / 2 blocks].. OK
0x00100200..0x00100d5f [0xb60 / 12 blocks]............ OK
Resetting hardware...
write failed: libusb0-dll:err [_usb_reap_async] reaping request failed, win erro
r: A device attached to the system is not functioning.
!
Trying to reopen device...
Connected units:
1. SN: [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
proxmark3> All done.
Have a nice day!
Press any key to continue . . .
When I go to the Device Manager, the Proxmark is not coming up under the Ports. It is listed/identified under libusb-win32 devices and does not have a COM port. From the debug information above, does the bootrom update appear to have been successful?
Thanks again!
Dan
Offline
Well, from reading a few other posts, I tried proxmark3.exe from r486 and it recognized my device:
C:\Users\Rolphd\Desktop\pm3-bin-r486\Win32>proxmark3.exe
Connected units:
1. SN: ChangeMe [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 671 2013-03-07 17:12:17
#db# os: svn 486-unclean 2011-08-28 18:52:03
#db# FPGA image built on 2009/12/ 8 at 8: 3:54
proxmark3>
I'm still not seeing it show up in my Device Manager ports.
Offline
Well, it appears that I just needed to browse through a few more postings and try a few more things. I have everything working and updated. On Win 7, I used the latest inf. I then performed the bottom, fpga, and os updates with the proxmark button pressed. The device now shows up each time under the Ports in the Device Manager. The command line operations are working just as expected.
Sorry for the spam postings!
Dan
Offline
Pages: 1