- l4-hackers - example.com Site

omap4.dev config file for PandaBoard
by sebastian.eckl＠mytum.de 19 Sep '12

19 Sep '12

Hi, I own a PandaBoard with OMAP 4430 processor and have unavailingly tried to build L4Android for it. As basis I take the latest l4re_snapshot 2012081219. L4Re and Fiasco kernel itself are running, the provided Hello World example shows no problems. I already realized that I'll need a correct .dev config file specific to my platform, when creating the .uimage file for U-Boot. Unfortunately, an omap4.dev or panda.dev configuration file does not exist at the moment. So, I'd like to ask, if someone already adapted a .dev file to the PandaBoard and can provide me with some information or even may share his configuration with me or the public. Thank you very much in advance for your help. Sebastian

1 0

a question about L4_MAP_ITEM_GRANT
by Chen Tian 13 Sep '12

13 Sep '12

Hello, I have a simple question. If a parent maps a page into a child's space with this flag, can the parent regain this page and remove this mapping later? I did a simple test. It seems that with this flag in l4_task_map, the child owns the mapped page permanently. What I'd like to do is when a child finishes its job and returns such a granted page to its parent, the parent can reuse this page for some other child. Thanks.

2 1

Startup help for L4Linux
by Andrej S 12 Sep '12

12 Sep '12

Hi Adam, I have build some packages on my self on-top of bare fiasco, but however I didn't get l4linux to run. I got snapshot, I configure it, like readmy says me, with 'make setup' with all default settings and paths. Then I build it with 'make'. What should be my next steps to run l4linux? 2012/7/2 Adam Lackorzynski <adam(a)os.inf.tu-dresden.de>: > > On Sun Jul 01, 2012 at 08:57:41 -0500, Andrej S wrote: >> thanks for answer. >> I explored sources given with snapshot little bit and now I'm able to >> compile and run fiasco-ux. >> >> But not all is perfect: >> 1. I copied fiasco-ux with irq0, moe, ned and sigma0 together, but >> if I try to run hello-example it quits with >> FATAL exception in MOE: >> Exception: No such object found: rom/l4re: backtrace ... > > Go to the l4-obj directory where L4Re was built to and issue: > make ux E=hello > > You'll probably need to setup the path to the Fiasco UX build in > l4/conf/Makeconf.boot > >> 2. I have no idea, which package and why should I give to fiasco-ux to >> run l4linux. > > make ux E=L4Linux-mag-x86 > > or similar. The key here is the l4/conf/modules.list file which contains > which files are taken for which boot entry etc. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

2 1

Mapping physical mem region
by Nikolay Golikov 12 Sep '12

12 Sep '12

Hi, l4-hackers! How I can map some physical memory region to task address space? I tried to use l4sigma0_map_mem, but it return me "No fpage received" error. I tried different region szes from 256M to 4K. PS I try to do it on i.mx53 TZ-VMM | Hello from tz-vmm! TZ-VMM | Nonsecure Ram mapping failed (No fpage received)! TZ-VMM | Addr: 0x80000000 Size: 0x1000 (4K) SIGMA0: Memory usage: a total of 4096 byte are in the memory pool allocated 10 of 203 objects this are 200 of 4060 byte SIGMA0: Dump of all resource maps RAM:------------------------ [4:70000000;70000fff] [4:70061000;7008ffff] [4:70097000;70097fff] [4:7009f000;8effffff] IOMEM:---------------------- [0:0;53efffff] [10:53f00000;53f03fff] [0:53f04000;63f9bfff] [10:63f9c000;63f9ffff] [0:63fa0000;6fffffff] [0:90000000;ffffffff]

2 1

Fiasco.OC (rev. 40) Pandaboard support
by Stefan Kalkowski 07 Sep '12

07 Sep '12

Hi L4-hackers, recently I've tried to adapt Genode's Fiasco.OC-platform support to use the latest Fiasco.OC/L4Re subversion revision. When trying it on x86 I didn't run into any trouble. It worked "out of the box". But when it came to ARM, I got problems to boot Fiasco.OC on the Pandaboard in general (also when using plain Fiasco.OC/L4Re). I've debugged the problem down to Cpu::init_errata_workarounds(). The problem is that pandaboard's boot code initializes TrustZone, and triggers a configuration-disable signal beforehand. That leads to 'undefined instruction' exceptions, whenever one tries to write into the p15/c15-c0-1 debug register (like it's done in init_errata_workarounds). The attached patch implements Cpu::init_errata_workarounds() empty for the pandaboard. Moreover, it restricts the appliance of ERRATA 743622 to CPU revisions: r2p0-r2p2. With the attached patch Fiasco.OC runs fine on the Pandaboard too. Best regards Stefan -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 2

l4linux filesystem under fiasco-ux
by Ryan Brown 27 Aug '12

27 Aug '12

So far I've been running l4linux in a virtual machine. I'd like to run it in fiasco.ux to compare performance. But if l4linux under ux has no access to hardware, how do I access the filesystem? Am I stuck with the initial ramdisk? Or is there some way to mount the host filesystem, or a part of it?

2 1

Announcement: Genode 12.08 improves NOVA and ARM support
by Christian Helmuth 23 Aug '12

23 Aug '12

