DM8168 Boot with NFS

Do you want o have NSF or JSFF2?

if you want to JSFF2, remove rootfstype=jsff2 from bootargs

if you want to JSFFS, pleas set the root=/dev/mtdbl0ck04 and remvoe nfsroot from bootargs.

bootargs 'rootdelay=10 mem=254M console=ttyO2,115200n8 root=/dev/nfs rw rootfstype=jffs2 nfsroot=192.168.1.20:/home/heb/tftproot ip=192.168.1.10:192.168.1.20:192.168.1.1:255.255.255.0::eth0:off vram=20M notifyk.vpssm3_sva=0xBFD00000'

Regards

yihe

Everything looks to be in place. Maybe try removing "rootfstype=jffs2" from the bootargs. I've never seen rootfstype used with NFS. Maybe it is confusing mount. What do you have at 192.168.1.20:/home/heb/tftproot?

Hi folks,
thanks for Your answers,


The bootarg "rootfstype=jffs2" comes from UdWorks.
I used this like a template.

Here is the content of 192.168.1.20/home/heb/tftproot:

 uImage_DM816X_DVR (Kernel to load via Tftp)   
 uboot_NAND_DM816X_DVR (Uboot binary)
 rfs_256_DM816X_DVR.jffs2 (256 MB version of root file system, JFFS2)
 rfs_128_DM816X_DVR.jffs2 (128 MB version of root file system, JFFS2)
 /folder rfs (complete root file system folder)


By the way, I am not sure, but I would expect a connection via RPC
like this:

 "Looking up port of RPC xxxxxx/x on 192.168.1.20"

after the network connection occurs and before the root delay waiting comes up.

 IP-Config: Complete:
     device=eth0, addr=192.168.1.10, mask=255.255.255.0, gw=192.168.1.1,
     host=192.168.1.10, domain=, nis-domain=(none),
     bootserver=192.168.1.20, rootserver=192.168.1.20, rootpath=
 -->  ???
 Waiting 5sec before mounting root device...


And I also can not understand why I'm not able to mount the nfs if the
original kernel from UdWorks is running fromm Flash

 mount -t nfs 192.168.1.20:/home/heb/tftproot /test/

Here I get the following message:

 mount: RPC: Remote system error - Connection refused

Is this a portmapper problem ?

Yeah, you should be getting RPC messages. Some TI kernels might suppress those messages.

Do you have a firewall setup on your server? Try disabling it.

The NFS root directory should contain the usual root stuff, eg. dev, etc, home, etc. Does 192.168.1.20/home/heb/tftproot/rfs have all that?

Hi Norman,
Thanks for Your reply.

Yes, I expected RCP messages after network connection.
I also activated NFS4 in the kernel configuration,
but without success. For testing, I disabled NFS3 in the kernel
configuration to use only NFS4, but in this situation, the kernel hangs.

But back to Your question:
The firewall of my host is disabled. (sudo iptables -F)
My /home/heb/tftproot/rfs contains a complete root file system with all the necessary folders and files.
So,one question, for my understanding: The bootcmd contains a jffs2 file.
Do You think to load the root file system directly here, is this possible ?
Than I have to change the bootcmds ?

Happy Easter to You !

Happy Easter as well!

Just noticed you stated that the server firewall is off in your first post. Sorry, I missed that. I think you've exceed my knowledge on the subject. Everything looks very proper. To review. U-boot can TFTP...so it's not a HW problem. You can access your NFS server from other machines. So it's not likely to be an NFS server problem. The exports has no_root_squash and masked to local subnet. All good.

You do need to point to the rfs directory for NFS. Change your bootargs and exports as appropriate. The rfs directory has to be owned by root. Personally, I've not had success of creating an NFS root directory by any other means except by untaring an archive. Takes care of those special files that copy does not handle properly

I don't see a JFFS2 reference in the bootcmd. It downloads a uImage in that U-Boot specific format. If you mean for U-boot to load the filesystem, I've only seen examples of U-boot loading a compressed EXT2 image (.gz) into RAM for a ramdisk.

It is quite odd that you cannot manually mount the NFS directory. The error message is different from another error that suggests you need to repeat the address in the mount command. The error message would suggest a server mismatch or permission problem. I don't have much experience with that. You know more than I about the NFS3 vs NFS4 issues. A quick sanity check. Can you ping the server from Linux?

