users February 2019

users@lists.genode.org

15 participants
13 discussions

usb_drv error -92 for RPi | Genode 18.05 with Fiasco.OC 79
by Alexander Weidinger 18 Apr '19

18 Apr '19

Hello everyone, when executing 'lwip' on the RPi 2, I get the following output for the usb_drv: > [init -> usb_drv] dev_info: DWC OTG Controller > [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 1 > [init -> usb_drv] dev_info: irq 9, io mem 0x00000000 > [init -> usb_drv] dev_info: USB hub found > [init -> usb_drv] dev_info: 1 port detected > [init -> usb_drv] dev_info: new high-speed USB device number 2 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/all, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 3 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/all, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 4 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 5 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: unable to enumerate USB device Does anyone have an idea what I can do, to get the Ethernet adapter working? Any help is appreciated! I don't really understand the problem here, since the driver works flawlessly for the RPi 1 B+ (using foc_rpi as platform) - which uses the same chip as the RPi 2 (SMSC LAN9514). My Genode version [2] and Fiasco.OC version [3]. To the backstory: ----------------- I am currently in the process of "porting" Fiasco.OC/Genode to the Raspberry Pi 2 (Model B). As a basis I use Genode in the version 18.05 and Fiasco.OC in the version 79. I created a new device, the rpi2, and based it on the already available rpi model. The main changes I did for the rpi2 platform [1] are - the different arm architecture - from armv6 to armv7a in a few files - the different physical base address - from 0x2000:0000 to 0x3f00:0000 - a RAM size of 1008 MB starting at 0x0000:0000 (1024 MB - 16 MB for peripherals) I use version 79 of the Fiasco.OC kernel since it adds support for the three different BCM283X platforms. In order to get version 79 of the kernel running with Genode, I used the official 79 as a basis and cherry-picked commits from Genode's version of Fiasco.OC (72). [0] My setup works completely fine for the RPi 1 (Model B+), even for the usb/nic driver. As the RPi 1 (Model B+) makes use of the SMSC LAN9514, instead of the SMSC LAN9512 (used in RPi Model B) it should also work for the RPi 2 (Model B), since this SBC also uses the SMSC LAN9514. [0] https://github.com/skalk/foc/commits/r72 [1] https://github.com/irgendwie/genode/commits/foc-rpi2 [2] https://github.com/irgendwie/genode/tree/foc-rpi2 [3] https://github.com/irgendwie/foc/tree/genode-r79-rpi2 ----------------- Best regards Alexander

5 15

Version release 19.02 fixes my problem :) Leaves me with a question...
by baconicsynergy＠protonmail.ch 01 Mar '19

01 Mar '19

I was successfully able to build a new sculpt disk image based on 19.02 :) Erased my VM and am starting from scratch again. What should I choose for my File System (Target) for cnuke's Download Debian procedure?

2 1

Genode on RPI - second round
by Tomasz Gajewski 28 Feb '19

28 Feb '19

