CW308T-STM32F/ChipWhisperer Bootloader - Revision history

Adewar at 15:03, 7 May 2020

2020-05-07T15:03:21Z

Adewar at 15:02, 7 May 2020

2020-05-07T15:02:42Z

Adewar at 19:21, 12 March 2020

2020-03-12T19:21:01Z

Adewar at 17:58, 11 March 2020

2020-03-11T17:58:13Z

Adewar at 16:26, 27 February 2020

2020-02-27T16:26:51Z

Cwiesner: /* Rev -02 Boards */

2018-02-15T21:10:44Z

‎Rev -02 Boards

Coflynn: /* Rev -02 Boards */

2018-02-06T03:50:42Z

‎Rev -02 Boards

Coflynn at 03:05, 6 February 2018

2018-02-06T03:05:07Z

Coflynn at 03:04, 6 February 2018

2018-02-06T03:04:08Z

Coflynn at 03:03, 6 February 2018

2018-02-06T03:03:45Z

@@ Line 22: / Line 22: @@
 To access the bootloader you can perform these steps. They vary based on if you have a "Rev 02" board or a "Rev 03 or Later" board. The revision number is printed on the bottom side as part of the PCB part number (STM32F-03 is Rev -03 for example).
-=== Rev -03 or Later ===
+==== Rev -03 or Later ====
 Run the following python code once you have the scope and target set up:
@@ Line 38: / Line 38: @@
 * If using a CW308 based STM, try mounting a jumper between the "SH-" and "SH+" pins at J16 (to the left of the SMA connector) on the UFO board. Retry programming with the jumper mounted.
-=== Rev -02 Boards ===
+==== Rev -02 Boards ====
 The Rev -02 boards did not have all programming connections present. They require some additional steps:

@@ Line 22: / Line 22: @@
 To access the bootloader you can perform these steps. They vary based on if you have a "Rev 02" board or a "Rev 03 or Later" board. The revision number is printed on the bottom side as part of the PCB part number (STM32F-03 is Rev -03 for example).
-== Rev -03 or Later ==
+=== Rev -03 or Later ===
 Run the following python code once you have the scope and target set up:
@@ Line 38: / Line 38: @@
 * If using a CW308 based STM, try mounting a jumper between the "SH-" and "SH+" pins at J16 (to the left of the SMA connector) on the UFO board. Retry programming with the jumper mounted.
-== Rev -02 Boards ==
+=== Rev -02 Boards ===
 The Rev -02 boards did not have all programming connections present. They require some additional steps:

@@ Line 3: / Line 3: @@
 Important notes before we begin:
-* You MUST setup a clock and the serial lines for the chip. This is easily done by selecting a start-up script such as the "AES SimpleSerial on XMEGA" startup script.
+* You MUST setup a clock and the serial lines for the chip. This is easily done by connecting to the scope and target, then running <code>default_setup()</code>:
-* On the STM32F1, you MUST adjust the clock frequency to 8MHz. The bootloader does not work with our usual 7.37 MHz clock frequency. '''This 8MHz frequency does not apply to the code that you're running on the device. Once you're done programming, you'll need to set the frequency back to F_CPU (likely 7.37MHz)'''
+<syntaxhighlight lang=python>
 To access the bootloader you can perform these steps. They vary based on if you have a "Rev 02" board or a "Rev 03 or Later" board. The revision number is printed on the bottom side as part of the PCB part number (STM32F-03 is Rev -03 for example).

@@ Line 1: / Line 1: @@
 The STM32Fx devices have a built-in bootloader, and the ChipWhisperer software as of 3.5.2 includes support for this bootloader.
 Important notes before we begin:
 * You MUST setup a clock and the serial lines for the chip. This is easily done by selecting a start-up script such as the "AES SimpleSerial on XMEGA" startup script.
