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