dose@dose:~$ uname -a
Linux dose 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
What I just saw when executing:
dmesg
[ 8654.486290] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[ 8876.036360] cdc_acm 2-1.1:1.0: failed to set dtr/rts
[ 8876.103764] usb 2-1.1: USB disconnect, device number 9
[ 8876.376595] usb 2-1.1: new full-speed USB device number 10 using ehci-pci
[ 8881.619386] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[ 8881.619393] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8881.619406] usb 2-1.1: Product: proxmark3
[ 8881.619409] usb 2-1.1: Manufacturer: proxmark.org
[ 8881.619410] usb 2-1.1: SerialNumber: iceman
[ 8881.619968] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
[ 8894.791157] usb 2-1.1: USB disconnect, device number 10
[ 8896.804862] usb 2-1.1: new full-speed USB device number 11 using ehci-pci
[ 8896.916904] usb 2-1.1: New USB device found, idVendor=9ac4, idProduct=4b8f
[ 8896.916912] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8896.916915] usb 2-1.1: Product: proxmark3
[ 8896.916918] usb 2-1.1: Manufacturer: proxmark.org
[ 8896.916921] usb 2-1.1: SerialNumber: iceman
[ 8896.917676] cdc_acm 2-1.1:1.0: ttyACM0: USB ACM device
cdc_acm 2-1.1:1.0: failed to set dtr/rts - Seems to make some trouble every now and then.
What I also just noticed is that when unplugging the USB cable from my computer and plugging it back again it says:
[!] ⚠️ Communicating with Proxmark3 device failed
[=] Running in OFFLINE mode. Use "hw connect" to reconnect
[offline] pm3 --> hw connect
[=] Using UART port /dev/ttyACM0
[=] Communicating with PM3 over USB-CDC
[usb] pm3 --> hw tune
[=] Measuring antenna characteristics, please wait...
[=] You can cancel this operation by pressing the pm3 button
..
[+] LF antenna: 68,06 V - 125,00 kHz
[+] LF antenna: 36,44 V - 134,83 kHz
[+] LF optimal: 70,26 V - 126,32 kHz
[+]LF antenna is OK
[+] HF antenna: 46,06 V - 13.56 MHz
[+]HF antenna is OK
Probably that is the connection ? ...
Thank's for your help, anyway!
]]>The hw tune part is done here https://github.com/RfidResearchGroup/pr … ain.c#L208
which assumse the GPIO hipeak is set high, which we do in the main loop on device side when init. https://github.com/RfidResearchGroup/pr … in.c#L2080
hw setmux, sets the GPIO pin high. period. https://github.com/RfidResearchGroup/pr … galoader.c
Which OS?, did you compile yourself? Any warnings/errors?
]]>I am running the lates version of iceman's client on my pm3 rdv4:
[ CLIENT ]
client: RRG/Iceman
compiled with GCC 7.5.0 OS:Linux ARCH:x86_64
[ PROXMARK3 RDV4 ]
external flash: present
smartcard reader: present
[ PROXMARK3 RDV4 Extras ]
FPC USART for BT add-on support: absent
[ ARM ]
bootrom: RRG/Iceman/master/c49bfa08 2020-05-05 20:17:35
os: RRG/Iceman/master/c49bfa08 2020-05-05 20:17:51
compiled with GCC 6.3.1 20170620
[ FPGA ]
LF image built for 2s30vq100 on 2020-02-22 at 12:51:14
HF image built for 2s30vq100 on 2020-01-12 at 15:31:16
[ Hardware ]
--= uC: AT91SAM7S512 Rev B
--= Embedded Processor: ARM7TDMI
--= Nonvolatile Program Memory Size: 512K bytes, Used: 290269 bytes (55%) Free: 234019 bytes (45%)
--= Second Nonvolatile Program Memory Size: None
--= Internal SRAM Size: 64K bytes
--= Architecture Identifier: AT91SAM7Sxx Series
--= Nonvolatile Program Memory Type: Embedded Flash Memory
When executing the tune command I am getting an error message that the HF antenna is UNUSABLE. First of all I exchanged antennas and the error message kept coming. Then I started to play with the hardware settings and noticed that setting any mux signal makes the antenna work:
hw setmux hipkd
hw setmux lopkd
hw setmux hiraw
hw setmux loraw
Complete output with hw setmux hipkd:
[usb] pm3 --> hw tune
[=] Measuring antenna characteristics, please wait...
[=] You can cancel this operation by pressing the pm3 button
..
[+] LF antenna: 68,47 V - 125,00 kHz
[+] LF antenna: 36,44 V - 134,83 kHz
[+] LF optimal: 70,67 V - 126,32 kHz
[+]LF antenna is OK
[!]HF antenna is UNUSABLE
[+] Displaying LF tuning graph. Divisor 88 is 134,83 kHz, 95 is 125,00 kHz.
[usb] pm3 --> hw setmux hipkd
[usb] pm3 --> hw tune
[=] Measuring antenna characteristics, please wait...
[=] You can cancel this operation by pressing the pm3 button
..
[+] LF antenna: 68,47 V - 125,00 kHz
[+] LF antenna: 36,44 V - 134,83 kHz
[+] LF optimal: 70,67 V - 126,32 kHz
[+]LF antenna is OK
[+] HF antenna: 46,34 V - 13.56 MHz
[+]HF antenna is OK
[+] Displaying LF tuning graph. Divisor 88 is 134,83 kHz, 95 is 125,00 kHz.
However, pushing the button seems to loose this configuration and the antenna is no longer working.
I tried to find out where the setmux setting comes from and what it does. Unfortunately, I have neither deep programming skills nor I am an hardware expert. What I found out is that the "setmux signal" is part of the I/O's from chip: AT91SAM7S. I.e. MUXEL_HIPKD = PA19; MUXEL_LOPKD = PA20; MUXEL_HIRAW = PA21; MUXEL_LORAW = PA22.
My intention is to find out which part of the hardware is defect. Any ideas? I am also interested in understanding the follwoing:
- If none of the setmux settings is set, which I/O of the chip will than be triggered?
- What is the use of the setmux signals?
Any other hints or advise is also highly appreciated!
Cheers
]]>