s32g3 multicore enable

[pupu_ji]

Hi, all

I refer "Enabling Multicore Application on S32G2using S32G2 Platform Software Integration" to use it on s32g3.

Building U-Boot use "s32g399ardb3_defconfig" ,and generate fin.32 as described in the "Linux BSP 35.0 User Manual for S32G3 platforms"  ,changing 'FIP_ALIGN := 16'  to 'FIP_ALIGN := 64', adding FIP_QSPI_OFFSET=<QSPI offset> make parameter . The log  as follow:

But when use the dd if=fip.s32 of=/dev/sdb skip=512 seek=512 iflag=skip_bytes oflag=seek_bytes
conv=fsync,notrunc copy fip.32 to SD card , the SD card will become garbled. Can't copy else file.

If I copy them  directly to SD card , nothing on the terminal.

Could you help me?

[Daniel-Aguirre]

Hi,

We have made the modifications to have the FIP_ALIGN:=64 and replaced the fip.s32 file by using the following command:

We are not seeing any problem on regards of this configuration. One difference is that we are not adding any "FIP_QSPI_OFFSET" to the make command.

You cannot just copy the fip.s32 directly to your SD card, you need to replace the fip section inside the image for it to work.

Before replacing the fip.s32 file, was your image working?

Please, let us know.

[pupu_ji]

Thanks for your reply. ><

My SD card has two partition: "boot_s32g39" and "fsl-image-auto-s".

I copy fip.32 to fsl-image-auto-s using the command, and it seems good.

SW4-7 ON, (boot from sd card) is working.

But nothing is on the uart when SW4 is all OFF(boot from nor flash).

Did I do something wrong?  Help me,plead.  TOT.

Copied ipc.ko to SD card boot_s32g39.

Used s32ds flash tool to load bt_m7_blob.bin , fip.bin and IPCF.bin. 

[Daniel-Aguirre]

Hi,

For what you have shown, it seems that the fip.s32 file was made correctly. In order to verify the fip.bin, you can create an IVT where A53_0 is the boot core, fip.bin is the application bootloader and select QSPI as boot interface (adding the configuration parameters to increase the speed of the interface).

If the fip.bin was created correctly, then you should be able to boot from QSPI and see a Linux terminal as the one you are seeing under your SD boot mode. Just as a note, fip.s32 also needs to be replaced on your SD (as you have already done). You cannot use fip.bin with an image that does not have the fip.s32 file modified.

The example mentioned above is still not a multicore application but will let us confirm if the fip.bin was also generated correctly.

Please, let us know.

[pupu_ji]

Hi, I tried the method you mentioned, created an INV where A53_0 is the boot core, but it failed. Does it indicate that the fip.bin was created incorrectly? But fin.bin and fin.32 was created at same time at /arm-trusted-firmware/build/s32g399/release. There is a question , how to prove that fip.32 was indeed copied successfully? I can' find fip.32 in my SD card "fsl-image-auto-s" partition.

[Daniel-Aguirre]

Hi,

Thanks for your feedback. We remember that you added the FIP_QSPI_OFFSET variable to your make command, we did not.

Have you tried running the make command without it? We can see an output on the terminal with the IVT + A53_0 boot + QSPI + (App_BL -> fip.bin).

Also, which RAM start pointer and entry pointer did you use? We remembered you share the ATF output log, but which addresses did you use and where?

As to proof if fip.s32 has been copied, you will not see it directly in the SD partition. You might need to do a HEX dump and compare to see if the fip.s32 section was indeed modified.

Please, let us know.

[pupu_ji]

Hi,

I tried command without FIP_QSPI_OFFSET, still failed.

"Also, which RAM start pointer and entry pointer did you use? We remembered you share the ATF output log, but which addresses did you use and where?"

I used

entry point ->reset handler address

load address ->load image at address(RAM)

And could you provide the files for me to try it ?

[Daniel-Aguirre]

Hi,

Thanks for your feedback.

One you created fip.bin without the QSPI offset, which addresses are you using for the IVT structure (RAM start address; RAM entry address)?

We are still referring to the non-multicore boot, which selects A53_0 core as the boot core and the fip.bin as the Application Bootloader.

Also, did you add QSPI parameters to increase the speed of the interface?

We see that you are still using the bootloader for the fip.bin, have you tried to boot the A53_0 without the bootloader?

As for sharing files, help us opening a ticket under the NXP online services, since we do not commonly share files through the community.

Please, let us know.