- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
-
- NXP Tech Blogs
- Home
- :
- Product Forums
- :
- S32K
- :
- Re: AWS IoT middleware on S32K396
AWS IoT middleware on S32K396
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Solved! Go to Solution.
VaneB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
