users August 2017

users@lists.genode.org

20 participants
30 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

cli_monitor vs launcher vs launchpad
by Jörg-Christian Böhme 08 Sep '17

08 Sep '17

My setup/environment: - Source: Branch: staging commit 17f3b559735027bcbde233ebacbb1f9d173a566c Date: Thu Aug 3 09:44:17 2017 -0500 - 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 try to understand the difference between cli_monitor, launcher, launchpad and qt-launchpad. I looked into the source code and I understand following: - app/cli_monitor is the command line version to start child processes. It exists in the low-level OS components repo. - app/launcher is the UI version of cli_monitor and uses some headers from cli_monitor. It exists in the gems repo. - app/launchpad is the UI version to start child processes. Launchpad is not using the cli_monitor headers. It exists in the demo repo. - app/qt5/qt_launchpad is the Qt version of launchpad. It uses lib/launchpad from demo repo. It exists in the libports repo. Both cli_monitor headers and lib/launchpad using the Genode::Child and Genode::Child_policy API to managed the child compoments as described in section 8.17.2. Child management [1]. What I see between the cli_monitor/launcher and launchpad approach, that the configuration of the subsystems is different. But is there even more differences ? May I asked, what are the future plans of these "launchers"? Cli_monitor is in the OS repo and sounds like the API is what I should use to implement some "own" launchers. Launch app in gems repo, as what I understand from the email from Norman (see Friday, 4. August 2017 11:56:38 CEST from Norman Feske) this is outdated. Launchpad is in the demo repo and what I see in the git commit history, this is also the older approach to "launch" subsystems in genode, or? Here some background information, why I asked... I will use genode as a desktop system and for such a use case I need something to launch applications. I notice, that genode is currently implementing a package management and it sounds like for me, in the future I need a launcher that are flexible enough to start an application after I installed a package in genode :-) ... but step by step. I'm a C++ developer and using STL/boost etc. but for UI I use Qt/QML. The idea, I will try to develope a launcher in Qt/QML (I know there is a launchpad in Qt ... but not in QML). I still try to find out, which approach is the best: Use the lib/launchpad or cli_monitor API or develope from scratch as described in section 8.17.2. Child management [1]. Maybe I will still using the current aprroaches (launchpad etc.), it depends on the email reply :-) Cheers, Jörg [1] http://genode.org/documentation/genode-foundations-17-05.pdf

4 6

Affinity Subspace Mapping
by Lex, Stephan 06 Sep '17

06 Sep '17

I am working with affinities in order to start and bind various components on different cores. I am using QEMU as emulation platform to start the system with four cores. My situation looks as follows: I have one parent component which creates two more children. Each of these including the init component should be assigned to a different core. The idea was to start init with an affinity configuration 4x1 in the run script: => <affinity-space width="4" height="1"/> The custom parent component should be configured to get a affinity subspace of 3x1 beginning from the second core like: => <affinity xpos="1" ypos="0" width="3" height="1"/> The next idea was to create two affinities with a subspace of 1x1 for the two children and start them within the parent component. The two children should be working on the third and fourth core respectively, so my intention was to declare them as xpos 1 and 2 relative to the parents subspace of 3x1: => const Genode::Affinity &aff_count{Genode::Affinity::Space(1), Genode::Affinity::Location(1, 0)}; => const Genode::Affinity &aff_val{Genode::Affinity::Space(1), Genode::Affinity::Location(2, 0)}; To check this attempt i inserted a log call in the constructor of core's Cpu_session_component: => log("CORE ",__func__,": Affinity location: xpos: ",_location.xpos()," ypos: ",_location.ypos()," width: ",_location.width()," height: ",_location.height()); The log outputs seem relatively coherent with what was originally planned: => init cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 0 ypos: 0 width: 4 height: 1" => parent cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 1 ypos: 0 width: 3 height: 1" => child_1 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 2 ypos: 0 width: 3 height: 1" => child_2 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 3 ypos: 0 width: 3 height: 1" Unfortunately right after the second child gets started, the program loops and does not terminate. If i change the affinity for the children to => const Genode::Affinity &aff_count{Genode::Affinity::Space(1), Genode::Affinity::Location(0, 0)}; => const Genode::Affinity &aff_val{Genode::Affinity::Space(1), Genode::Affinity::Location(1, 0)}; the log outputs also change to => child_1 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 1 ypos: 0 width: 3 height: 1" => child_2 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 2 ypos: 0 width: 3 height: 1" and the program continues its work as intended. If you could tell me my thinking errors, if there are any, or how to achieve that each component gets assigned to their respective cores, i would appreciate it a lot. -- Thank you, Stephan Lex

3 5

Qt5 Threads
by Johannes Kliemann 01 Sep '17

01 Sep '17

Hi, is anyone using threads in Qt5 applications on Genode? Is it possible to use QThreads or are Genodes own threads required? If so, how would I get an instance of Genode::Env in a Qt application (which I would need for the thread). Regards, Johannes

2 2

Re: ffat_fs server build in 17.08?
by Nobody III 31 Aug '17

31 Aug '17

The release notes say that ffat_fs is deprecated in favor of a vfs plugin. I'd recommend reading the release notes to see how to adapt your scenario. On Aug 30, 2017 11:58 AM, "Bob Stewart" <robjsstewart@...9...> wrote: Hi, I migrated to 17.08 from 17.05 this morning. One system I routinely build on prior releases fails with the 'server/ffat_fs' does not exist error. The prepare_tool was run to get the source, as usual. I've either forgotten a step or the current build is broken for users of the old ffat_fs server. The complete make output is: make run/rico_no_usb KERNEL=hw | tee build.log including /Work/Genode/genode-17.08/tool/run/boot_dir/hw including /Work/Genode/genode-17.08/tool/run/image/uboot including /Work/Genode/genode-17.08/repos/os/run/rico_no_usb.run building targets: core init server/pin_mux_ctl server/shared_mem drivers/platform/spec/437x drivers/platform/spec/437x/client drivers/timer drivers/gpio/spec/437x drivers/pwm drivers/i2c drivers/uart drivers/sd_card drivers/pruss app/soc_leds server/ffat_fs app/motor_control app/ap_cli app/ap_sensors app/autopilot spawn make core init server/pin_mux_ctl server/shared_mem drivers/platform/spec/437x drivers/platform/spec/437x/client drivers/timer drivers/gpio/spec/437x drivers/pwm drivers/i2c drivers/uart drivers/sd_card drivers/pruss app/soc_leds server/ffat_fs app/motor_control app/ap_cli app/ap_sensors app/autopilot make[1]: Entering directory '/Work/Genode/genode-17.08/build/437x' Error: target 'server/ffat_fs' does not exist Makefile:211: recipe for target 'error_missing_targets' failed make[1]: *** [error_missing_targets] Error 1 make[1]: Leaving directory '/Work/Genode/genode-17.08/build/437x' Error: Genode build failed make: *** [run/rico_no_usb] Error 252 Makefile:309: recipe for target 'run/rico_no_usb' failed. Thanks, Bob Stewart ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ genode-main mailing list genode-main(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users August 2017