users

users@lists.genode.org

2285 discussions

Start a nNew thread

Re: Workflows
by Colin Parker 24 Dec '22

24 Dec '22

2 1

Workflows
by Will Senn 23 Dec '22

23 Dec '22

Hi, I have been watching the genode project for quite a while now - seems like at least 10 years, if not more. I have tried it off and on, over the years, but until recently didn't really give it more than a quick run through. Now, I'm getting more interested. I've got a Thinkpad T430 and it seems to mostly work with Sculpt 22.10 running on a 32GB USB 3 drive. I have a few questions: 1. Is Wifi on the T430 supposed to work? I couldn't get it to do more than scanning. There are some teensy tiny error messages in the logs, so if it helps I could get out my magnifier and share them, but if there's a known issue, I figured y'all would know that without the specific error message. The wired connection works, so I'm ok with that as a fallback (but it makes it less mobile). 2. Persistence - what about persistence? I picked the ram-fs per the getting started document, but I would like to save SOME stuff- say bookmarks and source code, how do I do that? 3. I read that the genode folks use Sculpt as their daily drivers - so I'm guessing they don't boot from USB, build their environment up from scratch, add in firefox, terminal, whatever and so on, every day, just to start doing other productive things. Is there somewhere where typical workflows are described? Oh, and thanks for doing this - I like the modularity and exposed dependencies. Thanks, Will

3 4

fec_nic_drv runtime error in Genode 22.11
by Pontus Åström 22 Dec '22

22 Dec '22

I upgraded genode-imx and genode to version 22.11 for my IMX project. As per the drivers.config example in genode-imx/recipes/raw/drivers_nic-imx8q_evk/drivers.config I added a new ROM service for the nic_drv.dtb as follows: <service name="ROM" label="nic_drv.dtb"><parent label="fec_nic_drv-imx8q_evk.dtb"/> My fec_nic config now looks like as follows: <start name="eth0_drv" caps="130" priority="0"> <binary name="fec_nic_drv" /> <resource name="RAM" quantum="20M"/> <resource name="CPU" quantum="30"/> <config verbose="yes" mode="uplink_client"/> } <route> <service name="CPU"><parent/></service> <service name="LOG"><parent/></service> <service name="PD"><parent/></service> <service name="RM"><parent/></service> <service name="ROM" label="nic_drv.dtb"> <parent label="fec_nic_drv-imx8q_evk.dtb"/> </service> <service name="ROM"><parent/></service> <service name="Uplink"> <child name="net0_router"/></service> <service name="Timer"> <child name="timer_drv"/></service> <service name="Platform"><child name="platform_drv"/></service> </route> </start> Now everything compiles successfully but I get a runtime setup error where the driver complains about an unavailable IO resource: [init -> eth0_drv] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [init -> eth0_drv] clocksource: dde_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 3526361616960 ns [init -> eth0_drv] sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2199023255500ns [init -> eth0_drv] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [init -> eth0_drv] clocksource: Switched to clocksource dde_counter [init -> eth0_drv] mdio_bus: Fixed MDIO Bus: probed [init -> eth0_drv] Error: memory-mapped I/O resource 0x30be0000 (size=0x10000) unavailable What might be the cause of this error? Best regards, Pontus

3 4

base-linux: LD: exception during program load
by Pirmin Duss 21 Dec '22

21 Dec '22

Hello Genodians While Testing the `wasmedge` application that I'm porting with the Goa tool (goa run), I get the following errors: ``` Error: _map_local: lx_mmap failed(addr_in=0x0, addr_out=0xffffffffffffffed/-19) overmap=0 Error: LD: exception during program load: 'Genode::Region_map::Region_conflict' Error: Uncaughht exception of type 'Genode::Region_map::Region_conflict' Warning: abort called - thread: ep ``` I tried to follow the path that leads to this by adding some debug prints to the code in base-linux. If I'm not mistaken, the error happens, when in `load_phdr()` in the file `base/src/lib/ldso/include/file.h` a temporary dataspace is created. The binary compiled for x86_64 is 312K in size. Has somebody an idea what could be going wrong? Best regards, Pirmin

