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.

Trouble with mounting file system over NFS with PSP 3.22.0.02

Other Parts Discussed in Thread: OMAPL138, OMAP-L138, TCA6416, DA8XX, PMP, AM1808

Hi all,

I am working with PSP 3.22.0.02 on OMAPL138. Having trouble getting rootfs mount over NFS.

I have the NFS server set up on my Ubuntu development machine and I could the EVM to mount rootfs over NFS when using the DVSDK (ti-dvsdk_omapl138-evm_04_03_00_06)

But, I am moving to PSP 3.22.0.02, but having trouble mounting rootfs

I am referring to

http://processors.wiki.ti.com/index.php/GSG:_Setting_up_OMAP-L1/AM1x_Target_File_System

to get the rootfs. I am looking at the link in the section which talks about how to set up targetfs for PSP versions greater than 3.20.00.11

The board boots up (using tftpboot), but cannot find the NFS server. Wondering if there are any NFS version differences with the latest PSP which is causing trouble or if that rootfs from the above page is not the correct one for PSP version 3.22.0.02

Can you please let me know when you get a chance?

  • Cutting and pasting output from minicom below. At this point, even minicom commands do not respond. Neither does Ctrl-C/Ctrl-Z. Have to kill the terminal.

    **************************

    U-Boot > boot
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    DHCP client bound to address 10.203.190.149
    Using device
    TFTP from server 10.112.102.73; our IP address is 10.203.190.149; sending throug
    h gateway 10.203.128.1
    Filename 'uImage.3.22.02.02'.
    Load address: 0xc0700000
    Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ###################################################
    done
    Bytes transferred = 2585720 (277478 hex)
    ## Booting kernel from Legacy Image at c0700000 ...
    Image Name: Linux-3.3.0
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 2585656 Bytes = 2.5 MB
    Load Address: c0008000
    Entry Point: c0008000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK
    OK

    Starting kernel ...

    Uncompressing Linux... done, booting the kernel.
    Booting Linux on physical CPU 0
    Linux version 3.3.0 (rgsubr@ubuntu) (gcc version 4.3.3 (GCC) ) #1 PREEMPT Tue Oc
    t 9 18:50:27 PDT 2012
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    CPU: VIVT data cache, VIVT instruction cache
    Machine: DaVinci DA850/OMAP-L138/AM18x EVM
    Memory policy: ECC disabled, Data cache writeback
    BUG: mapping for 0x80000000 at 0xfffe0000 out of vmalloc space
    DaVinci da850/omap-l138/am18x variant 0x1
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 24320
    Kernel command line: console=ttyS2,115200n8 noinitrd rw mem=32M@0xc0000000 mem=6
    4M@0xc4000000 root=/dev/nfs nfsroot=10.112.102.73:/home/rgsubr/workspace/ti/arag
    ofs,nolock ip=dhcp
    PID hash table entries: 512 (order: -1, 2048 bytes)
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 32MB 64MB = 96MB total
    Memory: 91944k/91944k available, 6360k reserved, 0K highmem
    Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000 ( 4 kB)
    fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
    vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
    lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
    modules : 0xbf000000 - 0xc0000000 ( 16 MB)
    .text : 0xc0008000 - 0xc04cb000 (4876 kB)
    .init : 0xc04cb000 - 0xc04f8000 ( 180 kB)
    .data : 0xc04f8000 - 0xc0533ca0 ( 240 kB)
    .bss : 0xc0533cc4 - 0xc0551714 ( 119 kB)
    SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    NR_IRQS:245
    Console: colour dummy device 80x30
    Calibrating delay loop... 148.88 BogoMIPS (lpj=744448)
    pid_max: default: 32768 minimum: 301
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    Setting up static identity map for 0xc03a74f0 - 0xc03a7548
    gpiochip_add: registered GPIOs 0 to 31 on device: DaVinci
    gpiochip_add: registered GPIOs 32 to 63 on device: DaVinci
    gpiochip_add: registered GPIOs 64 to 95 on device: DaVinci
    gpiochip_add: registered GPIOs 96 to 127 on device: DaVinci
    gpiochip_add: registered GPIOs 128 to 143 on device: DaVinci
    DaVinci: 144 gpio irqs
    print_constraints: dummy:
    NET: Registered protocol family 16
    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
    print_constraints: VDCDC1: 3200 <--> 3300 mV at 3300 mV
    print_constraints: VDCDC2: 1750 <--> 3300 mV at 3300 mV
    print_constraints: VDCDC3: 950 <--> 1350 mV at 1200 mV
    print_constraints: LDO1: 1800 mV
    print_constraints: LDO2: 1150 <--> 1300 mV at 1200 mV
    pca953x 1-0020: failed reading register
    pca953x 1-0021: interrupt support not compiled in
    gpiochip_add: registered GPIOs 160 to 175 on device: tca6416
    i2c-gpio i2c-gpio.1: using pins 20 (SDA) and 21 (SCL)
    Advanced Linux Sound Architecture Driver Version 1.0.24.
    Switching to clocksource timer0_1
    musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
    musb-hdrc musb-hdrc: dma type: dma-cppi41
    MUSB255 controller's USBSS revision = 4ea11003
    Waiting for USB PHY clock good...
    musb-hdrc musb-hdrc: USB OTG mode controller at fee00000 using DMA, IRQ 58
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    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 named UNIX socket transport module.
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    EMAC: MII PHY configured, RMII PHY will not be functional
    JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
    msgmni has been set to 179
    io scheduler noop registered (default)
    da8xx_lcdc da8xx_lcdc.0: GLCD: Found Sharp_LK043T1DG01 panel
    Console: switching to colour frame buffer device 60x34
    Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
    serial8250.0: ttyS0 at MMIO 0x1c42000 (irq = 25) is a AR7
    serial8250.0: ttyS1 at MMIO 0x1d0c000 (irq = 53) is a AR7
    serial8250.0: ttyS2 at MMIO 0x1d0d000 (irq = 61) is a AR7
    console [ttyS2] enabled
    brd: module loaded
    ahci ahci: forcing PORTS_IMPL to 0x1
    ahci ahci: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci: flags: ncq sntf pm led clo only pmp pio slum part ccc
    scsi0 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x01e18000-0x01e19fff] port 0x100 irq 67
    spi_davinci spi_davinci.1: DMA: supported
    spi_davinci spi_davinci.1: DMA: RX channel: 18, TX channel: 19, event queue: 0
    m25p80 spi1.0: m25p64 (8192 Kbytes)
    Creating 6 MTD partitions on "m25p80":
    0x000000000000-0x000000010000 : "UBL"
    0x000000010000-0x000000090000 : "U-Boot"
    0x000000090000-0x0000000a0000 : "U-Boot-Env"
    0x0000000a0000-0x000000320000 : "Kernel"
    0x000000320000-0x000000720000 : "Filesystem"
    0x0000007f0000-0x000000800000 : "MAC-Address"
    Read MAC addr from SPI Flash: 00:08:ee:05:92:b2
    spi_davinci spi_davinci.1: Controller at 0xfef0e000
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.5
    davinci_mdio davinci_mdio.0: detected phy mask fffffffe
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[0]: device davinci_mdio-0:00, driver SMSC LAN87
    10/LAN8720
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    ohci ohci.0: DA8xx OHCI
    ohci ohci.0: new USB bus registered, assigned bus number 1
    Waiting for USB PHY clock good...
    ohci ohci.0: irq 59, io mem 0x01e25000
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    input: gpio-keys-polled as /devices/platform/gpio-keys-polled.1/input/input0
    input: TPS6507x Touchscreen as /devices/platform/i2c-gpio.1/i2c-1/1-0048/input/i
    nput1
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    omap_rtc: RTC power up reset detected
    i2c /dev entries driver
    lirc_dev: IR Remote Control driver registered, major 253
    ata1: SATA link down (SStatus 0 SControl 300)
    IR NEC protocol handler initialized
    IR RC5(x) protocol handler initialized
    IR RC6 protocol handler initialized
    IR JVC protocol handler initialized
    IR Sony protocol handler initialized
    IR RC5 (streamzap) protocol handler initialized
    IR SANYO protocol handler initialized
    IR MCE Keyboard/mouse protocol handler initialized
    IR LIRC bridge handler initialized
    Linux video capture interface: v2.00
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (1.1.1)
    watchdog watchdog: heartbeat 60 sec
    cpuidle: using governor ladder
    cpuidle: using governor menu
    davinci_mmc davinci_mmc.0: Using DMA, 4-bit mode
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    usbcore: registered new interface driver snd-usb-audio
    soc-audio soc-audio.0: ASoC: Failed to create card debugfs directory
    _regulator_get: 1-0018 supply IOVDD not found, using dummy regulator
    _regulator_get: 1-0018 supply DVDD not found, using dummy regulator
    _regulator_get: 1-0018 supply AVDD not found, using dummy regulator
    _regulator_get: 1-0018 supply DRVDD not found, using dummy regulator
    mmc0: new high speed SDHC card at address b368
    asoc: tlv320aic3x-hifi <-> davinci-mcasp.0 mapping ok
    mmcblk0: mmc0:b368 USD 3.75 GiB
    mmcblk0: p1 p2
    ALSA device list:
    #0: DA850/OMAP-L138 EVM
    TCP cubic registered
    NET: Registered protocol family 17
    regulator_init_complete: LDO2: incomplete constraints, leaving on
    regulator_init_complete: LDO1: incomplete constraints, leaving on
    regulator_init_complete: VDCDC3: incomplete constraints, leaving on
    regulator_init_complete: VDCDC2: incomplete constraints, leaving on
    regulator_init_complete: VDCDC1: incomplete constraints, leaving on
    console [netcon0] enabled
    netconsole: network logging started
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    davinci_mdio davinci_mdio.0: resetting idled controller
    net eth0: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=davinci_m
    dio-0:00, id=7c0f1)
    PHY: davinci_mdio-0:00 - Link is Up - 100/Full
    Sending DHCP requests ....., OK
    IP-Config: Got DHCP answer from 0.0.0.0, my address is 10.203.190.149
    IP-Config: Complete:
    device=eth0, addr=10.203.190.149, mask=255.255.192.0, gw=10.203.128.1,
    host=10.203.190.149, domain=dsv.eng.dolby.net, nis-domain=(none),
    bootserver=0.0.0.0, rootserver=10.112.102.73, rootpath=
    VFS: Mounted root (nfs filesystem) on device 0:13.
    Freeing init memory: 180K
    udevd (624): /proc/624/oom_adj is deprecated, please use /proc/624/oom_score_adj
    instead.
    udev: starting version 141
    udevd[624]: inotify_add_watch(3, (null), 10) failed: Bad address

    udevd[624]: inotify_add_watch(3, (null), 10) failed: Bad address

    udevd[624]: inotify_add_watch(3, (null), 10) failed: Bad address

    udevd[624]: inotify_add_watch(3, (null), 10) failed: Bad address

    modprobe: FATAL: Could not open 'kernel/fs/minix/minix.ko': No such file or dire
    ctory

    modprobe: FATAL: Could not open 'kernel/fs/minix/minix.ko': No such file or dire
    ctory

    modprobe: FATAL: Could not open 'kernel/fs/minix/minix.ko': No such file or dire
    ctory

    modprobe: FATAL: Could not open 'kernel/fs/minix/minix.ko': No such file or dire
    ctory

    EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional featu
    res (4)
    EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is rec
    ommended
    kjournald starting. Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): recovery complete
    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    nfs: server 10.112.102.73 not responding, still trying

  • Hi Raja,

    You can use the same file system - just do a make modules and make modules_install afterwards to the file system so Linux kernel 3.3.0 can find the right headers and modules.

  • Thank you Loc.

    I got an e-mail with an embedded reply which looked different. Don't know where it is gone as the page shows something different.

    Anyhow, I did like you suggested and did the modules_install with INSTALL_ROO_PATH pointing to the targetfs which worked previously with 2.6.37 kernel.

    Now, I can boot to the login level. But I do get some errors (after running depmod and rebooting). Cutting and pasting below. Not sure if any of this is problematic.

    I still cannot get the rootfs from the link I posted in my original message to work even after modules_install (actually I had already done that yesterday before posting this request). Where is the place where I can download the proper rootfs (asking this for future reference:-))

    *******************

    Please wait: booting...
    Starting udev
    udevd (638): /proc/638/oom_adj is deprecated, please use /proc/638/oom_score_adj
    instead.
    udev: starting version 141
    Root filesystem already rw, not remounting
    Caching udev devnodes
    Populating dev cacheVFS: Can't find a Minix filesystem V1 | V2 | V3 on device mm
    cblk0.
    FAT-fs (mmcblk0): bogus number of reserved sectors
    FAT-fs (mmcblk0): Can't find a valid FAT filesystem
    EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
    EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.
    cramfs: wrong magic
    FAT-fs (mmcblk0): bogus number of reserved sectors
    FAT-fs (mmcblk0): Can't find a valid FAT filesystem
    ISOFS: Unable to identify CD-ROM format.
    EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is rec
    ommended
    kjournald starting. Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    mv: cannot rename '/tmp/devices': No such file or directory
    NET: Registered protocol family 10
    logger: mount: mount point /proc/bus/usb does not exist
    ALSA: Restoring mixer settings...
    NOT configuring network interfaces: / is an NFS mount
    INIT: Entering runlevel: 5
    Starting system message bus: dbus.
    Starting Dropbear SSH server: dropbear.
    Starting telnet daemon.
    Starting network benchmark server: netserver.
    Starting syslogd/klogd: done
    Starting thttpd.
    FATAL: Module cmemk not found.
    FATAL: Module dsplinkk not found.
    FATAL: Module dm365mmap not found.
    BusyBox v1.13.2 (2011-12-23 12:39:34 IST) multi-call binary

    Usage: mknod [OPTIONS] NAME TYPE MAJOR MINOR

    Create a special file (block, character, or pipe)

    Options:
    -m Create the special file using the specified mode (default a=rw)
    TYPEs include:
    b: Make a block device
    c or u: Make a character device
    p: Make a named pipe (MAJOR and MINOR are ignored)


    _____ _____ _ _
    | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
    | | _| .'| . | . | | __| _| . | | | -_| _| _|
    |__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
    |___| |___|

    Arago Project http://arago-project.org arago ttyS2

    Arago 2011.06 arago ttyS2

    arago login:

  • Rootfs usually are set up for specific purpose besides the key requirements which is a busybox shell and support libraries compiled for the right ISA (in this case ARMv5). It is tailored to the flavor of the SDK. Some include stacks such as Qt, GStreaner, etc.

    For omap-l138 file system can come the SDKs (TI or 3Ps) e.g. OMAP-L138 or AM1808 at www.ti.com or built from scratch using the base file system recipe at http://arago-project.org/wiki/index.php/Setting_Up_Build_Environment 

    For errors: FAT-fs (mmcblk0): bogus number of reserved sectors

    FAT-fs (mmcblk0): Can't find a valid FAT filesystem
    EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.
    EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0

    Those are related to how the SD card was formatted and can be changed.

    FATAL: Module cmemk not found.
    FATAL: Module dsplinkk not found.
    FATAL: Module dm365mmap not found.

    These are related to a start up script (probably a demo) that expects those drivers at a certain location but did not find them. You can check the /etc/init.d/rc5.d to see if there's a demo script related to cmem, dsplink and dm365. Those lines can be removed.

  • Thank you very for your help Loc.

    I will read through the Arago page you sent to understand how setting up to build a rootfs works.

  • If you are so inclined to build your custom filesystem, you can try building one using the steps provided in the Arago Project page.  You can also simply and easily  create a new filesystem for your device at:

    http://www.angstrom-distribution.org/

    Click the Online Builder tab and make your appropriate selections.  You'll still have to make/build your Linux modules and install/copy them into your new filesystem.

  • Thank you very much Arnie.

    I suspect that we will tailor the filesystem to our needs eventually. So, it is very useful to have these instructions from you. Thank you again for your help.

    Cheers,

    -raja.