x

Abhishek B

Prodigy 35 points

Other Parts Discussed in Thread: AM3517

over 15 years ago

0 Frank Walzer over 15 years ago

TI__Mastermind 44306 points

Abhishek,

I would say that your bootargs settings are wrong.

This

/tftpboot/$(nfshost):$(rootpath)

looks like you want to set it using u-boot variables but something got wrong. Maybe you switched to a new u-boot which is using ${var} syntax?

Regards

0 Arindam Halder over 15 years ago in reply to Frank Walzer

Prodigy 30 points

Try to use bellow bootargs commands

setenv bootargs 'mem=80M console=ttyS0,115200n8 noinitrd rw ip="your board ip add" root=/dev/nfs nfsroot="your server ip":rootfs path,nolock '

setenv serverip your server ip

setenv bootfile kernel_image

setenv bootcmd 'tftpboot 0x80000000 kernel_image;bootm'

0 Jeff L over 15 years ago in reply to Arindam Halder

TI__Expert 5960 points

FYI - I believe AM3517 is using ttyS2 instead of ttyS0.

0 Frank Walzer over 15 years ago

TI__Mastermind 44306 points

Abhishek,

I suggest you do a printenv and paste this here.

Regards.

0 Frank Walzer over 15 years ago

TI__Mastermind 44306 points

Ok,

this is the changed version already, right? I can't see /tftpboot anymore.

Also I believe u-boot does not evaluate the variables in bootargs but just passes the string to the kernel. I usually have a variable that gets executed ('run') which sets bootargs. This variable may contain others but I assume your u-boot requires ${} as I mentioned before. There are examples in your setup. So try the different syntax or hard code the stuff into bootargs. Then it should work. Never forget the saveenv if you want to keep the environment permanent.

Regards.

0 Frank Walzer over 15 years ago

TI__Mastermind 44306 points

Then I don't get it. Either there is an additional u-boot script running (maybe from the SDcard) or you have some other problem. Usually the bootargs passed to the kernel are displayed in the log right after the kernel start. Maybe this can help.

Regards.

0 Prad over 15 years ago in reply to Frank Walzer

Expert 1125 points

Hi,

Did you solve the problem?

may be on the host you may want to edit /etc/hosts.allow to allow network access to the nfs server

and start the portmap and nfslock daemons. I hope below site could help you to solve problem with NFS.

http://wiki.archlinux.org/index.php/NFS

Regards.

Processors

Processors forum

x