It appears that the STM32WLxx FW 1.4 package includes a LoRaWAN stack that implements AES in software. Is there a technical reason that the AES accelerator in the STM32WLxx is not used?
I can imagine things like:
- AES hardware functionally uses more power, or increases latency waking from STOP2, than the Semtech implementation.
- AES hardware does not provide the functionality required by LoRaWAN (at first glance, this does not appear to be the case).
- It's just too organizationally difficult to fork the Semtech code to use the AES hardware, or there is some licensing wrinkle (I can't imagine such a thing).
If there's no reason not to use the AES hardware, I'd like to explore doing so.