Hi Norman,
Thank You for the detailed answer.
My host can ping the target and my target can ping the host.
Tomorrow if I am back in the office, I will try to load the rfs in the way You suggested.

Hi Holger,

Can you restart your NFS server?

http://e2e.ti.com/support/embedded/linux/f/354/p/180934/652113.aspx#652113

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!

Hi Anil,
Yes I also used exportfs and restarted the NFS server.
The NFS server is running, I have access from an external
NFS client from another PC. I have tested this.
Regards

Hi Holger,

Just now noticed one point from your log messages.

NFS server directory should have all the filesystem common folders (as Norman pointed out, /etc/, /usr, /home/, /root/, /var etc)

Modify the line in exportfs file to

/home/heb/tftproot/rfs     *(rw,no_root_squash,no_subtree_check,no_all_squash,sync)

then restart your server, so that you can able to mount the file system.

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!

 Hi folks,

Ok, I changed the bootcmd:

setenv bootcmd 'ping 192.168.1.20; sleep 2; tftp 0x81000000 uImage_DM816X_DVR; bootm 0x81000000';
setenv bootargs 'rootdelay=10 mem=254M console=ttyO2,115200n8 root=/dev/nfs rw nfsroot=192.168.1.20:/home/heb/tftproot/rfs ip=192.168.1.10:192.168.1.20:192.168.1.1:255.255.255.0::eth0:off vram=20M notifyk.vpssm3_sva=0xBFD00000'

and I also change exports:

/home/heb/tftproot/rfs 192.168.1.0/255.255.255.0(rw,insecure,async,no_subtree_check,no_root_squash)

but no success occurs.

I get the following output from my target if the kernel is running:

Connect speed 100M Full
Using DaVinci EMAC device
host 192.168.1.20 is alive
Connect speed 100M Full
Using DaVinci EMAC device
TFTP from server 192.168.1.20; our IP address is 192.168.1.10
Filename 'uImage_DM816X_DVR'.
Load address: 0x81000000
Loading: #################################################################
         #################################################################
         ###############################