2 3

Announcement: Sculpt OS 22.10 released
by Norman Feske 20 Dec '22

20 Dec '22

Hello everyone, I'm happy to announce today's release of the Genode-based Sculpt operating system version 22.10. https://genode.org/news/sculpt-os-release-22.10 At the surface, this version is a maintenance release with almost no visible changes. Under the hood, however, we poured immense efforts into the lowest-level parts of the driver infrastructure like the discovery and management of PCI resources and the hotplugging of USB devices. Those low-level architectural changes left almost no driver unturned. We thoroughly tested Sculpt on our team's arsenal of machines. Please let us know how it works on your's. Besides the driver-related changes, seasoned Sculpt users might notice performance improvements in several areas, ranging from faster system startup, over increased network throughput, to improved GUI responsiveness. The release is accompanied by up-to-date packages. For example, you can find - An updated Chromium engine in the form of the Falkon and Morph web browsers in cproc's depot, - An updated audio driver based on OpenBSD 7.1 in genodelabs' depot, - Performance and battery monitoring tools in alex-ab's depot. As a starting point, please find a ready-to-use disk image at the Sculpt download page: https://genode.org/download/sculpt The matching documentation for using Sculpt or building it at home is available at: https://genode.org/documentation/articles/sculpt-22-10 https://genode.org/documentation/sculpt-22-10.pdf I hope you'll enjoy 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

2 3

Compiling toolchain on void
by Sagar Acharya 13 Dec '22

13 Dec '22

On voidlinux, packaged ncurses doesn't have non-UTF version It has ncursesw accroding to the devs there. $pkg-config --exists ncurses && echo foo $ Above command doesn't print foo. Replacing ncurses with ncursesw does. Will I face future issues building toolchain with this? Thanking you Sagar Acharya https://designman.org

2 3

Announcement: Genode OS Framework version 22.11 released
by Christian Helmuth 30 Nov '22

30 Nov '22

Hello Genodians, it's end of November and, hence, it's time for a fresh Genode release. This time the release addresses a variety of topics from least-privilege device drivers to virtualization improvements on ARM and x86 with the following highlights. The first notable improvement is the completion of our year-long effort to a unified cross-platform device-driver infrastructure. The uniform use of the generic platform-driver interface renders the I/O-related foundation of the system much more dependable and clear. Next, the current version adds support for Intel Gen12/Iris Xe to our accelerated graphics stack and hugely improves robustness and performance of the GPU multiplexer component. Further, the release includes all ingredients for an integrated hardware-software co-design workflow with Genode on Xilinx Zynq. This enables the development of IP cores for the FPGA programmable logic and Genode components in tandem and allows system designs that include hardware reconfiguration at runtime. The current release contains the following changes and new features: - Hardware-software co-design with Genode on Xilinx Zynq - Hardware-accelerated graphics with Intel GEN12+ GPUs - Unified device-driver infrastructure across PC and ARM - Low-level support for suspend/resume on PC hardware - Device drivers - New PinePhone drivers for audio, camera, and power control - New PCI and network drivers for NXP i.MX - Intel display-driver support for 12th-Gen hardware - PC audio driver updated to OpenBSD 7.1 - Forthcoming Sculpt OS variant for the PinePhone - Virtualization - Improved usability of the ARM VMM - Virtio device models for the Seoul VMM on PCs - MSI support for the base-hw microkernel Read the complete release documentation for the version 22.11 here https://genode.org/documentation/release-notes/22.11 Best regards -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://twitter.com/GenodeLabs · https://genodians.org/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

USDHC driver failure and imx8mm platfrom support
by Jean-Adrien Domage 24 Nov '22

24 Nov '22

