Hi,
I'm trying to get L4Android working on a BeagleBoard (rev. C4).
After some minor issues, I finally managed to build L4Re, Fiasco.OC,
L4Linux and L4Android successfully. Everything works great on my board,
including L4Linux.
But L4Android gives me some errors during the bootstrap:
io | Io service
io | L4Re[rm]: unhandled read page fault @40000c pc=102b4c8
io | L4Re: unhandled exception: pc=0x102b4c8
Please see [1] for the full bootstrap (target: ARM beagleboard).
To …
[View More]exclude some hardware related issues, I rebuilt L4Android with
realview board (ARM) as target, in order to test it using qemu. This
time, I get the following error:
android | L4Re: unhandled exception: pc=0xa80001c8
Please see [2] for the full bootstrap (target: ARM realview board).
Would be nice if someone could build L4Android for realview-b and tell
me if it works in qemu. Maybe those errors are related to my newbieness :D
Just another thing. On the L4Android Website, in the 'build diskimage'
instructions, you write:
"Next we need to modify the init.rc script. Mount the newly created
image and locate the section where the system and data partition are to
be mounted and replace the commands with the lines following the mount:"
mount cramfs /l4bdds0 /system
mount cramfs /l4bdds0 /system ro remount
mount tmpfs tmpfs /data size=32M
Then I saw that on your prebuilt root/system images for x86, the "on fs"
section of the init.rc file is empty:
on fs
# mount mtd partitions
So, i could not compare the section with mine, which looks the following:
on fs
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a
checkpoint
# mount yaffs2 mtd@system /system
# mount yaffs2 mtd@system /system ro remount
# mount yaffs2 mtd@userdata /data nosuid nodev
mount cramfs /l4bdds0 /system
mount cramfs /l4bdds0 /system ro remount
mount tmpfs tmpfs /data size=32M
mount yaffs2 mtd@cache /cache nosuid nodev #unchanged
Anyway, I tried to empty the "on fs" section like on the prebuilt
images, but the above errors still persist.
So any idea about those errors?
Thank you!
Giorgio
Build environment in use
========================
- L4Re/L4Linux/Fiasco.OC: l4re-snapshot-2011062216 (not the last
revision, since l4android needs to be updated)
- L4Android: latest available revision (19 Jul 2011)
- Compiler: CodeSourcery (arm-2010.09-50-arm-none-linux-gnueabi)
- OS: Ubuntu 11.04 x86
[1] http://pastebin.com/95M7iiPv
[2] http://pastebin.com/eYvM65ij
[View Less]
Hi,
I found a small issue during the build process of L4Android for x86
target (arm target build works as expected). When using the make command
to generate images (e.g make grub2iso lx_gingerbread-x86), the following
error appears:
Processing entry 'l4_gingerbread'
Could not find 'l4_gingerbread.cfg' with path '...'
make[1]: *** [grub2iso] Error 2
make[1]: Exiting Directory
'/home/giowck/tests/target_x86/l4re-snapshot-2011062216/src/l4'
make: *** [grub2iso] Error 2
This is caused by an …
[View More]outdated module entry in the 'modules-x86.list'
file in the 'configs' git repository (and L4Android Website in the
'Create ISO Image' instructions). Here are some 'x86' suffixes missing.
Patch file
==========
--- modules-x86.list 2011-08-28 13:43:09.669688003 +0200
+++ modules-x86_fixed.list 2011-08-28 13:44:02.546068212 +0200
@@ -1,6 +1,6 @@
modaddr 0x01100000
entry l4_gingerbread
-roottask moe rom/l4_gingerbread.cfg
+roottask moe rom/l4_gingerbread-x86.cfg
kernel fiasco -serial_esc
module l4re
module ned
@@ -8,9 +8,9 @@
module rtc
module mag
module fb-drv
-module l4_gingerbread.cfg
+module l4_gingerbread-x86.cfg
module x86-legacy.devs
-module l4_android.vbus
+module l4_android-x86.vbus
module vmlinuz.android
module root-x86-ginger.img
module system-x86-ginger.img
With the above patch, the images are built successfully.
It would be nice if you update the L4Android Website ("Create ISO
Image") and the configs repository.
Regards
Giorgio
[View Less]
Hi,
I downloaded the latest l4re snapshot (l4re-snapshot-2011081207), in order
to compile it along with l4android for arm.
Finally it compiles with the CodeSourcery cross compiler (as noted in the
README file), where the previous snapshot failed and worked only for me with
the 4.2-arm-softfloat compiler (without EABI support).
But, with the latest snapshot I get a new error:
# make L4ARCH=arm CROSS_COMPILE=arm-linux- -j4
make -C /home/wicklein/tests/l4android/kernel
O=/home/wicklein/tests/…
[View More]l4android/l4android_builddir/.
Package l4re-main was not found in the pkg-config search path.
Perhaps you should add the directory containing `l4re-main.pc'
to the PKG_CONFIG_PATH environment variable
No package 'l4re-main' found
Getting required compilation flags failed.
L4OBJ: /home/wicklein/tests/l4re-snapshot-latest/obj/l4/arm-beagleboard
L4_REQUIRED_MODS: l4re-main libc_be_minimal_log_io libc_minimal
libsupc++_minimal log l4re_c-util libio libvcpu shmc
/home/wicklein/tests/l4android/kernel/arch/l4/Makefile:315: *** Aborting..
Schluss.
make[1]: *** [sub-make] Fehler 2
make: *** [all] Fehler 2
Just wanted to report that. Now I'll try to copy just the l4re-main.pc file
from the old snapshot to the new pc directory.
Regards
Giorgio
[View Less]
Hi there,
I attached a small build correction I encountered while building L4Env
with Perl 5.12. This is necessary since Perl 5.11's and above 'split'
does not automatically assign '@_' anymore.
Greetings,
Sebastian
Hi l4-hackers,
I'm trying to compile the L4 Runtime for the x86 arch, using the latest
snapshot (l4re-snapshot-2011062216).
After "make setup" and "make", the following error interrupts the build
process:
"/home/giowck/tests/l4re-snapshot-2011062216/src/l4/pkg/uclibc-minimal/libc/Make.rules:22:
*** unkwon source file: libc/signal/sigsetops.h. Abort."
The full output of the make command is available on a pastebin [1].
I'm using: gcc-Version 4.6.1 (GCC), see [2] for the full "gcc -v"
…
[View More]output. My system is Arch Linux i686.
Maybe anyone can give me a hint?
Thank you,
Giorgio
[1] http://pastebin.com/r4K4SFef
[2] http://pastebin.com/1zLnLy9w
[View Less]
Hello Hackers,
I've been tinkering with the internals of Fiasco a bit, and I'm at the
point where the kernel boots & runs hello as well as hello-shared
without issue.
The thing is, though, these tests seem to use only a fraction of my code
(and I know there are some pretty sketchy lurkers in my code...), so I'm
looking for a more thorough test of kernel capabilities to verify my
changes are relatively operational in many/most cases.
I'm aware of some options here, but I didn't want to …
[View More]use a hammer if all
I need is a screwdriver. So, to you: what is the most straightforward
way to test Fiasco with existing software?
I'm aware of L4Linux and ORe as possibilities -- are these good options,
or is there a simpler tool for the job?
Thank you!
--Bryce
[View Less]