theobroma systems RK3399-Q7, User Manual

Page: 34 / 52

If you want to step through the sequence manually or customize it, you can execute the following commands on the U-Boot
prompt:
setenv bootargs console = tty0 console = ttyS2, 115200 root =/ dev / mmcblk1p1 rw rootwait
ext4load mmc 0 : 1 0x40008000 boot / uImage
ext4load mmc 0 : 1 0x40000000 boot / rk3399 - puma . dtb
bootm 0x40008000 - 0x40000000
Optionally, these commands can be compiled together in a single command and saved so it is performed on every subse-
quent boot:
setenv boot_sd "ext4load mmc 0:1 0x40008000 boot/uImage
ext4load mmc 0 : 1 0x40000000 boot / rk3399 - puma . dtb
bootm 0x40008000 - 0x40000000 "
setenv bootcmd "run boot_sd"
saveenv
To reset the U-Boot settings to default, execute:
env default - f - a
saveenv
4.10 Deploy on NOR-flash
To have a reliable boot sequence even if eMMC and/or SD-card fail, U-Boot can be written in to the onboard NOR-flash.
The file ‘’spl.img” for this has to be built differently than before.
Compile using:
cd puma - u - boot
export CROSS_COMPILE =/ opt / gcc - linaro - 6.3 . 1 - 2017.02 - x86_64_aarch64 - linux - gnu / bin / aarch64 - linux - gnu -
sudo make puma - rk3399_defconfig
sudo make - j4
sudo tools / mkimage - n rk3399 - T rkspi - d spl / u - boot - spl . bin spl . img
U-boot:
sf probe
load mmc 1 $kernel_addr_r root/spl.img
sf erase 0 +$filesize
sf write $kernel_addr_r 0 $filesize
Release v0.2-3-g574c114
Page 30