Proxmark3 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 2020-07-15 23:34:09

4ntcard
Contributor
Registered: 2020-05-24
Posts: 9

jtag Proxmark3 rdv4 problems

Hello, can someone help me, please?

System: Ubuntu 18.04
openocd installed
J-link v8 plus & jtag tool


ubuntu@linux:~$ lsusb
Bus 001 Device 007: ID 1366:0101 SEGGER J-Link PLUS


sudo dmesg | grep -i usb
Device= 1.00
[ 5126.086356] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5126.086359] usb 1-3: Product: J-Link
[ 5126.086362] usb 1-3: Manufacturer: SEGGER
[ 5126.086364] usb 1-3: SerialNumber: 004294967295

ubuntu@linux:~/proxmark3/tools/jtag_openocd$ ./openocd_flash_recovery.sh
./openocd_flash_recovery.sh: línea 4: openocd_configuration: File or directory does not exist

Can someone give me some clue where I am failing and how I can bring my proxmark3 back to life?.Thanks

Offline

#2 2020-07-18 11:49:31

4ntcard
Contributor
Registered: 2020-05-24
Posts: 9

Re: jtag Proxmark3 rdv4 problems

Hello.. openocd . it gives me the following error. proxmark3 now has all the LEDs on blu and reds, and is obviously not detected by usb. Can someone help me. thanks

Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> halt
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x300000d3 pc: 0x0011d1dc
> flash erase_sector 0 0 15
erased sectors 0 through 15 on flash bank 0 in 0.031944s
> flash erase_sector 1 0 15
erased sectors 0 through 15 on flash bank 1 in 0.030221s
> dump_image backup.bin 0x100000 0x80000
dumped 524288 bytes in 26.594435s (19.252 KiB/s)
> flash write_image ./recovery/proxmark3_recovery.bin 0x100000
couldn't open ./recovery/proxmark3_recovery.bin

Offline

#3 2020-07-19 21:47:39

fazer
Contributor
Registered: 2019-03-02
Posts: 69

Re: jtag Proxmark3 rdv4 problems

Good evening 4ntcard, have you looked at the jtag procedure in the proxmark3 / tools / jtag_openocd file. I think you will have some interesting info for your jtag procedure.
Good night

Offline

#4 2020-07-20 09:18:32

4ntcard
Contributor
Registered: 2020-05-24
Posts: 9

Re: jtag Proxmark3 rdv4 problems

Good day. Thank. the truth is well documented. And it is complicated, if you read and follow the instructions on github, I have already flashed it, but I still have a problem, which does not enter this thread. Thank you.

n3thunter@linux:~/p1/tools/jtag_openocd$ ./openocd_flash_recovery.sh
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
adapter speed: 1000 kHz
srst_only srst_pulls_trst srst_gates_jtag srst_open_drain connect_deassert_srst
Info : No device selected, using first device.
Info : J-Link ARM V8 compiled Nov 28 2014 13:44:46
Info : Hardware version: 8.00
Info : VTarget = 3.274 V
Info : clock speed 1000 kHz
Info : JTAG tap: sam7x.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787 (<unknown>), part: 0xf0f0, ver: 0x3)
Info : Embedded ICE version 1
Info : sam7x.cpu: hardware has 2 breakpoint/watchpoint units
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x800000d3 pc: 0x0000003c
erased sectors 0 through 15 on flash bank 0 in 0.032039s
erased sectors 0 through 15 on flash bank 1 in 0.032204s
wrote 267224 bytes from file ../../recovery/proxmark3_recovery.bin in 26.988897s (9.669 KiB/s)

Offline

Board footer

Powered by FluxBB