Openocd - Revision history

Leo: Added categories and navbox

2021-12-30T01:11:32Z

Added categories and navbox

← Older revision		Revision as of 01:11, 30 December 2021
Line 87:		Line 87:
	Changing the RDP levels with the stm32f1x unlock command will erase the contents on the device. You may try to readout the contents through the CPU using the [https://github.com/doegox/stm32f1-firmware-extractor stm32f1-firmware-extractor project], but this is imperfect and leaves many gaps in the dump. It's probably still better than nothing.		Changing the RDP levels with the stm32f1x unlock command will erase the contents on the device. You may try to readout the contents through the CPU using the [https://github.com/doegox/stm32f1-firmware-extractor stm32f1-firmware-extractor project], but this is imperfect and leaves many gaps in the dump. It's probably still better than nothing.

	~~<br />~~		{{Navbox Linux}}
			[[Category:Linux]]
			[[Category:LinuxUtilities]]

Leo at 23:44, 25 May 2021

2021-05-25T23:44:49Z

← Older revision		Revision as of 23:44, 25 May 2021
Line 42:		Line 42:

	==Interfacing with STM32F100==		==Interfacing with STM32F100==
	~~There are some specific commands~~ for the ~~STM32F100 through~~ the ~~stm32f1x commands~~. To begin, ~~run~~:		The STM32 like many ARM Cortex processors can be debugged using a Serial Wire Debug (SWD) interface which consists of two signals: SWDCLK (clock) and SWDIO (for bi-directional data). The SWD uses an interface called a Debug Access Port (DAP) which defines a master (the Debug Port or DP) and one or more slaves (the target, referred to as Access Ports or AP). You can read more about the details on [https://research.kudelskisecurity.com/2019/05/16/swd-arms-alternative-to-jtag/ this article "SWD – ARM’S ALTERNATIVE TO JTAG]".

			To begin interfacing with a STM32, use a STLink USB dongle and connect the clock line to SWCLK, the data line to SWDIO, and ground to ground. Run OpenOCD with the following command using the interface and target files that comes with OpenOCD:
	{{Highlight		{{Highlight
	\| code = # openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg		\| code = # openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg
Line 62:		Line 64:
	\|}		\|}

	=== STM32's readout protection ===		===STM32's readout protection===
	When running the options_read command, you will see whether there is readout protection enabled:		When running the options_read command, you will see whether there is readout protection enabled:
	{{Highlight		{{Highlight
Line 79:		Line 81:
	There are 3 levels or RDP:		There are 3 levels or RDP:

	* 0: No read protection.		*0: No read protection.
	* 1: Read protection enabled.		*1: Read protection enabled.
	* 2: Debug/chip read protection disabled. Will disable JTAG, which is bad for our case.		*2: Debug/chip read protection disabled. Will disable JTAG, which is bad for our case.

	Changing the RDP levels with the stm32f1x unlock command will erase the contents on the device. You may try to readout the contents through the CPU using the [https://github.com/doegox/stm32f1-firmware-extractor stm32f1-firmware-extractor project], but this is imperfect and leaves many gaps in the dump. It's probably still better than nothing.		Changing the RDP levels with the stm32f1x unlock command will erase the contents on the device. You may try to readout the contents through the CPU using the [https://github.com/doegox/stm32f1-firmware-extractor stm32f1-firmware-extractor project], but this is imperfect and leaves many gaps in the dump. It's probably still better than nothing.

	<br />		<br />

Leo at 21:46, 25 May 2021

2021-05-25T21:46:04Z

@@ Line 1: / Line 1: @@
 <br />
-== Cheat Sheet ==
+==Cheat Sheet==
 For a comprehensive list of commands, see: http://www.openocd.org/doc/html/General-Commands.html
 {| class="wikitable"
@@ Line 41: / Line 41: @@
 |}
-== Interfacing with STM32F100 ==
+==Interfacing with STM32F100==
 There are some specific commands for the STM32F100 through the stm32f1x commands. To begin, run:
 {{Highlight
@@ Line 61: / Line 61: @@
 |Unlock the readout protection (Warning: erases existing contents!)
 |}
 <br />

Leo: Created page with "
== Cheat Sheet == For a comprehensive list of commands, see: http://www.openocd.org/doc/html/General-Commands.html {| class="wikitable" !Command !Description |- |
2021-05-25T21:42:14Z

Created page with "<br /> == Cheat Sheet == For a comprehensive list of commands, see: http://www.openocd.org/doc/html/General-Commands.html {| class="wikitable" !Command !Description |- |<code..."

New page
<br />

== Cheat Sheet ==
For a comprehensive list of commands, see: http://www.openocd.org/doc/html/General-Commands.html
{| class="wikitable"
!Command
!Description
|-
|<code>init</code>
|initalize
|-
|<code>halt</code>
|halt the processor
|-
|<code>reset halt</code>
|reset device and halt
|-
|<code>reset run</code>
|reset device and start execution
|-
|<code>flash list</code>
|lists detected flash devices
|-
|<code>flash read_bank <bank> <outputfile></code>

<code>flash read_bank 0 firmware.bin 0 0x8000</code>
|Reads the entire bank of flash memory into an output file.
Eg. read the first 32KB of flash memory
|-
|<code>reg</code>
|shows all registers
|-
|<code>reg <register></code>
|Shows a specific register. Eg. <code>reg r0</code>.
|-
|<code>md{d,w,h,b} <address></code>
|Memory access (d = double/64 bit, w = word/32 bit, h = half/16 bit, b = byte/8 bit)
|-
|<code>mw{d,w,h,b} <address></code>
|Memory write (same units above).
|}

== Interfacing with STM32F100 ==
There are some specific commands for the STM32F100 through the stm32f1x commands. To begin, run:
{{Highlight
| code = # openocd -f interface/stlink-v2.cfg -f target/stm32f1x.cfg
| lang = terminal
}}
You may use the commands listed in the cheat sheet above and also the STM32 specific commands below.
{| class="wikitable"
!Command
!Description
|-
|<code>stm32f1x mass_erase 0</code>
|Erase
|-
|<code>stm32f1x options_read 0</code>
|Check set options, such as if readout protection is enabled.
|-
|<code>stm32f1x unlock 0</code>
|Unlock the readout protection (Warning: erases existing contents!)
|}
<br />