Hi

I took a look at the messages at the end of the uClinux boot log and
noticed that the "ifconfig" and "route" commands are not found by the
rc script. Might this be because the initrd is missing these files. The
sequence in the README.or32 file builds the filesystem *after* the
uClinux build so the "linux" image will have an old initrd in it. This
does not seem to me like a good test.

An earlier post did have some correct instructions, although I am not
sure why uClinux needs building twice.

I have built a filesystem with all the userland programmes
(init,sh,ifconfig,route and ping). [BTW The ext2fs is not big enough to
hold all this.] All is OK but I would like to, at least, be able to:
ping 127.0.0.1 and get a successful result. I have not yet worked out
what is needed (setup the loopback interface in ifconfig and add a route
for it) as the simulator/kernel hangs when I issue a second ifconfig.

I am currently working out how to get GDB working with or2ksim. Right
now the JTAG server is not starting even with debug=1.

I have more thoughts and comments but thats enough for one post...

- Dyson

----- Original Message ----- From: dyson.wilkes@iee.org> To: openrisc@opencores.org> Sent: Monday, February 02, 2004 12:28 PM Subject: [openrisc] ATS messages for uClinux boot

These two files are not part of the ramdisk used in this particular case.
ATS is not using the "network" ramdisk that has those files. Ignore this
error.

regards,
Damjan

* dyson.wilkes@iee.org (dyson.wilkes@iee.org) wrote: try with --srv do you have a recent or1ksim, since i thnik this was fixed recently. regards, p.