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

2 Yocto Integration (TI SDK Wrynose)

The steps in this section assume that the user has a working TI SDK Yocto build environment for AM62Lx already set up. If you have not done this yet, follow the Building the SDK with Yocto guide first.

The expected directory layout after setup:

tisdk/
├── sources/          ← all layers live here
└── build/
    └── conf/
        ├── bblayers.conf ← add extra layers here
        └── local.conf    ← add IMAGE_INSTALL / DISTRO_FEATURES / BBMASK here
All path references below use tisdk/ as the root.

Build prerequisite: Before following any steps in this document, you must have sourced the Yocto build environment and completed at least one full image build (Step B — Section 2.6). These steps are prerequisites and must be done once:

cd tisdk/build
. conf/setenv
MACHINE=am62lxx-evm bitbake tisdk-default-image

The environment source (. conf/setenv) must be re-run in every new terminal session before invoking bitbake or running any bitbake-based commands.