I am stuck trying to run STM32MP215DK M33 firmware examples on an (unmodified) ostl distribution I built.
I went through the getting started tutorials no problems, now starting to experiment with customisation, but have got myself stuck. Some advice would be appreciated. This STM32MP ecosystem is quite overwhelming to the uninitiated, especially once you add in trusted firmware.
As per this page, I loaded the image FlashLayout_sdcard_stm32mp215f-dk-ca35tdcid-ostl-m33-examples-optee.tsv. I have been playing with building and debugging the various example projects for M33.
When trying to alter the M33 examples, I came up against the hardware firewall. It became clear that I was going to need M33 access to ports and peripherals that were currently allocated to the A35 core. I still haven't worked out how to solve that yet. But ultimately a custom kernel layer will be required, so I started looking into that.
As per this page, I built the default linux distribution and flashed it to my sdcard. I notice this only builds the image FlashLayout_sdcard_stm32mp215f-dk-optee.tsv. I could not work out how to build the above image for m33 examples.
Now with the image I built running, I cannot load firmware to the M33 (through STM32CubeIDE run configuration as per above tutorial). I also see this in the serial console:
[ 4238.970552] remoteproc remoteproc0: powerin3
[ 4238.972101] remoteproc remoteproc0: Image is corrupted (bad magic)
[ 4238.979777] remoteproc remoteproc0: Boot failed: -22
I was assuming it is because the firmware was not signed with the right keys for the distribution I built. But, to be honest, I don't know if the distribution I built actually contains all the support for running M33 firmware (RPMsg, optee etc)?
Please help understand where I went wrong. Thanks in advance.
