- l4-hackers - example.com Site

Debugging Fiasco OC + L4Re + L4Linux together
by Mahdi Aichouch 09 Jun '15

09 Jun '15

Hello, I tried to debug Fiasco OC + L4Re + L4Linux using a DS-5 IDE and a DSTREAM JTAG on an i.MX 6 device. I was able to do a step-by-step through the source code of L4RE until I reach the " *virtual* *void* boot_kernel(unsigned long entry) " function in support.h (see screenshot 1) which is the function in L4Re that enters the Fiasco kernel, from there when I execute a "step into" action in order to execute the next instruction which is in Fiasco kernel the debugger go into "running" mode (see screenshot 2). I am unable to do a step-by-step walk neither in the Fiasco kernel nor in l4linux source code. Stopping the debugger after that do only give a disassembly information. Is it possible to debug all the Fiasco OC + L4Re + L4Linux together? Are there any debugger configurations that I might be missing? Many thanks in advance. Best regards, Mahdi

2 1

Thread monitoring
by Biermans Joeri 09 Jun '15

09 Jun '15

Hey everyone, Is there a way available to perform some thread monitoring? Like for instance get some information about on which CPU a thread is running, when they're suspended, completed, etc. Thanks in advance and kind regards, Joeri

2 1

Using a second Ethernet connector in L4Linux
by Mahdi Aichouch 03 Jun '15

03 Jun '15

Hello, I have a Freescale i.MX 6 Sabre SD board. It is equipped with one Ethernet RJ45 connector. I need to add a second Ethernet RJ45 connector to the board. The board has a micro-USB OTG port that allow to connect a plugable USB OTG Micro-B to Ethernet adapter like for instance this one: http://plugable.com/products/usb2-otge100 I would like to know if L4Linux might access such a second Ethernet device connected through micro-USB. Does anyone has tried this before. Could someone points me to a tutorial or a guide that shows what are the configurations steps that I should follow to build up a working test case. Thank you very much in advance. Best regards, Mahdi

2 1

Cann't access git://git.l4android.org/build_script.git
by 刘海剑 02 Jun '15

02 Jun '15

When I run this command, git clone git://git.l4android.org/build_script.git, I got some error info: fatal: unable to connect to l4android.org: l4android.org[0: 141.76.48.99]: errno=Connection refused Thanks.

2 1

Implementing a few real time scheduling algorithms on Fiasco.OC
by Biermans Joeri 30 May '15

30 May '15

Hi everyone, I'm a student at the university of Antwerp and I'm currently working on my master's thesis. My project is about comparing the performance of a few global multicore scheduling algorithms (G-RM, G-EDF, ...) on an embedded system. A part of my thesis is to make an implementation on a real embedded system equipped with a quadcore processor (i.MX6). To do that I need an RTOS. Fiasco with the l4re at a first sight seems an interesting candidate. To test the performance of the above algorithms I will schedule a bunch of randomly generated tasksets comprising some periodic tasks having implicit deadlines* with each of the algorithms and try to detect if any deadlines are missed. * Such a task is executed repeatedly after a fixed amount of time and its deadline is equal to its period, which is the point of time when the next invocation of the task takes place. This brings me to my first question: Would this be achievable with the fiasco kernel? I've been trying to interpret the project of the fiasco kernel during the last days, but this seems easier said than done. As a first step I've been trying to figure out how the scheduler works and how exactly the scheduling policies are implemented. (I have read somewhere the current scheduling policy is fixed priority round robin) Is there perhaps a more documented version of the code or an overview of the different classes, their functions and the way they interact available? It's really hard to figure out a bunch of code without any leads on how exactly the project has been implemented. Besides that I don't really have a clue about how to start developing on the fiasco kernel. Some tips about how to start working on the kernel are always welcome. Has anyone got experience with developing on the fiasco kernel? It would be nice to get some directions on this matter because I'm quite stuck on this. Thanks in advance! Kind regards, Joeri

3 2

Booting error of L4Linux enabled SMP surpport
by Xiefeng (Stephen) 29 May '15

29 May '15

