Binary Demo Image for Logic PD Linux BSP ReadMe ------------------------------------------------------------------------------- Logic PD BSP Version: 2.4-4 Hardware: DM3730/AM3703 SOM-LV, DM3730/AM3703 Torpedo SOM, DM3730/AM3703 Torpedo + Wireless SOM Date: 9/1/2015 ------------------------------------------------------------------------------- --------------------------- Table of Contents --------------------------- 0 Scope of Document 1 Overview 2 Files 3 Format SD Card 4 Configurations --------------------------- 0) Scope of Document -------------------- The information contained within these release notes may pertain only to this version of the Linux BSP. Please refer to Logic PD's website for more information. For installation instructions, please refer to the "DM37x Linux BSP User Guide" available at: http://support.logicpd.com/downloads/1431/ 1) Overview ----------- The files in this package are pre-built binary images for demonstration purposes. As Linux has an infinite number of configurations, the configurations represented here are only those that demonstrate a typical configuration a customer might use. 2) Files -------- Below is a list of files included in this package: --) MLO This file is X-Loader, the first-stage bootloader. The CPU boot ROM requires that the file is named "MLO" in order to load upon power up or after CPU reset. The purpose of X-Loader is to load the second-stage bootloader. X-Loader can be placed on an SD card or in NAND flash. --) u-boot.bin This file is U-Boot, the second-stage bootloader. U-Boot supports a shell, scripting and basic debug. U-Boot itself can be placed on an SD card or in NAND flash. --) u-boot.bin.ift This file is the same "u-boot.bin" file above; however, it includes a header that X-Loader uses to identify the size of the file. This is used for NAND flash when there is not a file system X-Loader can query to identify the size of the U-Boot image. --) rootfs.ext2.gz.uboot This is a RAM-based Linux root filesystem. The Linux OS requires some sort of root filesystem. This root filesystem is based in RAM and is loaded by U-Boot at boot time. Any changes to a RAM-based root filesystem will be lost between power cycles. --) rootfs.yaffs2 This is a NAND-based root filesystem with new-bluez. This image is sspecifically formatted to be loaded on to the NAND flash device. Using a NAND-based root filesystem allows the entire RAM to be used for the Linux kernel. Any changes to the NAND-based root filesystem are persistent across power cycles. --) uImage This is a typical Linux kernel. The Linux kernel is loaded by U-Boot with the root filesystem at boot time. --) mkLogicFATcard.sh This is a Linux script to format and write a bootable partition on an SD card. Located 3) Format SD Card ----------------- The boot ROM within the Texas Instruments (TI processor requires a specific boot partition for a bootable SD card. The SD card can be created using the following steps: 1) Create a bootable SD card by running the script "mkLogicFATcard.sh" from your Linux desktop. When running the script, specify the SD card device. For example: $ mkLogicFATcard.sh /dev/sd? where "/dev/sd?" is replaced with your SD card reader device. Be sure you indicate the correct device, as the script will erase all data on that device. 2) It is good practice to remove the SD card, wait at least five seconds, then reinsert the SD card. This will ensure the SD card is formatted and remounted properly. 3) Unzip the 102xxxxx_LogicPD_Linux_BSP_x.x-x_SD_Card_Demo_Image.zip using a desktop PC. 4) Copy only the "MLO" file to the SD card. Some customers have reported that the CPU fails to recognize the "MLO" boot file if not copied first. 5) Copy all remaining files to the SD card. 4) Configurations ----------------- All the files can be placed on an SD card, and the SOM will boot the SD card boot image. To select a configuration, U-Boot is used to configure and set up the different boot configurations. The files listed above provide four different bootable configurations. Below is a list of those configurations and the files required for each. Every configuration requires some form of X-Loader, U-Boot, a root filesystem, and the Linux kernel. --) A typical SD card boot image with RAM-based root filesystem. Required Files: * MLO * u-boot.bin * rootfs.ext2.gz.uboot * uImage 1) Ensure the files above are on the SD card. 2) Insert the SD card into the kit. 3) Power on the kit. --) A typical NAND boot image with RAM-based root filesystem. Required Files: * MLO * u-boot.bin * u-boot.bin.ift * rootfs.ext2.gz.uboot * uImage 1) Ensure the files above are on the SD card. 2) Insert the SD card into the kit. 3) Power on the kit. 4) Press a key on the terminal to interrupt the auto-boot process. 5) At the prompt, enter "run makenandboot". 6) Once complete, remove the SD card. 7) Cycle the power on the kit. --) A typical NAND boot image with NAND-based root filesystem. Required Files: * MLO * u-boot.bin * u-boot.bin.ift * rootfs.yaffs2 * uImage 1) Ensure the files above are on the SD card. 2) Insert the SD card into the kit. 3) Power on the kit. 4) Press a key on the terminal to interrupt the auto-boot process. 5) At the prompt, enter "run makeyaffsboot". 6) Once complete, remove the SD card. 7) Cycle the power on the kit. NOTE: The above instructions assume there is no prior U-Boot environment saved in NAND flash. If U-Boot has a prior U-Boot environment stored in NAND flash, use the U-Boot command "env default -f" to revert to the default environment prior to running the steps above. See the "DM37x Linux BSP User Guide" for more information (see Section 0 of this document for a link). ----------------------------------------------------------------------------- Copyright (c) 2015 Logic PD, Inc. www.logicpd.com