S32G RDB2 multicore boot hang in bsp41

[Allen_Cheng]

Hi NXP team,

I try to setup a multicores environment with A53 and M7 following AN13750 official document.

I found a boot issue in bsp41 and I also use bsp42 to clarify.

But BSP42 can bootup to Linux kernel successfully.

BSP41 will always hang in

bootloader 0x2 Application 1 image fragment 0 loaded from QSPI.
bootloader 0x2 Application M7_0 was loaded.

I add these two versions log in attachment.

Could you please help to clarify this issue?

Thanks.

SW:

Integration_Reference_Examples_S32G2_2023_06

EB 27.1

RTD 4.4_4.0.0_P05_HF01

HSE_FW S32G2XX_0_1_0_16

[Joey_z]

hi，Allen_Cheng

Did you change the ATF Load address and Entry point in the Bootloader? As shown in the following figure, the corresponding address is different for different versions of BSP.

Also, you need to check that no SRAM image loading and running addresses of M7 and fip are conflicting

BR

Joey

[Allen_Cheng]

Hi Joey,

The ATF load address are the same in bsp41/bsp42.
Entry point are 0x34700000.
Thanks.

Allen

[Joey_z]

hi,Allen_Cheng

Thank you for your reply.

Your BSP41 print message attachment shows that BL2 should not be started, check to see if the fip.bin of BSP41 was loaded correctly during your compliance with AN13750.

In addition, in order to provide better support, whether you can provide your blob.bin, I will test this problem for you as soon as possible.

BR

Joey

[Allen_Cheng]

Hi Joey,

Attachment is my blob.bin.

Thanks.

[Joey_z]

hi,Allen_Cheng

I have received your blob.bin and have repeated your problem and will solve it as soon as possible.
In addition, I found that BSP41 can be started using your blob.bin and BSP42's fip.bin, you can try it, I suspect that this may be caused by some initialization conflict between the ATF in BSP41 and the Bootloader used, this needs further testing.

BR

Joey

[Allen_Cheng]

Hi Joey,

I used the blob.bin and BSP42's fip.bin with BSP41's sdcard(official image+BSP41's fip.s32).

It can bootup to linux successfully.

So the result means the first question BL2 can't start in BSP41 may have certain issue?  

Another confusion:

If the ATF Load address and others condition are the same in BSP41 and BSP42, the blob.bin need to rebuild again? or they can use the same blob.bin?

Thanks!

Allen

[Joey_z]

hi，

1. According to the printed information, BL2 fails to start. There is an initialization conflict between fip.bin of BSP41 and the Bootloader you made, resulting in a start failure. Did you completely follow the configuration of AN13750? If you made some modifications, could you please give me more specific information? Or could you please provide me with your modified Bootloader project?
2.The ATF Load address in BSP41 is the same as that in BSP42. It should be noted that the Size is a little different, but it does not affect the result of starting kernal. When you have other changes to the initialization requirements, you need to modify the Bootloader project and then regenerate blob.bin.

BR

Joey

[Allen_Cheng]

Hi Joey,

All Configuration of the AN13750 are almost the same but I only modified:

1. u-boot : enable HSE and firmware path

2. ATF not apply mmc patch

3. remove m7_1 and m7_2 in bootloader

Attach files are bootlader and eb project.

Thanks.

Allen

[Joey_z]

hi,Allen_Cheng

Sorry for the late reply.
You can try Disable Secure Boot, as shown in the image below.

In addition, if you are not using mmc patch, make sure you modify the s32_common.mk file.

Wish it can help you.

BR

Joey

[Allen_Cheng]

Hi Joey,

I try to disable secure boot in EB tresos and disable HSE in u-boot.

But it looks like the same result.

Thanks.

[Joey_z · Accepted solution]

HI,Allen_Cheng

After investigation, this is a known issue as described in ALB-11457, and it has been resolved in Linux BSP42. The root cause lies in the bootloader de-initializes (in SysDal) the peripheral clocks before starting the applications, but s32_io_setup() is called without any prior initialization of the SDHC clocks from ATF. The description is shown in the BSP42 release note:

The easiest solution to fix this issue is recommending use BSP>=42. If continue working with BSP41, you can refer to these public commits to modify ATF code.

Hope it can help you.

BR

Joey

[Allen_Cheng]

Hi Joey,

Thanks for your help.

I will base on BSP42 for development.

Allen

[Joey_z]

hi,Allen_Cheng

Thank you for your reply.

I have reported the problem,and I will reply to you as soon as I have the result.

BR

Joey