-* On the STM32F1, you MUST adjust the clock frequency to by 8MHz. The bootloader does not work with our usual 7.37 MHz clock frequency. '''You must set the clock frequency back to 7.37MHz after programming the device.'''
+* On the STM32F1, you MUST adjust the clock frequency to 8MHz. The bootloader does not work with our usual 7.37 MHz clock frequency. '''This 8MHz frequency does not apply to the code that you're running on the device. Once you're done programming, you'll need to set the frequency back to F_CPU (likely 7.37MHz)'''
 To access the bootloader you can perform these steps. They vary based on if you have a "Rev 02" board or a "Rev 03 or Later" board. The revision number is printed on the bottom side as part of the PCB part number (STM32F-03 is Rev -03 for example).
@@ Line 9: / Line 10: @@
 == Rev -03 or Later ==
-# Select the "Serial STM32F Programmer"
+Run the following python code once you have the scope and target set up:
-#: [[File:arm_programmer.png]]
+<syntaxhighlight lang=python>
-# Select the hex-file and press the "Program/Verify" button.
+prog = cw.programmers.STM32FProgrammer
-# The device should program, it may take a moment to fully program/verify on larger devices:
+cw.program_target(scope, prog, "<path to fw hex file>")
-#: [[File:arm_programmed.png]]
+</syntaxhighlight>
-{{Warningbox|If you get verify errors, it's possible the shunt resistor is causing power to dip too low. This can be solved by mounting a jumper between the "SH-" and "SH+" pins at J16 (to the left of the SMA connector) on the UFO board. Retry programming with the jumper mounted. }}
+If you get errors during the programming process:
 == Rev -02 Boards ==
@@ Line 21: / Line 28: @@
 The Rev -02 boards did not have all programming connections present. They require some additional steps:
-# Select the "Serial STM32F Programmer"
+# Setup the device as usual:
-#: [[File:arm_programmer.png]]
+#:<syntaxhighlight lang=python>
 # Mount a jumper between the H1 and PDIC pins (again this is ONLY for the -02 rev).
 #: [[File:STMF32F-02 programmer jumper.jpg|400px]]
 # Reset the ARM device either by pressing the reset button (newer UFO boards only), or by toggling power:
-#: [[File:arm_togglepower.png]]
+#:<syntaxhighlight lang=python>
-# Select the hex-file and press the "Program/Verify" button.
+import time
-# The device should program, it may take a moment to fully program/verify on larger devices:
+scope.io.target_pwr = False
-#: [[File:arm_programmed.png]]
+time.sleep(1)
 # Remove the jumper between the H1/H2 pins.
 # Reset the ARM device either by pressing the reset button (newer UFO boards only), or by toggling power:
-#: [[File:arm_togglepower.png]]
+#:<syntaxhighlight lang=python>
+import time
-{{Warningbox|If you get verify errors, it's possible the shunt resistor is causing power to dip too low. This can be solved by mounting a jumper between the "SH-" and "SH+" pins at J16 (to the left of the SMA connector) on the UFO board. Retry programming with the jumper mounted. }}
+scope.io.target_pwr = False

@@ Line 3: / Line 3: @@
 Important notes before we begin:
 * You MUST setup a clock and the serial lines for the chip. This is easily done by selecting a start-up script such as the "AES SimpleSerial on XMEGA" startup script.
-* On the STM32F1, you MUST adjust the clock frequency to by 8MHz. The bootloader does not work with our usual 7.37 MHz clock frequency.
+* On the STM32F1, you MUST adjust the clock frequency to by 8MHz. The bootloader does not work with our usual 7.37 MHz clock frequency. '''You must set the clock frequency back to 7.37MHz after programming the device.'''
 To access the bootloader you can perform these steps. They vary based on if you have a "Rev 02" board or a "Rev 03 or Later" board. The revision number is printed on the bottom side as part of the PCB part number (STM32F-03 is Rev -03 for example).

@@ Line 23: / Line 23: @@
 # Select the "Serial STM32F Programmer"
 #: [[File:arm_programmer.png]]
-# Mount a jumper between the H1/H2 pins on the UFO board:
+# Mount a jumper between the H1/H2 pins on the UFO board (again this is ONLY for the -02 rev, the -03 and newer revision DO NOT need this jumper as the ChipWhisperer will toggle the pin).
 #: [[File:samjumper.png|400px]]
 # Reset the ARM device either by pressing the reset button (newer UFO boards only), or by toggling power: