|
|
| Line 1: |
Line 1: |
| − | {{Infobox cw308target
| + | == Page Moved == |
| − | |name = CW308T-STM32F
| + | |
| − | |image = STM32F3-Top_Rev03.jpg
| + | |
| − | |caption =
| + | |
| − | |Target Device = ST STM32F
| + | |
| − | |Target Architecture = Cortex M0,M3,M4
| + | |
| − | |Hardware Crypto = Possible
| + | |
| − | |Purchase Hardware = [http://store.newae.com/stm32f0-target-for-cw308-arm-cortex-m0-128kb-flash-8kb-sram/ Webstore, F0]
| + | |
| | | | |
| − | [http://store.newae.com/stm32f1-target-for-cw308-arm-cortex-m3-128kb-flash-8kb-sram/ Webstore, F1] | + | See [https://rtfm.newae.com/Targets/UFO%20Targets/CW308T-STM32F/ NewAE RTFM Page] which is now built from the [https://github.com/newaetech/chipwhisperer-target-cw308t GIT Repo]. |
| | | | |
| − | [http://store.newae.com/stm32f3-target-for-cw308-arm-cortex-m4-256kb-flash-40kb-sram/ Webstore, F3]
| + | The previous content on this wiki has been moved to the above link. See wiki history if you would like to view exact older versions of this page. |
| − | | + | |
| − | [http://store.newae.com/stm32f4-target-for-cw308-arm-cortex-m4-1mb-flash-192kb-sram/ Webstore, F4]
| + | |
| − | | + | |
| − | [http://store.newae.com/blank-pcb-stm32fx-cw308-target/ Webstore PCB]
| + | |
| − | |Design Files = [https://github.com/newaetech/chipwhisperer/tree/master/hardware/victims/cw308_ufo_target/stm32f GITHub Link]
| + | |
| − | | + | |
| − | [https://wiki.newae.com/CW308T-STM32F OSH Park PCBs]
| + | |
| − | | + | |
| − | |Supported Applications = [[SimpleSerial | Simple Serial Enc/Auth]]
| + | |
| − | |Programmer = ST-LINK/V2
| + | |
| − | |Status = Released
| + | |
| − | }}
| + | |
| − | | + | |
| − | {{Warningbox|ChipWisperer v5.1.3 before commit 3557 and arm-none-eabi-gcc before q2-2018 can produce non-working binaries for the STM32F3. The only fix is to update either ChipWhisperer or gcc}}
| + | |
| − | | + | |
| − | == Supported Devices ==
| + | |
| − | | + | |
| − | The STM32F board supports several STM32F devices in the TQFP-64 package. Various solder jumpers need to bet set to either the "A" or "B" position to select appropriate VCC supply for the different series. The following table summarizes examples of suitable devices:
| + | |
| − | {| class="wikitable"
| + | |
| − | !STM32F Series
| + | |
| − | !Package
| + | |
| − | !Device
| + | |
| − | !Hardware AES
| + | |
| − | !Tested
| + | |
| − | !Jumper
| + | |
| − | !Flash
| + | |
| − | !SRAM
| + | |
| − | !NAE P/N
| + | |
| − | |-
| + | |
| − | |F0
| + | |
| − | |TQFP-64
| + | |
| − | |STM32F071RBT6
| + | |
| − | |No
| + | |
| − | |Yes
| + | |
| − | |B
| + | |
| − | |128KB
| + | |
| − | |16KB
| + | |
| − | |NAE-CW308T-STM32F0
| + | |
| − | |-
| + | |
| − | |F1
| + | |
| − | |TQFP-64
| + | |
| − | |STM32F100RBT6B
| + | |
| − | |No
| + | |
| − | |Yes
| + | |
| − | |B
| + | |
| − | |128KB
| + | |
| − | |8KB
| + | |
| − | |NAE-CW308T-STM32F1
| + | |
| − | |-
| + | |
| − | |F2
| + | |
| − | |TQFP-64
| + | |
| − | |STM32F215RET6
| + | |
| − | |Yes
| + | |
| − | |Yes
| + | |
| − | |A
| + | |
| − | |512KB
| + | |
| − | |132KB
| + | |
| − | |NAE-CW308T-STM32F2HWC
| + | |
| − | |-
| + | |
| − | |F3
| + | |
| − | |TQFP-64
| + | |
| − | |STM32F303RCT7
| + | |
| − | |No
| + | |
| − | |Yes
| + | |
| − | |B
| + | |
| − | |256KB
| + | |
| − | |40KB
| + | |
| − | |NAE-CW308T-STM32F3
| + | |
| − | |-
| + | |
| − | |F4
| + | |
| − | |TQFP-64
| + | |
| − | |STM32F415RGT6
| + | |
| − | |Yes
| + | |
| − | |Yes
| + | |
| − | |A
| + | |
| − | |1MB
| + | |
| − | |192KB
| + | |
| − | |NAE-CW308T-STM32F4HWC
| + | |
| − | |-
| + | |
| − | |F4
| + | |
| − | |TQFP-64
| + | |
| − | |STM32F405RGT6
| + | |
| − | |No
| + | |
| − | |Yes
| + | |
| − | |A
| + | |
| − | |1MB
| + | |
| − | |192KB
| + | |
| − | |NAE-CW308T-STM32F4
| + | |
| − | |-
| + | |
| − | |L4
| + | |
| − | |TQFP-64
| + | |
| − | |STM32L443RCT6
| + | |
| − | |Yes
| + | |
| − | |Yes
| + | |
| − | |B
| + | |
| − | |256KB
| + | |
| − | |64KB
| + | |
| − | |NAE-CW308T-STM32L4 (this version has hardware crypto)
| + | |
| − | |-
| + | |
| − | |L5
| + | |
| − | |TQFP-64
| + | |
| − | |STM32L562RET6
| + | |
| − | |Yes
| + | |
| − | |Yes
| + | |
| − | |B
| + | |
| − | |512KB
| + | |
| − | |256KB
| + | |
| − | |NAE-CW308T-STM32L5HWC
| + | |
| − | |}
| + | |
| − | | + | |
| − | === 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.
| + | |
| − | | + | |
| − | Many example projects are available via Jupyter Notebooks: https://chipwhisperer.readthedocs.io/en/latest/tutorials.html. Note that all of these examples were created for the CWLITEARM (equivalent STM32F3) target. You will need to make changes based on which target you have to run the tutorials. For some tutorials, changing the PLATFORM variable in the first block to the one you're using is enough to get the tutorial working:
| + | |
| − | <syntaxhighlight lang=python>
| + | |
| − | SCOPETYPE = "OPENADC"
| + | |
| − | PLATFORM = "CW308_STM32F4" #For STM32F4 target, was originally "CWLITEARM"
| + | |
| − | </syntaxhighlight>
| + | |
| − | | + | |
| − | === 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]]
| + | |
| − | | + | |
| − | {{CollapsibleSection
| + | |
| − | |intro = === Programming via ChipWhisperer Bootloader ===
| + | |
| − | |content= CW308T-STM32F/ChipWhisperer_Bootloader}}
| + | |
| − | | + | |
| − | {{CollapsibleSection
| + | |
| − | |intro = === Running ST Example with ST-Link ===
| + | |
| − | |content= CW308T-STM32F/ST_Link}}
| + | |
| − | | + | |
| − | {{CollapsibleSection
| + | |
| − | |intro = === Building and Debugging via ST's System Workbench ===
| + | |
| − | |content= CW308T-STM32F/Debugging_with_ST_Link}}
| + | |
| − | | + | |
| − | == 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]]
| + | |
