Getting Started Guide for the OMAP35x
- 1 Installation Guide
- 2 What's Tested and Supported
- 3 What's Tested and not Supported
- 4 What's not Tested
Setting up serial access to the Linux console
You use the serial port to control u-boot and Linux. The picocom terminal emulator work well for this purpose.
Partitioning an SD card
You can store the file system on an SD card. To do this, you need to have the right partitions setup on the SD card. These steps will create two partitions, the second one is used to hold the target file system.
Setting up a TFTP server
If you are using the SDK, you can speed downloads to the target hardware by using TFTP. You host PC needs to be configured as a TFTP server for this to work.
Setting up an NFS server
For application development, it is convenient to use root NFS mount file system for the target hardware. This allows you to rebuild your application on the host and immediately run the application on the target hardware with no interveining steps. You host PC needs to be configured as a NFS server for this to work.
Checking out the binary images
If you simply want to run the pre-built versions of the Linux kernel using the pre-built file system, then start by downloading the pre-built images from 're not able to use the SDK you could download the pre-built images.
Saving pre-built kernel and file system on target hardware
In order to boot the OMAP35x from an SD you must follow the following steps:
1. First, format an SD Card with 2 partitions; in the first one use a FAT32 format with 32Mb of size and with the boot flag enabled, the second one partition with the rest of the SD Card, called rootfs, must have an EXT3 format as is described in Creating a bootable SDcard
2. Copy the u-boot image, x-loader image (must be called MLO into the SD) and the kernel image located in <PathofYourSDK>/images into the partion named boot:
<PathofYourSDK>/images$ cp bootloader /media/boot/u-boot.bin <PathofYourSDK>/images$ cp x-load.bin.ift /media/boot/MLO <PathofYourSDK>/images$ cp kernel.uImage /media/boot/uImage
3. Uncompress with sudo privileges the file system into the partition named rootfs.
sudo tar -C /media/rootfs -xjf OMAP35x-fs.tar.bz2
4. Ensure SW4 is set as is described in Section Main Board SW4
5. Once the above steps have been completed, turn on the OMAP35x and press enter to get a U-boot prompt and set the bootargs as follows:
OMAP3_EVM # setenv bootargs 'console=ttyS0,115200n8 rootdelay=2 root=/dev/mmcblk0p2 mem=102M' OMAP3_EVM # saveenv
What's Tested and Supported
- AUDIO audio test OMAP35x
- USB-RS232 USB-RS232 test OMAP35x
- Ethernet Ethernet Test OMAP35x
- USB ports USB0 USB1 USB Test OMAP35x
- DVSDK DVSDK Test OMAP35x
- GStreamer GStreamer Test OMAP35x
What's Tested and not Supported
- Audio not working.
- Logic PD 4.3” WQVGA DISPLAY KIT, model number: LCD-4.3-WQVGA-10R
- Changing the mode with OMAPL138 related pins
What's not Tested
- FPGA Communications Ports
- OMAP DEBUG (JTAG Interface)
- ALI Interface (AVNET LCD Interface)
- USER switches
- User LEDs
- FPGA GTP Interfaces
- installing an updated bootloader using make installbootloader