• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 114 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.

TDA4VEN-Q1: J722S tiny-rootfs problem

cesar.xu
Intellectual 370 points
Part Number: TDA4VEN-Q1

Tool/software:

Hi,

sdk version: 11.0

1. tisdk-adas-image-j722s-evm.rootfs.tar.xz, it can Mount nfs using rootfs,

   but use tisdk-tiny-image-j722s-evm.rootfs.tar.xz  mount failed

root@j722s-evm:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 58:A1:5F:C1:D6:A0
          inet addr:192.168.0.62  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::5aa1:5fff:fec1:d6a0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4505 errors:0 dropped:954 overruns:0 frame:0
          TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:595890 (581.9 KiB)  TX bytes:4330 (4.2 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@j722s-evm:~# ping 192.168.0.100
PING 192.168.0.100 (192.168.0.100): 56 data bytes
64 bytes from 192.168.0.100: seq=0 ttl=64 time=0.289 ms
64 bytes from 192.168.0.100: seq=1 ttl=64 time=0.230 ms
64 bytes from 192.168.0.100: seq=2 ttl=64 time=0.170 ms
^C
--- 192.168.0.100 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.170/0.229/0.289 ms
root@j722s-evm:~# mount -t nfs -o nolock 192.168.0.100:/home/cesar/work/nfs /mnt
mount: /mnt: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.
       dmesg(1) may have more information after failed mount system call.

Regards,

Cesar

  • 0
    TI__Guru**** 163100 points

    Cesar,

    Tiny FS is for a minimal boot. There are no modules loaded in the case of tiny rootfs. Most likely the failure is due to a dependency on one of the modules that get loaded in the case of full fledged tisdk Vs no modules on tinyFS.

    - Keerthy

  • 0 in reply to Keerthy J
    Intellectual 370 points

    Hi Keerthy,

    All the modules have been loaded. Could you please test them as well? We need to use this rootfs

    Regards,

    Cesar

  • 0 in reply to cesar.xu
    TI__Guru**** 163100 points

    Hello Cesar,

    mount -t nfs -o nolock 192.168.0.100:/home/cesar/work/nfs /mnt
    mount: /mnt: bad option; for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount.<type> helper program.
    dmesg(1) may have more information after failed mount system call.

    The minimal file system does not have the libraries needed. /sbin/mount is missing. You can try copying all the /sbin/* from full fledged file system to tiny.
    You will have trial and check as there can be multiple dependencies.

    - Keerthy

  • 0 in reply to Keerthy J
    Intellectual 370 points

    Hi Keerthy,

    This tiny has this bug. You should also test, verify and fix it. I'm trying to do it here.

    But I will encounter many more problems later, please also test it

    Regards,

    Cesar

  • 0 in reply to cesar.xu
    TI__Guru**** 163100 points

    Cesar,

    cesar.xu said:

    This tiny has this bug. You should also test, verify and fix it. I'm trying to do it here.

    But I will encounter many more problems later, please also test it

    tiny is not really meant for complete functionality. That is the very reason we have complete file system.

    - Keerthy