Running STM32F2 with CWHusky

1

Hello,

I’ve to say I’m pretty new to CWHusky hardware and operating it. I’m in a need to perform SCA testing on STM32F2. I’ve assembled the hardware (STM32F2 target + CW308→CW312 adapter board + CW313 target board support). I manged to connect it to CWHusky and ensure that it runs alright - that mean, I can implement some program, flash it to the board and see over UART that it works.

It seems I also can collect traces by triggering GPIO12 up/down.

scope.gain.gain = 45                # Increase gain (range typically 0-45)
scope.adc.samples = 8000            # Number of samples to capture (10000 = \~1.36 ms at 7.37 MHz)
scope.clock.clkgen_freq = 7370000   # 7.37 MHz
scope.adc.offset = 0                # Center the signal
scope.trigger.triggers = 'tio4'     # Use TIO4 for trigger
scope.io.tio1 = 'serial_rx'
scope.io.tio2 = 'serial_tx'

scope.io.target_pwr = 0
time.sleep(BOOT_WAIT)
scope.io.target_pwr = 1
time.sleep(BOOT_WAIT)

I wanted do ask 2 questions:

  1. Do I need to do something more to setup the target correctly? I understand that STM32F2 is not a “default” target that CWHusky is delivered with and hence I was wondering if CWHusky requires any additional configuration. I’m only interested in collecting power traces for DPA analysis on cryptographic schemes?
  2. What would be the best way to validate a setup? I’ve noticed that there is a lab called Lab 2_1B - Power Analysis for Password Bypass (MAIN).ipynb. Would running that excersise successfully validate correctness of my setup?
  3. Is it possible to configure the target to run faster than 7MhZ (but still be able to collect high quality traces)?

image
image1920×1427 552 KB

Any feedback on that will be more than welcome.

Kind regards,
HC

2

The STM32 is well supported by all ChipWhisperer hardware. The STM32F3 was our standard target for a long time; it was replaced by the SAM4S when Husky was released due to supply chain issues. But Husky support for the STM32 family is no different than CW-LIte’s.

Most notebooks will work well on this target; simply set PLATFORM accordingly (i.e. CW308_STM32F2).

In some cases you’ll need to make some tweaks (e.g. glitching parameters) but that’s part of the fun and learning.

1 Like