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.
Summary:
flasher.exe hangs in "Waiting for Proxmark to reappear.
Setup:
Driver: Proxmark-Driver-2012-01-15
-Installed both with button depressed,
-Installed with button released,
-Showing up under device manager as lib-usb devices
Client: ProxSpace-20100226-r390.rar
OS: win7-64 (VM) (USB devices set to automatically connect to this VM)
Description:
Can successfully to connect to the console using proxmark3.exe.
hw version yields the following:
$ client/proxmark3.exe
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 756 2013-07-13 08:11:47
#db# os: svn 651-suspect 2013-01-25 15:52:19
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3>
Running flasher.exe with old bootrom (r651) or new (r834) fails as follows:
$ ./client/flasher.exe -b bootrom/obj/br-new.elf
Waiting for Proxmark to appear on USB... Found.
Entering flash-mode...
(You don't have to do anything. Press and release the button only if you want to abort)
Waiting for Proxmark to reappear on USB...
The proxmark3 looks like it goes into flash mode after the "Found" message
Red+Orange LEDs are lit
This is the same behavior I see if I plug it in with the button depressed (red+orange LEDs lit), is this "flash mode?"
It never "redetects" the proxmark3 and fails to complete the upgrade procedure.
I have tried this upgrade with the button depressed as well with no success.
After reading the wiki and forums, the proposed workarounds or fixes I have found have not resolved the issue. I have seen some references to using an old flasher.exe with a new bootrom.elf, and have tried as far back as r651-flasher.exe with as new as r834-bootrom.elf with no luck. If you know a specific combo of flasher.exe and bootrom that might work in this case, let me know. To me, it looks like when the proxmark3 goes into "flash mode" it is not re-detected by flasher.exe.
If there is something else I'm missing, please let me know. I would love to find out that this is a noob mistake.
Thank you!
-MoF
Offline
Answering my own question here...but still not sure why the first step fixed anything... at any rate, it's solved and here's what worked for me:
###########Using Ubuntu Flasher to Change Bootrom#############
This part doesn't make sense to me, but I want to document it in case anyone else runs into it...
From ubuntu 10.04, ran r651 flasher to upgrade bootrom to r651 (Had to hold the button as I connected the proxmark3 for this to work
Although the Ubuntu flasher never worked for me, this allowed the r486 flasher to work from within windows as shown below
###########Upgrading bootrom############
pm3 /c/project/proxmark/proxmark-r486$ ./client/flasher.exe -b c:\\project\\proxmark\\proxmark-r834\\bootrom\\obj\\bootrom.elf
Loading ELF file 'c:\project\proxmark\proxmark-r834\bootrom\obj\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.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on USB.....
Connected units:
1. SN: ChangeMe [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
Found.
Flashing...
Writing segments for file: c:\project\proxmark\proxmark-r834\bootrom\obj\bootrom.elf
0x00100000..0x001001ff [0x200 / 2 blocks].. OK
0x00100200..0x00100d5f [0xb60 / 12 blocks]............ OK
Resetting hardware...
All done.
Have a nice day!
###########Checking bootrom (r486 proxmark.exe client)############
pm3 /c/project/proxmark/proxmark-r486$ ./client/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 839 2013-11-20 15:24:18
#db# os: svn 651-suspect 2013-01-25 15:52:19
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3> exit
###########Upgrading fpga image using flasher from r839############
pm3 /c/project/proxmark/proxmark-r834$ ./client/flasher.exe COM3 armsrc/obj/fpgaimage.elf
Loading ELF file 'armsrc/obj/fpgaimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0000a4bc->0x0000a4bc) [R ] @0xb4
Waiting for Proxmark to appear on COM3. Found.
Flashing...
Writing segments for file: armsrc/obj/fpgaimage.elf
0x00102000..0x0010c4bb [0xa4bc / 83 blocks]............................................................................
....... OK
Resetting hardware...
All done.
Have a nice day!
#At this point, I still had to use r486 version of proxmark.exe to connect to the device
pm3 /c/project/proxmark/proxmark-r834$ ./client/proxmark3.exe COM3
ERROR: invalid serial port
proxmark3> exit
pm3 /c/project/proxmark/proxmark-r834$ ../proxmark-r486/client/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 839 2013-11-20 15:24:18
#db# os: svn 651-suspect 2013-01-25 15:52:19
#db# FPGA image built on 2013/11/19 at 18:17:10
proxmark3> exit
###########Upgrading osimage using flasher.exe from r839############
pm3 /c/project/proxmark/proxmark-r834$ ./client/flasher.exe COM3 c:\\project\\proxmark\\proxmark-r834\\armsrc\\obj\\osimage.elf
Loading ELF file 'c:\project\proxmark\proxmark-r834\armsrc\obj\osimage.elf'...
Loading usable ELF segments:
1: V 0x00110000 P 0x00110000 (0x00013ce5->0x00013ce5) [R X] @0xb8
2: V 0x00200000 P 0x00123ce8 (0x00002b50->0x00002b50) [RWX] @0x13da0
Note: Extending previous segment from 0x13ce5 to 0x16838 bytes
Note: 0x3-byte hole created
Waiting for Proxmark to appear on COM3. Found.
Flashing...
Writing segments for file: c:\project\proxmark\proxmark-r834\armsrc\obj\osimage.elf
0x00110000..0x00126837 [0x16838 / 181 blocks]..........................................................................
........................................................................................................... OK
Resetting hardware...
All done.
Have a nice day!
###########Checking osimage using r839 proxmark.exe############
pm3 /c/project/proxmark/proxmark-r834$ ./client/proxmark3.exe COM3
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 839 2013-11-20 15:24:18
#db# os: svn 839 2013-11-20 15:24:22
#db# FPGA image built on 2013/11/19 at 18:17:10
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>
#########END############
Again, I'm not sure why I had to use the Ubuntu flasher initially, nor do I fully understand why in some instances I needed the r486 binary vs the r839 binary. It looks like it has something to do with the driver that Windows is using (lib-usb vs COM).
Hope this helps someone,
-MoF
Offline
My problem is the same and different! the thing is that first windows recognizes the pm3 but after running the command the msg "windows cannot recognize the device and then I see the "Waiting for Proxmark to appear Found USB" msg and it stuck!
Offline