Using the bootloader with a custom M7 image

[Matteo_Zini]

Good morning,

I was trying to customize the GoldVIP boot process by changing the M7 image with a custom one.

After flashing the complete GoldVIP image on the QSPI memory with u-boot, as explained in the goldvip user manual (Everything starts with this configuration), I built an example project with S32DS and tried to customize the bootloader configuration to adapt it to the new binary, trying to follow the instructions provided in AN13750, in the bootloader manual, and in the "S32G-VNP-GLDBOX3 SOFTWARE ENABLEMENT GUIDE".

However, after flashing the new bootloder binary, the new bootloader's configuration and the custom M7 binary with the S23 Flash Tool, the bootloader executes corretly and the stock A53 image is started, while the new M7 binary apparently fails to execute.

Therefore, I was wondering if any binary built with S32DS can be used with the bootloader or if there is some additional step to be taken in order to use it in this context.

Thank you in advance.

[chenyin_h · Accepted solution]

Hello, @Matteo_Zini 

Thanks for the post.

From my understanding, your own M7 binary built from S32DS and/or EB could be used as the M7 application part mentioned in AN13750.

Different M7 application used may have different conflictions situation with A core software(BSP), so that there would be additional work for you to analyze and debug,(sometimes M core may not start correctly and sometimes A core not) which is specific for different status.

BR

Chenyin