[Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

zup · 2019-08-14 22:41:10

Hi there, again!

I asked a question at the introduction thread, and I have already read the info that you suggested. Forgot to mention that I am using Ubuntu.

"I just got my proxmark3 RDV4.01 (Iceman collection, with black antenna) at DefCon. I tried to use the standalone cloning functionality right away, (lights blinking correctly and stuff) but nothing happened when I tried to scan the card (Light D was still blinking). When I got home I tried to flash my device to the newest version from the RRG github repo. However, it is not recognising my device when specifying the correct path. (/dev/ttyACM0, or /dev/pm3-0). So I cant flash the device at all, or use the client to connect to it."

I have checked that the ttyACM0 device appears when I connect it with USB.

Output from dmesg:

[10647.792134] usb 1-2: new full-speed USB device number 24 using xhci_hcd
[10647.943200] usb 1-2: New USB device found, idVendor=9ac4, idProduct=4b8f, bcdDevice= 1.00
[10647.943205] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10647.943208] usb 1-2: Product: proxmark3
[10647.943211] usb 1-2: Manufacturer: proxmark.org
[10647.943213] usb 1-2: SerialNumber: iceman
[10647.945545] cdc_acm 1-2:1.0: ttyACM0: USB ACM device

Output from the flashing process:

$ client/flasher /dev/ttyACM0 -b bootrom/obj/bootrom.elf armsrc/obj/fullimage.elf
[+] Waiting for Proxmark3 to appear on /dev/ttyACM0           
............................................................          
[!] ERROR: invalid serial port /dev/ttyACM0 
          
[!!] Could not find Proxmark3 on /dev/ttyACM0 .

"It did not work properly out of the box, and I cant upgrade firmware / reflash it, so what should I do from here? I have read all of the documentation I could find."

Last edited by zup (2019-08-15 20:53:53)

iceman · 2019-08-14 23:45:37

First, did you follow instructions for linux ? Killing the modemmanager? If not, go to repo and read.

When all of that is nice and done, I suggest you
flash bootrom
reset device
flash fullimage

Sometime you might need "button trick" to get the device to flash.

zup · 2019-08-15 10:24:07

Yes, I already uninstalled modemmanager. Followed the instructions for linux. I can try to first flash the bootrom, reset and then flash fullimage. But I have a feeling that it wont recognise my device when I try it. I also tried the button trick by holding down the button while connecting it to the computer. Either my device was bricked when I got it, or there is something else. I do have a bus pirate I can use if we suspect there is something wrong with the device, but I want to make sure there is not something else thats wrong

Last edited by zup (2019-08-15 10:24:47)

iceman · 2019-08-15 10:27:14

if you have a buspirate, you can just jtag it. Plenty of instructions in the repo about it under /tools

zup · 2019-08-15 10:29:49

I can take a look at the access rights for /dev/ttyACM0 again. I added myself to the correct group, but ill check that I have permission to read/write to it when im home

zup · 2019-08-15 10:31:21

But thanks, ill check the instructions for jtagging it

zup · 2019-08-15 16:58:37

iceman wrote:

First, did you follow instructions for linux ? Killing the modemmanager? If not, go to repo and read.
When all of that is nice and done, I suggest you
flash bootrom
reset device
flash fullimage
Sometime you might need "button trick" to get the device to flash.

I found out that my user did not have the correct permissions for reading/writing to the /dev/ttyACM0 even though my user is in the dialout group and I have logged out/in

zup · 2019-08-15 18:41:54

