README.rockchip 21 KB

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