Adam Ford | 55bdf92 | 2017-04-17 08:09:45 -0500 | [diff] [blame] | 1 | Summary |
| 2 | ======= |
| 3 | |
| 4 | The source for omap3som encompases the DM3730 SOM-LV and DM3730 Torpedo platforms. |
| 5 | |
| 6 | By default, the Torpedo Device Tree is integrated into U-Boot,but the MMC controller, GPIO and I2C controllers are the same, so for the purposes of loading U-Boot, it should be sufficient. However this will display the Model as "LogicPD Zoom DM3730 Torpedo + Wireless Development Kit" upon boot. |
| 7 | |
| 8 | The actual board remains autodetected and the Board will read "DM37xx SOM LV" when used on the DM37 SOM-LV. The device tree loaded with Linux is also correct. |
| 9 | |
| 10 | Integrating the SOM-LV Device Tree into U-Boot |
| 11 | ============================================== |
| 12 | |
| 13 | This step is optional, but should you want to change the default to the SOM-LV, locate the configs/omap3_logic_defconfig file and make the following change. |
| 14 | |
| 15 | CONFIG_DEFAULT_DEVICE_TREE="logicpd-som-lv-37xx-devkit" |
| 16 | |
| 17 | make distclean |
| 18 | make omap3_logic_defconfig |
| 19 | |
Adam Ford | 9968e4a | 2017-12-04 17:54:50 -0600 | [diff] [blame] | 20 | Falcon Mode: FAT SD cards |
| 21 | ========================= |
| 22 | |
| 23 | In this case the additional file is written to the filesystem. In this |
| 24 | example we assume that the uImage and device tree to be used are already on |
| 25 | the FAT filesystem (only the uImage MUST be for this to function |
| 26 | afterwards) along with a Falcon Mode aware MLO and the FAT partition has |
| 27 | already been created and marked bootable: |
| 28 | |
| 29 | U-Boot # mmc rescan |
| 30 | # Load kernel and device tree into memory, perform export |
| 31 | U-Boot # fatload mmc 0 ${loadaddr} uImage |
| 32 | U-Boot # run loadfdt |
| 33 | U-Boot # setenv optargs quiet |
| 34 | U-Boot # run mmcargs |
| 35 | U-Boot # run common_bootargs |
| 36 | U-Boot # spl export fdt ${loadaddr} - ${fdtaddr} |
| 37 | |
| 38 | This will print a number of lines and then end with something like: |
| 39 | Loading Device Tree to 8dec9000, end 8dee0295 ... OK |
| 40 | |
| 41 | So then note the starting address and write the args to mmc/sd: |
| 42 | |
| 43 | U-Boot # fatwrite mmc 0:1 0x8dec9000 args 0x20000 |
| 44 | |
| 45 | The size of 0x20000 matches the CMD_SPL_WRITE_SIZE. |
| 46 | |
| 47 | Falcon Mode: NAND |
| 48 | ================= |
| 49 | |
| 50 | In this case the additional data is written to another partition of the |
| 51 | NAND. In this example we assume that the uImage and device tree to be are |
| 52 | already located on the NAND somewhere (such as filesystem or mtd partition) |
| 53 | along with a Falcon Mode aware MLO written to the correct locations for |
| 54 | booting and mtdparts have been configured correctly for the board: |
| 55 | |
| 56 | U-Boot # nand read ${loadaddr} kernel |
| 57 | U-Boot # load nand rootfs ${fdtaddr} /boot/am335x-evm.dtb |
| 58 | U-Boot # run nandargs |
| 59 | U-Boot # run common_bootargs |
| 60 | U-Boot # spl export fdt ${loadaddr} - ${fdtaddr} |
| 61 | U-Boot # nand erase.part u-boot-spl-os |
| 62 | U-Boot # nand write ${fdtaddr} u-boot-spl-os |