done
Bytes transferred = 2353616 (23e9d0 hex)
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Created:      2012-02-07   7:43:56 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2353552 Bytes = 2.2 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.37 (root@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-
203) ) #1 Tue Feb 7 16:43:51 KST 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8168_dvr
vram size = 20971520 at 0x0
reserved size = 20971520 at 0x0
FB: Reserving 20971520 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8168 1.1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 59396
Kernel command line: rootdelay=10 mem=254M console=ttyO2,115200n8 root=/dev/nfs
rw nfsroot=192.168.1.20:/home/heb/tftproot/rfs ip=192.168.1.10:192.168.1.20:192.
168.1.1:255.255.255.0::eth0:off vram=20M notifyk.vpssm3_sva=0xBFD00000
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 234MB = 234MB total
Memory: 232276k/232276k available, 27820k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xd0000000 - 0xf8000000   ( 640 MB)
    lowmem  : 0xc0000000 - 0xcfe00000   ( 254 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc0039000   ( 196 kB)
      .text : 0xc0039000 - 0xc0476000   (4340 kB)
      .data : 0xc0476000 - 0xc04b99c0   ( 271 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
OMAP clockevent source: GPTIMER1 at 27000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 0
3-wired eeprom init done. (H/W ver:5b)
_omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl
_omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda
registered ti816x_vpss device
registered TI816x on-chip HDMI device
registered ti816x_sr device
registered ti81xx_vidout device
pm_dbg_init: only OMAP3 supported
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
regulator: pmbus_vr: 800 <--> 1100 mV at 890 mV
regulator: tps40400 probe done.
omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
musb-hdrc: kernel must blacklist external hubs
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d001e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
musb-hdrc: kernel must blacklist external hubs
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d0028800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 453
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x3
ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc
scsi0 : ahci_platform
scsi1 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
ata2: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
omap2-nand driver initializing
NAND device: Maf ID: 0xec, Chip ID: 0xda (Samsung, )
 erasesize: 0x20000, writesize: 2048, oobsize: 64
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000240000 : "U-Boot"
0x000000240000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffff8
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
davinci_mdio davinci_mdio.0: phy[2]: device 0:02, driver unknown
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
rtc-ds1307 1-0068: rtc core: registered ds1337 as rtc0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usb 1-1: new low speed USB device using musb-hdrc and address 2
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0x
bfd00000
usbcore: registered new interface driver snd-usb-audio
number of tvp5158 chips 4
chip address 59,chip address 5d,chip address 5b,chip address 5f,
tvp5158-audio.2-005c initial ok!
asoc: tvp5158-hifi <-> davinci-mcasp.0 mapping ok
asoc: SII9022a-hdmi-codec <-> davinci-mcasp.1 mapping ok
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
  #0: TI81XX DVR
  #1: TI81XX DVR (HDMI)
TCP cubic registered
NET: Registered protocol family 17
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
smartreflex-ti816x: ti816x_sr_probe done!
rtc-ds1307 1-0068: setting system clock to 2012-04-10 06:55:57 UTC (1334040957)
usb 1-1: New USB device found, idVendor=046d, idProduct=c050
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: USB-PS/2 Optical Mouse
usb 1-1: Manufacturer: Logitech
generic-usb 0003:046D:C050.0001: input: USB HID v1.10 Mouse [Logitech USB-PS/2 O
ptical Mouse] on usb-musb-hdrc.0-1/input0
davinci_mdio davinci_mdio.0: resetting idled controller
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=1cc914)
IP-Config: Complete:
     device=eth0, addr=192.168.1.10, mask=255.255.255.0, gw=192.168.1.1,
     host=192.168.1.10, domain=, nis-domain=(none),
     bootserver=192.168.1.20, rootserver=192.168.1.20, rootpath=
Waiting 10sec before mounting root device...
ata1: SATA link down (SStatus 0 SControl 300)
PHY: 0:01 - Link is Up - 100/Full
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.15: Port Multiplier 1.2, 0x197b:0x3215 r0, 5 ports, feat 0x5/0xf
ata2.00: hard resetting link
ata2.00: SATA link down (SStatus 0 SControl 320)
ata2.01: hard resetting link
ata2.01: SATA link down (SStatus 0 SControl 320)
ata2.02: hard resetting link
ata2.02: SATA link up 3.0 Gbps (SStatus 123 SControl 320)
ata2.03: hard resetting link
ata2.03: SATA link down (SStatus 0 SControl 320)
ata2.04: hard resetting link
ata2.04: SATA link down (SStatus 0 SControl 320)
ata2.02: ATA-8: Hitachi HTS545050KTA300, BKFOC60M, max UDMA/133
ata2.02: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.02: configured for UDMA/133
ata2: EH complete
scsi 1:2:0:0: Direct-Access     ATA      Hitachi HTS54505 BKFO PQ: 0 ANSI: 5
sd 1:2:0:0: Attached scsi generic sg0 type 0
sd 1:2:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 1:2:0:0: [sda] Write Protect is off
sd 1:2:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO
 or FUA
 sda: sda1
sd 1:2:0:0: [sda] Attached SCSI disk
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            2304 mtdblock0  (driver?)
1f01             256 mtdblock1  (driver?)
1f02            4352 mtdblock2  (driver?)
1f03          204928 mtdblock3  (driver?)
1f04           50304 mtdblock4  (driver?)
0800       488386584 sda  driver: sd
  0801       488385560 sda1 00000000-0000-0000-0000-000000000sda1
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c0047b90>] (dump_backtrace+0x0/0x110) from [<c0355060>] (dump_stack+0x18/0x1c)

 r7:ce7d8000 r6:00000000 r5:c002c7a4 r4:c04ba110
[<c0355048>] (dump_stack+0x0/0x1c) from [<c03550c4>] (panic+0x60/0x17c)
[<c0355064>] (panic+0x0/0x17c) from [<c0009254>] (mount_block_root+0x1e0/0x220)
 r3:00000000 r2:00000000 r1:ce42bf58 r0:c04017cc
[<c0009074>] (mount_block_root+0x0/0x220) from [<c0009340>] (mount_root+0xac/0xc
c)
[<c0009294>] (mount_root+0x0/0xcc) from [<c00094d0>] (prepare_namespace+0x170/0x
1d4)
 r4:c04b9a24
