[SOLVED] [RDV4] Issues - Power Lights, no HF/LF tune, unstable?

Mrmysteryguest · 2019-01-02 01:51:46

tl;dr version - It was faulty. RMA fixed it.

---

Hey guys

Running Unbuntu 18.04 through VMWare Workstation Pro.

Someone purchased me an RDV4 from Defcon as a christmas present. They bought three, the other two are working fine with no issues. I only just opened this one last week and it is so unstable. Hoping someone can help as I don't have any off these issues with the PM3V2.

One LF tune, intermittent HF tune - I can run 'hw tune' and get the HF working consistently it seems. The LF has only worked once (about 5 minutes ago after 5 days of trying!!). Now it's back to being unusable, yet I somehow was able to scan an LF tag I had laying around. Logs below of the differences, and some other errors I've been getting. I couldn't even do an lf scan after the antenna was useable.
Power lights - Only 3 out of 4 are active (https://ibb.co/Z8MSMGw). Most other pictures I see only show all lights active.
I've tried reading the stock HF/LF cards that come with the RDV4, no luck. I had success with one tag I had laying around. Log below.
I've tried normal iceman repo; RRG repo (the one iceman udpated 8 hours ago), and the official PM3 repo. Tuning issues exist across all of them.
When trying to change firmware from official back to RFIDResearchGroup, I'm having to use the buspirate to flash the firmware and recover. That said I've gotten it down to a 7 minute process. When I do this, I re-download the RRG repo, rebuild, and flash using that firmware
The stock white USB cable that came with the RDV4 doesn't work anymore, so threw it in the bin and swapped to different cables too.
I've unscrewed the HF antenna off the proxmark, and the LF antenna off the HF and checked connectivity. Redone the screws back up too.

Now I was getting the following error yesterday when running 'hw status'. It repeated the "WARNING: blah blah" 14 times at one point, 7 another, 22 another. Now this morning when LF worked, I didn't get this error at all.

#db# USB Speed          
#db#   Sending USB packets to client...          
Status command failed. USB Speed Test timed out          
[-] WARNING: Command buffer about to overwrite command! This needs to be fixed!

Any ideas? I'm confused by the intermittent and really unstable behaviour of it....

EDIT: HF Search - Fixed the bad drawable error by adding "QT_X11_NO_MITSHM=1" to /etc/environment

pm3 --> hf search
[!] timeout while waiting for reply.          
UART:: write time-out
[!] sending bytes to proxmark failed          
UART:: write time-out
[!] sending bytes to proxmark failed          
Waiting for a response from the proxmark...          
You can cancel this operation by pressing the pm3 button          
          
[-] no known/supported 13.56 MHz tags found
          
pm3 --> X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000015

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................24MHz          
#db#   Init....................OK          
#db#   Memory size.............2 mbits / 256kb          
#db#   Unique ID...............0xd567a882a7348725          
#db# Smart card module (ISO 7816)          
#db#   version.................v2.06          
#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#   [a] startgap............29*8 (232)          
#db#   [b] writegap............17*8 (136)          
#db#   [c] write_0.............15*8 (120)          
#db#   [d] write_1.............47*8 (376)          
#db#   [e] readgap.............15*8 (120)          
#db# USB Speed          
#db#   Sending USB packets to client...          
#db#   Time elapsed............1500ms          
#db#   Bytes transferred.......795648          
#db#   USB Transfer Speed PM3 -> Client = 530432 Bytes/s          
#db# Various          
#db#   MF_DBGLEVEL.............1          
#db#   ToSendMax...............-1          
#db#   ToSendBit...............0          
#db#   ToSend BUFFERSIZE.......2308          
#db# Installed StandAlone Mode          
#db#    LF HID26 standalone - aka SamyRun (Samy Kamkar)

HW Version

 [ CLIENT ]          
 client: iceman build for RDV40 with flashmem; smartcard;  
          
 [ ARM ]
 bootrom: iceman/master/0fb0c353 2019-01-01 18:56:07
      os: iceman/master/0fb0c353 2019-01-01 18:56:11

 [ FPGA ]
 LF image built for 2s30vq100 on 2018/ 9/ 8 at 13:57:51
 HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23          

 [ Hardware ]           
  --= uC: AT91SAM7S512 Rev B          
  --= Embedded Processor: ARM7TDMI          
  --= Nonvolatile Program Memory Size: 512K bytes, Used: 240678 bytes (46%) Free: 283610 bytes (54%)          
  --= Second Nonvolatile Program Memory Size: None          
  --= Internal SRAM Size: 64K bytes          
  --= Architecture Identifier: AT91SAM7Sxx Series          
  --= Nonvolatile Program Memory Type: Embedded Flash Memory

HW Tune when LF worked once

[+] LF antenna: 12.04 V - 125.00 kHz          
[+] LF antenna: 12.04 V - 134.00 kHz          
[+] LF optimal: 15.58 V -  46.88 kHz          
[+] LF antenna is OK  
          
[+] HF antenna: 45.18 V - 13.56 MHz          
[+] HF antenna is OK           
          
[+] Displaying LF tuning graph. Divisor 89 is 134khz, 95 is 125khz.
          
pm3 --> X Error: BadAccess (attempt to access private resource denied) 10
  Extension:    131 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x255
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:    131 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0x2000010
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000011
X Error: BadAccess (attempt to access private resource denied) 10
  Extension:    131 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x255
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:    131 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0x2000012
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode: 54 (X_FreePixmap)
  Resource id:  0x2000011
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:    131 (MIT-SHM)
  Minor opcode: 2 (X_ShmDetach)
  Resource id:  0x2000010
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000013
X Error: BadAccess (attempt to access private resource denied) 10
  Extension:    131 (MIT-SHM)
  Minor opcode: 1 (X_ShmAttach)
  Resource id:  0x131
X Error: BadShmSeg (invalid shared segment parameter) 128
  Extension:    131 (MIT-SHM)
  Minor opcode: 5 (X_ShmCreatePixmap)
  Resource id:  0x2000014
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000015
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000015
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000015
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000013
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x2000015

DMESG dump of the device

[  916.483316] usb 2-2.1: USB disconnect, device number 6
[  921.839695] usb 2-2.1: new full-speed USB device number 7 using uhci_hcd
[  922.164126] usb 2-2.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[  922.164129] usb 2-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  922.164130] usb 2-2.1: Product: proxmark3
[  922.164131] usb 2-2.1: Manufacturer: proxmark.org
[  922.164132] usb 2-2.1: SerialNumber: iceman
[  922.168107] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device

