1 # SPDX-License-Identifier: GPL-2.0+
3 # Copyright (C) 2015 Google. Inc
4 # Written by Simon Glass <sjg@chromium.org>
9 A wide range of Rockchip SoCs are supported in mainline U-Boot
17 - Firefly RK3288 board or something else with a supported RockChip SoC
18 - Power connection to 5V using the supplied micro-USB power cable
19 - Separate USB serial cable attached to your computer and the Firefly
20 (connect to the micro-USB connector below the logo)
22 - openssl (sudo apt-get install openssl)
23 - Serial UART connection [4]
24 - Suitable ARM cross compiler, e.g.:
25 sudo apt-get install gcc-4.7-arm-linux-gnueabi
31 At present 11 RK3288 boards are supported:
33 - EVB RK3288 - use evb-rk3288 configuration
34 - Firefly RK3288 - use firefly-rk3288 configuration
35 - Hisense Chromebook - use chromebook_jerry configuration
36 - Asus C100P Chromebook - use chromebook_minnie configuration
37 - Asus Chromebit - use chromebook_mickey configuration
38 - MiQi RK3288 - use miqi-rk3288 configuration
39 - phyCORE-RK3288 RDK - use phycore-rk3288 configuration
40 - PopMetal RK3288 - use popmetal-rk3288 configuration
41 - Radxa Rock 2 - use rock2 configuration
42 - Tinker RK3288 - use tinker-rk3288 configuration
43 - Vyasa RK3288 - use vyasa-rk3288 configuration
45 Two RK3036 boards are supported:
47 - EVB RK3036 - use evb-rk3036 configuration
48 - Kylin - use kylin_rk3036 configuration
50 Two RK3328 board are supported:
52 - EVB RK3328 - use evb-rk3328_defconfig
53 - Pine64 Rock64 board - use rock64-rk3328_defconfig
55 Size RK3399 boards are supported (aarch64):
57 - EBV RK3399 - use evb_rk3399 configuration
58 - Firefly RK3399 - use the firefly_rk3399 configuration
59 - Puma - use puma_rk3399 configuration
60 - Ficus - use ficus-rk3399 configuration
61 - Rock960 (Vamrs) - use rock960-rk3399 configuration
62 - Bob - use chromebook_bob configuration
64 Four RK3368 boards are supported:
66 - Sheep - use sheep-rk3368 configuration
67 - Lion - use lion-rk3368 configuration
68 - Geekbox - use geekbox configuration
69 - EVB PX5 - use evb-px5 configuration
71 One RK3128 board is supported:
73 - EVB RK3128 - use evb-rk3128 configuration
75 One RK3229 board is supported:
77 - EVB RK3229 - use evb-rk3229 configuration
79 Two RV1108 boards are supported:
81 - EVB RV1108 - use evb-rv1108 configuration
82 - Elgin R1 - use elgin-rv1108 configuration
84 One RV3188 baord is supported:
86 - Raxda Rock - use rock configuration
91 1. To build RK3288 board:
93 CROSS_COMPILE=arm-linux-gnueabi- make O=firefly firefly-rk3288_defconfig all
95 (or you can use another cross compiler if you prefer)
97 2. To build RK3399 board:
99 Option 1: Package the image with Rockchip miniloader:
103 => cd /path/to/u-boot
104 => make nanopi-neo4-rk3399_defconfig
109 => git clone https://github.com/rockchip-linux/rkbin.git
114 => ./tools/trust_merger RKTRUST/RK3399TRUST.ini
119 => ./tools/loaderimage --pack --uboot /path/to/u-boot/u-boot-dtb.bin uboot.img
121 (Get trust.img and uboot.img)
123 Option 2: Package the image with SPL:
125 - Export cross compiler path for aarch64
131 => git clone git://git.theobroma-systems.com/arm-trusted-firmware.git
132 => cd arm-trusted-firmware
133 => make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
136 => export BL31=/path/to/arm-trusted-firmware/build/rk3399/release/bl31/bl31.bin
138 For rest of rk3399 boards.
140 => git clone https://github.com/ARM-software/arm-trusted-firmware.git
141 => cd arm-trusted-firmware
143 (export cross compiler path for Cortex-M0 MCU likely arm-none-eabi-)
145 => make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399
148 => export BL31=/path/to/arm-trusted-firmware/build/rk3399/release/bl31/bl31.elf
150 - Compile PMU M0 firmware
152 This is optional for most of the rk3399 boards and required only for Puma board.
154 => git clone git://git.theobroma-systems.com/rk3399-cortex-m0.git
155 => cd rk3399-cortex-m0
157 (export cross compiler path for Cortex-M0 PMU)
158 => make CROSS_COMPILE=arm-cortex_m0-eabi-
160 (export rk3399m0.bin)
161 => export PMUM0=/path/to/rk3399-cortex-m0/rk3399m0.bin
165 => cd /path/to/u-boot
166 => make orangepi-rk3399_defconfig
169 (Get spl/u-boot-spl-dtb.bin, u-boot.itb images and some boards would get
170 spl/u-boot-spl.bin since it doesn't enable CONFIG_SPL_OF_CONTROL
172 If TPL enabled on the target, get tpl/u-boot-tpl-dtb.bin or tpl/u-boot-tpl.bin
173 if CONFIG_TPL_OF_CONTROL not enabled)
175 Writing to the board with USB
176 =============================
178 For USB to work you must get your board into ROM boot mode, either by erasing
179 your MMC or (perhaps) holding the recovery button when you boot the board.
180 To erase your MMC, you can boot into Linux and type (as root)
182 dd if=/dev/zero of=/dev/mmcblk0 bs=1M
184 Connect your board's OTG port to your computer.
186 To create a suitable image and write it to the board:
188 ./firefly-rk3288/tools/mkimage -n rk3288 -T rkimage -d \
189 ./firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
190 cat out | openssl rc4 -K 7c4e0304550509072d2c7b38170d1711 | rkflashtool l
192 If all goes well you should something like:
194 U-Boot SPL 2015.07-rc1-00383-ge345740-dirty (Jun 03 2015 - 10:06:49)
195 Card did not respond to voltage select!
196 spl: mmc init failed with error: -17
197 ### ERROR ### Please RESET the board ###
199 You will need to reset the board before each time you try. Yes, that's all
200 it does so far. If support for the Rockchip USB protocol or DFU were added
201 in SPL then we could in principle load U-Boot and boot to a prompt from USB
202 as several other platforms do. However it does not seem to be possible to
203 use the existing boot ROM code from SPL.
206 Booting from an SD card
207 =======================
209 To write an image that boots from an SD card (assumed to be /dev/sdc):
211 ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
212 firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
213 sudo dd if=out of=/dev/sdc seek=64 && \
214 sudo dd if=firefly-rk3288/u-boot-dtb.img of=/dev/sdc seek=16384
216 This puts the Rockchip header and SPL image first and then places the U-Boot
217 image at block 16384 (i.e. 8MB from the start of the SD card). This
218 corresponds with this setting in U-Boot:
220 #define CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR 0x4000
222 Put this SD (or micro-SD) card into your board and reset it. You should see
225 U-Boot 2016.01-rc2-00309-ge5bad3b-dirty (Jan 02 2016 - 23:41:59 -0700)
227 Model: Radxa Rock 2 Square
229 MMC: dwmmc@ff0f0000: 0, dwmmc@ff0c0000: 1
230 *** Warning - bad CRC, using default environment
233 Out: vop@ff940000.vidconsole
235 Net: Net Initialization Skipped
237 Hit any key to stop autoboot: 0
240 The rockchip bootrom can load and boot an initial spl, then continue to
241 load a second-stage bootloader (ie. U-Boot) as soon as the control is returned
242 to the bootrom. Both the RK3288 and the RK3036 use this special boot sequence.
243 The configuration option enabling this is:
245 CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y
247 You can create the image via the following operations:
249 ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
250 firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
251 cat firefly-rk3288/u-boot-dtb.bin >> out && \
252 sudo dd if=out of=/dev/sdc seek=64
254 If you have an HDMI cable attached you should see a video console.
256 For evb_rk3036 board:
257 ./evb-rk3036/tools/mkimage -n rk3036 -T rksd -d evb-rk3036/spl/u-boot-spl.bin out && \
258 cat evb-rk3036/u-boot-dtb.bin >> out && \
259 sudo dd if=out of=/dev/sdc seek=64
261 Note: rk3036 SDMMC and debug uart use the same iomux, so if you boot from SD, the
262 debug uart must be disabled
265 Booting from an SD card on RK3288 with TPL
266 ==========================================
268 Since the size of SPL can't be exceeded 0x8000 bytes in RK3288, it is not possible add
269 new SPL features like Falcon mode or etc.
271 So introduce TPL so-that adding new features to SPL is possible because now TPL should
272 run minimal with code like DDR, clock etc and rest of new features in SPL.
274 As of now TPL is added on Vyasa-RK3288 board.
276 To write an image that boots from an SD card (assumed to be /dev/mmcblk0):
278 sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64 &&
279 sudo dd if=u-boot-dtb.img of=/dev/mmcblk0 seek=16384
281 Booting from an SD card on RK3188
282 =================================
284 For rk3188 boards the general storage onto the card stays the same as
285 described above, but the image creation needs a bit more care.
287 The bootrom of rk3188 expects to find a small 1kb loader which returns
288 control to the bootrom, after which it will load the real loader, which
289 can then be up to 29kb in size and does the regular ddr init. This is
290 handled by a single image (built as the SPL stage) that tests whether
291 it is handled for the first or second time via code executed from the
294 Additionally the rk3188 requires everything the bootrom loads to be
295 rc4-encrypted. Except for the very first stage the bootrom always reads
296 and decodes 2kb pages, so files should be sized accordingly.
298 # copy tpl, pad to 1020 bytes and append spl
299 tools/mkimage -n rk3188 -T rksd -d spl/u-boot-spl.bin out
301 # truncate, encode and append u-boot.bin
302 truncate -s %2048 u-boot.bin
303 cat u-boot.bin | split -b 512 --filter='openssl rc4 -K 7C4E0304550509072D2C7B38170D1711' >> out
305 Booting from an SD card on Pine64 Rock64 (RK3328)
306 =================================================
308 For Rock64 rk3328 board the following three parts are required:
309 TPL, SPL, and the u-boot image tree blob.
311 - Write TPL/SPL image at 64 sector
313 => sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
315 - Write u-boot image tree blob at 16384 sector
317 => sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
319 Booting from an SD card on RK3399
320 =================================
322 To write an image that boots from an SD card (assumed to be /dev/sdc):
324 Option 1: Package the image with Rockchip miniloader:
326 - Create idbloader.img
328 => cd /path/to/u-boot
329 => ./tools/mkimage -n rk3399 -T rksd -d /path/to/rkbin/bin/rk33/rk3399_ddr_800MHz_v1.20.bin idbloader.img
330 => cat /path/to/rkbin/bin/rk33/rk3399_miniloader_v1.19.bin >> idbloader.img
332 - Write idbloader.img at 64 sector
334 => sudo dd if=idbloader.img of=/dev/sdc seek=64
336 - Write trust.img at 24576
338 => sudo dd if=trust.img of=/dev/sdc seek=24576
340 - Write uboot.img at 16384 sector
342 => sudo dd if=uboot.img of=/dev/sdc seek=16384
345 Put this SD (or micro-SD) card into your board and reset it. You should see
348 DDR Version 1.20 20190314
350 Channel 0: DDR3, 933MHz
351 Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
353 ch 0 ddrconfig = 0x101, ddrsize = 0x20
354 pmugrf_os_reg[2] = 0x10006281, stride = 0x17
356 Boot1: 2019-03-14, version: 1.19
359 mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
360 mmc: ERROR: Card did not respond to voltage select!
362 mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
363 mmc: ERROR: Card did not respond to voltage select!
365 mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
366 mmc: ERROR: Card did not respond to voltage select!
372 FwPartOffset=2000 , 0
373 StorageInit ok = 45266
375 SecureInit read PBA: 0x4
376 SecureInit read PBA: 0x404
377 SecureInit read PBA: 0x804
378 SecureInit read PBA: 0xc04
379 SecureInit read PBA: 0x1004
380 SecureInit read PBA: 0x1404
381 SecureInit read PBA: 0x1804
382 SecureInit read PBA: 0x1c04
383 SecureInit ret = 0, SecureMode = 0
384 atags_set_bootdev: ret:(0)
385 GPT 0x3380ec0 signature is wrong
387 GPT 0x3380ec0 signature is wrong
389 LoadTrust Addr:0x4000
391 Load uboot, ReadLba = 2000
392 hdr 0000000003380880 + 0x0:0x88,0x41,0x3e,0x97,0xe6,0x61,0x54,0x23,0xe9,0x5a,0xd1,0x2b,0xdc,0x2f,0xf9,0x35,
394 Load OK, addr=0x200000, size=0x9c9c0
396 NOTICE: BL31: v1.3(debug):370ab80
397 NOTICE: BL31: Built : 09:23:41, Mar 4 2019
398 NOTICE: BL31: Rockchip release version: v1.1
399 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
400 INFO: Using opteed sec cpu_context!
401 INFO: boot cpu mask: 0
402 INFO: plat_rockchip_pmu_init(1181): pd status 3e
403 INFO: BL31: Initializing runtime services
404 INFO: BL31: Initializing BL32
405 INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-195-g8f090d20 #6 Fri Dec 7 06:11:20 UTC 2018 aarch64)
407 INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2
409 INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
410 INFO: BL31: Preparing for EL3 exit to normal world
411 INFO: Entry point address = 0x200000
415 U-Boot 2019.04-rc4-00136-gfd121f9641-dirty (Apr 16 2019 - 14:02:47 +0530)
417 Model: FriendlyARM NanoPi NEO4
419 MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
420 Loading Environment from MMC... *** Warning - bad CRC, using default environment
425 Model: FriendlyARM NanoPi NEO4
426 Net: eth0: ethernet@fe300000
427 Hit any key to stop autoboot: 0
430 Option 2: Package the image with SPL:
432 - Prefix rk3399 header to SPL image
434 => cd /path/to/u-boot
435 => ./tools/mkimage -n rk3399 -T rksd -d spl/u-boot-spl-dtb.bin out
437 - Write prefixed SPL at 64th sector
439 => sudo dd if=out of=/dev/sdc seek=64
441 - Write U-Boot proper at 16384 sector
443 => sudo dd if=u-boot.itb of=/dev/sdc seek=16384
446 Put this SD (or micro-SD) card into your board and reset it. You should see
449 U-Boot SPL board init
450 Trying to boot from MMC1
453 U-Boot 2019.01-00004-g14db5ee998 (Mar 11 2019 - 13:18:41 +0530)
455 Model: Orange Pi RK3399 Board
457 MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
458 Loading Environment from MMC... OK
462 Model: Orange Pi RK3399 Board
463 Net: eth0: ethernet@fe300000
464 Hit any key to stop autoboot: 0
467 Option 3: Package the image with TPL:
469 - Write tpl+spl at 64th sector
471 => sudo dd if=idbloader.img of=/dev/sdc seek=64
473 - Write U-Boot proper at 16384 sector
475 => sudo dd if=u-boot.itb of=/dev/sdc seek=16384
478 Put this SD (or micro-SD) card into your board and reset it. You should see
481 U-Boot TPL board init
482 Trying to boot from BOOTROM
483 Returning to boot ROM...
485 U-Boot SPL board init
486 Trying to boot from MMC1
489 U-Boot 2019.07-rc1-00241-g5b3244767a (May 08 2019 - 10:51:06 +0530)
491 Model: Orange Pi RK3399 Board
493 MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
494 Loading Environment from MMC... OK
498 Model: Orange Pi RK3399 Board
499 Net: eth0: ethernet@fe300000
500 Hit any key to stop autoboot: 0
503 Using fastboot on rk3288
504 ========================
505 - Write GPT partition layout to mmc device which fastboot want to use it to
508 => gpt write mmc 1 $partitions
510 - Invoke fastboot command to prepare
514 - Start fastboot request on PC
516 fastboot -i 0x2207 flash loader evb-rk3288/spl/u-boot-spl-dtb.bin
518 You should see something like:
521 WARNING: unknown variable: partition-type:loader
522 Starting download of 357796 bytes
524 downloading of 357796 bytes finished
526 ........ wrote 357888 bytes to 'loader'
531 To write an image that boots from SPI flash (e.g. for the Haier Chromebook or
534 ./chromebook_jerry/tools/mkimage -n rk3288 -T rkspi \
535 -d chromebook_jerry/spl/u-boot-spl-dtb.bin spl.bin && \
536 dd if=spl.bin of=spl-out.bin bs=128K conv=sync && \
537 cat spl-out.bin chromebook_jerry/u-boot-dtb.img >out.bin && \
538 dd if=out.bin of=out.bin.pad bs=4M conv=sync
540 This converts the SPL image to the required SPI format by adding the Rockchip
541 header and skipping every second 2KB block. Then the U-Boot image is written at
542 offset 128KB and the whole image is padded to 4MB which is the SPI flash size.
543 The position of U-Boot is controlled with this setting in U-Boot:
545 #define CONFIG_SYS_SPI_U_BOOT_OFFS 0x20000
547 If you have a Dediprog em100pro connected then you can write the image with:
549 sudo em100 -s -c GD25LQ32 -d out.bin.pad -r
551 When booting you should see something like:
553 U-Boot SPL 2015.07-rc2-00215-g9a58220-dirty (Jun 23 2015 - 12:11:32)
556 U-Boot 2015.07-rc2-00215-g9a58220-dirty (Jun 23 2015 - 12:11:32 -0600)
561 Using default environment
571 Immediate priorities are:
575 - Run CPU at full speed (code exists but we only see ~60 DMIPS maximum)
577 - Boot U-Boot proper over USB OTG (at present only SPL works)
583 There are plenty of patches in the links below to help with this work.
585 [1] https://github.com/rkchrome/uboot.git
586 [2] https://github.com/linux-rockchip/u-boot-rockchip.git branch u-boot-rk3288
587 [3] https://github.com/linux-rockchip/rkflashtool.git
588 [4] http://wiki.t-firefly.com/index.php/Firefly-RK3288/Serial_debug/en
593 rkimage.c produces an SPL image suitable for sending directly to the boot ROM
594 over USB OTG. This is a very simple format - just the string RK32 (as 4 bytes)
595 followed by u-boot-spl-dtb.bin.
597 The boot ROM loads image to 0xff704000 which is in the internal SRAM. The SRAM
598 starts at 0xff700000 and extends to 0xff718000 where we put the stack.
603 rksd.c produces an image consisting of 32KB of empty space, a header and
604 u-boot-spl-dtb.bin. The header is defined by 'struct header0_info' although
605 most of the fields are unused by U-Boot. We just need to specify the
606 signature, a flag and the block offset and size of the SPL image.
608 The header occupies a single block but we pad it out to 4 blocks. The header
609 is encoding using RC4 with the key 7c4e0304550509072d2c7b38170d1711. The SPL
610 image can be encoded too but we don't do that.
612 The maximum size of u-boot-spl-dtb.bin which the boot ROM will read is 32KB,
613 or 0x40 blocks. This is a severe and annoying limitation. There may be a way
614 around this limitation, since there is plenty of SRAM, but at present the
615 board refuses to boot if this limit is exceeded.
617 The image produced is padded up to a block boundary (512 bytes). It should be
618 written to the start of an SD card using dd.
620 Since this image is set to load U-Boot from the SD card at block offset,
621 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR, dd should be used to write
622 u-boot-dtb.img to the SD card at that offset. See above for instructions.
627 rkspi.c produces an image consisting of a header and u-boot-spl-dtb.bin. The
628 resulting image is then spread out so that only the first 2KB of each 4KB
629 sector is used. The header is the same as with rksd and the maximum size is
630 also 32KB (before spreading). The image should be written to the start of
633 See above for instructions on how to write a SPI image.
638 You can use this script to create #defines for SoC register access. See the
642 Device tree and driver model
643 ----------------------------
645 Where possible driver model is used to provide a structure to the
646 functionality. Device tree is used for configuration. However these have an
647 overhead and in SPL with a 32KB size limit some shortcuts have been taken.
648 In general all Rockchip drivers should use these features, with SPL-specific
649 modifications where required.
652 ----------------------------
654 Rockchip use a unified GPT partition layout in open source support.
655 With this GPT partition layout, uboot can be compatilbe with other components,
656 like miniloader, trusted-os, arm-trust-firmware.
658 There are some documents about partitions in the links below.
659 http://rockchip.wikidot.com/partitions
662 Jagan Teki <jagan@amarulasolutions.com>
664 Simon Glass <sjg@chromium.org>