Proxmark3 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.

Announcement

Time changes and with it the technology
Proxmark3 @ discord

Users of this forum, please be aware that information stored on this site is not private.

#1 2014-09-27 00:59:46

ProxDesease
Member
Registered: 2014-09-27
Posts: 5

Darkside attack and Emulation problems

Hi to such a greate community,

I've updated to the latest Bootrom, OS and FPGA firmwares.
Thats the log:
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument                 
#db# bootrom: /-suspect 2014-09-19 10:31:37                 
#db# os: /-suspect 2014-09-13 11:21:04                 
#db# HF FPGA image built on 2014/ 6/19 at 21:26: 2                 
uC: AT91SAM7S256 Rev B         
Embedded Processor: ARM7TDMI         
Nonvolatile Program Memory Size: 256K bytes         
Second Nonvolatile Program Memory Size: None         
Internal SRAM Size: 64K bytes         
Architecture Identifier: AT91SAM7Sxx Series         
Nonvolatile Program Memory Type: Embedded Flash Memory

1) So the problem is that when I start the darkside attack, most of the time it just hangs and than proxmark restarts by itself
2) The second problem is that it doesnt emulate the mifare card. I load the eml file into memory, it is stored there, no problem here, but than I use command: "hf mf sim" and it just returns:
uid:N/A, numreads:0, flags:0 (0x00)           
proxmark3>
proxmark3> #db# 4B UID: 5c444x7s

And no simlutation is going on.
Then I press the button on the proxmark itself and get this:
proxmark3> #db# Emulator stopped. Tracing: 1  trace length: 0

I would really appreciate any help,
Have been messing with it whole nights,

Yours sincerely,
John

Offline

#2 2014-10-27 19:00:35

holiman
Contributor
Registered: 2013-05-03
Posts: 566

Re: Darkside attack and Emulation problems

Regarding 2)
How do you know it does not emulate ? What you're describing sound like it is - how do you check what is happening on the air?
Also try increasing the debuglevel 'hf mf dbg 4'. Doing so may by itself screw with the functionality, since doing USB-writes to write the debug messages disturb the sensitive timings in the reader<-> tag communication, but at least it gives you some more info.

Offline

Board footer

Powered by FluxBB