topic Re: Start Linux form M7_0 Failed in S32G

Start Linux form M7_0 Failed

StanleyShen — Wed, 11 Jan 2023 12:32:20 GMT

Hi there

Since both start M core(APP) and A core still no good, and refer to the attatched document,

I want to start Linux form M7_0 bootloader all lone (not include M7 APP).

I did following steps, but there was not any info output from the UART0,

Could you tell me where the problem is?

Prepare images for Cortex-A53 cores

1:download binaries_auto_linux_bsp33.0_s32g2_pfe.tgz and extract it
2:dd if=binaries_auto_linux_bsp33.0_s32g2_pfe/s32g274ardb2/fsl-image-auto-s32g274ardb2.sdcard of=/dev/sdc bs=1M status=progress && sync
- (by this, SD mode startup OK)
3:checkout release/bsp33.0-2020.04 and build it
4:checkout arm-trusted-firmware (release/bsp33.0-2.5) and buid it (`FIP_ALIGN := 64` and unset LDFLAS because I had a "aarch64-fsl-linux-ld.bfd: unrecognized option '-Wl,-O1'" error)
5:Build the ATF and got a fip.32 the address info as blow:
- IVT Location: SD/eMMC
- Load address: 0x342fc580
- Entry point: 0x34302000
6:renew fip.32

dd if=fip.s32 of=/dev/sdb skip=512 seek=512 iflag=skip_bytes oflag=seek_bytes conv=fsync,notrunc

Prepare bootloader for Cortex-A7_0 core

1:load Integration_Reference_Examples bootloder to EB
2:disable RM Eep MemDal CryptoDal Crypto plugin and releated options
- (In my Env the SDHC and HSE is still abnormal)
3:Bootloader(…)->Bootloader->General Software breakpoint enable uncheck
4:boot option like blow:
5:generate project and build bootloader.bin
6:Generate S32G Boot Image Using S32DS IVT_TOOL
7:Deploy the bootloader(with IVT) and fip.32 to QSPI(NOR Flash) with s32ft.exe
- bootlader 0x0000_0000
- fip.32 0x0010_0000

After above operations, set RDB2 to QSPI boot mode.

Re: Start Linux form M7_0 Failed

Daniel-Aguirre — Wed, 11 Jan 2023 19:11:22 GMT

Hi,

We may not understand the scope of your application but, why are you trying to boot the A53 core with the M7 if the M7 is not going to be used?

Also, the fip.s32 is not to be used on QSPI if it was not built to work with QSPI, there should be another fip file that was created for the QSPI interface.

The following is said in the Linux BSP User Manual [Page 25, Linux BSP 33.0 User Manual for S32G2 platforms, 07/2022]:

"For QSPI boot, configure TF-A to read the FIP image from a defined QSPI offset. Add FIP_QSPI_OFFSET= make parameter, as in the following example:

make CROSS_COMPILE=/path/to/your/toolchain/dir/bin/aarch64-none-linux-gnu- \ ARCH=aarch64 PLAT= BL33= \ FIP_QSPI_OFFSET=0x5400"

Please, let us know.

Re: Start Linux form M7_0 Failed

StanleyShen — Thu, 12 Jan 2023 01:59:43 GMT

We may not understand the scope of your application but, why are you trying to boot the A53 core with the M7 if the M7 is not going to be used?

Because I want to start both A53 and M7 from M7, I broke down the steps, first BOOTROM>M7_ 0(bootloader)-> A53_ 0. If this is successful, then BOOTROM ->M7_ 0(bootloader)-> M7_ 0(App)

Also, the fip.s32 is not to be used on QSPI if it was not built to work with QSPI, there should be another fip file that was created for the QSPI interface.

If you look at the attachment I uploaded, you will know that the actual startup sequence I used is BOOTROM ->M7_ 0(in Nor Flash) -> fip.32(in Nor Flash) -> u-boot(in SD), not BOOTROM ->M7_ 0(in Nor Flash) -> fip.32(in Nor Flash) -> u-boot(in Nor Flash), so, I think configure TF-A to read the FIP image is unnecessary.

Unfortunately, the problem returns to the point that I have been confused,

That is how to verify the following startup process in the simplest way:

QSPI startup mode

