Mm-iot-sdk vs mm-iot-cmsis: Which is the most robust path for TWT, AWS, and a custom board?

General
1

Hi everyone,

I’m developing firmware for a custom board based on the MM6108-EKH05 (STM32U5), but featuring a Quectel HaLow module and ST sensors (Accelerometer and Temperature).

My main focus is extreme battery savings using TWT and cloud connectivity via AWS IoT. I started my initial implementation in STM32CubeIDE, which led me to consider the mm-iot-cmsis pack due to how incredibly easy it is to use CubeMX to initialize the sensors. However, I noticed that the direct mm-iot-sdk repository seems to have TWT and the AWS stack much more deeply integrated and ready to use out-of-the-box.

Considering that I need to adapt the base hardware (like changing the BCF file to support the Quectel module) and integrate my own I2C/SPI sensors:

I would appreciate any insights from the community: for those who have already been through this process, which environment (pure mm-iot-sdk or mm-iot-cmsis) has proven to be more robust, flexible, and reliable to take a custom project like this from prototyping all the way to production?

Thanks in advance for any feedback or shared experiences!

2

Hi @marcusanderson

From the Morse Micro side, we’ve had customers build products with both :slight_smile: .
If you’re expecting to engage with ST regarding additional features not covered by the mm-iot-sdk (eg, something like TrustZone support), you may find it easier to choose mm-iot-cmsis.

We’re also interested in knowing what others in the community are finding helpful.