Fixed it! There was a bug with my display manager. Even though I was in the dialout group and the dialout group already existed, I had to do newgrp dialout (https://unix.stackexchange.com/questions/458194/missing-groups-at-each-startup/458523#458523)

[usb] pm3 --> hw status
#db# Memory           
#db#   BIGBUF_SIZE.............40000          
#db#   Available memory........40000          
#db# Tracing           
#db#   tracing ................1          
#db#   traceLen ...............0          
#db# Currently loaded FPGA image           
#db#   mode.................... HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23          
#db# Flash memory           
#db#   Baudrate................24 MHz           
#db#   Init....................OK           
#db#   Memory size.............2 mbits / 256 kb           
#db#   Unique ID...............0xD567A882A7ADB425          
#db# Smart card module (ISO 7816)           
#db#   version.................v3.10           
#db# LF Sampling config           
#db#   [q] divisor.............95 ( 125 kHz )          
#db#   [b] bps.................8          
#db#   [d] decimation..........1          
#db#   [a] averaging...........Yes          
#db#   [t] trigger threshold...0          
#db# LF T55XX config           
#db#            [r]               [a]   [b]   [c]   [d]   [e]   [f]   [g]          
#db#            mode            |start|write|write|write| read|write|write          
#db#                            | gap | gap |  0  |  1  | gap |  2  |  3          
#db# ---------------------------+-----+-----+-----+-----+-----+-----+------          
#db# fixed bit length (default) |  29 |  17 |  15 |  47 |  15 | N/A | N/A |           
#db#     long leading reference |  31 |  20 |  18 |  50 |  15 | N/A | N/A |           
#db#               leading zero |  31 |  20 |  18 |  40 |  15 | N/A | N/A |           
#db#    1 of 4 coding reference |  29 |  17 |  15 |  31 |  15 |  47 |  63 |           
#db#           
#db# Transfer Speed           
#db#   Sending packets to client...          
#db#   Time elapsed............500ms          
#db#   Bytes transferred.......309760          
#db#   Transfer Speed PM3 -> Client = 619520 bytes/s          
#db# Various           
#db#   DBGLEVEL................1          
#db#   ToSendMax...............-1          
#db#   ToSendBit...............0          
#db#   ToSend BUFFERSIZE.......2308          
#db#   Slow clock..............31484 Hz          
#db# Installed StandAlone Mode           
#db#   LF HID26 standalone - aka SamyRun (Samy Kamkar)          
#db# Flash memory dictionary loaded           
      
[usb] pm3 --> hw version

 [ Proxmark3 RFID instrument ] 
          

 [ CLIENT ]          
  client: RRG/Iceman          
  compiled with GCC 8.3.0          

 [ PROXMARK RDV4 ]          
  external flash:                  present           
  smartcard reader:                present           

 [ PROXMARK RDV4 Extras ]          
  FPC USART for BT add-on support: absent           
          
 [ ARM ]
  bootrom: RRG/Iceman/master/db0ac163 2019-08-14 12:22:22
       os: RRG/Iceman/master/db0ac163 2019-08-14 12:22:32
  compiled with GCC 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]

 [ FPGA ]
  LF image built for 2s30vq100 on 2019/ 7/31 at 15:57:16
  HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23          

 [ Hardware ]           
  --= uC: AT91SAM7S512 Rev A          
  --= Embedded Processor: ARM7TDMI          
  --= Nonvolatile Program Memory Size: 512K bytes, Used: 270581 bytes (52%) Free: 253707 bytes (48%)          
  --= Second Nonvolatile Program Memory Size: None          
  --= Internal SRAM Size: 64K bytes          
  --= Architecture Identifier: AT91SAM7Sxx Series          
  --= Nonvolatile Program Memory Type: Embedded Flash Memory          

          
[usb] pm3 --> hw tune
          
[=] Measuring antenna characteristics, please wait...
          
[=] You can cancel this operation by pressing the pm3 button          
..
          
[+] LF antenna: 67,70 V - 125.00 kHz          
[+] LF antenna: 37,11 V - 134.00 kHz          
[+] LF optimal: 67,70 V - 125,00 kHz          
[+] LF antenna is OK  
          
[+] HF antenna: 47,73 V - 13.56 MHz          
[+] HF antenna is OK           
          
[+] Displaying LF tuning graph. Divisor 89 is 134kHz, 95 is 125kHz.

Last edited by zup (2019-08-15 18:42:50)

iceman · 2019-08-15 19:20:35

I suggest you edit your first post and add the suffix [solved] to your title.

Proxmark3 community

Announcement

#1 2019-08-14 22:41:10

[Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#2 2019-08-14 23:45:37

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#3 2019-08-15 10:24:07

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#4 2019-08-15 10:27:14

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#5 2019-08-15 10:29:49

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#6 2019-08-15 10:31:21

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#7 2019-08-15 16:58:37

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#8 2019-08-15 18:41:54

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

#9 2019-08-15 19:20:35

Re: [Solved] Just bought a Proxmark3 RDV4.01 - wont recognise device

Board footer