users September 2017

users@lists.genode.org

16 participants
21 discussions

Individual file access
by Nobody III 16 Mar '18

16 Mar '18

To start off, I'm planning on building a component that handles file open/save requests for other components, primarily graphical applications. My plan is to use a qt5 QFileDialog for the user to select one or more files, then modify the vfs server's configuration to attach the selected file(s) to the component's filesystem. To attach individual files to a component's filesystem, it seems like I should write a server-side link vfs plugin. The plugin would be like a symlink, but would transparently resolve the link within the vfs server, providing access to otherwise inaccessible files. Is this possible? If so, can you give me some tips on how to implement it?

2 7

Boot problems using Genode 16.08 with Fiasco.OC r67 on a RPi Model B
by Alexander Weidinger 27 Nov '17

27 Nov '17

Dear Genode community, we are currently trying to get a Raspberry Pi 1 Model B running with Genode 16.08 and Fiasco.OC r67 from https://github.com/skalk/foc/. We made changes to both, genode and foc but the basis are the two mentioned versions. Trying to boot the RPi, we are left with the following message, the board resets itself? and again tries to boot: > ... > reading genode.img > 2060288 bytes read in 331 ms (5.9 MiB/s) > Kernel image @ 0x1000000 [ 0x1000000 - 0x11f7000 ] > > Starting k > L4 Bootstrapper > Build: #5 Wed Jul 5 17:34:36 CEST 2017, 4.9.2 > Scanning up to 512 MB RAM, starting at offset 32MB > > > U-Boot 2014.07-rc3-gd4614d4 (Jun 14 2014 - 01:23:23) > ... (Trying to boot vanilla genode 16.08 with vanilla foc r67 (from skalk) leads to the same behavior.) We were successful in running our setup (foc r67 and genode 16.08 both with our changes) on a pandaboard (real hardware) and on pbxa9 (qemu). Additionally we are able to successfully boot the RPi using vanilla genode 16.08 with the provided foc version (r56), using our u-boot configuration. Do we need to make additional changes to foc and/or genode to be able to boot the RPi using r67 of foc? Any hints or information are very welcomed! Regards, Alexander

2 4

Raspberry Pi B+ with uboot and genode
by Bernhard Blieninger 24 Nov '17

24 Nov '17

Hi, I am currently working to get the raspberry pi b+ working with genode. I started with an raspberry pi uboot and a tftp server where genode.img lies on. The sd card was flashed via dd and the sd card image from here: http://wiki.beyondlogic.org/index.php?title=Compiling_uBoot_RaspberryPi For the genode image I used the newest version of genode on github and compiled a foc_rpi and an rpi with this command: ./tool/create_builddir foc_rpi BUILD_DIR=buildrpi or that ./tool/create_builddir rpi BUILD_DIR=./build-rpi and the command make run/demo This is working with the Raspberry Pi B(!) but when i put the sd card in the Raspberry Pi B +(!) it is not even booting. Therefore i prepared a sd card with raspbian and changed the kernel.img with the newly compiled u-boot.bin from http://git.denx.de/u-boot.git The sd card now boots again and shows u-boot but if I want to load genode.img it does not continue. If genode is loaded, for example by manually triggering it with bootz, the serial connected minicom screen shows encoding problem nonsense. Starting up a linux kernel works. If I start genode.img directly from the sd card it is not working either. If I try this sd card with the Raspberry Pi B(!) it is not working. What I have tested in a last step is, what happens if I substitute the u-boot.bin with the genode.img while using the sd card image that was provided by beyondlogic in the first place, this is working for the B model but not for the B +. Also tried a fresh sd card format it to fat16 and put all the stuff on it, which is in the boot folder from https://github.com/raspberrypi/firmware , but that is also not working. So I assume, that either the bootcode.bin and/or start.elf provided by raspberry are too new to use them with genode. I could maybe find older versions but I would just like to ask if this will help, maybe genode was never (meant to) run with some raspberry boot code that is newer then 2013.11 (http://genode.org/documentation/release-notes/13.11#Raspberry_Pi). Thanks in Advance for your help. Best Regards, Bernhard.