Hi all, I use entry L4Linux-mag-x86 in modules.list to start a L4Linux on L4Re successfully. The codes is l4re-snapshot-2014092821. L4Linux use x86-native_deconfig complie, use l4lx-gfx.cfg to start L4Linux. This config is just set one cpu for L4Linux. If I set l4x_cpus=2 in l4lx-gfx.cfg, use x86-mp_vPCI_defconfig and set CONFIG_NR_CPUS=2 to compile the L4Linux, when I start L4Linux, a kernel panic happened: l4linux | Loading: rom/ramdisk-x86.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 88d70000 to 89070000 [3072KiB] l4linux | rtc not found l4linux | l4lx_thread_create: Created thread 41f (timer0) (u:b3000a00, v:00000000, sp:008e1fa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x414bad l4linux | WARNING: Unknown rdmsr: 00000186 at 0x85e1d6 l4linux | WARNING: Unknown rdmsr: 00000187 at 0x85e1d6 l4linux | WARNING: Unknown wrmsr: 000000c1 at 0x85e2a7 l4linux | Launching cpu1 on pcpu 1 at 0x4024e0 l4linux | l4lx_thread_create: Created thread 420 (cpu1) (u:b3000800, v:b3000600, sp:008c7fa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x414bad l4linux | l4lx_thread_create: Created thread 424 (timer1) (u:b3000400, v:00000000, sp:008e3fa8) l4linux | Spurious IPI on CPU0: 4 l4linux | panic: going to sleep forever, bye Has anyone encountered this problem? Stephen

3 4

Boot L4Linux Error
by 刘海剑 28 May '15

28 May '15

Hello everyone, after building l4re-snapshot-2014092821 on my Ubuntu-14.04(32bit), I run L4Linux-mag-x86, and get some errors. The information is as follows: qemu-system-i386 -kernel /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/bootstrap -append "bootstrap -modaddr 0x01100000" -initrd "/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco -serial_esc,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/l4re ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/ned ,/home/lhj/L4Linux/l4re-snapshot-2014092821/src/l4/conf/examples/l4lx-gfx.cfg ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/io ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/fb-drv ,/home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/mag ,/home/lhj/L4Linux/l4re-snapshot-2014092821/files/cfg/x86-legacy.devs ,/home/lhj/L4Linux/l4re-snapshot-2014092821/src/l4/conf/examples/l4lx-x86.io ,/tmp/QEVRyiQlKD/vmlinuz ,/home/lhj/L4Linux/l4re-snapshot-2014092821/files/ramdisk-x86.rd " -m 256 -serial stdio L4 Bootstrapper Build: #1 Tue May 26 16:48:47 CST 2015, x86-32, 4.8.2 RAM: 0000000000000000 - 000000000009fbff: 639kB RAM: 0000000000100000 - 000000000fffdfff: 261112kB Total RAM: 255MB Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco -serial_esc Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 Scanning /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg need 1368 bytes to copy MBI reserved 1368 bytes at 0x2000 Moving up to 13 modules behind 1100000 moving module 12 { 2266400-25663ff } -> { 3085000-3384fff } [3145728] moving module 11 { 1e8e400-2265919 } -> { 2cad000-3084519 } [4027674] moving module 10 { 1e8d400-1e8d626 } -> { 2cac000-2cac226 } [551] moving module 09 { 1e8c400-1e8c63e } -> { 2cab000-2cab23e } [575] moving module 08 { 1a29400-1e8ba0b } -> { 2848000-2caa60b } [4597260] moving module 07 { 189f400-1a28598 } -> { 26be000-2847198 } [1610137] moving module 06 { 98e400-189ee03 } -> { 17ad000-26bda03 } [15796740] moving module 05 { 98d400-98d96a } -> { 17ac000-17ac56a } [1387] moving module 04 { 736400-98ce09 } -> { 1555000-17aba09 } [2451978] moving module 03 { 5fc400-735b2c } -> { 141b000-155472c } [1283885] moving module 02 { 3a9400-5fb7eb } -> { 11c8000-141a3eb } [2434028] moving module 01 { 353400-3a928a } -> { 1172000-11c7e8a } [351883] moving module 00 { 2e1400-352677 } -> { 1100000-1171277 } [463480] Loading /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco Loading re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 Loading /l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe find kernel info page... found kernel info page at 0x400000 Regions of list 'regions' [ 0, fff] { 1000} Arch BIOS [ 1000, 1fff] { 1000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 2000, 2557] { 558} Root mbi_rt [ 9fc00, 9ffff] { 400} Arch BIOS [ f0000, fffff] { 10000} Arch BIOS [ 100000, 10b193] { b194} Sigma0 re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/sigma0 [ 140000, 193363] { 53364} Root /l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe [ 2d0400, 2df43f] { f040} Boot bootstrap [ 300000, 38ffff] { 90000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 400000, 475fff] { 76000} Kern /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco [ 141b000, 3384fff] { 1f6a000} Root Module [ fffe000, fffffff] { 2000} Arch BIOS [ fffc0000, ffffffff] { 40000} Arch BIOS API Version: (87) experimental Sigma0 config ip:0010021c sp:00000000 Roottask config ip:001401f6 sp:00000000 Starting kernel /L4Linux/l4re-snapshot-2014092821/obj/fiasco/ia32/fiasco at 003007b8 Welcome to Fiasco.OC (ia32)! L4/Fiasco.OC ia32 microkernel (C) 1998-2013 TU Dresden Rev: unknown compiled with gcc 4.8.2 for Intel Pentium [] Build: #1 Tue May 26 16:33:03 CST 2015 Performance-critical config option(s) detected: CONFIG_NDEBUG is off CONFIG_NO_FRAME_PTR is off Superpages: yes Kmem:: cpu page at fffd000 (4096Bytes) ACPI-Init ACPI: RSDP[0xf09e0]r00 OEM:BOCHS. ACPI: RSDT[0x203ffbc1]r01 OEM:BOCHS. OEMTID:BXPCRSDT ACPI: FACP[0x203ff1c0]r01 OEM:BOCHS. OEMTID:BXPCFACP ACPI: SSDT[0x203ff234]r01 OEM:BOCHS. OEMTID:BXPCSSDT ACPI: APIC[0x203ffb11]r01 OEM:BOCHS. OEMTID:BXPCAPIC ACPI: HPET[0x203ffb89]r01 OEM:BOCHS. OEMTID:BXPCHPET IO-APIC: MADT = 0x203ffb11 IO-APIC[ 0]: struct: 0x203ffb45 adr=fec00000 IO-APIC[ 0]: pins 24 PIN[ 0m]: vector=20, del=0, dm=physical, dest=0 (high, edge) PIN[ 1m]: vector=21, del=0, dm=physical, dest=0 (high, edge) PIN[ 2m]: vector=22, del=0, dm=physical, dest=0 (high, edge) PIN[ 3m]: vector=23, del=0, dm=physical, dest=0 (high, edge) PIN[ 4m]: vector=24, del=0, dm=physical, dest=0 (high, edge) PIN[ 5m]: vector=25, del=0, dm=physical, dest=0 (high, edge) PIN[ 6m]: vector=26, del=0, dm=physical, dest=0 (high, edge) PIN[ 7m]: vector=27, del=0, dm=physical, dest=0 (high, edge) PIN[ 8m]: vector=28, del=0, dm=physical, dest=0 (high, edge) PIN[ 9m]: vector=29, del=0, dm=physical, dest=0 (high, edge) PIN[10m]: vector=2a, del=0, dm=physical, dest=0 (high, edge) PIN[11m]: vector=2b, del=0, dm=physical, dest=0 (high, edge) PIN[12m]: vector=2c, del=0, dm=physical, dest=0 (high, edge) PIN[13m]: vector=2d, del=0, dm=physical, dest=0 (high, edge) PIN[14m]: vector=2e, del=0, dm=physical, dest=0 (high, edge) PIN[15m]: vector=2f, del=0, dm=physical, dest=0 (high, edge) PIN[16m]: vector=30, del=0, dm=physical, dest=0 (high, edge) PIN[17m]: vector=31, del=0, dm=physical, dest=0 (high, edge) PIN[18m]: vector=32, del=0, dm=physical, dest=0 (high, edge) PIN[19m]: vector=33, del=0, dm=physical, dest=0 (high, edge) PIN[20m]: vector=34, del=0, dm=physical, dest=0 (high, edge) PIN[21m]: vector=35, del=0, dm=physical, dest=0 (high, edge) PIN[22m]: vector=36, del=0, dm=physical, dest=0 (high, edge) PIN[23m]: vector=37, del=0, dm=physical, dest=0 (high, edge) IO-APIC: dual 8259: yes IO-APIC: ovr[ 0] 00 -> 2 0 IO-APIC: ovr[ 1] 05 -> 5 d IO-APIC: ovr[ 2] 09 -> 9 d IO-APIC: ovr[ 3] 0a -> a d IO-APIC: ovr[ 4] 0b -> b d Allocate cpu_mem @ 0xfdbf9400 FPU0: SSE Local APIC[00]: version=11 max_lvt=5 APIC ESR value before/after enabling: 00000000/00000000 Using the Local APIC timer on vector 90 (Periodic Mode) for scheduling ACPI: FACS phys=fffe000 virt=0x203fe000 ACPI: HW sig=0 SERIAL ESC: allocated IRQ 4 for serial uart Absolute KIP Syscalls using: Sysenter Enable MSI support: chained IRQ mgr @ 0xfdbf9150 SERIAL ESC: allocated IRQ 4 for serial uart Not using serial hack in slow timer handler. CPU[0]: GenuineIntel (6:6:3:0)[00000663] Model: QEMU Virtual CPU version 2.0.0 at 2507MHz 32 KB L1 I Cache (8-way associative, 64 bytes per line) 32 KB L1 D Cache (8-way associative, 64 bytes per line) 2048 KB L2 U Cache (8-way associative, 64 bytes per line) Freeing init code/data: 24576 bytes (6 pages) Calibrating timer loop... done. MDB: use page size: 22 MDB: use page size: 12 SIGMA0: Hello! KIP @ 400000 Found Fiasco: KIP syscalls: yes allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:2000;2fff] [0:3000;9efff] [0:10c000;13ffff] [4:140000;193fff] [0:194000;3fffff] [0:470000;141afff] [4:141b000;3384fff] [0:3385000;eb8afff] IOMEM:---------------------- [0:0;fff] [0:9f000;fffff] [0:fffe000;febfffff] [0:fec01000;fedfffff] [0:fee01000;ffffffff] IO PORTS-------------------------- [0:0;fffffff] MOE: Hello world MOE: found 207796 KByte free memory MOE: found RAM from 2000 to eb8b000 MOE: allocated 235 KByte for the page array @0x3000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [141b000-155472d] [C:503000] l4re BOOTFS: [1555000-17aba0a] [C:504000] ned BOOTFS: [17ac000-17ac56b] [C:505000] l4lx-gfx.cfg BOOTFS: [17ad000-26bda04] [C:506000] io BOOTFS: [26be000-2847199] [C:507000] fb-drv BOOTFS: [2848000-2caa60c] [C:508000] mag BOOTFS: [2cab000-2cab23f] [C:509000] x86-legacy.devs BOOTFS: [2cac000-2cac227] [C:50a000] l4lx-x86.io BOOTFS: [2cad000-308451a] [C:50b000] vmlinuz BOOTFS: [3085000-3385000] [C:50c000] ramdisk-x86.rd MOE: cmdline: /home/lhj/L4Linux/l4re-snapshot-2014092821/obj/l4/x86/bin/x86_586/l4f/moe rom/l4lx-gfx.cfg MOE: Starting: rom/ned rom/l4lx-gfx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx-gfx.cfg' io | Io service io | Find root Pointer io | Find root Pointer: f09e0 io | ACPI: RSDP 0xf09e0 00014 (v00 BOCHS ) io | ACPI: RSDT 0xffffbc1 00034 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001) io | ACPI: FACP 0xffff1c0 00074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001) io | ACPI: DSDT 0xfffe040 01180 (v01 BOCHS BXPCDSDT 00000001 BXPC 00000001) io | ACPI: FACS 0xfffe000 00040 io | ACPI: SSDT 0xffff234 008DD (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001) io | ACPI: APIC 0xffffb11 00078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001) io | ACPI: HPET 0xffffb89 00038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) io | Parsing all Control Methods: io | Table [DSDT](id 0001) - 144 Objects with 18 Devices 52 Methods 8 Regions io | Parsing all Control Methods: io | Table [SSDT](id 0002) - 155 Objects with 32 Devices 42 Methods 1 Regions io | tbxfload-0274 [02] TbLoadNamespace : ACPI Tables successfully acquired io | evxfevnt-0175 [02] Enable : Transition to ACPI mode successful io | evgpeblk-0523 [04] EvCreateGpeBlock : GPE 00 to 0F [_GPE] 2 regs on int 0x9 io | Completing Region/Field/Buffer/Package initialization:..................................... io | Initialized 9/9 Regions 2/2 Fields 21/21 Buffers 5/5 Packages (308 nodes) io | Initializing Device/Processor/Thermal objects by executing _INI methods: io | Executed 0 _INI methods requiring 1 _STA executions (examined 53 objects) io | ACPICA-Version:20121018, System in ACPI MODE, 32bit timer io | evgpeblk-0615 [03] EvInitializeGpeBlock : Enabled 16 GPEs in this block io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | IRQ [00000000000000-00000000000000 1] none (32bit) (align=0 flags=40201) io | rom/l4lx-x86.io:17.28-36: warning: could not find 'PNP0100' io | Ready. Waiting for request. mag | Hello from MAG fb-drv | Trying execution of ``set VBE mode'' using x86emu fb-drv | Found VESA BIOS version 3.0 fb-drv | OEM SeaBIOS VBE(C) 2011 fb-drv | VBE mode 0x117 successfully set. fb-drv | Framebuffer memory: phys: fc000000 - fc400000 fb-drv | virt: 400000 - 800000 fb-drv | Starting server loop mag | mapped frame buffer at 0x400000 mag | View::Info: mag | flags: 0 mag | size: 1024x768 pos: 0, 0 mag | bytes_per_line: 2048 mag | buffer_offset: 0 mag | RGBA(2): 5(11):6(5):5(0):0(0) mag | memory 400000-800000 mag | Plugin: Mag_client service started mag | Plugin: Frame-buffer service started mag | L4INPUT native mode activated mag | L4INPUT: !!! W A R N I N G !!! mag | L4INPUT: Please, do not use Fiasco's "-esc" with L4INPUT. mag | L4INPUT: !!! W A R N I N G !!! mag | serio: i8042 AUX port at 0x60,0x64 irq 12 mag | serio: i8042 KBD port at 0x60,0x64 irq 1 mag | input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1 mag | input: AT Translated Set 2 keyboard on isa0060/serio0 mag | connect "ImExPS/2 Generic Explorer Mouse", isa0060/serio1/input0 mag | connect "AT Translated Set 2 keyboard", isa0060/serio0/input0 l4linux | PH 0 (t: 1) offs=00001000 vaddr=00400000 vend=006dc000 l4linux | phys=00400000 ephys=006dc000 l4linux | f_sz=002dc000 memsz=002dc000 flgs=r-x l4linux | PH 1 (t: 1) offs=002dd000 vaddr=006dc000 vend=007d8000 l4linux | phys=006dc000 ephys=007d8000 l4linux | f_sz=00050f30 memsz=000fc000 flgs=rw- l4linux | PH 2 (t: 4) offs=0023cd64 vaddr=0063bd64 vend=0063bd88 l4linux | phys=0063bd64 ephys=0063bd88 l4linux | f_sz=00000024 memsz=00000024 flgs=--- l4linux | Starting binary at 0x400000, argc=6 argv=0xafff4f90 *argv=0xb1007ff4 argv0=rom/vmlinuz l4linux | External resolver is at 0xa8000730 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (lhj@ubuntu) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #1 Tue May 26 16:58:34 CST 2015 l4linux | Binary name: rom/vmlinuz l4linux | Linux kernel command line (5 args): mem=64M console=tty0 l4x_rd=rom/ramdisk-x86.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 00400000 - 007d8000 [3936 KiB]. l4linux | Areas: Text: 00400000 - 006dc000 [2928kB] (a bit longer) l4linux | Data: 006dc000 - 00706ac0 [170kB] l4linux | Initdata: 00709000 - 0072d000 [144kB] l4linux | BSS: 0072e000 - 007c2000 [592kB] l4linux | gs=43 fs=43 l4linux | Device scan: l4linux | Device: L4ICU l4linux | Device: PCI0 l4linux | Device: pci_l4x[0000] l4linux | PORT: 0000c040 - 0000c04f l4linux | PORT: 000001f0 - 000001f7 l4linux | PORT: 000003f6 - 000003f6 l4linux | IRQ: 0000000e - 0000000e l4linux | PORT: 00000170 - 00000177 l4linux | PORT: 00000376 - 00000376 l4linux | IRQ: 0000000f - 0000000f l4linux | Device: pci_l4x[0001] l4linux | IRQ: 0000000b - 0000000b l4linux | MEM: febc0000 - febdffff l4linux | PORT: 0000c000 - 0000c03f l4linux | Device scan done. l4linux | l4x_fiasco_gdt_entry_offset = 9 l4linux | rtc not found l4linux | WARNING: RTC server does not seem to be there! l4linux | l4lx_thread_create: Created thread 417 (cpu0) (u:b3000e00, v:b3000c00, sp:006ddfac) l4linux | main thread will be 417 l4linux | l4x_register_pointer_section: addr = 006dc000 size = 1032192 l4linux | section-with-init: Virt: 0x6dc000 to 0x7d7fff [1008 KiB] l4linux | section-with-init: Phys: 0x0090f000 to 0x00a0afff, [1008 KiB] l4linux | Main thread running, waiting... l4linux | WARNING: Unknown wrmsr: 0000008b at 0x411f0d l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 00400000 l4linux | Main memory: Virt: 0x800000 to 0x47fffff [65536 KiB] l4linux | Main memory: Phys: 0x03400000 to 0x073fffff, [65536 KiB] l4linux | l4x: vmalloc area: 04800000 - 0c800000 l4linux | Filling lower ptabs... l4linux | Done (1062 entries). l4linux | l4x_register_pointer_section: addr = 00400000 size = 2998272 l4linux | text: Virt: 0x400000 to 0x6dbfff [2928 KiB] l4linux | text: Phys: 0x00614000 to 0x008effff, [2928 KiB] l4linux | Loading: rom/ramdisk-x86.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 0c91b000 to 0cc1b000 [3072KiB] l4linux | rtc not found l4linux | l4lx_thread_create: Created thread 41f (timer0) (u:b3000a00, v:00000000, sp:0075bfa8) l4linux | WARNING: Unknown wrmsr: 0000008b at 0x411f0d l4linux | WARNING: Unknown rdmsr: 00000186 at 0x710579 l4linux | WARNING: Unknown rdmsr: 00000187 at 0x710579 l4linux | WARNING: Unknown wrmsr: 000000c1 at 0x71064a mag | Input: new pointer device (src='<Input_source userdata: 1D80C>' stream='userdata: 0x3abb4') mag | bus='i8042' vendor=0x2 product=0x6 version=0 mag | Input: new keyboard device (src='<Input_source userdata: 1D80C>' stream='userdata: 0x3b358') mag | bus='i8042' vendor=0x1 product=0x1 version=43841 And I printed my screen. See attached png-file. Thanks for any reply!

2 1

Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD
by Mahdi Aichouch 28 May '15

28 May '15

Hello, I tried to run L4Linux + Fiasco on a Freescale i.mx 6 Sabre SD board. The L4Linux is started but it stops at loading the ramdisk, as shown in the debug messages below. Does someone has an idea of what might be wrong. Thank you very much in advance. Best regards, Mahdi L4 Bootstrapper Build: #80 Wed May 27 18:22:31 CEST 2015, 4.8.3 20140320 (prerelease) Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118aa000-118e363f } -> { 1199a000-119d363f } [235072] moving module 01 { 118a0000-118a938b } -> { 11990000-1199938b } [37772] moving module 00 { 11848000-1189fb17 } -> { 11938000-1198fb17 } [359192] moving module 09 { 11548000-11847fff } -> { 11638000-11937fff } [3145728] moving module 08 { 111d6000-11547497 } -> { 112c6000-11637497 } [3609752] moving module 07 { 111d5000-111d50bc } -> { 112c5000-112c50bc } [189] moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f } [1401968] moving module 05 { 1107d000-1107d17b } -> { 1116d000-1116d17b } [380] moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f } [338976] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10066fff] { 65000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 11937fff] { 838000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #14 Wed Apr 29 13:37:03 CEST 2015 GIC: Switching IRQ 29 to secure Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10067000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11937fff] [0:11938000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] MOE: Hello world MOE: found 236564 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d17c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c50bd] [C:507000] arm-rv.io BOOTFS: [112c6000-11637498] [C:508000] vmlinuz.arm BOOTFS: [11638000-11938000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023defa8 l4linux | phys=02000000 ephys=023defa8 l4linux | f_sz=00359394 memsz=003defa8 flgs=rwx l4linux | PH 1 (t: 4) offs=0031afe0 vaddr=02312fe0 vend=02313004 l4linux | phys=02312fe0 ephys=02313004 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002b0, argc=6 argv=0xafff4f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (5 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02332000 [3272kB] (a bit longer) l4linux | Data: 02332000 - 023543a0 [136kB] l4linux | Initdata: 02314000 - 02331024 [116kB] l4linux | BSS: 02359394 - 023defa8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02333fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | section-with-init: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | section-with-init: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4059136 l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | 'swp(b)' instruction at 0224f728 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? l4linux | 'swp(b)' instruction at 02161dd4 and faulting. l4linux | Linux built for the wrong ARM version? ...

2 1

Utcb in syscall
by watermirror 26 May '15

26 May '15

hi ,in sys_ipc_wrapper, the code first get the current thread's syscall entry frame: .... Thread *curr=current_thread(); Syscall_frame *f = curr-regs(); ... according to the Syscall_frame's implemention, it can get the Utcb by Syscall_frame::utcb(). but the following code get the Utcb in another way: Utcb *utcb = curr->utcb().access(true); what's the difference between those two Utcb?

4 4

Re: Booting error in L4android for Exynos 5250.
by Youren Shen 26 May '15

26 May '15

> > > > I'm trying to booting L4Android in Exynos 5250 platform. I got some > > > questions. If anyone can give me any direction or document, It will be > > very > > > helpful. > > > > > > 1, How to edit this vbus and devs file to match my platform? > > > For example, if I want replace the MOUSE in vbus with TOUCHSCREEN, what > > > should I write to determine the driver of the touchscreen, and the > > register > > > address of the driver? > > > It seems the .hid can assign the driver? And the MMio can remap the > > address > > > of the IO for driver? > > > > A vbus defines the resources (IRQs and MMIO) for a whole client, i.e. > > it's not per driver but per client (e.g. L4Linux). For the touchscreen > > you need to give the MMIO regions and IRQs that the touchscreen driver > > is using. > > > > > 2, As for GUI driver, what the mag and fb-drv do ? Should I write one > > > > The fb-drv is the framebuffer driver, i.e. the driver that maps some > > memory in such a way to the framebuffer hardware that something appears > > on the screen. mag is a small window manager that makes multiple > > windows, that you can drag around, out of the single hardware > > framebuffer. > > > > > driver in L4RE or I can reuse the driver in Linux? > > > > Reusing the driver from L4Linux is possible but typically framebuffer > > drivers are reasonable small to be implemented standalone. > > For the driver reuse: I read the User Guide of rearview platform, it seems that the MMIO should set as the register Address in memory map. And the IRQs should be the interrupt number + 32. I know how to write LCD driver and framebuffer in native Linux System. But for L4Linux, I still have some question. I am not sure how to reuse the driver of Linux or rewrite the fb-drv. Here is the situation: The folder in arch/arm/mach-exynos has plenty code to initial the platform, so I added config L4_PLATFORM_EXYNOS in arch/l4/Kconfig and PLATFORMNAME-$(CONFIG_L4_PLATFORM_EXYNOS) = exynos in arch/l4/Makefile. However, when build the kernel, there is some error. It seems like the L4Linux startup invoke some variables defined in Realview or Generic platform like NR_IRQS_HW. Is this rectifiable? I found that there is l4fb.c as driver in driver/video, what's different with the module in l4/pkg? And last question, how to run the driver I want to use? Thank you very much! -- Best Regards. Youren Shen.

2 1