[okl4-developer] help getting started

[Laborator SRCT]

Hi.

I'm currently trying to determin a good Linux OS base on which to bring up L4 on an ARM based machine. 

My initial attempts were to use the already available targets, based on the assumption that if everything works then I had reached a stable system on which I can change the scripts for my target hardware.

First I want to ask you what Linux distro is suitable (and with what added packages) to build an L4 binary and run image simulations (under skyeye).

Second, I want to ask if the example targets are tested to work or if there are pieces missing from the archive available on http://wiki.ok-labs.com/ .

PS: I can't figure the reason behind gumstix machine simulations, but I think the kzm_arm11 are due to mising files.

I started with Opensuse10.2 (gcc-4.1.2) on which I have added scons, arm-linux-gcc and skyeye from the Nicta site, python-2.4.4 (from python.org). This way, I got rid of the obvious build errors.

I started by running the existing targets and see what happens. I was expecting the scripts to automatically load a simulation into skyeye (like they did in the Nicta implemntation).

I typed:

#tools/build.py machine=gumstix project=iguana wombat=yes
#tools/build.py machine=gumstix project=iguana wombat=yes simulate

After the second command I get (in okl4 version 1.4.1.1):
load section vmlinux.con_initcall.init: lma = 0xa0e775c8 (vma = 0x012775c8)  size = 0x00000004.
not load section vmlinux.security_initcall.init: addr = 0x012775cc  size = 0x00000000 .
load section vmlinux.init.ramfs: lma = 0xa0e78000 (vma = 0x01278000)  size = 0x00000085.
load section vmlinux.exitcall: lma = 0xa0e79000 (vma = 0x01279000)  size = 0x00000048.
not load section vmlinux.bss: addr = 0x01279060  size = 0x000205fc .
start addr is set to 0xa0000000 by exec file.

or in okl4-1.5.2:
load section vmlinux.initcall.init: lma = 0xa066d850 (vma = 0x8136d850)  size = 0x000000dc.
load section vmlinux.con_initcall.init: lma = 0xa066d92c (vma = 0x8136d92c)  size = 0x00000004.
not load section vmlinux.security_initcall.init: addr = 0x8136d930  size = 0x00000000 .
load section  vmlinux.init.ramfs: lma = 0xa066e000 (vma = 0x8136e000)  size = 0x00000086.
load section vmlinux.exitcall: lma = 0xa066f000 (vma = 0x8136f000)  size = 0x0000004c.
not load section vmlinux.bss: addr = 0x8136f060  size = 0x000204e8 .
load section rootfs: lma = 0xa0700000 (vma = 0x80600000)  size = 0x007d0000.
load section bootinfo: lma = 0xa0074000 (vma = 0x80014000)  size = 0x00004000.
start addr is set to 0xa0000000 by exec file.

and then everything hangs.

Different problems arise when I try to use kzm_arm11 as the machine argument. I'm asked for the linux/kernel-2.6.10-v1/  folder. If I simply copy/rename the kernel-2.6.12-v2 present in the archive at simulate stage I get:

  Building modules, stage 2.
  MODPOST
  CC      drivers/block/loop.mod.o
  LD [M]  drivers/block/loop.ko
  CC      drivers/block/rd.mod.o
  LD [M]  drivers/block/rd.ko
  CC      drivers/net/dummy.mod.o
  LD [M]  drivers/net/dummy.ko
  CC      drivers/net/tun.mod.o
  LD [M]  drivers/net/tun.ko
  CC      fs/binfmt_misc.mod.o
  LD [M]  fs/binfmt_misc.ko
  CC      fs/nls/nls_iso8859-1.mod.o
  LD [M]  fs/nls/nls_iso8859-1.ko
  CC      fs/nls/nls_utf8.mod.o
  LD [M]  fs/nls/nls_utf8.ko
make: Leaving directory `/download/okl4_release_1.5.2/linux/kernel-2.6.10-v1'
[XML ] build/images/weaver.xml
[ELF ] build/images/image.elf
[ELF ] build/images/image.boot
[SIM ] build/images/image.boot
sh: tools/unittest/kzm-boot.sh: No such file or directory
scons: done building targets.


Gabi

Thaks



       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080130/2219d125/attachment.htm