Today Genode Labs released the 4th anniversary version of the Genode OS Framework. Most notable are the NOVA microhypervisor platform improvements for x86 64bit, object-integrity protection, and centralized kernel-resource allocation in core as well as comprehensive support for the OMAP4 SoC used in the PandaBoard. A quick overview of all changes that come with version 12.08: - Base platforms - New base-hw platform for running the framework on bare ARM hardware - NOVA support for x86_64, object integrity protection, core-only kernel-resource allocation - New OMAP4 SoC device drivers - HDMI output - SD-card - USB HID - Networking - New FFAT-based file-system service - New TAR file-system service - Improved Noux runtime - New port of the Lynx web browser - Shell scripting support - 3rd-party libraries - New ports of openssl, pcre, expat - MPC, libgmp for x86_64 and ARM - lwIP updated to version 1.4.1-rc1 - New port of the lighttpd web server More details are described in the release notes http://genode.org/documentation/release-notes/12.08 Have fun with our new release -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Local APIC address and MSI address
by Chen Tian 22 Aug '12

22 Aug '12

Hi, According to Intel manual, local APIC address starts at FEE00000, which is overlapping with the MSI's address register. How does this actually work? Thanks.

2 1

i.mx53 and fiasco.oc
by Nikolay Golikov 22 Aug '12

22 Aug '12

Hello. I trying to run fiasco.oc + l4re on freescale i.mx53qsb. And have some problems to do this. I using i.mx51 platform configuration with some changes. I changed addresses in src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp: EXTENSION class Mem_layout { public: enum Virt_layout_imx53 { Timer_map_base = 0xef1ac000, Uart_map_base = 0xef1bc000, Watchdog_map_base = 0xef198000, Pic_map_base = 0xef200000, Uart_base = Uart_map_base, }; enum Phys_layout_imx53 { Device_phys_base_1 = 0x53f00000, Device_phys_base_2 = 0x0fffc000, Watchdog_phys_base = 0x53f98000, // wdog1 Timer_phys_base = 0x53fac000, // epit1 Uart_phys_base = 0x53fbc000, // uart1 Pic_phys_base = 0x0fffc000, }; }; And made some little changes in other source files. When I try to boot it, I see something like this: ## Booting kernel from Legacy Image at 70800000 ... Image Name: L4 Image #47 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 897192 Bytes = 876.2 kB Load Address: 71000000 Entry Point: 71000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... L4 Bootstrapper Build: #47 �В�т. �а�в�г. 21 16:49:21 MSK 2012, 4.5.1 Scanning up to 1024 MB RAM Memory size is 512MB (Limited by Scan) (70000000 - 90000000) RAM: 0000000070000000 - 000000008fffffff: 524288kB Total RAM: 512MB mod04: 710c1000-710da540: hello mod03: 710a7000-710c0458: l4re mod02: 7106d000-710a6624: moe mod01: 71063000-7106c370: sigma0 mod00: 71015000-71062cac: fiasco Moving 5 modules to 71100000 with offset eb000 moving module 05 { 710c1000-710da540 } -> { 711ac000-711c5540 } moving module 04 { 710a7000-710c0458 } -> { 71192000-711ab458 } moving module 03 { 7106d000-710a6624 } -> { 71158000-71191624 } moving module 02 { 71063000-7106c370 } -> { 7114e000-71157370 } moving module 01 { 71015000-71062cac } -> { 71100000-7114dcac } Scanning fiasco Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0x7100f000-0x7100f0d6] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x70002000 Regions of list regions [ 70001000, 700019bf] { 9c0} Kern fiasco [ 70002000, 7005cfff] { 5b000} Kern fiasco [ 70090000, 7009e17b] { e17c} Sigma0 sigma0 [ 70140000, 701717d3] { 317d4} Root moe [ 70178000, 7018eec7] { 16ec8} Root moe [ 71000000, 710143ef] { 143f0} Boot bootstrap [ 7100f000, 7100f1d3] { 1d4} Root Multiboot info [ 71192000, 711c553f] { 33540} Root Modules Memory API Version: (87) experimental Sigma0 config ip:700900e0 sp:71013044 Roottask config ip:70140178 sp:00000000 Starting kernel fiasco at 70001000 Hello from Startup::stage2 Initialize page table It stops on line 151 src/kern/arm/gic.cpp: Io::write<Mword>(0, _dist_base + DIST_CTRL); where _dist_base is Pic_map_base. If I understand correctly tzic on i.mx53 and tzic on i.mx51 is equivalent. And second question: I do not understand for what purpose make pysical devices and sdram mapping in: src/kern/arm/bootstrap.cpp? // map sdram linear from 0xf0000000 for (va = Mem_layout::Map_base, pa = Mem_layout::Sdram_phys_base; va < Mem_layout::Map_base + (4 << 20); va += 0x100000, pa += 0x100000) map_1mb(page_dir, va, pa, true, false); // map sdram 1:1 for (va = Mem_layout::Sdram_phys_base; va < Mem_layout::Sdram_phys_base + (4 << 20); va += 0x100000) map_1mb(page_dir, va, va, true, true); map_hw(page_dir); And why afterwards devises on physical addresses are out of order?

2 1

Local APIC cannot deliver MSI to CPU (Fiasco.OC) ?
by Chen Tian 22 Aug '12

22 Aug '12

I am trying to use MSI for my network card. After setting the MSI slot in the PCI configuration block based on Intel manual, I can confirm the interrupt is delivered to the processor's local APIC by looking at the IRR content in kernel debugger. The bit in IRR that reflects the vector I specified in MSI message is set to 1 by APIC. However, the interrupt handler installed at that vector is never invoked. Does someone have any idea on this? The priority does not seem to be the issue, because I checked the TPR, which was 0x80 when I entered kernel debugger and decreased to 0 when I press 'g'. The error status register is also zero in the kernel debugging mode, while there is a pending interrupt request as suggested by IRR. But the cpu just can't get the interrupt. Any suggestions? Thanks.

1 0