users

users@lists.genode.org

1 participants
2335 discussions

error when running l4android on genode-15.05
by 刘海剑 04 Jun '15

04 Jun '15

Hi, I run l4linux perfectly on genode-15.05, but got some errors as follow: Genode 15.05 int main(): --- create local services --- int main(): --- start init --- int main(): transferred 460 MB to init int main(): --- init created, waiting for exit condition --- [init] Could not open ROM session for module "ld.lib.so" [init] void* abort(): abort called And here is my own l4android.run: >>>>>>>>>>>>> assert_spec foc assert_spec 32bit # # Build # set use_platform_drv [expr [have_spec platform_arndale] || [have_spec platform_imx53]] set use_usb_drv [expr [have_spec omap4] || [have_spec exynos5]] set use_nic_drv [expr !$use_usb_drv] #set use_atapi_drv [have_spec x86] set use_sd_card_drv [expr [have_spec omap4] || [have_spec exynos5] || [have_spec pl180]] # generic components set build_components { core init drivers/timer drivers/framebuffer server/nitpicker server/nit_fb server/terminal_log l4android } lappend_if [have_spec pci] build_components drivers/pci lappend_if [have_spec acpi] build_components drivers/acpi lappend_if [have_spec ps2] build_components drivers/input/ps2 lappend_if [have_spec usb] build_components drivers/usb lappend_if $use_usb_drv build_components drivers/usb lappend_if $use_nic_drv build_components drivers/nic #lappend_if $use_atapi_drv build_components drivers/atapi lappend_if $use_sd_card_drv build_components drivers/sd_card lappend_if $use_platform_drv build_components drivers/platform build $build_components create_boot_directory # # Config # set config { <config prio_levels="2"> <parent-provides> <service name="ROM"/> <service name="RAM"/> <service name="IRQ"/> <service name="IO_MEM"/> <service name="IO_PORT"/> <service name="CAP"/> <service name="PD"/> <service name="RM"/> <service name="CPU"/> <service name="LOG"/> <service name="SIGNAL"/> </parent-provides> <default-route> <any-service> <parent/> <any-child/> </any-service> </default-route> <start name="timer"> <resource name="RAM" quantum="1M"/> <provides><service name="Timer"/></provides> </start> <start name="nitpicker"> <resource name="RAM" quantum="2M"/> <provides><service name="Nitpicker"/></provides> <route> <service name="Input"> <child name="input_drv"/> </service> <service name="Framebuffer"> <child name="fb_drv"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> <start name="android_fb"> <binary name="nit_fb"/> <resource name="RAM" quantum="4M"/> <provides> <service name="Framebuffer"/> <service name="Input"/> </provides> <config xpos="0" ypos="0" width="640" height="480" refresh_rate="25"/> </start> <start name="android_term_fb"> <binary name="nit_fb"/> <resource name="RAM" quantum="4M"/> <provides> <service name="Framebuffer"/> <service name="Input"/> </provides> <config xpos="0" ypos="482" width="1024" height="268" refresh_rate="25"/> </start> <start name="log_term_fb"> <binary name="nit_fb"/> <resource name="RAM" quantum="4M"/> <provides> <service name="Framebuffer"/> <service name="Input"/> </provides> <config xpos="642" ypos="0" width="380" height="480" refresh_rate="25"/> </start> #<start name="android_term"> #<binary name="terminal"/> #<resource name="RAM" quantum="1M"/> #<provides><service name="Terminal"/></provides> #<route> #<service name="Input"> <child name="android_term_fb"/> </service> #<service name="Framebuffer"> <child name="android_term_fb"/> </service> #<any-service> <parent/> <any-child/> </any-service> #</route> #</start> <start name="log_term"> <binary name="terminal"/> <resource name="RAM" quantum="1M"/> <provides><service name="Terminal"/></provides> <route> <service name="Input"> <child name="log_term_fb"/> </service> <service name="Framebuffer"> <child name="log_term_fb"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> <start name="terminal_log"> <resource name="RAM" quantum="1M"/> <provides><service name="LOG"/></provides> <route> <service name="Terminal"> <child name="log_term"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> <start name="l4android"> <resource name="RAM" quantum="512M"/> <config args="mem=128M console=ttyS0 l4x_rd=root-ginger.gz"> <block label="sda"/> </config> <route> <service name="Input"> <child name="android_fb"/> </service> <service name="Framebuffer"> <child name="android_fb"/> </service> #<service name="Terminal"> <child name="android_term"/> </service> <service name="LOG"> <child name="terminal_log"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start>} append_if [have_spec acpi] config { <start name="acpi"> <resource name="RAM" quantum="8M"/> <binary name="acpi_drv"/> <provides> <service name="PCI"/> <service name="IRQ" /> </provides> <route> <service name="PCI"> <any-child /> </service> <any-service> <parent/> <any-child /> </any-service> </route> </start>} append_if [expr ![have_spec acpi] && [have_spec pci]] config { <start name="pci_drv"> <resource name="RAM" quantum="5M"/> <provides><service name="PCI"/></provides> </start>} append_if $use_platform_drv config { <start name="platform_drv"> <resource name="RAM" quantum="1M"/> <provides> <service name="Regulator"/> </provides> </start>} append_if [have_spec gpio] config { <start name="gpio_drv"> <resource name="RAM" quantum="4M"/> <provides><service name="Gpio"/></provides> <config/> </start>} append_if $use_usb_drv config { <start name="usb_drv"> <resource name="RAM" quantum="12M"/> <provides> <service name="Nic"/> <service name="Input"/> </provides> <config uhci="yes" ehci="yes" xhci="yes"> <nic mac="02:00:00:00:01:01" /> <hid/> </config> </start>} append_if $use_nic_drv config { <start name="nic_drv"> <resource name="RAM" quantum="4M"/> <provides><service name="Nic"/></provides> </start>} #append_if $use_atapi_drv config { #<start name="blk_drv"> #<start name="atapi_drv"/> #<resource name="RAM" quantum="1M" /> #<provides><service name="Block" /></provides> #<config ata="yes"/> #</start>} append_if $use_sd_card_drv config { <start name="blk_drv"> <binary name="sd_card_drv"/> <resource name="RAM" quantum="1M"/> <provides><service name="Block"/></provides> </start>} append_if [have_spec framebuffer] config { <start name="fb_drv"> <resource name="RAM" quantum="4M"/> <provides><service name="Framebuffer"/></provides> <config width="1024" height="768" depth="16" output="HDMI" buffered="yes" /> </start>} append_if [have_spec ps2] config { <start name="input_drv"> <binary name="ps2_drv"/> <resource name="RAM" quantum="1M"/> <provides><service name="Input"/></provides> </start>} append config { </config>} install_config $config # # Boot modules # set boot_modules { core init timer nitpicker nit_fb terminal_log l4android root-ginger.gz } lappend_if [have_spec acpi] boot_modules acpi_drv lappend_if [have_spec pci] boot_modules pci_drv lappend_if [have_spec gpio] boot_modules gpio_drv lappend_if [have_spec ps2] boot_modules ps2_drv lappend_if [have_spec framebuffer] boot_modules fb_drv lappend_if $use_usb_drv boot_modules usb_drv lappend_if $use_nic_drv boot_modules nic_drv #lappend_if $use_atapi_drv boot_modules atapi_drv lappend_if $use_sd_card_drv boot_modules sd_card_drv lappend_if $use_platform_drv boot_modules platform_drv if {[have_spec x86]} { set initrd_uri "http://genode.org/files/release-11.11/l4lx/root-ia32-ginger.gz" set system_uri "http://genode.org/files/release-11.11/l4lx/system-ia32-ginger.img" } elseif {[have_spec arm]} { set initrd_uri "http://genode.org/files/release-11.11/l4lx/root-arm-ginger.gz" set system_uri "http://genode.org/files/release-11.11/l4lx/system-arm-ginger.img" } if {![file exists bin/root-ginger.gz]} { puts "Download initramfs ..." exec curl $initrd_uri > bin/root-ginger.gz 2> /dev/null } if {![file exists bin/system-ginger.img]} { puts "Download system image ..." exec curl $system_uri > bin/system-ginger.img 2> /dev/null } #exec >& /dev/null wget -O bin/root-ginger.gz.md5 $initrd_uri.md5 #exec >& /dev/null wget -O bin/system-ginger.img.md5 $system_uri.md5 cd bin #exec md5sum -c root-ginger.gz.md5 #exec md5sum -c system-ginger.img.md5 cd .. build_boot_image [join $boot_modules " "] append qemu_args " -m 512 " append qemu_args " -serial mon:stdio " #append_if $use_atapi_drv qemu_args " -hda bin/system-ginger.img " append_if $use_sd_card_drv qemu_args " -drive file=bin/system-ginger.img,if=sd,cache=writeback " append_if [have_spec x86] qemu_args " -net nic,model=e1000 " append_if [have_spec lan9118] qemu_args " -net nic,model=lan9118 " append_if $use_nic_drv qemu_args " -net user -redir tcp:5555::5555 " run_genode_until forever <<<<<<<<<<<<<<<<<<<<< What is the matter? Thanks a lot.

