Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 349 subscribers
  • Views 2796 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

EL3 execution

segfault

Hello Experts,

I need to operate a custom app at EL3 on a Cortex-A53 core running on the i.MX8 based  platform. The bootflow shows me that a hand-off from ATF (BL31) to U-boot (BL33) is where the transition from EL3 to EL2 occurs for Uboot and it stays at EL2.

Can anyone suggest a procedure or mechanism to keep the Uboot and custom apps running at EL3? Are there any examples ?

Thanks in advance.

Parents
  • 0 in reply to Martin Weidmann

    Thanks for the reply. The EL3 requirement is imposed by the BSP vendor supplying the RTOS. At this time the purpose is not clear. Currently, I can see U-boot operating after BL31 handoff at EL2.

    Can you suggest what can be customized in BL31 (ATF) for initial experiments?

    I tried some mods to BL31 code to avoid the EL2 setup but that appears to fail. 

Reply
  • 0 in reply to Martin Weidmann

    Thanks for the reply. The EL3 requirement is imposed by the BSP vendor supplying the RTOS. At this time the purpose is not clear. Currently, I can see U-boot operating after BL31 handoff at EL2.

    Can you suggest what can be customized in BL31 (ATF) for initial experiments?

    I tried some mods to BL31 code to avoid the EL2 setup but that appears to fail. 

Children