6 8

foc_odroid_x2 with tftp boot via uboot on odroid u3
by Bernhard Blieninger 22 Nov '17

22 Nov '17

Hi guys, we are trying to get genode running on an odroid u3 which should be quite similar to the foc_odroid_x2. I followed the instructions from here: http://odroid.com/dokuwiki/doku.php?id=en:u3_building_u-boot and here: http://forum.odroid.com/viewtopic.php?f=82&t=9128 And i used the newest version of u-boot from hardkernel here: https://github.com/hardkernel/u-boot/tree/odroid-v2015.10 I wanted to use tftp boot so and did not really know how to start at first place, so i picked up the ubuntu image from here: http://odroid.com/dokuwiki/doku.php?id=en:u3_release_linux_ubuntu and copied it via dd to the sd card. Then I just let the sd_fuse script from the first link overwrite the bootcode on the sdcard. And wrote into the boot.txt at the first partition the bootcode which it should execute, in my case something like this: |setenv ethact sms0| |setenv ethaddr 00:10:75:2A:AE:E0| |setenv gatewayip 192.168.4.1| |setenv netmask 255.255.255.0| |setenv serverip 192.168.4.2| |setenv usbethaddr 00:10:75:2A:AE:E0| |setenv ipaddr 192.168.4.43| || |usb start| |tftp 0x70000000 odroid/uImage| |bootm| | |Where uImage is the uImage created from the foc_odroid build. Then I used ||| | ||mkimage -A arm -C none -T script -n 'Custom Boot Script' -d boot.txt boot.scr|| |||| || ||to build the boot.scr and booted the odroid u3.|| || Problem now is that is says something like: || *ERROR: booting os 'Unknown OS' (3) is not supported* Where 3 means something like Checksum OK as the uboot manual states. Now I took the zImage from the ubuntu on the sd card and converted it to a uImage with the mkimage program. Put both on the tftp server and changed the boot.txt accordingly. If i select zImage the ubuntu kernel boots up and gets a kernel panic, if i select uImage(now from Ubuntu) i get the same unknown OS error. Does someone have similar issues and can tell me how to fix it? Is it even possible to use the foc_odroid_x2 on u3, they share the same hardware so it should be? Thanks in advance. Best regards, Bernhard.| | -- Bernhard Blieninger, B.Sc. Technische Universität München Fakultät für Informatik Lehrstuhl für Betriebssysteme Boltzmannstraße 3 85748 Garching Tel. +49 89 289 18795 Fax +49 89 289 18557 bliening@...389... www.os.in.tum.de

6 14

Restoring child with checkpointed state
by Denis Huber 15 Nov '17

15 Nov '17

Dear Genode community, thanks to you [1], I could implement my Checkpoint/Restore mechanism on Genode/Fiasco.OC. I also added the incremental checkpoint optimization, to stored only changed memory regions compared to the last checkpoint (although this is not working reliably due to a Fiasco.OC bug, which Stefan Kalkowski found for me [2]). I also managed to checkpoint the capability map and restore it with new badges and insert missing capabilities into the capability space of Fiasco.OC. [1] https://sourceforge.net/p/genode/mailman/message/35322604/ [2] https://sourceforge.net/p/genode/mailman/message/35377269/ My problem is, although I restore all RPC objects, especially the instruction and stack pointer of the main thread, and the capability map and space, the target component just starts its execution from the beginning of its Component::construct function. My approach: For the restore phase, I use Genode's native bootstrap mechanism (i.e. I create a Genode::Child object) until it requests a LOG session from my Checkpoint/Restore component. I force a LOG session request in ::Constructor_component::construct() just before "Genode::call_component_construct(env);" in https://github.com/genodelabs/genode/blob/16.08/repos/base/src/lib/base/ent… Until the session request several RAM dataspaces are created, among other RPC objects, and attached to the address space. In my restore mechanism I identify the RPC objects, which were created by the bootstrap/startup mechanism, and only restore their state. After that point, I recreate and restore the state of all other RPC objects which are known by the child component. At last, I restore the capability map and space. During that process the mandatory CPU threads are identified (three of them: "ep", "signal_handler", and "childs_rom_name") and restored to their checkpointed state, especially the ip and sp registers. I did that through the use of Cpu_thread::state(Thread_state), but without luck. Also, although I know that the CPU threads were already started, I tried to call Cpu_thread::start(ip, sp), but without success. After the restoration which happens entirely during the LOG session request of the child, my component returns with a valid session object to the child. Now the child should continue the work from the point where it was checkpointed, but it continues its execution right after the LOG session request, ignoring the setting of the instruction pointer. The source code of the restore CPU thread state is found in [3]. I used run script [4] for the tests. [3] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/660a… [4] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/660a… Curiously, the child runs just as nothing happened, although its stack area was also manipulated. Perhaps my approach by reusing the bootstrap/startup mechanism is not destined to work, or maybe I have missed some important points in this mechanism. If so, please point me to the problem. I would also consider other restoration approaches, for example, by recreating all RPC objects manually and insert them into the capability map/space. What are your thoughts on my approach? Can it work? Does something else work better? Kind regards, Denis

