ChipWhisperer Wiki - User contributions [en]

CW308T-PSOC6

2018-11-30T10:18:46Z

Hakonp: /* Rev -01 Schematic */

{{Infobox cw308target
|name = CW308T-PSOC6
|image = PSOC6-target.png
|caption =
|Target Device = Cypress PSOC6
|Target Architecture = Cortex M0+, M4
|Hardware Crypto = Possible on M0+ core

|Design Files = [https://github.com/newaetech/chipwhisperer/tree/develop/hardware/victims/cw308_ufo_target/psoc6 GITHub Link]

|Status = Beta
}}

== Supported Devices ==

The PSOC6 board supports several PSOC6 devices in the BGA-116 package. The devices have the same pinout. Various header jumpers can be set different positions to select appropriate power supply for the different power dominans of the device, and different measurements points. The devices in the following table shows two compatible devices:
{| class="wikitable"
!Cypress PSOC6 series
!Package
!Device
!Hardware AES
!TRNG
!Tested
!Process node
!Flash
!SRAM
!OTP
|-
|PSOC6
|BGA-116
|CY8C6347BZI-BLD53E
|Yes
|Yes
|Yes
|40 nm
|1MB
|288KB
|No
|-
|}
There are other flavors of the devices with the same pinout, which makes them compatible with this target board.

== Power supply ==
The device must be supplied with minimum 1V7, and maxiumum 3v6. The logic core uses 1v2.

=== Internal regulators ===
The device contains an internal regulator regulating the input voltage down to 1v2. This can however be bypassed by supplying a slightly higher voltage to the target board's 1v2 pin.

== Measuring power consumption ==
The target board contains headers which lets the hacker select where to measure. It is possible to select to measure power on the 3v3 input and the 1v2 input/decoupling on the core pin.

== Hardware cryptography ==
The PSOC6 devices have hardware cryptography with support for AES, 3DES, RSA, SHA-512, SHA-256 and ECC.

== Programming Connection ==
The target board supports using both JTAG and SWD for programming. An external programmer is needed, e.g. a SEGGER Jlink or a ST-Link.

== Example Projects ==
SimpleSerial builds for the PSOC6 devices using the PSOC Creator. This is an Eclipse based IDE with support for debugging, flashing and provides good support for various peripherals. The PSOC Creator-project is included in the repo.

Program the device using your preferred method. SEGGER JFlash is a great tool for that.
After this, you're ready to go - you can use the ChipWhisperer terminal to talk to your target. You might need to reset the target before you do anything else.

== Schematic ==

=== Rev -01 Schematic ===

The current revision of the target is -01. The following shows this schematic:

[[File:CW308T-PSOC6-01.png|200px]]

== Hardware ==
{{Template:Hardware}}

[[Category: CW308 Targets]]

CW308T-STM32X7

2018-11-29T17:39:04Z

Hakonp:

CW308T-PSOC6

2018-11-29T17:35:06Z

Hakonp: Created page with "{{Infobox cw308target |name = CW308T-PSOC6 |image = PSOC6-target.png |caption = |Target Device = Cypress PSOC6 |Tar..."

{{Infobox cw308target
|name = CW308T-PSOC6
|image = PSOC6-target.png
|caption =
|Target Device = Cypress PSOC6
|Target Architecture = Cortex M0+, M4
|Hardware Crypto = Possible on M0+ core

|Design Files = [https://github.com/newaetech/chipwhisperer/tree/develop/hardware/victims/cw308_ufo_target/psoc6 GITHub Link]

|Status = Beta
}}

== Supported Devices ==

The PSOC6 board supports several PSOC6 devices in the BGA-116 package. The devices have the same pinout. Various header jumpers can be set different positions to select appropriate power supply for the different power dominans of the device, and different measurements points. The devices in the following table shows two compatible devices:
{| class="wikitable"
!Cypress PSOC6 series
!Package
!Device
!Hardware AES
!TRNG
!Tested
!Process node
!Flash
!SRAM
!OTP
|-
|PSOC6
|BGA-116
|CY8C6347BZI-BLD53E
|Yes
|Yes
|Yes
|40 nm
|1MB
|288KB
|No
|-
|}
There are other flavors of the devices with the same pinout, which makes them compatible with this target board.

== Power supply ==
The device must be supplied with minimum 1V7, and maxiumum 3v6. The logic core uses 1v2.

=== Internal regulators ===
The device contains an internal regulator regulating the input voltage down to 1v2. This can however be bypassed by supplying a slightly higher voltage to the target board's 1v2 pin.

== Measuring power consumption ==
The target board contains headers which lets the hacker select where to measure. It is possible to select to measure power on the 3v3 input and the 1v2 input/decoupling on the core pin.

== Hardware cryptography ==
The PSOC6 devices have hardware cryptography with support for AES, 3DES, RSA, SHA-512, SHA-256 and ECC.

== Programming Connection ==
The target board supports using both JTAG and SWD for programming. An external programmer is needed, e.g. a SEGGER Jlink or a ST-Link.

== Example Projects ==
SimpleSerial builds for the PSOC6 devices using the PSOC Creator. This is an Eclipse based IDE with support for debugging, flashing and provides good support for various peripherals. The PSOC Creator-project is included in the repo.

Program the device using your preferred method. SEGGER JFlash is a great tool for that.
After this, you're ready to go - you can use the ChipWhisperer terminal to talk to your target. You might need to reset the target before you do anything else.

== Schematic ==

=== Rev -01 Schematic ===

The current revision of the target is -01. The following shows this schematic:

[[File:CW308T-PSOC6-01.png|1100px]]

== Hardware ==
{{Template:Hardware}}

[[Category: CW308 Targets]]

File:CW308T-PSOC6-01.png

2018-11-29T17:33:30Z

Hakonp: Schematic for the PSOC6 target

Schematic for the PSOC6 target

File:PSOC6-target.png

2018-11-29T17:12:11Z

Hakonp: PSOC6 Target board

PSOC6 Target board

CW308T-STM32X7

2018-11-29T16:47:00Z

Hakonp: /* Measuring power consumption = */

CW308T-STM32X7

2018-11-29T16:46:21Z

Hakonp: /* Schematic */

CW308T-STM32X7

2018-11-29T16:43:19Z

Hakonp: /* Rev -01 Schematic */

CW308T-STM32X7

2018-11-29T16:42:29Z

Hakonp: /* Rev -01 Schematic */

CW308T-STM32X7

2018-11-29T16:42:06Z

Hakonp: /* Rev -01 Schematic */

File:CW308T-STM32X7-01.png

2018-11-29T16:39:45Z

Hakonp: Hakonp uploaded a new version of File:CW308T-STM32X7-01.png

Schematic for STM32X7 targets

File:CW308T-STM32X7-01.png

2018-11-29T16:39:33Z

Hakonp: Hakonp uploaded a new version of File:CW308T-STM32X7-01.png

Schematic for STM32X7 targets

CW308T-STM32X7

2018-11-29T16:36:29Z

Hakonp:

CW308T-STM32X7

2018-11-29T16:36:06Z

Hakonp:

File:CW308T-STM32X7-01.png

2018-11-29T16:35:53Z

Hakonp: Schematic for STM32X7 targets

Schematic for STM32X7 targets

CW308T-STM32X7

2018-11-29T16:05:30Z

Hakonp:

{{Infobox cw308target
|name = CW308T-STM32X7
|image = STM32X7-target.png
|caption =
|Target Device = ST STM32F
|Target Architecture = Cortex M7, H7
|Hardware Crypto = Possible

|Design Files = [https://github.com/newaetech/chipwhisperer/tree/develop/hardware/victims/cw308_ufo_target/stm32x7 GITHub Link]

|Status = Beta
}}

== THIS IS CURRENTLY A DRAFT, FURTHER READING NOT ADVISED ==
== Supported Devices ==

The STM32X7 board supports several STM32X7 devices in the UFBGA-176 package. The devices have the same pinout. Various header jumpers can be set different positions to select appropriate power supply for the different power dominans of the device, and different measurements points. The devices in the following table shows two compatible devices:
{| class="wikitable"
!STM32X7 Series
!Package
!Device
!Hardware AES
!TRNG
!Tested
!Process node
!Flash
!SRAM
!OTP
|-
|F7
|UFBGA-176
|STM32F746IEK6
|No
|Yes
|Yes
|90 nm
|1MB
|320KB
|1KB
|-
|H7
|UFBGA-176
|STM32H743IIK6
|No
|Yes
|Yes
|40 nm
|1MB
|320KB
|1KB
|-
|}
There are other flavors of the devices with the same pinout, which makes them compatible with this target board. E.g.

== Power supply ==
The device must be supplied 3v3, since the device's I/O logic uses 3v3. The logic core uses 1v2.

=== Internal regulators ===
The device contains an internal regulator regulating the input voltage down to 1v2. This can however be bypassed by supplying a slightly higher voltage to the target board's 1v2 pin.

== Measuring power consumption ===
The target board contains headers which lets the hacker select where to measure. It is possible to select to measure power on the 3v3 input and the 1v2 input/decoupling.

== Hardware AES ==

The STM32F21x, and STM32F41x/43x have hardware crypto modules (AES, DES, TDES) along with hardware hash (SHA1, MD5). Hardware crypto for the STM32F4 has been integrated into the Hal build system on the develop branch. To use the hardware crypto, call HW_AES128_Init() at the beginning of your program. You can update the key with HW_AES128_LoadKey(), encrypt plaintext with HW_AES128_Enc(), and decrypt data with HW_AES128_Dec().

== CAN Connection ==

A 6-pin header is present for devices which have CAN hardware support (not all devices have this). A CANoodler can be plugged in to provide the physical transceiver. This header is not normally mounted, unless the board is part of an 'automotive bundle'. The header is left unmounted as it can impede sweeping a probe over the surface of the chip.

== Programming Connection ==

=== ChipWhisperer Programmer via Bootloader ===

See further down this wiki page for details.

=== JTAG Programmer ===

The 20-pin JTAG port (J6 on CW308 Board) can be used with the [https://www.digikey.com/product-detail/en/stmicroelectronics/ST-LINK-V2/497-10484-ND/2214535 ST-LINK/V2] which is a low-cost JTAG programmer.

It is also possible to use other JTAG programmers such as OpenOCD. The following command worked with an Olimex OpenOCD programmer and their [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/ OpenOCD for Windows] software:
<pre>
openocd
-f path/to/board/files/cw308.cfg
-c init
-c targets
-c "halt"
-c "flash write_image erase path/to/firmware.hex"
-c "verify_image path/to/firmware.hex"
-c "reset run"
-c shutdown
</pre>
where the contents of <code>cw308.cfg</code> are
<pre>
source [find interface/olimex-arm-usb-ocd-h.cfg]
source [find target/stm32f4x.cfg]
reset_config srst_only
</pre>

== Example Projects ==

SimpleSerial builds for each of the STM32Fx Devices. Each device is a separate HAL. These HAL modules have been copied from ST's HAL (not the CUBE) and greatly reduced in size by deleting unused files (such as headers for unused devices), and combining several C-source files into a single low-level C-file.

=== Building ST Example on Command Line ===
The regular firmware build process works with the STM32 devices. For example, to build `simpleserial-aes`, navigate to the folder `chipwhisperer\hardware\victims\firmware\simpleserial-aes` and run the following command on the command line:

<code>
make PLATFORM=CW308_STM32F0 CRYPTO_TARGET=TINYAES128C
</code>

If all goes well, this command will finish by printing the output file size and the platform:

[[File:Stm32-make.png]]

=== Programming via ChipWhisperer Bootloader ===

{{:CW308T-STM32F/ChipWhisperer_Bootloader}}

=== Running ST Example with ST-Link ===
If instead of using the bootloader, you want to use a ST-Link you can instead plug your programmer into the 20 pin JTAG connector (J6 on the UFO board):

[[File:Stm32-jtag.jpg|600px]]

Then, the details of this step will depend on your programmer. If you're using an ST-Link programmer, open the ST-Link utility and connect to the device:

[[File:Stm32-connect.png]]

Load your `.hex` file and program the device with the Program and Verify button:

[[File:Stm32-program.png]]

After this, you're ready to go - you can use the ChipWhisperer terminal to talk to your target. You might need to reset the target before you do anything else.

=== Building and Debugging via ST's System Workbench ===
It's also possible to work on the example projects using [http://www.st.com/en/development-tools/sw4stm32.html ST's System Workbench IDE]. This IDE also supports debugging, which is helpful for working out all the kinks in your firmware.

To build the ChipWhisperer examples in System Workbench:

1. Create a new Mcu project by going to ''File > New > C Project'' and selecting ''<nowiki/>'<nowiki/>''Ac6 STM32 MCU Project'''.'' When you get to Target Configuration, click the Mcu tab and select the microcontroller that you want to target:

[[File:STM32 New Project.PNG|400px]]

[[File:STM32 MCU-Selection.PNG|400px]]

2. Link the external files into the project. To do this, under ''File > Import'', select ''File System''. In the `chipwhisperer\hardware\victims\firmware` directory, select all of the relevant files and folders (Makefile in base folder, Makefile in HAL folder, STM32Fx HAL folder).:

[[File:STM32 Import.PNG|400px]]

3. Set up the build command. In ''File > Properties'', go to ''C/C++ Build > Behavior'' and remove 'all''<nowiki/>''' from 'Build' and deselect 'Enable parallel build'. Next, click the ''Builder Settings'' tab and deselect 'Use default build command' and 'Generate Makefiles Automatically'. Enter the command you would normally enter on the command line and change 'Build directory' to the folder you want to build in:

[[File:STM32 Behaviour.PNG|400px]]

[[File:STM32 Build-Settings.PNG|400px]]

4. Build the project and confirm that the build works from the output in the IDE console.

Then, if you want to set up debugging:

1. Go to ''in File > Properties'' select Run/Debug Settings and create a new debug configuration. Under Debugger, click 'Show generator options...' and setup your Connection Setup based on your debugger. Change 'Reset Mode' to 'Software System reset':

[[File:STM32 Debugging.PNG|400px]]

2. Click Apply and enter debugging mode.

'''Caveat''': the I/O register map in the debugger appears to use the last known device (ie: if you debugged an STM32F4 project before your Makefile project, it sticks with F4's registers). Check that the registers' addresses are correct before you trust them!

== Schematic ==
The following variants are possible, see the table above for SRAM/FLASH/HW-Crypto status:
{| class="wikitable"
!Variant
!U1
!R3 (VCC-Shunt)
!R4 (Clock)
|-
|F0
|STM32F071RBT6
|33-ohm
|120-ohm
|-
|F1
|STM32F100RBT6
|22-ohm
|51-ohm
|-
|F2HWC
|STM32F215RET6
|10-ohm
|51-ohm
|-
|F3
|STM32F303RCT7
|12-ohm
|51-ohm
|-
|F4
|STM32F405RGT6
|10-ohm
|51-ohm
|-
|F4HWC
|STM32F415RGT6
|10-ohm
|51-ohm
|}

=== Rev -03 Schematic ===

The current revision of the target is -03. The following shows this schematic:

[[File:CW308T_STM32F_03.png|1100px]]

=== Rev -02 Schematic ===

The original board sold was the -02 revision. The revision is part of the part number, for example these boards will be marked STM32F-02. The -02 revision also does not have the CAN connector:
[[File:cw308_stm32f.jpg|400px]]

[[File:CW308T_STM32F_02.png|1100px]]

== Hardware ==
{{Template:Hardware}}

[[Category: CW308 Targets]]

CW308T-STM32X7

2018-11-28T17:31:18Z

Hakonp:

{{Infobox cw308target
|name = CW308T-STM32X7
|image = STM32X7-target.png
|caption =
|Target Device = ST STM32F
|Target Architecture = Cortex M7, H7
|Hardware Crypto = Possible

|Design Files = [https://github.com/newaetech/chipwhisperer/tree/develop/hardware/victims/cw308_ufo_target/stm32x7 GITHub Link]

|Status = Beta
}}

== THIS IS CURRENTLY A DRAFT, FURTHER READING NOT ADVISED ==
== Supported Devices ==

The STM32X7 board supports several STM32X7 devices in the UFBGA-176 package. Various header jumpers can be set different positions to select appropriate power supply for the different power domians of the device, and different measurements points. The following table summarizes examples of suitable devices:
{| class="wikitable"
!STM32X7 Series
!Package
!Device
!Hardware AES
!Tested
!Jumper
!Flash
!SRAM
|-
|F7
|UFBGA-176
|STM32F746IEK6
|No
|Yes
|B
|128KB
|16KB
|-
|F7
|UFBGA-176
|STM32F746IEK6
|No
|Yes
|B
|128KB
|16KB
|-
|}

=== VCC-Int Supply ===
Several devices (F2, F4) have internal core voltage regulators. By default the CW308 board attempts to provide power for these pins, but the voltage may not be high enough to cause the internal regulator to disable itself. In this case you can use the VADJ regulator to ensure the internal regulator is disabled. See [[Targets with Internal Regulators]] for details.

=== Pin-outs across TQFP Devices ===

The following shows differences in pinouts between three groups of devices. The left-most is the STM32F051RB, which uses the same 3.3V VCORE as the STM32F1/F3. It has fewer VCC pins, so the I/O occupying that are VCC/GND pins on the STM32F1 (such as PF6/PF7) are tied to GND/VCC. The right-most part is the pinout of the STM32F2/F4. It has an internal regulator, where the VCAP pins are the output of this regulator (and input to the internal core logic).

[[File:power_diffstm32.png|800px]]

Note for the devices with a 3.3V VCORE, you should not mount decoupling capacitors C5/C6/C7/C8. You will still get some leakage with those capacitors mounted, but a stronger signal is present without them.

== Hardware AES ==

The STM32F21x, and STM32F41x/43x have hardware crypto modules (AES, DES, TDES) along with hardware hash (SHA1, MD5). Hardware crypto for the STM32F4 has been integrated into the Hal build system on the develop branch. To use the hardware crypto, call HW_AES128_Init() at the beginning of your program. You can update the key with HW_AES128_LoadKey(), encrypt plaintext with HW_AES128_Enc(), and decrypt data with HW_AES128_Dec().

== CAN Connection ==

A 6-pin header is present for devices which have CAN hardware support (not all devices have this). A CANoodler can be plugged in to provide the physical transceiver. This header is not normally mounted, unless the board is part of an 'automotive bundle'. The header is left unmounted as it can impede sweeping a probe over the surface of the chip.

== Programming Connection ==

=== ChipWhisperer Programmer via Bootloader ===

See further down this wiki page for details.

=== JTAG Programmer ===

The 20-pin JTAG port (J6 on CW308 Board) can be used with the [https://www.digikey.com/product-detail/en/stmicroelectronics/ST-LINK-V2/497-10484-ND/2214535 ST-LINK/V2] which is a low-cost JTAG programmer.

It is also possible to use other JTAG programmers such as OpenOCD. The following command worked with an Olimex OpenOCD programmer and their [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/ OpenOCD for Windows] software:
<pre>
openocd
-f path/to/board/files/cw308.cfg
-c init
-c targets
-c "halt"
-c "flash write_image erase path/to/firmware.hex"
-c "verify_image path/to/firmware.hex"
-c "reset run"
-c shutdown
</pre>
where the contents of <code>cw308.cfg</code> are
<pre>
source [find interface/olimex-arm-usb-ocd-h.cfg]
source [find target/stm32f4x.cfg]
reset_config srst_only
</pre>

== Example Projects ==

SimpleSerial builds for each of the STM32Fx Devices. Each device is a separate HAL. These HAL modules have been copied from ST's HAL (not the CUBE) and greatly reduced in size by deleting unused files (such as headers for unused devices), and combining several C-source files into a single low-level C-file.

=== Building ST Example on Command Line ===
The regular firmware build process works with the STM32 devices. For example, to build `simpleserial-aes`, navigate to the folder `chipwhisperer\hardware\victims\firmware\simpleserial-aes` and run the following command on the command line:

<code>
make PLATFORM=CW308_STM32F0 CRYPTO_TARGET=TINYAES128C
</code>

If all goes well, this command will finish by printing the output file size and the platform:

[[File:Stm32-make.png]]

=== Programming via ChipWhisperer Bootloader ===

{{:CW308T-STM32F/ChipWhisperer_Bootloader}}

=== Running ST Example with ST-Link ===
If instead of using the bootloader, you want to use a ST-Link you can instead plug your programmer into the 20 pin JTAG connector (J6 on the UFO board):

[[File:Stm32-jtag.jpg|600px]]

Then, the details of this step will depend on your programmer. If you're using an ST-Link programmer, open the ST-Link utility and connect to the device:

[[File:Stm32-connect.png]]

Load your `.hex` file and program the device with the Program and Verify button:

[[File:Stm32-program.png]]

After this, you're ready to go - you can use the ChipWhisperer terminal to talk to your target. You might need to reset the target before you do anything else.

=== Building and Debugging via ST's System Workbench ===
It's also possible to work on the example projects using [http://www.st.com/en/development-tools/sw4stm32.html ST's System Workbench IDE]. This IDE also supports debugging, which is helpful for working out all the kinks in your firmware.

To build the ChipWhisperer examples in System Workbench:

1. Create a new Mcu project by going to ''File > New > C Project'' and selecting ''<nowiki/>'<nowiki/>''Ac6 STM32 MCU Project'''.'' When you get to Target Configuration, click the Mcu tab and select the microcontroller that you want to target:

[[File:STM32 New Project.PNG|400px]]

[[File:STM32 MCU-Selection.PNG|400px]]

2. Link the external files into the project. To do this, under ''File > Import'', select ''File System''. In the `chipwhisperer\hardware\victims\firmware` directory, select all of the relevant files and folders (Makefile in base folder, Makefile in HAL folder, STM32Fx HAL folder).:

[[File:STM32 Import.PNG|400px]]

3. Set up the build command. In ''File > Properties'', go to ''C/C++ Build > Behavior'' and remove 'all''<nowiki/>''' from 'Build' and deselect 'Enable parallel build'. Next, click the ''Builder Settings'' tab and deselect 'Use default build command' and 'Generate Makefiles Automatically'. Enter the command you would normally enter on the command line and change 'Build directory' to the folder you want to build in:

[[File:STM32 Behaviour.PNG|400px]]

[[File:STM32 Build-Settings.PNG|400px]]

4. Build the project and confirm that the build works from the output in the IDE console.

Then, if you want to set up debugging:

1. Go to ''in File > Properties'' select Run/Debug Settings and create a new debug configuration. Under Debugger, click 'Show generator options...' and setup your Connection Setup based on your debugger. Change 'Reset Mode' to 'Software System reset':

[[File:STM32 Debugging.PNG|400px]]

2. Click Apply and enter debugging mode.

'''Caveat''': the I/O register map in the debugger appears to use the last known device (ie: if you debugged an STM32F4 project before your Makefile project, it sticks with F4's registers). Check that the registers' addresses are correct before you trust them!

== Schematic ==
The following variants are possible, see the table above for SRAM/FLASH/HW-Crypto status:
{| class="wikitable"
!Variant
!U1
!R3 (VCC-Shunt)
!R4 (Clock)
|-
|F0
|STM32F071RBT6
|33-ohm
|120-ohm
|-
|F1
|STM32F100RBT6
|22-ohm
|51-ohm
|-
|F2HWC
|STM32F215RET6
|10-ohm
|51-ohm
|-
|F3
|STM32F303RCT7
|12-ohm
|51-ohm
|-
|F4
|STM32F405RGT6
|10-ohm
|51-ohm
|-
|F4HWC
|STM32F415RGT6
|10-ohm
|51-ohm
|}

=== Rev -03 Schematic ===

The current revision of the target is -03. The following shows this schematic:

[[File:CW308T_STM32F_03.png|1100px]]

=== Rev -02 Schematic ===

The original board sold was the -02 revision. The revision is part of the part number, for example these boards will be marked STM32F-02. The -02 revision also does not have the CAN connector:
[[File:cw308_stm32f.jpg|400px]]

[[File:CW308T_STM32F_02.png|1100px]]

== Hardware ==
{{Template:Hardware}}

[[Category: CW308 Targets]]

CW308T-STM32X7

2018-11-28T17:30:52Z

Hakonp: Start draft for STM32X7 target board

{{Infobox cw308target
|name = CW308T-STM32X7
|image = STM32X7-target.jpg
|caption =
|Target Device = ST STM32F
|Target Architecture = Cortex M7, H7
|Hardware Crypto = Possible

|Design Files = [https://github.com/newaetech/chipwhisperer/tree/develop/hardware/victims/cw308_ufo_target/stm32x7 GITHub Link]

|Status = Beta
}}

== THIS IS CURRENTLY A DRAFT, FURTHER READING NOT ADVISED ==
== Supported Devices ==

The STM32X7 board supports several STM32X7 devices in the UFBGA-176 package. Various header jumpers can be set different positions to select appropriate power supply for the different power domians of the device, and different measurements points. The following table summarizes examples of suitable devices:
{| class="wikitable"
!STM32X7 Series
!Package
!Device
!Hardware AES
!Tested
!Jumper
!Flash
!SRAM
|-
|F7
|UFBGA-176
|STM32F746IEK6
|No
|Yes
|B
|128KB
|16KB
|-
|F7
|UFBGA-176
|STM32F746IEK6
|No
|Yes
|B
|128KB
|16KB
|-
|}

=== VCC-Int Supply ===
Several devices (F2, F4) have internal core voltage regulators. By default the CW308 board attempts to provide power for these pins, but the voltage may not be high enough to cause the internal regulator to disable itself. In this case you can use the VADJ regulator to ensure the internal regulator is disabled. See [[Targets with Internal Regulators]] for details.

=== Pin-outs across TQFP Devices ===

The following shows differences in pinouts between three groups of devices. The left-most is the STM32F051RB, which uses the same 3.3V VCORE as the STM32F1/F3. It has fewer VCC pins, so the I/O occupying that are VCC/GND pins on the STM32F1 (such as PF6/PF7) are tied to GND/VCC. The right-most part is the pinout of the STM32F2/F4. It has an internal regulator, where the VCAP pins are the output of this regulator (and input to the internal core logic).

[[File:power_diffstm32.png|800px]]

Note for the devices with a 3.3V VCORE, you should not mount decoupling capacitors C5/C6/C7/C8. You will still get some leakage with those capacitors mounted, but a stronger signal is present without them.

== Hardware AES ==

The STM32F21x, and STM32F41x/43x have hardware crypto modules (AES, DES, TDES) along with hardware hash (SHA1, MD5). Hardware crypto for the STM32F4 has been integrated into the Hal build system on the develop branch. To use the hardware crypto, call HW_AES128_Init() at the beginning of your program. You can update the key with HW_AES128_LoadKey(), encrypt plaintext with HW_AES128_Enc(), and decrypt data with HW_AES128_Dec().

== CAN Connection ==

A 6-pin header is present for devices which have CAN hardware support (not all devices have this). A CANoodler can be plugged in to provide the physical transceiver. This header is not normally mounted, unless the board is part of an 'automotive bundle'. The header is left unmounted as it can impede sweeping a probe over the surface of the chip.

== Programming Connection ==

=== ChipWhisperer Programmer via Bootloader ===

See further down this wiki page for details.

=== JTAG Programmer ===

The 20-pin JTAG port (J6 on CW308 Board) can be used with the [https://www.digikey.com/product-detail/en/stmicroelectronics/ST-LINK-V2/497-10484-ND/2214535 ST-LINK/V2] which is a low-cost JTAG programmer.

It is also possible to use other JTAG programmers such as OpenOCD. The following command worked with an Olimex OpenOCD programmer and their [https://www.olimex.com/Products/ARM/JTAG/ARM-USB-OCD-H/ OpenOCD for Windows] software:
<pre>
openocd
-f path/to/board/files/cw308.cfg
-c init
-c targets
-c "halt"
-c "flash write_image erase path/to/firmware.hex"
-c "verify_image path/to/firmware.hex"
-c "reset run"
-c shutdown
</pre>
where the contents of <code>cw308.cfg</code> are
<pre>
source [find interface/olimex-arm-usb-ocd-h.cfg]
source [find target/stm32f4x.cfg]
reset_config srst_only
</pre>

== Example Projects ==

SimpleSerial builds for each of the STM32Fx Devices. Each device is a separate HAL. These HAL modules have been copied from ST's HAL (not the CUBE) and greatly reduced in size by deleting unused files (such as headers for unused devices), and combining several C-source files into a single low-level C-file.

=== Building ST Example on Command Line ===
The regular firmware build process works with the STM32 devices. For example, to build `simpleserial-aes`, navigate to the folder `chipwhisperer\hardware\victims\firmware\simpleserial-aes` and run the following command on the command line:

<code>
make PLATFORM=CW308_STM32F0 CRYPTO_TARGET=TINYAES128C
</code>

If all goes well, this command will finish by printing the output file size and the platform:

[[File:Stm32-make.png]]

=== Programming via ChipWhisperer Bootloader ===

{{:CW308T-STM32F/ChipWhisperer_Bootloader}}

=== Running ST Example with ST-Link ===
If instead of using the bootloader, you want to use a ST-Link you can instead plug your programmer into the 20 pin JTAG connector (J6 on the UFO board):

[[File:Stm32-jtag.jpg|600px]]

Then, the details of this step will depend on your programmer. If you're using an ST-Link programmer, open the ST-Link utility and connect to the device:

[[File:Stm32-connect.png]]

Load your `.hex` file and program the device with the Program and Verify button:

[[File:Stm32-program.png]]

After this, you're ready to go - you can use the ChipWhisperer terminal to talk to your target. You might need to reset the target before you do anything else.

=== Building and Debugging via ST's System Workbench ===
It's also possible to work on the example projects using [http://www.st.com/en/development-tools/sw4stm32.html ST's System Workbench IDE]. This IDE also supports debugging, which is helpful for working out all the kinks in your firmware.

To build the ChipWhisperer examples in System Workbench:

1. Create a new Mcu project by going to ''File > New > C Project'' and selecting ''<nowiki/>'<nowiki/>''Ac6 STM32 MCU Project'''.'' When you get to Target Configuration, click the Mcu tab and select the microcontroller that you want to target:

[[File:STM32 New Project.PNG|400px]]

[[File:STM32 MCU-Selection.PNG|400px]]

2. Link the external files into the project. To do this, under ''File > Import'', select ''File System''. In the `chipwhisperer\hardware\victims\firmware` directory, select all of the relevant files and folders (Makefile in base folder, Makefile in HAL folder, STM32Fx HAL folder).:

[[File:STM32 Import.PNG|400px]]

3. Set up the build command. In ''File > Properties'', go to ''C/C++ Build > Behavior'' and remove 'all''<nowiki/>''' from 'Build' and deselect 'Enable parallel build'. Next, click the ''Builder Settings'' tab and deselect 'Use default build command' and 'Generate Makefiles Automatically'. Enter the command you would normally enter on the command line and change 'Build directory' to the folder you want to build in:

[[File:STM32 Behaviour.PNG|400px]]

[[File:STM32 Build-Settings.PNG|400px]]

4. Build the project and confirm that the build works from the output in the IDE console.

Then, if you want to set up debugging:

1. Go to ''in File > Properties'' select Run/Debug Settings and create a new debug configuration. Under Debugger, click 'Show generator options...' and setup your Connection Setup based on your debugger. Change 'Reset Mode' to 'Software System reset':

[[File:STM32 Debugging.PNG|400px]]

2. Click Apply and enter debugging mode.

'''Caveat''': the I/O register map in the debugger appears to use the last known device (ie: if you debugged an STM32F4 project before your Makefile project, it sticks with F4's registers). Check that the registers' addresses are correct before you trust them!

== Schematic ==
The following variants are possible, see the table above for SRAM/FLASH/HW-Crypto status:
{| class="wikitable"
!Variant
!U1
!R3 (VCC-Shunt)
!R4 (Clock)
|-
|F0
|STM32F071RBT6
|33-ohm
|120-ohm
|-
|F1
|STM32F100RBT6
|22-ohm
|51-ohm
|-
|F2HWC
|STM32F215RET6
|10-ohm
|51-ohm
|-
|F3
|STM32F303RCT7
|12-ohm
|51-ohm
|-
|F4
|STM32F405RGT6
|10-ohm
|51-ohm
|-
|F4HWC
|STM32F415RGT6
|10-ohm
|51-ohm
|}

=== Rev -03 Schematic ===

The current revision of the target is -03. The following shows this schematic:

[[File:CW308T_STM32F_03.png|1100px]]

=== Rev -02 Schematic ===

The original board sold was the -02 revision. The revision is part of the part number, for example these boards will be marked STM32F-02. The -02 revision also does not have the CAN connector:
[[File:cw308_stm32f.jpg|400px]]

[[File:CW308T_STM32F_02.png|1100px]]

== Hardware ==
{{Template:Hardware}}

[[Category: CW308 Targets]]

File:STM32X7-target.png

2018-11-28T17:30:44Z

Hakonp: STM32X7 target pcb for CW308 UFO

STM32X7 target pcb for CW308 UFO