[okl4-developer] OKLinux on x86

[Henning Schild]

Am Tue, 11 Nov 2008 06:40:48 +1100
schrieb Geoffrey Lee <glee at ok-labs.com>:

> I have booted 2.1 on hardware before, so that should work.  Do I
> understand correctly that you have also tried to run it under the 
> QEMU emulator as well and it works under QEMU?  If you did succeed 
> in getting it running on QEMU, is the image that you run on QEMU 
> identical to the image that you run on hardware, including the root
> filesystem settings?  How did you setup your hardware to boot OKL4?  
> Since you did actually manage to get some output on hardware I think 
> it's probably OK but I'd just like to make sure anyway.  Finally,
> which toolchain are you using to build your software?

I bootet all three releases on Qemu and on Hardware. All of them
only worked on Qemu.
For Qemu i used build/images/c.img and for Hardware i used grub with a
config similar to build/images/grub/menu.lst. My only change to that
config is the location of image.elf. And i am using a different version
of grub, but that should not be a problem. As you said, it should fail
earlier if it was a bootloader problem.
All images where built with the latest toolchain available:
http://www.ertos.nicta.com.au/downloads/tools/arm-linux-3.4.4.tar.gz

In my first tries i patched tools/build.py to use "python" (2.5.2
on my system) instead of "python2.4". Then i used a machine with
python2.4 to build the releases. As i expected the problem is not
related to the version of python. I could built all releases with a
recent version of python, maybe you can drop the dependency for the old
version some day.

> It might be a good idea at this point to break into the debugger
> (Ctrl-k).  Once you are in the debugger, you can turn on tracepoints.
> Hit r for the tracepoint menu then E to turn on tracepoints, then
> you can enable all tracepoints or just some specific ones (hit ? for
> help).  That'll tell you what the system is doing.

It tells what the system is doing. Before i go on reading code or docs
i will post the nonzero values maybe someone has an idea. This are the
values of OKLinux hanging several minutes:

> 11   INTERRUPT                     n      n    17847 
> 12   IPC_TRANSFER                  n      n      127 
> 22   SYSCALL_INTERRUPT_CONTROL     n      n    17847 
> 23   SYSCALL_IPC                   n      n    53789 
> 35   TIMESLICE_EXPIRED             n      n       57 

Henning