Following is the scenario we want:
** Flash Layout for boot **
---------------------------------------------------------------------------------------
Exported Blob |
(IVT + QSPI reconf + DCD + HSE + Application bootloader(M7)) |
---------------------------------------------------------------------------------------
Application for M7 |
---------------------------------------------------------------------------------------
u-boot for A53 |
--------------------------------------------------------------------------------------
1. Application bootloader downloads Application for M7 and u-boot for A53
2. Application bootloader activates A53 and M7
3. u-boot in A53 configures hardware and downloads kernel for A53 from DRAM
4. u-boot jumps to kernel for A53
Is this possible scenario for S32R45? If so, can we make u-boot only image without IVT+QSPI reconf+DCD+HSE? What I found in mamual is the way of makeing u-boot image with them. Otherwise, Are there any other guided scenario for M7 bootloader to activate A53 in NXP?
Attached image is the S32DS bootsource configuration for better understanding
Another question is that:
When we build ATF, we couldn't find a was to change fip image's load address.
It seems to be fixed as 0x34300980 as below. That's why we add FIP_MEMORY_OFFSET with 0x34300980.
Can we change this address? Entry point might change accordingly.
Hello,
Have you successfully customized these two addresses?
About Load address and Entry point in ATF.
I have no idea about Load address...
Hi,
The load address is calculated depending on the size of dtb and a fip header (dummy_fip file). The image is built in the next way:
DUMYY_FIP_HEADER: Load address
DTB: BL2 address - DTB size
BL2 start and entry point at 0x3430_2000
Saludos,
Alejandro