Changes

|image = STM32X7-target.jpgpng

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 domians dominans of the device, and different measurements points. The devices in the following table summarizes examples of suitable shows two compatible devices:

!JumperProcess node

|BYes|128KB90 nm|16KB1MB|320KB|1KB

|F7H7

|STM32F746IEK6STM32H743IIK6

|BYes|128KB40 nm|16KB1MB|320KB|1KB

=== VCC-Int Supply =Power supply ==Several devices (F2The device must be supplied 3v3, F4) have internal core voltage regulators. By default since 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 itselfdevice's I/O logic uses 3v3. In this case you can use the VADJ regulator to ensure the internal regulator is disabled. See [[Targets with Internal Regulators]] for detailsThe logic core uses 1v2.

=== Pin-outs across TQFP Devices 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 following shows differences in pinouts between three groups of devices. The left-most is the STM32F051RB, target board contains headers which uses lets the same 3.3V VCORE as the STM32F1/F3hacker select where to measure. It has fewer VCC pins, so the I/O occupying that are VCC/GND pins is possible to select to measure power on the STM32F1 (such as PF6/PF7) are tied to GND/VCC. The right-most part is 3v3 input and the pinout of the STM32F21v2 input/F4decoupling. VCAP1 and VCAP2 should be shorted, an only one shunt resistor should be used. It has an internal regulator, where seems that the VCAP pins are from the output of this regulator (and input to same power domain, namely the internal digital core logic)domain.

[[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 cryptography == 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 Some flavors of the STM32X7 supports hardware crypto, call HW_AES128_Init() at the beginning of your programcryptography . 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 The tested 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 above table do not normally mountedsupport hardware cryptography, unless hence there are no firmware which supports 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 chiphardware cryptography yet.

 === ChipWhisperer Programmer via Bootloader === See further down this wiki page for details. === JTAG Programmer === The 20-pin target board supports using both JTAG port (J6 on CW308 Board) can be used with the [https://wwwand SWD for programming.digikey.com/product-detail/en/stmicroelectronics/ST-LINK-V2/497-10484-ND/2214535 ST-LINK/V2] which is a low-cost JTAG An external programmer.  It is also possible to use other JTAG programmers such as OpenOCDneeded, e. The following command worked with an Olimex OpenOCD programmer and their [https://wwwg.olimex.com/Products/ARM/JTAG/ARMa SEGGER Jlink or a ST-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/stm32f4xLink.cfg]reset_config srst_only</pre>

=== STM32F7 ===SimpleSerial builds for each of the STM32Fx DevicesSTM32F7 devices using the ChipWhisperer build system. 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 . === STM32H7 ===SimpleSerial builds for unused the STM32H7 devices), and combining several Cusing Arm Keil uVision. This project could easily be ported to support the ChipWhisperer build system. The Keil-source files into a single low-level C-fileproject is also included in the repo. Keil IDE also supports debugging, which is helpful for working out all the kinks in your firmware.

make PLATFORM=CW308_STM32F0 CW308_STM32F7 CRYPTO_TARGET=TINYAES128C

If all goes well, this command will finish by printing Program 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 device 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-jtagpreferred method.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-programSEGGER JFlash is a great tool for that.png]] 

=== Rev -03 Schematic === The current revision of the target is -0301. 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_02CW308T-STM32X7-01.png|1100px200px]]