Hi,
This error message has appeared before to us since there is a restriction over the alignment of the FIP image:
Did you modify the FIP_ALIGN variable to be 64? This is also told under the AN13750. Once we modified the alignment, the error disappeared from our build.
The calculation for the load address is as follow:
Please, let us know.
Hi,
For the information you are providing, you are using yocto project, is this correct? If so, we are not obtaining the image from yocto project, but from manually building both u-boot and ATF (as described under the AN13750).
Below will be some comments on regards of your questions:
A1 >> They are not the same. Seeing the contents of both fip.bin and fip.s32-qspi, fip.bin is the binary for the fip itself, while fip.s32-qspi contains both the fip itself and the whole IVT structure which can be flashed directly to the QSPI. As seen on the image below, the offset of the image is different from the *.bin (no offset) to the *.s32-qspi (offset):
Again, the offset is due to the IVT structure under the *.s32-qspi file.
A2 >> Can be obtained by manually building both u-boot/ATF. This is described under the "Manually building Linux BSP components" under the respective BSP User Manual, or under the AN13750 itself.
As a note, codeaurora link is not available anymore, the new link should be the one from github itself:
https://github.com/nxp-auto-linux
As for yocto, should be located under the following path:
A3 >> On regards of the RAM pointers under the IVT, they are not the same. The addresses are the following:
This can be confirmed by looking into the *.map file from the Bootloader.bin.
Please, let us know.
Hi,
We have not used the "fip.bin" file created by yocto, but looking into the folder we shared it seems that the structure is the same, hence it should work.
As for the log, we are not finding the exact log that it is printed (as shown under the AN13750), but you should be able to find the "Entry Point" by looking into the *.map file for BL2:
Regarding the "Load Address", this is calculated with the following formula:
For which, BL2_BASE should be the Entry Point and the FIP_HDR_SIZE and DTB_SIZE are available under the same folder as the "fip.bin" file:
With them, you should be able to obtain the "Load Address".
As for the QSPI addresses, these can remain the same.
Please, let us know.
Hi,
For the first error, you require to install "bison", we have it installed under our setup as follows:
For ATF, you require do require for u-boot compilation, since it uses the u-boot binaries for the ATF compilation stage.
As for the DTC version, we do have one version greater than the one being specified:
Could be a problem with the packages that you have installed.
Please, let us know.
Dear Daniel,
I checked the map file in bl2.map, dtb_size and fip_hdr_size and got
bl2_entrypoint = 0x34302000
dtb_size = 0x7000
fip_hdr_size = 0xe0
So I got a load address = 0x342FAF20 using the formula you told, and config bootloader in EB as follow:
But error messages appeared when I try to generate project:
Invalid value for node "/AUTOSAR/TOP-LEVEL-PACKAGES/Bootloader/ELEMENTS/Bootloader/BootSources/linux_bsp_atf/ImageFragments/...": The load RAM address is invalid. If you use CRC over DMA transfer, the start address must be multiple of 8 If you don't use CRC over DMA transfer, the start address must be multiple of 64
What shall I do to make the ATF load RAM address OK?
Thanks.
Hi,
This error message has appeared before to us since there is a restriction over the alignment of the FIP image:
Did you modify the FIP_ALIGN variable to be 64? This is also told under the AN13750. Once we modified the alignment, the error disappeared from our build.
The calculation for the load address is as follow:
Please, let us know.
