S32GのトピックUsing the S32g274rdb2 development board to debug the bootloader

Using the S32g274rdb2 development board to debug the bootloader

sdx111 — Thu, 22 Aug 2024 07:48:56 GMT

With reference to this document, I have changed the state of SPI1 of BSP35 in core A to disable. Why does this GPIO LED still stop flashing after core A loads SPI1 during operation?

Re: Using the S32g274rdb2 development board to debug the bootloader

chenyin_h — Mon, 26 Aug 2024 03:03:13 GMT

Hello, @sdx111

Thanks for the question and sorry for the delay.

May I know if it stops flashing once entering the uboot or kernel? how you disabling the SPI1?

Chenyin

Re: Using the S32g274rdb2 development board to debug the bootloader

sdx111 — Mon, 26 Aug 2024 03:39:01 GMT

It stops flashing once entering the kernel.
I only changed the status of SPI1 for dts in uboot and kernel to disable.The document I refer to is S32G_Bootloader_V2-2022.1024_eng.pdf .

Re: Using the S32g274rdb2 development board to debug the bootloader

chenyin_h — Tue, 27 Aug 2024 02:41:47 GMT

Hello, @sdx111

Thanks for the clarification.

Sorry that I do not see problem from this training document attached, from your test, it is correct under u-boot, right? since there is issue once enter the kernel, would you please try removing the corresponding nodes from kernel DTS?

Chenyin

Re: Using the S32g274rdb2 development board to debug the bootloader

sdx111 — Tue, 27 Aug 2024 05:14:57 GMT

Yes,It is correct under u-boot.
In addition, please check 4.3 DIO MCAL+Linux test in the training document, which also suggests the A core driver stops after loading SPI.
I tried to remove the corresponding nodes from kernel DTS earlier. However, I do not know why A core will not start directly. Could you please tell me some detailed operations?

Re: Using the S32g274rdb2 development board to debug the bootloader

chenyin_h — Wed, 28 Aug 2024 04:30:34 GMT

Hello, @sdx111

Thanks for the reply.

I assume that you are using the DIO example as the M core application to flash the LED, right? I remember that only GPIO6 is used in that example.

If you have disabled the corresponding pin in kernel, it seems odd that the Linux booting is impacted. May I know if your bootloader could boot the A core side properly if not booting the M core side simultaneously?

Let me summarize the status, correct me if any misunderstanding made, if any, I do apologize.

1. The LED keep flashing when enter u-boot.

2. When entering the kernel, if only changed the state of SPI1 in kernel dts to disable, the kernel could boot correctly but the LED stop flashing.

3. When entering the kernel, if only removing the corresponding nodes from kernel DTS, the kernel could not boot correctly, right? how about the LED status?

At last, I remeber that the DIO example's code will blink the LED for some time, and do not flash at last, may I know if you were actually using the Dio_ToggleLed_S32G274A_M7 example from which version of RTD?

Chenyin

Re: Using the S32g274rdb2 development board to debug the bootloader

sdx111 — Mon, 02 Sep 2024 08:28:39 GMT

I am using the DIO example as the M core application to flash the LED.
My bootloader could boot the A core side properly if not booting the M core side simultaneously.

1. The LED keep flashing when enter u-boot.
Yes

2. When entering the kernel, if only changed the state of SPI1 in kernel dts to disable, the kernel could boot correctly but the LED stop flashing.
Yes

3. When entering the kernel, if only removing the corresponding nodes from kernel DTS, the kernel could not boot correctly. LED keep flashing.

We changed the DIO example to always flash.

Re: Using the S32g274rdb2 development board to debug the bootloader

chenyin_h — Tue, 03 Sep 2024 06:52:58 GMT

Hello, @sdx111

Thanks for your reply.

Well, commonly such A&M booting issue is caused by the resource conflicts, including clock, memory, pinmux, etc.

Let me try it later to see if it could be reproduced, if any findings made, I will update you, besides, I suggest continue checking any possible conflicts one by one according to your own implementation.

Chenyin