Dear Genodians, I need help with the clock controller module in the platform driver for an imx8mm-based SoC. We must configure the clock controller module to communicate with an eMMC device. We have worked with the Compulab imx8mm IoT gateway for a year. So far, it has worked exceptionally well. We received a board from Compulab with a new revision and an updated Linux BSP a few weeks ago. Unfortunately, the new version of that board broke the eMMC driver. I have not yet been able to get eMMC working with the new driver. We ported the eMMC driver from the older Linux BSP for the older version of the board. That version of the driver does not work with the new board because of a voltage validation sequence failure. I suspect this is because we assumed only minimal modifications are needed in the platform driver to enable imx8mm from the existing imx8mq base. I recently discovered that the CCM register definition differs quite substantially between imx8mm and imx8mq. You can see this discrepancy in section 5.1.8.1 ("CCM_analog memory map definition") from the SoC reference manual of the imx8mq and imx8mm SoC. It looks like the older board worked out of pure luck because U-Boot sets these CCM registers correctly, and the platform driver does not alter them in a way that breaks the expected behavior. Here are my thoughts on solving the eMMC driver of the new board: There appears to be no way around rewriting `ccm.cc` and `ccm.h` of the `platform_drv` for the imx8mm SoC to set the CCM registers correctly. However, I'm not 100% convinced that it would help with my eMMC problem. 1. This approach seems straightforward fix the CCM registers to set the proper clock settings and gating. Can someone confirm? 2. To someone with experience with the `sd_card_drv` imx8mq, do you think fixing the CCM would also solve any voltage validation sequences? 3. The new Linux eMMC driver tries to reconfigure the `pinctrl` for the controller multiple times. Is it currently impossible to do that from a component with base-hw kernel using the Linux DDE? Only the `platform.cc` from the `bootstrap` boot module seems to be able to set that configuration. Setting that configuration within the `bootstrap` module is how we currently achieve it on the older board. I have pushed my imx8mm changes to the following repository: https://github.com/a-dmg/genode-imx/tree/1558-merge_imx_and_imx8mm_repos This repo works with Genode 22.08 on the older revision of the Compulab imx8mm IoT gateway. I created a run script called `sd_card_imx8mm_iot_gate.run` to verify this. Cheers! Jad ---- Jean-Adrien Domage Software Engineer Gapfruit AG

2 2

Regarding RISCV on genode virt_qemu_riscv
by Pranab Kumar Rout cs21m045 23 Nov '22

23 Nov '22

Hello genodians, We are trying to port genode for BOARD=virt_qemu_riscv I could not find the "virt_qemu_riscv" directory inside genode. So I cloned the riscv inside repos under genode from " https://github.com/genodelabs/genode-riscv/". I build the directory for riscv inside build Then I ran the following command: > make run/log BOARD=virt_qemu_riscv KERNEL=hw Please help me under the error I received. I have attached last few lines of the terminal --------------------------------------------------------------------- Library core-hw-virt_qemu_riscv COMPILE version.o MERGE core-hw-virt_qemu_riscv.lib.a Program core/hw/core-hw-virt_qemu_riscv make[1]: Leaving directory '/home/pranab/MTP/genode-riscv/genode/build/riscv' genode build completed using 'ld-hw.lib.so' as 'ld.lib.so' core link address is 0xffffffc000000000 spawn qemu-system-riscv64 -nographic -serial mon:stdio -kernel var/run/log/boot/image.elf -m 512 -machine virt -cpu rv64,priv_spec=v1.10.0 -bios default -global virtio-mmio.force-legacy=false -device virtio-net-device,bus=virtio-mmio-bus.0,netdev=net0 -device virtio-mouse-device -device virtio-keyboard-device -device virtio-gpu-device -netdev user,id=net0 qemu-system-riscv64: Unable to load the RISC-V firmware "opensbi-riscv64-virt-fw_jump.bin" Aborting, received EOF Log step failed, retry. ------------------------------------------------------------------------ Regards, Pranab

3 2

Test Genode on RISC-V from release notes Failed
by Pranab Rout 27 Oct '22

27 Oct '22

Hi all, I was following the instructions in the release notes 16.02 ( Section 'Steps to test genode on RISC-V'). url - https://genode.org/documentation/release-notes/16.02 I was able to execute successfully all the given steps The last command - 'make run/printf' is not working. There is no run directory nor printf script. Kindly help me with in this problem and with some resources also, so that I can proceed further. I am working on to build Genode based OS on RISC-V. Kindly guide me by providing a roadmap to follow and learn. Regards, Pranab

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users