Problem starting BSP31 uboot with M7 bootloader

[Ben6]

Hi, 

I was trying to start bsp31-uboot with bootloader from " Platform_Software_Integration_S32G2XX_2022_06 " on s32g274a-vnp-rdb2, but the uboot won't start and board reset once reaching the following line in " BootloaderSpecific.c ":

    Bl_StartApplication() -> REG_WRITE32(RGM_PRST(partition), resetCore);

I have built the bsp31-uboot in standalone mode (without Yocto), here's the output log:

    MKIMAGE u-boot.s32

    IVT: Offset: 0x0 Size: 0x100
    IVT (duplicate): Offset: 0x1000 Size: 0x100
    DCD: Offset: 0x1200 Size: 0x2000
    AppBootCode Header: Offset: 0x3200 Size: 0x40
    U-Boot/FIP: Offset: 0x3400 Size: 0xc0e7d
    U-Boot Environment: Offset: 0x1e0000 Size: 0x2000

The file "uboot.s32" was programed to flash address 0x300000,  the BootSource in Bootloader plugin was configured as follow (using information in IVT header) : 

    - Reset handler address: 0x340a0000

    - Source address (in QSPI): 0x303240

    - Load image at address (RAM): 0x3408fe40

Additional information:

    - The uboot.s32 image could run with out problem if booting form SD card.

    - I have also tried to load fip.s32 from bsp33-atf using same bootloader package, and it can work. But I need to use bsp31 now for some reason.

Please give me some advice, thank you.

[nxf92355]

Hi Bang-Yuan Liu

Hope you are doing well.

Thanks for reaching to us. I am analyzing your issue description. i need to regenerate issue. can you share the steps that you perform to build bsp31-uboot with bootloader from Platform_Software_Integration_S32G2XX_2022_06.

Best Regards ,

Tushar

[Ben6]

Thanks for your reply

For uboot, I downloaded  version "release/bsp31.0-2020.04" from nxp github and directly build with make command, no configuration was changed.  

For Bootloader, I started with platform integration packge from goldvip1.5. I disabled Rm module in tresos project, added PortPin for LLCE_CAN & PFE, then edit bootsource to start A53 with uboot (no m7 application was involved now).  

[nxf92355]

Hi Bang-Yuan Liu

Seems you got a reset as soon as A53 core 0 was released. you need to check the starting code of BL2. Since BL2 code assumes there is no other cores run on parallel, it might do some initialization of shared resources (e.g. clock, power) that breaks something.

Compare BL2 starting code from bsp31 and that from bsp33 may help to find the root cause.

Regards ,

Tushar

[nxf92355]

Hi ,

I have raised a internal ticket about your issue, i will update as i got reply

Regards ,

Tushar