blob: 50ef401b7c95f5d1af51f25d09e4b0e8cbe1b3c2 [file] [log] [blame]
Tom Rini95a372b2012-08-20 09:31:52 -07001Summary
2=======
3The README is for the boot procedure used for various DA850 (or compatible
4parts such as the AM1808) based boards.
5
6In the context of U-Boot, the board is booted in three stages. The initial
7bootloader which executes upon reset is the ROM Boot Loader (RBL) and sits
8in the internal ROM. The RBL initializes the internal memory and then
9depending on the exact board and pin configurations will initialize another
10controller (such as SPI or NAND) to continue the boot process by loading
11the secondary program loader (SPL). The SPL will initialize the system
12further (some clocks, SDRAM) and then load the full u-boot from a
13predefined location in persistent storage to DDR and jumps to the u-boot
14entry point.
15
16AIS is an image format defined by TI for the images that are to be loaded
17to memory by the RBL. The image is divided into a series of sections and
18the image's entry point is specified. Each section comes with meta data
19like the target address the section is to be copied to and the size of the
20section, which is used by the RBL to load the image. At the end of the
21image the RBL jumps to the image entry point. The AIS format allows for
22other things such as programming the clocks and SDRAM if the header is
23programmed for it. We do not take advantage of this and instead use SPL as
24it allows for additional flexibility (run-time detect of board revision,
25loading the next image from a different media, etc).
26
27
28Compilation
29===========
30The exact build target you need will depend on the board you have. For
31Logic PD boards, or other boards which store the ethernet MAC address at
Adam Ford8dd75d32019-07-29 08:28:39 -050032the end of SPI flash, run 'make da850evm'. Once this build completes you will have a
Tom Rini95a372b2012-08-20 09:31:52 -070033u-boot.ais file that needs to be written to the correct persistent
34storage.
35
36
37Flashing the images to SPI
38==========================
39The AIS image can be written to SPI flash using the following commands.
40Assuming that the network is configured and enabled and the u-boot.ais file
41is tftp'able.
42
43U-Boot > sf probe 0
44U-Boot > sf erase 0 +320000
45U-Boot > tftp u-boot.ais
46U-Boot > sf write c0700000 0 $filesize
47
ahaslam@baylibre.comdaa483d2017-03-17 16:55:23 +010048Flashing the images to NAND
49===========================
50The AIS image can be written to NAND using the u-boot "nand" commands.
51
52Example:
53
54OMAPL138_LCDK requires the AIS image to be written to the second block of
55the NAND flash.
56
57From the "nand info" command we see that the second block would start at
58offset 0x20000:
59
60 U-Boot > nand info
61 sector size 128 KiB (0x20000)
62 Page size 2048 b
63
64From the tftp command we see that we need to copy 0x74908 bytes from
65memory address 0xc0700000 (0x75000 if we align a page of 2048):
66
67 U-Boot > tftp u-boot.ais
68 Load address: 0xc0700000
69 Bytes transferred = 477448 (74908 hex)
70
71The commands to write the image from memory to NAND would be:
72
73 U-Boot > nand erase 0x20000 0x75000
74 U-Boot > nand write 0xc0700000 0x20000 0x75000
75
76Alternatively, MTD partitions may be defined. Using "mtdparts" to
77conveniently have a bootloader partition starting at the second block
78(offset 0x20000):
79
80 setenv mtdids nand0=davinci_nand.0
81 setenv mtdparts mtdparts=davinci_nand.0:128k(bootenv),2m(bootloader)
82
83In this case the commands would be simplified to:
84
85 U-Boot > tftp u-boot.ais
86 U-Boot > nand erase.part bootloader
87 U-Boot > nand write 0xc0700000 bootloader
88
Adam Ford57ade072019-02-14 20:13:53 -060089On the DA850-EVM, NAND can also be written with SW7:7-8 ON and
90
91 sudo mono sfh_OMAP-L138.exe -targetType AM1808 -p /dev/ttyUSB0 \
92 -flash_noubl -flashType NAND ~/src/u-boot/u-boot.ais
93
94To boot the DA850-EVM from NAND, SW7:5 should be switched on and all others
95off.
96
ahaslam@baylibre.com4aac44b2017-02-13 18:49:40 +010097Flashing the images to MMC
98==========================
99If the boot pins are set to boot from mmc, the RBL will try to load the
100next boot stage form the first couple of sectors of an external mmc card.
101As sector 0 is usually used for storing the partition information, the
102AIS image should be written at least after the first sector, but before the
103first partition begins. (e.g: make sure to leave at least 500KB of unallocated
104space at the start of the mmc when creating the partitions)
105
106CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR is used by SPL, and should
107point to the sector were the u-boot image is located. (eg. After SPL)
108
109There are 2 ways to copy the AIS image to the mmc card:
110
111 1 - Using the TI tool "uflash"
112 $ uflash -d /dev/mmcblk0 -b ./u-boot.ais -p OMAPL138 -vv
113
114 2 - using the "dd" command
115 $ dd if=u-boot.ais of=/dev/mmcblk0 seek=117 bs=512 conv=fsync
116
117uflash writes the AIS image at offset 117. For compatibility with uflash,
118CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR is set to take into account this
119offset, and the dd command is adjusted accordingly.
Tom Rini95a372b2012-08-20 09:31:52 -0700120
Adam Ford09d84112018-08-11 07:34:55 -0500121Flashing the images to NOR
122==========================
123NOR Flash is XIP (execute-in-place), so no AIS (or SPL) is needed. The
124u-boot.bin is directy flashed, but CONFIT_DA850_LOWLEVEL must be set
125to initialize hardware that's normally done by SPL.
126
Simon Glass98463902022-10-20 18:22:39 -0600127For this case, CONFIG_TEXT_BASE=0x60000000 which is the address to
Adam Ford09d84112018-08-11 07:34:55 -0500128which the bootloader jumps when powered on.
129
130Example:
131For the da850evm, there is a defconfig setup to use the NOR flash on
132the UI expander board called da850evm_direct_nor_defconfig.
133
134Flash to NOR directly using
135sudo mono ./sfh_OMAP-L138.exe -p /dev/ttyUSB0 -flash_noubl
136 -flashType NOR u-boot.bin
137
138SW7:5 through SW7:7 should be switched on and all others off.
139
Tom Rini95a372b2012-08-20 09:31:52 -0700140Recovery
141========
142
143In the case of a "bricked" board, you need to use the TI tools found
144here[1] to write the u-boot.ais file. An example of recovering to the SPI
145flash of an AM1808 would be:
146
147$ mono sfh_OMAP-L138.exe -targetType AM1808 -p /dev/ttyUSB0 \
148 -flash_noubl /path/to/u-boot.ais
149
150For other target types and flash locations:
151
152$ mono sfh_OMAP-L138.exe -h
153
154Links
155=====
156[1]
157 http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138