Hi to all. In my last message I wrote: "Now I'm starting again from start but with different knowledge level." and now I have some preliminary results and another set of issues/questions. After making run/log work on single core I had two possible directions to take: device drivers or enable smp. I started with smp as with the device drivers I need an advice about build system (later in this email). For SMP on RPI I implemented new timer driver as the current one was not capable to support multiple independent timers for cores and new PIC driver - for timer and inter processor interrputs. Current code is in (rewritten) same branch as previously at [1] in case you wanted to look. run/smp test is almost working on all cores with the exception for thread cleanup (which will be another question later in email). 1. Register sets. On multicore Raspbery Pi there are sets of registers in which each register has the same structure and each is "assigned" to different core. Currently I replicated definitions of registers for each core [2] but it's obviously not a good solution. Additionally it forces to write ugly code when cpu_id is in the variable as in [3]. Is there some support in Genode for such structures? If not, do you see how that could be implemented? Some wrapper for Register? I fail to see how dynamic value of 'cpu_id' could be nicely mixed with register offsets passed as template arguments. I think ideally it would be to define something like this: struct CoreTIrqCtl : RegisterSet<0x40, 32, COUNT, OFFSET> and use it like this: write<CoreTIrqCtl>(CPU_ID, 0); Any thoughts? 2. Interrupts handling I have doubts about interrupts processing. I have limited knowledge in this area so I may be totally wrong but based on what I read for RPI I think that: a. On one IRQ there can be more than one interrupt flag marking an exception. During this one entry to 'Thread::exception(Cpu&)' and later to 'Cpu_job::_interrupt(unsigned const)' all pending interrupts should be handled in some loop. Without that some interrupts may stay unhandled. And I don't see such loop in this code. One exception is taken from Pic driver, handled and that's all. b. I don't know where clearing an interrupt should be handled. I would have thought that 'Pic::finish_request()' would be good for this, but there are many empty implementations. Should code in 'Pic::take_exception(...) also clear the exception condition? My doubts come from feeling that if I do this too early "something" can happen before handling of interrupt is finished. If 'finish_request()' is a proper place to clear interrupt as handled than it would be useful to pass to it interrupt number earlier returned from 'take_request'. Otherwise there would have to be separate storage for each core in Pic to store information about currently handled exception on a given core. Am I right? Does it work properly in [4]? 3. run/smp test hangs during threads destruction Like I wrote earlier run/smp test is almost working on multiple cores. It hangs somewhere in [5] during destructing thread running non-zero core (destroying first one does not cause problems). I don't have any concrete questions here. The only ones are: a. Does this test properly work on arndale? b. Do you have any thoughts what can go wrong? Maybe I haven't implemented something important for smp yet? Only timer and IPI? 4. Drivers reused for different configurations Currently to support RPI3 I created configurations named 'rpi3bplus'. How should I proceed to reuse a driver written for rpi? For example framebuffer driver has 'REQUIRES = rpi' in target.mk [6] and that causes that it does not compile for my 'rpi3bplus'. It would be nice to have: 'REQUIRES = rpi|rpi3bplus' but I don't think it is possible. Can you suggest something? Tomasz Gajewski [1] https://github.com/tomga/genode/tree/rpi3bplus [2] https://github.com/tomga/genode/blob/rpi3bplus/repos/base-hw/src/core/spec/… [3] https://github.com/tomga/genode/blob/rpi3bplus/repos/base-hw/src/core/spec/… [4] https://github.com/tomga/genode/blob/rpi3bplus/repos/base-hw/src/lib/hw/spe… [5] https://github.com/tomga/genode/blob/rpi3bplus/repos/base/src/test/smp/main… [6] https://github.com/tomga/genode/blob/rpi3bplus/repos/os/src/drivers/framebu…

3 6

Announcement: Genode OS Framework version 19.02 released
by Norman Feske 28 Feb '19

28 Feb '19

Hello everyone, I'm proud to announce the release of Genode 19.02! This first release of the year already shows our commitment to our road-map's leitmotif for 2019 - making Genode relevant and attractive for a broader community. On that account, it features the "community experience" (CE) revision of Sculpt OS with an interactive way of discovering, installing, and deploying components provided by different software providers. Sculpt CE and the just announced Genodians.org blogging platform are supposed to work in tandem: Developers become able to promote new software by posting articles to Genodians.org. For Sculpt users, the software discovered at the website is just a few clicks away. The user does not need to trust the software provider because the interaction of the downloaded software with the Sculpt system is completely under the control of the user. This way, Sculpt becomes a rather playful and fun experience. Regarding our ambition to increase the utility value of Genode, the release features our port of OpenJDK with just-in-time compilation enabled for both ARM and 64-bit x86. The use of Java on an embedded platform is showcased by an exemplary system scenario called Boot2Java. This is just the tip of the iceberg. For the full story, please have a look at the release documentation: https://genode.org/documentation/release-notes/19.02 A short summary of the highlights: - Sculpt OS with federated software provisioning - Showcase of a Java-based IoT network appliance (Boot2Java) - Showcase for a component-based web service (Genodians.org) - OpenJDK with JIT on 32-bit ARM and 64-bit x86 - Improved Ada and SPARK support, including AUnit - Initial support for the OCaml programming language - Removal of deprecated APIs - API-safety improvements - Support of i.MX6 Quad Sabrelite and Nitrogen6 SoloX Have fun with exploring the new version! Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Seoul-net scenario hangs on "overmap attempt MEM" message when using uefi
by Parfait Tokponnon 27 Feb '19

27 Feb '19

