On 26 July 2017 at 04:40, Philipp Tomsich
<philipp.toms...@theobroma-systems.com> wrote:
> For the RK3368, we use a multi-stage boot-process consisting of the
> following:
>   1.  TPL: initalises DRAM, returns to boot-ROM (which then loads
>            the next stage and transfers control to it)
>   2.  SPL: a full-features SPL stage including OF_CONTROL and FIT
>            image loading, which fetches the ATF, DTB and full U-Boot
>            and then transfers control to the ATF (using the BL31
>            parameter block to indicate the location of BL33/U-Boot)
>   3.  ATF: sets up the secure world and exits to BL33 (i.e. a full
>            U-Boot) in the normal world
>   4.  full U-Boot
>
> TPL/SPL and the full U-Boot are built from this tree and need to
> run from distinct text addresses and with distinct initial stack
> pointer addresses.
>
> This commit sets up the configuration to run:
>   -  TPL from the SRAM at 0xff8c0000 (note that the first 0x1000
>          are reserved for use by the boot-ROM and contain the SP
>          when the TPL is entered)
>   -  SPL from DRAM at 0x0
>   -  U-Boot from DRAM at 0x200000
>
> Signed-off-by: Philipp Tomsich <philipp.toms...@theobroma-systems.com>
> ---
>
> Changes in v2: None
>
>  include/configs/rk3368_common.h | 11 +++++++++++
>  1 file changed, 11 insertions(+)

Reviewed-by: Simon Glass <s...@chromium.org>
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to