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.
Hello,
I bought Proxmark with original firmware from 3.1.2009 (bootrom.s19 and osimage.s19).
Few days ago I downloaded pm3-20090603-r29 and flashed bootrom.s19, osimage.s19 and fpgaimage.s19.
System stopped working - after booting - red led was shining, and I had to restore the original firmware from 3.1.2009.
I revealed that the problematic firmware is fpgaimage.s19, when I flashed only bootrom.s19 and osimage.s19 everything works without problem.
The same behaviour has the recent version pm3-20090713-r52, when I flash bootrom.s19 and osimage.s19, everything works, but when I try to flash fpgaimage.s19 (using prox fpga fpgaimage.s19) system stops working and I need to restore firmware from 3.1.2009.
So at this time, I use fpga firmware (probably from 3.1.2009 firmware) and bootrom and osimage from pm3-20090713-r52, and it seems working.
Where is a problem?
Thanks for explanation,
Pavol
Offline
You need to flash bootrom-merged.s19 not bootrom.s19
Offline
Thanks, now it works.
Offline
I'll stop including the other bootroms in the binary packages.
Offline
I was just doing some code development this evening and came across a similar issue where flashing updated code to the PM3 seemed to break it. It wouldn't boot or be recognized by the PC. Reflashing earlier code would fix it. Initially I suspected my code changes were breaking it but this wasn't the case here as adding some dummy code (like duplicate an existing function) would make the problem go away.
I haven't gotten to the bottom of it yet but I have a hunch that there is a bug in the bootloader FLASH code where it fails to write the last page of the s19 file if it doesn't end on a 256 byte boundary. Just be warned for now. I'll look into this when I have some spare time unless someone wants to beat me to it and analyse the boot flash code.
Offline
d18, when you said you were able to reflash earlier code, I assume you didn't flash over the bootrom so that you didn't need a JTAG?
I'm on a 128k chip and definitely went over 128k when writing.
Offline
Nah my bootrom was untouched at all times. I've never seen the issue where the flash goes bezerk and rewrites everything
Offline