BOOTROM->M7_ 0(bootloader)->A53_ 0(FIP)->M7_ 0(APP output "hello world" to UART1)

L______-> A53(U-Boot->Linux)

I think I have basically referred to attached Multicore Application on S32G2. pdf, but still not work

Re: Start Linux form M7_0 Failed

Daniel-Aguirre — Thu, 12 Jan 2023 16:09:34 GMT

Thanks for the information.

You are referring to an attachment, but we could not find it, is the attachment the images provided above?

Taking your words "...the actual startup sequence I used is BOOTROM ->M7_ 0(in Nor Flash) -> fip.32(in Nor Flash) -> u-boot(in SD)...", we retake our point, the fip file you are using is the same you used for your SD boot? if so, this is wrong. You should use a fip file configured to work from QSPI.

We could recommend a previous step which could be BOOTROM ->M7_ 0(in Nor Flash) -> A53(in SD). As you said, if the SD boot was OK, you will add the M7 variable to the equation, then if adding the M7 and booting the A53 from SD works, you can jump to using the NOR Flash. Just a recommendation.

Please, let us know if this information was helpful or not.

Re: Start Linux form M7_0 Failed

StanleyShen — Fri, 13 Jan 2023 09:24:10 GMT

- You are referring to an attachment, but we could not find it, is the attachment the images provided above?

Sorry for this, I will attach the file .

- we retake our point, the fip file you are using is the same you used for your SD boot? if so, this is wrong. You should use a fip file configured to work from QSPI.

I am sorry I still don't think so, pls let me explain the reason

1:refer to the GoldVIP binaries and GoldVIP document, we found the following files that you provided.

And I dd the fsl-image-goldvip-s32g274ardb2.sdcard to SD card and burnt the boot-loader and fip.32-sdcard to QSPI Flash, the Linux can start normally in QSPI mode.

Alao I hexdumped the fip.32-sdcard and you can the IVT image is on the 0x1000,

that is the position of IVT in SD mode.

2: I downloaded the u-boot and make s32g274ardb2_qspi_defconfig and create IVT image with arm-trusted-firmware, but still NG(burnt it to NOR Flash but no any message outputed on UART0)

I also confirmed that this FIP file is available(no burnt linux image to QSPI)

NOTICE: BL2: v2.5(release):bsp33.0-2.5-dirty NOTICE: BL2: Built : 08:08:26, Jan 13 2023 NOTICE: BL2: Booting BL31 U-Boot 2020.04 (Jan 13 2023 - 16:06:18 +0800) CPU: NXP S32G274A rev. 2.0 Model: NXP S32G274A-RDB2 DRAM: 3.5 GiB MMC: FSL_SDHC: 0 Loading Environment from SPI Flash... SF: Detected mx25uw51245g with page size 256 Bytes, erase size 64 KiB, total 64 MiB *** Warning - bad CRC, using default environment Using external clock for PCIe0, CRNS Configuring PCIe0 as RootComplex(x2) Using external clock for PCIe1, CRNS Frequency 125Mhz configured for PCIe1 Configuring PCIe1 as SGMII(x2) [XPCS0 2.5G, XPCS1 OFF] Setting PCI Device and Vendor IDs to 0x4002:0x1957 PCIe0: Failed to get link up Pcie0: LINK_DBG_1: 0x00000000, LINK_DBG_2: 0x00000800 (expected 0x000000d1) DEBUG_R0: 0x00189900, DEBUG_R1: 0x08200000 PCI: Failed autoconfig bar 20 PCI: Failed autoconfig bar 24 PCIe1: Not configuring PCIe, PHY not configured In: serial@401c8000 Out: serial@401c8000 Err: serial@401c8000 Board revision: RDB2/GLDBOX Revision D Net: EQOS phy: rgmii @ 1 Warning: eth_eqos (eth0) using random MAC address - 12:e8:6d:ee:63:42 eth0: eth_eqos PFE: emac0: sgmii emac1: none emac2: rgmii ## No elf image at address 0xffdc92f8 PFEng firmware file '<NULL>@0x03000000:<NULL>' loading failed: -22 Hit any key to stop autoboot: 0 ## No elf image at address 0xffdc9048 PFEng firmware file '<NULL>@0x03000000:<NULL>' loading failed: -22 PFE: emac0: sgmii emac1: none emac2: rgmii pfeng_cfg_mode_enable: Invalid PFE device Booting from flash... device 0 offset 0x1f0000, size 0xe00000 SF: 14680064 bytes @ 0x1f0000 Read: OK device 0 offset 0xff0000, size 0x100000 SF: 1048576 bytes @ 0xff0000 Read: OK device 0 offset 0x10f0000, size 0x2000000 SF: 33554432 bytes @ 0x10f0000 Read: OK Bad Linux ARM64 Image magic! => =>