[<c0009360>] (prepare_namespace+0x0/0x1d4) from [<c0008784>] (kernel_init+0x114/
0x154)
 r5:c0008670 r4:c04b99c0
[<c0008670>] (kernel_init+0x0/0x154) from [<c006c540>] (do_exit+0x0/0x5e4)
 r5:c0008670 r4:00000000

Hi,

Can you use the same NFS for the other board? did you extract the rootfs with sudo permission? you should be sudo while doing this.

After doing set booatrgs and doing saveenv can attach the log printenv?

Can you also attach the log of following commands ,

1: sudo exportfs -ra

2: sudo /etc/init.d/nfs-kernel-server restart

Thx,

--Prabhakar Lad

Hi Prabhakar Lad,

The NFS server is accessable from an external PC, this works.
I used sudo permission for extracting rootfs.
Here comes the log You wanted:

UBOOT # printenv
baudrate=115200
autoload=no
gatewayip=192.168.1.1
ntpserverip=192.168.1.151
timeoffset=32400
ethact=DaVinci EMAC
filesize=23E9D0
ipaddr=192.168.1.10
gateway=192.168.1.1
netmask=255.255.255.0
serverip=192.168.1.20
bootdelay=5
rootwait=0
rootdelay=5
bootcmd=ping 192.168.1.20; sleep 2; tftp 0x81000000 uImage_DM816X_DVR; bootm 0x8
1000000
bootargs=rootdelay=10 mem=254M console=ttyO2,115200n8 root=/dev/nfs rw nfsroot=1
92.168.1.20:/home/heb/tftproot/rfs ip=192.168.1.10:192.168.1.20:192.168.1.1:255.
255.255.0::eth0:off vram=20M notifyk.vpssm3_sva=0xBFD00000
stdin=serial
stdout=serial
stderr=serial
ethaddr=44:aa:27:00:01:2e
eth1addr=44:aa:27:00:01:2f
hwver=00:5b
ver=U-Boot 2010.06 (Dec 08 2011 - 21:47:27)

heb@heb-desktop:~/tftproot$ sudo exportfs -rav
exporting 192.168.1.0/255.255.255.0:/home/heb/tftproot/rfs

heb@heb-desktop:~/tftproot$ sudo /etc/init.d/nfs-kernel-server restart
 * Stopping NFS kernel daemon                                            [ OK ]
 * Unexporting directories for NFS kernel daemon...                      [ OK ]
 * Exporting directories for NFS kernel daemon...                        [ OK ]
 * Starting NFS kernel daemon                                            [ OK ]

Best regards Holger

Hi,

The logs look perfect , apart from as Norman pointed out

in your exports file change the entry to /home/heb/tftproot/rfs     *(rw,no_root_squash,no_subtree_check,no_all_squash,sync)

and restart the NFS server and try.

Thx,

--Prabhakar Lad

Hi,

Ok I changed the line in the export file, but no success.

No booting from NFS.

Best regards Holger

