AWS IoT middleware on S32K396

[Henrik-Wires]

We are looking into building an IoT like device with lwip, MbedTLS+HSE, MQTT, OTA update etc, and found that the AWS IoT middleware does all this and more. But appears this middleware only supports K344 and K358?

Is there anything that inherently stops the AWS libraries from working on K396? I do not mind porting what is needed as part of the application. But find it confusing that the AWS middleware bundles all of MbedTLS, HSE FW and a bit more.

[Henrik-Wires]

I will assume the reason mbedtls is embedded in the aws package is only because it has not been packaged as a S32DS package separately and that it was easier to include mbedtls in the aws package than to get it packaged for s32ds separately.

[VaneB · Accepted solution]

Hi @Henrik-Wires 

The software components on which the AWS Libraries for S32K3 depend; such as FreeRTOS, the TCP/IP stack, HSE firmware, and the S32K3 Real-Time Drivers, are available for S32K396 devices.

However, as you mentioned, the AWS Libraries themselves are only officially released for S32K344 and S32K358. As a result, in S32DS, this software package can only be configured for those specific devices.

It may be possible to manually add and configure the AWS Libraries for S32K396, but please note that this scenario has not been tested or validated. Because of this, we cannot guarantee correct functionality, full integration, or proper interaction with other software components when used on an unsupported device. Any manual integration would be highly dependent on your own implementation and testing.

BR, VaneB