CM4 EEPROM bootloader says Balena image start4cd.elf is too old

Hello, we are flashing CM4 modules with a Balena CM4/CM4IO image downloaded from the Balena dashboard. Some modules work fine, others won’t boot, complaining of the start4cd.elf being not compatible and that “new software” is needed. I believe this is because they have a newer EEPROM bootloader which doesn’t like the Balena bootloader. I tried flashing a newer EEPROM bootloader (just in case) but that didn’t help, also tried replacing the .elf files from a (newer) development Balena image, but this also didn’t boot. Has anyone else had this type of issue and have any suggestions please? Thanks!

Hey @neil.simpson welcome to the forums and thanks for reporting this! I’ll have to ping in my colleagues here but we’ll get back to you as soon as we can.

In the meantime, it may help if you can check to see if there are any physical differences - for example, check the image below. Is there any correlation between the differences in this image and in the behaviour you’re seeing?

Thanks for the reply Chris. I will try to get you the pictures tomorrow.

Hello,

Which version of balenaOS are you using? If you are using using a version earlier than 2.91.1, please keep reading.

When I choose to “add device” to my fleet and choose “Raspberry Pi CM4 IO Board” I am offered v2.88.4+rev0", that is the version I am using. Is there some way to access a newer version for the CM4?

As you suspected, the modules which don’t work have the Dialog DA9090 PMC, whereas the older modules which do work have a different branded chip. Does anyone have a suggested solution - is there a new release on the way from Balena which will support the new CM4?

Hi, there should be a newer OS release for the CM4. Can you try with release version v2.112.12 and let us know if you still have issues with it?

Will do, thank you Florin.