blob: d78d993cfc6f4008ce5eff2d1b6cfe4a95f2e2c0 [file] [log] [blame]
Tom Rini10e47792018-05-06 17:58:06 -04001# SPDX-License-Identifier: GPL-2.0+
Simon Glassf874fdc2015-08-30 16:55:43 -06002#
3# Copyright (C) 2015 Google. Inc
4# Written by Simon Glass <sjg@chromium.org>
Simon Glassf874fdc2015-08-30 16:55:43 -06005
6U-Boot on Rockchip
7==================
8
Simon Glassd06e1ff2019-01-21 14:53:23 -07009A wide range of Rockchip SoCs are supported in mainline U-Boot
Simon Glassf874fdc2015-08-30 16:55:43 -060010
Simon Glassf874fdc2015-08-30 16:55:43 -060011
12Prerequisites
13=============
14
15You will need:
16
Simon Glass419bf142016-01-21 19:45:25 -070017 - Firefly RK3288 board or something else with a supported RockChip SoC
Simon Glassf874fdc2015-08-30 16:55:43 -060018 - 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)
21 - rkflashtool [3]
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
26
27
28Building
29========
30
Simon Glassb32ae5f2019-01-21 14:53:22 -070031At present 12 RK3288 boards are supported:
Simon Glassf874fdc2015-08-30 16:55:43 -060032
Xu Ziyuan3da09a82016-07-05 18:06:30 +080033 - EVB RK3288 - use evb-rk3288 configuration
jk.kernel@gmail.comb1aeb092016-07-26 18:28:29 +080034 - Fennec RK3288 - use fennec-rk3288 configuration
Xu Ziyuan535b3dc2016-08-01 08:46:19 +080035 - Firefly RK3288 - use firefly-rk3288 configuration
36 - Hisense Chromebook - use chromebook_jerry configuration
Simon Glassb32ae5f2019-01-21 14:53:22 -070037 - Asus C100P Chromebook - use chromebook_minnie configuration
38 - Asus Chromebit - use chromebook_mickey configuration
Jernej Skrabec971e53a2017-03-30 01:23:14 +020039 - MiQi RK3288 - use miqi-rk3288 configuration
Wadim Egorove2c69d62017-06-19 12:36:41 +020040 - phyCORE-RK3288 RDK - use phycore-rk3288 configuration
jk.kernel@gmail.com7a614ac2016-07-26 18:28:30 +080041 - PopMetal RK3288 - use popmetal-rk3288 configuration
Xu Ziyuan535b3dc2016-08-01 08:46:19 +080042 - Radxa Rock 2 - use rock2 configuration
Jernej Skrabec3c6372d2017-03-30 01:23:13 +020043 - Tinker RK3288 - use tinker-rk3288 configuration
Simon Glassb32ae5f2019-01-21 14:53:22 -070044 - Vyasa RK3288 - use vyasa-rk3288 configuration
Simon Glassf874fdc2015-08-30 16:55:43 -060045
Simon Glassb32ae5f2019-01-21 14:53:22 -070046Two RK3036 boards are supported:
huang lin86d0a902015-11-17 14:20:31 +080047
Simon Glass419bf142016-01-21 19:45:25 -070048 - EVB RK3036 - use evb-rk3036 configuration
49 - Kylin - use kylin_rk3036 configuration
huang lin86d0a902015-11-17 14:20:31 +080050
Matwey V. Kornilov971fd482019-06-09 00:27:18 +030051Two RK3328 board are supported:
Simon Glassb32ae5f2019-01-21 14:53:22 -070052
Matwey V. Kornilov971fd482019-06-09 00:27:18 +030053 - EVB RK3328 - use evb-rk3328_defconfig
54 - Pine64 Rock64 board - use rock64-rk3328_defconfig
Simon Glassb32ae5f2019-01-21 14:53:22 -070055
Simon Glass8fbf9922019-01-21 14:53:36 -070056Size RK3399 boards are supported (aarch64):
Simon Glassb32ae5f2019-01-21 14:53:22 -070057
58 - EBV RK3399 - use evb_rk3399 configuration
59 - Firefly RK3399 - use the firefly_rk3399 configuration
60 - Puma - use puma_rk3399 configuration
61 - Ficus - use ficus-rk3399 configuration
62 - Rock960 (Vamrs) - use rock960-rk3399 configuration
Simon Glass8fbf9922019-01-21 14:53:36 -070063 - Bob - use chromebook_bob configuration
Simon Glassb32ae5f2019-01-21 14:53:22 -070064
65Four RK3368 boards are supported:
66
67 - Sheep - use sheep-rk3368 configuration
68 - Lion - use lion-rk3368 configuration
69 - Geekbox - use geekbox configuration
70 - EVB PX5 - use evb-px5 configuration
71
72One RK3128 board is supported:
73
74 - EVB RK3128 - use evb-rk3128 configuration
75
76One RK3229 board is supported:
77
78 - EVB RK3229 - use evb-rk3229 configuration
79
80Two RV1108 boards are supported:
81
82 - EVB RV1108 - use evb-rv1108 configuration
83 - Elgin R1 - use elgin-rv1108 configuration
84
85One RV3188 baord is supported:
86
87 - Raxda Rock - use rock configuration
88
89
Simon Glassf874fdc2015-08-30 16:55:43 -060090For example:
91
Jagan Teki36a49db2019-05-08 11:11:51 +0530921. To build RK3288 board:
93
Simon Glassf874fdc2015-08-30 16:55:43 -060094 CROSS_COMPILE=arm-linux-gnueabi- make O=firefly firefly-rk3288_defconfig all
95
Jagan Teki36a49db2019-05-08 11:11:51 +053096 (or you can use another cross compiler if you prefer)
97
982. To build RK3399 board:
99
100 Option 1: Package the image with Rockchip miniloader:
101
102 - Compile U-Boot
103
104 => cd /path/to/u-boot
105 => make nanopi-neo4-rk3399_defconfig
106 => make
107 => make u-boot.itb
108
109 - Get the rkbin
110
111 => git clone https://github.com/rockchip-linux/rkbin.git
112
113 - Create trust.img
114
115 => cd /path/to/rkbin
116 => ./tools/trust_merger RKTRUST/RK3399TRUST.ini
117
118 - Create uboot.img
119
120 => cd /path/to/rkbin
121 => ./tools/loaderimage --pack --uboot /path/to/u-boot/u-boot-dtb.bin uboot.img
122
123 (Get trust.img and uboot.img)
124
125 Option 2: Package the image with SPL:
126
127 - We need the Python elftools.elf.elffile library for make_fit_atf.py to work
128
129 => sudo apt-get install python-pyelftools
130
131 - Export cross compiler path for aarch64
132
133 - Compile ATF
Simon Glassf874fdc2015-08-30 16:55:43 -0600134
Jagan Teki36a49db2019-05-08 11:11:51 +0530135 For Puma board.
136
137 => git clone git://git.theobroma-systems.com/arm-trusted-firmware.git
138 => cd arm-trusted-firmware
139 => make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
140
Jagan Tekia91124e2019-06-20 15:37:39 +0530141 (export bl31.bin)
142 => export BL31=/path/to/arm-trusted-firmware/build/rk3399/release/bl31/bl31.bin
Jagan Teki36a49db2019-05-08 11:11:51 +0530143
144 For rest of rk3399 boards.
145
146 => git clone https://github.com/ARM-software/arm-trusted-firmware.git
147 => cd arm-trusted-firmware
148
149 (export cross compiler path for Cortex-M0 MCU likely arm-none-eabi-)
150 => make realclean
151 => make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399
152
Jagan Teki2c2b4292019-06-20 16:29:22 +0530153 (export bl31.elf)
154 => export BL31=/path/to/arm-trusted-firmware/build/rk3399/release/bl31/bl31.elf
Jagan Teki36a49db2019-05-08 11:11:51 +0530155
156 - Compile PMU M0 firmware
157
158 This is optional for most of the rk3399 boards and required only for Puma board.
159
160 => git clone git://git.theobroma-systems.com/rk3399-cortex-m0.git
161 => cd rk3399-cortex-m0
162
163 (export cross compiler path for Cortex-M0 PMU)
164 => make CROSS_COMPILE=arm-cortex_m0-eabi-
165
Jagan Tekia91124e2019-06-20 15:37:39 +0530166 (export rk3399m0.bin)
167 => export PMUM0=/path/to/rk3399-cortex-m0/rk3399m0.bin
Jagan Teki36a49db2019-05-08 11:11:51 +0530168
169 - Compile U-Boot
170
171 => cd /path/to/u-boot
172 => make orangepi-rk3399_defconfig
173 => make
174 => make u-boot.itb
175
176 (Get spl/u-boot-spl-dtb.bin, u-boot.itb images and some boards would get
Jagan Teki9e103192019-05-29 13:55:49 +0530177 spl/u-boot-spl.bin since it doesn't enable CONFIG_SPL_OF_CONTROL
178
179 If TPL enabled on the target, get tpl/u-boot-tpl-dtb.bin or tpl/u-boot-tpl.bin
180 if CONFIG_TPL_OF_CONTROL not enabled)
Simon Glassf874fdc2015-08-30 16:55:43 -0600181
182Writing to the board with USB
183=============================
184
185For USB to work you must get your board into ROM boot mode, either by erasing
186your MMC or (perhaps) holding the recovery button when you boot the board.
187To erase your MMC, you can boot into Linux and type (as root)
188
189 dd if=/dev/zero of=/dev/mmcblk0 bs=1M
190
191Connect your board's OTG port to your computer.
192
193To create a suitable image and write it to the board:
194
Jeffy Chen0510e2b2015-11-27 12:07:18 +0800195 ./firefly-rk3288/tools/mkimage -n rk3288 -T rkimage -d \
Simon Glass1510ffe2015-08-30 16:55:52 -0600196 ./firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
Simon Glassf874fdc2015-08-30 16:55:43 -0600197 cat out | openssl rc4 -K 7c4e0304550509072d2c7b38170d1711 | rkflashtool l
198
199If all goes well you should something like:
200
201 U-Boot SPL 2015.07-rc1-00383-ge345740-dirty (Jun 03 2015 - 10:06:49)
202 Card did not respond to voltage select!
203 spl: mmc init failed with error: -17
204 ### ERROR ### Please RESET the board ###
205
206You will need to reset the board before each time you try. Yes, that's all
207it does so far. If support for the Rockchip USB protocol or DFU were added
208in SPL then we could in principle load U-Boot and boot to a prompt from USB
209as several other platforms do. However it does not seem to be possible to
210use the existing boot ROM code from SPL.
211
212
213Booting from an SD card
214=======================
215
216To write an image that boots from an SD card (assumed to be /dev/sdc):
217
Jeffy Chen0510e2b2015-11-27 12:07:18 +0800218 ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
Simon Glass1510ffe2015-08-30 16:55:52 -0600219 firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
220 sudo dd if=out of=/dev/sdc seek=64 && \
Kever Yangc121f8a2017-11-02 15:16:35 +0800221 sudo dd if=firefly-rk3288/u-boot-dtb.img of=/dev/sdc seek=16384
Simon Glassf874fdc2015-08-30 16:55:43 -0600222
223This puts the Rockchip header and SPL image first and then places the U-Boot
Goldschmidt Simon4d930572017-11-10 11:38:32 +0000224image at block 16384 (i.e. 8MB from the start of the SD card). This
Simon Glassf874fdc2015-08-30 16:55:43 -0600225corresponds with this setting in U-Boot:
226
Kever Yangc121f8a2017-11-02 15:16:35 +0800227 #define CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR 0x4000
Simon Glassf874fdc2015-08-30 16:55:43 -0600228
229Put this SD (or micro-SD) card into your board and reset it. You should see
230something like:
231
Simon Glass419bf142016-01-21 19:45:25 -0700232 U-Boot 2016.01-rc2-00309-ge5bad3b-dirty (Jan 02 2016 - 23:41:59 -0700)
Simon Glassf874fdc2015-08-30 16:55:43 -0600233
Simon Glass419bf142016-01-21 19:45:25 -0700234 Model: Radxa Rock 2 Square
Simon Glassf874fdc2015-08-30 16:55:43 -0600235 DRAM: 2 GiB
Simon Glass419bf142016-01-21 19:45:25 -0700236 MMC: dwmmc@ff0f0000: 0, dwmmc@ff0c0000: 1
237 *** Warning - bad CRC, using default environment
Simon Glassf874fdc2015-08-30 16:55:43 -0600238
Simon Glass419bf142016-01-21 19:45:25 -0700239 In: serial
240 Out: vop@ff940000.vidconsole
241 Err: serial
242 Net: Net Initialization Skipped
243 No ethernet found.
244 Hit any key to stop autoboot: 0
Simon Glassf874fdc2015-08-30 16:55:43 -0600245 =>
246
Xu Ziyuan5401eb82016-07-12 19:09:49 +0800247The rockchip bootrom can load and boot an initial spl, then continue to
Heinrich Schuchardtf4359782018-06-03 20:41:29 +0200248load a second-stage bootloader (ie. U-Boot) as soon as the control is returned
249to the bootrom. Both the RK3288 and the RK3036 use this special boot sequence.
250The configuration option enabling this is:
Xu Ziyuan5401eb82016-07-12 19:09:49 +0800251
Heinrich Schuchardtf4359782018-06-03 20:41:29 +0200252 CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y
Xu Ziyuan5401eb82016-07-12 19:09:49 +0800253
254You can create the image via the following operations:
255
256 ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
257 firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
258 cat firefly-rk3288/u-boot-dtb.bin >> out && \
259 sudo dd if=out of=/dev/sdc seek=64
260
Simon Glass419bf142016-01-21 19:45:25 -0700261If you have an HDMI cable attached you should see a video console.
262
huang lin86d0a902015-11-17 14:20:31 +0800263For evb_rk3036 board:
Jeffy Chen0510e2b2015-11-27 12:07:18 +0800264 ./evb-rk3036/tools/mkimage -n rk3036 -T rksd -d evb-rk3036/spl/u-boot-spl.bin out && \
huang lin86d0a902015-11-17 14:20:31 +0800265 cat evb-rk3036/u-boot-dtb.bin >> out && \
266 sudo dd if=out of=/dev/sdc seek=64
267
268Note: rk3036 SDMMC and debug uart use the same iomux, so if you boot from SD, the
269 debug uart must be disabled
Simon Glassf874fdc2015-08-30 16:55:43 -0600270
Heiko Stübnerfdf967c2017-03-24 00:41:34 +0100271
Jagan Teki387fd4b2017-09-27 23:03:12 +0530272Booting from an SD card on RK3288 with TPL
273==========================================
274
275Since the size of SPL can't be exceeded 0x8000 bytes in RK3288, it is not possible add
276new SPL features like Falcon mode or etc.
277
278So introduce TPL so-that adding new features to SPL is possible because now TPL should
279run minimal with code like DDR, clock etc and rest of new features in SPL.
280
281As of now TPL is added on Vyasa-RK3288 board.
282
283To write an image that boots from an SD card (assumed to be /dev/mmcblk0):
284
285 ./tools/mkimage -n rk3288 -T rksd -d ./tpl/u-boot-tpl.bin out &&
286 cat ./spl/u-boot-spl-dtb.bin >> out &&
287 sudo dd if=out of=/dev/mmcblk0 seek=64 &&
Jagan Teki354a9f82017-11-10 17:18:43 +0530288 sudo dd if=u-boot-dtb.img of=/dev/mmcblk0 seek=16384
Jagan Teki387fd4b2017-09-27 23:03:12 +0530289
Heiko Stübnerfdf967c2017-03-24 00:41:34 +0100290Booting from an SD card on RK3188
291=================================
292
293For rk3188 boards the general storage onto the card stays the same as
294described above, but the image creation needs a bit more care.
295
296The bootrom of rk3188 expects to find a small 1kb loader which returns
297control to the bootrom, after which it will load the real loader, which
Philipp Tomsich16c689c2017-10-10 16:21:15 +0200298can then be up to 29kb in size and does the regular ddr init. This is
299handled by a single image (built as the SPL stage) that tests whether
300it is handled for the first or second time via code executed from the
301boot0-hook.
Heiko Stübnerfdf967c2017-03-24 00:41:34 +0100302
303Additionally the rk3188 requires everything the bootrom loads to be
304rc4-encrypted. Except for the very first stage the bootrom always reads
305and decodes 2kb pages, so files should be sized accordingly.
306
307# copy tpl, pad to 1020 bytes and append spl
Philipp Tomsich16c689c2017-10-10 16:21:15 +0200308tools/mkimage -n rk3188 -T rksd -d spl/u-boot-spl.bin out
Heiko Stübnerfdf967c2017-03-24 00:41:34 +0100309
310# truncate, encode and append u-boot.bin
311truncate -s %2048 u-boot.bin
312cat u-boot.bin | split -b 512 --filter='openssl rc4 -K 7C4E0304550509072D2C7B38170D1711' >> out
313
Matwey V. Kornilov971fd482019-06-09 00:27:18 +0300314Booting from an SD card on Pine64 Rock64 (RK3328)
315=================================================
316
317For Rock64 rk3328 board the following three parts are required:
318TPL, SPL, and the u-boot image tree blob. While u-boot-spl.bin and
319u-boot.itb are to be compiled as usual, TPL is currently not
320implemented in u-boot, so you need to pick one from rkbin:
321
322 - Get the rkbin
323
324 => git clone https://github.com/rockchip-linux/rkbin.git
325
326 - Create TPL/SPL image
327
328 => tools/mkimage -n rk3328 -T rksd -d rkbin/bin/rk33/rk3328_ddr_333MHz_v1.16.bin idbloader.img
329 => cat spl/u-boot-spl.bin >> idbloader.img
330
331 - Write TPL/SPL image at 64 sector
332
333 => sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
334
335 - Write u-boot image tree blob at 16384 sector
336
337 => sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
338
Jagan Teki36a49db2019-05-08 11:11:51 +0530339Booting from an SD card on RK3399
340=================================
341
342To write an image that boots from an SD card (assumed to be /dev/sdc):
343
344Option 1: Package the image with Rockchip miniloader:
345
346 - Create idbloader.img
347
348 => cd /path/to/u-boot
349 => ./tools/mkimage -n rk3399 -T rksd -d /path/to/rkbin/bin/rk33/rk3399_ddr_800MHz_v1.20.bin idbloader.img
350 => cat /path/to/rkbin/bin/rk33/rk3399_miniloader_v1.19.bin >> idbloader.img
351
352 - Write idbloader.img at 64 sector
353
354 => sudo dd if=idbloader.img of=/dev/sdc seek=64
355
356 - Write trust.img at 24576
357
358 => sudo dd if=trust.img of=/dev/sdc seek=24576
359
360 - Write uboot.img at 16384 sector
361
362 => sudo dd if=uboot.img of=/dev/sdc seek=16384
363 => sync
364
365Put this SD (or micro-SD) card into your board and reset it. You should see
366something like:
367
368DDR Version 1.20 20190314
369In
370Channel 0: DDR3, 933MHz
371Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
372no stride
373ch 0 ddrconfig = 0x101, ddrsize = 0x20
374pmugrf_os_reg[2] = 0x10006281, stride = 0x17
375OUT
376Boot1: 2019-03-14, version: 1.19
377CPUId = 0x0
378ChipType = 0x10, 239
379mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
380mmc: ERROR: Card did not respond to voltage select!
381emmc reinit
382mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
383mmc: ERROR: Card did not respond to voltage select!
384emmc reinit
385mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
386mmc: ERROR: Card did not respond to voltage select!
387SdmmcInit=2 1
388mmc0:cmd5,20
389SdmmcInit=0 0
390BootCapSize=0
391UserCapSize=60543MB
392FwPartOffset=2000 , 0
393StorageInit ok = 45266
394SecureMode = 0
395SecureInit read PBA: 0x4
396SecureInit read PBA: 0x404
397SecureInit read PBA: 0x804
398SecureInit read PBA: 0xc04
399SecureInit read PBA: 0x1004
400SecureInit read PBA: 0x1404
401SecureInit read PBA: 0x1804
402SecureInit read PBA: 0x1c04
403SecureInit ret = 0, SecureMode = 0
404atags_set_bootdev: ret:(0)
405GPT 0x3380ec0 signature is wrong
406recovery gpt...
407GPT 0x3380ec0 signature is wrong
408recovery gpt fail!
409LoadTrust Addr:0x4000
410No find bl30.bin
411Load uboot, ReadLba = 2000
412hdr 0000000003380880 + 0x0:0x88,0x41,0x3e,0x97,0xe6,0x61,0x54,0x23,0xe9,0x5a,0xd1,0x2b,0xdc,0x2f,0xf9,0x35,
413
414Load OK, addr=0x200000, size=0x9c9c0
415RunBL31 0x10000
416NOTICE: BL31: v1.3(debug):370ab80
417NOTICE: BL31: Built : 09:23:41, Mar 4 2019
418NOTICE: BL31: Rockchip release version: v1.1
419INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
420INFO: Using opteed sec cpu_context!
421INFO: boot cpu mask: 0
422INFO: plat_rockchip_pmu_init(1181): pd status 3e
423INFO: BL31: Initializing runtime services
424INFO: BL31: Initializing BL32
425INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-195-g8f090d20 #6 Fri Dec 7 06:11:20 UTC 2018 aarch64)
426
427INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2
428
429INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
430INFO: BL31: Preparing for EL3 exit to normal world
431INFO: Entry point address = 0x200000
432INFO: SPSR = 0x3c9
433
434
435U-Boot 2019.04-rc4-00136-gfd121f9641-dirty (Apr 16 2019 - 14:02:47 +0530)
436
437Model: FriendlyARM NanoPi NEO4
438DRAM: 1022 MiB
439MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
440Loading Environment from MMC... *** Warning - bad CRC, using default environment
441
442In: serial@ff1a0000
443Out: serial@ff1a0000
444Err: serial@ff1a0000
445Model: FriendlyARM NanoPi NEO4
446Net: eth0: ethernet@fe300000
447Hit any key to stop autoboot: 0
448=>
449
450Option 2: Package the image with SPL:
451
452 - Prefix rk3399 header to SPL image
453
454 => cd /path/to/u-boot
455 => ./tools/mkimage -n rk3399 -T rksd -d spl/u-boot-spl-dtb.bin out
456
457 - Write prefixed SPL at 64th sector
458
459 => sudo dd if=out of=/dev/sdc seek=64
460
461 - Write U-Boot proper at 16384 sector
462
463 => sudo dd if=u-boot.itb of=/dev/sdc seek=16384
464 => sync
465
466Put this SD (or micro-SD) card into your board and reset it. You should see
467something like:
468
469U-Boot SPL board init
470Trying to boot from MMC1
471
472
473U-Boot 2019.01-00004-g14db5ee998 (Mar 11 2019 - 13:18:41 +0530)
474
475Model: Orange Pi RK3399 Board
476DRAM: 2 GiB
477MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
478Loading Environment from MMC... OK
479In: serial@ff1a0000
480Out: serial@ff1a0000
481Err: serial@ff1a0000
482Model: Orange Pi RK3399 Board
483Net: eth0: ethernet@fe300000
484Hit any key to stop autoboot: 0
485=>
Heiko Stübnerfdf967c2017-03-24 00:41:34 +0100486
Jagan Teki9e103192019-05-29 13:55:49 +0530487Option 3: Package the image with TPL:
488
489 - Prefix rk3399 header to TPL image
490
491 => cd /path/to/u-boot
492 => ./tools/mkimage -n rk3399 -T rksd -d tpl/u-boot-tpl-dtb.bin out
493
494 - Concatinate tpl with spl
495
496 => cd /path/to/u-boot
497 => cat ./spl/u-boot-spl-dtb.bin >> out
498
499 - Write tpl+spl at 64th sector
500
501 => sudo dd if=out of=/dev/sdc seek=64
502
503 - Write U-Boot proper at 16384 sector
504
505 => sudo dd if=u-boot.itb of=/dev/sdc seek=16384
506 => sync
507
508Put this SD (or micro-SD) card into your board and reset it. You should see
509something like:
510
511U-Boot TPL board init
512Trying to boot from BOOTROM
513Returning to boot ROM...
514
515U-Boot SPL board init
516Trying to boot from MMC1
517
518
519U-Boot 2019.07-rc1-00241-g5b3244767a (May 08 2019 - 10:51:06 +0530)
520
521Model: Orange Pi RK3399 Board
522DRAM: 2 GiB
523MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
524Loading Environment from MMC... OK
525In: serial@ff1a0000
526Out: serial@ff1a0000
527Err: serial@ff1a0000
528Model: Orange Pi RK3399 Board
529Net: eth0: ethernet@fe300000
530Hit any key to stop autoboot: 0
531=>
532
Xu Ziyuanadd8d492016-07-18 09:56:46 +0800533Using fastboot on rk3288
534========================
Xu Ziyuanadd8d492016-07-18 09:56:46 +0800535- Write GPT partition layout to mmc device which fastboot want to use it to
536store the image
537
538 => gpt write mmc 1 $partitions
539
540- Invoke fastboot command to prepare
541
542 => fastboot 1
543
544- Start fastboot request on PC
545
546 fastboot -i 0x2207 flash loader evb-rk3288/spl/u-boot-spl-dtb.bin
547
548You should see something like:
549
550 => fastboot 1
551 WARNING: unknown variable: partition-type:loader
552 Starting download of 357796 bytes
553 ..
554 downloading of 357796 bytes finished
555 Flashing Raw Image
556 ........ wrote 357888 bytes to 'loader'
557
Simon Glassf874fdc2015-08-30 16:55:43 -0600558Booting from SPI
559================
560
Simon Glass8fbf9922019-01-21 14:53:36 -0700561To write an image that boots from SPI flash (e.g. for the Haier Chromebook or
562Bob):
Simon Glassf874fdc2015-08-30 16:55:43 -0600563
Simon Glass2ac46482015-12-29 05:22:45 -0700564 ./chromebook_jerry/tools/mkimage -n rk3288 -T rkspi \
565 -d chromebook_jerry/spl/u-boot-spl-dtb.bin spl.bin && \
566 dd if=spl.bin of=spl-out.bin bs=128K conv=sync && \
567 cat spl-out.bin chromebook_jerry/u-boot-dtb.img >out.bin && \
Simon Glassf874fdc2015-08-30 16:55:43 -0600568 dd if=out.bin of=out.bin.pad bs=4M conv=sync
569
570This converts the SPL image to the required SPI format by adding the Rockchip
Simon Glass27f8d372019-01-21 14:53:27 -0700571header and skipping every second 2KB block. Then the U-Boot image is written at
Simon Glassf874fdc2015-08-30 16:55:43 -0600572offset 128KB and the whole image is padded to 4MB which is the SPI flash size.
573The position of U-Boot is controlled with this setting in U-Boot:
574
575 #define CONFIG_SYS_SPI_U_BOOT_OFFS (128 << 10)
576
577If you have a Dediprog em100pro connected then you can write the image with:
578
579 sudo em100 -s -c GD25LQ32 -d out.bin.pad -r
580
581When booting you should see something like:
582
583 U-Boot SPL 2015.07-rc2-00215-g9a58220-dirty (Jun 23 2015 - 12:11:32)
584
585
586 U-Boot 2015.07-rc2-00215-g9a58220-dirty (Jun 23 2015 - 12:11:32 -0600)
587
588 Model: Google Jerry
589 DRAM: 2 GiB
590 MMC:
591 Using default environment
592
593 In: serial@ff690000
594 Out: serial@ff690000
595 Err: serial@ff690000
596 =>
597
Simon Glassf874fdc2015-08-30 16:55:43 -0600598Future work
599===========
600
601Immediate priorities are:
602
Simon Glassf874fdc2015-08-30 16:55:43 -0600603- USB host
604- USB device
Simon Glass419bf142016-01-21 19:45:25 -0700605- Run CPU at full speed (code exists but we only see ~60 DMIPS maximum)
Simon Glassf874fdc2015-08-30 16:55:43 -0600606- NAND flash
Simon Glassf874fdc2015-08-30 16:55:43 -0600607- Boot U-Boot proper over USB OTG (at present only SPL works)
608
609
610Development Notes
611=================
612
613There are plenty of patches in the links below to help with this work.
614
615[1] https://github.com/rkchrome/uboot.git
616[2] https://github.com/linux-rockchip/u-boot-rockchip.git branch u-boot-rk3288
617[3] https://github.com/linux-rockchip/rkflashtool.git
618[4] http://wiki.t-firefly.com/index.php/Firefly-RK3288/Serial_debug/en
619
620rkimage
621-------
622
623rkimage.c produces an SPL image suitable for sending directly to the boot ROM
624over USB OTG. This is a very simple format - just the string RK32 (as 4 bytes)
625followed by u-boot-spl-dtb.bin.
626
627The boot ROM loads image to 0xff704000 which is in the internal SRAM. The SRAM
628starts at 0xff700000 and extends to 0xff718000 where we put the stack.
629
630rksd
631----
632
633rksd.c produces an image consisting of 32KB of empty space, a header and
634u-boot-spl-dtb.bin. The header is defined by 'struct header0_info' although
635most of the fields are unused by U-Boot. We just need to specify the
636signature, a flag and the block offset and size of the SPL image.
637
638The header occupies a single block but we pad it out to 4 blocks. The header
639is encoding using RC4 with the key 7c4e0304550509072d2c7b38170d1711. The SPL
640image can be encoded too but we don't do that.
641
642The maximum size of u-boot-spl-dtb.bin which the boot ROM will read is 32KB,
643or 0x40 blocks. This is a severe and annoying limitation. There may be a way
644around this limitation, since there is plenty of SRAM, but at present the
645board refuses to boot if this limit is exceeded.
646
647The image produced is padded up to a block boundary (512 bytes). It should be
648written to the start of an SD card using dd.
649
650Since this image is set to load U-Boot from the SD card at block offset,
651CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR, dd should be used to write
652u-boot-dtb.img to the SD card at that offset. See above for instructions.
653
654rkspi
655-----
656
657rkspi.c produces an image consisting of a header and u-boot-spl-dtb.bin. The
658resulting image is then spread out so that only the first 2KB of each 4KB
659sector is used. The header is the same as with rksd and the maximum size is
660also 32KB (before spreading). The image should be written to the start of
661SPI flash.
662
663See above for instructions on how to write a SPI image.
664
Simon Glassb42f7e42016-01-21 19:45:08 -0700665rkmux.py
666--------
667
668You can use this script to create #defines for SoC register access. See the
669script for usage.
670
Simon Glassf874fdc2015-08-30 16:55:43 -0600671
672Device tree and driver model
673----------------------------
674
675Where possible driver model is used to provide a structure to the
676functionality. Device tree is used for configuration. However these have an
677overhead and in SPL with a 32KB size limit some shortcuts have been taken.
678In general all Rockchip drivers should use these features, with SPL-specific
679modifications where required.
680
Jacob Chen615cacc2016-10-08 13:47:42 +0800681GPT partition layout
682----------------------------
683
684Rockchip use a unified GPT partition layout in open source support.
685With this GPT partition layout, uboot can be compatilbe with other components,
686like miniloader, trusted-os, arm-trust-firmware.
687
688There are some documents about partitions in the links below.
689http://rockchip.wikidot.com/partitions
Simon Glassf874fdc2015-08-30 16:55:43 -0600690
691--
Jagan Teki36a49db2019-05-08 11:11:51 +0530692Jagan Teki <jagan@amarulasolutions.com>
69327 Mar 2019
Simon Glassf874fdc2015-08-30 16:55:43 -0600694Simon Glass <sjg@chromium.org>
69524 June 2015