Proxmark3 community

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.

Announcement

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.

#1 2014-09-02 14:33:43

hheile
Contributor
Registered: 2014-03-03
Posts: 35

updating bootrom and firmware problems

hello,

today i checkt the procedure to upgrade the bootrom and osimage and so on on the proxmark.

backround:
proxmark3> hw version
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

#db# Prox/RFID mark3 RFID instrument                 
#db# bootrom: svn 848                 
#db# os: master/v1.0.0-2-g7eb0f3d-suspect 2014-04-03 13:05:19                 
#db# FPGA image built on 2014/03/24 at 21:54:44


what i did:
make in directory armsrc which gives me the os image and fpga image
make in bootrom which gives me the bootrom.elf

everything is clear until now.
then:
pressing the button until red and yellow lids.

sudo ./flasher -b ../bootrom/obj/bootrom.elf

and: boom:
sudo ./flasher -b ../bootrom/obj/bootrom.elf
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 (0x00000b38->0x00000b38) [RWX] @0x298
Attempted to write bootloader but bootloader writes are not enabled
Error while loading ../bootrom/obj/bootrom.elf

normaly the write mode is enabled with holding the button, am i right?
i remember that this procedure was changed later on.. so, how to flash when version is 848

thanks in advance

hheile

Offline

#2 2014-09-03 20:11:16

wax
Member
Registered: 2014-08-31
Posts: 3

Re: updating bootrom and firmware problems

with bootrom svn 848 you should have a serial port (usually /dev/ttyACM0), you can see with linux command dmesg

for flash you should use this command, change the serial device for you case.

sudo ./flasher /dev/ttyACM0 -b ../bootrom/obj/bootrom.elf 

Offline

#3 2014-10-28 09:54:02

YoungJules
Contributor
Registered: 2012-01-29
Posts: 60

Re: updating bootrom and firmware problems

I have pretty much the same problem, I'm guessing my bootrom is older than the one that gives the serial port... can we still upgrade the bootrom without the serial port?

I'm using Linux Ubuntu 14.04, have latest from github, my Proxmark comes up with:

sudo ./flasher -b ../bootrom/obj/bootrom.elf 
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 (0x00000b38->0x00000b38) [RWX] @0x298
Attempted to write bootloader but bootloader writes are not enabled
Error while loading ../bootrom/obj/bootrom.elf

FYI, dmesg reports the following:

[ 2348.929400] usb 1-1.2: New USB device found, idVendor=9ac4, idProduct=4b8f
[ 2348.929407] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2348.929412] usb 1-1.2: Product: ProxMark-3 RFID Instrument
[ 2348.929415] usb 1-1.2: Manufacturer: J. Westhues
[ 2348.929418] usb 1-1.2: SerialNumber: ChangeMe
[ 2348.931136] hid-generic 0003:9AC4:4B8F.0011: hiddev0,hidraw5: USB HID v1.00 Device [J. Westhues ProxMark-3 RFID Instrument] on usb-0000:00:1a.0-1.2/input0

So do I need "the old flasher" ?

Last edited by YoungJules (2014-10-28 10:06:27)

Offline

#4 2014-10-28 11:13:03

YoungJules
Contributor
Registered: 2012-01-29
Posts: 60

Re: updating bootrom and firmware problems

Well, in the end I got it working with a combination of the old flasher, the new bootrom, and trying with the button held all the time through the flashing procedure... it's not that clear in the instructions whether you should let go of the button once the red and yellow leds light up... I thought I'd bricked it as after installing the new bootrom, it started always with the red and yellow leds on and seemed to be continually rebooting every 20 seconds or so... but now I have:

[ 5503.132251] usb 1-1.2: new full-speed USB device number 74 using ehci-pci
[ 5508.225645] usb 1-1.2: New USB device found, idVendor=2d2d, idProduct=504d
[ 5508.225652] usb 1-1.2: New USB device strings: Mfr=1, Product=0, SerialNumber=0
[ 5508.225656] usb 1-1.2: Manufacturer: proxmark.org
[ 5508.226190] cdc_acm 1-1.2:1.0: This device cannot do calls on its own. It is not a modem.
[ 5508.226216] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device

And from the new proxmark3 program:

./proxmark3 /dev/ttyACM0
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument                 
#db# bootrom: master/v1.1.0-24-g92d255d-suspect 2014-10-28 00:10:12                 
#db# os: master/v1.1.0-24-g92d255d-suspect 2014-10-28 08:48:41                 
#db# HF FPGA image built on 2014/ 6/19 at 21:26: 2                 
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 

So I guess I'm good to go!  big_smile

Offline

Board footer

Powered by FluxBB