Changes

CW308T-STM32F

3,330 bytes removed, 19:34, 29 July 2020
Replaced content with "== Page Moved == See [https://rtfm.newae.com/Targets/UFO%20Targets/CW308T-STM32F/ NewAE RTFM Page] which is now built from the [https://github.com/newaetech/chipwhisperer..."
{{Infobox cw308target|name = CW308T-STM32F|image = cw308_stm32f.jpg|caption Page Moved = |Target Device = ST STM32F|Target Architecture = Cortex M0,M3,M4|Hardware Crypto = Possible|Purchase Hardware = |Design Files = [https://github.com/newaetech/chipwhisperer/tree/master/hardware/victims/cw308_ufo_target/stm32f GITHub Link]
See [https://wikirtfm.newae.com/Targets/UFO%20Targets/CW308T-STM32F OSH Park PCBs/ NewAE RTFM Page]which is now built from the [https://github.com/newaetech/chipwhisperer-target-cw308t GIT Repo].
|Supported Applications = [[SimpleSerial | Simple Serial Enc/Auth]]|Programmer = ST-LINK/V2|Status = Released}} == Supported Devices == The STM32F board supports several STM32F devices in the TQFP-64 package. Various solder jumpers need to bet set previous content on this wiki has been moved 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|-|F0|TQFP-64||||B*|-|F1|TQFP-64||||B|-|F2|TQFP-64||||A|-|F3|TQFP-64||||B|-|F4|TQFP-64|STM32F415RGT6|Yes|Yes|A|} <nowiki>*</nowiki> The F0 variant has a slightly different pinout, as has less VCC/GND pins and more I/O pins than other devices. The result is several I/O pins cannot be used as they are tied to VCC/GND. This will NOT affect regular usageabove link. See details below. === 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 wiki history if you can use the VADJ regulator would like 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 STM32F0, 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 view exact older versions of this regulator (and input to the internal core logic). [[File:power_diffstm32.png|800px]] == Hardware AES == The STM32F21x, and STM32F41x/43x have hardware crypto modules (AES, DES, TDES) along with hardware hash (SHA1, MD5). == Programming Connection == 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 == WARNING: The current example projects are built for the -01 rev of the PCB. The only change is the trigger pin has changed, you will need to modify the stm32f4 HAL file to reflect the trigger is now PA12 (-02 version) instead of PA11 (-01 version). == Schematic ==[[File:CW308T_STM32F_02page.png|1100px]]  [[Category: CW308 Targets]]
Approved_users, bureaucrat, administrator
1,956
edits