Difference between revisions of "Boot option"

From Rockchip open source Document
Jump to: navigation, search
 
(18 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
  
 
= Boot introduce =
 
= Boot introduce =
Line 13: Line 14:
  
 
And [http://opensource.rock-chips.com/wiki_Partitions Rockcip Linux GPT partition] here.
 
And [http://opensource.rock-chips.com/wiki_Partitions Rockcip Linux GPT partition] here.
 +
 +
 
  
 
== Boot flow ==
 
== Boot flow ==
  
Here is a table show the detail what we may use in Rockchip platform, for 2 boot stage:
+
This chapter introduce the generic boot flow for Rockchip Application Processors, including the detail about what image we may use in Rockchip platform for kind of boot path:
  
- use U-Boot SPL;
+
- use U-Boot TPL/SPL from upsream or rockchip U-Boot, fully source code;
  
- use Rockchp idbLoader which is combinded by Rockchip ddr init bin and miniloader bin;
+
- use Rockchp idbLoader which is combinded by Rockchip ddr init bin and miniloader bin from Rockchip [https://github.com/rockchip-linux/rkbin rkbin project];
 
<pre>+--------+----------------+----------+-------------+---------+
 
<pre>+--------+----------------+----------+-------------+---------+
| Boot  | Terminology #1 | Actual  | Rockchip    |         |
+
| Boot  | Terminology #1 | Actual  | Rockchip    | Image  |
| stage  |                | program  |  Image      |         |
+
| stage  |                | program  |  Image      | Location|
| number |                | name    |  Name      |         |
+
| number |                | name    |  Name      | (sector)|
 
+--------+----------------+----------+-------------+---------+
 
+--------+----------------+----------+-------------+---------+
 
| 1      |  Primary      | ROM code | BootRom    |        |
 
| 1      |  Primary      | ROM code | BootRom    |        |
Line 30: Line 33:
 
|        |  Loader        |          |            |        |
 
|        |  Loader        |          |            |        |
 
|        |                |          |            |        |
 
|        |                |          |            |        |
| 2      |  Secondary    | U-Boot  |idbloader.img| 0x40    |including u-boot if not use miniloader
+
| 2      |  Secondary    | U-Boot  |idbloader.img| 0x40    | pre-loader
|        |  Program      | SPL     |idbspl.img  |        |
+
|        |  Program      | TPL/SPL |             |        |
 
|        |  Loader (SPL)  |          |            |        |
 
|        |  Loader (SPL)  |          |            |        |
 
|        |                |          |            |        |
 
|        |                |          |            |        |
 
| 3      |  -            | U-Boot  | u-boot.itb  | 0x4000  | including u-boot and atf
 
| 3      |  -            | U-Boot  | u-boot.itb  | 0x4000  | including u-boot and atf
|        |                |          | u-boot.bin  | 0x4000  |
+
|        |                |          | uboot.img  |         | only used with miniloader
|        |                |          | uboot.img  | 0x4000  | only used with miniloader
 
 
|        |                |          |            |        |
 
|        |                |          |            |        |
|        |                | ATF     | trust.img  | 0x6000  | only used with miniloader for armv8
+
|        |                | ATF/TEE  | trust.img  | 0x6000  | only used with miniloader
 
|        |                |          |            |        |
 
|        |                |          |            |        |
 
| 4      |  -            | kernel  | boot.img    | 0x8000  |
 
| 4      |  -            | kernel  | boot.img    | 0x8000  |
Line 57: Line 59:
 
&nbsp;
 
&nbsp;
  
[[File:Rockchip bootflow.jpg|1000x1000px|Rockchip bootflow.jpg]]
+
[[File:Rockchip bootflow20181122.jpg|1000x1000px|Rockchip bootflow.jpg]]
  
Boot Flow 1 is typical Rockchip boot flow with Rockchip miniloader;<br/> Boot Flow 2 is used for most SoCs with U-Boot TPL for ddr init and SPL for trust(ATF/OP-TEE) load and run into next stage;<br/> Boot Flow 3 is use only for RK3399 with SPL ATF support;<br/> Boot Flow 4 is used for armv7 SoCs which do not support trust;<br/> <br/> Note 1. If loader1 have more than 1 stage, program will back to bootrom and bootrom load and run into next stage. eg. If loader1 is tpl and spl, the bootrom will run into tpl first, tpl init ddr and back to bootrom, bootrom then load and run into spl.<br/> Note 2. If trust is enabled, loader1 need to load both trust and u-boot, and then run into trust in secure mode(EL3 in armv8), trust do the initialize and run into U-Boot in non-secure mode(EL2 in armv8).<br/> Note 3. For trust(in trust.img or u-boot.itb), armv7 has only one tee.bin with or without ta, armv8 has bl31.elf and option with bl32.<br/> Note 4. In boot.img, content can be zImage and its dtb for Linux, and can optionally be grub.efi, and can be AOSP boot.img, ramdisk is option;
+
Boot Flow 1 is typical Rockchip boot flow with Rockchip miniloader;<br/> Boot Flow 2 is used for most SoCs with U-Boot TPL for ddr init and SPL for trust(ATF/OP-TEE) load and run into next stage;<br/> <br/> Note 1. If loader1 have more than 1 stage, program will back to bootrom and bootrom load and run into next stage. eg. If loader1 is tpl and spl, the bootrom will run into tpl first, tpl init ddr and back to bootrom, bootrom then load and run into spl.<br/> Note 2. If trust is enabled, loader1 need to load both trust and u-boot, and then run into trust in secure mode(EL3 in armv8), trust do the initialize and run into U-Boot in non-secure mode(EL2 in armv8).<br/> Note 3. For trust(in trust.img or u-boot.itb), armv7 has only one tee.bin with or without ta, armv8 has bl31.elf and option with bl32.<br/> Note 4. In boot.img, content can be zImage and its dtb for Linux, and can optionally be grub.efi, and can be AOSP boot.img, ramdisk is option;
  
 
== Package option ==
 
== Package option ==
Line 76: Line 78:
 
We offer two different boot-loader methods for different solutions, the steps and request files are also complete different. But not all the platforms supports the both boot-loader methods. Here are the types to&nbsp;package image from those files:
 
We offer two different boot-loader methods for different solutions, the steps and request files are also complete different. But not all the platforms supports the both boot-loader methods. Here are the types to&nbsp;package image from those files:
  
 +
&nbsp;
 +
 +
 +
 +
 +
 +
=== The Pre-bootloader(IDBLoader) ===
 +
 +
==== What is idbloader ====
  
 +
idbloader.img is a Rockchip format pre-loader suppose to work at SoC start up, it contains:
  
 +
- IDBlock header which is known by Rockchip BootRom;
  
 +
- DRAM init program which is load by MaskRom and running at internal SRAM;
  
=== The Pre-bootloader ===
+
- loader for next stage which is load by MaskRom and running at DDR SDRAM;
  
==== Rockchip Miniloader ====
+
You can get idbloader with below methods.
  
Package the image from Rockchip binary:
+
==== Get idbloader for eMMC from Rockchip release loader ====
  
No need to package a idbloader for eMMC because you can use below command to write idbloader from loader:
+
No need to package a idbloader.img for eMMC if you are using Rockchip release loader, you can get idbloader on eMMC with below command:
<pre>rkdeveloptool db rkxx_ddr_vx.xx.bin
+
<pre>rkdeveloptool db rkxx_loader_vx.xx.bin
rkdeveloptool ul rkxx_ddr_vx.xx.bin</pre>
+
rkdeveloptool ul rkxx_loader_vx.xx.bin</pre>
  
For SD boot, you need a idbloader(combinded with ddr and miniloader) to write to SD card.
+
==== Package the idbloader.img from Rockchip binary: ====
 +
 
 +
For SD boot or eMMC(update with rockusb wl cmd), you need a idbloader(combinded with ddr and miniloader) .
 
<pre>tools/mkimage -n rkxxxx -T rksd -d rkxx_ddr_vx.xx.bin idbloader.img
 
<pre>tools/mkimage -n rkxxxx -T rksd -d rkxx_ddr_vx.xx.bin idbloader.img
 
cat rkxx_miniloader_vx.xx.bin >> idbloader.img
 
cat rkxx_miniloader_vx.xx.bin >> idbloader.img
 
</pre>
 
</pre>
  
==== idbloader.img with tpl/spl ====
+
==== Package the idbloader.img from U-Boot&nbsp;TPL/SPL(which is fully open source): ====
 
<pre>tools/mkimage -n rkxxxx -T rksd -d tpl/u-boot-tpl.bin idbloader.img
 
<pre>tools/mkimage -n rkxxxx -T rksd -d tpl/u-boot-tpl.bin idbloader.img
 
cat spl/u-boot-spl.bin >> idbloader.img
 
cat spl/u-boot-spl.bin >> idbloader.img
 
</pre>
 
</pre>
  
==== idbspl.img ====
+
Flash the idbloader.img to offset 0x40 which including stage 2, and you will need a uboot.img for boot stage 3.
 
 
U-Boot SPL support ddr init and load data for next stage, only available in rk3399 now.
 
<pre>mkimage -n rkxxxx -T rksd -d spl/u-boot-spl.bin idbspl.img
 
</pre>
 
 
 
Flash the idbloader.img/idbspl.img&nbsp;to offset 0x40 which including stage 2, and you will need a uboot.img for boot stage 3.
 
  
 
=== U-Boot ===
 
=== U-Boot ===
Line 113: Line 123:
  
 
When using idbLoader from&nbsp;Rockchip miniloader, need package u-boot.bin into miniloader loadable format by Rockchip tool loaderimage.
 
When using idbLoader from&nbsp;Rockchip miniloader, need package u-boot.bin into miniloader loadable format by Rockchip tool loaderimage.
<pre>tools/loaderimage --pack --uboot u-boot.bin uboot.img</pre>
+
<pre>tools/loaderimage --pack --uboot u-boot.bin uboot.img $SYS_TEXT_BASE</pre>
  
&nbsp;
+
Where SoCs may have different&nbsp;$SYS_TEXT_BASE.
  
 
==== u-boot.itb ====
 
==== u-boot.itb ====
Line 152: Line 162:
 
This is a package from ddr.bin, usbplug.bin, miniloader.bin, Rockchip tool ''DB ''command will make usbplug.bin running in target which perform as a Rockusb device. You can skip to package this image, Rockchip will offer this image at the most of time.
 
This is a package from ddr.bin, usbplug.bin, miniloader.bin, Rockchip tool ''DB ''command will make usbplug.bin running in target which perform as a Rockusb device. You can skip to package this image, Rockchip will offer this image at the most of time.
  
 +
&nbsp;
  
 
= Flash and boot from Media device =
 
= Flash and boot from Media device =
Line 159: Line 170:
 
Get image Ready:
 
Get image Ready:
  
*For armv7 with SPL with SPL_BACK_TO_BROM option enabled:
+
*For&nbsp;with SPL:  
**idbLoader.img
+
**idbloader.img  
**boot.img or boot folder with zImage, dtb and exitlinulx inside
+
**u-boot.itb  
**rootfs.img 
 
*For armv7 with SPL with SPL_BACK_TO_BROM option disabled:  
 
**idbspl.img  
 
**u-boot.bin
 
**boot.img or boot folder with zImage, dtb and exitlinulx inside
 
**rootfs.img 
 
*For armv7 with miniloader
 
**idbLoader.img
 
**uboot.img
 
**boot.img or&nbsp;boot folder with zImage, dtb and exitlinulx inside
 
**rootfs.img 
 
*For armv8 with SPL:
 
**idbspl.img
 
**bl3.itb  
 
 
**boot.img or&nbsp;boot folder with Image, dtb and exitlinulx inside  
 
**boot.img or&nbsp;boot folder with Image, dtb and exitlinulx inside  
 
**rootfs.img   
 
**rootfs.img   
*For armv8 with miniloader  
+
*For&nbsp;with miniloader  
**idbLoader.img  
+
**idbloader.img  
 
**uboot.img  
 
**uboot.img  
 
**trust.img  
 
**trust.img  
 
**boot.img or&nbsp;boot folder with Image, dtb and exitlinulx inside  
 
**boot.img or&nbsp;boot folder with Image, dtb and exitlinulx inside  
 
**rootfs.img   
 
**rootfs.img   
 +
 +
&nbsp;
  
 
== Boot from eMMC ==
 
== Boot from eMMC ==
Line 199: Line 198:
 
rkdeveloptool gpt parameter_gpt.txt</pre>
 
rkdeveloptool gpt parameter_gpt.txt</pre>
  
*For armv7 with SPL with SPL_BACK_TO_BROM option enabled(rk3036, rk3188, rk3288):  
+
*For&nbsp;with SPL:  
 
<pre style="margin-left: 40px">rkdeveloptool db rkxx_loader_vx.xx.bin
 
<pre style="margin-left: 40px">rkdeveloptool db rkxx_loader_vx.xx.bin
 
rkdeveloptool wl 0x40 idbloader.img
 
rkdeveloptool wl 0x40 idbloader.img
 +
rkdeveloptool wl 0x4000 u-boot.itb
 
rkdeveloptool wl 0x8000 boot.img
 
rkdeveloptool wl 0x8000 boot.img
 
rkdeveloptool wl 0x40000 rootfs.img
 
rkdeveloptool wl 0x40000 rootfs.img
Line 207: Line 207:
 
</pre>
 
</pre>
  
*For armv7 with SPL with SPL_BACK_TO_BROM option disabled(rk3288):
+
*For&nbsp;with miniloader  
<pre style="margin-left: 40px">rkdeveloptool db rkxx_loader_vx.xx.bin
 
rkdeveloptool wl 0x40 idbspl.img
 
rkdeveloptool wl 0x200 u-boot.bin
 
rkdeveloptool wl 0x8000 boot.img
 
rkdeveloptool wl 0x40000 rootfs.img
 
rkdeveloptool rd
 
</pre>
 
 
 
*For armv7 with miniloader(rk3036, rk3188, rk3288)
 
 
<pre style="margin-left: 40px">rkdeveloptool db rkxx_loader_vx.xx.bin
 
<pre style="margin-left: 40px">rkdeveloptool db rkxx_loader_vx.xx.bin
 
rkdeveloptool ul rkxx_loader_vx.xx.bin
 
rkdeveloptool ul rkxx_loader_vx.xx.bin
 
rkdeveloptool wl 0x4000 uboot.img
 
rkdeveloptool wl 0x4000 uboot.img
 +
rkdeveloptool wl 0x6000 trust.img
 
rkdeveloptool wl 0x8000 boot.img
 
rkdeveloptool wl 0x8000 boot.img
 
rkdeveloptool wl 0x40000 rootfs.img
 
rkdeveloptool wl 0x40000 rootfs.img
Line 225: Line 217:
 
</pre>
 
</pre>
  
*For armv8 with SPL(rk3399):
+
&nbsp;
<pre style="margin-left: 40px">rkdeveloptool db rkxx_loader_vx.xx.bin
 
rkdeveloptool wl 0x40 idbspl.img
 
rkdeveloptool wl 0x200 bl3.itb
 
rkdeveloptool wl 0x8000 boot.img
 
rkdeveloptool wl 0x40000 rootfs.img
 
rkdeveloptool rd
 
</pre>
 
  
*For armv8 with miniloader(rk3399, rk3328)
 
<pre style="margin-left: 40px">rkdeveloptool db rkxx_loader_vx.xx.bin
 
rkdeveloptool ul rkxx_loader_vx.xx.bin
 
rkdeveloptool wl 0x4000 uboot.img
 
rkdeveloptool wl 0x6000 trust.img
 
rkdeveloptool wl 0x8000 boot.img
 
rkdeveloptool wl 0x40000 rootfs.img
 
rkdeveloptool rd
 
</pre>
 
  
 
== Boot from SD/TF Card ==
 
== Boot from SD/TF Card ==
Line 250: Line 226:
 
Insert SD card to PC and we assume the /dev/sdb is the SD card device.
 
Insert SD card to PC and we assume the /dev/sdb is the SD card device.
  
*For armv7 with SPL with SPL_BACK_TO_BROM option enabled(rk3036, rk3188, rk3288):
+
*For&nbsp;with SPL:  
<pre style="margin-left: 40px">dd if=idbloader.img of=sdb seek=64
 
dd if=boot.img of=sdb seek=32768
 
dd if=rootfs.img of=sdb seek=262144
 
</pre>
 
 
 
*For armv7 with SPL with SPL_BACK_TO_BROM option disabled(rk3288):
 
<pre style="margin-left: 40px">dd if=idbspl.img of=sdb seek=64
 
dd if=u-boot.bin of=sdb seek=512
 
dd if=boot.img of=sdb seek=32768
 
dd if=rootfs.img of=sdb seek=262144
 
</pre>
 
 
 
*For armv7 with miniloader(rk3036, rk3188, rk3288)
 
 
<pre style="margin-left: 40px">dd if=idbloader.img of=sdb seek=64
 
<pre style="margin-left: 40px">dd if=idbloader.img of=sdb seek=64
dd if=uboot.img of=sdb seek=16384
+
dd if=u-boot.itb of=sdb seek=16384
dd if=boot.img of=sdb seek=32768
 
dd if=rootfs.img of=sdb seek=262144
 
</pre>
 
 
 
*For armv8 with SPL(rk3399):
 
<pre style="margin-left: 40px">dd if=idbspl.img of=sdb seek=64
 
dd if=bl3.itb of=sdb seek=512
 
 
dd if=boot.img of=sdb seek=32768
 
dd if=boot.img of=sdb seek=32768
 
dd if=rootfs.img of=sdb seek=262144
 
dd if=rootfs.img of=sdb seek=262144
 
</pre>
 
</pre>
  
*For armv8 with miniloader(rk3399, rk3328)
+
*For&nbsp;with miniloader:
 
<pre style="margin-left: 40px">dd if=idbloader.img of=sdb seek=64
 
<pre style="margin-left: 40px">dd if=idbloader.img of=sdb seek=64
 
dd if=uboot.img of=sdb seek=16384
 
dd if=uboot.img of=sdb seek=16384

Latest revision as of 03:52, 15 November 2019


Boot introduce

First, let's make the concept clear, there are many boot stages when we boot up a Linux OS;

Then we need to know about how the image should packaged, where the image locate;

At last, we will explain how to write to different media and boot from there.

Here is Rockchip pre-released binaries which may be mentioned later:

https://github.com/rockchip-linux/rkbin

And Rockcip Linux GPT partition here.

 

Boot flow

This chapter introduce the generic boot flow for Rockchip Application Processors, including the detail about what image we may use in Rockchip platform for kind of boot path:

- use U-Boot TPL/SPL from upsream or rockchip U-Boot, fully source code;

- use Rockchp idbLoader which is combinded by Rockchip ddr init bin and miniloader bin from Rockchip rkbin project;

+--------+----------------+----------+-------------+---------+
| Boot   | Terminology #1 | Actual   | Rockchip    | Image   |
| stage  |                | program  |  Image      | Location|
| number |                | name     |   Name      | (sector)|
+--------+----------------+----------+-------------+---------+
| 1      |  Primary       | ROM code | BootRom     |         |
|        |  Program       |          |             |         |
|        |  Loader        |          |             |         |
|        |                |          |             |         |
| 2      |  Secondary     | U-Boot   |idbloader.img| 0x40    | pre-loader
|        |  Program       | TPL/SPL  |             |         |
|        |  Loader (SPL)  |          |             |         |
|        |                |          |             |         |
| 3      |  -             | U-Boot   | u-boot.itb  | 0x4000  | including u-boot and atf
|        |                |          | uboot.img   |         | only used with miniloader
|        |                |          |             |         |
|        |                | ATF/TEE  | trust.img   | 0x6000  | only used with miniloader
|        |                |          |             |         |
| 4      |  -             | kernel   | boot.img    | 0x8000  |
|        |                |          |             |         |
| 5      |  -             | rootfs   | rootfs.img  | 0x40000 |
+--------+----------------+----------+-------------+---------+

Then when we talking about boot from eMMC/SD/U-Disk/net, they are in different concept:

  • Stage 1 is always in boot rom, it loads stage 2 and may load stage 3(when SPL_BACK_TO_BROM option enabled).
  • Boot from SPI flash means firmware for stage 2 and 3(SPL and U-Boot only) in SPI flash and stage 4/5 in other place;
  • Boot from eMMC means all the firmware(including stage 2, 3, 4, 5) in eMMC;
  • Boot from SD card means all the firmware(including stage 2, 3, 4, 5) in SD card;
  • Boot from U-Disk means firmware for stage 4 and 5(not including SPL and U-Boot) in Disk, optionally only including stage 5;
  • Boot from net/tftp means firmeware for stage 4 and 5(not including SPL and U-Boot) on the network;

 

Rockchip bootflow.jpg

Boot Flow 1 is typical Rockchip boot flow with Rockchip miniloader;
Boot Flow 2 is used for most SoCs with U-Boot TPL for ddr init and SPL for trust(ATF/OP-TEE) load and run into next stage;

Note 1. If loader1 have more than 1 stage, program will back to bootrom and bootrom load and run into next stage. eg. If loader1 is tpl and spl, the bootrom will run into tpl first, tpl init ddr and back to bootrom, bootrom then load and run into spl.
Note 2. If trust is enabled, loader1 need to load both trust and u-boot, and then run into trust in secure mode(EL3 in armv8), trust do the initialize and run into U-Boot in non-secure mode(EL2 in armv8).
Note 3. For trust(in trust.img or u-boot.itb), armv7 has only one tee.bin with or without ta, armv8 has bl31.elf and option with bl32.
Note 4. In boot.img, content can be zImage and its dtb for Linux, and can optionally be grub.efi, and can be AOSP boot.img, ramdisk is option;

Package option

After we know about the boot stages,

Here are the file list before package for stage 2~4:

  • From source code:
    • From U-Boot: u-boot-spl.bin, u-boot.bin(may use u-boot-nodtb.bin and u-boot.dtb instead),
    • From kernel: kernel Image/zImage file, kernel dtb,
    • From ATF: bl31.elf;
  • From Rockchip binary:
    • ddr, usbplug, miniloader, bl31/op-tee, (all with chip 'rkxx_'  prefix and with version '_x.xx.bin' postfix);

We offer two different boot-loader methods for different solutions, the steps and request files are also complete different. But not all the platforms supports the both boot-loader methods. Here are the types to package image from those files:

 



The Pre-bootloader(IDBLoader)

What is idbloader

idbloader.img is a Rockchip format pre-loader suppose to work at SoC start up, it contains:

- IDBlock header which is known by Rockchip BootRom;

- DRAM init program which is load by MaskRom and running at internal SRAM;

- loader for next stage which is load by MaskRom and running at DDR SDRAM;

You can get idbloader with below methods.

Get idbloader for eMMC from Rockchip release loader

No need to package a idbloader.img for eMMC if you are using Rockchip release loader, you can get idbloader on eMMC with below command:

rkdeveloptool db rkxx_loader_vx.xx.bin
rkdeveloptool ul rkxx_loader_vx.xx.bin

Package the idbloader.img from Rockchip binary:

For SD boot or eMMC(update with rockusb wl cmd), you need a idbloader(combinded with ddr and miniloader) .

tools/mkimage -n rkxxxx -T rksd -d rkxx_ddr_vx.xx.bin idbloader.img
cat rkxx_miniloader_vx.xx.bin >> idbloader.img

Package the idbloader.img from U-Boot TPL/SPL(which is fully open source):

tools/mkimage -n rkxxxx -T rksd -d tpl/u-boot-tpl.bin idbloader.img
cat spl/u-boot-spl.bin >> idbloader.img

Flash the idbloader.img to offset 0x40 which including stage 2, and you will need a uboot.img for boot stage 3.

U-Boot

uboot.img

When using idbLoader from Rockchip miniloader, need package u-boot.bin into miniloader loadable format by Rockchip tool loaderimage.

tools/loaderimage --pack --uboot u-boot.bin uboot.img $SYS_TEXT_BASE

Where SoCs may have different $SYS_TEXT_BASE.

u-boot.itb

When using SPL to load the ATF/OP-TEE, package the bl31.bin, u-boot-nodtb.bin and uboot.dtb into one FIT image. You can skip the step to package the Trust image and flash that image in the next section.

make u-boot.itb

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

Trust

trust.img

When using idbLoader from Rockchip miniloader, need package bl31.bin into miniloader loadable format by Rockchip tool trustmerge.

tools/trustmerge tools/rk_tools/RKTRUST_RKXXXXTRUST.ini

Flash the trust.img to offset 0x6000 which is for using Rockchip miniloader

boot.img

This image is package the kernel Image and dtb file into a know filesystem(FAT or EXT2) image for distro boot.

See Install kernel for detail about generate boot.img from kernel zImage/Image, dtb.

Flash the boot.img to offset 0x8000 which is stage 4.

rootfs.img

Flash the rootfs.img to offset 0x40000 which is stage 5. As long as the kernel you chosen can support that filesystem, there is not limit in the format of the image.

rkxx_loader_vx.xx.xxx.bin

This is provide by Rockchip in binary mode, which is used for firmware upgrade to eMMC with rkdeveloptool, can not be wirte to media device directly.

This is a package from ddr.bin, usbplug.bin, miniloader.bin, Rockchip tool DB command will make usbplug.bin running in target which perform as a Rockusb device. You can skip to package this image, Rockchip will offer this image at the most of time.

 

Flash and boot from Media device

Here we introduce how to write image to different Medeia device.

Get image Ready:

  • For with SPL:
    • idbloader.img
    • u-boot.itb
    • boot.img or boot folder with Image, dtb and exitlinulx inside
    • rootfs.img
  • For with miniloader
    • idbloader.img
    • uboot.img
    • trust.img
    • boot.img or boot folder with Image, dtb and exitlinulx inside
    • rootfs.img

 

Boot from eMMC

The eMMC is on the hardware board, so we need:

Example commands for flash image to target.

Flash the gpt partition to target:

rkdeveloptool db rkxx_loader_vx.xx.bin
rkdeveloptool gpt parameter_gpt.txt
  • For with SPL:
rkdeveloptool db rkxx_loader_vx.xx.bin
rkdeveloptool wl 0x40 idbloader.img
rkdeveloptool wl 0x4000 u-boot.itb
rkdeveloptool wl 0x8000 boot.img
rkdeveloptool wl 0x40000 rootfs.img
rkdeveloptool rd
  • For with miniloader
rkdeveloptool db rkxx_loader_vx.xx.bin
rkdeveloptool ul rkxx_loader_vx.xx.bin
rkdeveloptool wl 0x4000 uboot.img
rkdeveloptool wl 0x6000 trust.img
rkdeveloptool wl 0x8000 boot.img
rkdeveloptool wl 0x40000 rootfs.img
rkdeveloptool rd

 


Boot from SD/TF Card

We can write SD/TF card with Linux PC dd command very easily.

Insert SD card to PC and we assume the /dev/sdb is the SD card device.

  • For with SPL:
dd if=idbloader.img of=sdb seek=64
dd if=u-boot.itb of=sdb seek=16384
dd if=boot.img of=sdb seek=32768
dd if=rootfs.img of=sdb seek=262144
  • For with miniloader:
dd if=idbloader.img of=sdb seek=64
dd if=uboot.img of=sdb seek=16384
dd if=trust.img of=sdb seek=24576
dd if=boot.img of=sdb seek=32768
dd if=rootfs.img of=sdb seek=262144

In order to make sure everything has write to SD card before unpluged, recommand to run below command:

sync

Note, when using boot from SD card, need to update the kernel cmdline(which is in extlinux.conf) for the correct root value.

append  earlyprintk console=ttyS2,115200n8 rw root=/dev/mmcblk1p7 rootwait rootfstype=ext4 init=/sbin/init

Write GPT partition table to SD card in U-Boot, and then U-Boot can find the boot partition and run into kernel.

gpt write mmc 0 $partitions

Boot from U-Disk

Same as boot-from-sdcard, but please note that U-Disk only support stage 4 and 5, see Boot Stage for detail.

If U-Disk used for stage 4 and 5, format the U-Disk in gpt format and at least 2 partitions, write boot.img and rootfs.img in those partitions;

if U-Dist is only used for stage 5, we can dd the rootfs.img to U-Disk device directly.

Note, need to update the kernel cmdline(which is in extlinux.conf) for the correct root value.

    append  earlyprintk console=ttyS2,115200n8 rw root=/dev/sda1 rootwait rootfstype=ext4 init=/sbin/init

Boot from Network

To be continued.

See also

rkdeveloptool

rockusb

Rockchip Linux partition definition