1 0

Re: Port Genode(13.05) to exynos4412 with Fiasco.oc(R67)
by 四枚羽根 03 Jun '15

03 Jun '15

Hi, We have alreadly got fiasco.oc(R67) running on the Exynos4412 successfully, and tested Genode(13.05) on pandaboard.So i am trying to test Genode(13.05） with fiasco.oc(R67) on Exynos4412. Have made all the configuration and passed the compilation(printf.run),i get a 'image.elf' and then change it to 'image.raw'. The Fiasco.oc starts successfully during the execution of image.raw on Exynos4412,but end with the error,i know it is about protection domain. Do you have any idea about the error? Then can you show me the log of your Fiasco.oc's boot(on Odroid-X2). Thanks and regards Sunyu 发自 Windows 邮件

2 1

AHCI still not working
by Nobody III 01 Jun '15

01 Jun '15

I've tried to get AHCI to work several times. With the new AHCI driver (I updated Genode today), I thought it would finally work. It discovers my devices correctly (2 ATA and one ATAPI), and my configuration is good. (I've updated it and tested an almost identical scenario in Qemu.) I've tried it on both Nova and Fiasco.OC (Nova's pci_device_pd gave me an error: "assignment of PCI device failed") Any ideas what to do now?

5 18

Port Genode(13.05) to exynos4412 with Fiasco.oc(R67)
by sunyu 29 May '15

