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 15 16Boot Sequence 17------------- 18 19For AARCH32: 20 Bootrom --> BL1/BL2 --> BL32 --> BL33 --> Linux kernel 21 22For AARCH64: 23 Bootrom --> BL1/BL2 --> BL31 --> BL33 --> Linux kernel 24 25BL1/2 and BL33 can currently be supplied from either: 26- Coreboot + Depthcharge 27- U-Boot - either separately as TPL+SPL or only SPL 28 29 30How to build 31------------ 32 33Rockchip SoCs expect TF-A's BL31 (AARCH64) or BL32 (AARCH32) to get 34integrated with other boot software like U-Boot or Coreboot, so only 35these images need to get build from the TF-A repository. 36 37For AARCH64 architectures the build command looks like 38 39 make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31 40 41while AARCH32 needs a slightly different command 42 43 make ARCH=aarch32 CROSS_COMPILE=arm-linux-gnueabihf- PLAT=rk3288 AARCH32_SP=sp_min bl32 44 45Both need replacing the PLAT argument with the platform from above you 46want to build for and the CROSS_COMPILE argument with you cross- 47compilation toolchain. 48 49 50How to deploy 51------------- 52 53Both upstream U-Boot and Coreboot projects contain instructions on where 54to put the built images during their respective build process. 55So after successfully building TF-A just follow their build instructions 56to continue. 57