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.
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.
I can't seem to make a connection between my segger jlink to ProxMark3 easy 512.
In JLinkExe, after running "h", jlink is complaining:
**************************
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
**************************
I've tried resetting the protection bits on the atmel (following: http://www.proxmark.org/forum/viewtopic.php?pid=34445#p34445):
* While the PM3E was powered up:
* connecting/shorting Pin 55 to v3.3, for 1 second.
* power cycled the board.
Hardware:
* Segger J Link (clone, latest firmware)
* Proxmark3 Easy 512 (AT91SAM7S512)
OS: Mac OSX 10.15.4 Catalina
Brew has Proxmark installed.
This is what I've tried, in as much relevant details as possible:
Connected the
(Proxmark 3 Easy <=> Segger JLink)
TMS <=> TMS
TDI <=> TDI
TDO <=> TDO
TCK <=> TCK
GND <=> GND
3.3V <=> VTref (pin1), I've tried pin 2 as well.
using a continuity tester, at start of one header to another. All good connections.
Both the JTAG and Proxmark are plugged into the computer via USB. the headers are connected together.
$> sudo SLinkExe
J-Link> exec device = AT91SAM7S512
J-Link> exec EnableFlashDL
J-Link> h
J-Link> loadbin "proxmark3_recovery.bin" 0x100000
LOG
$> sudo JLinkExe
Password:
SEGGER J-Link Commander V6.72b (Compiled May 4 2020 13:45:14)
DLL version V6.72b, compiled May 4 2020 13:44:57
Connecting to J-Link via USB...O.K.
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware version: V8.00
S/N: -1
License(s): RDI,FlashDL,FlashBP,JFlash,GDB
VTref=3.274V
Type "connect" to establish a target connection, '?' for help
J-Link>exec device = AT91SAM7S512
Device "AT91SAM7S512" selected.
J-Link>exec EnableFlashDL
J-Link>h
Target connection not established yet but required for command.
Please specify device / core. <Default>: AT91SAM7S512
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "AT91SAM7S512" selected.
Connecting to target via JTAG
TotalIRLen = ?, IRPrint = 0x..000000000000000000000001
**************************
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
**************************
TotalIRLen = ?, IRPrint = 0x..000000000000000000000001
TotalIRLen = ?, IRPrint = 0x..000000000000000000000001
**************************
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
**************************
TotalIRLen = ?, IRPrint = 0x..000000000000000000000001
Cannot connect to target.
J-Link>
I'm not here yet... but I've compiled the source, to get proxmark3_recovery.bin still not sure if this is the appropriate bin to flash/unbrick with
Compiled recovery bin from source (following the compiling instructions, and getting the latest versions
$> md5sum proxmark3_recovery.bin
15ee9583ab60cf8212d219d5ee86630f proxmark3_recovery.bin
I'm at a loss... maybe the pin55 erase never got shorted properly? Anyone have some ideas, or does the proxmark3 easy go back on my healing bench for eternity?
Offline