So, Although It hard to say what the model is, I think the blow flow can work normally

QSPI mode
BOOTROM -> M-core bootloader(with IVT in NOR Flash) -> M-core APP

|-------A-core FIP(SD-Card mode and in NOR Flash) -> A-Core U-Boot(in SD-Card)->A-Core Linux(in SD-Card)

Back to the question of the title

I used the UART sample of RTD, and configured the bootloader like blow:

And I burnt both bootload, ATF(SD-Card and QSPI ), UART sample with windows GUI tool

the UART0 can be output normally like blow but UART0 still NG

I also give the IVT compilation log. Can you give me some suggestions?

SD Mode

QSPI Mode

Re: Start Linux form M7_0 Failed

Daniel-Aguirre — Fri, 13 Jan 2023 19:26:58 GMT

Hi,

Thanks for the attachment.

We do apologize for our insistence, but we want to retake the following point:

"- we retake our point, the fip file you are using is the same you used for your SD boot? if so, this is wrong. You should use a fip file configured to work from QSPI."

Below should be a capture of what is provided inside the NXP BSP 33.0 binaries folder, under the RDB2 sub-folder.

In which 2 fip files are provided, one for SD and one for QSPI.

For what you have been telling us, you are using the same fip file you used (and worked) on the SD interface. This should not work on the QSPI interface.

Have you tried (at this point in time) to boot up linux (without M7 into the equation) from NOR Flash?

From the first point you mentioned "...and fip.32-sdcard to QSPI Flash, the Linux can start normally in QSPI mode." and also "...I hexdumped the fip.32-sdcard and you can the IVT image is on the 0x1000." we understand you tried this option, but it is not explicitly mentioned.

In QSPI mode, S32G looks for the IVT on 0x0, not 0x1000 [Table 137, Page 1146, S32G2 Reference Manual, Rev. 6, 11/2022], which the IVT for the fip file you are using is located, but you still got it working in QSPI mode.

We suspect you got your platform to boot up from the SD (not QSPI), which is expected from the steps you mentioned (and files you used).

Still, as we said before, we could not be understanding correctly your application nor configuration/set-up.

Please, let us know.

Re: Start Linux form M7_0 Failed

StanleyShen — Sun, 15 Jan 2023 02:17:01 GMT

- Have you tried (at this point in time) to boot up linux (without M7 into the equation) from NOR Flash?

Yes I did and juest the yesterday's thread, the result as blow, beacuse I didn't burn the zImage to QSPI flash, U-Boot -> Linux start NG, but I think the from NOR Flash start Linux was OK.

- From the first point you mentioned "...and fip.32-sdcard to QSPI Flash, the Linux can start normally in QSPI mode." and also "...I hexdumped the fip.32-sdcard and you can the IVT image is on the 0x1000." we understand you tried this option, but it is not explicitly mentioned.

- We suspect you got your platform to boot up from the SD (not QSPI), which is expected from the steps you mentioned (and files you used).

Maybe I didn't explain my process in detail enough, in my boot sequence, The used IVT is included in M7_ 0_ Bootloader, not fip, and in M7_ 0_ Bootloader.bin the offset of the IVT image is 0x0.

(means that the fip.32 was called by M7_0 bootloader, not by BOOTROOM)

I don't know if you have read the attachment I added [Enabling Multicore Application on S32G2 .pdf]

the deployment as blow:

As I said in before thread, the actual boot flow is:

BOOTROM -> M-core bootloader(with IVT in NOR Flash) -> M-core APP

|-------A-core FIP(in NOR Flash but load and start by M-core bootloader) -> A-Core U-Boot(in SD-Card)->A-Core Linux(in SD-Card)

