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
Hi,
I just got a Proxmark3 board, and I have been struggling to get it working on Windows 7 (64-bit). I have installed the drivers & the board does appear in the device manager as "ProxMark-3 RFID Instrument" under "libusb-win32 devices. I grabbed ProxSpace and built client/proxmark3.exe. However, when I try to run that executable, I get "ERROR: invalid serial port". In some of the documentation I have seen (Proxmark_III-Windows7_GSG_v1.pdf), it sounds like I should see a list of connected Proxmark boards. There is nothing showing on my COM ports according to the device manager, and supplying an arbitrary port doesn't seem to work. Is my board wonky, or am I missing something? Please help...
many thanks,
-Jamison
Offline
Update: After hunting around, I found http://proxmark3.com/dl/pm3-bin-r486.zip which contains proxmark.exe... which kind of works with my board. I ran it to get the version info:
$ 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 486-unclean 2011-08-28 18:52:03
#db# os: svn 651-suspect 2013-01-25 15:52:19
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
I'm not sure why the version of proxmark.exe I built isn't working, but I would love to have the latest & greatest stable versions. Any help would be greatly appreciated!
thanks,
-Jamison
Offline
If you look at a different thread on this forum, http://www.proxmark.org/forum/viewtopic.php?id=1562 you find a Windows client from Asper. Which is kind of simple to upgrade to the new internal usb communications with. However, remember to use the old flashe för the bootrom update, after that, you can use the new flasher..
Offline
Hi,
Thanks for your reply. I'm very much a n00b to the Proxmark3, and I have to admit that the profusion of versions of the software & documentation is rather confusing. My main goal is to get the board up & running so I can snoop NFC exchanges... is my firmware (i.e., bootloader, OS, and FPGA image versions) sufficient for that, or do I need to reflash anything?
thanks,
-Jamison
Offline
hrm... well..
You will need to upgrade to a new bootrom. Go with the client from thread I mentioned earlier. You only need to edit the "FLASH nnnnn.bat" files to your com-port. Then they work great.
After that, you use the proxmark.exe client inside aswell. After that you are good to go.
Offline
Is there somewhere else where I can download the software from? I'm trying to download this from work, and the IDS here is complaining about sendspace.com. I also tried grabbing the file from my phone, but the site wants me to install some sort of downloader (ilivid.exe?). I'm not wild about installing software that I know nothing about...
Offline
Please ignore my previous post... I got the pm3-bin-715.rar file, and will try it out shortly.
Offline
it is pretty straight forward when u use that package.
first u flash the new bootrom with the old flasher.
then u use the "FLASH nnnn.bat" files.. (u need to edit them thou.)
Offline
No luck. Here's what I'm doing:
1. I run the "FLASH - Bootrom.bat" file with the Proxmark disconnected from USB. I get the big WARNING screen.
2. I then hit a key & see the following:
====================================
FLASHING 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...........................................
3. And then when I plug the Proxmark into my USB port, I hear the Windows new hardware connected sound, and then... nothing. I never see the instructions screen described in the UpdateBootloader.pdf file. I just keep getting more ....... printed to the screen.
Have I missed something, or is my board malfunctioning?
Offline
OK, I got it... I was using the wrong bootrom flasher. :-( My apologies!
Offline
No worries,
It took me sometime also the first time before I got the hang of it.
I missed the -b in the command the first times.. took abit of googling to find out
Offline
I think I'm making progress, though I am still having trouble getting my Proxmark board to be seen as a COM port. I found this (http://www.proxmark.org/forum/viewtopic.php?id=1614) but when I try the new .inf file, the Proxmark shows up as COM21 in the device manager until I release the button, at which point it just shows up as a "ProxMark-3 RFID Instrument" under "libusb-win32 devices".
I have a version of proxmark3.exe that doesn't require a COM port, and when I do "hw version" this is what I see:
C:\Proxmark3\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 715 2013-05-10 07:59:22
#db# os: svn 651-suspect 2013-01-25 15:52:19
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3>
So it looks like the bootrom did in fact get updated, but something is still not quite right. :-( Is there anything peculiar to Windows 7 that could be causing me problems?
Offline
You got the bootrom ok,
Now you need to get the ini right. The old libusb-win32 device, you can "remove" from the system. Next time the pm3 show up in the devicemanager, the u change the driver to the one from Asper's package.
When thats in place, you will find the pm3 under "Ports (com & LP) in the Devicemananger.
The assigned COM -port, is what you need to edit the FLASH - nnnn.bat files with. After that, you run the bat-files and Bob's yr uncle
Offline
W00t! It works! :-)
So after mucking around with the drivers for a whle, the Proxmark would still only show up as a COM port when the button was pressed. Otherwise, it only appeared as a libusb-win32 device.
I decided that I would go ahead & try to flash the bootloader, FPGA, and OS to revision 715 using that com port (COM2, in my case). I succeeded in flashing all three, so now I'm up to the following revisions:
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 715 2013-05-10 07:59:22
#db# os: svn 715 2013-05-10 07:59:26
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3>
And... my Proxmark is now visible as COM2 all the time, even without the button being pressed! :-)
So I'm not sure exactly why the device was not showing up as a COM port before, but it is now.
Offline
Oh, and many thanks, iceman. ;-)
Offline
U're welcome.
Have fun!
Offline
I have this exact same problem on Windows XP. I can't seem to have any luck. I tried to remove the libusb driver from Device Manager and then it comes in as an HID USB device. I can get the PM3 to show up as a COM9 only when I hold down the button to connect it.
I successfully updated the bootrom using the old flash method, but now I am stuck at this step. I also tried the idea of holding down the button while trying to flash new bootloader, FPGA and OS, but none of them worked. I got the same error/issue as above when I try to rerun the old bootloader Flash method. I can't communicate with the PM3 through any COM port.
Any ideas? Thanks in advance!
Offline
I just tried updating my bootloader to the latest version. Now my pm3 is not detected by my windows 7-64bit. I'm still trying to figure a way out of this... any input is appreciated!
Offline
try holding on, and keep the button pressed down during the bootrom, fgpa, os flash...
Offline
Hi, I have the same problem above,, I keep holding down the button for more than 20 mins , but no results showed , how long do i need to hold down the button ?? and now i can not run the proxmark3.exe . do i have to re-install the pm3 all over again ?? pls help. thanks.
Offline
Well, try button trick is to have the PM3 unplugged, press the button (and keep it pressed) then with the other hand reconnect the usb cable to the PM3. Then start the flash commands (keeping it pressed).. after that you can hold down until the flashing is finished. Takes 1min maximum.
Offline
Pages: 1