Proxmark developers community

Research, development and trades concerning the powerful Proxmark3 device.

Remember; sharing is caring. Bring something back to the community.


"Learn the tools of the trade the hard way." +Fravia

You are not logged in.

#1 2018-04-17 17:19:14

homer2320776
Contributor
Registered: 2018-01-30
Posts: 7

Dead Proxmark3 Easy

Hey guys!

I currently have 2 of the Proxmark3 Easy's from Elechouse, and one started acting up about a month ago. Both are running the latest firmware and software from Icemans fork, but it started acting up before the flashing.

Proxmark3 RFID instrument

 [ ARM ]
 bootrom: iceman/master/ice_v3.1.0-790-ga968ea8c 2018-04-17 13:30:43
      os: iceman/master/ice_v3.1.0-790-ga968ea8c 2018-04-17 13:30:48
 [ FPGA ]
 LF image built for 2s30vq100 on 2017/10/25 at 19:50:50
 HF image built for 2s30vq100 on 2017/11/10 at 19:24:16

 [ Hardware ]
  --= uC: AT91SAM7S256 Rev D
  --= Embedded Processor: ARM7TDMI
  --= Nonvolatile Program Memory Size: 256K bytes, Used: 237702 bytes (91%) Free: 24442 bytes ( 9%)
  --= Second Nonvolatile Program Memory Size: None
  --= Internal SRAM Size: 64K bytes
  --= Architecture Identifier: AT91SAM7Sxx Series
  --= Nonvolatile Program Memory Type: Embedded Flash Memory

The issue is when I try to read anything, LF or HF, all I get back are empty responses:

pm3 --> lf read
#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# Done, saved 40000 out of 40000 seen samples at 8 bits/sample
#db# buffer samples: ff ff ff ff ff ff ff ff ...
Reading 39999 bytes from device memory

Data fetched
Samples @ 8 bits/smpl, decimation 1:1
pm3 --> lf search
NOTE: some demods output possible binary
  if it finds something that looks like a tag

False Positives ARE possible

Checking for known tags:

Signal looks just like noise. Looking for Hitag signal now.
Waiting for a response from the proxmark...
You can cancel this operation by pressing the pm3 button
command execution time out

pm3 --> hf search

timeout while waiting for reply.
no known/supported 13.56 MHz tags found

The hardware information just in case it is needed:

pm3 --> hw tune

measuring antenna characteristics, please wait...
...
LF antenna: 23.65 V - 125.00 kHz
LF antenna: 17.00 V - 134.00 kHz
LF optimal: 25.35 V - 121.21 kHz
[+] LF antenna is OK

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

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

pm3 --> hw status
#db# Memory
#db#   BIGBUF_SIZE.............40000
#db#   Available memory........40000
#db# Tracing
#db#   tracing ................0
#db#   traceLen ...............162
#db# Fpga
#db#   mode....................HF
#db# Flash memory
#db#   init....................FAIL
#db# Smart card module (ISO 7816)
#db#   init....................OK
#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.......761856
#db#   USB Transfer Speed PM3 -> Client = 507904 Bytes/s
#db# Various
#db#   MF_DBGLEVEL.............1
#db#   ToSendMax...............24
#db#   ToSendBit...............8
#db#   ToSend BUFFERSIZE.......2308
#db# Installed StandAlone Mods
#db#    LF HID26 standalone - aka SamyRun (Samy Kamkar)

Any help would be greatly appreciated!

Offline

#2 2018-04-17 18:15:37

iceman
Administrator
Registered: 2013-04-25
Posts: 4,781
Website

Re: Dead Proxmark3 Easy

try latest source from offical pm3 repo.  It will give an indication if its the device or firmware.


冰人

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#3 2018-04-17 18:59:15

homer2320776
Contributor
Registered: 2018-01-30
Posts: 7

Re: Dead Proxmark3 Easy

Seems to do the same thing

proxmark3> hw ver
[[[ Cached information ]]]

Prox/RFID mark3 RFID instrument
bootrom: master/v3.0.1-361-ge069547-suspect 2018-04-03 11:12:28
os: master/v3.0.1-361-ge069547-suspect 2018-04-03 11:12:31
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2017/10/27 at 08:30:59

uC: AT91SAM7S256 Rev D
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 199639 bytes (76%). Free: 62505 bytes (24%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

proxmark3> hw tune

Measuring antenna characteristics, please wait.........
# LF antenna: 21.04 V @   125.00 kHz
# LF antenna: 18.84 V @   134.00 kHz
# LF optimal: 21.04 V @   125.00 kHz
# HF antenna: 25.17 V @    13.56 MHz
Displaying LF tuning graph. Divisor 89 is 134khz, 95 is 125khz.



proxmark3> hw status
#db# Memory
#db#   BIGBUF_SIZE.............40000
#db#   Available memory........40000
#db# Tracing
#db#   tracing ................1
#db#   traceLen ...............224
#db# Fgpa
#db#   mode....................HF
#db# LF Sampling config:
#db#   [q] divisor:           95
#db#   [b] bps:               8
#db#   [d] decimation:        1
#db#   [a] averaging:         1
#db#   [t] trigger threshold: 0
#db# USB Speed:
#db#   Sending USB packets to client...
#db#   Time elapsed:      1500ms
#db#   Bytes transferred: 795136
#db#   USB Transfer Speed PM3 -> Client = 530090 Bytes/s
#db# Various
#db#   MF_DBGLEVEL......2
#db#   ToSendMax........13
#db#   ToSendBit........8
proxmark3> lf read
#db# LF Sampling config:
#db#   [q] divisor:           95
#db#   [b] bps:               8
#db#   [d] decimation:        1
#db#   [a] averaging:         1
#db#   [t] trigger threshold: 0
#db# Done, saved 40000 out of 40000 seen samples at 8 bits/sample
#db# buffer samples: ff ff ff ff ff ff ff ff ...
Reading 39999 bytes from device memory

Data fetched
Samples @ 8 bits/smpl, decimation 1:1
proxmark3> hf search


no known/supported 13.56 MHz tags found

Awhile back when I first noticed this issue, I got frustrated and 'dropped' the device onto my desk, the percussive maintenance seemed to fix it for a short while but I was never able to get it working again.

The newer device works flawlessly but I would like to get this one working as a backup, just in case.

Offline

Board footer

Powered by FluxBB