Proxmark3: Debricking - Revision history

Silvie: Protected "Proxmark3: Debricking" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2021-03-19T15:05:51Z

Protected "Proxmark3: Debricking" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 15:05, 19 March 2021
(No difference)

Jostrowski at 20:21, 19 September 2020

2020-09-19T20:21:56Z

@@ Line 45: / Line 45: @@
 </pre>
 <code>make</code> will take about 15 minutes.
 === Connect physically ===
@@ Line 132: / Line 136: @@
 :: <code>sudo openocd -f tools/raspi.cfg</code>
 :: Now a openOCD session is started. Do '''not''' close it.
 ; 4. Connect to OpenOCD session
 : Open a new terminal window and telnet to the port that was specified in the .cfg file
 :: <code>telnet localhost 4444</code>
 ; 5. Flash via JTAG
 ; 6. Halt the Proxmark3
 :: <code>halt</code>
@@ Line 152: / Line 187: @@
 :: <code>flash write_image ./armsrc/obj/fullimage.elf</code>
 :: <code>flash write_image ./bootrom/obj/bootrom.elf</code>
 '''Done!'''

Jostrowski at 08:09, 19 September 2020

2020-09-19T08:09:06Z

← Older revision		Revision as of 08:09, 19 September 2020
Line 63:		Line 63:
	\| TCK \|\| 23 \|\| orange		\| TCK \|\| 23 \|\| orange
	\|-		\|-
	\| GND \|\| 6 \|\| ~~purple~~		\| GND \|\| 6 \|\| grey
	\|-		\|-
	\| 3.3V \|\| 1 \|\| ~~grey~~		\| 3.3V \|\| 1 \|\| purple
	\|}		\|}

Jostrowski at 19:17, 12 December 2019

2019-12-12T19:17:07Z

← Older revision		Revision as of 19:17, 12 December 2019
Line 1:		Line 1:
	== Summary ==		== Summary ==

	~~Description on~~ how to ~~debrick the~~ Proxmark3 RDV2 ~~if the bootloader or firmware is corrupted and there is no connection between the Proxmark3 and~~ the ~~computer~~.		This tutorial will show how to reset a Proxmark3 RDV2 via the JTAG interface.

	~~Note: The method with~~ the ~~Bus Pirate did~~ '''~~not work~~''' ~~for me~~. ~~Maybe you have better luck~~.		This is useful when the '''Proxmark3 RDV2''' is bricked and won't connect to the computer. This will solve any software failures like a corrupt firmware or bootloader.

	~~In the first part the debricking~~ process ~~for the~~ Raspberry Pi 3+ (version 2, 3 and 4 work exactly the same) ~~will be showcased~~. ~~In the second part~~ the ~~same will be shown using a~~ Bus Pirate.		'''1.''' Debricking process via '''Raspberry Pi''' 3+ (version 2, 3 and 4 work exactly the same)<br>
			'''2.''' Debricking process via '''Bus Pirate''' 3.6
			: Note: The method with the Bus Pirate did '''not work''' for me. Maybe you have better luck.

	== Requirements ==		== Requirements ==
