Difference between revisions of "U-Boot"

From Rockchip open source Document
Jump to: navigation, search
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  
 
= Download U-Boot =
 
= Download U-Boot =
 +
  
 
== Upstream U-Boot ==
 
== Upstream U-Boot ==
  
 
You can clone the u-boot repository by running:
 
You can clone the u-boot repository by running:
<pre>git clone git://git.denx.de/u-boot.git</pre>
+
<pre>git clone https://gitlab.denx.de/u-boot/u-boot.git</pre>
  
 
Alternatively you can use u-boot-rockchip instead which may with some patches not get in mainline:
 
Alternatively you can use u-boot-rockchip instead which may with some patches not get in mainline:
<pre>git clone git://git.denx.de/u-boot-rockchip.git</pre>
+
<pre>git clone https://gitlab.denx.de/u-boot/custodians/u-boot-rockchip.git</pre>
  
 
&nbsp;
 
&nbsp;
Line 17: Line 18:
 
<pre>git clone https://github.com/rockchip-linux/u-boot.git
 
<pre>git clone https://github.com/rockchip-linux/u-boot.git
 
</pre>
 
</pre>
 +
  
 
= Supported Devices =
 
= Supported Devices =
Line 32: Line 34:
  
 
#EVB RK3288 - use evb-rk3288 configuration  
 
#EVB RK3288 - use evb-rk3288 configuration  
#Fennec RK3288 - use fennec-rk3288 configuration
 
 
#Firefly RK3288 - use firefly-rk3288 configuration  
 
#Firefly RK3288 - use firefly-rk3288 configuration  
 
#Hisense Chromebook - use chromebook_jerry configuration  
 
#Hisense Chromebook - use chromebook_jerry configuration  
Line 50: Line 51:
 
*RK3399 boards&nbsp;supported:  
 
*RK3399 boards&nbsp;supported:  
  
#EVB RK3399 - use evb-rk3399 configuration  
+
#EVB RK3399 - use evb-rk3399 configuration
  
 
= Get a toolchain =
 
= Get a toolchain =
Line 67: Line 68:
 
<pre>https://github.com/rockchip-linux/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu.git</pre>
 
<pre>https://github.com/rockchip-linux/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu.git</pre>
  
= Configure U-Boot =
+
= Build U-Boot =
 +
 
 +
== Configure U-Boot ==
  
 
First you need to choose a correct defconfig for your board;
 
First you need to choose a correct defconfig for your board;
Line 81: Line 84:
  
 
&nbsp;
 
&nbsp;
 
 
= Build U-Boot =
 
  
 
== Buid Rockchip U-Boot ==
 
== Buid Rockchip U-Boot ==
  