When LF tag actually scanned

Checking for known tags:
          
[=] Signal looks just like noise. Looking for Hitag signal now.          
Valid Hitag2 tag found - UID: 01080100          
          
[+] Valid Hitag Found!

Last edited by Mrmysteryguest (2019-01-19 08:41:18)

iceman · 2019-01-02 08:15:16

Sorry to say, that device looks faulty. RMA where they bought it and get a replacement unit.

Never seen these kinds of errors before Error: BadDrawable (invalid Pixmap or Window parameter)

Mrmysteryguest · 2019-01-02 10:09:22

Thanks for the reply iceman. It was bought from HackerWareHouse at DC26. Garrett replied and has offered an RMA for me.

I'll update the thread once I get a new one and see how it goes.

Mrmysteryguest · 2019-01-19 08:39:52

New one arrived, works fine with no issues!

Definitely a DOA unit. Threat titled updated too.

Thanks for taking a look at it Iceman. And props to Hacker Warehouse for swapping it out so quick!

Last edited by Mrmysteryguest (2019-01-19 08:44:43)

Proxmark3 community

Announcement

#1 2019-01-02 01:51:46

[SOLVED] [RDV4] Issues - Power Lights, no HF/LF tune, unstable?

#2 2019-01-02 08:15:16

Re: [SOLVED] [RDV4] Issues - Power Lights, no HF/LF tune, unstable?

#3 2019-01-02 10:09:22

Re: [SOLVED] [RDV4] Issues - Power Lights, no HF/LF tune, unstable?

#4 2019-01-19 08:39:52

Re: [SOLVED] [RDV4] Issues - Power Lights, no HF/LF tune, unstable?

Board footer