Proxmark3 not detected after flashing bootrom

jinbr · 2015-03-20 09:04:14

Hi,

I'm new to the forum and the proxmark device.
I work as a security engineer doing occasionally physical security assessments, hence my interest in RFID and the proxmark3.

I received mine yesterday. I plugged it on ubuntu and saw it being correctly detected as explained in the "getting started" of the wiki section on github. Same thing on macOS.

I flashed the bootrom and got an successful update message.
I tried to update the fpga code and kept having this message "waiting to detect USB connection" I unplugged and re-plugged the device a couple times holding the button on the board. At some point the card stopped being recognized. nothing in dmesg, nothing when plugged into my mac either (not that it is not recognized, it is just not detected at all).
Whenever I plug the USB I have the red and yellow led light up and every 10 sec or so, the green led will light up for half a sec.

I'm wondering if I bricked the device. Is this the kind of symptom I would observe or would I still see the usb connection detected ?
Anything you suggest to try ? If you think I bricked the device I'll go ahead and acquire a buspirate, I just want to make sure first this is not hardware related.

Thank you for your help.

jinbr · 2015-03-20 19:12:15

Quick update.
I tried to connect the Rpxmark through a USB2 hub. It did not change anything.

What I noticed is if I press the button before plugging it, the device will be detected and mounted for the 10/15 sec before the I hear a bip and the green light blink quickly. This disconnect the USB.

[== Undefined ==]
[ 7004.319850] usb 2-2.2: new full-speed USB device number 7 using uhci_hcd
[ 7004.475453] usb 2-2.2: New USB device found, idVendor=2d2d, idProduct=504d
[ 7004.475458] usb 2-2.2: New USB device strings: Mfr=1, Product=0, SerialNumber=0
[ 7004.475461] usb 2-2.2: Manufacturer: proxmark.org
[ 7004.651072] cdc_acm 2-2.2:1.0: This device cannot do calls on its own. It is not a modem.
[ 7004.651099] cdc_acm 2-2.2:1.0: ttyACM0: USB ACM device
[ 7022.007833] usb 2-2.2: USB disconnect, device number 7

The last message I get right after the board emits the bip with the quick green light blink.
After that if I release the button and repush it for a second or two, the usb will be mounted again.
This scenarios repeats.

Did anyone had that before ? How can I maintain connection with the board ?

Thank you

jinbr · 2015-03-20 20:04:35

Update2
I realized that I first flashed the bootrom with the older hid-flasher (pm3/client/hid-flasher/flasher).
I have no idea what the firmware version initially was, if the card came in with the HID-based or USB CDC, but I think the problem comes from here.

I compiled the "new" flasher (pm3/client/flasher) and tried to flash the ROM with it during the 10 secs the card stays mounted as /dev/ttyACM0.

Below are the two tries I've made one specifying the device, the other without:

[== Undefined ==]
/opt/proxmark3/proxmark3/client$ 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 (0x00000b60->0x00000b60) [RWX] @0x298
Attempted to write bootloader but bootloader writes are not enabled
Error while loading ../bootrom/obj/bootrom.elf

[== Undefined ==]
/opt/proxmark3/proxmark3/client$ sudo ./flasher /dev/ttyACM0 -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 (0x00000b60->0x00000b60) [RWX] @0x298

Waiting for Proxmark to appear on /dev/ttyACM0. Found.
Sending bytes to proxmark failed

I believe I'm getting closer to the source of the problem.Any idea why I can't write the bootloader ? Should I try an older version of the flasher ? (If yes any version in mind).

iceman · 2015-03-20 20:12:33

Sometime, you need to press button and keep it pressed until flash finishes

jinbr · 2015-03-20 20:17:02

Thanks iceman.
Yes that's what I do, I always keep the button pressed when doing all the operation mentioned above (if not the device does not mount, but even when doing that the device will unmount every 10/15sec no matter what)

iceman · 2015-03-20 20:20:27

old bootroom? try old flasher

Seems like you are running on a linux/mac environment.
Did you follow these directions https://code.google.com/p/proxmark3/wiki/Linux

Last edited by iceman (2015-03-20 20:22:34)

jinbr · 2015-03-20 20:49:43

Hey Iceman,
thanks again for the advice. I mostly looked at the Github's wiki, I thought the Google code doc was outdated.

Here's the the few manipulations that are mentioned on Google doc but not on GitHub (if I'm not mistaken) and that seemed to help:

No drivers are required to use the Proxmark within Linux. You will however need to do a couple of things as root:
Add yourself to the dialout group:
sudo adduser <username> dialout
(You will need to logoff before the changes will take effect.)
Configure modem-manager to ignore the proxmark (this is important as it will block flashing):
sudo vi /etc/udev/rules.d/77-mm-usb-device-blacklist.rules
Create this file if it doesn't already exist, and add the following:
# proxmark3 - http://www.proxmark.org/
ATTRS{idVendor}=="2d2d" ATTRS{idProduct}=="504d", ENV{ID_MM_DEVICE_IGNORE}="1"
restart udev hotplug control:
sudo udevadm control --reload-rules

