One last thing I just remembered . . . ip_addr *has* to be defined, and correct in order to use TFTP boot. I talked with Robert about this a long time ago, but do not remember if client_ip is tied to ip_addr or not.
On Wed, Jul 1, 2015 at 12:06 PM, William Hermans <[email protected]> wrote: > Also as a guide . . . > > debian@beaglebone:~$ cat /nfs-uEnv.txt > ##Rename as: uEnv.txt to boot via nfs > > ##https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt > > ##SERVER: sudo apt-get install tftpd-hpa > ##SERVER: TFTP_DIRECTORY defined in /etc/default/tftpd-hpa > ##SERVER: zImage/*.dtb need to be located here: > ##SERVER: TFTP_DIRECTORY/zImage > ##SERVER: TFTP_DIRECTORY/dtbs/*.dtb > > ##client_ip needs to be set for u-boot to try booting via nfs > > client_ip=192.168.1.101 > > #u-boot defaults: uncomment and override where needed > > #server_ip=192.168.1.100 > #gw_ip=192.168.1.1 > #netmask=255.255.255.0 > #hostname= > #device=eth0 > #autoconf=off > #root_dir=/home/userid/targetNFS > #nfs_options=,vers=3 > #nfsrootfstype=ext4 rootwait fixrtc > > > On Wed, Jul 1, 2015 at 11:58 AM, Robert Nelson <[email protected]> > wrote: > >> On Wed, Jul 1, 2015 at 1:42 PM, <[email protected]> wrote: >> > I am having some serious problems getting TFTP boot to work. Apparently >> no >> > problems accessing a zImage or .dtb from other machines on the network. >> The >> > bone on the other hand plain nuts. Need to investigate further. >> > >> > >> > >> > 1 question. Saveenv appears to be disabled in the current u-boot build. >> Any >> > reason for this? >> >> It's disabled as it was causing boot issues on the beaglebone white.. >> >> > How then to clear everything without rebuilding and installing u-boot? >> > >> > I need to be able to drive u-boot from the command line to see if I can >> get >> > tftp and bootz to work. >> > >> > TAIA. >> > >> > P.S. We’ll leave the NFS side of things for later. That too appears >> whacked >> > on the B3. >> >> BTW, the default u-boot has a few things already setup for nfs. >> >> To enable it, via (/boot/uEnv.txt) set client_ip to your whish'ed ip >> address.. >> >> client_ip=192.168.(something..) >> >> Next, these are set by default: >> >> #************* >> server_ip=192.168.1.100 >> gw_ip=192.168.1.1 >> netmask=255.255.255.0 >> hostname= >> device=eth0 >> autoconf=off >> root_dir=/home/userid/targetNFS >> nfs_options=,vers=3 >> nfsrootfstype=ext4 rootwait fixrtc >> #************* >> >> For most users, setting server_ip, gw_ip & root_dir is enough. >> >> It loads the kernel/dtb over tftp either 2 ways: >> >> zImage >> dtbs/am335x-boneblack.dtb >> >> Or if uname_r is defined: >> >> vmlinuz-${uname_r} >> dtbs/${uname_r}/am335x-boneblack.dtb >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
