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.
Hey guys,
I'm at the brink of making the new CDC interface mandatory in the trunk. Maybe some of you are already using it, others may be a bit skeptical. But one thing is sure, it is much more reliable, faster, and supports frames with 512 bytes of data (content) in stead of the old 48 bytes. Secondly, it does not require a 50ms delay after sending something back to the host.
You can find more about the CDC in the following thread:
http://www.proxmark.org/forum/viewtopic.php?id=1467
The main question I have right now, is trying to gather some help from (experienced) users to guide others through the migration process. This could be done by answering questions, but maybe someone is willing to write a tutorial or make a movie about his migration process.
Thank you very much in advance for all the help!
Cheers,
Roel
Offline
I can make one if this sentence of mine is correct:
Can you use old flasher.exe to update the bootrom (while holding the button on pm3) then you can use the new flasher without holding tha button and specifying the com port... is that right ?
Offline
Here is the guide I wrote to update the old bootloader with the new-cdc one; there are also explanations on how to flash the new OS and FPGA files using the new bootloader !
I also provided some useful batch files+r664 compiled bootrom-fpga-os.
Hope to be helpful to someone !
Last edited by asper (2013-03-03 07:11:42)
Offline
Well, I didn't yet migrate to CDC, I'll be doing that and making a tutorial about it.
Two tutorials are already done here : http://www.youtube.com/user/C0Y0Ck3r
Offline
Guide updated to explain how to solve the unrecognized com port under Windows (thanks to Roel for the explanation).
Last edited by asper (2013-03-24 09:24:28)
Offline
I am running proxmark3 (svn:698) under Ubuntu 10.04
When i tried to flash bootrom.elf using the new flasher I get following error
Loading ELF file '../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
Attempted to write bootloader but bootloader writes are not enabled
Error while loading ../bootrom/obj/bootrom.elf
So I installed a new version of bootrom using old flasher. The hw version now is as below:
proxmark3> hw ver
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 698 2013-04-15 16:13:27
#db# os: svn 627 2012-11-30 14:45:58
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3>
When I plugin the device I don't see ACM port at all
[431493.690020] usb 4-2: new full speed USB device using uhci_hcd and address 119
[431498.878324] usb 4-2: configuration #1 chosen from 1 choice
[431498.887330] generic-usb 0003:9AC4:4B8F.004B: hiddev96,hidraw3: USB HID v1.00 Device [J. Westhues ProxMark-3 RFID Instrument] on usb-0000:00:1a.1-2/input0
I tried to install fpga and os images using old flasher, it takes long time to proceed. Only at this time I see ttyACM0 port.
[431500.820019] usb 4-2: new full speed USB device using uhci_hcd and address 120
[431500.998375] usb 4-2: configuration #1 chosen from 1 choice
[431501.001352] cdc_acm 4-2:1.0: This device cannot do calls on its own. It is not a modem.
[431501.001374] cdc_acm 4-2:1.0: ttyACM0: USB ACM device
However it ends with following error
Loading ELF file '../../proxmark3-read-only/armsrc/obj/fpgaimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0000a4bc->0x0000a4bc) [R ] @0xb4
Waiting for Proxmark to appear on USB....
Connected units:
1. SN: ChangeMe [004/119]
Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on USB............................................................................................................................................
Connected units:
1. SN: ChangeMe [004/121]
Found.
Note: Your bootloader does not understand the new START_FLASH command
It is recommended that you update your bootloader
Flashing...
Writing segments for file: ../../proxmark3-read-only/armsrc/obj/fpgaimage.elf
0x00102000..0x0010c4bb [0xa4bc / 165 blocks]ReceiveCommandPoll returned 0
Error: Unexpected reply 0x0000 (expected ACK)
ERROR
Error writing block 0 of 165
Now when I tried to use the new flasher I it ask for port which is nowhere to be found.
Usage: ./flasher <port> [-b] image.elf [image.elf...]
-b Enable flashing of bootloader area (DANGEROUS)
Example: ./flasher path/to/osimage.elf path/to/fpgaimage.elf
Can somebody help me
Offline
I solve the above issue with stupid hack.
I started flashing osimage using old flasher, the ttyACM0 port appears. While the flasher is waiting for the proxmark to appear in generic USB port, i.e. flasher is continuously printing dots (....), I pressed the button on the proxmark to stop flashing. Similarly I terminated the flasher. Now I still see ttyACM0 port so I used the new flasher to flash osimage and bootimage. All the best.
Offline