S32G3 RDB3 u-boot suppoting EL2

[khan_misbah]

Currently the u-boot image generated while building the yocto project for RDB is capable to booting Linux kernel in EL1 mode. When cant boot a Hypervisor image using it.

What configuration or change is required to force u-boot to launch the OS in Hypervisor mode.

[chenyin_h]

Hello, @khan_misbah 

Thanks for the reply.

I have looked into the issue via the link you mentioned, and noticed that the issue has been handled by your local NXP FAE, he is now working on it and may reply you later either via the thread you posted or directly contact with you via mails.

Thanks.

BR

Chenyin 

[chenyin_h]

Hello, @khan_misbah 

You are welcome, yes, in previous old BSPs, the u-boot could not load next level images running under BL2 with default settings.

I suggest trying the BSP42 and then to check if there are similar issues like what you had done on BSP34 and/or 37.

If still issues existed, we could continue the discussion on it.

BR

Chenyin

[khan_misbah]

We tried to switch to BSP42 but facing issue in launching elf binary image. The same binary was working fine with BSP34/BSP37. Reported the issue earlier, please find the link as:


https://community.nxp.com/t5/S32G/S32G3RDB3-with-BSP42-not-able-to-Boot-Image/td-p/2039501

Can you please suggest.

[chenyin_h]

Hello, @khan_misbah 

Thanks for your post.

May I know which version BSP currently used? as far as I know, from BSP42,  U-Boot starts the Kernel image in EL2 mode to allow running either Linux Kernel or a Hypervisor.

As a result, I suggest using BSP42 for your specific test.

BR

Chenyin

[khan_misbah]

Thank you for your reply.

I am using BSP34 & BSP37.

I can launch my OS (Microkernel based) on i.MX8 h/w both as OS & Hypervisor (when built for OS/Hypervisor) . But when i try to launch the same OS on S32G3 RDB3 h/w it is not loading as hypervisor (EL2) but can only get launched in EL1.

In EL1 mode also there is an issue that we are facing with respect to MMU & update of ttbr0_el1 specially on RDB3 hardware, but works perfectly well on i.MX8 both being cortex-a53 arch.

The detail of the issue as reported at:

https://community.nxp.com/t5/S32G/S32G3-u-boot-loading-OS-in-EL1-with-mmu-not-working-properly/m-p/2...

We will try to built BSP42 and check, But if NXP has any suggestion on the above issue would be great, because we are evaluating multiple h/w platform for our new OS and facing challenges with S32G3.

[khan_misbah]

Dear NXP community members,

As per our previous discussion we understood that BSP34's u-boot is not able to load OS in EL2 mode & it is confirmed by NXP technical team that there is a limitation in BSP34's u-boot. We tested BSP42 and it can load the OS built in EL2 mode in S32G-RDB3 board.

The issue is we have custom s32g3 based hardware ported with BSP34 & we need to run OS in EL2 mode. Porting BSP42 requires a lot of work & testing, qualification etc ... also the u-boot in BSP42 is different version.

We need a patch in u-boot with which we can use the BSP34 to load OS in EL2 mode. It could be some change in assembly code etc that can be used in BSP34 to make it load EL2 OS.

Can you please support with the solution as we are blocked.