Initial implementation

[twcook86]

This adds support for the lpc55s69 hw puf to wolfCrypt (WOLFSSL_HWPUF && WOLFSSL_NXP_PUF). An effort has been made to be as compatible with the sw puf (WOLFSSL_PUF) implementation as possible.

Not all features of the hw puf are supported yet. Specifically, this initial implementation supports...

1. keys of size 16, 24, 32 bytes for use with aes
2. ability to pass keys directly on the hw bus to the aes engine, thus never being exposed in ram

Testing

Tested with new test functionality added to wolfcrypt/test/test.c

Checklist

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

[github-actions]

MemBrowse Memory Report

gcc-arm-cortex-m3

• FLASH: .text +8 B (+0.0%, 120,133 B / 262,144 B, total: 46% used)

gcc-arm-cortex-m4-openssl-compat

• FLASH: .rodata +40 B, .text +192 B (+0.0%, 763,124 B / 1,048,576 B, total: 73% used)

gcc-arm-cortex-m4-pq

• FLASH: .text +64 B (+0.0%, 275,736 B / 1,048,576 B, total: 26% used)

gcc-arm-cortex-m4-tls12

• FLASH: .text +64 B (+0.1%, 120,909 B / 262,144 B, total: 46% used)
  No memory changes detected for:
• gcc-arm-cortex-m0plus
• 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-pkcs7
• gcc-arm-cortex-m4-rsa-only
• gcc-arm-cortex-m4-sp-math
• gcc-arm-cortex-m4-tls13
• gcc-arm-cortex-m7
• gcc-arm-cortex-m7-pq
• gcc-arm-cortex-m7-tls13
• stm32-sim-stm32h753

[dgarske]

Shouldn't this entire file not be compiled when WOLFSSL_NXP_PUF is defined? Maybe add a !WOLFSSL_NXP_PUF around it? Also did you consider extending the crypto callbacks to support PUF? So have an init_ex with devId/heap and support registering a PUF handler for the NXP?