Build M7 bootloader using Tresos and Platform Software Integration 21.07

[saurabh_patel]

Hello Team,

We want to design M7 bootloader  that should load M7_0 app and A53_0 U-boot. We are using Platform Software integration 21.07 and Tresos 27.1. We want to build and verify M7 bootloader on S32G274ARDB2board.  We have followed the Bootloader manual given with Platform Software Integration tool.  But we are unable to get logs on any of the cores.  Our boot media is QSPI. Steps summary is listed below. 

M7_0 Bootloader Design steps with Platform Integration Software 2021_07

•  Install Pre-requist softwares and tools as per Bootloader manual given in Documentation folder of Platform Integration Software 2021_07.
• Open "Bootloader_S32G2XX_ASR_4.4_M7" in Tresos 27.1
• Build Lightning Single Core application. Generate PlatformIntegration.bin 
• Keep default bootsource configurations which are as follows:
• Load U-BOOT from QSPI 0x300000 ; Text_base : 0x340a0000 : DTB: 0x34090000
• Load Lightning single core application from QSPI : 0x200000
• Build Bootloader.bin 
• Open S32DS and invoke IVT Tool from A53_0Diagnostic Project.
• Set Boot source as M7_0.
• Boot Media as QSPI 
• Select QuadSPI_133MHz_DDR_configuration bin from Platform Integration software
• Select S32G274_DCD_initSRAM.bin from Platform_Integration_software
• Select Bootloader.bin as application Binray
• Set RAM entry point addresses as 0x34700000
• click on "Align"
• export Blob Image
• Using Hex Editor Tool Add Platformintegration.bin at 0x200000 and u-boot.bin at 0x300000 to generate final_blob.bin image
• Flash this image on s32g274ardb2 board at QSPI offset 0x0.
• Verify bootlogs.

Query: 

Standalone A53_0 and M7_0 is working fine for SD, QSPI platform on S32G274ARDB2 board. But while we integrate it through Platform Software Integration tool,  we are not able to get logs on A53_0 and nothing for M7_0. 

When we try to configure M7_0 bootloader in IVT Tool with SD/eMMC we are not able to set IVT_Address to 0x1000. 

Kindly guide us and provide working demo example of Platform Software Integration 21.07 if available. 

[nxf58665]

Hi Saurabh,

"When we try to configure M7_0 bootloader in IVT Tool with SD/eMMC we are not able to set IVT_Address to 0x1000." - please use a newer S32DS version which supports the rev 2 changes regarding the IVT header offset. S32DS 3.4 should allow you to set the address correctly inside the IVT layout.

"we are not able to get logs on A53_0 and nothing for M7_0." - What do you mean by logs on A53_0? You don't get any U-boot logs?

Thanks,

Chris

[saurabh_patel]

Hi Chris,

Thank you for your response.

After selecting cortex_rev2, we are able to set IVT address to 0x1000 for SD/eMMC. Thanks for your input.

But, we are not able to get u-boot logs on A53_0 and no update on M7_0. We are using the default configuration of bootloader example in Tresos. 

Best regards,

Saurabh

[nxf58665]

Hi Saurabh,

Please keep in mind that at the moment we support only QSPI boot flow for the Bootloader IVT blob. SD boot flow is possible with the current release, but there are some differences in the Fls config.

The default configuration should work, but you must also make sure that you are flashing the right images at the mentioned flash addresses. Could you please enable the debug loop functionality and data.dump 0x34090000 and 0x34300000 after the images get loaded via QSPI in Bl_BootApplications?

Thanks!