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'm a total newbee, and have some problems with the new CDC.
I just bourght a PM3 from Proxmark3.com and have been following the getting started guide for win7. I have downloaded the ProxSpace and solved the compile error (-none) and have the Client.exe compiled OK. But when running it it requires an argument for the witch com port to use. I assume this is due to the new CDC where the PM3 will show upm as a Com port in Win7.
My PM3 is listen in Win device manager as "ProxMark-3 RFID Instrument" under "libusb-win32 devices" as I have installed the driver described in the Getting started guide whicj changed it from a HID device to PM3 device.
To make the PM3 ackt like a Com port I assume I need to flash a new bootloader, but how ?
In the Proxmarj Gui project for rev 709 ther is flsah scripts for this but it end up with "Waiting for Proxmark to appear on USB", and is stuck there. I have tried to un-and repluck the PM3 usb, and the device reappers in the device manager, but the flash script keep waiting.
Any Ideas, how to move on?
BR
Bjasen
Offline
Did you follow the script [FLASH - NEW Bootrom (uses old flasher exe).bat] on-screen instructions ?
Last edited by asper (2013-05-08 11:34:41)
Offline
To spare you some trouble, r709 (and also some previous, but I don't know exactly which) contains some bugs in the ARM-code. If you search the posts I've written you can read more about it.
Offline
To spare you some trouble, r709 (and also some previous, but I don't know exactly which) contains some bugs in the ARM-code. If you search the posts I've written you can read more about it.
You are right but at least the bootloader must be updated in order to use latest features
Anyway PM3 code (almost every release) contains some bugs that must be spotted and corrected !
Offline
Hi asper
Jes I followed the instruction, and get the follwing:
============================================
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 . . .
any idears?
/Bjasen
Offline
Please, try this batch file and tell me if it works.
Offline
That worked :-) Thanks
So now the bootrom is updated.
So far so good, but the device is still not recognised as a Com port.
Do I need an .inf file for win to recogise it as com port?
/bjasen
Offline
Hey Found solution in an other post, so now i have a COM5 port.
Thanks for your help, I realy appreciate it.
/Bjasen
Offline
Look at page 4 and 5 of the UpdateBootloader.pdf you can find in the package. The needed proxmark3.inf file is in the same folder.
EDIT: good to hear from you
EDIT2: if you find some errors in the GUI please post them here !
Last edited by asper (2013-05-08 13:18:51)
Offline
Hey Found solution in an other post, so now i have a COM5 port.
Thanks for your help, I realy appreciate it.
/Bjasen
Hi bjasen,
Do you recall what you did? I seem to be having difficulty getting my Proxmark to show up as a COM port (it only shows up in libusb-win32 devices). :-(
thanks,
-jadcock
Offline
I'm still having issues. I'm running from Parallels. I currently have r486 on my Proxmark. I'm attempting this from the r672 download. I tried the updated bat file posted by asper, and it did get further...
============================================
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]Error: Unexpected reply 0x00fe (expect
ed ACK)
ERROR
Error writing block 0 of 2
Press any key to continue . . .
Any suggestions on how to proceed so I can get the newer firmware installed?
Offline
I also tried going into my r486 download and simply reflashing the same bootrom - I got the same failure as show in my last post
Offline
I can rember when i was upgrading my proxmark getting it into some strange combo of bootloader and firmware it wasnt very happy with, and I also seem to recall having to add -b to the flasher command line to enable flashing the bootloader, the batch file asper posted in post #6 above has the -b added "flasher-OLD.exe -b ..\firmware_win\bootrom\bootrom.elf" also rember to hold the button pressed on the proxmark before you plug it in and I believe I held it for the entire time it took to flash the new bootloader.
Im sorry I cant be more specific as it was a while back that i did this and i didnt keep any notes.
If you succeed in getting the new bootloader installed then install the serial driver for it and continue to flash the firmware with the new flasher.
Offline
I'm now fully native on the Mac. OS X 10.8.2
I'm running the r486 flasher and attempting to flash the new bootloader. This should be the exact same procedure as done in the scripts for windows.
Unfortunately, I'm getting an error - does anyone have any idea what would be causing this?
>> ./flasher -b ../../proxmark3-752/bootrom/obj/bootrom.elf
Loading ELF file '../../proxmark3-752/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 [006/003]
Found.
Flashing...
Writing segments for file: ../../proxmark3-752/bootrom/obj/bootrom.elf
0x00100000..0x001001ff [0x200 / 2 blocks]Error: Unexpected reply 0x00fe (expected ACK)
ERROR
Error writing block 0 of 2
Offline
This is quite strange. I'm looking at the 486 codebase. The response of 0x00FE is NACK. I spent time in the bootloader code and added some printf statements in the flasher. The failure is in the first CMD_FINISH_WRITE. There are two cases where a NACK would be sent back, one is if the address is out of range. Using printf statement on the client, I verified that the values I'm sending are within the range being tested (at least according to the r486 code).
The other case is if the status register (sr) bits AT91C_MC_LOCKE or AT91C_MC_PROGE bits are set.
I'm guessing it's that one of these error bits is set. Any idea why they would be set or how to go about clearing them?
Offline
I just noticed that the AT91C chip on my Proxmark3 is a 256, NOT a 512. Is this OK? I'm still digging through the data sheet trying to find the right information and compare it to what's in the at91sam header file.
Offline
My guess, and this is purely an educated guess, is that the page(s) has (have) somehow become locked. It would be nice if there were a fallback attempt in the bootloader write that would attempt to unlock the pages if the lock error bit is set.
Offline
Please, try this batch file and tell me if it works.
I am in a similar situation (plus I am a total n00b)... what was this batch file about?
Offline
In my case, with the consistent failure and the NACKs returned, it turned out my board was damaged. I sent it back and they confirmed it was damaged. Once I got a new one, the upgrade worked fine.
There are a couple of other threads on here that I have contributed to about upgrading. They explain in detail the process. If you're using a Mac and still having problems, send me a direct message and I'll see if I can help.
Offline
Pages: 1