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

Performance Benchmarks

Note: Prerequisite packages for reproducing benchmarks:

The commands in this section require the following packages in IMAGE_INSTALL (see Section 2.3.2 and 2.5.2):

  • liboqs-tests → installs oqs_speed_kem , oqs_speed_sig to /usr/bin/
  • wolfcryptbenchmark → installs /usr/bin/wolfcryptbenchmark (through meta-wolfssl bbappend; triggers --enable-crypttests in the wolfssl build)

Without these packages, the binaries are not present on the rootfs. Installing the liboqs library and oqsprovider.so alone is not sufficient for running speed benchmarks.

All benchmarks run on AM62L3 EVM, Cortex-A53 at approximately 1.4GHz, Arago 2025.01. wolfSSL numbers use --enable-armasm (NEON Keccak + hardware AES/SHA-2 assembly active).

All benchmarks run on AM62L3 EVM, Cortex-A53 at approximately 1.4GHz, Arago 2025.01. wolfSSL numbers use --enable-armasm (NEON Keccak + hardware AES/SHA-2 assembly active).