OMAPL138 Experimenter : setup.sh : Problem during Load uboot script

Which part of this failed? It looks like it wrote the correct environmental variables and saved it to the SPI flash. Now you can just reboot the board and it should boot Linux.

Jeff

The problem is that when I boot the board, Linux do not start and displays:

The TFTP server seems to be configured correctly  and I have no firewall on my computer (10.04 LTS).

service tftp
{
protocol = udp
port = 69
socket_type = dgram
wait = yes
user = nobody
server = /usr/sbin/in.tftpd
server_args = /tftpboot
disable = no
}

Hubert

Are you sure the ethernet connection to the EVM is good? Are the lights blinking on the connector? And are the EVM and the host computer connected together by a local switch, or what does the network look like?

Jeff

The lights are blinking properly.

The network consists simply of a computer and the board connected by a straight cable RJ45 100MHz.

Must I use a crossover cable ?

Thanks.

Hubert

Do you have a network switch laying around you can try out? That will take care of the crossover for you, but in general yes you would need one.

Jeff

I have connected the board to my computer via a hub and two straight cables, but communication still fails.

Here is my network configuration:

Soon, I'll try with a crossover cable.

Hubert

The SDK install script assumes a set up involving a router with DHCP so using the switch or hub won't work.

If you want to use direct connect, you need to assign static IPs on both the Linux PC and EVM. Cross-over type cable is not necessary.

On the EVM, you need to modify the bootargs by replacing ip=dhcp with ip=<EVM static IP address>, and remove the "dhcp" part in the 'bootcmd' environment variable

For example, let's say you want to use static IP addresses 192.168.1.101 for the EVM and 192.168.1.105 for the Linux PC. On the PC, assign the static IP 192.168.1.105 as per the direction for Ubuntu 10.04. On the EVM, boot the EVM to u-boot command prompt and modify the u-boot settings:

1) First list the settings

U-Boot > pri

2) replace the contents in the bootargs line where "ip=dhcp" with "ip=192.168.1.101" using the setenv command

3) update the contents of "bootcmd"

U-Boot > setenv bootcmd 'setenv serverip 192.168.1.105;tftpboot;bootm' 

4) save the environment settings using "saveenv"

5) Boot Linux with the U-Boot "boot" command

I changed the bootargs like this:

but it still does not work.

You still have the server ip address missing from the bootargs. On the first screen above, your "nfsroot=" should have the static ip address that you have assigned to the server (host Linux PC). If it is 192.168.1.1, then the bootargs should show   ".... root=/dev/nfs nfsroot=192.168.1.1:/home/hubert/targetfs,nolock ..."

---------------------------------------------------------------------------------------------------------
Please click the Verify Answer button on this post if it answers your question.
--------------------------------------------------------------------------------------------------------- 

If the serverip is already saved, you can remove the "setenv serverip 192.168.1.1" from the boot command.