users August 2014

users@lists.genode.org

20 participants
21 discussions

Mark vea9x4 and imx31 deprecated
by Stefan Kalkowski 27 Aug '14

27 Aug '14

Hey Genode hackers, I'd like to propose to mark the following hardware boards as deprecated, and to discontinue the support of both platforms in Genode in the medium term for the following reasons: * i.MX31 is pretty old, and AFAIK not used by any Genode hackers * The Versatile Express platform is mainly used to get hands on fresh ARM CPUs at first, not widely used as a normal development board, and not used as a platform in practice at all, moreover it's quite expensive, and thereby not widespread. * The support of Cortex A9 cpus (cpu used in vea9x4) is already covered by the Pandaboard and the PBXA9 platform * A lot of (not widely used) hardware platforms is a burden for the (currently) relatively small Genode development community. * Last but not least, both platforms are not tested automatically like other hardware platforms Genode supports. Normally we try to automatically test a bunch of basic tests all night on various hardware platforms. Of course, we could add i.MX31 and vea9x4 to our test farm, but that includes hardware and engineering costs with (at least for us) questionable benefit. So, as long as there is nobody who cries: "No, I use one of these platforms with Genode! I need it." I would vote for the removal of both. Regards Stefan -- Stefan Kalkowski Genode Labs http://www.genode-labs.com/ · http://genode.org/

3 2

Adding Sparc/LEON3 support to Genode
by Johannes Schlatow 25 Aug '14

25 Aug '14

Hey guys, I'm trying to add a new architecture, namely the LEON3, to Genode. Some time ago, I already added rudimentary LEON3 support to Fiasco.OC. Thus I thought it shouldn't take too much of an effort to get this working with Genode on top of it. The LEON3 port for Fiasco.OC was based on the l4re snapshot from April 2013. I therefore (back)ported the implementation to Genode's foc clone. You can find the code at github [1] (beware, it's not tested yet). I also added the foc_leon3 build target along with the required platform-specific code to Genode [2]. Unfortunately, I got stuck a little at this point. I.e. when I run e.g. 'make run/printf' for this target, I get a couple of linker errors that I cannot relate to anything in the Genode source code, e.g.: repos/os/src/init/main.cc:178: undefined reference to `atexit' `.text.__sparc_get_pc_thunk.l7' referenced in section `.text' of /build/foc_leon3/var/libcache/cxx/cxx.lib.a(supc++.o): defined in discarded section `.text.__sparc_get_pc_thunk.l7[__sparc_get_pc_thunk.l7]' of build/foc_leon3/var/libcache/cxx/cxx.lib.a(supc++.o) build/foc_leon3/var/libcache/cxx/cxx.lib.a(supc++.o): In function `__gnu_cxx::__verbose_terminate_handler()': (.text+0x31cc): undefined reference to `_impure_ptr' I assume these errors might be related to the tool chain but this is a rather wild guess. Do you have any (more educated) suggestions? I'm using the dev version of the bare-c compiler provided by gaisler [3] which bases on gcc 4.6.0. Of course, this is not an optimal solution but the best I could achieve so far. [1] https://github.com/ValiValpas/foc/tree/leon3 [2] https://github.com/ValiValpas/genode/tree/leon3 [3] http://developer.gaisler.net/download/bcc/linux/4.6.0/ Cheers Johannes

3 4

MMU issues with AM335X and 14.05
by Bob Stewart 19 Aug '14

19 Aug '14

