tkaratapanis opened a new pull request, #16458: URL: https://github.com/apache/nuttx/pull/16458
## Summary Originally the i.MX9 bootloader was only supposed to run at EL3. However in some scenarios, for instance in a TF-A deployment, the nuttx bootloader is the BL33 payload and runs at EL1. To make the bootloader run at EL1 we need to remove parts of the initialization that are only expected to happen at EL3. This PR is minimal, and doesn't auto select DDR training and FIQ decoding if `ARCH_ARM64_EXCEPTION_LEVEL != 3`. Additionally `arm64_chip_boot()` excludes `imx9_mix_powerup()`, `imx9_ccm_clock_init()`, `imx9_trdc_init()` and `imx9_dram_init()` if `ARCH_ARM64_EXCEPTION_LEVEL != 3` ## Impact Boards that already run the bootloader at EL3 behave exactly as before. Boards built with `ARCH_ARM64_EXCEPTION_LEVEL=1` will operate correctly, provided they are paired with an EL3-level bootloader that performs the required EL3 initialization. ## Testing **Hardware**: custom i.MX93 board **Build**: `CONFIG_IMX9_BOOTLOADER=y`, `ARCH_ARM64_EXCEPTION_LEVEL=1` + custom defconfig that matches the hardware characteristics of the board **Scenario**: Minimal EL3 nuttx bootloader as BL2, TF-A as BL31, an EL1 nuttx bootloader as BL33 which in turn boots a PX4 image **Result**: PX4 boots; serial console and user tasks run normally. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
