WolfSSL
/
wolfssl-examples
mirror of https://github.com/wolfSSL/wolfssl-examples.git
1
0
Fork 0
Code Issues Releases Wiki Activity
wolfssl-examples/stsafe
History
Emma Stensland 278736016e F-2115 F-3693 F-3890 F-3895 F-5608 F-5609 F-5613 F-6290 F-6537 F-6538: fix RPi-Pico, TOPPERS, PSK, lwIP, Mynewt, uTasker, wolfIP, and STSafe examples issues 2026-07-13 17:29:28 -06:00
..
platform F-2115 F-3693 F-3890 F-3895 F-5608 F-5609 F-5613 F-6290 F-6537 F-6538: fix RPi-Pico, TOPPERS, PSK, lwIP, Mynewt, uTasker, wolfIP, and STSafe examples issues 2026-07-13 17:29:28 -06:00
Makefile Improvements to Makefile and examples 2026-01-21 00:03:05 +00:00
README.md Added ECDHE 2026-01-15 20:03:41 +00:00
stsafe_test.c Implemented all required SDK cryptographic wrappers. 2026-01-06 18:07:38 +00:00
user_settings.h Improvements to Makefile and examples 2026-01-21 00:03:05 +00:00
wolfssl_stsafe_full_test.c Fix for ECDHE 2026-01-22 22:49:08 +00:00
wolfssl_stsafe_test.c Improvements to Makefile and examples 2026-01-21 00:03:05 +00:00

README.md

wolfSSL STSAFE-A120 Test Suite

Test harness for wolfSSL integration with ST STSAFE-A120 secure element on Raspberry Pi 5.

Hardware Requirements

  • Raspberry Pi 5 (or compatible Linux system with I2C)
  • STSAFE-A120 secure element connected via I2C
  • I2C enabled on the system

Software Requirements

  • wolfSSL library (compiled with ECC, CMAC, SHA-384 support)
  • STSELib (ST Secure Element Library)
  • GCC compiler
  • Linux I2C development headers (libi2c-dev)

Quick Start

1. Enable I2C on Raspberry Pi

sudo raspi-config
# Navigate to: Interface Options -> I2C -> Enable

Reboot if prompted, then verify the STSAFE device is detected:

sudo i2cdetect -y 1
# STSAFE should appear at address 0x20

Optional: Allow non-root I2C access:

sudo usermod -a -G i2c $USER
# Logout and login again

2. Build wolfSSL

cd ~/wolfssl
./configure --enable-cryptocb --enable-ecc --enable-cmac --enable-sha384
make

3. Clone STSELib

git clone https://github.com/STMicroelectronics/STSELib.git ~/STSELib

4. Build and Run Tests

cd ~/wolfssl-examples/stsafe

# Build all test executables
make

# Run all tests
make test-all

Test Suites

Basic STSELib Tests (stsafe_test)

Tests core STSAFE-A120 functionality:

  • Echo command (I2C communication)
  • Random number generation
  • ECC P-256 key generation
  • ECDSA P-256 signing
  • ECC P-384 key generation
make && ./stsafe_test

wolfSSL Crypto Callback Tests (wolfssl_stsafe_test)

Tests wolfSSL crypto callbacks with STSAFE:

  • RNG with STSAFE-A120
  • ECC P-256/P-384 key generation via crypto callback
  • ECDSA P-256/P-384 sign/verify
  • ECDHE P-256 ephemeral key generation
  • ECDHE P-256 shared secret computation
make wolfssl && ./wolfssl_stsafe_test

Full Integration Tests (wolfssl_stsafe_full_test)

Comprehensive tests with benchmarks:

  • RNG benchmark
  • ECDSA P-256 benchmark (keygen, sign, verify timing)
  • ECDH P-256 key exchange (uses ECDHE ephemeral keys)
  • Multiple sequential operations
make wolfssl-full && ./wolfssl_stsafe_full_test

Build Targets

Target Description
make Build all test executables
make test-all Build and run all tests
make basic Build without wolfSSL (basic I2C tests only)
make clean Clean build artifacts
make info Show configuration

Expected Output

================================================
STSAFE-A120 Test Suite for wolfSSL Integration
================================================

Initializing STSAFE handler...
STSAFE-A120 initialized successfully.

Test: Echo Command
  Echo response matches!
[PASS] Echo command

Test: Random Number Generation
  Random data: A1 B2 C3 D4 ...
[PASS] Random number generation

Test: ECC Key Generation (P-256)
  Public Key X: 12345678...
  Public Key Y: ABCDEF01...
[PASS] ECC P-256 key generation

...

================================================
Test Summary: 5 passed, 0 failed
================================================

Performance Results (Raspberry Pi 5)

Operation Time Throughput
RNG (256 bytes) <1 ms ~9 MB/s
ECC P-256 KeyGen ~40 ms 25 ops/sec
ECDSA P-256 Sign ~51 ms 19.5 ops/sec
ECDSA P-256 Verify ~79 ms 12.7 ops/sec
ECDHE P-256 KeyGen ~42 ms ~24 ops/sec
ECDHE P-256 Shared Secret ~38 ms ~26 ops/sec

Directory Structure

stsafe/
├── Makefile                          # Build configuration
├── README.md                         # This file
├── user_settings.h                   # wolfSSL configuration
├── stsafe_test.c                     # STSELib basic tests
├── wolfssl_stsafe_test.c             # wolfSSL crypto callback tests
├── wolfssl_stsafe_full_test.c        # Full integration tests with benchmarks
└── platform/
    ├── stse_conf.h                   # STSELib configuration
    ├── stse_platform_generic.h       # Platform type definitions
    ├── stse_platform_linux.c         # Linux I2C platform implementation
    └── stse_platform_crypto_wolfssl.c # wolfSSL crypto for STSELib

Environment Variables

Default paths assume ~/wolfssl and ~/STSELib. Override if needed:

export WOLFSSL_DIR=/path/to/wolfssl
export STSELIB_DIR=/path/to/STSELib

Troubleshooting

Error 0x0104 (STSE_PLATFORM_BUS_ERR)

I2C communication error. Check:

  1. I2C is enabled: ls /dev/i2c*
  2. Device detected: sudo i2cdetect -y 1 (should show 20)
  3. Wiring connections are secure

Build errors

Ensure wolfSSL is built with required features:

./configure --enable-cryptocb --enable-ecc --enable-cmac --enable-sha384

References