From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NFS boot problems !
Date: Sat, 24 Oct 2009 10:09:04 -0400 [thread overview]
Message-ID: <4AE30A80.10604@gmail.com> (raw)
In-Reply-To: <9c789a000910240122j776b762dodbddb97a105c942b@mail.gmail.com>
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]
next prev parent reply other threads:[~2009-10-24 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 8:17 [U-Boot] NFS boot problems ! Cristian Axenie
2009-10-24 8:22 ` Cristian Axenie
2009-10-24 9:43 ` Wolfgang Denk
2009-10-24 14:09 ` Jerry Van Baren [this message]
[not found] ` <9c789a000910240721i3a5ff36aoa08c0e5ee5761070@mail.gmail.com>
2009-10-24 14:21 ` Cristian Axenie
2009-10-24 14:39 ` Jerry Van Baren
2009-10-24 17:12 ` Wolfgang Denk
2009-10-24 21:08 ` Cristian Axenie
2009-10-24 8:57 ` wilbur.chan
2009-10-24 9:03 ` Cristian Axenie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE30A80.10604@gmail.com \
--to=gvb.uboot@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.