From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Van Baren <gvb.uboot@gmail.com>
Date: Sat, 24 Oct 2009 10:09:04 -0400
Subject: [U-Boot] NFS boot problems !
In-Reply-To: <9c789a000910240122j776b762dodbddb97a105c942b@mail.gmail.com>
References: <9c789a000910240117i748bfcc3k2503c7cb39f309@mail.gmail.com>
	<9c789a000910240122j776b762dodbddb97a105c942b@mail.gmail.com>
Message-ID: <4AE30A80.10604@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Cristian Axenie wrote:
> Hi all !
> 
> I try to boot the kernel and rootfs using NFS!
> Next is my u-boot env:

[snip]

> bootfile=/home/haustiq/development/uImage

Likely wrong (see below).

> My problem is that when I
> 
> run bootcmd
> 
> I get :
> 
> 
> Speed: 100, full duplex
> Using eTSEC0 device
> TFTP from server 192.168.1.103; our IP address is 192.168.1.100
> Filename '/home/haustiq/development/uImage'.

This does *NOT* look like a valid path.  TFTP servers typically serve 
out of a dedicated directory (often /tftpboot) and the paths to the 
files are usually relative to the root folder.

You probably want to copy your uImage to /tftpboot/uImage and use the 
file name either uImage or /uImage or /tftboot/uImage.

Do a "tftp get" from a computer, preferably not your tftp server 
computer, to figure out your TFTP server path and file names before 
trying to TFTP from u-boot.

If you run stuck, use wireshark on your server to see what is going on 
on the wire.

> Load address: 0x1000000
> Loading: *
> TFTP error: 'Access violation' (2)
> Starting again
> 
> Any ideas ?

Wrong path/file.

Good luck,
gvb

[snip]