On 18 July 2016 at 02:46, Kever Yang <kever.y...@rock-chips.com> wrote: > Add a README to guide people flash the ATF and U-Boot > with rockchip tools to bring up to board. > > Signed-off-by: Kever Yang <kever.y...@rock-chips.com> > --- > > Changes in v4: None > Changes in v3: None > Changes in v2: > fix a binary path error > > board/rockchip/evb_rk3399/README | 73 > ++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 73 insertions(+) > create mode 100644 board/rockchip/evb_rk3399/README
Looks good, but please see nits below. > > diff --git a/board/rockchip/evb_rk3399/README > b/board/rockchip/evb_rk3399/README > new file mode 100644 > index 0000000..af4e45e > --- /dev/null > +++ b/board/rockchip/evb_rk3399/README > @@ -0,0 +1,73 @@ > +Introduction > +============ > + > +RK3399 key feature we might use in u-boot: features > +* CPU: ARMv8 64bit Big-Little architecture, > +* Big: dual-core Cortex-A72 > +* Little: quad-core Cortex-A53 > +* IRAM: 200KB > +* DRAM: 4GB-128MB dual-channel > +* eMMC: support eMMC 5.0/5.1, suport HS400, HS200, DDR50 > +* SD/MMC: support SD 3.0, MMC 4.51 > +* USB: USB3.0 typc-C port *2 with dwc3 controller > +* USB2.0 EHCI host port *2 > +* Display: RGB/HDMI/DP/MIPI/EDP > + > +evb feature: > +* regulator: pwm regulator for CPU B/L > +* PMIC: rk808 > +* debug console: UART2 > + > +In order to support Arm Trust Firmware, we need to use the Arm Trust Firmware (ATF) > +miniloader from rockchip which: > +* do DRAM init > +* load&verify ATF image load and verify ATF image > +* load&verify u-boot image load and verify U-Boot image > + > +Here is the step by step to boot to U-boot on rk3399. step-by-step Please use 'U-Boot' consistently - check below also. > + > +Get the Source and prebuild binary > +================================== > + > + > mkdir ~/evb_rk3399 > + > cd ~/evb_rk3399 > + > git clone https://github.com/ARM-software/arm-trusted-firmware.git > + > git clone https://github.com/rockchip-linux/rkbin > + > git clone https://github.com/rockchip-linux/rkflashtool > + > +Compile the ATF > +=============== > + > + > cd arm-trusted-firmware > + > make realclean > + > make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31 > + > +Compile the u-boot > +================== > + > + > cd ../u-boot > + > make CROSS_COMPILE=aarch64-linux-gnu- evb-rk3399_defconfig all > + > +Compile the rkflashtool > +======================= > + > + > cd ../rkflashtool > + > make > + > +Package the image for miniloader > +================================ > + > cd .. > + > cp arm-trusted-firmware/build/rk3399/release/bl31.bin rkbin/rk33 > + > ./rkbin/tools/trust_merger rkbin/tools/RK3399TRUST.ini > + > ./rkbin/tools/loaderimage --pack --uboot u-boot/u-boot-dtb.bin uboot.img > + > mkdir image > + > mv trust.img ./image/ > + > mv uboot.img ./image/rk3399evb-uboot.bin > + > +Flash the image > +=============== > +Power on(or reset with RESET KEY) with MASKROM KEY preesed, and then: > + > + > ./rkflashtool/rkflashloader rk3399evb > + > +You should be able to get U-boot log message in console/UART2 now. > -- > 1.9.1 > > Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot