1Rockchip SoCs 2============= 3 4Trusted Firmware-A supports a number of Rockchip ARM SoCs from both 5AARCH32 and AARCH64 fields. 6 7This includes right now: 8- px30: Quad-Core Cortex-A53 9- rk3288: Quad-Core Cortex-A17 (past A12) 10- rk3328: Quad-Core Cortex-A53 11- rk3368: Octa-Core Cortex-A53 12- rk3399: Hexa-Core Cortex-A53/A72 13- rk3566/rk3568: Quad-Core Cortex-A55 14- rk3576: Octa-Core Cortex-A53/A72 15- rk3588: Octa-Core Cortex-A55/A76 16 17 18Boot Sequence 19------------- 20 21For AARCH32: 22 Bootrom --> BL1/BL2 --> BL32 --> BL33 --> Linux kernel 23 24For AARCH64: 25 Bootrom --> BL1/BL2 --> BL31 --> BL33 --> Linux kernel 26 27BL1/2 and BL33 can currently be supplied from either: 28- Coreboot + Depthcharge 29- U-Boot - either separately as TPL+SPL or only SPL 30 31 32How to build 33------------ 34 35Rockchip SoCs expect TF-A's BL31 (AARCH64) or BL32 (AARCH32) to get 36integrated with other boot software like U-Boot or Coreboot, so only 37these images need to get build from the TF-A repository. 38 39For AARCH64 architectures the build command looks like 40 41 make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31 42 43while AARCH32 needs a slightly different command 44 45 make ARCH=aarch32 CROSS_COMPILE=arm-linux-gnueabihf- PLAT=rk3288 AARCH32_SP=sp_min bl32 46 47Both need replacing the PLAT argument with the platform from above you 48want to build for and the CROSS_COMPILE argument with you cross- 49compilation toolchain. 50 51 52How to deploy 53------------- 54 55Both upstream U-Boot and Coreboot projects contain instructions on where 56to put the built images during their respective build process. 57So after successfully building TF-A just follow their build instructions 58to continue. 59