RE: ml507 initrd problem

Morning John,

 

Thanks for the tip.  Running said ramdisk things certainly look lively, I’ll add a list of opens that I see at boot up at the bottom of this email.  Looks like it’s opening a shell and everything and yet I see no serial communication from the shell, just quiet.  Am I correct to expect the console to be the serial port (9pin DB) on the ml507 board at 9600 baud?  Also, if you could spare a desperate person a moment, could you send me the boot command line that you use for testing with the ramdisk?  Finally, another member of this form suggested that there is a fully build BSP (rootfs and all) available as ‘linux_support.tar.gz’ on the Xilinx site.  Are you familiar with this?  I tried locating it a few days ago to no avail.

 

Thanks very much for your help!

Stu

 

Freeing unused kernel memory: 144k init

open /dev/console

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bfdb9f00

open /lib/libcrypt.so.0

open /lib/libm.so.0

open /lib/libc.so.0

open /dev/console

open /dev/console

open /etc/TZ

open /etc/inittab

open /dev/console

open /etc/TZ

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bfd65eb0

open /lib/libcrypt.so.0

open /lib/libm.so.0

open /lib/libc.so.0

open /etc/rc.sh

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bfef2ea0

open /lib/libcrypt.so.0

open /lib/libm.so.0

open /lib/libc.so.0

open /etc/mtab

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bf9a8e90

open /lib/libcrypt.so.0

open /lib/libm.so.0

open /lib/libc.so.0

code 10000000 - 10039640, data 10039000 - 10039640, stack bfa47e70

open /lib/libm.so.0

open /lib/libcrypt.so.0

open /lib/libc.so.0

open /dev/null

open /tmp/xinetd.pid

open /etc/xinetd.conf

open /etc/xinetd.d

open /dev/console

open /etc/TZ

open /etc/xinetd.d/ftpd

open /dev/console

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bfda3ea0

open /etc/TZ

open /etc/TZ

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bf9c5ec0

open /etc/passwd

open /etc/xinetd.d/telnet

open /lib/libcrypt.so.0

open /etc/TZ

open /lib/libm.so.0

open /lib/libcrypt.so.0

open /etc/passwd

open /lib/libc.so.0

open /lib/libm.so.0

open /etc/protocols

open /bin/application

open /lib/libc.so.0

open /etc/services

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bffa9ea0

open .profile

open /etc/services

open /etc/profile

open /etc/protocols

open /etc/passwd

open /etc/services

open /lib/libcrypt.so.0

open /etc/services

open /lib/libm.so.0

open /etc/TZ

open /lib/libc.so.0

open /etc/TZ

code 10000000 - 1009c134, data 1009a128 - 1009c134, stack bfaa5eb0

open /lib/libcrypt.so.0

open /lib/libm.so.0

open /lib/libc.so.0

 

 

 

 

Hi Stu,

 

I realize you are trying to get your own ram disk to work, but if you want to get a baseline you can use one we have on our wiki site, at http://xilinx.wikidot.com/open-source-linux, under Files To Download.  This is the same ram disk that is included in the ELDK.

 

This is the ram disk that I use to test the ML507 design in our Git tree.  I also use NFS a lot for testing.

 

Looks like you’re close with yours, but I’m certainly no expert in that area as I typically have something that works and don’t change it.

 

Good luck,

John

 

This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.