Line 29:		Line 31:
	See [https://wiki.elvis.science/index.php?title=Proxmark3:_Installation Proxmark: Installation] or from the [https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux official website]		See [https://wiki.elvis.science/index.php?title=Proxmark3:_Installation Proxmark: Installation] or from the [https://github.com/Proxmark/proxmark3/wiki/Ubuntu-Linux official website]

	=== ~~Compiling~~ OpenOCD ===		=== Compile OpenOCD ===

	<pre>		<pre>
Line 51:		Line 53:
	! Proxmark3		! Proxmark3
	! Raspberry Pi		! Raspberry Pi
	! Cable ~~color~~		! Cable colour
	\|-		\|-
	\| TMS \|\| 22 \|\| yellow		\| TMS \|\| 22 \|\| yellow
Line 76:		Line 78:
	=== Connect via OpenOCD ===		=== Connect via OpenOCD ===

	''Note: Power the Proxmark ~~desperately~~ from the Raspberry Pi''		''Note: Power the Proxmark separately from the Raspberry Pi''

	; 1. Start OpenOCD		; 1. Start OpenOCD
	: switch to the Proxmark folder		: switch to the Proxmark folder
	:: <code>cd proxmark3</code>		:: <code>cd proxmark3</code>
	:: ''Note: the source code of the ~~proxmark~~ should be already be complied.''		:: ''Note: the source code of the Proxmark should be already be complied.''
	; 2. Create OpenOCD configuration		; 2. Create OpenOCD configuration
	:: <code>nano tools/raspi.cfg</code>		:: <code>nano tools/raspi.cfg</code>
Line 165:		Line 167:
	''Note: Here the Bus Pirate 3.6 will be used''		''Note: Here the Bus Pirate 3.6 will be used''

	''Note: This did not work for me, maybe it was faulty hardware a faulty firmware''		''Note: This did not work for me, maybe it was faulty hardware or faulty firmware''

	This tutorial is based on https://scund00r.com/all/rfid/2018/05/18/debrick-proxmark.html		This tutorial is based on https://scund00r.com/all/rfid/2018/05/18/debrick-proxmark.html

Jostrowski at 19:03, 12 December 2019

2019-12-12T19:03:08Z

@@ Line 5: / Line 5: @@
 Note: The method with the Bus Pirate did '''not work''' for me. Maybe you have better luck.
-In the first part the debricking process with an Raspberry Pi 3+ (version 2, 3 and 4 will work exactly the same) will be showcased. In the second part the same will be shown using a Bus Pirate.
+In the first part the debricking process for the Raspberry Pi 3+ (version 2, 3 and 4 work exactly the same) will be showcased. In the second part the same will be shown using a Bus Pirate.
 == Requirements ==
@@ Line 86: / Line 85: @@
 :: <code>nano tools/raspi.cfg</code>
 :: Past following code into the file
 <pre>
-TODO: Paste code here
+# Ports
 </pre>
 ; 3. Start OpenOCD with the configuration file just created
 :: <code>sudo openocd -f tools/raspi.cfg</code>

Jostrowski at 15:22, 12 December 2019

2019-12-12T15:22:04Z

@@ Line 45: / Line 45: @@
 <code>make</code> will take about 15 minutes.
-=== Connect ===
+=== Connect physically ===
 Connect the following pins from the Raspberry Pi to the Proxmark3
@@ Line 52: / Line 52: @@
 ! Proxmark3
 ! Raspberry Pi
 |-
-| TMS ||
+| TMS || 22 || yellow
 |-
-| TDI ||
+| TDI || 19 || blue
 |-
-| TDO ||
+| TDO || 21 || green
 |-
-| TCK ||
+| TCK || 23 || orange
 |-
-| GND || 6
+| GND || 6  || purple
 |-
-| 3.3V || 1
+| 3.3V || 1 || grey
 |}
 [[File:Proxmark raspi pin.jpg|border|600px]]
-The pin configuration can be set in: <code>/usr/share/openocd/interface/raspberrypi2-native.cfg</code>
+The pin configuration can be changed in: <code>/usr/share/openocd/interface/raspberrypi2-native.cfg</code>. (Not necessary for this tutorial)
 == Bus Pirate ==

Jostrowski at 11:26, 12 December 2019

2019-12-12T11:26:09Z

← Older revision		Revision as of 11:26, 12 December 2019
Line 63:		Line 63:
	\| GND \|\| 6		\| GND \|\| 6
	\|-		\|-
	\| 3.3V \|\| ~~3.3V~~		\| 3.3V \|\| 1
	\|}		\|}

Jostrowski at 11:24, 12 December 2019

2019-12-12T11:24:18Z

@@ Line 1: / Line 1: @@
 == Summary ==
-Description on how to debrick the Proxmark3 using a Bus Pirate. This tutorial is based on https://scund00r.com/all/rfid/2018/05/18/debrick-proxmark.html
+Description on how to debrick the Proxmark3 RDV2 if the bootloader or firmware is corrupted and there is no connection between the Proxmark3 and the computer.
 == Requirements ==
 * Proxmark3
 * Bus Pirate v3 (or higher)
 * Linux: Debian
-== Description ==
+== Raspberry Pi ==
 ; Update the Bus Pirate

Jostrowski: Jostrowski moved page Proxmark3: Debricking using the Bus Pirate to Proxmark3: Debricking

2019-12-12T10:02:59Z

Jostrowski moved page Proxmark3: Debricking using the Bus Pirate to Proxmark3: Debricking

← Older revision		Revision as of 10:02, 12 December 2019
(No difference)

Jostrowski at 09:51, 5 December 2019

2019-12-05T09:51:26Z

← Older revision		Revision as of 09:51, 5 December 2019
Line 56:		Line 56:
	buspirate_port /dev/ttyUSB0		buspirate_port /dev/ttyUSB0
	adapter_khz 1000		adapter_khz 1000
	~~: Launch OpenOCD~~
	~~:: <code>sudo openocd -f tools/at91sam7s512-buspirate.cfg</code>~~
	; Start OpenOCD		; Start OpenOCD
	: Launch OpenOCD		: Launch OpenOCD