4 19

Genode on i.MX6Q Sabre Lite
by unknown＠example.com 10 Nov '17

10 Nov '17

Hi, Alex Yes, default_log.cc is listed in core-sel4.mk file. However, I've recently noticed that not all of the components listed in SRC_CC actually get to compile (including default_log.cc), which results in incomplete core-sel4 library. After taking a closer look, it turned out that io_port_session_support.cc and io_port_session_component.cc are the source of this problem. I had them out commented for my sabre_lite build as you've previously suggested. Removing them from core-sel4.mk for seL4_x86_32 build gave me the same results as for sabre_lite: incomplete core-seL4 library Library core-sel4 COMPILE cpu_session_component.o COMPILE cpu_session_support.o COMPILE cpu_thread_component.o COMPILE io_mem_session_component.o COMPILE io_mem_session_support.o COMPILE main.o COMPILE pd_assign_pci.o COMPILE pd_session_component.o COMPILE pd_upgrade_ram_quota.o COMPILE ram_session_component.o COMPILE ram_session_support.o COMPILE rom_session_component.o COMPILE rpc_cap_factory.o COMPILE version.o MERGE core-sel4.lib.a and the same "undefined reference" errors at the end. Now that I know where the problem is: what can I do from here? >>Please check that you compile and link the >>file to core. Check that the symbol actually shows up as symbol in >>core.o, e.g. by examining the output of "readelf -s >>build/<arch>/core/sel4/core.o". Not sure what you mean by the symbol. "readelf -s core.o | grep -i log" gave me the following output: 10311: 00000000 0 FILE LOCAL DEFAULT ABS log.cc Comparing to successful build for x86_32: 8733: 00000000 0 FILE LOCAL DEFAULT ABS log.cc 9028: 00000000 0 FILE LOCAL DEFAULT ABS core_log.cc 9175: 00000000 0 FILE LOCAL DEFAULT ABS default_log.cc Thanks

8 21

ahci_drv default writeable?
by Steven Harp 27 Sep '17

27 Sep '17

Noticed that in 17.08 (and 17.05) these examples failed w. x86/nova - run/libc_vfs_fs_fat - run/libc_vfs_fat apparently because: [init -> ahci_drv] read-only session opened at device 0 for 'test-libc_vfs -> 0' so e.g., mkdir fails with EPERM. Hacking libports/run/libc_vfs_filesystem_test.inc to add writeable="yes" to the "ahci_drv" component configuration: <config> <policy label_prefix="test-libc_vfs" device="0" writeable="yes"/> <policy label_prefix="vfs" device="0" writeable="yes" /> </config> suffices, but maybe this is not appropriate. Was the default policy intended to be writeable="yes" for this driver? // Steve Harp

2 1

VirtualBox with Networking
by Chris Rothrock 26 Sep '17

26 Sep '17

