[rdv4] Proxmark3 RDV4 frequent disconnection

ghecko · 2018-08-28 20:32:05

Hello,

I have many "disconnection" from the proxmark with many command (read, write, brutforce attack, ...) any time. Any recommandation ? I have tried iceman github repos and the specific repo for the rdv40 version

Here an example with mfkeys.lua scripts :

Testing block 20, keytype 0, with 85 keys
Testing block 20, keytype 0, with 85 keys
Testing block 20, keytype 0, with 71 keys
Testing block 20, keytype 1, with 85 keys
Testing block 20, keytype 1, with 85 keys
Testing block 20, keytype 1, with 85 keys
Testing block 20, keytype 1, with 85 keys
#db# ChkKeys: Can't select card (UID)
#db# ChkKeys: Can't select card (UID)
#db# ChkKeys: Can't select card (UID)
#db# ChkKeys: Can't select card (UID)
...
Timeout while waiting for response. Increase TIMEOUT in mfkeys.lua to wait longer
Testing block 24, keytype 0, with 85 keys
#db# ChkKeys: Can't select card (UID)
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
Timeout while waiting for response. Increase TIMEOUT in mfkeys.lua to wait longer
Testing block 24, keytype 0, with 85 keys
Sending bytes to proxmark failed - offline
Waiting for a response from the proxmark...
You can cancel this operation by pressing the pm3 button
Timeout while waiting for response. Increase TIMEOUT in mfkeys.lua to wait longer
Testing block 24, keytype 0, with 85 keys
Sending bytes to proxmark failed - offline
Waiting for a response from the proxmark...
You can cancel this operation by pressing the pm3 button
Timeout while waiting for response. Increase TIMEOUT in mfkeys.lua to wait longer

For information :

OS : archlinux Linux ghecko 4.18.1-arch1-1-ARCH #1 SMP PREEMPT Wed Aug 15 21:11:55 UTC 2018 x86_64 GNU/Linux

hw version :
Proxmark3 RFID instrument
[ CLIENT ]
client: iceman build for RDV40 with flashmem; smartcard;

[ ARM ]
bootrom: iceman/master/ 2018-08-23 14:42:53
os: iceman/master/ 2018-08-23 14:42:54

[ FPGA ]
LF image built for 2s30vq100 on 2017/10/25 at 19:50:50
HF image built for 2s30vq100 on 2018/ 8/10 at 11:48:34

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

hw status :
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/ 8/10 at 11:48:34
#db# Flash memory
#db# init....................OK
#db# Memory size.............2 mbits / 256kb
#db# Unique ID...............0xd567a882a7af7126
#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# USB Speed
#db# Sending USB packets to client...
#db# Time elapsed............1500ms
#db# Bytes transferred.......859136
#db# USB Transfer Speed PM3 -> Client = 572757 Bytes/s
#db# Various
#db# MF_DBGLEVEL.............1
#db# ToSendMax...............-1
#db# ToSendBit...............0
#db# ToSend BUFFERSIZE.......2308
#db# Installed StandAlone Mods
#db# LF HID26 standalone - aka SamyRun (Samy Kamkar)

hw tune :
[=] measuring antenna characteristics, please wait...

....

[+] LF antenna: 70.25 V - 125.00 kHz
[+] LF antenna: 38.81 V - 134.00 kHz
[+] LF optimal: 70.25 V - 125.00 kHz
[+] LF antenna is OK

[+] HF antenna: 33.92 V - 13.56 MHz
[+] HF antenna is OK

[+] Displaying LF tuning graph. Divisor 89 is 134khz, 95 is 125khz.

I have also tried with an other usb cable, it's the same...

Another output error message :

pm3 --> hf search
UART:: os troubles (-1)
sending bytes to proxmark failed
UART:: os troubles (-1)
sending bytes to proxmark failed
UART:: os troubles (-1)
sending bytes to proxmark failed
Sending bytes to proxmark failed - offline

I've tried it on a windows machine, same problem

iceman · 2018-08-28 20:35:40

Distance/positioning between tag and antenna when it comes to 14a commands. 1-2cm recommended.

Once it fails, the device is mess up, then your client messes up with sending to device which doesn't respond anymore (os trouble)

You will need to exit client and restart it, and unplug/plug device, when you see os trouble messages.

0xFFFF · 2018-08-29 00:53:24

Do you have an old computer? / Are you connecting the PM to a powered USB HUB?
Just wondering if this is the same as an issue I saw once when I was trying run a PM on an old laptop. It couldn't deliver the required power.

ghecko · 2018-08-29 11:39:27

Hi,

Thank you for your respons.
I use a recent laptop, thank you for this advice.
@iceman, When you recommend having a distance of 1-2cm minimum ? I do not have to stick the card on the proxmark ?

I tried it and I come back to you.

iceman · 2019-01-22 09:27:13

Since you are on a Archlinux distro, you may need to uninstall / kill you modem manager. Users of Kali / Archlinux seem to have this problem.

The readme.md / wiki has been updated with this suggestion.

KALI and ARCHLINUX users
Kali and ArchLinux users usually must kill their modem manager in order for the proxmark3 to enumerate properly.
sudo apt remove modemmanager

Proxmark3 community

Announcement

#1 2018-08-28 20:32:05

[rdv4] Proxmark3 RDV4 frequent disconnection

#2 2018-08-28 20:35:40

Re: [rdv4] Proxmark3 RDV4 frequent disconnection

#3 2018-08-29 00:53:24

Re: [rdv4] Proxmark3 RDV4 frequent disconnection

#4 2018-08-29 11:39:27

Re: [rdv4] Proxmark3 RDV4 frequent disconnection

#5 2019-01-22 09:27:13

Re: [rdv4] Proxmark3 RDV4 frequent disconnection

Board footer