• State
  • Locked Locked
  • Replies 19 replies
  • Subscribers 101 subscribers
  • Views 1754 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Booting from NFS

saadia
Intellectual 640 points

Hi guys,

I have been trying to boot from NFS. The steps are described in the GSG in sec.4.3.5. I have followed them all. But i get an error. Please check below:

DM355 EVM # setenv bootcmd 'nboot 0x8700000 0 0x400000;bootm'
DM355 EVM # setenv mfshost 00:0c:29:57:09:11
DM355 EVM # setenv rootpath /home/saadia/workdir/filesys
DM355 EVM # setenv bootargs 'console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/de
DM355 EVM # boot

Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000

** Bad Magic Number 0x1010101 **
## Booting image at 80700000 ...
Bad Magic Number

 

Can you tell me whats wrong?

  • 0
    TI__Mastermind 41665 points

    Bad magic number means that U-Boot tried to load and run the kernel uImage however the uImage was corrupted (magic number refers to a sort of key value in the image that validates it as being a real uImage), likely due to not loading from the proper place or loading somewhere it should not be loaded to. In this case my first thought is your bootcmd variable, you have 0x8700000 where it should be 0x80700000.

  • 0 in reply to Bernie Thompson TI
    Intellectual 640 points

     this is MT29F16G08FAA device
    UBL: detected valid U-Boot magic number
    UBL: booting to U-Boot


    U-Boot 1.2.0 (Oct 17 2007 - 15:38:02)

    DRAM:  128 MB
    NAND:  NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)
    Bad block table found at page 524224, version 0x01
    Bad block table found at page 524160, version 0x01
    nand_read_bbt: Bad block at 0x01fa0000
    nand_read_bbt: Bad block at 0x282c0000
    nand_read_bbt: Bad block at 0x2f600000
    nand_read_bbt: Bad block at 0x30a80000
    nand_read_bbt: Bad block at 0x33ce0000
    nand_read_bbt: Bad block at 0x33f80000
    nand_read_bbt: Bad block at 0x3a5c0000
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)
    Bad block table found at page 524224, version 0x01
    Bad block table found at page 524160, version 0x01
    nand_read_bbt: Bad block at 0x05cc0000
    nand_read_bbt: Bad block at 0x07060000
    nand_read_bbt: Bad block at 0x085e0000
    nand_read_bbt: Bad block at 0x211a0000
    nand_read_bbt: Bad block at 0x23780000
    nand_read_bbt: Bad block at 0x24480000
    nand_read_bbt: Bad block at 0x2e1e0000
    nand_read_bbt: Bad block at 0x37e00000
    nand_read_bbt: Bad block at 0x39260000
    2048 MiB
    In:    serial
    Out:   serial
    Err:   serial
    ARM Clock :- 216MHz
    DDR Clock :- 171MHz
    Hit any key to stop autoboot:  0

    Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
       Image Name:   Linux-2.6.10_mvl401
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1585240 Bytes =  1.5 MB
       Load Address: 80008000
       Entry Point:  80008000
    ## Booting image at 80700000 ...
       Image Name:   Linux-2.6.10_mvl401
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1585240 Bytes =  1.5 MB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    OK

    Starting kernel ...

    Uncompressing Linux.............................................................Linux version 2.6.10_mvl401 (a0270758@gtmatrix) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Wed Oct 17 15:44:12 EDT 2007
    CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    Machine: DaVinci DM355 EVM
    Memory policy: ECC disabled, Data cache writeback
    DM0350
    Built 1 zonelists
    Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev /nfs nfsroot=192.168.52.129:/home/saadia/workdir/filesys,nolock mem=116M
    PID hash table entries: 512 (order: 9, 8192 bytes)
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 116MB = 116MB total
    Memory: 114176KB available (2762K code, 585K data, 164K init)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: Testing write buffer coherency: ok
    spawn_desched_task(00000000)
    desched cpu_callback 3/00000000
    ksoftirqd started up.
    desched cpu_callback 2/00000000
    desched thread 0 started up.
    NET: Registered protocol family 16
    Registering platform device 'serial8250.0'. Parent at platform
    Registering platform device 'nand_davinci.0'. Parent at platform
    Registering platform device 'dm9000.0'. Parent at platform
    Registering platform device 'mmc.0'. Parent at platform
    Registering platform device 'mmc.1'. Parent at platform
    DaVinci I2C DEBUG: 15:42:09 Oct 17 2007
    Registering platform device 'i2c'. Parent at platform
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    musb_hdrc: version 2.2a/db-0.4.8 [pio] [host] [debug=0]
    Registering platform device 'musb_hdrc'. Parent at platform
    musb_hdrc: USB Host mode controller at c7800000 using PIO, IRQ 12
    musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:123 dm355_spi_board_init
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:129 REG BOARD  ret 0
    Registering platform device 'dm_spi.0'. Parent at platform
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:136 REGISTER DEVICE ret 0
    NetWinder Floating Point Emulator V0.97 (double precision)
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    yaffs Oct 17 2007 15:41:45 Installing.
    Initializing Cryptographic API
    Registering platform device 'dm355fb.0'. Parent at platform
    Console: switching to colour frame buffer device 90x30
    watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec
    Registering platform device 'davinci_pwm0.0'. Parent at platform
    Registering platform device 'davinci_pwm1.1'. Parent at platform
    Registering platform device 'davinci_pwm2.2'. Parent at platform
    Registering platform device 'davinci_pwm3.3'. Parent at platform
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    Registering platform device 'serial8250'. Parent at platform
    ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
    ttyS1 at MMIO 0x1c20400 (irq = 41) is a 16550A
    ttyS2 at MMIO 0x1e06000 (irq = 14) is a 16550A
    io scheduler noop registered
    io scheduler anticipatory registered
    RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
    loop: loaded (max 8 devices)
    dm9000 Ethernet Driver
    eth0: dm9000 at c7862000,c7864002 IRQ 45 MAC: 00:0e:99:02:c3:b0
    i2c /dev entries driver
    Linux video capture interface: v1.00
    Registering platform device 'vpfe.1'. Parent at platform
    vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded
    ipipe major#: 253, minor# 0
    Registering platform device 'dm355_ipipe.2'. Parent at platform
    ipipe driver registered
    af major#: 252, minor# 0
    Registering platform device 'dm355_af.2'. Parent at platform
    aew major#: 251, minor# 0
    Registering platform device 'dm355_aew.2'. Parent at platform
    elevator: using anticipatory as default io scheduler
    at25xxA_spi_eeprom init
    nand_davinci nand_davinci.0: Using 4-bit hardware ECC
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)
    2 NAND chips detected
    nand_bbt: ECC error while reading bad block table
    nand_bbt: ECC error while reading bad block table
    Creating 5 MTD partitions on "nand_davinci.0":
    0x00000000-0x003c0000 : "bootloader"
    0x003c0000-0x00400000 : "params"
    0x00400000-0x00800000 : "kernel"
    0x00800000-0x20800000 : "filesystem1"
    0x20800000-0x80000000 : "filesystem2"
    nand_davinci nand_davinci.0: hardware revision: 2.3
    scan_boardinfo:<NULL>:-1067850772
     modias <NULL> irq 2000000 max_speed 65535 bus_num 0 chip_select 0 mode -1068867824
    drivers/spi/spi.cat25xxA_spi_eeprom device register Succeeded
    dm_spi.0: dm355 SPI Controller driver at 0xc7866000 (irq = 42)
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.0:USB HID core driver
    mice: PS/2 mouse device common for all mice
    mmc mmc.0: Supporting 4-bit mode
    mmc mmc.0: Using DMA mode
    mmc mmc.1: Supporting 4-bit mode
    mmc mmc.1: Using DMA mode
    Registering platform device 'davinci-audio.0'. Parent at platform
    NET: Registered protocol family 2
    IP: routing cache hash table of 512 buckets, 4Kbytes
    TCP: Hash tables configured (established 8192 bind 16384)
    Initializing XFRM netlink socket
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    eth0: link down

     

    this is my log after the change of 80700000. I think something is wrong with my host linux...settings?

     

  • 0 in reply to saadia
    TI__Mastermind 41665 points

    It is strange that it ends with eth0: link down, usually I would expect some additional messages about it failing to mount the NFS. In any case it sounds like it is not able to start up the ethernet interface, when it gets to this point do the LEDs on the ethernet connector light up?

    I think your initial bootargs U-boot variable was cut off from the forums somehow, I think some is missing, there could be some typo or issue in there that may be leading to this. Looking at the rest of your arguments it looks like you have m in the place of n for nfshost, and what looks like a MAC address instead of an IP address, perhaps this is confusing the kernel.

  • 0 in reply to Bernie Thompson TI
    Intellectual 640 points

    Ok. So is  this the right NFS host address? HWaddr 00:0c:29:57:09:1. I mean it should be something like this right?

    Also is it only possible to connect to the host linux via ethernet cable or can i use RS232?

     

     

  • 0 in reply to saadia
    TI__Mastermind 41665 points

    The NFS host address should be the IP address of the host, something like 192.168.1.5, the address you are using looks like a MAC address, I doubt U-Boot will recognize it.

    Typically you would use an ethernet connection, I do not believe you can mount NFS over RS232, or at least that no one has written driver layers to do so that I know of, I have heard of it being done over USB by using a virtual network over USB however by far the most common and easiest is ethernet.

  • 0 in reply to saadia
    TI__Mastermind 37340 points

    Additionally, if you tried to NFS mount via UART or USB, you may need to modify u-boot (not easy effort).

  • 0 in reply to Juan Gonzales
    Intellectual 640 points

    Hi,

    I am using VMware player to run UBUNTU. Can that be the reason why my DVEVM is not booting from NFS?

    I am getting this see below:


    DM355 EVM # setenv bootcmd 'nboot 0x80700000 0 0x400000;bootm'
    DM355 EVM # setenv nfshost <161.131.7.61>
    DM355 EVM # setenv rootpath </home/saadia/workdir/filesys>
    DM355 EVM # setenv bootargs 'console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M'
    DM355 EVM # saveenv
    Saving Environment to NAND...
    Erasing Nand...Writing to Nand... done
    DM355 EVM # printenv
    bootdelay=3
    baudrate=115200
    bootfile="uImage"
    mfshost=00:0c:29:57:09:11
    nfs=192.168.52.129
    rootpaths=</home/saadia/workdir.filesys>
    stdin=serial
    stdout=serial
    stderr=serial
    videostd=pal
    bootcmd=nboot 0x80700000 0 0x400000;bootm
    nfshost=<161.131.7.61>
    rootpath=</home/saadia/workdir/filesys>
    bootargs=console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M

    Environment size: 443/16380 bytes
    DM355 EVM # boot

    Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
       Image Name:   Linux-2.6.10_mvl401
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1585240 Bytes =  1.5 MB
       Load Address: 80008000
       Entry Point:  80008000
    ## Booting image at 80700000 ...
       Image Name:   Linux-2.6.10_mvl401
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1585240 Bytes =  1.5 MB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    OK

    Starting kernel ...

    Linux version 2.6.10_mvl401 (a0270758@gtmatrix) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Wed Oct 17 15:44:12 EDT 2007
    CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    Machine: DaVinci DM355 EVM
    Memory policy: ECC disabled, Data cache writeback
    DM0350
    Built 1 zonelists
    Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=dhcp root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M
    PID hash table entries: 512 (order: 9, 8192 bytes)
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 116MB = 116MB total
    Memory: 114176KB available (2762K code, 585K data, 164K init)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: Testing write buffer coherency: ok
    spawn_desched_task(00000000)
    desched cpu_callback 3/00000000
    ksoftirqd started up.
    desched cpu_callback 2/00000000
    desched thread 0 started up.
    NET: Registered protocol family 16
    Registering platform device 'serial8250.0'. Parent at platform
    Registering platform device 'nand_davinci.0'. Parent at platform
    Registering platform device 'dm9000.0'. Parent at platform
    Registering platform device 'mmc.0'. Parent at platform
    Registering platform device 'mmc.1'. Parent at platform
    DaVinci I2C DEBUG: 15:42:09 Oct 17 2007
    Registering platform device 'i2c'. Parent at platform
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    musb_hdrc: version 2.2a/db-0.4.8 [pio] [host] [debug=0]
    Registering platform device 'musb_hdrc'. Parent at platform
    musb_hdrc: USB Host mode controller at c7800000 using PIO, IRQ 12
    musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:123 dm355_spi_board_init
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:129 REG BOARD  ret 0
    Registering platform device 'dm_spi.0'. Parent at platform
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:136 REGISTER DEVICE ret 0
    NetWinder Floating Point Emulator V0.97 (double precision)
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    yaffs Oct 17 2007 15:41:45 Installing.
    Initializing Cryptographic API
    Registering platform device 'dm355fb.0'. Parent at platform
    Console: switching to colour frame buffer device 90x30
    watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec
    Registering platform device 'davinci_pwm0.0'. Parent at platform
    Registering platform device 'davinci_pwm1.1'. Parent at platform
    Registering platform device 'davinci_pwm2.2'. Parent at platform
    Registering platform device 'davinci_pwm3.3'. Parent at platform
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    Registering platform device 'serial8250'. Parent at platform
    ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
    ttyS1 at MMIO 0x1c20400 (irq = 41) is a 16550A
    ttyS2 at MMIO 0x1e06000 (irq = 14) is a 16550A
    io scheduler noop registered
    io scheduler anticipatory registered
    RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
    loop: loaded (max 8 devices)
    dm9000 Ethernet Driver
    eth0: dm9000 at c7862000,c7864002 IRQ 45 MAC: 00:0e:99:02:c3:b0
    i2c /dev entries driver
    Linux video capture interface: v1.00
    Registering platform device 'vpfe.1'. Parent at platform
    vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded
    ipipe major#: 253, minor# 0
    Registering platform device 'dm355_ipipe.2'. Parent at platform
    ipipe driver registered
    af major#: 252, minor# 0
    Registering platform device 'dm355_af.2'. Parent at platform
    aew major#: 251, minor# 0
    Registering platform device 'dm355_aew.2'. Parent at platform
    elevator: using anticipatory as default io scheduler
    at25xxA_spi_eeprom init
    nand_davinci nand_davinci.0: Using 4-bit hardware ECC
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)
    2 NAND chips detected
    nand_bbt: ECC error while reading bad block table
    nand_bbt: ECC error while reading bad block table
    Creating 5 MTD partitions on "nand_davinci.0":
    0x00000000-0x003c0000 : "bootloader"
    0x003c0000-0x00400000 : "params"
    0x00400000-0x00800000 : "kernel"
    0x00800000-0x20800000 : "filesystem1"
    0x20800000-0x80000000 : "filesystem2"
    nand_davinci nand_davinci.0: hardware revision: 2.3
    scan_boardinfo:<NULL>:-1067850772
     modias <NULL> irq 2000000 max_speed 65535 bus_num 0 chip_select 0 mode -1068867824
    drivers/spi/spi.cat25xxA_spi_eeprom device register Succeeded
    dm_spi.0: dm355 SPI Controller driver at 0xc7866000 (irq = 42)
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.0:USB HID core driver
    mice: PS/2 mouse device common for all mice
    mmc mmc.0: Supporting 4-bit mode
    mmc mmc.0: Using DMA mode
    mmc mmc.1: Supporting 4-bit mode
    mmc mmc.1: Using DMA mode
    Registering platform device 'davinci-audio.0'. Parent at platform
    NET: Registered protocol family 2
    IP: routing cache hash table of 512 buckets, 4Kbytes
    TCP: Hash tables configured (established 8192 bind 16384)
    Initializing XFRM netlink socket
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    eth0: link down
    Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
    ..<7>eth0: no IPv6 routers present
    ... timed out!

     

    Can anyone suggest on what to do.

    Cheers!

  • 0 in reply to saadia
    TI__Guru 64490 points

    saadia: Thank you for the log and u-boot environment settings.  This is helpful.

    Based on the end of your serial console log from the DM355 EVM, an ethernet connection with an IP address has not bee made yet.  In order for a NFS mount to occur, the DM355 EVM has to be issued an IP address.
    Currently, with the below, the DM355 is trying to establish an IP address through DHCP, which means your VMWare running Ubuntu needs to have a DHCP server running on it.  Either it doesn't, or at the very least the service
    is not running.

    saadia said:

    NET: Registered protocol family 2
    IP: routing cache hash table of 512 buckets, 4Kbytes
    TCP: Hash tables configured (established 8192 bind 16384)
    Initializing XFRM netlink socket
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    eth0: link down
    Sending DHCP requests .<6>eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
    ..<7>eth0: no IPv6 routers present
    ... timed out!

    There are a couple of ways to quickly identify this.

    1) Setup your DM355 EVM with a static IP address by changing the bootargs with ip=<whatever IP address is on the same subnet as your VMWare ubuntu>
    Assuming the VMWare ubuntu's IP address is 161.131.7.61

    setenv bootargs 'console=ttyS0,115200n8 noinitrd rw ip=161.131.7.100 root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M'

    2) Start a DHCP server on the VMWare ubuntu.

  • 0 in reply to BrandonAzbell
    Intellectual 640 points

    thanks for the info.

    I have checked the DHCP subnet address from the Vmware network which appears to be 192.168.11.0.

    When type /sbin/ifconfig i get eth0 ip address as : 161.131.7.61.

    So i have changed the bootargs to this:setenv bootargs 'console=ttyS0,115200n8 noinitrd rw ip=192.168.11.0 root=/dev/nfs/ nfsroot=$(nfshost):$(rootpath),nolock mem=116M'.

    After that I save it by typing 'saveenv'. Before booting up I start the DHCP server on the Vmware by selecting the Virtual network editor from windows and selecting DHCP tab and clicking onto START tab.

    I get this see below:

    IP-Config: Auto-configuration of network failed.
    Root-NFS: No NFS server available, giving up.
    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
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

     

    Now whats wrong?

  • 0 in reply to saadia
    Intellectual 640 points

    forgot to mention that before this I typed setenv nfshost <161.131.7.61>

  • 0 in reply to saadia
    TI__Mastermind 37340 points

    Saadia,

    1) Just to make sure your EVM can see the host, can you try pinging the host PC from your EVM u-boot prompt (use host address returned from 'ifconfig')?  If you cannot do this, then we need to get passed this issue first.

    2) Also, you can refer to the following App Note for setting up your environment using static IPs; it was written from DM6446 EVM point of view, but should apply to DM355 as well.

    http://focus.ti.com/lit/an/spraaq0/spraaq0.pdf

  • 0 in reply to Juan Gonzales
    Intellectual 640 points

    I have tried pinging and it comes as not alive!

    I think my EVM is not able to find the ubuntu?

    Can anyone suggest?

  • 0 in reply to Juan Gonzales
    Intellectual 640 points

    I have read the App note given above and set up according to it....but I still cant NFS mounted on EVM...vheck my log below:

    DM355 EVM # setenv serverip 192.168.1.40
    DM355 EVM # setenv ipaddr 192.168.1.41
    DM355 EVM # setenv gateway 192.168.1.1
    DM355 EVM # setenv netmask 255.255.255.0
    DM355 EVM # setenv dns1 192.168.1.2
    DM355 EVM # setenv dns2 192.168.1.3
    DM355 EVM # setenv ethaddr 00:0c:29:57:09:11
    DM355 EVM # setenv rootpath /home/saadia/workdir/filesys
    DM355 EVM # setenv bootargs 'console=ttyS0,115200n8 noinitrd rw ip=192.168.1.41:                                                                             192.168.1.40:192.168.1.1:255.255.255.0:::off root=/dev/nfs nfsroot=192.168.1.40:                                                                             /home/saadia/workdir/filesys,nolock mem=116M'
    DM355 EVM # saveenv
    Saving Environment to NAND...
    Erasing Nand...Writing to Nand... done
    DM355 EVM # printenv
    bootdelay=3
    baudrate=115200
    bootfile="uImage"
    mfshost=00:0c:29:57:09:11
    nfs=192.168.52.129
    rootpaths=</home/saadia/workdir.filesys>
    bootards=console=ttyS0,115200n8 noinitrd rw ip=192.168.11.0 root=/dev/nfs nfsroot=$(nfshost):$(rootpath),nolock mem=116M
    bootcmd=nboot 0x80700000 0 0x400000;bootm
    nfshost=<192.168.1.40>
    stdin=serial
    stdout=serial
    stderr=serial
    videostd=pal
    serverip=192.168.1.40
    ipaddr=192.168.1.41
    gateway=192.168.1.1
    netmask=255.255.255.0
    dns1=192.168.1.2
    dns2=192.168.1.3
    ethaddr=00:0c:29:57:09:11
    rootpath=/home/saadia/workdir/filesys
    bootargs=console=ttyS0,115200n8 noinitrd rw ip=192.168.1.41:192.168.1.40:192.168.1.1:255.255.255.0:::off root=/dev/nfs nfsroot=192.168.1.40:/home/saadia/workdir/filesys,nolock mem=116M

    Environment size: 778/16380 bytes
    DM355 EVM # boot

    Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
       Image Name:   Linux-2.6.10_mvl401
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1585240 Bytes =  1.5 MB
       Load Address: 80008000
       Entry Point:  80008000
    ## Booting image at 80700000 ...
       Image Name:   Linux-2.6.10_mvl401
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1585240 Bytes =  1.5 MB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
    OK

    Starting kernel ...

    Linux version 2.6.10_mvl401 (a0270758@gtmatrix) (gcc version 3.4.3 (MontaVista 3.4.3-25.0.104.0600975 2006-07-06)) #1 Wed Oct 17 15:44:12 EDT 2007
    CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
    Machine: DaVinci DM355 EVM
    Memory policy: ECC disabled, Data cache writeback
    DM0350
    Built 1 zonelists
    Kernel command line: console=ttyS0,115200n8 noinitrd rw ip=192.168.1.41:192.168.1.40:192.168.1.1:255.255.255.0:::off root=/dev/nfs nfsroot=192.168.1.40:/home/saadia/workdir/filesys,nolock mem=116M
    PID hash table entries: 512 (order: 9, 8192 bytes)
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 116MB = 116MB total
    Memory: 114176KB available (2762K code, 585K data, 164K init)
    Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
    CPU: Testing write buffer coherency: ok
    spawn_desched_task(00000000)
    desched cpu_callback 3/00000000
    ksoftirqd started up.
    desched cpu_callback 2/00000000
    desched thread 0 started up.
    NET: Registered protocol family 16
    Registering platform device 'serial8250.0'. Parent at platform
    Registering platform device 'nand_davinci.0'. Parent at platform
    Registering platform device 'dm9000.0'. Parent at platform
    Registering platform device 'mmc.0'. Parent at platform
    Registering platform device 'mmc.1'. Parent at platform
    DaVinci I2C DEBUG: 15:42:09 Oct 17 2007
    Registering platform device 'i2c'. Parent at platform
    SCSI subsystem initialized
    usbcore: registered new driver usbfs
    usbcore: registered new driver hub
    musb_hdrc: version 2.2a/db-0.4.8 [pio] [host] [debug=0]
    Registering platform device 'musb_hdrc'. Parent at platform
    musb_hdrc: USB Host mode controller at c7800000 using PIO, IRQ 12
    musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:123 dm355_spi_board_init
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:129 REG BOARD  ret 0
    Registering platform device 'dm_spi.0'. Parent at platform
    arch/arm/mach-davinci/spi_platform_init.c:dm355_spi_board_init:136 REGISTER DEVICE ret 0
    NetWinder Floating Point Emulator V0.97 (double precision)
    JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
    yaffs Oct 17 2007 15:41:45 Installing.
    Initializing Cryptographic API
    Registering platform device 'dm355fb.0'. Parent at platform
    Console: switching to colour frame buffer device 90x30
    watchdog: TI DaVinci Watchdog Timer: timer margin 64 sec
    Registering platform device 'davinci_pwm0.0'. Parent at platform
    Registering platform device 'davinci_pwm1.1'. Parent at platform
    Registering platform device 'davinci_pwm2.2'. Parent at platform
    Registering platform device 'davinci_pwm3.3'. Parent at platform
    Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
    Registering platform device 'serial8250'. Parent at platform
    ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
    ttyS1 at MMIO 0x1c20400 (irq = 41) is a 16550A
    ttyS2 at MMIO 0x1e06000 (irq = 14) is a 16550A
    io scheduler noop registered
    io scheduler anticipatory registered
    RAMDISK driver initialized: 1 RAM disks of 32768K size 1024 blocksize
    loop: loaded (max 8 devices)
    dm9000 Ethernet Driver
    eth0: dm9000 at c7862000,c7864002 IRQ 45 MAC: 00:0e:99:02:c3:b0
    i2c /dev entries driver
    Linux video capture interface: v1.00
    Registering platform device 'vpfe.1'. Parent at platform
    vpfe vpfe.1: DaVinci v4l2 capture driver V1.0 loaded
    ipipe major#: 253, minor# 0
    Registering platform device 'dm355_ipipe.2'. Parent at platform
    ipipe driver registered
    af major#: 252, minor# 0
    Registering platform device 'dm355_af.2'. Parent at platform
    aew major#: 251, minor# 0
    Registering platform device 'dm355_aew.2'. Parent at platform
    elevator: using anticipatory as default io scheduler
    at25xxA_spi_eeprom init
    nand_davinci nand_davinci.0: Using 4-bit hardware ECC
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)
    2 NAND chips detected
    nand_bbt: ECC error while reading bad block table
    nand_bbt: ECC error while reading bad block table
    Creating 5 MTD partitions on "nand_davinci.0":
    0x00000000-0x003c0000 : "bootloader"
    0x003c0000-0x00400000 : "params"
    0x00400000-0x00800000 : "kernel"
    0x00800000-0x20800000 : "filesystem1"
    0x20800000-0x80000000 : "filesystem2"
    nand_davinci nand_davinci.0: hardware revision: 2.3
    scan_boardinfo:<NULL>:-1067858964
     modias <NULL> irq 2000000 max_speed 65535 bus_num 0 chip_select 0 mode -1068867824
    drivers/spi/spi.cat25xxA_spi_eeprom device register Succeeded
    dm_spi.0: dm355 SPI Controller driver at 0xc7866000 (irq = 42)
    Initializing USB Mass Storage driver...
    usbcore: registered new driver usb-storage
    USB Mass Storage support registered.
    usbcore: registered new driver usbhid
    drivers/usb/input/hid-core.c: v2.0:USB HID core driver
    mice: PS/2 mouse device common for all mice
    mmc mmc.0: Supporting 4-bit mode
    mmc mmc.0: Using DMA mode
    mmc mmc.1: Supporting 4-bit mode
    mmc mmc.1: Using DMA mode
    Registering platform device 'davinci-audio.0'. Parent at platform
    NET: Registered protocol family 2
    IP: routing cache hash table of 512 buckets, 4Kbytes
    TCP: Hash tables configured (established 8192 bind 16384)
    Initializing XFRM netlink socket
    NET: Registered protocol family 1
    NET: Registered protocol family 10
    IPv6 over IPv4 tunneling driver
    NET: Registered protocol family 17
    eth0: link down
    IP-Config: Complete:
          device=eth0, addr=192.168.1.41, mask=255.255.255.0, gw=192.168.1.1,
         host=192.168.1.41, domain=, nis-domain=(none),
         bootserver=192.168.1.40, rootserver=192.168.1.40, rootpath=
    Looking up port of RPC 100003/2 on 192.168.1.40
    eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
    portmap: server 192.168.1.40 not responding, timed out
    Root-NFS: Unable to get nfsd port number from server, using default
    Looking up port of RPC 100005/1 on 192.168.1.40
    portmap: server 192.168.1.40 not responding, timed out
    Root-NFS: Unable to get mountd port number from server, using default

  • 0 in reply to saadia
    TI__Mastermind 37340 points

    saadia,

    The fact that you cannot ping your host machine tells us there is something wrong with the network setup and therefore I would expect NFS to fail.

    Can you describe your network setup?  Are you connecting directly to EVM or going thru a router?  If directly, are you using a cross-over cable (some newer pc/laptops may not require this)?  Another thing to consider is that ubuntu may not have all the right network services enabled by default, but I have worked with a few customers using ubuntu, so I know it is possible.  I think we need to resolve this ping issue first, before attempting to NFS mount.

  • 0 in reply to Juan Gonzales
    Intellectual 640 points

    I have connected the EVM board with the ethernet cable directly to my PC. My PC runs Windows XP and I am using VMware Player to run UBUNTU 8.06.

     

  • 0 in reply to saadia
    TI__Guru 64490 points

    I would suggest we strip the setup down to the bare minimum to test the network connection.  I would not have VMWare Player running to test the bare minimum setup.

    In the setup you mention above, PC running Windows XP connected directly to EVM via ethernet cable, you will need to configure Windows XP for a static IP address.
    Using the EVM console, you will need to configure u-boot to use a static IP address as well, on the same subnet.
    Then, within the u-boot console, ping the Windows Machine.

    If this is successful, then you can start to add layers back into the mix, to determine where the issue is.
    An example would be to connect the Windows Machine back into your network and the EVM into that network, hopefully through an ethernet hub which is serving both devices.

  • 0 in reply to Juan Gonzales
    Intellectual 470 points

    I have Virtual Box on Windows XP and Ubuntu 10 as guest OS.  I set Virtual Box network as bridge.  The DHCP server is at 192.168.2.1.  NFS server is on Ubuntu virtual machine which has DHCP assigned IP 192.168.2.100.  I setup the 6467T EVM bootargs to have ip=dhcp.  The Linux kernel was uncompressed OK.  Then I saw DHCP request, and the evm board IP was set.  Then there were requests for RPC port, and these requests failed.  The root file system could not be mounted...  According to some of the posts, the problem might related to network security.  I tried to follow the above document to set up static IPs ip=192.168.2.133:192.168.2.100:192.168.2.1:::off.  However, the board still behaved the same way:  it requested for DHCP and ran to the same problem with RPC port request. 

    What do I need to do to use NFS file system?  Thank you.

     

  • 0 in reply to th
    Intellectual 355 points

    I hope you have already setup the nfs-server on your ubuntu 10.04 guest OS.

    Steps to do this is as mentioned at:

    http://www.ubuntugeek.com/nfs-server-and-client-configuration-in-ubuntu.html

    Are you able to get connected to your network from guest OS? Also update the exports file to export the rootfs directory. Also could you send the boot log for further analysis?

    Regards,

    Suhas Jain

    Sr. Associate,

    www.mavensystems.com

     

  • 0 in reply to Suhas Jain
    Intellectual 470 points

    I got it to work.  Thank you.