29 May '15

Hi, I'm trying to port Genode(13.05) to Samsung Exynos4412,using R67 of Fiasco.oc. There's a error while the image(compiled with printf.run) is running. ------------------------------------------------------------------------------------------------------ int main(): --- create local services --- int main(): --- start init --- int main(): transferred 1981 MB to init Could not assign parent interface to new PD unknown exception? int main(): --- init created, waiting for exit condition -- ------------------------------------------------------------------------------------------------------- I'd like to know how to solve this problem and get R67 running on Genode(13.05). Sunyu

3 2

I2C / SPI drivers for the Raspberry Pi
by Duss Pirmin 27 May '15

27 May '15

Hello I have pledged for one of this E-Paper displays for the Raspberry Pi https://www.kickstarter.com/projects/pisupply/papirus-the-epaper-screen-hat… To control this SPI, I2C and GPIO are needed. Are there already drivers for this interfaces? Otherwise I would be willing to implement this drivers and resource multiplexers. Best regrars Pirmin

3 7

Tracing with Genode
by Torsten Frenzel 27 May '15

27 May '15

Hello, currently, I explore Genode's tracing-feature and have a few questions regarding policy modules and trace buffers: I'm working with the 15.02 release and found two examples of policy modules, called null and rpc_name. Are there other examples in branches of the repo on how to implement a custom policy module. In general what are the restrictions, when implementing a policy module? Is it possible to extract more specific information for a certain event, for example, the name of the destination, that was called. Furthermore, the policy modules for Rpc_call and Rpc_returned events have access to a data structure of type Msgbuf_base. As far as I understood the message buffer contains the arch-depended marshalled data. Is there a generic mechanism to interpret these data in a meaningful way inside policy module or the trace monitor? It would be helpful to accurately timestamp every recorded event with a value of a real time clock. But that would require access to service that provides such an information. Again, I cannot see how to get access to such a service from inside the policy module, because it hasn't access to the Genode runtime environment. Maybe the correct approach would be to use a fast timestamp function inside the policy module and later calculate the real time value in the trace monitor? Is it possible to disable/enable specific types of events (, may be using the Trace::Control data structure)? Is there a mechanism that the trace monitor is notified, when a trace-buffer is full or has reached a threshold? When I played around with the test_trace program, I noticed that loading more than policy module into core fails. After some investigations I found that the slab_size for the constructed allocator used in the Policy_registry class for Trace::Policy objects is only 4 bytes, but Trace::Policy objects have a larger size of 26 bytes. When I changed the constructor in the session component as shown below everything works fine. So for some reason the compiler selects the Avl_node_base::Policy class in the template. diff -r ./base/src/core/include/trace/session_component.h . 40,41c40,41 < Tslab<Trace::Policy, 4096> _policies_slab; --- > Tslab<Policy, 4096> _policies_slab; Regards, Torsten

3 2

Accessing two UARTs from within one application
by Stark, Josef 26 May '15

26 May '15

