docs/plat/rpi3.rst

28 This explains why it is possible to change the execution state (AArch64/AArch32)
35   SD card, it will load it and execute in EL2 in AArch64. Basically, it executes
38 - If there is also a file called ``armstub8.bin``, it will load it at address
39   **0x0** (instead of the default stub) and execute it in EL3 in AArch64. All
43 `Raspbian`_ distribution by renaming it to ``kernel8.img``, while TF-A and
45 default bootstrap code. When using a AArch64 kernel, it is only needed to make
53 To get the most out of a AArch32 kernel, we want to boot it in Hypervisor mode
56 is used for EL2. When using a AArch64 kernel, it should simply start in EL2.
66 file, but we can specify the address it is loaded to in ``config.txt``.
76     that it is loaded above 32MiB in order to avoid the need to relocate
91 **0x00000000** to **0x3F000000**, it just has different names to simulate a real
131 so that the kernel doesn't use it. The current port tries to modify the live DTB
136 instructions to see how to do it. This system is strongly discouraged.
150 kernel. In that case, BL33 is booted in AArch32 Hypervisor mode so that it
151 can jump to the kernel in the same mode and let it take over that privilege
153 TF-A) it could only jump to the kernel in AArch32 in Supervisor mode.
167 the system off, it simply reboots it and asks the VideoCore firmware to keep it
170 The kernel used by `Raspbian`_ doesn't have support for PSCI, so it is needed to
181 Once BL31 has finished and the primary core has jumped to the BL33 payload, it
184 from the kernel. When the primary CPU jumps into the kernel, it will send an
185 address to the mailbox so that the secondary CPUs jump to it and are recognised
206   in AArch64 mode. If set to 1, it will jump to BL33 in Hypervisor in AArch32
213   ``config.txt``. It doesn't have to contain a kernel, it could have any
219   ``PRELOADED_BL33_BASE`` will most likely be needed as well because it is
274      If OP-TEE is used it may be needed to add the following options to the
281   it. In order to use TBB, you might want to set ``GENERATE_COT=1`` to let the
361 filesystem are 32-bit binaries, but it's a quick way to get it working, and it
372 2. Configure and compile the kernel. Adapt the number after ``-j`` so that it is
416    bootloader will look for a file called ``armstub8.bin`` and load it at
432 to it (for example, with ``screen /dev/ttyUSB0 115200``) you should see some