Did a bit of reading on the "Connection refused" error (https://help.ubuntu.com/community/SettingUpNFSHowTo). Might indeed be a portmapper problem. Check "/etc/default/portmap" for binding to loopback, eg -l option. However that does not explain why other machines can connect to the NFS server. Maybe a router between your target and server causing problems? Yeah, grasping at straws here.

Comparing your bootloag against another bootlog (http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/158046.aspx). A few differences. His has IPV6, random MAC address and just 1 PHY. Probably not important? The "Link is Up" message is missing from your bootlog. When you are running from flash do you get that same message? Perhaps try a ridiculously long rootdelay. Appears the JFFS2 bootarg okay with NFS bootargs. A red herring I think.

Hi Norman,
Thanks for watching my problem. Nice community here.

I checked /etc/default/portmap. The line with loopback is commented.
I also did try a long rootdelay (60 seconds).
Using the bootarg "rootfstype=jffs2" has no effect.

And last bur not least, I used a new kernel. I tested Kernel 04.04.00.01 with the same results.

Tomorrow, in the office, I will try to setup another PC and run Ubuntu without Virtualbox.
I will post my results.

The mention of Ubuntu and VirtualBox reminded me about posts about "bridged adapter" mode in your virtual machine. Quickly mentioned here:

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/t/121814.aspx#435754

Hi folks,
I found the problem. Running Ubuntu in Virtualbox avoids contact to the NFS server.
I made a setup for Ubuntu 10.10 standalone and now I can boot the root file system.
For me it is not easy to understand, because I have access to the NFS server form an
external client (Windows PC) also via Virtualbox. And the network adapter in
Virtualbox is configured "Bridge"
Has anybody a solution for using Virtualbox with NFS ?

Hi Holger,

I'm using the same board with a 2.6.34 kernel and boot it via nfs. Virtual host has Ubuntu 10.04. with EZSDK + toolchain + tftp + nfs + targetfs image. I was using VirtualBox for the first time but when its screen resolution brakes a little I started using vmware. No special adjustments were made to them. Networking mode - bridge. Real host - Ubuntu 11.10.

Below my uboot config allowing a number of different boot modes (mmc, nfs, tftp and combinations). Perhaps it will be useful for you.

To choose a special boot mode once I write `run bootorig` to run original boot from sd or `run boot_tftp_nfs` (I'm using it and it is default boot mode now) or other command. 

Uboot config: 

TI8168_EVM#printenv
bootdelay=3
baudrate=115200
verify=yes
ramdisk_file=ramdisk.gz
loadaddr=0x81000000
script_addr=0x80900000
loadbootscript=fatload mmc 1 ${script_addr} boot.scr
bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${script_addr}
ethact=DaVinci EMAC
bootorig=if mmc init; then if run loadbootscript; then run bootscript; else echo In case ENV on MMC/SD is required; echo Please put a valid script named boot.scr on the card; echo Refer to the User Guide on how to generate the image; fi; else echo Please set bootargs and bootcmd before booting the kernel; echo If that has already been done please ignore this message; fi
setipaddr=dhcp; run addip;
addip=setenv bootargs ${bootargs} ip=${ipaddr}:${nfsserver}:${gatewayip}:${netmask}:${hostname}:eth0:off
ethaddr=00:08:65:23:22:19
hostname=integra
bootnfs=run setbootargs; run addip; nfs 0x81000000 ${nfsserver}:${nfsdir}/boot/${bootfile}; bootm 0x81000000;
nfsopts=timeo=70
setbootargs=setenv bootargs console=ttyS2,115200n8 root=/dev/nfs rw noinitrd init=/sbin/init nfsroot=${nfsserver}:${nfsdir},${nfsopts};
bootmmc_w_nfsroot=run setbootargs; run addip; mmc init; fatload mmc 1 0x81000000 uImage; bootm 0x81000000;
boot_tftp_nfs=setenv autoload no; setenv bootfile uImage-dm816x-evm.bin; run setbootargs_tftp_nfs; dhcp; tftpboot; bootm;
bootcmd=run boot_tftp_nfs
setbootargs_tftp_nfs=setenv bootargs console=ttyO2,115200n8 rootwait rw mem=120M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=${nfsserver}:${nfsdir} ip=dhcp
autoload=no
bootargs=console=ttyO2,115200n8 rootwait rw mem=120M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=192.168.102.160:/home/user/targetfs_last ip=dhcp
bootfile=uImage-dm816x-evm.bin
gatewayip=192.168.102.60
netmask=255.255.255.0
ipaddr=192.168.102.189
dnsip=192.168.102.71
dnsip2=192.168.101.60
nfsdir=/home/user/targetfs
nfsserver=192.168.102.195
serverip=192.168.102.195
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2010.06 (Nov 18 2010 - 22:36:59)

Hi Holger,

Good to see that problem is resolved.

I observed the same if I connect my Virtualbox to wireless network, I am able to access the NFS if I use the wired network. But I haven't investigated why this is happened?

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!

Hi Michael,

Thanks for Your answer and Your bootsettings.

At the moment, I use Windows XP with VirtualBox. Next I will test VMWare.

I have good experience with VMWare in the past.

I will post the results.

Hi folks,

I have tested Ubuntu10.04 running in VMWare with Windows 7.

NFS boot works perfect.

Thank You to all the folks here in this forum for the support  !