- l4-hackers - example.com Site

Ankh Examples
by Ayad Mostafa 09 Apr '14

09 Apr '14

hello l4 hackers, i'm experimenting with ankh and so far failed to successfully ping morpork from my host machine. it seems that receive() blocks at wait_for_data() indefinitely. i can see irq activity on displayed on screen but wait_for_data() does not unblock. i appreciate any help or ideas... software version: l4re revision r63 (2014-02-28) gcc version 4.8.2 qemu version 1.7.0 qemu command: qemu -cpu core2duo -m 128 -cdrom ./morpork.iso \ -net nic,vlan=0,macaddr=00:e0:4c:c6:45:f4,model=rtl8139 -net tap,vlan=0,ifname=tap0 -serial stdio ping command: arping -i tap0 00:E0:4C:C6:45:F4 output: [32mankh | Initialized DDELinux 2.6 [0m [32mankh | <6>net_namespace: 636 bytes [0m [32mankh | Initializing DDE page cache [0m [32mankh | ddekit_pci_init [0m [32mankh | pci bus constructor [0m [32mankh | PCI: L4 root bridge is device 31ca0 [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | l4dde26_register_rx_callback: [36mNew rx callback @ 0x1000200. [0m [0m [32mankh | Softirq daemon starting [0m [32mankh | init_wq_head [0m [32mankh | <6>8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [0m [32mankh | pci_irq_enable: [36mdev 0x118004 [0m [0m [32mankh | pci_irq_enable: [36mirq 11, pin 1, devfn 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1mdevfn 0, pin 0 [0m [0m [32mankh | ddekit_pci_irq_enable: [32;1ml4vbus_pci_irq_enable() = 11 [0m [0m [32mankh | IRQ: set irq type of 11 to 4 [0m [32mankh | enable_dev: 0 [0m [32mankh | <6>eth0: RTL-8139C+ at 0x109000, 0x11615cM, IRQ 11 [0m [32mankh | unimplemented: pci_set_master [0m [32mankh | <6>pcnet32.c:v1.35 21.Apr.2008 tsbogend(a)alpha.franken.de [0m [32mankh | <6>Intel(R) PRO/1000 Network Driver - version 7.3.21-k3-NAPI [0m [32mankh | <6>Copyright (c) 1999-2006 Intel Corporation. [0m [32mankh | open_network_devices() [0m [32mankh | opening lo [0m [32mankh | <6>device lo entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | opening eth0 [0m [32mankh | <6>device eth0 entered promiscuous mode [0m [32mankh | set interface to promiscuous mode. [0m [32mankh | Thread 0x85 for IRQ 11 [0m [32mankh | <6>eth0: link up, 100Mbps, full-duplex, lpa 0x05E1 [0m [32mankh | Opened 2 network devices. [0m [32mankh | lo IRQ: 0x00 MAC: 00:00:00:00:00:00 MTU: 16436 [0m [32mankh | eth0 IRQ: 0x0B MAC: 00:E0:4C:C6:45:F4 MTU: 1500 [0m [32mankh | Registered @ registry. [0m [32mankh | Gooood Morning Ankh-Morpoooooork! TID = 0x5a [0m [32mankh | Creating session factory. [0m [32mankh | Configuration: debug,promisc,device=eth0,shm=shm_morpork,bufsize=16384,phys_mac [0m [32mankh | Debug mode ON. [0m [32mankh | Using promiscuous mode. [0m [32mankh | Device 'eth0' requested. [0m [32mankh | SHM area 'shm_morpork' requested. [0m [32mankh | Buffer size: 16384 [0m [32mankh | Physical MAC requested. [0m [32mankh | shmc_create: 0 [0m [32mankh | Created shmc area 'shm_morpork' [0m [32mankh | Assigning MAC address: 00:E0:4C:C6:45:F4 [0m [36mmorpork | Using shm area: 'shm_morpork' [0m [36mmorpork | argv[2] = '16384' [0m [36mmorpork | My TID = 0x93 [0m [36mmorpork | Attached shm area 'shm_morpork': 0 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'tx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9b, TX 9c [0m [36mmorpork | buf @ 0x301c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | add_chunk: area 0x10555c0, name 'rx_ring', size 16420 [0m [36mmorpork | SND: signal RX 9d, TX 9e [0m [36mmorpork | buf @ 0x3074, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | SEND RB @ 0x3018 RECV RB @ 0x3070 INFO @ 0x30c8 [0m [32mankh | l4shmc_attach("shm_morpork") = 0 [0m [32mankh | Shm_chunk::get(0xcf98, "info", 36) [0m [32mankh | ... = 0xcec8 [0m [32mankh | RCV: signal RX 9d, TX 9e [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcd3c, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner 0, name rx_ring, signal rx_signal [0m [32mankh | head @ 0x16c07c, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x16c09d [0m [32mankh | SND: attaching to signal 9e (443000) [0m [32mankh | buf @ 0x16c07c [0m [36mmorpork | activated Ankh connection. [0m [32mankh | xmit thread started, data @ 0xcf38, TID: 0xa0 [0m [32mankh | RCV: signal RX 9b, TX 9c [0m [32mankh | RCV: buf size 16420 [0m [32mankh | buf @ 0xcf04, area 0xcf98 (shm_morpork), size 16420 [0m [32mankh | owner ffffffff, name tx_ring, signal tx_signal [0m [32mankh | head @ 0x168030, lock state 'unlocked', data size 16384 [0m [32mankh | next_rd 0 next_wr 0 filled 0, data @ 0x168051 [0m [32mankh | RCV: attaching to signal 9b (448000) [0m [32mankh | 16384 ... 16384 [0m [36mmorpork | RCV: signal RX 9b, TX 9c [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x3114, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name tx_ring, signal tx_signal [0m [36mmorpork | head @ 0x103030, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x103051 [0m [36mmorpork | SND: attaching to signal 9c (41c000) [0m [36mmorpork | buf @ 0x103030 [0m [36mmorpork | sender: 0x3100 [0m [36mmorpork | RCV: signal RX 9d, TX 9e [0m [36mmorpork | RCV: buf size 16420 [0m [36mmorpork | buf @ 0x317c, area 0x10555c0 (shm_morpork), size 16420 [0m [36mmorpork | owner 0, name rx_ring, signal rx_signal [0m [36mmorpork | head @ 0x10707c, lock state 'unlocked', data size 16384 [0m [36mmorpork | next_rd 0 next_wr 0 filled 0, data @ 0x10709d [0m [36mmorpork | RCV: attaching to signal 9d (41e000) [0m [36mmorpork | receiver: 0x3168 [0m [36mmorpork | Got assigned MAC: 00:E0:4C:C6:45:F4 [0m [36mmorpork | info @ 0x10b0c8 [0m [36mmorpork | 00:E0:4C:C6:45:F4 MTU 1500 [0m [36mmorpork | RX packets: 0 dropped: 0 [0m [36mmorpork | TX packets: 0 dropped: 0 [0m [36mmorpork | RX bytes: 0 TX bytes: 0 [0m [36mmorpork | recv->wait_for_data(); [0m kind regards, ayad

3 8

Ankh Examples
by Ayad Mostafa 08 Apr '14

08 Apr '14

Hi, i also tried it using qemu development branch(version v2.0-rc0), but it is still not working. best regards ayad

1 0

newbie - trying to build
by Jack Andrews 06 Apr '14

06 Apr '14

Hi, Sorry if this is not the right forum. I'm following https://os.inf.tu-dresden.de/fiasco/build.html and i could build fiasco just fine. I made a couple of guesses about how to build L4Re because I couldn't find much info: jack@uv:~/fiasco/src/l4$ mkdir mybuild jack@uv:~/fiasco/src/l4$ make grub2iso E=hello O=mybuild MODULE_SEARCH_PATH=~/fiasco/src/kernel/fiasco/mybuild/ Processing entry 'hello' Could not find 'bootstrap' with path '/home/jack/fiasco/src/kernel/fiasco/mybuild/:/home/jack/fiasco/src/l4/mybuild/bin/amd64_opteron:/home/jack/fiasco/src/l4/mybuild/bin/amd64_opteron/l4f:/home/jack/fiasco/src/l4/mybuild/lib/amd64_opteron:/home/jack/fiasco/src/l4/mybuild/lib/amd64_opteron/l4f' make: *** [grub2iso] Error 1 I find bootstrap.o, but no 'bootstrap': jack@uv:~/fiasco/src/l4$ find ../kernel/fiasco/mybuild/ -name bootstrap\* ../kernel/fiasco/mybuild/bootstrap.o I have googled, including this list, but I haven't found the magic combination of words to get the answer. Thanks, jack. This is the kernel globalconfig.out: # # Automatically generated file; DO NOT EDIT. # Fiasco configuration # # # Target configuration # # CONFIG_IA32 is not set CONFIG_AMD64=y # CONFIG_ARM is not set CONFIG_PF_PC=y CONFIG_ABI_VF=y CONFIG_AMD64_K8=y # CONFIG_AMD64_CORE2 is not set # CONFIG_AMD64_ATOM is not set # CONFIG_AMD64_K10 is not set # CONFIG_CPU_VIRT is not set CONFIG_SCHED_APIC=y # CONFIG_WORKAROUND_AMD_FPU_LEAK is not set # # Kernel options # CONFIG_MP=y CONFIG_MP_MAX_CPUS=4 CONFIG_CONTEXT_4K=y # CONFIG_FINE_GRAINED_CPUTIME is not set CONFIG_SCHED_FIXED_PRIO=y # CONFIG_SCHED_WFQ is not set # CONFIG_SCHED_FP_WFQ is not set # CONFIG_DISABLE_VIRT_OBJ_SPACE is not set CONFIG_VIRT_OBJ_SPACE=y # # Debugging # # CONFIG_INLINE is not set CONFIG_NDEBUG=y CONFIG_NO_FRAME_PTR=y # CONFIG_STACK_DEPTH is not set # CONFIG_LIST_ALLOC_SANITY is not set # CONFIG_BEFORE_IRET_SANITY is not set # CONFIG_IRQ_SPINNER is not set # CONFIG_WATCHDOG is not set # CONFIG_SERIAL is not set # CONFIG_JDB is not set # CONFIG_POWERSAVE_GETCHAR is not set # CONFIG_WARN_NONE is not set CONFIG_WARN_WARNING=y # CONFIG_WARN_ANY is not set # # Compiling # CONFIG_CC="gcc" CONFIG_CXX="g++" CONFIG_HOST_CC="gcc" CONFIG_HOST_CXX="g++" # CONFIG_MAINTAINER_MODE is not set CONFIG_LABEL="" CONFIG_EXPERIMENTAL=y CONFIG_BIT64=y CONFIG_WARN_LEVEL=1 CONFIG_XARCH="amd64" CONFIG_IA32_TARGET="AMD Opteron" CONFIG_ABI="vf"

4 5

std::cin in Fiasco/L4Re (with 'make qemu')
by Emanuel Berg 03 Apr '14

03 Apr '14

How do I use std::cin in Fiasco/L4Re? The software compiles and links fine, only during execution (with 'make qemu'), this crashes it: Global_Scheduler::Global_Scheduler (bool read_from_file) : period_left(0), number_of_schedulers(0) { if (not read_from_file) { std::cout << "Global scheduler period: "; std::cin >> period; // ... There is no error, but there is no halt to execution (to wait for input), and the value "read" (to period) is inconsistent. -- underground experts united: http://user.it.uu.se/~embe8573

3 8

step forward on compilation
by Emanuel Berg 03 Apr '14

03 Apr '14

First: On - let's see - Fri, 28 Mar 2014 02:02:52 +0100 - I sent a message to this list with the subject "again, must know mechanics of compile" - previously, I was able to send to this list, but as for now, I can't find that message either in the group or in the web archive [1]. (I see my old posts though.) I looked for that message because I thought I build on that thread, that's how I noticed it wasn't there (?). Anyway, as for including header files, I found that you can indeed make a directory at the base package level, called "include" - and put a Makefile in it just like it is done for the other projects (but I'm unsure what the Makefile actually does - perhaps if you specify the include directory as a target in the *package* Makefile, you can drop it?). And, you can't use the C++ ".hh" extension, but ".h" works, if you include them like this: #include <l4/hs/task_scheduler.h> if your package is named "hs". In effect, this is quite the opposite of the #include "task_scheduler.hh", and then the -I flag to the compiler. As for -std=c++11, I found that you can pass that not with CFLAGS, but close - this works: CXXFLAGS += -std=c++11 [1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/thread.html -- underground experts united: http://user.it.uu.se/~embe8573

4 9

[Correction] Can't Fiasco.OC support multi-core-processor ?
by Taeung 03 Apr '14

03 Apr '14

Hello , L4 hackers I'm so sorry.. I amend my a question. Question 'Can't Fiasco.OC support multi-core-processor ?' is wrong.. Again, I've checked my thread and I've tested it. It's problem is about ramdisk or 'dd' command. I guess data in SD-card is some wrong. - Taeung -

1 0

Can't Fiasco.OC support multi-core-processor ?
by Taeung 03 Apr '14

03 Apr '14

Hello, L4 hackers :-) Always, I'm obliged to you. I have a question. When I configured Fiasco.OC containing option which is 'unable multi processor support' , I've succeeded booting (L4 linux + L4/Fiasco) on Freescale imx6q_sabre_sd(Cortex-a9). And, I've configured Fiasco.OC as follows.. , again. ========================= [*] Enable multi processor support (4) Maximal supported number of CPUs (NEW) [*] Fine-grained CPU time ========================= But I could not booting it successfully. It's stop at '*CPU[3]: goes to idle loop*' What's the problem ? Log I met is such as.... ========================= Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: r62 compiled with gcc 4.6.4 for i.MX6 [] Build: #1 Thu Apr 3 13:48:45 KST 2014 Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) Allocate 2448 bytes (2KB) for CPU[4] local storage (offset=1193508, 0xf11ea000-0xf11ea990) Number of CPUs: 4 Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) done. Allocate 2448 bytes (2KB) for CPU[1] local storage (offset=1195508, 0xf11ec000-0xf11ec990) MDB: use page size: 20 Cache config: ON ... (ellipsis) MOE: Hello world Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) CPU[1]: goes to idle loop Allocate 2448 bytes (2KB) for CPU[2] local storage (offset=1182508, 0xf11d9000-0xf11d9990) ... (ellipsis) BOOTFS: [11210000Per_cpu_data_alloc: (orig: 0xf0056af8-0xf0057488) -CPU[2]: goes to idle loop 1Allocate 2448 bytes (2KB) for CPU[3] local storage (offset=1158508, 0xf11af000-0xf11af990) 1Cache config: ON 5ID_PFR[01]: 00001231 000000115 ID_[DA]FR0: 00010444 00000000 1ID_MMFR[04]: 00100103 20000000 01230000 00102111 494] [C:508000] vmlinuz.arm BOOTFS: [11552000-11852000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx_xs.cfg MOE: Starting: rom/ned rom/l4lx_xs.cfg MOE: loading 'rom/ned' Ned says: Hi World! L4Re: unhandled exception: pc=0x10211d4 *CPU[3]: goes to idle loop* ========================= - Taeung -

1 0

Custom ramdisk
by Tim Komarov 01 Apr '14

01 Apr '14

Hello, L4 hackers! I use Pandaboard for my practising with Fiasco.OC and L4Linux. 1) I got a problem with booting L4Linux with my own ramdisk. When I use 18 mb ramdisk, I got the following error: reading image.elf 24691072 bytes read ## Starting application at 0x81000000 ... ... ,,,[Everything is usual] ,,, NET: Registered protocol family 17 List of all partitions: No filesystem could mount root, tried: ext3 ext2 ext4 cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.0-l4 #1 [<0200c624>] (unwind_backtrace+0x0/0xec) from [<020054c0>] (show_stack+0x10/0x14) [<020054c0>] (show_stack+0x10/0x14) from [<0222e63c>] (panic+0x7c/0x1b8) [<0222e63c>] (panic+0x7c/0x1b8) from [<022f2c40>] (mount_block_root+0x25c/0x29c) [<022f2c40>] (mount_block_root+0x25c/0x29c) from [<022f2f44>] (prepare_namespace+0x160/0) [<022f2f44>] (prepare_namespace+0x160/0x1b4) from [<022f2894>] (kernel_init_freeable+0x1) [<022f2894>] (kernel_init_freeable+0x174/0x1b8) from [<0222ccf0>] (kernel_init+0x8/0x118) [<0222ccf0>] (kernel_init+0x8/0x118) from [<020077d4>] (ret_from_fork+0x14/0x20) [<020077d4>] (ret_from_fork+0x14/0x20) from [<00000000>] ( (null)) panic: going to sleep forever, bye To make ramdisk I simply create a file, write 18 Mb of zeroes to it (with dd), create in that file ext2 partition and copy there files from ramdisk-arm.rd So, what should I do to get a proper working ramdisk? 2) Even more. If I create 20 mb ramdisk, I got this: reading image.elf 26788224 bytes read ## Starting application at 0x00000000 ... Than the booting hangs. Why so? Looking forward for your help, guys! Best wishes, Tim

2 3

I share attached this guide with you.
by Taeung 28 Mar '14

28 Mar '14

Hello, l4 hackers :-) !! I've promised a guide Document to you. It is "L4 / Fiasco porting guide on Freescale i.MX6 Quad SABRE SD(ARMv7)". I have had help from L4 Hackers. So, I was able to do booting "L4 Linux + L4/Fiasco.OC" on this board. I'm particularly grateful to /Tim Komarov /and /Ademd Ammar/ , /Adam Lackorzynski/, /Matthias Lange/. I don't know how much this document will help some beginner. I've thought that the guide Document might help them. But I share this document because I have had a big help from them. It is small but I am delighted to be able to contribute this open source community. :-) If it's contents is wrong , let me know your feedback. - Taeung -

3 2

hello/l4/fiasco.oc for realview pbxa9
by Alexis Fajardo Moya 27 Mar '14

27 Mar '14

Hello, recently I tried to run hello program in top of l4/fiasco.oc for exynos 4412 platform, but qemu doest'n have any platform that support it (at least my installed version) none empty machine collie Collie PDA (SA-1110) nuri Samsung NURI board (Exynos4210) smdkc210 Samsung SMDKC210 board (Exynos4210) connex Gumstix Connex (PXA255) verdex Gumstix Verdex (PXA270) highbank Calxeda Highbank (ECX-1000) midway Calxeda Midway (ECX-2000) integratorcp ARM Integrator/CP (ARM926EJ-S) (default) kzm ARM KZM Emulation Baseboard (ARM1136) mainstone Mainstone II (PXA27x) musicpal Marvell 88w8618 / MusicPal (ARM926EJ-S) n800 Nokia N800 tablet aka. RX-34 (OMAP2420) n810 Nokia N810 tablet aka. RX-44 (OMAP2420) sx1 Siemens SX1 (OMAP310) V2 sx1-v1 Siemens SX1 (OMAP310) V1 cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310) 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 akita Akita PDA (PXA270) spitz Spitz PDA (PXA270) borzoi Borzoi PDA (PXA270) terrier Terrier PDA (PXA270) lm3s811evb Stellaris LM3S811EVB lm3s6965evb Stellaris LM3S6965EVB tosa Tosa PDA (PXA255) versatilepb ARM Versatile/PB (ARM926EJ-S) versatileab ARM Versatile/AB (ARM926EJ-S) vexpress-a9 ARM Versatile Express for Cortex-A9 vexpress-a15 ARM Versatile Express for Cortex-A15 xilinx-zynq-a9 Xilinx Zynq Platform Baseboard for Cortex-A9 z2 Zipit Z2 (PXA27x) For that reason I try to test hello/l4/fiasco.oc in realview pbxa9 platform. I create build directories for l4 and fiasco, configure and compile them for realview pbxa9 platform. Then I execute the following command: ~/build/l4.realview$ make -j2 elfimage E=hello MODULE_SEARCH_PATH=~/build/foc.realview SYSTEM_TARGET=/usr/local/arm-2012.03/bin/arm-none-linux-gnueabi- and this was the result: make[1]: se ingresa al directorio «/home/afmoya/src/l4» =========== Updating RAM_BASE for platform rv_pbx to 0x70000000 ========= ... Regenerating RAM_BASE settings make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ==> Linking sigma0 ==> "sigma0" built ==> Installing sigma0 to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ==> Linking moe ==> "moe" built ==> Installing moe to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Building .general.d ... Building Makefile.inc Building entry "hello". Merging image /home/afmoya/build/foc.realview/fiasco to mod00 [344kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/sigma0 to mod01 [340kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/moe to mod02 [2396kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/l4re to mod03 [1227kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/hello to mod04 [887kB] make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Generating bootstrap.ld ... Compiling exec.o ... Compiling module.o ... Compiling ARCH-arm/crt0.o ... Compiling region.o ... Compiling startup.o ... Compiling init_kip_v2.o ... Compiling init_kip_v4.o ... Compiling libc_support+.o ... Compiling patch.o ... Compiling koptions.o ... Compiling platform/rv.o ... Compiling loader_mbi.o ... Compiling ARCH-arm/reboot.o ==> Linking bootstrap.elf ==> Post-processing bootstrap.elf ==> "bootstrap.elf" built ==> Installing bootstrap.elf in image directory ==> Installing bootstrap.elf to local build-tree ==> Installing bootstrap_hello to local build-tree ==> Installing bootstrap_hello.elf to local build-tree ==> Installing bootstrap_hello in image directory ==> Installing bootstrap_hello.elf in image directory Image size(s) in bytes: bootstrap_hello.elf: 971420 Start address: 0x71000000 --> Build-Nr: 2 make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[1]: se sale del directorio «/home/afmoya/src/l4» After that I execute: ~/build/l4.realview/images$ qemu-system-arm -M realview-pbx-a9 -kernel bootstrap_hello.elf -m 256 -serial mon:stdio -nographic this was the result of the execution: oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory audio: Failed to create voice `lm4549.out' L4 Bootstrapper Build: #2 mié mar 26 13:02:05 CDT 2014, 4.6.3 Scanning up to 256 MB RAM Memory size is 256MB (70000000 - 7fffffff) RAM: 0000000070000000 - 000000007fffffff: 262144kB Total RAM: 256MB mod04: 710cb000-710e4580: hello mod03: 710b1000-710ca460: l4re mod02: 71077000-710b062c: moe mod01: 7106d000-71076378: sigma0 mod00: 71017000-7106cedc: fiasco Moving up to 5 modules behind 71100000 moving module 00 { 71017000-7106cedb } -> { 711ce000-71223edb } [351964] moving module 03 { 710b1000-710ca45f } -> { 71100000-7111945f } [103520] moving module 04 { 710cb000-710e457f } -> { 71100000-7111957f } [103808] ...and that was all. No "Hello world". After that I kill the qemu process. What 's the problem with my procedure? Sorry for the huge amount of lines of my email. Best regards! Alexis.

2 6