Proxmark3 community

roosted

Contributor

Registered: 2018-10-22

Posts: 2

HF driver bad? Proxmark3 'easy' does not simulate

Hi all!

I've recently bought an 'original'(?) Proxmark3 Easy with 512k chip.
But sadly it seems be only partially working; reading and writing to cards works fine, but simulation does not work. (Also sniffing somehow only shows messages from the tag and never from the reader.)
I've tried many simulation modes (14a, mf, etc), but none of them work. Both my ACR122 and Oneplus device do not respond to the Proxmark at all..

Here is my hardware and software information:

[ ARM ]
 bootrom: iceman/master/ice_v3.1.0-1060-gbac9fe04 2018-10-21 07:00:25
      os: iceman/master/ice_v3.1.0-1060-gbac9fe04 2018-10-21 07:00:30

 [ FPGA ]
 LF image built for 2s30vq100 on 2017/10/25 at 19:50:50
 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: 235800 bytes (45%) Free: 288488 bytes (55%)          
  --= Second Nonvolatile Program Memory Size: None          
  --= Internal SRAM Size: 64K bytes          
  --= Architecture Identifier: AT91SAM7Sxx Series          
  --= Nonvolatile Program Memory Type: Embedded Flash Memory  

Ofcourse I also tried with the vanilla software, that made no difference. My host OS is Arch Linux.

The antenna performance seems great and not an issue. I can read cards and detect reader fields over 4cm away and resonance voltages also seem fine:

pm3 --> hw tune
          
[=] measuring antenna characteristics, please wait...
          
....
          
[+] LF antenna: 35,26 V - 125.00 kHz          
[+] LF antenna: 27,33 V - 134.00 kHz          
[+] LF optimal: 35,41 V - 123,71 kHz          
[+] LF antenna is OK 
          
[+] HF antenna: 27,20 V - 13.56 MHz          
[+] HF antenna is OK          
          
[+] Displaying LF tuning graph. Divisor 89 is 134khz, 95 is 125khz.

What could be causing this issue? It seems like my device can read the coil open and drive it, but cannot load the coil like a tag would.
I know there are 8 drivers per coil, could one of them be broken to cause these symptoms? How could I check this?

Many thanks in advance for your help