TI中文支持网您好，公司最近购买了一块OMAP-L138开发板，我按照SD卡里面的setup.htm步骤搭建开发平台，具体流程如下
Starting your Development on OMAP-L138
1. Hopefully you have already enjoyed the demos described in the OMAP-L138 eXperimeter Quick Start Guide or the OMAP-L138 EVM Quick Start Guide. This is the same print out which is provided with your OMAP-L138 kit. To get started ensure you have a Linux Ubuntu 10.04 LTS host environment setup to proceed. A Ubuntu 10.04 CD is provided in the kit. If you don't have a dedicated host Linux PC to install Ubuntu 10.4, visit How to create a Linux host machine on your Windows PC.
2. When your board is set up as described in the Quick Start Guide, insert the Code Sourcery Toolchain CD in to the CD-ROM drive of your Linux development host.
3. On Ubuntu 10.04 LTS open a terminal window as follows: Applications->Accessories->Terminal.
4. Enter the Code Sourcery directory (if necessary, replace 2009q1-203 with the version of Code Sourcery you are trying to install)
host# cd /media/cdrom/Sourcery\ G++\ Lite\ 2009q1-203\ for\ ARM\ GNU\ Linux/i686-pc-linux-gnu/
Note: On some machines the CD-ROM will be list as /media/disk.
5. Execute the installer with a .bin file extension as follows (again replace 2009q1-203 with the version of Code Sourcery you are trying to install if necessary). Follow the installer instructions on the screen to do a Typical installation.
host# ./arm-2009q1-203-arm-none-linux-gnueabi.bin
Note: There is no need to read the Getting Started Guide from Code Sourcery at this point in time. You can read it later if necessary.
6. Remove the CD from the CD-ROM.
7. Enter the /media/START_HERE directory and execute the dvsdk_omapl138-evm_4_XX_XX_XX_setuplinux file (if necessary, replace 4_XX_XX_XX with the actual version number of the file you have on the SD card). Follow the installer instructions.
host# cd /media/START_HERE
host# ./dvsdk_omapl138-evm_4_XX_XX_XX_setuplinux
8. Once installation is complete, the Software Developer's Guide (SDG) will open as a pdf file. Follow its instructions to start developing software for the OMAP-L138. The SDG and other documentation can be found in the docs folder of the DVSDK installation directory.
当安装完dvsdk_omapl138-evm_04_03_00_06_setuplinux之后，运行dvsdk目录下的setup.sh，安装默认设置，具体信息如下：
egg@egg:~/Desktop/Link to ti-dvsdk_omapl138-evm_04_03_00_06$ ./setup.sh
——————————————————————————–
TISDK setup script
This script will set up your development host for dvsdk development.
Parts of this script require administrator priviliges (sudo access).
——————————————————————————–
——————————————————————————–
Verifying Linux host distribution
Ubuntu 10.04 LTS found successfully, continuing..
——————————————————————————–
——————————————————————————–
This step will make sure you have the proper host support packages installed
using the following command: sudo apt-get install xinetd tftpd nfs-kernel-server minicom build-essential libncurses5-dev uboot-mkimage autoconf automake
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
[sudo] password for egg:
Reading package lists… Done
Building dependency tree
Reading state information… Done
xinetd is already the newest version.
tftpd is already the newest version.
nfs-kernel-server is already the newest version.
minicom is already the newest version.
build-essential is already the newest version.
libncurses5-dev is already the newest version.
uboot-mkimage is already the newest version.
autoconf is already the newest version.
automake is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 362 not upgraded.
Package verification and installation successfully completed
——————————————————————————–
——————————————————————————–
In which directory do you want to install the target filesystem?(if this directory does not exist it will be created)
[ /home/egg/targetfs ]
——————————————————————————–
——————————————————————————–
This step will extract the target filesystem to /home/egg/targetfs
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/egg/targetfs already exists
(r) rename existing filesystem (o) overwrite existing filesystem (s) skip filesystem extraction
[r] s
Skipping filesystem extraction
WARNING! Keeping the previous filesystem may cause compatibility problems if you are upgrading the SDK
——————————————————————————–
——————————————————————————–
This step will update the EXEC_DIR variables in the Rules.make file
This will facilitate the SDK to install (with make install) rebuilt binaries in
/home/egg/targetfs
The files will be available from / on the target.
This setting can be changed later by editing Rules.make and changing the
EXEC_DIR variable.
Press return to continue
Rules.make edited successfully..
——————————————————————————–
——————————————————————————–
This step will export your target filesystem for NFS access.
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/home/egg/targetfs already NFS exported, skipping..
* Stopping NFS kernel daemon [ OK ]
* Unexporting directories for NFS kernel daemon… [ OK ]
* Exporting directories for NFS kernel daemon… [ OK ]
* Starting NFS kernel daemon [ OK ]
——————————————————————————–
——————————————————————————–
Which directory do you want to be your tftp root directory?(if this directory does not exist it will be created for you)
[ /tftpboot ]
——————————————————————————–
——————————————————————————–
This step will set up the tftp server in the /tftpboot directory.
Note! This command requires you to have administrator priviliges (sudo access)
on your host.
Press return to continue
/tftpboot already exists, not creating..
/tftpboot/uImage-da850-omapl138-evm.bin already exists. The existing installed file can be renamed and saved under the new name.
(r) rename (o) overwrite (s) skip copy
[r] s
Skipping copy of uImage-da850-omapl138-evm.bin, existing version will be used
/etc/xinetd.d/tftp already exists..
/tftpboot already exported for TFTP, skipping..
Restarting tftp server
* Stopping internet superserver xinetd [ OK ]
* Starting internet superserver xinetd [ OK ]
——————————————————————————–
——————————————————————————–
This step will set up minicom (serial communication application) for
DVSDK development
Which serial port do you want to use with minicom?
[ /dev/ttyS0 ] /dev/ttyS1
Copied existing /home/egg/.minirc.dfl to /home/egg/.minirc.dfl.old
Configuration saved to /home/egg/.minirc.dfl. You can change it further from inside
minicom, see the Software Development Guide for more information.
——————————————————————————–
——————————————————————————–
This step will set up the u-boot variables for booting the EVM.
Autodetected the following ip address of your host, correct it if necessary
[ 192.168.1.24 ]
Select board memory:
1: 128MB
2: 64MB
[ 1 ]
Select Linux kernel location:
1: TFTP
2: SD card
3: flash
[ 1 ]
Select root file system location:
1: NFS
2: SD card
[ 1 ]
Available kernel images in /tftpboot:
uImage-da850-omapl138-evm.bin
Which kernel image do you want to boot from TFTP?
[ uImage-da850-omapl138-evm.bin ]
Resulting u-boot variable settings:
setenv bootdelay 4
setenv baudrate 115200
setenv bootargs console=ttyS2,115200n8 noinitrd rw mem=32M@0xc0000000 mem=64M@0xc4000000 root=/dev/nfs nfsroot=192.168.1.24:/home/egg/targetfs,nolock ip=dhcp
setenv bootcmd 'dhcp;setenv serverip 192.168.1.24;tftpboot;bootm'
setenv autoload no
setenv serverip 192.168.1.24
setenv bootfile uImage-da850-omapl138-evm.bin
——————————————————————————–
——————————————————————————–
Would you like to create a minicom script with the above parameters (y/n)?
[ y ]
Moving existing setup_uimage-tftp_fs-nfs.minicom to setup_uimage-tftp_fs-nfs.minicom.old
Successfully wrote setup_uimage-tftp_fs-nfs.minicom
Would you like to run the setup script now (y/n)? This requires you to connect
the RS-232 cable between your host and EVM as well as your ethernet cable as
described in the Quick Start Guide. Once answering 'y' on the prompt below
you will have 300 seconds to connect the board and power cycle it
before the setup times out.
After successfully executing this script, your EVM will be set up. You will be
able to connect to it by executing 'minicom -w' or if you prefer a windows host
you can set up Tera Term as explained in the Software Developer's Guide.
If you connect minicom or Tera Term and power cycle the board Linux will boot.
[ y ]
~/Desktop/Link to ti-dvsdk_omapl138-evm_04_03_00_06 ~/Desktop/Link to ti-dvsdk_omapl138-evm_04_03_00_06
当到了这一步，DVSDK的setup.sh运行完成，reset EVM后将通过串口将启动配置写入SPI Flash，
Welcome to minicom 2.4
OPTIONS: I18n
Compiled on Jan 25 2010, 06:49:09.
Port /dev/ttyS1
Press CTRL-A Z for help on special keys
Booting with TI UBL
Device OPP (300MHz, 1.2V)
U-Boot 2010.12 (Dec 23 2011 – 11:22:43)
I2C: ready
DRAM: 128 MiB
MMC: davinci: 0
SF: Detected M25P64 with page size 256, total 8 MiB
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 132000000 Hz
Net: Ethernet PHY: GENERIC @ 0x00
DaVinci-EMAC
Hit any key to stop autobo 0
U-Boot >setenv bootdelay 4
U-Boot >setenv baudrate 115200
## Switch baudrate to 115200 bps and press ENTER …U-Boot >setenv oldbootargs }
U-Boot >ip=dhcp
U-Boot >setenv autoload no
U-Boot >setenv oldserverip ${serverip}
U-Boot >setenv serverip 192.168.1.24
U-Boot >setenv bootfile uImage-da850-omapl138-evm.bin
U-Boot >setenv oldbootcmd ${bootcmd}
U-Boot >setenv bootcmd 'dhcp;setenv serverip 192.168.1.24;tftpboot;bootm'
U-Boot >saveenv
Saving Environment to SPI Flash…
SF: Detected M25P64 with page size 256, total 8 MiB
Erasing SPI flash…Writing to SPI flash…done
U-Boot >
You can manually run minicom in the future with this setup script using: minicom -S setup_uimage-tftp_fs-nfs.minicom
——————————————————————————–
TISDK setup completed!
Please continue reading the Software Developer's Guide for more information on
how to develop software on the EVM
egg@egg:~/Desktop/Link to ti-dvsdk_omapl138-evm_04_03_00_06$ minicom -w
完成写入配置信息，reset EVM，之后问题就来了，EVM找不到tfpt上的系统镜像文件，启动不了，错误信息如下：
Welcome to minicom 2.4
OPTIONS: I18n
Compiled on Jan 25 2010, 06:49:09.
Port /dev/ttyS1
Press CTRL-A Z for help on special keys
Booting with TI UBL
Device OPP (300MHz, 1.2V)
U-Boot 2010.12 (Dec 23 2011 – 11:22:43)
I2C: ready
DRAM: 128 MiB
MMC: davinci: 0
SF: Detected M25P64 with page size 256, total 8 MiB
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 132000000 Hz
Net: Ethernet PHY: GENERIC @ 0x00
DaVinci-EMAC
Hit any key to stop autoboot: 0
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 52
*** Unhandled DHCP Option in OFFER/ACK: 52
DHCP client bound to address 192.168.1.105
Using DaVinci-EMAC device
TFTP from server 192.168.1.24; our IP address is 192.168.1.105
Filename '锟?.
Load address: 0xc0700000
Loading: *
TFTP error: 'File not found' (1)
Not retrying…
Wrong Image Format for bootm command
ERROR: can't get kernel image!
请问有哪位遇见过这种情况，请帮忙指点。
Sheng Liu1：
红色部分打印文件名有问题：
Filename '锟?.
建议UBoot启动后重新进行设置，可以参考：
U-Boot >setenv bootfile uImage-da850-omapl138-evm.bin
重新设置bootfile