Hello all, I got an issue when executing the seoul-net scenario in a freshly downloaded Genode directory and using uefi boot. Execution hangs on "overmap attempt MEM ....". It should be noted that it works fine with other boot option (disk, iso, ...). But I need the uefi boot and it used to work fine in old versions. Any idea to on to investigate this issue? Enclosed here the log file, as well as the modified build.conf and seoul.inc The tianocore.bin comes from here <https://www.kraxel.org/repos/jenkins/edk2/edk2.git-ovmf-x64-0-20190131.920.…> -- Parfait T.

2 2

Enhancement of German Wikipedia article
by Martin Stein 27 Feb '19

27 Feb '19

I have enhanced the German Wikipedia article about Genode by the paragraphs "Critique" and "Sculpt" and updated the article to the latest release. However, the new version needs a review to be published, so, if any of the German users likes to fasten the process: https://de.wikipedia.org/wiki/Genode Cheers, Martin

1 0

Properly build latest Sculpt image from latest source code?
by baconicsynergy＠protonmail.ch 26 Feb '19

26 Feb '19

I'm attempting to build the latest version of sculpt from the source code via the following procedure: - git clone https://github.com/genodelabs/genode.git - I'm checking out the latest NOVA pkg via - ./tool/depot/download genodelabs/bin/x86_64/base-nova/2019-02-12 - and the latest verison of sculpt via - ./tool/depot/download genodelabs/pkg/sculpt/2019-02-11 - I then make and configure the build directory and enable the proper repositories - I then attempt to run "make -C build/x86_64 run/sculpt KERNEL=nova" I receive the following error message: Error: missing depot archives: genodelabs/bin/x86_64/base-nova/2019-02-25 genodelabs/pkg/x86_64/sculpt/2019-02-25 However, these packages do not exist. I must be missing some silly error. Can someone tell me where I went wrong?

1 0

New Spanish Wikipedia article
by Martin Stein 25 Feb '19

25 Feb '19

I'm glad to announce that we have managed to translate the latest version of the English Wikipedia article about Genode into Spanish! Thereby, I'd like to invite everyone - especially all native Spanish speakers - to have a look at the result and maybe even contribute improvements: https://es.wikipedia.org/wiki/Genode Cheers, Martin

1 0

Sculpt OS
by voidpin 24 Feb '19

24 Feb '19

Hi, First things first, congratulations! I think Sculpt is the OS I've been looking for, mainly the concept of running a micro kernel and have drivers in userland. I've been playing with Sculpt (VC) for a few days. Have it on a 16GB usb and have aplyed Extend so the whole usb is used. It boots both on my Void Linux laptop in UEFI mode and on my NetBSD laptop in legacy mode without an itch. Also, all my wifi bands are detected and I had NO issues adding software from the repo. Although, documentation doesn't really describe how to install onto a SSD, I think I will manage with a slight work around. But, before I do that I have a few questions, if you don't mind!? 1) How to shutdown my machine? Up to now, I haven't figured it out and been forcing shutdown using the power switch. I've tried 'poweroff' and 'shutdown -p now' to no avail. 2) Is a new release coming soon? I have a SE_SV keyboard and although, I can do it with de this is not optimal. I might just write a keyboard definition, but if its coming soon, it would be a waste of time. 3) Related to 2)... I've changed config to use de instead of en_US, but everytime I restart its back in en_US!? I've looked through the documentation, but I'm afraid I'm doing something wrong, as changes are not stored!?! Thank you for your time and for this amazing OS. Regards, Pin Skickat från ProtonMail mobile

4 6

How to enable Virtualbox EFI firmware on sculpt
by Johannes Schlatow 22 Feb '19

22 Feb '19

Hi, I'd would like to boot my native Linux installation from within Sculpt using Virtualbox. First, let me briefly describe what I have done so far: I created a raw disk image that contains the relevant partitions (ESP, root and home), added the Block devices to the vfs of Virtualbox, and routed the Block sessions to the corresponding part_blk server. I also made the EFI firmware file available to Virtualbox. I created a vbox file and tested it on another Linux system. However, when using this vbox file on sculpt, I noticed that vbox does not respect the '<Firmware type="EFI"/>', i.e. neither my boot manager nor the UEFI shell appears. I had a look in the Genode repository and noticed that there is a vbox patch that removes (ifdef 0) the Nvram initialisation which is supposed to happen if the firmware type is EFI. Thus it appears that EFI support has been 'patched-out' from the virtualbox port. Is this intentional? Are there any major blockers that prevent us from using Virtualbox with some EFI firmware? Cheers Johannes

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users February 2019