SDAA498 September   2026 AM62L

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Platform
  5. 2Yocto Integration (TI SDK Wrynose)
    1. 2.1 Layer Stack
    2. 2.2 OpenSSL 3.5 Native PQC: No Extra Steps Required
    3. 2.3 liboqs / oqs-provider Integration
    4. 2.4 Recovering From Build Errors
    5. 2.5 wolfSSL Integration
      1. 2.5.1 Choosing a Path
      2. 2.5.2 Step A1 — Option A: meta-wolfssl
      3. 2.5.3 Step A2 — Option B: meta-oe wolfssl (Library Only)
    6. 2.6 Step B — Build
    7. 2.7 Step C — OpenSSL Provider Configuration
  6. 3Performance Benchmarks
    1. 3.1 ML-KEM — All implementations
    2. 3.2 ML-DSA — All implementations
    3. 3.3 FrodoKEM (liboqs only)
    4. 3.4 Hybrid KEM — TLS overhead
    5. 3.5 armasm Impact on wolfSSL Performance
  7. 4NEON and HW Acceleration Analysis
    1. 4.1 Acceleration Status per Implementation
    2. 4.2 Recommendation by Algorithm
  8. 5Algorithm Availability Summary
  9. 6References

3.3 FrodoKEM (liboqs only)

oqs_speed_kem -d 3 FrodoKEM-640-AES
oqs_speed_kem -d 3 FrodoKEM-976-AES
oqs_speed_kem -d 3 FrodoKEM-1344-AES
Algorithm keygen/s encaps/s decaps/s Notes
FrodoKEM-640-AES310270278Hardware AES active
FrodoKEM-976-AES145120126Hardware AES active
FrodoKEM-1344-AES816767Hardware AES active

FrodoKEM is approximately 25 to 40 times slower than ML-KEM due to large matrix operations, but benefits directly from hardware AES (OQS_USE_ARM_AES_INSTRUCTIONS=ON).