With Torizon OS 6, u-boot is able to load and start firmware on M7 core using EXT4LOAD method.
The method is described here and on some topics on this community:
But with the new Torizon OS 7 this method doesn’t work anymore.
I tried:
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
The issue you’re experiencing with the EXT4LOAD method not working in Torizon OS 7 for loading firmware on the M7 core is a known problem. This method was functional in Torizon OS 6 but has been reported as non-functional in specific versions of Torizon OS 7, including 7.0.0+build.1 and 7.1.0-devel-20241105+build.90. This change indicates a regression or alteration in functionality with the transition to Torizon OS 7. Users facing this issue are encouraged to check community discussions for any potential workarounds or updates that might address this problem.
Please, also check if these links can help you solve your problem:
Hello @vix,
I apologize for the delay on this topic.
I will look into it and get back to you.
Best Regards,
Bruno
Hello @vix,
I tested this again with Torizon OS 7.0.0 and the Cortex-M7 booted successfully.
I tried with both the default firmware and a firmware that is located in the DDR and both worked.
You likely already know this, but when using a firmware located in the DDR, you need to change the addresses in the cm_boot command.
Can you share what procedure you are following?
Best Regards,
Bruno
It’s the same CI/CD pipeline that builds Torizon OS customizing u-boot.
Let me double-check what happens on my side.
