Adam Ford | 55bdf92 | 2017-04-17 08:09:45 -0500 | [diff] [blame] | 1 | Summary |
| 2 | ======= |
| 3 | |
Adam Ford | 81b19d7 | 2018-09-29 14:10:19 -0500 | [diff] [blame] | 4 | The 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. |
Adam Ford | 55bdf92 | 2017-04-17 08:09:45 -0500 | [diff] [blame] | 5 | |
Adam Ford | 81b19d7 | 2018-09-29 14:10:19 -0500 | [diff] [blame] | 6 | omap3_logic_defconfig = DM37 Torpedo / Torpedo + Wireless |
| 7 | omap35_logic_defconfig = OMAP35 Torpedo |
| 8 | omap3_logic_somlv_defconfig = DM37 SOM-LV |
| 9 | omap35_logic_somlv_defconfig = OMAP35 SOM-LV |
Adam Ford | 55bdf92 | 2017-04-17 08:09:45 -0500 | [diff] [blame] | 10 | |
Adam Ford | 81b19d7 | 2018-09-29 14:10:19 -0500 | [diff] [blame] | 11 | The 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 | recomended to mix and match the defconfig files. |
Adam Ford | 55bdf92 | 2017-04-17 08:09:45 -0500 | [diff] [blame] | 13 | |
Adam Ford | 9968e4a | 2017-12-04 17:54:50 -0600 | [diff] [blame] | 14 | Falcon Mode: FAT SD cards |
| 15 | ========================= |
| 16 | |
| 17 | In this case the additional file is written to the filesystem. In this |
| 18 | example we assume that the uImage and device tree to be used are already on |
| 19 | the FAT filesystem (only the uImage MUST be for this to function |
| 20 | afterwards) along with a Falcon Mode aware MLO and the FAT partition has |
| 21 | already been created and marked bootable: |
| 22 | |
| 23 | U-Boot # mmc rescan |
| 24 | # Load kernel and device tree into memory, perform export |
| 25 | U-Boot # fatload mmc 0 ${loadaddr} uImage |
| 26 | U-Boot # run loadfdt |
| 27 | U-Boot # setenv optargs quiet |
| 28 | U-Boot # run mmcargs |
| 29 | U-Boot # run common_bootargs |
| 30 | U-Boot # spl export fdt ${loadaddr} - ${fdtaddr} |
| 31 | |
| 32 | This will print a number of lines and then end with something like: |
| 33 | Loading Device Tree to 8dec9000, end 8dee0295 ... OK |
| 34 | |
| 35 | So then note the starting address and write the args to mmc/sd: |
| 36 | |
| 37 | U-Boot # fatwrite mmc 0:1 0x8dec9000 args 0x20000 |
| 38 | |
| 39 | The size of 0x20000 matches the CMD_SPL_WRITE_SIZE. |
| 40 | |
| 41 | Falcon Mode: NAND |
| 42 | ================= |
| 43 | |
| 44 | In this case the additional data is written to another partition of the |
| 45 | NAND. In this example we assume that the uImage and device tree to be are |
| 46 | already located on the NAND somewhere (such as filesystem or mtd partition) |
| 47 | along with a Falcon Mode aware MLO written to the correct locations for |
| 48 | booting and mtdparts have been configured correctly for the board: |
| 49 | |
| 50 | U-Boot # nand read ${loadaddr} kernel |
| 51 | U-Boot # load nand rootfs ${fdtaddr} /boot/am335x-evm.dtb |
| 52 | U-Boot # run nandargs |
| 53 | U-Boot # run common_bootargs |
| 54 | U-Boot # spl export fdt ${loadaddr} - ${fdtaddr} |
| 55 | U-Boot # nand erase.part u-boot-spl-os |
| 56 | U-Boot # nand write ${fdtaddr} u-boot-spl-os |