Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
project:arm_debugging:start [2019/01/28 00:19]
abyssal [Chipwhisperer + UFO target board + STLink v2 + STM32F4] SHUNTL+SHUNTH jumper and other gotchas for programming
project:arm_debugging:start [2019/08/21 18:00] (current)
trimen [Example: Unbricking (restoring) Proxmark bootloader]
Line 290: Line 290:
  
 The code halts processor, erases bootloader sectors, then writes bootloader from ''/​path/​to/​booloader.elf''​. After power cycling the bootloader should be working if the elf file is correct. The code halts processor, erases bootloader sectors, then writes bootloader from ''/​path/​to/​booloader.elf''​. After power cycling the bootloader should be working if the elf file is correct.
 +
 +If you receiving errors:
 +<​code>​
 +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
 +</​code>​
 +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 =====
 
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki