Problems booting from an NFS server with U-boot in a AM1705 custom board
Hello,
First of all, my board has the following hardware:
SPI Flash : K0XMFI011 (Spansion) - 4MBytes - Connected to SPI0
Nand Flash: S34ML01G200TFI000 (Spansion) - 128MBytes - Connected to EMIFA
SDR SDRAM : AS4C16M16SA (Alliance Memory) - 32MBytes - Connected to EMIFB - Only one RAM chip
Ethernet : LAN8720a
Audio : TLV320AIC3106
Power : TPS65023
Important : I'm using UART1 for the console. This is for U-boot and Linux as well.
I have modified and recompiled U-boot and the Kernel to be able to use UART1 instead of UART0.
So far U-boot runs well with UART1 as console. Linux also runs OK when using the ramdisk http://arago-project.org/files/releases/2009.11/images/arago/arago-base-image-arago.ext2.gz
However the problems begin, when I try to boot from an NFS server.
I mounted a NFS server and tested it from another computer to be sure that it is ok. I have tried 4 different file systems where the only one that shows "more output" (lines in gray shwon below) in the terminal is from this link:
http://arago-project.org/files/releases/2009.11/images/arago/arago-base-image-arago.tar.gz
The last lines shown before the terminal shows no more information are the following:
udevd (489): /proc/489/oom_adj is deprecated, please use /proc/489/oom_score_adj instead.
udev: starting version 141
udevd[489]: inotify_add_watch(3, (null), 10) failed: Bad address
modprobe: FATAL: Could not load /lib/modules/3.3.0/modules.dep: No such file or directory
modprobe: FATAL: Could not load /lib/modules/3.3.0/modules.dep: No such file or directory
modprobe: FATAL: Could not load /lib/modules/3.3.0/modules.dep: No such file or directory
STAYS HERE FOREVER
When pinging the board from another computer, I can see that it is alive so the kernel must be still running.
Another interesting test is the one when disconnecting the ethernet cable, it shows the following activity: (so the kernel is definitely running)
nfs: server 192.168.0.27 not responding, still trying
nfs: server 192.168.0.27 not responding, still trying
nfs: server 192.168.0.27 OK
nfs: server 192.168.0.27 OK
Could this be a console configuration problem since I'm using UART1 instead of the default one UART0? I know that Linux is correctly builded to use UART1 (because it worked with the ramdisk).
Maybe when the filesystem gets loaded, some configuration file could be overwriting the configurations. But why then when using the ramdisk there is no problem? (assuming that both links shown above are the same file system only in different format) What do you think?
If you think that some file should be modified in the filesystem, where should I look?
My inittab, terminal log and U-boot environment vars are attached.
Thank you very much for your help
Best regards,
Patricio
(Please visit the site to view this file)
(Please visit the site to view this file)
(Please visit the site to view this file)