[dgarske]

Description

The V2 PKA clobbers RAM[PKA_ECC_SCALAR_MUL_IN_OP_NB_BITS] during the operation, so HAL_PKA_ECCMul_GetResult() recomputing the result length from that slot read zero, copied nothing out, and left wc_ecc_mulmod_ex2() handing back the caller's own input point - public keys derived from a private key were wrong, so signatures did not verify against them and ECDH mismatched, surfacing as ECIES and PKCS7 KARI failures rather than as an ECC fault; HAL_PKA_ECCMul() now saves the modulus size on the handle as the V2 HAL does, and V1 still reads it from RAM. Separately the V2 PKA draws on the RNG during its init self-check, so SR.INITOK never asserted from cold and every operation failed with WC_HW_E, which HAL_PKA_Init() now avoids by bringing the RNG up first. Also fixed: INT_MAX undeclared on an STM32 USE_FAST_MATH build, and wolfcrypt_test failing to compile with NO_PKCS7_ENCRYPTED_DATA.

Only reachable without WOLFSSL_HAVE_SP_ECC, since with SP math key generation and ECDH stay in software and never reach the PKA.

ZD 22578

Testing

Validated on NUCLEO-U545RE-Q and B-U585I-IOT02A against the NIST P-256 CAVP d -> Q vector and the full wolfcrypt_test, and regressed on NUCLEO-U385RG-Q (V2 PKA) and STM32L562E-DK (V1 PKA).

Checklist

• added tests
• updated/added doxygen
• updated appropriate READMEs
• Updated manual and documentation

[github-actions]

MemBrowse Memory Report

No memory changes detected for:

• gcc-arm-cortex-m0plus
• gcc-arm-cortex-m3
• gcc-arm-cortex-m4
• gcc-arm-cortex-m4-baremetal
• gcc-arm-cortex-m4-crypto-only
• gcc-arm-cortex-m4-dtls13
• gcc-arm-cortex-m4-min-ecc
• gcc-arm-cortex-m4-openssl-compat
• gcc-arm-cortex-m4-pkcs7
• gcc-arm-cortex-m4-pq
• gcc-arm-cortex-m4-rsa-only
• gcc-arm-cortex-m4-sp-math
• gcc-arm-cortex-m4-tls12
• gcc-arm-cortex-m4-tls13
• gcc-arm-cortex-m7
• gcc-arm-cortex-m7-pq
• gcc-arm-cortex-m7-tls13
• linuxkm-pie
• stm32-sim-stm32h753