rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-05-15 02:57:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

user/zynqmp-rpu: Update boot suggestion

Browse Source 
Change the development suggestion for booting the R5 since the R5 u-boot
is only minimally functional without significant development. This also
adds caveats when booting the R5 cores from the A53.
This commit is contained in:
Kinsey Moore 2024-02-18 19:39:40 -06:00 committed by Joel Sherrill
parent 204ac80935
commit 24cce927ed
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
user/bsps/arm/xilinx-zynqmp-rpu.rst
View File

@ -31,8 +31,18 @@ Boot on ZynqMP Hardware
On the ZynqMP RPU, RTEMS can be started by Cortes-R5 u-boot, Cortex-A53 u-boot,
via JTAG, or directly as part of BOOT.bin. For quick turnaround during testing,
it is recommended to use Cortex-R5 u-boot to avoid repeated BOOT.bin generation
and to ensure that the Cortex-R5 FSBL is run.
it is recommended to use Cortex-A53 u-boot to avoid repeated BOOT.bin
generation since the provided Cortex-R5 u-boot is highly limited and has no
network or MMC/SD access.
Note that if the RPU image is started by the Cortex-A53 u-boot, the BSP
configuration must be updated to move ZYNQMP_RPU_RAM_INT_0_ORIGIN and
ZYNQMP_RPU_RAM_INT_1_ORIGIN into DDR since the TCMs are not directly available
to the Cortex-A53 cores at their Cortex-R5 internal addresses. Alternatively,
those sections could be copied to the TCMs using their global addresses, but
this must be done using additional commands within u-boot. If this is not taken
into account, the Cortex-R5 CPU will fail to boot correctly since execution
will jump into uninitialized TCM.
Hardware Boot Image Generation
------------------------------