Hi all, is it possible to use two UARTs at the same time from within one app? We had a look at the example script and application repos/os/run/uart.run and repos/os/src/test/uart and tried several things, including: - adding two lines in the config for the same process but with different UARTs: <policy label="test-uart1" uart="1"/> <policy label="test-uart1" uart="2"/> - comma-separating UARTs (uart="1,2") - adding a second uart-attribute (uart="1" uart="2") - and many more. - In the application, we simply added a second instance of Uart::Connection and accessed it in the same way as the first. (The Uart::Connection doesn't seem to offer any other constructor than the default one, in which one could specify which UART to access.) but all of those attemptes either led to a build error or made the output appear on only one UART. Is there any way to access two UARTs in one application or would we need a separate process for each one? Thanks in advance, Josef

2 2

Announcement: Genode OS Framework version 15.05 released
by Norman Feske 26 May '15

26 May '15

I am happy to announce the version 15.05 of the Genode OS Framework, which represents the most comprehensive release in our history. Its most visible feature is a completely new written documentation in book form. On the technical side, the highlights of the release are: - Comprehensive architectural documentation - Feature completion of the our custom kernel - Kernel-protected capabilities - Principal support for the 64-bit x86 - Dynamic thread weights - Revised device-driver infrastructure - Device drivers - New AHCI driver - Multi-touch support - Audio drivers ported from OpenBSD - SD-card drivers for i.MX53 and Raspberry Pi - Board support for i.MX6-based Wandboard - Support for GPT partitions - Proof-of-concept support for the seL4 kernel - NOVA kernel mechanism for signals - Tool chain updated to GCC 4.9.2 and binutils 2.25 These and many more improvements are described in the release documentation: http://genode.org/documentation/release-notes/15.05 Best regards Norman -- Dr.-Ing. Norman Feske 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

1 0

Port OpenDDS to Genode
by Roger Ferreira 25 May '15

25 May '15

Dear Genode Community, This is my first message, and actually first contact with microkernel world. I beg your patience in this first time. I am on the application development & integration deployment side. I have been thinking long ago about the possibility of tailoring a software environment with the very basic stuff (code) demanded by specific application domain. I work with mission safe-critical automation domain, and the applications are basically regarded algorithms / computation / networking. GUI can be splitted ou very basic. Using Linux as base OS provide what is needed, but together with a bunch of unecessary code / packages that increase the unrealiability of the overall final system. Now, having learn the important concept of isolating security-critical functions, in order to avoid security breach from the very ground,I got excited about the idea to bring the applications I work with in such scenario. And particularly to explore virtualization with the least possible software overhead. I did a survey on microkernel, microhypervisor. Found L4-based Fiasco-OC and then NOVA. I was still a little skeptical because of the low level knowledge required. Genode gave me the light I was looking for. Specially when I saw the porting of Qt5, which actually I use long time. With Qt5 integration I am very close to my objective. However, I still demand to integrate a 3-rd party software, namely, to port OpenDDS to Genode. I dig into the manual:http://genode.org/files/53bcb8e33fe6602fed25edc3c7b922c5/manual-2015… and genode site. I did the manual hello world example, built some environments (NOVA, Fiasco.OC), run the demo. Everything worked fine with QEMU. With Qt5 examples I was not successful yet, though. But before I can move on, I need to integrate an external library. My question / doubt is regarding porting an external Library:http://genode.org/documentation/developer-resources/porting_applica… Specifically, OpenDDS3.6 which relies on ACE-TAO2.2a:http://download.ociweb.com/TAO-2.2a/ACE+TAO-2.2a_with_latest_pa… I create a specific repo inside repos, and did the port files. The make prepare worked with no problems. But then come the challenging part: 1) Adapting Makefiles /Config files to Genode specific platform. ACE-TAO need a specific config and platform files. There are examples for linux, free and openbsd, vxworks, qnx, vxworks, lynxos. From which should I start from? 2) Creation of the patches. How to create the patches? Just with diff -crNb? 3) Building specific tools. ACE-TAO and OpenDDS rely on specific tools for IDL files. I saw the Qt example with the host_tools.mk approach, but not tested yet. 4) Creation of the run file. What should be a first trial? Where can I can get better insight of how to do that? I have digged through the Genode code, particularly the Qt5 porting, but it is quite hard. Is there any specific guide, or there is no easy way. Is a try and test process? Thanks for your attention. Best regards and congratulations for the Genode project, Roger

2 5

Port of base-hw to RISC-V / lowRISC ?
by Rolf Sommerhalder 22 May '15

22 May '15

Dear list, GSoC has accepted a project to port seL4 to RISC-V (64 bit) architecture, which is used in the lowRISC System-on-a-Chip (SoC) Open Source project. Further, lowRISC supports another project to port rump kernels to minimal RISC-V cores which lowRISC plans to use as I/O co-processors, for example as TCP/IP offload engines [1]. There are tool chains and ports of Linux kernels to RISC-V / lowRISC to run them in simulators and emulators (qemu), on FPGA (Xilinx Zynq), and ASIC [2, 3]. Although my HW/SW co-design skills are a bit rusty, I am tempted to reverse that and try such a port. In order to get a better idea about complexity and effort required, I currently study the sources of base-hw for ARMv7, and its recent port to x86_64 in the staging branch. Is anyone aware of such a porting effort, or has anyone else an interest to run Genode base-hw on RISC-V64, and might want to chime in eventually? Thanks, Rolf [1] http://www.lowrisc.org/blog/2015/05/summer-of-code-students-for-lowrisc/ [2] http://riscv.org/ [3] https://github.com/ucb-bar/rocket-chip

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users