Getting Started Guide for DM6446 EVM
On this page you are going to find all the necessary information to start from scratch to use the RidgeRun SDK on your DM6446 evaluation module (EVM). In the following sections we assume that you have already downloaded the DVSDK version 4.01.00.09 for OMAP3X processor (this version is compatible with the DM6446) and that you have installed the toolchain 2009q1-203 from codesourcery as well as your DM6446 SDK following the steps on The RidgeRun installation guide.
RidgeRun SDK's kernel has support for the following list of drivers for the DM6446 processor:
- UART driver
- I2C driver
- GPIO driver
- EDMA driver
- NAND driver with 4-bit ECC, SLC/MLC, up to 4K page size support
- MMC/SD driver with SDHC and SDIO support
- SPI driver with EEPROM support (polled, PIO and DMA mode of operation)
- USB driver with Host, Device and OTG modes; Supports USB Host/Device Mass Storage Class, USB Hub and HID clasess as well as USB Device CDC / RNDIS classes
Basic preliminary work
Installing the DVSDK
- Set the DVSDK binary as executable and set the required permissions.
sudo chmod 777 dvsdk_omap3530-evm_4_01_00_09_setuplinux
- Install the DVSDK. For ubuntu versions different than Ubuntu 10.04 LTS 32-bit you will need to add the --forcehost argument to install it:
note: During the EZSDK installation process you will be asked for the toolchain's path, assuming that you installed it on /opt, the path that you need to provide is /opt/codesourcery/arm-2009q1/bin/
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.
Setting up a TFTP server
If you are planning to use the SDK's installer to install images generated by the SDK in NAND, installing a TFTP server you will speed up downloads to the target hardware by using TFTP.
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 in order to work properly.
It is possible that during u-boot / UBL related tasks your board's bootloader becomes corrupted ( likely due to a write / erase operation of address where u-boot / UBL is stored in NAND / NOR ). In such case, it is necessary to use the TI's Flash Utilities provided with your DM6446 SDK.