Hi, I've been casually using Genode on a TI Beaglebone SoC for about a year now. One of the first issues I had was that virtualized memory management wouldn't work at all. This I eventually traced to memory attributes in TLB entries. The Am335X processors expects cacheability to be: Inner -- Write-thru, No Write Allocate Outer -- Write-back, Write Allocate. So, based on the info in the ARM Architecture Ref Manual for the Arm_v7 (pp 1368), I set the attributes in memory_region_attr (Genode 13.08) to : if(Arm::Page_flags::D::get(flags)) return Tex::bits(0) | C::bits(0) | B::bits(1); // return Tex::bits(2) | C::bits(0) | B::bits(0); if(Arm::Page_flags::C::get(flags)) return Tex::bits(5) | C::bits(1) | B::bits(0); // return Tex::bits(5) | C::bits(0) | B::bits(1); return Tex::bits(6) | C::bits(1) | B::bits(0); MMU worked fine after this change, until 14.05 came along. When 14.05 was released I attempted to migrate to it and made the needed changes for the extensive changes needed for MP. I used the above memory attribute settings (now in translation_table.h), but another MMU issue occurred and the kernel would not complete initialization. I decided to stay with 14.02 as I was working with a uni-processor system anyway and I wanted to complete porting of some linux drivers. I went back to the 14.05 issues today and found I could get the kernel initialization to complete successfully if I reverted the S bit to "unshared" in the memory attributes in a Section entry create. Prior to 14.05 this bit was set to "unshared" and was presumably changed in 14.05 to allow for multiple processors accessing the same memory regions. It's unclear to me why this behaviour occurred but it is possibly due to the specific implementation of the Arm_v7 architecture on this particular processor. Or is there something I'm missing in the implementation of multiple processors in Genode? In addition, after completing kernel initialization, core's "main" function is entered, the info message for creating local services shows up, a translation for the top of RAM (0x80000000) is created, then the message "failed to communicate thread event" occurs and init is never called. Any thoughts on why that message is appearing would be appreciated. It appears to be coming from initialization of the root interfaces. Thanks, Bob Stewart

2 14

Building Genode with Nix
by Emery Hemingway 18 Aug '14

18 Aug '14

In what started as an effort to fix some simple problems when building Genode on NixOS, I have gone ahead and attempted to replace the Make build system with one implemented in Nix. For those not familiar with Nix there is a brief overview here, but what I have done falls outside the scope of package management. http://nixos.org/nix/about.html The theory behind Nix is explained in detail here. http://dspace.library.uu.nl/handle/1874/7540 To start out with, here are some problems with a Nix build system: * Nix must be ported to Genode if Genode shall be self hosting. * Each Make target will probably have to be re-expressed in Nix. * Nix produces more arcane output than Make. Some benefits as I see it: * Nix is the only build system dependency. * More build parallelism. * Lazy dependency evaluation means faster rebuilding. * Binary component packages. * NixOS can be nested in the Genode build system. * Genode can be nested in the NixOS build system. * Less boilerplate. * Less user interaction. That said, my conversion is far from complete, my focus has been on getting the Linux and Nova implemenations working. I have core and init building for Linux and Nova as well as a number of tests. The Expect framework for executing Genode has been wrapped and works for Linux, but I will have to express the Nova kernel before moving on to Qemu support. I've been bypassing ARM to avoid getting into the details of the spec managment for now. If anyone would like to try it out I'm working on the 'nix' branch at https://github.com/ehmry/genode.git The only depency is Nix which you can get here: http://nixos.org/nix/ There is a script named 'try_me.sh' that will run the tests that have been defined. If you wish to explore further the command that you will need to get aquainted with is 'nix-build'. For example, to build some components: nix-build ~/genode/specs/x86_64-nova.nix -A base.core nix-build ~/genode/specs/x86_64-nova.nix -A os.tests nix-build ~/genode/specs/x86_64-linux.nix -A run.thread Nix-build will leave a symlink named 'result' in your current directory that contains the output of the Nix expression you call. To remove the outputs that Nix has built, delete the result symlink and run 'nix-store -gc' to invoke the garbarge collector. If you first want to know what Nix will do when building a run from scratch, here is a summary: Install dependencies for the Nix build environment, Nix will likely not use anything in your current PATH. Download and patch the Genode toolchain for the Genode build environment. Compile the sources of each dependency into object files. Merge objects into libraries. Link libraries into applications. Execute Genode and leave the build output and a log of the run in a directory in the Nix store. If there are any questions I will be lurking as 'emery' in the IRC channel on Freenode. As some of us like to say over here, "If it ain't broke, you're not trying." Emery Hemingway

2 2

Platform Initialization Problem
by chirag garg 18 Aug '14

18 Aug '14

Hi stefan, Thanks a lot in Advance, We are trying to debug the " Failed to communicate Thread Event ". And we found that Platform is not getting Initialized, we are facing Problem in the Platform constructor located in file : base-hw/src/coe/platform.cc In the Platform () constructor Rom_module * rom_module = new (core_mem_alloc()) Rom_module(header->base, header->size, (const char*)header->name); is not getting executed(giving page fault) . Do you know what could be the problem ? Regards Chirag Garg IIT Madras , Rise Lab

7 10

GUI API changes just merged in the master branch
by Norman Feske 15 Aug '14

