• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 99 subscribers
  • Views 506 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.

Shared file system for OMAP-L138

ben philip
Prodigy 130 points
Other Parts Discussed in Thread: OMAP-L138

Hello,

I am a student, and I am trying to start with the OMAP-L138 Experimenter Kit.

I am following the Wiki but I am stuck in exporting a shared file system for target access : http://processors.wiki.ti.com/index.php/GSG:_Setting_up_OMAP-L1_Target_File_System

There is this line at paragraph 4) : 

host $ cp -a /home/<useracct>/<target_name>/DaVinci-PSP-SDK-03.#.#.#/images/fs/nfs.tar.gz 

But when I am in the "images" directory, I can't find the "fs" directory. I looked everywhere whithout finding the nfs.tar.gz file.

Thank you in advance.

B.PHILIP

 

  • 0
    TI__Expert 4010 points

    Starting with release 3.20.00.11, the file system is no longer included in the PSP package.  You will need to download it seperately from the product download page.  I will update the GSG wiki to reflect this change.

  • 0 in reply to David Meixner
    Prodigy 130 points

    Thank you.

    About the product download page, I filled the page about the US Government Export Approval in order to download the ti_cgt_c6000_6.1.9_setup_linux_x86.bin file.

    I don't have any answer since 2 days, and I don't have any activation ID in order to download from TI's website.

    How can I get this software?

    Regards,

    Ben PHILIP

  • 0 in reply to ben philip
    Prodigy 130 points

    I would have another question. When I boot my OMAP-L138 EVM, I have this message : Root-NFS: Unable to get nfsd port number from server

    My NFS server is working locally, but it looks like it is not working with the EVM.

    I did the following settings : 

    ethaddr=00:08:ee:03:b1:9b

    ethact=

    nfshost=192.168.0.237

    serverip=192.168.0.237

    bootfile=uImage

    ipaddr=192.168.0.190

    bootcmd=tftp;bootm

    bootargs=console=ttyS2,115200n8 noinitrd rw ip=192.168.0.190 root=/dev/nfs nfsroot=192.168.0.237:/home/bp/workdir/filesys/,nolock mem=32M

    rootpath=/home/bp/workdir/filesys

    And here is the end of the boot : 

    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)

    eth0: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=1:00, id=7c0f1)

    IP-Config: Guessing netmask 255.255.255.0

    IP-Config: Complete:

         device=eth0, addr=192.168.0.190, mask=255.255.255.0, gw=255.255.255.255,

         host=192.168.0.190, domain=, nis-domain=(none),

         bootserver=255.255.255.255, rootserver=192.168.0.237, rootpath=

    Looking up port of RPC 100003/2 on 192.168.0.237

    PHY: 1:00 - Link is Up - 100/Full

    Root-NFS: Unable to get nfsd port number from server, using default

    Looking up port of RPC 100005/1 on 192.168.0.237

    Root-NFS: Unable to get mountd port number from server, using default

    Root-NFS: Server returned error -110 while mounting /home/bp/workdir/filesys/

    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             256 mtdblock0 (driver?)

    1f01              64 mtdblock1 (driver?)

    1f02            7808 mtdblock2 (driver?)

    1f03              64 mtdblock3 (driver?)

    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

    Backtrace:

    [<c0031730>] (dump_backtrace+0x0/0x114) from [<c0320420>] (dump_stack+0x18/0x1c)

     r7:00008000 r6:c1c13000 r5:c0025a08 r4:c0446f38

    [<c0320408>] (dump_stack+0x0/0x1c) from [<c0320488>] (panic+0x64/0x13c)

    [<c0320424>] (panic+0x0/0x13c) from [<c0008fec>] (mount_block_root+0x1e0/0x220)

     r3:00000001 r2:00000001 r1:c1c23f60 r0:c03b5856

    [<c0008e0c>] (mount_block_root+0x0/0x220) from [<c00090f0>] (mount_root+0xc4/0xfc)

     r8:00000000 r7:00000000 r6:00000000 r5:00000000 r4:00200000

    [<c000902c>] (mount_root+0x0/0xfc) from [<c0009298>] (prepare_namespace+0x170/0x1c8)

     r5:c0025a08 r4:c0446a20

    [<c0009128>] (prepare_namespace+0x0/0x1c8) from [<c00084c8>] (kernel_init+0xf0/0x12c)

     r5:00000000 r4:c04467e0

    [<c00083d8>] (kernel_init+0x0/0x12c) from [<c0045424>] (do_exit+0x0/0x6b4)

     r5:00000000 r4:00000000

    Thank you for your consideration

  • 0 in reply to ben philip
    TI__Mastermind 24340 points

    Hi ben,

    I never saw this specific error, so think maybe google might help with some light in the issue. :)

    But here are some hints:

    1) Double check steps 5 and 6 of the page:

    http://processors.wiki.ti.com/index.php/GSG:_Setting_up_OMAP-L1_Target_File_System#Exporting_a_Shared_File_System_for_Target_Access

    2) Check the firewall, please see this page:

    http://wiki.openmoko.org/wiki/Booting_from_NFS

    look at the GSG again and make sure you did not skip any step, it could be something specific to your network, etc.