[U-Boot] NFS boot problems !
Hi all !
I try to boot the kernel and rootfs using NFS! Next is my u-boot env:
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr bootdelay=6 baudrate=115200 loads_echo=1 ethaddr=04:00:00:00:00:0A eth1addr=04:00:00:00:00:0B netdev=eth0 consoledev=ttyS0 fdtaddr=400000 ethact=eTSEC0 fdtfile=mpc8315erdb_default.dtb ramdiskfile=rootfs.ext2.gz.uboot ipaddr=192.168.1.100 othbootargs=ramdisk_size=65535 loadaddr=1000000 ramdiskaddr=2000000 sataboot=setenv bootargs root=/dev/sda1 rw console=ttyS0,115200;bootm fe500000 - fe700000 ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm fe500000 fe100000 fe700000 mtdids=nor0=nor,nand0=nand usbstick=run usbstick_args;bootm fe500000 - fe700000 usbstick_args=setenv bootargs root=/dev/sda1 ro rootdelay=5 rootfstype=ext2 init=/sbin/init console=ttyS0,115200 serverip=192.168.1.103 rootpath=/home/haustiq/development/rootfs gatewayip=192.168.1.103 netmask=255.255.0.0 macaddr=04000000000A hostname=haustiq bootcmd=run nfsboot stdin=serial stdout=serial stderr=serial bootfile=/home/haustiq/development/uImage
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'. Load address: 0x1000000 Loading: * TFTP error: 'Access violation' (2) Starting again
Any ideas ?
Changing file permissions on the server side shared files didn't helped !
Best !
Hi all !
I try to boot the kernel and rootfs using NFS! Next is my u-boot env:
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr - $fdtaddr bootdelay=6 baudrate=115200 loads_echo=1 ethaddr=04:00:00:00:00:0A eth1addr=04:00:00:00:00:0B netdev=eth0 consoledev=ttyS0 fdtaddr=400000 ethact=eTSEC0 fdtfile=mpc8315erdb_default.dtb ramdiskfile=rootfs.ext2.gz.uboot ipaddr=192.168.1.100 othbootargs=ramdisk_size=65535 loadaddr=1000000 ramdiskaddr=2000000 sataboot=setenv bootargs root=/dev/sda1 rw console=ttyS0,115200;bootm fe500000 - fe700000 ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm fe500000 fe100000 fe700000 mtdids=nor0=nor,nand0=nand usbstick=run usbstick_args;bootm fe500000 - fe700000 usbstick_args=setenv bootargs root=/dev/sda1 ro rootdelay=5 rootfstype=ext2 init=/sbin/init console=ttyS0,115200 serverip=192.168.1.103 rootpath=/home/haustiq/development/rootfs gatewayip=192.168.1.103 netmask=255.255.0.0 macaddr=04000000000A hostname=haustiq bootcmd=run nfsboot stdin=serial stdout=serial stderr=serial bootfile=/home/haustiq/development/uImage
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'. Load address: 0x1000000 Loading: * TFTP error: 'Access violation' (2) Starting again
Any ideas ?
Changing file permissions on the server side shared files didn't helped !
Best !
Dear Cristian Axenie,
In message 9c789a000910240122j776b762dodbddb97a105c942b@mail.gmail.com you wrote:
I try to boot the kernel and rootfs using NFS!
What exactly has this to do with NFS at all?
TFTP from server 192.168.1.103; our IP address is 192.168.1.100 Filename '/home/haustiq/development/uImage'. Load address: 0x1000000 Loading: * TFTP error: 'Access violation' (2)
This is a TFTP error message. Not NTS.
Any ideas ?
Well, check your server configuration. This is not a U-Boot problem.
Changing file permissions on the server side shared files didn't helped !
You did not manage to change the right permissions, then. In addition to file permissions there are directory permissions, and eventually things like hosts.allow/.deny and/or firewall rules. But the 'Access violation' message is pretty clear.
Fix your TFTP server config.
Best regards,
Wolfgang Denk
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]
2009/10/24 Cristian Axenie cristian.axenie@gmail.com:
Load address: 0x1000000 Loading: * TFTP error: 'Access violation' (2)
Test this : mw 0x1000000 0x1234
Ok ! And what do you exactly want to test with this, if I can write to the memory ? The u-boot command returns sucessfully! no problem with mw !
On Sat, Oct 24, 2009 at 11:57 AM, wilbur.chan wilbur512@gmail.com wrote:
2009/10/24 Cristian Axenie cristian.axenie@gmail.com:
Load address: 0x1000000 Loading: * TFTP error: 'Access violation' (2)
Test this : mw 0x1000000 0x1234
participants (4)
-
Cristian Axenie -
Jerry Van Baren -
wilbur.chan -
Wolfgang Denk