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.
Hi, I've tried to flash by pm3 bootloader, fpga and os and along the process something went wrong I think. I guess the issue is related to wrong drivers or bootloader. I'm running Win7.
Below you see that I'm able to communicate with my pm3 using the "old" HID (libusb-win32 device). Note the bootrom says "svn 0" is that good or bad?:
C:\NFC\proxmark3\pm3-bin-r486\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 0 2013-08-17 21:51:48
#db# os: svn 651-suspect 2013-01-25 15:52:19
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3>Now, when I reconnect my pm3 while keeping the button on the pm3 down, it shows up as a COM devices. When I release the button it fall back to HID again.
I believe that this behaviour is giving me flashing issues, because when I execute flasher.exe -b bootrom.elf the device is first found on the USB, then it reconnect and return on the COM port instead of USB as it should:
Loading ELF file 'C:\NFC\proxmark3\pm3-bin-r486\pm3-bin-r486\Firmware\fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0000a4bc->0x0000a4bc) [R ] @0xb4
1: V 0x00110000 P 0x00110000 (0x000104fe->0x000104fe) [R X] @0xa570
2: V 0x00200000 P 0x001204fe (0x00001c54->0x00001c54) [RWX] @0x1aa70
Note: Extending previous segment from 0x104fe to 0x12152 bytes
Waiting for Proxmark to appear on USB...
Connected units:
1. SN: ChangeMe [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on USB.......................................................................................................................................Any advice how to proceed from here would be very appreciated!
Offline
I don't have much experience with windows-usage, but been through the same issues on linux. What happens is that your OS seems to be stuck in the old 'hid' device swamp, whereas your bootrom is cdc. So, whenever you try the normal flashing procedure, it *will* fail. In order to make it whole again, you need to either update the os or downgrade the bootrom. I would opt to update everything.
1. Since your bootrom is in new cdc, you need to use the new flasher.
2. You need to keep the button pressed before inserting into the host. This will trigger the bootrom to connect (using the new protocol)
3. Using the new flasher, flash with -b flag, but point to new fullimage (with new cdc capabilities). Alternatively, you don't have to update the bootrom, but something is a bit weird with the 'svn 0', so I'd recommend a new full build.
Also, I'm not sure why you're on r651, the svn version is up at 754 or something like that. I think r651 is the one that ships with pre-assembled pm3 no ? I wouldn't use that, but go with the latest and greatest instead. I can only speak for myself, but if someone reports a problem with code that's 100+ revisions after head, I often don't feel inclined to spend time fixing it, since more often than not, it's already fixed.
Good luck, and godspeed!
Offline
thanks a lot, I managed to upgrade OS first, and then the boot loader to latest and greatest r756
Offline
This appears to be on topic, and related.
I would appreciate any help.
I have a newly purchased Proxmark3, and I'm trying to connect
to either Windows, or Ubuntu. Not having great luck so far.
It seems I have best luck with Ubuntu, as it at least can
connect, using the older proxmark app version.
================================================================
It appears I am connecting only via HID, not ACM0 unless I
connect with the PM3 button continually pressed.
================================================================
root@Notebook-PC:/home/user/proxmark3-old-3/client# ./proxmark3
Connected units:
1. SN: ChangeMe [008/015]
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 755 2013-07-13 08:14:12
#db# os: svn 651 2013-01-31 14:52:31
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3>
================================================================
Using the older flasher, I attempted to update to the newer
Proxmark 2.0.0, but could not complete the flash, as follows:
0) disable modem manager (common problem under Ubuntu)
1) cd to ../proxmark3-old-3/client
2) copy bootrom.elf from Proxmark 2.0.0 to same directory
3) Press and continually hold PM3 button, and plug in to USB
4) As root, enter: # ./flasher -b bootrom.elf
5) See the message, "waiting for proxmark to appear on usb...."
That message continues............................. forever.
I've read in forums where others have seen this problem under
Windows. Generally, it seems to be related to libusb drivers.
I avoided that (I hoped) by going with Ubuntu (14.04 LTS / 64).
Using the older Proxmark app, I'm able to connect to the PM3
via HID, which is how I got the above version info.
I am very willing to change O/s, interface, etc., or do what
it takes to get this device updated. If JTAG is required, I
have a Wiggler (LPT-JTAG) and parallel port available.
Offline
OMG! Fixed!
I was re-re-reading Hollman's post above, when I realized that despite my device not being detected under Ubuntu as /tty/ACM0, it is using a newer Bootloader (svn 755, per above info), and cannot be flashed with the older HID client's flasher as I was attempting to do.
So I used the new flasher that comes with Proxmark3 v2.0.0, held the PM3's button constantly, and successfully flashed the 'fullimage.elm'.
I then checked in the terminal with the 'dmesg' command, and saw the PM3 is now seen as an ACM0, but there was a problem!
The PM3 kept auto-resetting every 10 seconds or so (I could hear the relay clicking).
So I went back and used the new flasher app to reflash the bootrom.elf.
That fixed it!
======================================================
root@Notebook-PC:/home/user/proxmark3-master-2-0-0/client# ./proxmark3 /dev/ttyACM0
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: /-suspect 2015-04-27 02:45:46
#db# os: /-suspect 2015-04-27 02:45:48
#db# HF FPGA image built on 2015/03/09 at 08:41:42
uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3>
======================================================
I just wanted to provide my steps, in case anyone else is in a similar situation.
Offline
Thanks for following up and saving me the trouble of repeating my post above! Just curious, you had the same firmware mismatch as above, where does that come from? Is that how they're shipped from rhyscorp nowadays?
Offline
New, as shipped direct from XFPGA, pretty confusing.
Still, I don't suppose it's any better / worse than had the bootrom been an earlier version.
I just had to do fullimage, and THEN go back and re-update the bootrom (though it was already at 755) to make it happy, both with the new version flasher app and button pressed throughout.
It was good to capture the version info prior to flashing, if anything, just to let others know this is a possible 'new product' starting place.
Offline