15 Aug '14

Hello, I'd like to give you a heads-up information about several API changes that entered the master branch today. When updating to the new version, please pay attention to the commit log. The most significant changes are: ROM: The ROM session interface has been enhanced by a new 'update' function that allows a light-weight update of ROM module content without the need for unmapping the ROM dataspace. (see the documentation in rom_session.h) Framebuffer: The session interface gained a new facility for synchronizing the client with a periodically working server by the means of receiving sync signals. Currently, nitpicker is the on server that supports this feature. Nitpicker: The session interface has been completely revised to support the atomic processing of nitpicker operations. View operations are no longer performed on view capabilities but by invoking the session interface using session-local handles. The mouse pointer and status bar are no longer parts of nitpicker but realized as separate programs located at os/src/app/pointer and os/src/app/status_bar. Please refer to the README at os/src/server/nitpicker to learn about nitpicker's new configuration parameters. I also recommend to have a look at the os/run/demo.run script to see a working example of how those components can be tied together. Loader: The loader session has been updated to use the new nitpicker interface. Window manager: New components for window management have landed in the gems repository. The components are server/wm, app/decorator, and app/floating_window_layouter. Combined, they supplement Genode's existing GUI infrastructure with window management. All Qt5 run scripts have been updated to use the new window manager. More details about the enhanced GUI stack will be presented in the release notes of version 14.08. All programs included in the Genode mainline repository have been updated to use the new interfaces. So you can find plenty of examples of how to use nitpicker's new API (e.g., have a look at testnit). If you run into any problems with updating to the new version, please report. So we can assist. Cheers 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

seL4 now open source
by Ernst Rohlicek jun. 12 Aug '14

12 Aug '14

Greetings, The seL4 microkernel has recently been open-sourced and is now hosted on GitHub. It features high performance and includes proof of formal correctness, ie. freedom of bugs. Maybe this has relevance for your Genode OS framework regarding expanding the choice of base platforms.

3 2

Celebrating Genode's 6th Anniversary
by Norman Feske 11 Aug '14

11 Aug '14

Hello everyone, the 6th anniversary of the Genode OS Framework is approaching, which gives us many reasons to celebrate. To just name a few, in the past year, we have conquered VirtualBox to run on Genode, embraced NetBSD Rump kernels, and went full steam ahead with the development of our custom base-hw kernel. Business-wise, we are happy to be recognised as a trusted partner by our existing longtime customers. At the same time, we are excited that our company has gained much visibility outside of Europe. For example, the wide anticipation of our work on ARM TrustZone has taken us by surprise. Let us celebrate the 6th anniversary of Genode together! To follow up with the tradition of the past years, we invite you to join our barbecue and campfire at the river Elbe: Google Maps: http://goo.gl/maps/C0luj 28th of August, 6 pm near Moritzburger Str. 1 in Dresden Whether you like to enjoy grilled vegetarian or non-vegetarian food, clink glasses with the Genode team, or catch up with local microkernel enthusiasts, you are welcome! If you are going to attend, we would greatly appreciate a short note from you to ease our preparations: info@...1... Cheers 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

connect to existing RPC server
by Mhamad Hmad 11 Aug '14

11 Aug '14

Hi , In the Genode RPC we start the client and the server in the same time as in Hello world tutorial. in my case i want the server to serve many clients in the same time .if i create run file for each client each time a new server instance (process) will be created . are there any ways to make the second client use the same running server . i tried to run the both client in same run file but it did not work.I am sure that there are some way to get capability from the existing server . thank you in advance . -- *Mohammad *

8 14

Problems with virtualbox after commit cdb7904
by Christian Menard 05 Aug '14

05 Aug '14

Hi, I'm trying to tun NOVA(64)+Genode+VMBox+Android on a System with Intel Core i5-4302Y CPU. So far it worked fine, but I got trouble since commit cdb7904 "timer: nova specific version of the service". With this patch applied, Android on VMBox is not booting up anymore. Instead I get messages like this: [ 19.900000] INFO: rcu_preempt self-detected stall on CPU I tried to reproduce the issue in QEMU, but there everything works fine. So the issue seems to be related to my Hardware. In the logs everything looks fine, I couldn't find any abnormalities. Do you have any ideas on what might go wrong or where I should start investigating? Unfortunately my debugging possibilities are limited, as I have no serial connection. Thanks Christian

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users August 2014