RfidResearchGroup/proxmark3
1
1
Fork 0
mirror of https://github.com/RfidResearchGroup/proxmark3.git synced 2025-03-03 19:43:09 +08:00
Code Issues Projects Releases Packages Wiki Activity

Misc work about flashing firmware by JTAG

Browse source 
Add config file for CMSIS-DAP
Highlight the note for unlocking the JTAG ports
This commit is contained in:
wh201906 2024-02-16 14:57:41 +08:00
parent bfcdce9613
commit af11b98f09
No known key found for this signature in database
3 changed files with 28 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
doc/jtag_notes.md
View file

@ -11,12 +11,12 @@ Some notes on how to reflash a bricked Proxmark3 over JTAG.
- [RDV4 pinout](#rdv4-pinout)
- [JLink pinout](#jlink-pinout)
- [Raspberry Pi pinout](#raspberry-pi-pinout)
- [Notes for enabling JTAG port](#notes-for-enabling-jtag-port)
- [Where to find more information?](#where-to-find-more-information)
- [Third party notes on using a BusPirate](#third-party-notes-on-using-a-buspirate)
- [Third party notes on using a J-Link](#third-party-notes-on-using-a-j-link)
- [Third party notes on using a RaspBerry Pi](#third-party-notes-on-using-a-raspberry-pi)
- [Third party notes on using a J-Link on Windows](#third-party-notes-on-using-a-j-link-on-windows)
- [Stack Overflow write up article.](#stack-overflow-write-up-article)
- [Old original docs](#old-original-docs)
@ -95,6 +95,23 @@ GND | 6
3.3 | 1
```
# Notes for enabling JTAG port
^[Top](#top)
If you can communicate with Proxmark3 with OpenOCD, then you don't need to care about this note, as the JTAG port is enabled by default. However, if you see the following output when running OpenOCD, it indicates that the MCU is found, but the JTAG port is disabled (locked).
```
Info : JTAG tap: sam7x.cpu tap/device found: 0x3f0f0f0f (mfg: 0x787 (<unknown>), part: 0xf0f0, ver: 0x3)
Info : TAP auto0.tap does not have valid IDCODE (idcode=0x0)
......
Error: double-check your JTAG setup (interface, speed, ...)
......
Info : Halt timed out, wake up GDB.
Error: timed out while waiting for target halted
```
To resolve this, you need to erase the chip by following the instructions in this Stack Overflow thread.
https://stackoverflow.com/questions/48794076/error-halt-timed-out-wake-up-gdb/64291913#64291913
# Where to find more information?
^[Top](#top)
@ -125,11 +142,6 @@ There has been lots of articles and blogposts about recovering, debricking, JTAG
* https://github.com/Proxmark/proxmark3/wiki/De-Bricking-Segger
## Stack Overflow write up article.
^[Top](#top)
https://stackoverflow.com/questions/48794076/error-halt-timed-out-wake-up-gdb/64291913#64291913
## Old original docs
^[Top](#top)

6
tools/jtag_openocd/interface-cmsis-dap.cfg Normal file
View file

@ -0,0 +1,6 @@
# Note:
# 1. CMSIS-DAP v2 (USB bulk based) is only supported in OpenOCD v0.11.0 and higher versions.
# 2. Some of the CMSIS-DAP debuggers do not implement the JTAG protocol. These debuggers cannot be used for Proxmark3.
source [find interface/cmsis-dap.cfg]
transport select jtag

5
tools/jtag_openocd/openocd_configuration.sample
View file

@ -9,6 +9,9 @@ DUMP="dump_$(date +'%Y%m%d-%H%M%S').bin"
# Segger Jlink:
CONFIG_IF=interface/jlink.cfg
# CMSIS-DAP (read interface-cmsis-dap.cfg for notes):
#CONFIG_IF=interface-cmsis-dap.cfg
# Raspberry Pi models Pi1, Pi2 and Pi Zero (read interface-raspberrypi.cfg for pinout)
#CONFIG_IF=interface-raspberrypi.cfg
@ -34,4 +37,4 @@ CONFIG_IF=interface/jlink.cfg
#CONFIG_IF=interface/parport.cfg
# Shikra:
#CONFIG_IF=interface-shikra.cfg
#CONFIG_IF=interface-shikra.cfg