Mm-iot-cmsis pack missing AWS OTA functionality

Hello, I have been working with the mm-iot-cmsis pack and the EKH05 dev kit on STM32CubeIDE for a couple months now and I’m trying to get the aws iot example with OTA update working. so far it seems that the library directories needed to get this working are not included in the current release and when I try to include them myself from the 2.6.4 sdk I get a lot of undefined reference errors. One thing I am currently stuck is the fact that the mmconfig source files provided in the pack is different from the ones in the sdk so I get errors like this STM32Cube/Repository/Packs/MorseMicro/MM_IoT/1.5.0/HaLow_example_spi/Debug/../Middlewares/Third_Party/MorseMicro_AWS_AWS-libraries/AWS-common/ota_pal.c:76: undefined reference to `mmconfig_write_string’

I will appreciate any support on this as I am on a tight deadline to evaluate this.
Thanks,
Dami

Hi @doludiran ,
The 1.5.0 version of cmsis-pack doesn’t come with a writable configuration (the mmconfig compenent in cmsis-pack doesn’t support it in 1.5.0).
Soon the cmsis-pack will be updated to have mmconfig component with write ability.

Since you’re on a tight timeline, I’ll recommend you to have a look at GitHub - MorseMicro/mm-iot-sdk
The mm-iot-sdk have the full functioning aws-iot example.
Kind Regards,
Milad

Thanks for your response @Milad, We will give the sdk a try using platformIO. Do you have any idea when support will be added to the cmsis pack?

you’re welcome @doludiran.
I don’t have any estimation of the date for next release.
but even if you get the new cmsis-pack with writable mmconfig component, it wouldn’t have the aws OTA example in it.
aws OTA example from mm-iot-sdk, needs some fundamental infrastructure such as bootloader that doesn’t exist in cmsis-pack yet.
Kind Regards,

Ok thanks. Hit some road block working with the sdk on platformIO. It keeps failing to flash the firmware on the dev kit and it works fine when I use stm32cubeIDE

Hi @doludiran,

Would you mind double checking that you have all the jumpers loaded correctly? Testing with the porting_assistant application, I was able to reproduce the symptoms you are seeing if I removed any one of the jumper’s outlined in green (removing power to the STM). With the jumpers present I am not able to reproduce.

Additionally, I would recommend populating the T_VDD jumper to your board so the debugger can detect the voltage being supplied to the target. Note, this will cause additional leakage if you are trying to do power consumption measurements which is why it is not loaded by default.

Using GitHub - MorseMicro/mm-iot-sdk 2.7.2 to test

1 Like