115fde737SAdam FordSummary 215fde737SAdam Ford======= 315fde737SAdam Ford 4*46580f2fSAdam FordThe source for omap3logic.c encompases the OMAP35 and DM3730 SOM-LV and DM3730 Torpedo platforms, but there are device trees custom taylored to each board. 515fde737SAdam Ford 6*46580f2fSAdam Fordomap3_logic_defconfig = DM37 Torpedo / Torpedo + Wireless 7*46580f2fSAdam Fordomap35_logic_defconfig = OMAP35 Torpedo 8*46580f2fSAdam Fordomap3_logic_somlv_defconfig = DM37 SOM-LV 9*46580f2fSAdam Fordomap35_logic_somlv_defconfig = OMAP35 SOM-LV 1015fde737SAdam Ford 11*46580f2fSAdam FordThe device tree included with each of the defconfig files will also direct the board as to which dtb file to load when loading the kernel, so it is not 12*46580f2fSAdam Fordrecomended to mix and match the defconfig files. 1315fde737SAdam Ford 146032c029SAdam FordFalcon Mode: FAT SD cards 156032c029SAdam Ford========================= 166032c029SAdam Ford 176032c029SAdam FordIn this case the additional file is written to the filesystem. In this 186032c029SAdam Fordexample we assume that the uImage and device tree to be used are already on 196032c029SAdam Fordthe FAT filesystem (only the uImage MUST be for this to function 206032c029SAdam Fordafterwards) along with a Falcon Mode aware MLO and the FAT partition has 216032c029SAdam Fordalready been created and marked bootable: 226032c029SAdam Ford 236032c029SAdam FordU-Boot # mmc rescan 246032c029SAdam Ford# Load kernel and device tree into memory, perform export 256032c029SAdam FordU-Boot # fatload mmc 0 ${loadaddr} uImage 266032c029SAdam FordU-Boot # run loadfdt 276032c029SAdam FordU-Boot # setenv optargs quiet 286032c029SAdam FordU-Boot # run mmcargs 296032c029SAdam FordU-Boot # run common_bootargs 306032c029SAdam FordU-Boot # spl export fdt ${loadaddr} - ${fdtaddr} 316032c029SAdam Ford 326032c029SAdam FordThis will print a number of lines and then end with something like: 336032c029SAdam Ford Loading Device Tree to 8dec9000, end 8dee0295 ... OK 346032c029SAdam Ford 356032c029SAdam FordSo then note the starting address and write the args to mmc/sd: 366032c029SAdam Ford 376032c029SAdam FordU-Boot # fatwrite mmc 0:1 0x8dec9000 args 0x20000 386032c029SAdam Ford 396032c029SAdam FordThe size of 0x20000 matches the CMD_SPL_WRITE_SIZE. 406032c029SAdam Ford 416032c029SAdam FordFalcon Mode: NAND 426032c029SAdam Ford================= 436032c029SAdam Ford 446032c029SAdam FordIn this case the additional data is written to another partition of the 456032c029SAdam FordNAND. In this example we assume that the uImage and device tree to be are 466032c029SAdam Fordalready located on the NAND somewhere (such as filesystem or mtd partition) 476032c029SAdam Fordalong with a Falcon Mode aware MLO written to the correct locations for 486032c029SAdam Fordbooting and mtdparts have been configured correctly for the board: 496032c029SAdam Ford 506032c029SAdam FordU-Boot # nand read ${loadaddr} kernel 516032c029SAdam FordU-Boot # load nand rootfs ${fdtaddr} /boot/am335x-evm.dtb 526032c029SAdam FordU-Boot # run nandargs 536032c029SAdam FordU-Boot # run common_bootargs 546032c029SAdam FordU-Boot # spl export fdt ${loadaddr} - ${fdtaddr} 556032c029SAdam FordU-Boot # nand erase.part u-boot-spl-os 566032c029SAdam FordU-Boot # nand write ${fdtaddr} u-boot-spl-os 57