After doing that, When pressing the button the board would be recognized on my Ubuntu VM (as it was before), the main difference is when kept pressed, I don't lose it every 10/15 sec anymore.
Better yet, the previous commands all worked: I could flash the bootrom, fpga and os.

Maybe the Github doc could be updated with that info.
Hope this post will help others in the future.

Thank you!

iceman · 2015-03-20 20:54:30

something about the blacklist.rules file...

Enjoy yr updated PM3

Earman · 2015-04-03 06:05:12

I tried to update the bootrom with the new release (2.0.0 from 0.0.7). The Win 32 FLASH - Bootrom process went fine on screen and it indicated success. 0x200 / 1 blocks OK and 0xb60 / 6 blocks OK, resetting hardware, all done, have a nice day... but the red light is stuck on the Proxmark! I tried re-flashing while holding the button down, it worked again but same result, the unit is stuck with the red light on.

I tried flashing a 3rd time with the button pressed but it did not appear on Com 5 anymore.

Am I stuck and need to get a JTAG (I don't have one yet) or can I try something else?

Thanks!

UPDATE: I was able to re-flash the previous bootrom 0.0.7 while pressing the button (it eventually appeared on COM 5 after several tries). No more red light. So its working again but does not accept the new bootrom. Any suggestions?

Last edited by Earman (2015-04-03 06:15:40)

asper · 2015-04-03 07:16:17

After flashing 2.0.0 bootrom you need to flash osimage 2.0.0 while holding the button; flashing bootrom only is not enough.

Last edited by asper (2015-04-03 07:16:43)

Earman · 2015-04-03 07:50:35

Thanks a lot Asper, worked like a charm!

I got confused when I saw the red light after flashing the bootrom as I thought it meant the bootrom was corrupted and I should not try to flash the OS in that condition! Now I know! Thanks a million!

Last edited by Earman (2015-04-03 08:46:25)

asper · 2015-04-03 12:34:00

I am happy it worked out !
Next time just have a better look at the instructions in the release thread:

Last edited by asper (2015-04-03 12:34:20)

Earman · 2015-04-03 18:36:46

I had read the instructions and knew I would have to press the button to flash the OS. What stopped me was the red light that I was not expecting. I thought there was something wrong with the first part of the process and did not dare going to step 2 thinking I has done something wrong in the first part and continuing to step 2 might make it worse... The instructions were perfectly clear, it was just me panicking with that red light (unexpected to me)! Now, I know it is normal to have the red light after step 1, as there is a temporary mismatch between the new Bootrom and the old OS and I should have just continued to the next step. Sorry for wasting your time, you are doing so much on this board, your help has been greatly appreciated!

Last edited by Earman (2015-04-03 20:33:43)

Earman · 2015-04-05 22:51:59

Since I upgraded to 2.0.0 my Proxmark3 does not work anymore. The upgrade process was fine, all the lights go through the normal test pattern when I connect. When I send the command hw detectreader l or h there is no response. There is no LED turned ON on the board (they only cycle properly when I connect to computer, as expected).

When I send "hw tune" it says "aborting no response from Proxmark". I switched to a new cable between Proxmark and antenna, no improvement. I also switched from LF antenna to HF antenna, to eliminate an antenna problem, same results. I cannot read any FOB anymore.

I downgraded to 0.0.7 as I thought it might be a problem with the uograde and I have the same problem, not working. I upgraded again, without any problem, to 2.0.0 and still same problem. Maybe there is a hardware problem in the USB connectors on the Proxmark board, but it is weird this started immediately after the upgrade while it was working fine just before...

Any troubleshooting suggestions? Thanks!

proxmark3> hw tune
Measuring antenna characteristics, please wait...........
No response from Proxmark. Aborting...
proxmark3>
proxmark3> hw tune
Measuring antenna characteristics, please wait...........
No response from Proxmark. Aborting...
proxmark3>
proxmark3> hw detectreader l
proxmark3>

Last edited by Earman (2015-04-05 22:59:33)

asper · 2015-04-05 23:35:34

If you downgrade to 0.0.7 you need to reflash also 0.0.7 bootrom; anyway the things you are reporting seem to be related to an hardware problem... my suggestion is to try to reboot your pc or use another pc/opertaing system to see if it works.

Last edited by asper (2015-04-05 23:45:05)

Earman · 2015-04-06 01:57:04

Thanks Asper. Yes, I had flashed the previous bootrom as well as OS, FPGA and Fullimage. I tried on a different computer and I was able to get the Version (which I was not previously able to get on the first computer) but the system still cannot read from the antenna. It is very possible that it is a hardware problem, but it was working fine before the upgrade and I did not drop it or put strain on the cables or anything, so that's a weird coincidence. I am wondering if I can have screwed-up something in the rom during flashing, even though it looked like it was going smoothly... Below is my latest try. Can you see any problem showing there? I don't understand what "-suspect" means for the Bootrom and OS... Thanks!

proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: /-suspect 2015-04-02 15:12:04
#db# os: /-suspect 2015-04-02 15:12:11
#db# HF FPGA image built on 2015/03/09 at 08:41:42
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
proxmark3>
proxmark3> hw detectreader l
proxmark3>
proxmark3> #db# LF 125/134kHz Baseline: 0mV
proxmark3> hw tune
Measuring antenna characteristics, please wait...........
No response from Proxmark. Aborting...
proxmark3>

*** UPDATE ***

I don't know what happened but the antenna suddenly started to work again (even on original computer) and I got (only HF antenna connected):

proxmark3> hw tune
Measuring antenna characteristics, please wait......
# LF antenna: 22.82 V @ 125.00 kHz
# LF antenna: 12.10 V @ 134.00 kHz
# LF optimal: 24.20 V @ 126.32 kHz
# HF antenna: 0.25 V @ 13.56 MHz
# Your HF antenna is unusable.
Done! Divisor 89 is 134khz, 95 is 125khz.
proxmark3>

I then was able to read a Paradox FOB without problem! To check for an intermittent, I tortured the cable, shook the connectors, tapped on the antenna... and it is still working right now. I am crossing my finger that it will continue, but I have no idea what was wrong! Maybe there was a magnetic field or something that overpowered it, can't figure it out!

PS: Is it normal to have "-suspect" for bootrom and os? (It still shows that, now that it works again)...

Thanks!!!

Last edited by Earman (2015-04-06 03:02:39)

Earman · 2015-04-06 03:04:34

On a different subject, Avast keeps removing Proxmark Tool as a potential threat! I did put it in the exception list but I am wondering if others have the same problem with their anti-virus showing a false positive? I reported it to Avast, hopefully they will white list it

Last edited by Earman (2015-04-06 03:05:30)

marshmellow · 2015-04-06 04:40:55

the -suspect is normal. the antenna connector on the pm3 is not the best. tends to have issues (in my experience)... i have not had any issues with the proxmark tool and anti-viruses yet...

iceman · 2015-04-06 08:21:46

There was an other thread on the forum, about which exact parts that triggered the false-positiv response from the antivirus software http://www.proxmark.org/forum/viewtopic.php?id=1562&p=6

It seems to be the "process.start" call that the antivirus software doesnt like.

asper · 2015-04-06 08:58:43

Maybe you have a loose contact/soldering somewhere (antenna connector?). Triplecheck with a tester.

Last edited by asper (2015-04-06 09:07:14)

Earman · 2015-04-06 10:10:39

Thanks!

Proxmark3 community

Announcement

#1 2015-03-20 09:04:14

Proxmark3 not detected after flashing bootrom

#2 2015-03-20 19:12:15

Re: Proxmark3 not detected after flashing bootrom

#3 2015-03-20 20:04:35

Re: Proxmark3 not detected after flashing bootrom

#4 2015-03-20 20:12:33

Re: Proxmark3 not detected after flashing bootrom

#5 2015-03-20 20:17:02

Re: Proxmark3 not detected after flashing bootrom

#6 2015-03-20 20:20:27

Re: Proxmark3 not detected after flashing bootrom

#7 2015-03-20 20:49:43

Re: Proxmark3 not detected after flashing bootrom

#8 2015-03-20 20:54:30

Re: Proxmark3 not detected after flashing bootrom

#9 2015-04-03 06:05:12

Re: Proxmark3 not detected after flashing bootrom

#10 2015-04-03 07:16:17

Re: Proxmark3 not detected after flashing bootrom

#11 2015-04-03 07:50:35

Re: Proxmark3 not detected after flashing bootrom

#12 2015-04-03 12:34:00

Re: Proxmark3 not detected after flashing bootrom

#13 2015-04-03 18:36:46

Re: Proxmark3 not detected after flashing bootrom

#14 2015-04-05 22:51:59

Re: Proxmark3 not detected after flashing bootrom

#15 2015-04-05 23:35:34

Re: Proxmark3 not detected after flashing bootrom

#16 2015-04-06 01:57:04

Re: Proxmark3 not detected after flashing bootrom

#17 2015-04-06 03:04:34

Re: Proxmark3 not detected after flashing bootrom

#18 2015-04-06 04:40:55

Re: Proxmark3 not detected after flashing bootrom

#19 2015-04-06 08:21:46

Re: Proxmark3 not detected after flashing bootrom

#20 2015-04-06 08:58:43

Re: Proxmark3 not detected after flashing bootrom

#21 2015-04-06 10:10:39

Re: Proxmark3 not detected after flashing bootrom

Board footer