README.rockchip 23 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765
  1. # SPDX-License-Identifier: GPL-2.0+
  2. #
  3. # Copyright (C) 2015 Google. Inc
  4. # Written by Simon Glass <sjg@chromium.org>
  5. U-Boot on Rockchip
  6. ==================
  7. A wide range of Rockchip SoCs are supported in mainline U-Boot
  8. Prerequisites
  9. =============
  10. You will need:
  11. - Firefly RK3288 board or something else with a supported RockChip SoC
  12. - Power connection to 5V using the supplied micro-USB power cable
  13. - Separate USB serial cable attached to your computer and the Firefly
  14. (connect to the micro-USB connector below the logo)
  15. - rkflashtool [3]
  16. - openssl (sudo apt-get install openssl)
  17. - Serial UART connection [4]
  18. - Suitable ARM cross compiler, e.g.:
  19. sudo apt-get install gcc-4.7-arm-linux-gnueabi
  20. Building
  21. ========
  22. At present 11 RK3288 boards are supported:
  23. - EVB RK3288 - use evb-rk3288 configuration
  24. - Firefly RK3288 - use firefly-rk3288 configuration
  25. - Hisense Chromebook - use chromebook_jerry configuration
  26. - Asus C100P Chromebook - use chromebook_minnie configuration
  27. - Asus Chromebit - use chromebook_mickey configuration
  28. - MiQi RK3288 - use miqi-rk3288 configuration
  29. - phyCORE-RK3288 RDK - use phycore-rk3288 configuration
  30. - PopMetal RK3288 - use popmetal-rk3288 configuration
  31. - Radxa Rock 2 - use rock2 configuration
  32. - Tinker RK3288 - use tinker-rk3288 configuration
  33. - Vyasa RK3288 - use vyasa-rk3288 configuration
  34. Two RK3036 boards are supported:
  35. - EVB RK3036 - use evb-rk3036 configuration
  36. - Kylin - use kylin_rk3036 configuration
  37. Two RK3308 boards are supported:
  38. - EVB RK3308 - use evb-rk3308 configuration
  39. - ROC-CC-RK3308 - use roc-cc-rk3308 configuration
  40. Two RK3328 board are supported:
  41. - EVB RK3328 - use evb-rk3328_defconfig
  42. - Pine64 Rock64 board - use rock64-rk3328_defconfig
  43. Size RK3399 boards are supported (aarch64):
  44. - EBV RK3399 - use evb_rk3399 configuration
  45. - Firefly RK3399 - use the firefly_rk3399 configuration
  46. - Puma - use puma_rk3399 configuration
  47. - Ficus - use ficus-rk3399 configuration
  48. - Rock960 (Vamrs) - use rock960-rk3399 configuration
  49. - Bob - use chromebook_bob configuration
  50. Four RK3368 boards are supported:
  51. - Sheep - use sheep-rk3368 configuration
  52. - Lion - use lion-rk3368 configuration
  53. - Geekbox - use geekbox configuration
  54. - EVB PX5 - use evb-px5 configuration
  55. One RK3128 board is supported:
  56. - EVB RK3128 - use evb-rk3128 configuration
  57. One RK3229 board is supported:
  58. - EVB RK3229 - use evb-rk3229 configuration
  59. Two RV1108 boards are supported:
  60. - EVB RV1108 - use evb-rv1108 configuration
  61. - Elgin R1 - use elgin-rv1108 configuration
  62. One RV3188 baord is supported:
  63. - Raxda Rock - use rock configuration
  64. For example:
  65. 1. To build RK3288 board:
  66. CROSS_COMPILE=arm-linux-gnueabi- make O=firefly firefly-rk3288_defconfig all
  67. (or you can use another cross compiler if you prefer)
  68. 2. To build RK3308 board:
  69. - Get the rkbin
  70. => git clone https://github.com/rockchip-linux/rkbin.git
  71. - Compile U-Boot
  72. => cd /path/to/u-boot
  73. => export BL31=/path/to/rkbin/bin/rk33/rk3308_bl31_v2.22.elf
  74. => make roc-cc-rk3308_defconfig
  75. => make CROSS_COMPILE=aarch64-linux-gnu- all
  76. => ./tools/mkimage -n rk3308 -T rksd -d /path/to/rkbin/bin/rk33/rk3308_ddr_589MHz_uart2_m0_v1.26.bin idbloader.img
  77. => cat spl/u-boot-spl.bin >> idbloader.img
  78. 3. To build RK3399 board:
  79. Option 1: Package the image with Rockchip miniloader:
  80. - Compile U-Boot
  81. => cd /path/to/u-boot
  82. => make nanopi-neo4-rk3399_defconfig
  83. => make
  84. - Get the rkbin
  85. => git clone https://github.com/rockchip-linux/rkbin.git
  86. - Create trust.img
  87. => cd /path/to/rkbin
  88. => ./tools/trust_merger RKTRUST/RK3399TRUST.ini
  89. - Create uboot.img
  90. => cd /path/to/rkbin
  91. => ./tools/loaderimage --pack --uboot /path/to/u-boot/u-boot-dtb.bin uboot.img
  92. (Get trust.img and uboot.img)
  93. Option 2: Package the image with SPL:
  94. - Export cross compiler path for aarch64
  95. - Compile ATF
  96. For Puma board.
  97. => git clone git://git.theobroma-systems.com/arm-trusted-firmware.git
  98. => cd arm-trusted-firmware
  99. => make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399 bl31
  100. (export bl31.bin)
  101. => export BL31=/path/to/arm-trusted-firmware/build/rk3399/release/bl31/bl31.bin
  102. For rest of rk3399 boards.
  103. => git clone https://github.com/ARM-software/arm-trusted-firmware.git
  104. => cd arm-trusted-firmware
  105. (export cross compiler path for Cortex-M0 MCU likely arm-none-eabi-)
  106. => make realclean
  107. => make CROSS_COMPILE=aarch64-linux-gnu- PLAT=rk3399
  108. (export bl31.elf)
  109. => export BL31=/path/to/arm-trusted-firmware/build/rk3399/release/bl31/bl31.elf
  110. - Compile PMU M0 firmware
  111. This is optional for most of the rk3399 boards and required only for Puma board.
  112. => git clone git://git.theobroma-systems.com/rk3399-cortex-m0.git
  113. => cd rk3399-cortex-m0
  114. (export cross compiler path for Cortex-M0 PMU)
  115. => make CROSS_COMPILE=arm-cortex_m0-eabi-
  116. (export rk3399m0.bin)
  117. => export PMUM0=/path/to/rk3399-cortex-m0/rk3399m0.bin
  118. - Compile U-Boot
  119. => cd /path/to/u-boot
  120. => make orangepi-rk3399_defconfig
  121. => make
  122. (Get spl/u-boot-spl-dtb.bin, u-boot.itb images and some boards would get
  123. spl/u-boot-spl.bin since it doesn't enable CONFIG_SPL_OF_CONTROL
  124. If TPL enabled on the target, get tpl/u-boot-tpl-dtb.bin or tpl/u-boot-tpl.bin
  125. if CONFIG_TPL_OF_CONTROL not enabled)
  126. Writing to the board with USB
  127. =============================
  128. For USB to work you must get your board into ROM boot mode, either by erasing
  129. your MMC or (perhaps) holding the recovery button when you boot the board.
  130. To erase your MMC, you can boot into Linux and type (as root)
  131. dd if=/dev/zero of=/dev/mmcblk0 bs=1M
  132. Connect your board's OTG port to your computer.
  133. To create a suitable image and write it to the board:
  134. ./firefly-rk3288/tools/mkimage -n rk3288 -T rkimage -d \
  135. ./firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
  136. cat out | openssl rc4 -K 7c4e0304550509072d2c7b38170d1711 | rkflashtool l
  137. If all goes well you should something like:
  138. U-Boot SPL 2015.07-rc1-00383-ge345740-dirty (Jun 03 2015 - 10:06:49)
  139. Card did not respond to voltage select!
  140. spl: mmc init failed with error: -17
  141. ### ERROR ### Please RESET the board ###
  142. You will need to reset the board before each time you try. Yes, that's all
  143. it does so far. If support for the Rockchip USB protocol or DFU were added
  144. in SPL then we could in principle load U-Boot and boot to a prompt from USB
  145. as several other platforms do. However it does not seem to be possible to
  146. use the existing boot ROM code from SPL.
  147. Writing to the eMMC with USB on ROC-RK3308-CC
  148. =============================================
  149. For USB to work you must get your board into Bootrom mode,
  150. either by erasing the eMMC or short circuit the GND and D0
  151. on core board.
  152. Connect the board to your computer via tyepc.
  153. => rkdeveloptool db rk3308_loader_v1.26.117.bin
  154. => rkdeveloptool wl 0x40 idbloader.img
  155. => rkdeveloptool wl 0x4000 u-boot.itb
  156. => rkdeveloptool rd
  157. Then you will see the boot log from Debug UART at baud rate 1500000:
  158. DDR Version V1.26
  159. REGFB: 0x00000032, 0x00000032
  160. In
  161. 589MHz
  162. DDR3
  163. Col=10 Bank=8 Row=14 Size=256MB
  164. msch:1
  165. Returning to boot ROM...
  166. U-Boot SPL 2020.01-rc1-00225-g34b681327f (Nov 14 2019 - 10:58:04 +0800)
  167. Trying to boot from MMC1
  168. INFO: Preloader serial: 2
  169. NOTICE: BL31: v1.3(release):30f1405
  170. NOTICE: BL31: Built : 17:08:28, Sep 23 2019
  171. INFO: Lastlog: last=0x100000, realtime=0x102000, size=0x2000
  172. INFO: ARM GICv2 driver initialized
  173. INFO: Using opteed sec cpu_context!
  174. INFO: boot cpu mask: 1
  175. INFO: plat_rockchip_pmu_init: pd status 0xe b
  176. INFO: BL31: Initializing runtime services
  177. WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will rK
  178. ERROR: Error initializing runtime service opteed_fast
  179. INFO: BL31: Preparing for EL3 exit to normal world
  180. INFO: Entry point address = 0x600000
  181. INFO: SPSR = 0x3c9
  182. U-Boot 2020.01-rc1-00225-g34b681327f (Nov 14 2019 - 10:58:47 +0800)
  183. Model: Firefly ROC-RK3308-CC board
  184. DRAM: 254 MiB
  185. MMC: dwmmc@ff480000: 0, dwmmc@ff490000: 1
  186. rockchip_dnl_key_pressed read adc key val failed
  187. Net: No ethernet found.
  188. Hit any key to stop autoboot: 0
  189. Card did not respond to voltage select!
  190. switch to partitions #0, OK
  191. mmc1(part 0) is current device
  192. Scanning mmc 1:4...
  193. Found /extlinux/extlinux.conf
  194. Retrieving file: /extlinux/extlinux.conf
  195. 151 bytes read in 3 ms (48.8 KiB/s)
  196. 1: kernel-mainline
  197. Retrieving file: /Image
  198. 14737920 bytes read in 377 ms (37.3 MiB/s)
  199. append: earlycon=uart8250,mmio32,0xff0c0000 console=ttyS2,1500000n8
  200. Retrieving file: /rk3308-roc-cc.dtb
  201. 28954 bytes read in 4 ms (6.9 MiB/s)
  202. Flattened Device Tree blob at 01f00000
  203. Booting using the fdt blob at 0x1f00000
  204. ## Loading Device Tree to 000000000df3a000, end 000000000df44119 ... OK
  205. Starting kernel ...
  206. [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd042]
  207. [ 0.000000] Linux version 5.4.0-rc1-00040-g4dc2d508fa47-dirty (andy@B150) (gcc version 6.3.1 20170404 (Linaro GCC 6.3-209
  208. [ 0.000000] Machine model: Firefly ROC-RK3308-CC board
  209. [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000ff0c0000 (options '')
  210. [ 0.000000] printk: bootconsole [uart8250] enabled
  211. Booting from an SD card
  212. =======================
  213. To write an image that boots from an SD card (assumed to be /dev/sdc):
  214. ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
  215. firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
  216. sudo dd if=out of=/dev/sdc seek=64 && \
  217. sudo dd if=firefly-rk3288/u-boot-dtb.img of=/dev/sdc seek=16384
  218. This puts the Rockchip header and SPL image first and then places the U-Boot
  219. image at block 16384 (i.e. 8MB from the start of the SD card). This
  220. corresponds with this setting in U-Boot:
  221. #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
  223. something like:
  224. U-Boot 2016.01-rc2-00309-ge5bad3b-dirty (Jan 02 2016 - 23:41:59 -0700)
  225. Model: Radxa Rock 2 Square
  226. DRAM: 2 GiB
  227. MMC: dwmmc@ff0f0000: 0, dwmmc@ff0c0000: 1
  228. *** Warning - bad CRC, using default environment
  229. In: serial
  230. Out: vop@ff940000.vidconsole
  231. Err: serial
  232. Net: Net Initialization Skipped
  233. No ethernet found.
  234. Hit any key to stop autoboot: 0
  235. =>
  236. The rockchip bootrom can load and boot an initial spl, then continue to
  237. load a second-stage bootloader (ie. U-Boot) as soon as the control is returned
  238. to the bootrom. Both the RK3288 and the RK3036 use this special boot sequence.
  239. The configuration option enabling this is:
  240. CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y
  241. You can create the image via the following operations:
  242. ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
  243. firefly-rk3288/spl/u-boot-spl-dtb.bin out && \
  244. cat firefly-rk3288/u-boot-dtb.bin >> out && \
  245. sudo dd if=out of=/dev/sdc seek=64
  246. Or:
  247. ./firefly-rk3288/tools/mkimage -n rk3288 -T rksd -d \
  248. firefly-rk3288/spl/u-boot-spl-dtb.bin:firefly-rk3288/u-boot-dtb.bin \
  249. out && \
  250. sudo dd if=out of=/dev/sdc seek=64
  251. If you have an HDMI cable attached you should see a video console.
  252. For evb_rk3036 board:
  253. ./evb-rk3036/tools/mkimage -n rk3036 -T rksd -d evb-rk3036/spl/u-boot-spl.bin out && \
  254. cat evb-rk3036/u-boot-dtb.bin >> out && \
  255. sudo dd if=out of=/dev/sdc seek=64
  256. Or:
  257. ./evb-rk3036/tools/mkimage -n rk3036 -T rksd -d \
  258. evb-rk3036/spl/u-boot-spl.bin:evb-rk3036/u-boot-dtb.bin out && \
  259. sudo dd if=out of=/dev/sdc seek=64
  260. Note: rk3036 SDMMC and debug uart use the same iomux, so if you boot from SD, the
  261. debug uart must be disabled
  262. Booting from an SD card on RK3288 with TPL
  263. ==========================================
  264. Since the size of SPL can't be exceeded 0x8000 bytes in RK3288, it is not possible add
  265. new SPL features like Falcon mode or etc.
  266. So introduce TPL so-that adding new features to SPL is possible because now TPL should
  267. run minimal with code like DDR, clock etc and rest of new features in SPL.
  268. As of now TPL is added on Vyasa-RK3288 board.
  269. To write an image that boots from an SD card (assumed to be /dev/mmcblk0):
  270. sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64 &&
  271. sudo dd if=u-boot-dtb.img of=/dev/mmcblk0 seek=16384
  272. Booting from an SD card on RK3188
  273. =================================
  274. For rk3188 boards the general storage onto the card stays the same as
  275. described above, but the image creation needs a bit more care.
  276. The bootrom of rk3188 expects to find a small 1kb loader which returns
  277. control to the bootrom, after which it will load the real loader, which
  278. can then be up to 29kb in size and does the regular ddr init. This is
  279. handled by a single image (built as the SPL stage) that tests whether
  280. it is handled for the first or second time via code executed from the
  281. boot0-hook.
  282. Additionally the rk3188 requires everything the bootrom loads to be
  283. rc4-encrypted. Except for the very first stage the bootrom always reads
  284. and decodes 2kb pages, so files should be sized accordingly.
  285. # copy tpl, pad to 1020 bytes and append spl
  286. tools/mkimage -n rk3188 -T rksd -d spl/u-boot-spl.bin out
  287. # truncate, encode and append u-boot.bin
  288. truncate -s %2048 u-boot.bin
  289. cat u-boot.bin | split -b 512 --filter='openssl rc4 -K 7C4E0304550509072D2C7B38170D1711' >> out
  290. Booting from an SD card on Pine64 Rock64 (RK3328)
  291. =================================================
  292. For Rock64 rk3328 board the following three parts are required:
  293. TPL, SPL, and the u-boot image tree blob.
  294. - Write TPL/SPL image at 64 sector
  295. => sudo dd if=idbloader.img of=/dev/mmcblk0 seek=64
  296. - Write u-boot image tree blob at 16384 sector
  297. => sudo dd if=u-boot.itb of=/dev/mmcblk0 seek=16384
  298. Booting from an SD card on RK3399
  299. =================================
  300. To write an image that boots from an SD card (assumed to be /dev/sdc):
  301. Option 1: Package the image with Rockchip miniloader:
  302. - Create idbloader.img
  303. => cd /path/to/u-boot
  304. => ./tools/mkimage -n rk3399 -T rksd -d /path/to/rkbin/bin/rk33/rk3399_ddr_800MHz_v1.20.bin idbloader.img
  305. => cat /path/to/rkbin/bin/rk33/rk3399_miniloader_v1.19.bin >> idbloader.img
  306. - Write idbloader.img at 64 sector
  307. => sudo dd if=idbloader.img of=/dev/sdc seek=64
  308. - Write trust.img at 24576
  309. => sudo dd if=trust.img of=/dev/sdc seek=24576
  310. - Write uboot.img at 16384 sector
  311. => sudo dd if=uboot.img of=/dev/sdc seek=16384
  312. => sync
  313. Put this SD (or micro-SD) card into your board and reset it. You should see
  314. something like:
  315. DDR Version 1.20 20190314
  316. In
  317. Channel 0: DDR3, 933MHz
  318. Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB
  319. no stride
  320. ch 0 ddrconfig = 0x101, ddrsize = 0x20
  321. pmugrf_os_reg[2] = 0x10006281, stride = 0x17
  322. OUT
  323. Boot1: 2019-03-14, version: 1.19
  324. CPUId = 0x0
  325. ChipType = 0x10, 239
  326. mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
  327. mmc: ERROR: Card did not respond to voltage select!
  328. emmc reinit
  329. mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
  330. mmc: ERROR: Card did not respond to voltage select!
  331. emmc reinit
  332. mmc: ERROR: SDHCI ERR:cmd:0x102,stat:0x18000
  333. mmc: ERROR: Card did not respond to voltage select!
  334. SdmmcInit=2 1
  335. mmc0:cmd5,20
  336. SdmmcInit=0 0
  337. BootCapSize=0
  338. UserCapSize=60543MB
  339. FwPartOffset=2000 , 0
  340. StorageInit ok = 45266
  341. SecureMode = 0
  342. SecureInit read PBA: 0x4
  343. SecureInit read PBA: 0x404
  344. SecureInit read PBA: 0x804
  345. SecureInit read PBA: 0xc04
  346. SecureInit read PBA: 0x1004
  347. SecureInit read PBA: 0x1404
  348. SecureInit read PBA: 0x1804
  349. SecureInit read PBA: 0x1c04
  350. SecureInit ret = 0, SecureMode = 0
  351. atags_set_bootdev: ret:(0)
  352. GPT 0x3380ec0 signature is wrong
  353. recovery gpt...
  354. GPT 0x3380ec0 signature is wrong
  355. recovery gpt fail!
  356. LoadTrust Addr:0x4000
  357. No find bl30.bin
  358. Load uboot, ReadLba = 2000
  359. hdr 0000000003380880 + 0x0:0x88,0x41,0x3e,0x97,0xe6,0x61,0x54,0x23,0xe9,0x5a,0xd1,0x2b,0xdc,0x2f,0xf9,0x35,
  360. Load OK, addr=0x200000, size=0x9c9c0
  361. RunBL31 0x10000
  362. NOTICE: BL31: v1.3(debug):370ab80
  363. NOTICE: BL31: Built : 09:23:41, Mar 4 2019
  364. NOTICE: BL31: Rockchip release version: v1.1
  365. INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
  366. INFO: Using opteed sec cpu_context!
  367. INFO: boot cpu mask: 0
  368. INFO: plat_rockchip_pmu_init(1181): pd status 3e
  369. INFO: BL31: Initializing runtime services
  370. INFO: BL31: Initializing BL32
  371. INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-195-g8f090d20 #6 Fri Dec 7 06:11:20 UTC 2018 aarch64)
  372. INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.2
  373. INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
  374. INFO: BL31: Preparing for EL3 exit to normal world
  375. INFO: Entry point address = 0x200000
  376. INFO: SPSR = 0x3c9
  377. U-Boot 2019.04-rc4-00136-gfd121f9641-dirty (Apr 16 2019 - 14:02:47 +0530)
  378. Model: FriendlyARM NanoPi NEO4
  379. DRAM: 1022 MiB
  380. MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
  381. Loading Environment from MMC... *** Warning - bad CRC, using default environment
  382. In: serial@ff1a0000
  383. Out: serial@ff1a0000
  384. Err: serial@ff1a0000
  385. Model: FriendlyARM NanoPi NEO4
  386. Net: eth0: ethernet@fe300000
  387. Hit any key to stop autoboot: 0
  388. =>
  389. Option 2: Package the image with SPL:
  390. - Prefix rk3399 header to SPL image
  391. => cd /path/to/u-boot
  392. => ./tools/mkimage -n rk3399 -T rksd -d spl/u-boot-spl-dtb.bin out
  393. - Write prefixed SPL at 64th sector
  394. => sudo dd if=out of=/dev/sdc seek=64
  395. - Write U-Boot proper at 16384 sector
  396. => sudo dd if=u-boot.itb of=/dev/sdc seek=16384
  397. => sync
  398. Put this SD (or micro-SD) card into your board and reset it. You should see
  399. something like:
  400. U-Boot SPL board init
  401. Trying to boot from MMC1
  402. U-Boot 2019.01-00004-g14db5ee998 (Mar 11 2019 - 13:18:41 +0530)
  403. Model: Orange Pi RK3399 Board
  404. DRAM: 2 GiB
  405. MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
  406. Loading Environment from MMC... OK
  407. In: serial@ff1a0000
  408. Out: serial@ff1a0000
  409. Err: serial@ff1a0000
  410. Model: Orange Pi RK3399 Board
  411. Net: eth0: ethernet@fe300000
  412. Hit any key to stop autoboot: 0
  413. =>
  414. Option 3: Package the image with TPL:
  415. - Write tpl+spl at 64th sector
  416. => sudo dd if=idbloader.img of=/dev/sdc seek=64
  417. - Write U-Boot proper at 16384 sector
  418. => sudo dd if=u-boot.itb of=/dev/sdc seek=16384
  419. => sync
  420. Put this SD (or micro-SD) card into your board and reset it. You should see
  421. something like:
  422. U-Boot TPL board init
  423. Trying to boot from BOOTROM
  424. Returning to boot ROM...
  425. U-Boot SPL board init
  426. Trying to boot from MMC1
  427. U-Boot 2019.07-rc1-00241-g5b3244767a (May 08 2019 - 10:51:06 +0530)
  428. Model: Orange Pi RK3399 Board
  429. DRAM: 2 GiB
  430. MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0
  431. Loading Environment from MMC... OK
  432. In: serial@ff1a0000
  433. Out: serial@ff1a0000
  434. Err: serial@ff1a0000
  435. Model: Orange Pi RK3399 Board
  436. Net: eth0: ethernet@fe300000
  437. Hit any key to stop autoboot: 0
  438. =>
  439. Using fastboot on rk3288
  440. ========================
  441. - Write GPT partition layout to mmc device which fastboot want to use it to
  442. store the image
  443. => gpt write mmc 1 $partitions
  444. - Invoke fastboot command to prepare
  445. => fastboot 1
  446. - Start fastboot request on PC
  447. fastboot -i 0x2207 flash loader evb-rk3288/spl/u-boot-spl-dtb.bin
  448. You should see something like:
  449. => fastboot 1
  450. WARNING: unknown variable: partition-type:loader
  451. Starting download of 357796 bytes
  452. ..
  453. downloading of 357796 bytes finished
  454. Flashing Raw Image
  455. ........ wrote 357888 bytes to 'loader'
  456. Booting from SPI
  457. ================
  458. To write an image that boots from SPI flash (e.g. for the Haier Chromebook or
  459. Bob):
  460. ./chromebook_jerry/tools/mkimage -n rk3288 -T rkspi \
  461. -d chromebook_jerry/spl/u-boot-spl-dtb.bin spl.bin && \
  462. dd if=spl.bin of=spl-out.bin bs=128K conv=sync && \
  463. cat spl-out.bin chromebook_jerry/u-boot-dtb.img >out.bin && \
  464. dd if=out.bin of=out.bin.pad bs=4M conv=sync
  465. This converts the SPL image to the required SPI format by adding the Rockchip
  466. header and skipping every second 2KB block. Then the U-Boot image is written at
  467. offset 128KB and the whole image is padded to 4MB which is the SPI flash size.
  468. The position of U-Boot is controlled with this setting in U-Boot:
  469. #define CONFIG_SYS_SPI_U_BOOT_OFFS 0x20000
  470. If you have a Dediprog em100pro connected then you can write the image with:
  471. sudo em100 -s -c GD25LQ32 -d out.bin.pad -r
  472. When booting you should see something like:
  473. U-Boot SPL 2015.07-rc2-00215-g9a58220-dirty (Jun 23 2015 - 12:11:32)
  474. U-Boot 2015.07-rc2-00215-g9a58220-dirty (Jun 23 2015 - 12:11:32 -0600)
  475. Model: Google Jerry
  476. DRAM: 2 GiB
  477. MMC:
  478. Using default environment
  479. In: serial@ff690000
  480. Out: serial@ff690000
  481. Err: serial@ff690000
  482. =>
  483. Future work
  484. ===========
  485. Immediate priorities are:
  486. - USB host
  487. - USB device
  488. - Run CPU at full speed (code exists but we only see ~60 DMIPS maximum)
  489. - NAND flash
  490. - Boot U-Boot proper over USB OTG (at present only SPL works)
  491. Development Notes
  492. =================
  493. There are plenty of patches in the links below to help with this work.
  494. [1] https://github.com/rkchrome/uboot.git
  495. [2] https://github.com/linux-rockchip/u-boot-rockchip.git branch u-boot-rk3288
  496. [3] https://github.com/linux-rockchip/rkflashtool.git
  497. [4] http://wiki.t-firefly.com/index.php/Firefly-RK3288/Serial_debug/en
  498. rkimage
  499. -------
  500. rkimage.c produces an SPL image suitable for sending directly to the boot ROM
  501. over USB OTG. This is a very simple format - just the string RK32 (as 4 bytes)
  502. followed by u-boot-spl-dtb.bin.
  503. The boot ROM loads image to 0xff704000 which is in the internal SRAM. The SRAM
  504. starts at 0xff700000 and extends to 0xff718000 where we put the stack.
  505. rksd
  506. ----
  507. rksd.c produces an image consisting of 32KB of empty space, a header and
  508. u-boot-spl-dtb.bin. The header is defined by 'struct header0_info' although
  509. most of the fields are unused by U-Boot. We just need to specify the
  510. signature, a flag and the block offset and size of the SPL image.
  511. The header occupies a single block but we pad it out to 4 blocks. The header
  512. is encoding using RC4 with the key 7c4e0304550509072d2c7b38170d1711. The SPL
  513. image can be encoded too but we don't do that.
  514. The maximum size of u-boot-spl-dtb.bin which the boot ROM will read is 32KB,
  515. or 0x40 blocks. This is a severe and annoying limitation. There may be a way
  516. around this limitation, since there is plenty of SRAM, but at present the
  517. board refuses to boot if this limit is exceeded.
  518. The image produced is padded up to a block boundary (512 bytes). It should be
  519. written to the start of an SD card using dd.
  520. Since this image is set to load U-Boot from the SD card at block offset,
  521. CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR, dd should be used to write
  522. u-boot-dtb.img to the SD card at that offset. See above for instructions.
  523. rkspi
  524. -----
  525. rkspi.c produces an image consisting of a header and u-boot-spl-dtb.bin. The
  526. resulting image is then spread out so that only the first 2KB of each 4KB
  527. sector is used. The header is the same as with rksd and the maximum size is
  528. also 32KB (before spreading). The image should be written to the start of
  529. SPI flash.
  530. See above for instructions on how to write a SPI image.
  531. rkmux.py
  532. --------
  533. You can use this script to create #defines for SoC register access. See the
  534. script for usage.
  535. Device tree and driver model
  536. ----------------------------
  537. Where possible driver model is used to provide a structure to the
  538. functionality. Device tree is used for configuration. However these have an
  539. overhead and in SPL with a 32KB size limit some shortcuts have been taken.
  540. In general all Rockchip drivers should use these features, with SPL-specific
  541. modifications where required.
  542. GPT partition layout
  543. ----------------------------
  544. Rockchip use a unified GPT partition layout in open source support.
  545. With this GPT partition layout, uboot can be compatilbe with other components,
  546. like miniloader, trusted-os, arm-trust-firmware.
  547. There are some documents about partitions in the links below.
  548. http://rockchip.wikidot.com/partitions
  549. --
  550. Jagan Teki <jagan@amarulasolutions.com>
  551. 27 Mar 2019
  552. Simon Glass <sjg@chromium.org>
  553. 24 June 2015