Therefore, the FIP image must be in SD-Card mode because it needs to read U-boot from SD card.

Please focus on document I was attached [Enabling Multicore Application on S32G2 .pdf]

I refer to this document in depth and have the following differences from it:

1: don't use IPC(both Linux and MCAL)

2:use Uart_TS_T40D11M30I2R0(RTD_4.4_3.0.2) replace to IPCF_Example

3:disable crypto and SDHC on bootloader

So now I'm puzzled why the UART of M-core can start normally, but the U-Boot and Linux of A-core can't start(maybe start OK but can't output to UART...).

Is it the reason that my bootloader does not contain crypto and SDHC?

In addition, I debugged the bootloader and found that FIP was loaded and executed normally without any error

bootloader.c - main() - Bl_Run() - Bl_BootApplications() - Bl_LoadApplication() - Bl_FetchApplication() - Bl_LoadAndAuthFromQspi() - Bl_StartDmaTransfer() // Fetch application image and copy to RAM OK - Bl_StartAllApplications() - Bl_StartApplication() // run FIP image(BL2) OK - Bl_StartApplicationOnCurrentCore() // run UART sample OK

- update CST 2023/01/14 21:43

Just refer to the [Enabling Multicore Application on S32G2 .pdf], I rebuild the bootloader with SDHC and HSE

So, for now, the only difference from the document is that I use UART instead of IPCF to verify M7's actions.

But still work abnormal.

To facilitate understanding, I clean up my boot flow as blow:

Re: Start Linux form M7_0 Failed

StanleyShen — Tue, 17 Jan 2023 01:34:53 GMT

Can somebody help me ?

Re: Start Linux form M7_0 Failed

StanleyShen — Tue, 17 Jan 2023 02:33:16 GMT

Hi Daniel

In addition to the information sent last Friday that needs your help to confirm, I have a new idea and I don't know if you can cooperate

Just refer to [Enabling Multicore Application on S32G2 .pdf] that we was attached, you should be able to compile the relevant binary files for starting A53 through M7, so can you provide the files compiled according to this document, as blow:

m7_ bootloader.bin(with IVI image and start fip.32(BL2))
m7_ bootloader.elf(with compile infomation)
fip.32
m7_ app.bin

I want to burn these normal files, and then debug m7_ Bootloader.elf to compare with my environment.

Also

These attached files are compiled from my environment. I wonder if you can debug my files to see why A53 doesn't start normally

Burn and write bootloader_ a_ m_ Blob.bin to 0x00
Burn fip.s32-sdcard-self_ 0114 to 0x100000
Burn main.bin to 0x200000

Then with the QSPI mode and you can see the output of main.bin on serial port 1 (9600 rate)

Next, you can debug fip.s32-sdcard-self with S32G debug probe.

Thinks.

Re: Start Linux form M7_0 Failed

Daniel-Aguirre — Tue, 17 Jan 2023 20:42:36 GMT

Hi,

Thanks for your patience, we are still working on your case.

We will update you as soon as we have more information on your inquiry.

Just as a question (maybe you have already answered this), have you tried running the application without modifications? To verify if there is a problem with the instructions. The software related to this AN is provided in the S32G2 product page as AN13750SW.

Please, let us know. We want to be sure that you can run the provided application prior to making modifications.

Re: Start Linux form M7_0 Failed

Daniel-Aguirre — Fri, 20 Jan 2023 21:42:48 GMT

Hi,

We do apologize for the delay.

We want to step back a little bit from the whole starting up A53 with linux from the M7 core, due to it being complex to debug and difficult to explain.

We make you the following proposal, have you tried booting A53 Linux from the same A53 with QSPI interface? Has it worked for you?

This can be done directly with S32DS v3.4

This will let us know if the files you have are working for the following steps required in the multicore boot.

Please, let us know.

Re: Start Linux form M7_0 Failed

StanleyShen — Tue, 24 Jan 2023 12:35:35 GMT

Daniel

Sorry for the Chinese New Year leave.

- have you tried running the application without modifications?

Yes, I did, but still NG,But there was one difference:

to disable BREAKPOINT, I unchecked Bootloader(…)->Bootloader->General ->Software breakpoint enable, No code modification.

For confirmation, I Re-compiled the images and provide those files and IVT configuration

In addition,here are two questions, please let me to confirm

In AN13750, about deployment, should we have to copy two files, and is the deployed file a fip.bin file instead of a fip.s32 file?
I tried to debug the bootloader.elf file that I attached, it stopped at HSE firmware initialization, is there a problem here?(I think it should be because of the debugger， because I unchecked the [secure boot] at Bootloader(…)->EcuC(…)->Bootloader(…)-> Bootloader->General and the debug is OK,but start A53 still NG)

Maybe I still missed something, but there is still no special progress so far. Please help me.

Thank you very much.

Re: Start Linux form M7_0 Failed

Daniel-Aguirre — Tue, 24 Jan 2023 16:51:35 GMT

Hi,

No worries. Before going to debugging the multicore application, we would like to confirm if you can boot-up Linux from NOR Flash using the A53 core. This can be done directly from S32DS and by following Section 4 from AN13750.

The fip file that needs to be modified on the BSP provided by NXP is the fip.s32. The fip.bin is the one that needs to be flashed into NOR Flash. We can say is the "application bootloader" that you flash into the IVT of S32DS for our scenario of booting from A53. This will let us know if your files are working correctly.

Please, let us know.

Re: Start Linux form M7_0 Failed

StanleyShen — Wed, 25 Jan 2023 11:47:46 GMT

Hi Daniel

Thank you for your kind help,

Since I reconfigure the IVT image like blow, it seems that both A53 and M7_0 were startup OK

and between Linux Kernel and Cortex-M7 cores the IPC communication was OK too.

- we would like to confirm if you can boot-up Linux from NOR Flash using the A53 core. This can be done directly from S32DS and by following Section 4 from AN13750.

About this, I still think that the content in Section 4 describes starting Linux from SD card instead of NOR Flash.

BTW,

we will soon use S32G to develop AUTOSAR AP and domain controllers, and I inquired about NXP's customer service in China. They mentioned that the support of S32G is in Europe (the Netherlands?), because there is a time difference between China and the Netherlands. Besides this forum, is there any more easy way (near-real-time) to ask you questions?

In addition,

I saw some Chinese menual in the forum. I don't know whether these menaul were made by NXP employees in China or Chinese employees in Europe?

Therefore, even in Europe, is it possible for Chinese (or Ethnic Chinese) to support China's S32G business in the future.

Re: Start Linux form M7_0 Failed

Daniel-Aguirre — Wed, 25 Jan 2023 17:41:19 GMT

Hi,

Good to know you got it working.

As for support, we may recommend talking to your local NXP representative, for them to channel the support for your current region.

As for us knowing, we may not be the correct person, we do apologize for this.

Please, help us reaching your local NXP contact and surely they will find some local support for your project.

Re: Start Linux form M7_0 Failed

StanleyShen — Thu, 26 Jan 2023 00:21:48 GMT

Hi Daniel

Thank you very much.

I got it.

Pls allow me to close this issue.

Re: Start Linux form M7_0 Failed

maiwl — Fri, 17 Feb 2023 16:55:24 GMT

Since I reconfigure the IVT image like blow, it seems that both A53 and M7_0 were startup OK

您好，您是通过修改M7核的Bootloader的IVT配置就启动成功了吗?烧录到norflash的是fip.s32还是fip.bin？

Re: Start Linux form M7_0 Failed

maiwl — Fri, 17 Feb 2023 16:56:55 GMT

我最近按照AN13750的文档进行M核引导A核的操作也遇到同样的问题，希望能得到你的帮助。

Re: Start Linux form M7_0 Failed

StanleyShen — Tue, 28 Feb 2023 08:02:49 GMT

- 您是通过修改M7核的Bootloader的IVT配置就启动成功了吗?烧录到norflash的是fip.s32还是fip.bin？

参考附件的Enabling Multicore Application on S32G2 .pdf就可以成功了，

注意烧到NORFlash的一定要是fip.bin。

Re: Start Linux form M7_0 Failed

maiwl — Wed, 08 Mar 2023 12:02:38 GMT

好的，谢谢，我想知道你一开始遇到的问题是什么，然后修改哪个地方就调通了？