project:arm_debugging:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
project:arm_debugging:start [2019/01/27 23:19] – [Chipwhisperer + UFO target board + STLink v2 + STM32F4] SHUNTL+SHUNTH jumper and other gotchas for programming abyssal | project:arm_debugging:start [2019/08/21 16:00] – [Example: Unbricking (restoring) Proxmark bootloader] trimen | ||
---|---|---|---|
Line 290: | Line 290: | ||
The code halts processor, erases bootloader sectors, then writes bootloader from ''/ | The code halts processor, erases bootloader sectors, then writes bootloader from ''/ | ||
+ | |||
+ | If you receiving errors: | ||
+ | < | ||
+ | Info : TAP autoX.tap does not have IDCODE | ||
+ | .(some more info) | ||
+ | Warn : Unexpected idcode after end of chain: XY 0x00000000 | ||
+ | .(some more warinings) | ||
+ | Error: auto0.tap: IR capture error; saw 0x0000 not 0x0001 | ||
+ | </ | ||
+ | It's because your CPU has locked flash/JTAG. | ||
+ | To solve this connect pin 55(ERASE) of CPU to 3.3V for at least 0.5sec. It will trigger erase of flash content and enable JTAG. | ||
+ | This is happening mostly on cheap clones of proxmark3 Easy. | ||
+ | |||
+ | |||
+ | |||
===== J-link connected to Proxmark ===== | ===== J-link connected to Proxmark ===== |
project/arm_debugging/start.txt · Last modified: 2021/06/05 19:29 by abyssal