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.
I know this info may not be helpful.
I met a similar problem, and got stuck on it for 2 days.
Then I just try anthoer Linux host B, the problem disappeared.
After that, I reinstalled my Linux image on host A and updated it, and then the problem get solved.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Jun_Zhang:
Could you please share the bootargs with us?
Are you able to run 'dhcp' at the u-boot prompt? Does it give you the correct ip address of your target & host?
Are you using a direct connection between your EVM & PC?
Make sure your host's "/etc/exports" has the correct NFS mount listed.
Be sure to disable your host firewall.
Thank You,Michael RisleyTexas Instruments
Could you please share the bootargs with us?
setenv bootargs 'mem=128M console=ttyO0,115200n8 root=/dev/nfs
In reply to Michael Risley:
i didn't run 'dhcp' at the u-boot prompt, i use static ip only
yes, EVM & PC is direct connection
if i boot board use filesystem in flash, after boot successfully, i can mount host folder to board.
must i boot under 'dhcp' when booting use filesystem by NFS ?
In reply to huang jack:
Hi huang huang
Please ensure your file system is under nfsroot=10.2.1.10:/BoardNFS and was set under nfs server.
I use DM8168, and my EZSDK is 5_02_xx_xx,
My bootcmd is like this "bootcmd=dhcp;setenv serverip 172.16.1.62;tftpboot;bootm", and my board works well.
In reply to Lei Wong:
the nfs filesystem is ok, since i can mount it after board boot successfully.
i use static ip not 'dhcp'.
would you try static ip for a test ?
How did you populate the BoardNFS directory? That directory may not be "bootable"...as it may not have all the special files and permissions. It may also not be owned by root. Usually you would untar a rootfs image onto that directory. Since you can mount the NFS directory, you could tar up your target rootfs and untar onto your mounted NFS directory. A plain recursive copy usually doesn't copy special file properly.
Hi huang huang,
Sorry for the late reply. Have you fixed your problem?
I tested my board using static ip, and it failed.
I set it just like this "setenv bootargs 'console=ttyO2,115200n8 rootwait rw mem=256M earlyprink notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=172.16.1.62:/home/xiaoxiao/targetfs2 ip=172.16.1.61:172.16.1.62:172.16.1.1:255.255.255.0:dm816x-evm:eth0:off'"
The booting message shows as below.
net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f013)
device=eth0, addr=172.16.1.61, mask=255.255.255.0, gw=172.16.1.1,
host=dm816x-evm, domain=, nis-domain=(none),
bootserver=172.16.1.62, rootserver=172.16.1.62, rootpath=
PHY: 0:01 - Link is Up - 1000/Full
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 8 mtdblock1 (driver?)
1f02 2560 mtdblock2 (driver?)
1f03 1272 mtdblock3 (driver?)
1f04 2432 mtdblock4 (driver?)
1f05 128 mtdblock5 (driver?)
1f06 4352 mtdblock6 (driver?)
1f07 204928 mtdblock7 (driver?)
1f08 50304 mtdblock8 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<c0046b44>] (dump_backtrace+0x0/0x110) from [<c0364b48>] (dump_stack+0x18/0x1c)
r7:cc813000 r6:00000000 r5:c002c014 r4:c04d9110
[<c0364b30>] (dump_stack+0x0/0x1c) from [<c0364bac>] (panic+0x60/0x17c)
[<c0364b4c>] (panic+0x0/0x17c) from [<c0009254>] (mount_block_root+0x1e0/0x220)
r3:00000000 r2:00000000 r1:cc82bf58 r0:c041a9dc
[<c0009074>] (mount_block_root+0x0/0x220) from [<c0009340>] (mount_root+0xac/0xc
[<c0009294>] (mount_root+0x0/0xcc) from [<c00094d0>] (prepare_namespace+0x170/0x
[<c0009360>] (prepare_namespace+0x0/0x1d4) from [<c0008784>] (kernel_init+0x114/
[<c0008670>] (kernel_init+0x0/0x154) from [<c006aeec>] (do_exit+0x0/0x5e4)
Sorry for the late reply, and thanks for your try. board still boot fail when using static IP. I'm waiting for the corresponding release SDK for my board.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.