Lines Matching refs:to
10 controller (such as SPI or NAND) to continue the boot process by loading
13 predefined location in persistent storage to DDR and jumps to the u-boot
16 AIS is an image format defined by TI for the images that are to be loaded
17 to memory by the RBL. The image is divided into a series of sections and
19 like the target address the section is to be copied to and the size of the
20 section, which is used by the RBL to load the image. At the end of the
21 image the RBL jumps to the image entry point. The AIS format allows for
33 u-boot.ais file that needs to be written to the correct persistent
37 Flashing the images to SPI
39 The AIS image can be written to SPI flash using the following commands.
48 Flashing the images to NAND
50 The AIS image can be written to NAND using the u-boot "nand" commands.
54 OMAPL138_LCDK requires the AIS image to be written to the second block of
64 From the tftp command we see that we need to copy 0x74908 bytes from
71 The commands to write the image from memory to NAND would be:
76 Alternatively, MTD partitions may be defined. Using "mtdparts" to
83 In this case the commands would be simplified to:
97 Flashing the images to MMC
99 If the boot pins are set to boot from mmc, the RBL will try to load the
103 first partition begins. (e.g: make sure to leave at least 500KB of unallocated
107 point to the sector were the u-boot image is located. (eg. After SPL)
109 There are 2 ways to copy the AIS image to the mmc card:
118 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR is set to take into account this
121 Flashing the images to NOR
125 to initialize hardware that's normally done by SPL.
127 For this case, CONFIG_SYS_TEXT_BASE=0x60000000 which is the address to
131 For the da850evm, there is a defconfig setup to use the NOR flash on
134 Flash to NOR directly using
143 In the case of a "bricked" board, you need to use the TI tools found
144 here[1] to write the u-boot.ais file. An example of recovering to the SPI
148 -flash_noubl /path/to/u-boot.ais