I have been able to make a working environment with Genode/NOVA/VirtualBox a single VM running TinyCore with networking enabled and can communicate across the network. So far, only on VirtualBox 4, 5 still has issues that I am still trying to work out that I will get into at a later time but my goal is multiple VMs with networking. With VirtualBox 4, I have successfully made two VM environments and both VMs see eth0, I can assign an IP address to each but neither VM can communicate outside their own VM. Unlike with the single VM, I was unsuccessful to get an IP via DHCP (hence why I used a static IP), they could not ping the other VM, they could not ping anything on the network to which they were attached. Is there a setting in the test.vbox file different than for a single VM mode that I need to make to make the bridge work for this? -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

3 5

config syntax in hw_gpio_drv?
by Steven Harp 25 Sep '17

25 Sep '17

In Genode 17.08 (master) on rpi platform with hw (or foc) base, run/lxip_udp_echo seems to generate config XML that doesn't quite pass the syntax check: * * * genode build completed var/run/lxip_udp_echo/genode/config:31: parser error : AttValue: " or ' expected <resource name=\"RAM\" quantum=\"4M\"/> ^ var/run/lxip_udp_echo/genode/config:31: parser error : attributes construct error <resource name=\"RAM\" quantum=\"4M\"/> ^ var/run/lxip_udp_echo/genode/config:31: parser error : Couldn't find end of Start Tag resource line 31 <resource name=\"RAM\" quantum=\"4M\"/> ^ var/run/lxip_udp_echo/genode/config:32: parser error : AttValue: " or ' expected <provides><service name=\"Gpio\"/></provides> ^ var/run/lxip_udp_echo/genode/config:32: parser error : attributes construct error <provides><service name=\"Gpio\"/></provides> ^ var/run/lxip_udp_echo/genode/config:32: parser error : Couldn't find end of Start Tag service line 32 <provides><service name=\"Gpio\"/></provides> ^ Error: Invalid XML syntax in var/run/lxip_udp_echo/genode/config Makefile:309: recipe for target 'run/lxip_udp_echo' failed * * * The extraneous reversed virgules in the attribute values appear only for hw_gpio_drv: <start name="hw_gpio_drv"> <resource name=\"RAM\" quantum=\"4M\"/> <provides><service name=\"Gpio\"/></provides> <config/> </start> 1. Suggestions? 2. Is it reasonable to suppose this should run okay on RPI-version (v1,2,3?) hardware? // Steve Harp

2 2

Porting third-party code to Genode
by Jörg-Christian Böhme 25 Sep '17

25 Sep '17

My setup/environment: - Source: Branch: master commit 0adbd1ce2428dadffc61664d93ec394d5b0e6722 Date: Wed Aug 30 12:42:42 2017 +0200 - Target-genode-System: nova x86_64 - Host-System: genode-x86-gcc (GCC) 6.3.0 Ubuntu 17.04 QEMU emulator version 2.8.0(Debian 1:2.8+dfsg-3ubuntu2.3) Hi, I read the documentation about Native Genode port of a library from the gnode website[1]. It looks very easy to "create a port" of a library for genode. I started to port a library and I have realized what is meant by Chapter "Creating the build Makefile". This Chapter says, that I should create a build (Makefile) for the third party source code ? I was expected that the port mechanism from genode will execute the configure script (Cross compiling) of the third party just as the "source based" Linux/UNIX (FreeBSD/Arch Linux) systems does. I investigate for example how libssh is ported and I see that in genode/repos/libports/lib/mk/libssh.mk every source file are added. For such a small lib it is easy but for a bigger lib like Qt5, I see there are helper scripts to generate the port mk for genode ? I didn't use "Makefiles" in my projects. I'm a cmake user :-). So my knowledge about Makefiles are very poor. Maybe I missed something. My question: It is not possible to execute the "third party build system" to cross compile it for genode? My port idea/work: I didn't see any information about boost on the "Future Challenges of the Genode project"[2] or "Genode Porting Wishlist"[3] site, so I try to port boost to genode. Maybe somebody is also working on this? Cheers Jörg [1] http://genode.org/documentation/developer-resources/porting_libraries [2] https://genode.org/about/challenges [3] http://usr.sysret.de/jws/genode/porting_wishlist.html

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users September 2017