For&nbsp;convenience, Rockchip provide a &nbsp;script 'make.sh' to make it easy to get everything before kernel, this script need toolchain and [[Rkbin|rkbin]] support.
+
For&nbsp;convenience, Rockchip provide a &nbsp;script 'make.sh' to make it easy to get everything before kernel, this script need toolchain and [https://github.com/rockchip-linux/rkbin rkbin] support.
 
<pre>├── prebuilts
 
<pre>├── prebuilts
 
│  └── gcc
 
│  └── gcc
Line 107: Line 107:
 
└── uboot.img</pre>
 
└── uboot.img</pre>
  
== Common Build Steps ==
+
&nbsp;
 +
 
 +
== Build Upstream U-Boot ==
  
 
This is common and available for both Upstream U-Boot and Rockchip U-Boot.
 
This is common and available for both Upstream U-Boot and Rockchip U-Boot.
Line 120: Line 122:
 
<pre>CFLAGS='-gdwarf-3'</pre>
 
<pre>CFLAGS='-gdwarf-3'</pre>
  
You can get available u-boot.bin, spl/u-boot-spl.bin, tpl/u-boot-tpl.bin at this step, and you need to package it with tool before use with rockchip upagrade tool. Get detail at&nbsp;[http://opensource.rock-chips.com/wiki_Boot_option boot option].
+
The output including u-boot.bin, spl/u-boot-spl.bin, tpl/u-boot-tpl.bin at this step, and you need to package it with mkimage tool before use with rockchip upagrade tool. Get detail at&nbsp;[http://opensource.rock-chips.com/wiki_Boot_option boot option].
  
 
'''Support ATF with SPL FIT image'''
 
'''Support ATF with SPL FIT image'''
  
For trust support, we are using FIT image with 'mkimage' cmd in Makefile and its script defined in defconfig:
+
For trust support in SPL, we are using FIT image with 'mkimage' cmd in Makefile and its script defined in defconfig:
 
<pre>make u-boot.itb</pre>
 
<pre>make u-boot.itb</pre>
  
Note: please copy the trust binary() to u-boot root directory and rename it to tee.bin(armv7) or bl31.elf(armv8).
+
Note: please copy the trust binary(optee.bin or bl31.elf from rkbin project) to u-boot root directory and rename it to tee.bin(armv7) or bl31.elf(armv8).
  
The u-boot.itb is a its based package including u-boot-nodtb.bin, board.dtb, and trust binaries which can be used directly with upgrade tool.
+
The output u-boot.itb is a its based package including u-boot-nodtb.bin, board.dtb, and trust binaries which can be used directly with upgrade tool.
 
<pre>├── u-boot  
 
<pre>├── u-boot  
 
│  ├── u-boot.bin
 
│  ├── u-boot.bin
Line 140: Line 142:
 
= Install U-Boot =
 
= Install U-Boot =
  
Rockchip SoCs's bootrom need special format named IDBlock at special offset 0x40&nbsp;block for boot, so we need to package&nbsp;SPL(or Rockchip miniloader) &nbsp;in IDB format.
+
See&nbsp;[http://opensource.rock-chips.com/wiki_Boot_option boot option]&nbsp;about how to
  
Rockchip bootrom supports SPL back to bootrom and bootrom load the U-Boot, so the SPL for Rockchip SoCs can option to back to bootrom, usually decided by if the IRAM is enough&nbsp;for driver to load U-Boot.
+
- package the available binaries
  
&nbsp;
+
- flash and boot from eMMC/SD card.
  
== Using U-Boot SPL ==
 
  
After build&nbsp;complete, U-Boot with SPL support will generate a spl folder with&nbsp;<var>u-boot-spl.bin</var>&nbsp;inside
 
<pre>tools/mkimage -n rk3288 -T rksd -d spl/u-boot-spl.bin idbloader.img</pre>
 
  
'''This image is supposed to flash to offset 0x40.'''
+
= Boot cmd =
 
 
For&nbsp;<var>u-boot.bin</var>, it's different for SPL back to bootrom or not, if enable&nbsp;CONFIG_ROCKCHIP_SPL_BACK_TO_BROM, we can append the U-Boot to IDB data:
 
<pre>cat u-boot.bin >> idbloader.img</pre>
 
 
 
<code>If&nbsp;</code>CONFIG_ROCKCHIP_SPL_BACK_TO_BROM&nbsp;not enabled, no more package operation is need for u-boot-dtb.bin, and it need to flalsh to 0x200 which is decide by&nbsp;CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR.
 
 
 
== Using Rockchip miniloader ==
 
 
 
Alternatively, you can use Rockchip miniloader and U-Boot instead which do not need SPL.
 
  
The miniloader is package as IDBlock, and the u-boot.bin need to package with rockchip tool:
+
Rockchip U-Boot supports image type:
<pre>loaderimage --pack --uboot u-boot.bin uboot.img</pre>
 
  
According to the&nbsp;[http://opensource.rock-chips.com/wiki_Partitions partitions]&nbsp;definition, the miniloader should write to offset 0x40 and &nbsp;this uboot.img should write to offset 0x4000.
+
Android boot(boot_android), Rockchip RKIMG boot(boot_rockchip) and LInux distro boot(distro_bootcmd).
  
&nbsp;
+
Upstream U-Boot supports image type::
  
== Boot up ==
+
Linux distro boot(distro_bootcmd).
 
 
See&nbsp;[http://opensource.rock-chips.com/wiki_Boot_option boot option]&nbsp;about how to boot from eMMC/SD card.
 
 
 
= Boot cmd =
 
 
 
Rockchip U-Boot Android boot, Rockchip RKIMG boot and Distro boot.
 
 
 
Upstream U-Boot suppot distro boot.
 
  
 
= Firmware download in U-Boot =
 
= Firmware download in U-Boot =
  
In U-Boot, there are multi way to update image for system, you can chose any of one easy use for you.
+
In U-Boot, there are multi way to update image into emmc via U-Boot, you can chose any of one easy use for you.
 
 
== fastboot ==
 
  
See&nbsp;[http://opensource.rock-chips.com/wiki_Fastboot fastboot]
+
fastboot:&nbsp;See&nbsp;[http://opensource.rock-chips.com/wiki_Fastboot fastboot]
  
== rockusb ==
+
rockusb: See [[Rockusb|rockusb]]

Latest revision as of 06:39, 4 September 2019

Download U-Boot

Upstream U-Boot

You can clone the u-boot repository by running:

git clone https://gitlab.denx.de/u-boot/u-boot.git

Alternatively you can use u-boot-rockchip instead which may with some patches not get in mainline:

git clone https://gitlab.denx.de/u-boot/custodians/u-boot-rockchip.git

 

Rockchip U-Boot

You can clone the u-boot repository by running:

git clone https://github.com/rockchip-linux/u-boot.git


Supported Devices

Upstream U-Boot support Rockchip SoCs:

RK3036, RK3188, RK3288RK3328RK3399

  • RK3036 boards supported:
  1. EVB RK3036 - use evb-rk3036 configuration
  2. Kylin - use kylin_rk3036 configuration
  • RK3288 boards supported:
  1. EVB RK3288 - use evb-rk3288 configuration
  2. Firefly RK3288 - use firefly-rk3288 configuration
  3. Hisense Chromebook - use chromebook_jerry configuration
  4. Miniarm RK3288 - use miniarm-rk3288 configuration
  5. PopMetal RK3288 - use popmetal-rk3288 configuration
  6. Radxa Rock 2 - use rock2 configuration
  7. ASUS Tinker
  • RK3188 boards supported:
  1. Radxa Rock - use rock configuration
  • RK3328 boards supported:
  1. EVB RK3328 - use evb-rk3328 configuration
  • RK3399 boards supported:
  1. EVB RK3399 - use evb-rk3399 configuration

Get a toolchain

If you haven't done so before, get a suitable toolchain installed and add it to your PATH.

In Ubuntu 14.04, you can use below command to install cross compiler for armv7:

sudo apt-get install gcc-arm-linux-gnueabi

Or for ARM64

sudo apt-get install gcc-aarch64-linux-gnu

Note that the latest U-Boot require version gcc-5.0 and later, we recommand to use linaro 6.3.1.

https://github.com/rockchip-linux/gcc-linaro-6.3.1-2017.05-x86_64_arm-linux-gnueabihf.git
https://github.com/rockchip-linux/gcc-linaro-6.3.1-2017.05-x86_64_aarch64-linux-gnu.git

Build U-Boot

Configure U-Boot

First you need to choose a correct defconfig for your board;

When you have determined what <board_name> you want to build, configure:

make CROSS_COMPILE=arm-linux-gnueabi- <board_name>_defconfig

You may need to change the U-Boot function/feature support by modify the defconfig file or,

there is also menuconfig to play with settings if you feel like it:

make CROSS_COMPILE=arm-linux-gnueabi- menuconfig

 

Buid Rockchip U-Boot

For convenience, Rockchip provide a  script 'make.sh' to make it easy to get everything before kernel, this script need toolchain and rkbin support.

├── prebuilts
│   └── gcc
│       └── linux-x86 
│           ├── aarch64
│           └── arm
├── rkbin
├── u-boot

expample for build rk3399:

./make.sh rk3399

and use './make.sh -h' for more option.

The output will including pre-loader, trust and u-boot image which is ready to use with rockchip upgrade tool, 

u-boot/
├── rk3399_loader_v1.09.112.bin
├── trust.img
└── uboot.img

 

Build Upstream U-Boot

This is common and available for both Upstream U-Boot and Rockchip U-Boot.

For armv7:

make CROSS_COMPILE=arm-linux-gnueabi-

or for ARM64:

make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu-

In order to support debug symbol in ARM DS-5, you may need add ctags in make command:

CFLAGS='-gdwarf-3'

The output including u-boot.bin, spl/u-boot-spl.bin, tpl/u-boot-tpl.bin at this step, and you need to package it with mkimage tool before use with rockchip upagrade tool. Get detail at boot option.

Support ATF with SPL FIT image

For trust support in SPL, we are using FIT image with 'mkimage' cmd in Makefile and its script defined in defconfig:

make u-boot.itb

Note: please copy the trust binary(optee.bin or bl31.elf from rkbin project) to u-boot root directory and rename it to tee.bin(armv7) or bl31.elf(armv8).

The output u-boot.itb is a its based package including u-boot-nodtb.bin, board.dtb, and trust binaries which can be used directly with upgrade tool.

├── u-boot 
│   ├── u-boot.bin
│   ├── u-boot.itb
│   ├── spl
│   │   └── u-boot-spl.bin
│   └── tpl 
│       └── u-boot-tpl.bin

Install U-Boot

See boot option about how to

- package the available binaries

- flash and boot from eMMC/SD card.


Boot cmd

Rockchip U-Boot supports image type:

Android boot(boot_android), Rockchip RKIMG boot(boot_rockchip) and LInux distro boot(distro_bootcmd).

Upstream U-Boot supports image type::

Linux distro boot(distro_bootcmd).

Firmware download in U-Boot

In U-Boot, there are multi way to update image into emmc via U-Boot, you can chose any of one easy use for you.

fastboot: See fastboot

rockusb: See rockusb