From charlesfang0301 at gmail.com Fri Sep 3 16:37:02 2010 From: charlesfang0301 at gmail.com (Mingwei.Fang) Date: Thu, 2 Sep 2010 23:37:02 -0700 (PDT) Subject: [okl4-developer] A Strange Problem Message-ID: <1283495822938-5494175.post@n2.nabble.com> In /arch/arm/pistachio/include/tcb.h, I have added two sentences in function set_mutex_thread_handle as follows: INLINE void tcb_t::set_mutex_thread_handle(capid_t handle) { printf("get_space1.1.1 = %d\n",get_space()->get_domain()); //first sentence to be added get_utcb()->mutex_thread_handle = handle; printf("get_space1.1.2 = %d\n",get_space()->get_domain()); //second sentence to be added } At beginning, the value of get_space1.1.1 to be printed is 16. But after ?get_utcb()->mutex_thread_handle = handle;?, which looks like have nothing to do with setting the value of domain, the value of get_space1.1.2 changed to 15. Can somebody tell me why the value of get_domain() changed? -- View this message in context: http://okl4-community-forum.9692.n2.nabble.com/A-Strange-Problem-tp5494175p5494175.html Sent from the OKL4 Community Forum mailing list archive at Nabble.com. From diesel.fan at zyxel.com.tw Mon Sep 6 19:23:54 2010 From: diesel.fan at zyxel.com.tw (fan.diesel) Date: Mon, 6 Sep 2010 02:23:54 -0700 (PDT) Subject: [okl4-developer] About SMP in OKL4 Message-ID: <1283765034590-5502592.post@n2.nabble.com> Suppose I am currently using an OS with no SMP. Then I run it on OKL4 micro kernel which supports SMP/SMT right now. Will I get any advantage on multi cores with the helping of OKL4? I mean, will the micro kernel dispatch the threads to different cores for me without the guest OS's awareness? I am really confusing here.... -- View this message in context: http://okl4-community-forum.9692.n2.nabble.com/About-SMP-in-OKL4-tp5502592p5502592.html Sent from the OKL4 Community Forum mailing list archive at Nabble.com. From benno at benno.id.au Mon Sep 6 20:36:58 2010 From: benno at benno.id.au (Ben Leslie) Date: Mon, 6 Sep 2010 20:36:58 +1000 Subject: [okl4-developer] About SMP in OKL4 In-Reply-To: <1283765034590-5502592.post@n2.nabble.com> References: <1283765034590-5502592.post@n2.nabble.com> Message-ID: Hi Fan, OKL4 is not able to automatically turn a uniprocessor OS into an SMP OS. So, if all you do is run a uni-processor operating system on top of OKL4, then no, you will not get any advantage. However, if you are running multiple operating systems these can take advantage of the extra available cores. In this case the microkernel will dispatch the different operating systems to different cores. Cheers, Ben On Mon, Sep 6, 2010 at 7:23 PM, fan.diesel wrote: > > Suppose I am currently using an OS with no SMP. Then I run it on OKL4 micro > kernel which supports SMP/SMT right now. Will I get any advantage on multi > cores with the helping of OKL4? I mean, will the micro kernel dispatch the > threads to different cores for me without the guest OS's awareness? I am > really confusing here.... > -- > View this message in context: > http://okl4-community-forum.9692.n2.nabble.com/About-SMP-in-OKL4-tp5502592p5502592.html > Sent from the OKL4 Community Forum mailing list archive at Nabble.com. > > _______________________________________________ > Developer mailing list > Developer at okl4.org > https://lists.okl4.org/mailman/listinfo/developer > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.okl4.org/pipermail/developer/attachments/20100906/19ca480f/attachment.htm From marcmaurialloza at gmail.com Mon Sep 6 23:53:40 2010 From: marcmaurialloza at gmail.com (Marc Mauri Alloza) Date: Mon, 6 Sep 2010 15:53:40 +0200 Subject: [okl4-developer] Just starting. Message-ID: Hello, I'm just starting programming on top of the OKL4 Microkernel I've folowed the Hello World tutorial. I would like to know if I can run all this on an x86 emulator instead of cross compiling for ARM and then run it on the Skyeye. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.okl4.org/pipermail/developer/attachments/20100906/0ecead81/attachment.htm From hu.ruihuan at zte.com.cn Mon Sep 6 13:23:52 2010 From: hu.ruihuan at zte.com.cn (specter117) Date: Sun, 5 Sep 2010 20:23:52 -0700 (PDT) Subject: [okl4-developer] why I can't build OKL4 Message-ID: <1283743432827-5501890.post@n2.nabble.com> It's my first build OKL4,but answer below: scons: warning: Ignoring missing SConscript 'tools/scons.py' File "build.py", line 100, in scons: done reading SConscript files. scons: Building targets ... scons: `.' is up to date. scons: done building targets. -- View this message in context: http://okl4-community-forum.9692.n2.nabble.com/why-I-can-t-build-OKL4-tp5501890p5501890.html Sent from the OKL4 Community Forum mailing list archive at Nabble.com. From juventini_belladonna at yahoo.com Thu Sep 16 00:52:17 2010 From: juventini_belladonna at yahoo.com (rika) Date: Wed, 15 Sep 2010 07:52:17 -0700 (PDT) Subject: [okl4-developer] Problem in Hello World SDK Tutorial Message-ID: <1284562337443-5534687.post@n2.nabble.com> Hi, i am a newbie in OKL4 and i want to try to run the Hello World example in SDK tutorial. But there is a problem when i want to do "make" in my working directory. The error is such followed. make -C hello KERNEL=micro BUILD=debug make[1]: Entering directory `/home/rafika/Desktop/sdk/okl4/arm1136js/examples/rikasdk/hello' cp hello.xml.in build.micro-debug/bin/hello.xml arm-unknown-linux-gnueabi-gcc -O2 --std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wmissing-declarations -Wredundant-decls -Wundef -Wpointer-arith -Wno-nonnull -Werror -march=armv5te -Wa,-mcpu=arm1136 -O2 -nostdlib -nostdinc -g -Iinclude -I../../../../../okl4/arm1136js/micro-debug/include -c src/hello.c -o build.micro-debug/src/hello.o make[1]: arm-unknown-linux-gnueabi-gcc: Command not found make[1]: *** [build.micro-debug/src/hello.o] Error 127 make[1]: Leaving directory `/home/rafika/Desktop/sdk/okl4/arm1136js/examples/rikasdk/hello' make: *** [hello/build.micro-debug/bin/hello.xml] Error 2 I have downloaded the cross compiler that supports EABI, arm-linux-gnueabi-4.2.4.tar.gz (68 MB) and download the latest version of Crosstool 0.43and I did apply the Crosstool EABI patch. Also I have built the toolchain by using # sh demo-arm-softfloat.sh Could anyone help me with this problem? Thank you so much! -- View this message in context: http://okl4-community-forum.9692.n2.nabble.com/Problem-in-Hello-World-SDK-Tutorial-tp5534687p5534687.html Sent from the OKL4 Community Forum mailing list archive at Nabble.com. From juventini_belladonna at yahoo.com Fri Sep 17 01:53:42 2010 From: juventini_belladonna at yahoo.com (rika) Date: Thu, 16 Sep 2010 08:53:42 -0700 (PDT) Subject: [okl4-developer] Problem in Hello World SDK Tutorial In-Reply-To: <1284562337443-5534687.post@n2.nabble.com> References: <1284562337443-5534687.post@n2.nabble.com> Message-ID: <1284652422774-5539084.post@n2.nabble.com> Dear Gaby, thank you for the quick and helpful answer. Now I did the export correctly. However, there is another problem after "make". It does not show " hello world! " message. Instead, the error appear is such following. make -C hello KERNEL=micro BUILD=debug make[1]: Entering directory `/home/rafika/Desktop/sdk/rikasdk/hello' cp hello.xml.in build.micro-debug/bin/hello.xml arm-unknown-linux-gnueabi-ld -o build.micro-debug/bin/hello -Ttext=0x90000000 -L/home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs /home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs/crt0.o build.micro-debug/src/hello.o --start-group /home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs/libc.a /home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs/libokl4.a /home/rafika/Downloads/arm-unknown-linux-gnueabi/bin/../lib/gcc/arm-unknown-linux-gnueabi/4.2.4/libgcc.a --end-group make[1]: Leaving directory `/home/rafika/Desktop/sdk/rikasdk/hello' cp image.xml.in build.micro-debug/images/image.xml sed -i -e 's%@ABS_MACHINE_XML_PATH@%/home/rafika/Desktop/sdk/kernel/arm1136js/micro-debug/object/machine.xml%' build.micro-debug/images/image.xml sed -i -e 's%@ABS_KERNEL_XML_PATH@%/home/rafika/Desktop/sdk/kernel/arm1136js/micro-debug/object/kernel.xml%' build.micro-debug/images/image.xml sed -i -e 's%@ABS_CELL_XML_PATHS@%\n %' build.micro-debug/images/image.xml /home/rafika/Desktop/sdk/bin/elfweaver --traceback merge -obuild.micro-debug/images/image.elf build.micro-debug/images/image.xml 'import site' failed; use -v for traceback /home/rafika/Desktop/sdk/bin/elfweaver modify -obuild.micro-debug/images/image.sim build.micro-debug/images/image.elf --physical_entry 'import site' failed; use -v for traceback /home/rafika/Desktop/sdk/bin/elfweaver modify -obuild.micro-debug/images/image.boot build.micro-debug/images/image.elf --physical_entry --physical 'import site' failed; use -v for traceback /home/rafika/Desktop/sdk/bin/elfweaver modify -obuild.micro-debug/images/image.boot.bin build.micro-debug/images/image.elf --binary 'import site' failed; use -v for traceback and when i run comnad: " skyeye -c skyeye.conf -e build.micro-debug/images/image.sim " the error appear is such following. Your elf file is little endian. arch: arm cpu info: xscale, pxa25x, 69052100, fffffff0, 2 mach info: name pxa_lubbock, mach_init addr 0x80689a0 uart_mod:0, desc_in:, desc_out:, converter: SKYEYE: use xscale mmu ops exec file "build.micro-debug/images/image.sim"'s format is elf32-little. load section initscript: lma = 0x80004000 (vma = 0x88000000) size = 0x00001000. load section hello.text: lma = 0x80010000 (vma = 0x90000000) size = 0x000059b0. SKYEYE:NumInstrs 0, mem_write_byte addr = 90000000 no bank I have downloaded the Skyeye-kenge-1.2.1n.tar.gz , add the bin directory to PATH, by using: PATH=$PATH:/home/Downloads/skyeye-1.2.8_rc1/bin and export path by: export PATH=$PATH:/home/Downloads/skyeye-1.2.8_rc1/bin Where did I do wrong? Could you please explain to me? Thank you so much for the help. Rika -- View this message in context: http://okl4-community-forum.9692.n2.nabble.com/Problem-in-Hello-World-SDK-Tutorial-tp5534687p5539084.html Sent from the OKL4 Community Forum mailing list archive at Nabble.com. From boy3dfx2 at yahoo.com Fri Sep 17 02:59:59 2010 From: boy3dfx2 at yahoo.com (Gabi Voiculescu) Date: Thu, 16 Sep 2010 09:59:59 -0700 (PDT) Subject: [okl4-developer] Problem in Hello World SDK Tutorial In-Reply-To: <1284652422774-5539084.post@n2.nabble.com> Message-ID: <556606.48347.qm@web113816.mail.gq1.yahoo.com> See my reply below. --- On Thu, 9/16/10, rika wrote: > From: rika > Subject: Re: [okl4-developer] Problem in Hello World SDK Tutorial > To: developer at okl4.org > Date: Thursday, September 16, 2010, 6:53 PM > > Dear Gaby, > > thank you for the quick and helpful answer. Now I did the > export correctly. > > However, there is another problem after "make". It does not > show " hello > world! " message. It shouldn't say that, unless you have the proper emulator installed and you run your resulting binary in it. > Instead, the error appear is such following. > > > make -C hello KERNEL=micro BUILD=debug > make[1]: Entering directory > `/home/rafika/Desktop/sdk/rikasdk/hello' > cp hello.xml.in build.micro-debug/bin/hello.xml > arm-unknown-linux-gnueabi-ld -o > build.micro-debug/bin/hello > -Ttext=0x90000000 > -L/home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs > /home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs/crt0.o > > build.micro-debug/src/hello.o --start-group > /home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs/libc.a > /home/rafika/Desktop/sdk/okl4/arm1136js/micro-debug/libs/libokl4.a > /home/rafika/Downloads/arm-unknown-linux-gnueabi/bin/../lib/gcc/arm-unknown-linux-gnueabi/4.2.4/libgcc.a > --end-group > make[1]: Leaving directory > `/home/rafika/Desktop/sdk/rikasdk/hello' > cp image.xml.in build.micro-debug/images/image.xml > sed -i -e > 's%@ABS_MACHINE_XML_PATH@%/home/rafika/Desktop/sdk/kernel/arm1136js/micro-debug/object/machine.xml%' > build.micro-debug/images/image.xml > sed -i -e > 's%@ABS_KERNEL_XML_PATH@%/home/rafika/Desktop/sdk/kernel/arm1136js/micro-debug/object/kernel.xml%' > build.micro-debug/images/image.xml > sed -i -e 's%@ABS_CELL_XML_PATHS@% file=\"hello/build.micro-debug/bin/hello.xml\"/>\n???%' > build.micro-debug/images/image.xml > /home/rafika/Desktop/sdk/bin/elfweaver --traceback merge > -obuild.micro-debug/images/image.elf > build.micro-debug/images/image.xml > 'import site' failed; use -v for traceback > /home/rafika/Desktop/sdk/bin/elfweaver modify > -obuild.micro-debug/images/image.sim > build.micro-debug/images/image.elf > --physical_entry > 'import site' failed; use -v for traceback > /home/rafika/Desktop/sdk/bin/elfweaver modify > -obuild.micro-debug/images/image.boot > build.micro-debug/images/image.elf > --physical_entry --physical > 'import site' failed; use -v for traceback > /home/rafika/Desktop/sdk/bin/elfweaver modify > -obuild.micro-debug/images/image.boot.bin > build.micro-debug/images/image.elf > --binary > 'import site' failed; use -v for traceback > I have never tried to run with one of these sdk-s. I prefer using the whole okl4 3 from sources. But from what I see above, the final scripts that create the images do not seem to work properly. You may experience a python version problem, the scripts are designed to work with python2.4. At least these are what a quick google search for the keywords: 'import site' failed; use -v for traceback, says. > > and when i run comnad: " skyeye -c skyeye.conf -e > build.micro-debug/images/image.sim " > A couple of things here: 1 - I use the boot image into skyeye instead of the sim. Don't remember what the sim image was created for. But I know only the boot image is liked by skyeye up to 1.2.6. From 1.2.8 onward there are issues with reading the .boot, too. 2 - skyeye is the emulator choice when you use sdk-pxa, not for sdk-arm1136. 3 - for arm1136 I believe the okl4 guys recommended a version of qemu: qemu-kzm from here: http://wiki.ok-labs.com/Release/3.0 http://wiki.ok-labs.com/downloads/release-3.0/qemu-okl.0.9.1.tar.gz 4 - I do not know what image is liked by qemu > the error appear is such following. > > > Your elf file is little endian. > arch: arm > cpu info: xscale, pxa25x, 69052100, fffffff0, 2 > mach info: name pxa_lubbock, mach_init addr 0x80689a0 > uart_mod:0, desc_in:, desc_out:, converter: > SKYEYE: use xscale mmu ops > exec file "build.micro-debug/images/image.sim"'s format is > elf32-little. > load section initscript: lma = 0x80004000 (vma = > 0x88000000)? size = > 0x00001000. > load section hello.text: lma = 0x80010000 (vma = > 0x90000000)? size = > 0x000059b0. > SKYEYE:NumInstrs 0, mem_write_byte addr = 90000000 no bank > > > > I have downloaded the Skyeye-kenge-1.2.1n.tar.gz , add the > bin directory to > PATH, by using: Again, I think you need qemu-kzm from either nicta or ok-labs websites. > > PATH=$PATH:/home/Downloads/skyeye-1.2.8_rc1/bin > Aaa.. then this is not skyeye 1.2.1 but 1.2.8-rc1! Wrong. You should have added something like /opt/nicta/skyeye/ if you would have used the right skyeye emulator binary. Skyeye 1.2.1 can be found on the ertos nicta site. http://wiki.ok-labs.com/Prerequisites?highlight=(qemu) http://www.ertos.nicta.com.au/downloads/tools/skyeye-kenge-1.2.1n.tar.gz > and export path by: > > export PATH=$PATH:/home/Downloads/skyeye-1.2.8_rc1/bin > > > > Where did I do wrong? Could you please explain to me? > > Thank you so much for the help. > > Rika > -- > View this message in context: http://okl4-community-forum.9692.n2.nabble.com/Problem-in-Hello-World-SDK-Tutorial-tp5534687p5539084.html > Sent from the OKL4 Community Forum mailing list archive at > Nabble.com. > > _______________________________________________ > Developer mailing list > Developer at okl4.org > https://lists.okl4.org/mailman/listinfo/developer > From frank.kaiser at opensynergy.com Tue Sep 21 02:12:43 2010 From: frank.kaiser at opensynergy.com (Frank Kaiser) Date: Mon, 20 Sep 2010 18:12:43 +0200 Subject: [okl4-developer] OKL4 compilation problem In-Reply-To: References: Message-ID: <026691588FEC5D48AE1A8857256F656A1AEFD9@os-s03.open-synergy.com> Hello, Janith First, you should have sent this request to the OKL4 mailing list, since your problem is related to the OKL4 kernel compilation, but not to the Genode Framework build. Second, the error message "sh: i686-unknown-linux-gnu-gcc: command not found" gives an unambiguous statement about your problem: the build script does not find the compiler you have instructed it to use by giving the option "toolprefix=i686-unknown-linux-gnu-". Even if you are a newbie you should be able to sort out this kind of problems by yourself before bothering hundreds of people on a mailing list! Regards Frank From: Janith Widarshana [mailto:e06widu at gmail.com] Sent: Monday, September 20, 2010 6:02 PM To: Genode OS Framework Mailing List Subject: hi all, I'm new to okl4.When I Compile the kernel by invoking the python script that can be found in the tools directory of the OKL4 source tree I got following error. Is that a problem with my processor architecture? please some one help me for this. okl4_2.1.1-patch.9$ ./tools/build.py project=l4test machine=ia32_pc99 toolprefix=i686-unknown-linux-gnu- scons: Reading SConscript files ... architecture ia32 is not yet supported by libcompat. architecture ia32 is not yet supported by libcompat. scons: done reading SConscript files. scons: Building targets ... [ASM ] build/pistachio/object/pistachio/tcb_layout.s sh: i686-unknown-linux-gnu-gcc: command not found scons: *** [build/pistachio/object/pistachio/tcb_layout.s] Error 127 scons: building terminated because of errors. Thanx. Janith Widarshana. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.okl4.org/pipermail/developer/attachments/20100920/1f789d3b/attachment.htm From itodroid at gmail.com Tue Sep 21 09:17:13 2010 From: itodroid at gmail.com (ito droid) Date: Mon, 20 Sep 2010 16:17:13 -0700 Subject: [okl4-developer] Building oklinux 2.6.24-v2 Message-ID: Hello all. I am attempting to build the OKLinux distribution oklinux_2.6.24.9-patch.4.tar.gz that I got from here: http://wiki.ok-labs.com/downloads/release-3.0/oklinux_2.6.24.9-patch.4.tar.gz I've extracted the contents of the tar file and put the apps/, kernel-2.6.24-v2/, rootfs-2.6.24-v2, and tools/ directories underneath the "linux" directory beneath my OKL4v3 sdk directory (i.e. okl4v3/linux). When I attempt to build OKLinux using the following command line: tools/build.py machine=versatile project=linux wombat=True TOOLCHAIN=gnu_arm_eabi_toolchain pistachio.TOOLCHAIN=gnu_arm_toolchain PYFREEZE=false the environment successfully builds the OKL libs (underneath build/oklinux) but fails to either start or build the oklinux tree. The last few lines from the build script are as follows: [AR ] build/oklinux/lib/libokl4.a [LIB ] build/oklinux/lib/libokl4.a [AR ] build/oklinux/lib/liboklinux.a [LIB ] build/oklinux/lib/liboklinux.a Mkdir("build/linux/install/tmp") Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/etc/inittab" as "build/linux/install/etc/inittab" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/etc/passwd" as "build/linux/install/etc/passwd" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/etc/group" as "build/linux/install/etc/group" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/etc/fstab" as "build/linux/install/etc/fstab" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/etc/hosts" as "build/linux/install/etc/hosts" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/etc/shells" as "build/linux/install/etc/shells" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/etc/init.d/rcS" as "build/linux/install/etc/init.d/rcS" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/evtest" as "build/linux/install/usr/bin/evtest" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/psplash" as "build/linux/install/usr/bin/psplash" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/netioctl" as "build/linux/install/usr/bin/netioctl" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/additional_scripts/wombat_banner" as "build/linux/install/usr/bin/wombat_banner" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/additional_scripts/wombat_test.sh" as "build/linux/install/usr/bin/wombat_test.sh" Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/additional_scripts/check_rootfs_size.sh" as "build/linux/install/usr/bin/check_rootfs_size.sh" Mkdir("build/linux/install/dev") Mkdir("build/linux/install/proc") Mkdir("build/linux/install/mnt") Mkdir("build/linux/install/sys") Mkdir("build/linux/install/root") Install file: "build/linux/object/_home_mydir_okl_okl4v3_linux_rootfs-2.6.24-v2/extras/udhcpc/default.script" as "build/linux/install/usr/share/udhcpc/default.script" scons: *** Source `linux/rootfs-2.6.24-v2/libc.so.6' not found, needed by target `build/linux/install/lib/libc.so.6'. Stop. scons: building terminated because of errors. It appears that scons is looking for the target libc shared library...but it hasn't been built yet! Did I miss a step here? So, I've been attempting to build the oklinux from the kernel-2.6.24-v2/ directory. Have tried "make ARCH=l4 SYSTEM=arm CROSS_COMPILE=arm-eabi-" but after the menuconfig, it fails terribly. I've tried building a straight cross-compiled version for a generic arm platform but the OKLinux changes are "hard coded" and not defined as part of a platform definition. Therefore, building fails for a generic arm as well. Has anyone ever successfully built oklinux from its sources (2.6.24-v2) successfully? And can they share their secret sauce? PS - I've tried both (arm-eabi-) gcc4.2.1 and gcc4.4.0 without success. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.okl4.org/pipermail/developer/attachments/20100920/58d22cd8/attachment.htm From brett.mahar at gmail.com Tue Sep 21 11:05:43 2010 From: brett.mahar at gmail.com (Brett Mahar) Date: Tue, 21 Sep 2010 11:05:43 +1000 Subject: [okl4-developer] Installing on BeagleBoard xM Message-ID: Hi, I am waiting on a BeagleBoard xM to arrive in the post, and in the meantime am wondering has anyone got OKL4 running on one? As I've never built an OS for an embedded device, is there are version of L4 that is least likely to give me major pain? Cheers, Brett. From juventini_belladonna at yahoo.com Wed Sep 22 21:30:51 2010 From: juventini_belladonna at yahoo.com (rika) Date: Wed, 22 Sep 2010 04:30:51 -0700 (PDT) Subject: [okl4-developer] Problem in Hello World SDK Tutorial In-Reply-To: <1284562337443-5534687.post@n2.nabble.com> References: <1284562337443-5534687.post@n2.nabble.com> Message-ID: <1285155051035-5558648.post@n2.nabble.com> Hi Gaby, thank you for the kind answer. I have followed your suggestions. Yes, my Ubuntu has only python 2.6 but now I have converted it to python2.4. Also now I have changed my simulator to qemu-okl 0.9.1, which work for arm1136, instead of skyeye. I still have the error when in "make". The error is such followed. rafika at rafika-desktop:~/Desktop/sdk/newSDK$ make make -C hello KERNEL=micro BUILD=debug make[1]: Entering directory `/home/rafika/Desktop/sdk/newSDK/hello' cp hello.xml.in build.micro-debug/bin/hello.xml arm-unknown-linux-gnueabi-ld -o build.micro-debug/bin/hello -Ttext=0x90000000 -L/home/rafika/Desktop/sdk//okl4/arm1136js/micro-debug/libs /home/rafika/Desktop/sdk//okl4/arm1136js/micro-debug/libs/crt0.o build.micro-debug/src/hello.o --start-group /home/rafika/Desktop/sdk//okl4/arm1136js/micro-debug/libs/libc.a /home/rafika/Desktop/sdk//okl4/arm1136js/micro-debug/libs/libokl4.a /home/rafika/Downloads/arm-unknown-linux-gnueabi/bin/../lib/gcc/arm-unknown-linux-gnueabi/4.2.4/libgcc.a --end-group make[1]: Leaving directory `/home/rafika/Desktop/sdk/newSDK/hello' cp image.xml.in build.micro-debug/images/image.xml sed -i -e 's%@ABS_MACHINE_XML_PATH@%/home/rafika/Desktop/sdk//kernel/arm1136js/micro-debug/object/machine.xml%' build.micro-debug/images/image.xml sed -i -e 's%@ABS_KERNEL_XML_PATH@%/home/rafika/Desktop/sdk//kernel/arm1136js/micro-debug/object/kernel.xml%' build.micro-debug/images/image.xml sed -i -e 's%@ABS_CELL_XML_PATHS@%\n %' build.micro-debug/images/image.xml /home/rafika/Desktop/sdk//bin/elfweaver --traceback merge -obuild.micro-debug/images/image.elf build.micro-debug/images/image.xml 'import site' failed; use -v for traceback What is other problem that can cause this error? And when I want to build the image, i typed : build.micro-debug/images/image.elf and the error occured is: rafika at rafika-desktop:~/Desktop/sdk/newSDK$ build.micro-debug/images/image.elf bash: build.micro-debug/images/image.elf: Permission denied However, when i want to simulate the image (which required me to install qemu-kvm-extras), the output is such following. rafika at rafika-desktop:~/Desktop/sdk/newSDK$ qemu-system-arm -M kzm -nographic -start-addr 0x86800000 -kernel build.micro-debug/images/image.elf Supported machines are: syborg Syborg (Symbian Virtual Platform) musicpal Marvell 88w8618 / MusicPal (ARM926EJ-S) mainstone Mainstone II (PXA27x) n800 Nokia N800 tablet aka. RX-34 (OMAP2420) n810 Nokia N810 tablet aka. RX-44 (OMAP2420) cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310) sx1 Siemens SX1 (OMAP310) V2 sx1-v1 Siemens SX1 (OMAP310) V1 tosa Tosa PDA (PXA255) akita Akita PDA (PXA270) spitz Spitz PDA (PXA270) borzoi Borzoi PDA (PXA270) terrier Terrier PDA (PXA270) connex Gumstix Connex (PXA255) verdex Gumstix Verdex (PXA270) lm3s811evb Stellaris LM3S811EVB lm3s6965evb Stellaris LM3S6965EVB realview-eb ARM RealView Emulation Baseboard (ARM926EJ-S) realview-eb-mpcore ARM RealView Emulation Baseboard (ARM11MPCore) realview-pb-a8 ARM RealView Platform Baseboard for Cortex-A8 realview-pbx-a9 ARM RealView Platform Baseboard Explore for Cortex-A9 versatilepb ARM Versatile/PB (ARM926EJ-S) versatileab ARM Versatile/AB (ARM926EJ-S) integratorcp ARM Integrator/CP (ARM926EJ-S) (default) What is actual output of the "Hello world" tutorial supposed to be? Thank you for your answer. Rika -- View this message in context: http://okl4-community-forum.9692.n2.nabble.com/Problem-in-Hello-World-SDK-Tutorial-tp5534687p5558648.html Sent from the OKL4 Community Forum mailing list archive at Nabble.com. From clement.mazin at etu.unilim.fr Sat Sep 25 00:27:58 2010 From: clement.mazin at etu.unilim.fr (Clement Mazin) Date: Fri, 24 Sep 2010 07:27:58 -0700 (PDT) Subject: [okl4-developer] How to configure Insight (gdb) with Qemu for OKL4 Message-ID: <1285338478389-5567034.post@n2.nabble.com> Hi all, I want to follow an OKL4 execution with insight. I installed it and succes to connect it to Qemu. I can follow registers and memory state but i can follow the source code. I think it's because OKL4 is not build with debug symbol. How can i fix it ? -- View this message in context: http://okl4-community-forum.9692.n2.nabble.com/How-to-configure-Insight-gdb-with-Qemu-for-OKL4-tp5567034p5567034.html Sent from the OKL4 Community Forum mailing list archive at Nabble.com.