S32G3 Bootloader only starts A core with hse feature through qspi boot mode

[Quincy_Wen]

Hi NXP,

If I want to use Bootloader to start the A-core image with hse feature normally, what should I do?Are there any examples or documentation to refer to? Am I missing some configuration or steps? Do you have any suggestions?

Referring to AN13750, I can use this Bootloader to successfully start the A-core image without HSE feature. The A-core image with HSE feature can also be started normally from the SD card boot mode. However, it fails to use Bootloader through qspi boot. The phenomenon is that uart0 has no output.

BSP40 hse is compiled through yocto, as follows:

DISTRO_FEATURES:append = " hse "
DISTRO_FEATURES:append = " pkcs11-hse "
NXP_FIRMWARE_LOCAL_DIR = "/home/work/NXP/fsl-auto-yocto-bsp/downloads"
HSE_VERSION = "0_2_22_0"
HSE_LIC = "license.rtf"
HSE_SOC_REV = "rev1.1"
HSE_LIC_MD5 = "a1bda359fc5cdcfca04f84834841a5ca"

EB's Bootloader configuration is as follows:

Reset handler address :0x34085000  Load image at address (RAM) :0x3407b2c0

SW:

EB tresos Studio27.1

Integration_Reference_Examples_S32G3_2023_02

SW32_RTD_4.4_4.0.0

BSP40

HSE_FW_S32G3XX_0_2_22_0

HW: S32G399A-RDB3

Best regards,
Quincy

[ashwini2024]

Hello @Quincy_Wen ,
I would like to know about your configurations on EB and on A core side. Could you please provide those details , if possible ?
Could you share the docs you referred ?

Thank you.

[ashwini2024]

Hello @Quincy_Wen @Daniel-Aguirre ,

I am facing the similar issue. Could you please tell me at which address u had configured the HSE-FW ??
I am configuring hse at 0x1200 in bootloader
Please could u give me the details?

[Quincy_Wen]

Because the time interval is too long, I can't remember the details.

But luckily I found the blob image, as shown in the screenshot, you can refer to it

[ashwini2024]

Hello @Quincy_Wen ,

Could you tell me what configurations or changes you had done on A53 core ?

Thank you.

[ashwini2024]

@Quincy_Wen 

Thank you so much for the reply.
The following is my image layout after enabling hse on a core :

The following shows my blob:

The following is the Eb configurations :

But when i flash the

• Bootloader: Address 0x0
• A-core Application: Flashed at 0x200000
• M-core Application: Flashed at 0x400000
  
  The output is stuck and does not transition to u-boot as shows :
  
  Could you please let me know the issue?
  

[Quincy_Wen]

Perhaps there is an issue with your EB configuration. For example, the value of the source address (QSPI) at 0x264ee0 should be changed to 0x200000. Additionally, you need to pay attention to the requirement of 1KB alignment, although it might also be 4KB alignment (different flashes have different alignment requirements).

[ashwini2024]

Hello @Quincy_Wen 

Thank you for the reply.
1)I changed the source address to 0x200000 but i am observing the same, control does not go to u-boot
2)Could you please elaborate more on the alignment, were u referring to A core alignment or was it on the bootloader side ?

[Quincy_Wen]

It means that the starting addresses of the HSE-FW and SYS-IMG stored on the flash should be multiples of 1KB. For example, my HSE starts at 0x1000.

[ashwini2024]

Thanks for the reply @Quincy_Wen .

I gave the source address at qspi as 0x200000.But i am still facing the same issue.
Could you please suggest on that ?

[Quincy_Wen · Accepted solution]

The problem has been solved.The reason is that I didn't set the correct address of HSE-FW.

[ashwini2024]

Could you please tell me the changes u did or what addresses u configured for HSE-FW in the ivt

[ashwini2024]

@Quincy_Wen 

Could you please tell me the changes u did or what addresses u configured for HSE-FW in the ivt?

[ashwini2024]

I would want to know what you did to enable hse throuh sd card boot mode .
What did u update in local.conf ?
Or any other modifications which u did ?
Which firmware u used ?

[ashwini2024]

The A-core image with HSE feature can also be started normally from the SD card boot mode.
[AG] : how did you achieve the above ? could you please elaborate on that ?
PLease do reply.
Thank you.

[Quincy_Wen]

You can refer S32G3 : how to use HSE in linux-A53 - NXP Community

But you have to calculate the MD5 value of "license.rtf" by yourself.

[ashwini2024]

I am using bsp 40 and the board i am using is s32g399ardb3.
In my local.conf i have added following :
DISTRO_FEATURES:append = " hse "
NXP_FIRMWARE_LOCAL_DIR = "/yocto-s32g3/folder"
HSE_VERSION="0_2_22_0"
HSE_SOC_REV="rev1.0"
HSE_LIC_MD5 = "a1bda359fc5cdcfca04f84834841a5ca"
But i am not finding any logs in target machine I get the below result :

[ashwini2024]

Thank you for your response.

[ashwini2024]

Are u able to find logs for sd card boot mode?

[Daniel-Aguirre]

Hi,

We understand that AN13750 only provides the steps to implement a secure boot with HSE-FW, since a patch is provided for the Bootloader.c file as well as including the HSE-FW under the IVT.

Have you confirmed that all steps are followed under AN13750? Since your BSP version is different from the one being shown under AN13750, care should be taken.

Please, let us know.

[Quincy_Wen]

Hi Daniel，

Thank you for your prompt reply.Yes, I have confirmed that all steps are followed under AN13750.Moreover, I am familiar with AN13750 and have successfully implemented multicore applications on both RDB2 and RDB3 by following the documentation. As I mentioned earlier, I can boot an A-core image without the hse feature using the Bootloader, so I can confirm that all my steps are followed under AN13750. However, it should be clarified that I didn't enable secure boot. Could this affect booting an A-core image with hse enabled?Do you have any suggestions on how to implement the title?

Best regards,
Quincy