Boot from eMMC means all the firmware(including stage 2, 3, 4, 5) in eMMC.Boot from SPI flash means firmware for stage 2 and 3(SPL and U-Boot only) in SPI flash and stage 4/5 in other place.Stage 1 is always in boot rom, it loads stage 2 and may load stage 3(when SPL_BACK_TO_BROM option enabled).Then when we talking about boot from eMMC/SD/U-Disk/net, they are in different concept: | | | ATF/TEE | trust.img | 0圆000 | only used with miniloader | | | | uboot.img | | only used with miniloader | 3 | - | U-Boot | b | 0x4000 | including u-boot and atf | 2 | Secondary | U-Boot |idbloader.img| 0x40 | pre-loader | Boot | Terminology #1 | Actual | Rockchip | Image | use Rockchp idbLoader which is combinded by Rockchip ddr init bin and miniloader bin from Rockchip rkbin project
U BOOT SPL CODE
use U-Boot TPL/SPL from upsream or rockchip U-Boot, fully source code This chapter introduce the generic boot flow for Rockchip Application Processors, including the detail about what image we may use in Rockchip platform for kind of boot path: Here is Rockchip pre-released binaries which may be mentioned later:
U BOOT SPL HOW TO
Then we need to know about how the image should packaged, where the image locate Īt last, we will explain how to write to different media and boot from there.
copy the related u-boot ans SPL files on nfs /home/root (for example).uses a rfs with kobs-ng utility available on it (e.g.The following steps are therefore necessary: For this reason, the mtdparts variable has to be modified for writing the complete u-boot image. for programming the second stage, the nandwrite command has to identify a proper mtd part witch correct size. This tool is required for writing correct information needed by bootrom to identify the NAND as a boot device.
The SPL and u-boot image, must be flashed on NAND using the NXP kobs-ng utility. Hit ENTER within 1 seconds to stop autobootĪs you can see, respect to the NOR SPI, the u-boot binaries for the SD card uses the environment on SD (labelled MMC on u-boot code): WARNING: CB ConfigID on block 0 is UNLOCKEDĭisplay: LDB-AM-800480STMQW-TA1-SBCX-REVB (800x480)īad partition index:2 for partition:recoveryīad partition index:5 for partition:system Relocating to 8ff30000, new gd at 8df2feb8, sp at 8df2fe90 Insert the DIP header on the pin selecting the BOOT_MODE_SEL from SD card and reset the board: MMC write: dev # 0, block # 138, count 981. 119 blocks written: OKįilename 'axel/xelk-3.5.0_m圆qdlaxel_u-boot.img'. MMC write: dev # 0, block # 2, count 119. from the running tftp server on the XELK 3 VM): load and program the SPL binaries (i.e.
U BOOT SPL UPDATE
NOR SPI and SD).Īnd the related update commands are (for example for the SD card storage device): In order to program the uboot SPL binaries ( SPL and u-boot.img) some new environment variables are useful for loading the binaries from a tftp server and store them on the storage boot device (i.e. Here below, you can find a step-by-step user's guide for updating u-boot to the new SPL version. It is then required to update the u-boot on AXEL LITE SoM using some new u-boot environment variables: those vars will be present and ready to be used on the new SPL default environment. Starting from XELK 3.5.0 binary version, u-boot supports the SPL first-stage bootloader and second-stage bootloader (the proper u-boot complete binary).
0 kommentar(er)
