users

users@lists.genode.org

1 participants
2310 discussions

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

Genode on RK3588 and Emulation
by Michael Grunditz 26 Oct '22

26 Oct '22

Hi, I am planning to start porting Genode to RK3588 Soc any day now. On top of that a cpu emulator for running 32bit code. The little cpu in the soc supports 32bit , but the big doesn't in a decent way. I think the basic bringup will be easy, but after that it becomes harder. I still haven't seen a manual for the soc. I have seen a dts in uboot and with a bit of luck it works similar to RK3399. For the emulation I use Unicorn emulation engine. A stripped down qemu that only does cpu. I hope that porting that to Genode will be a easy project, it doesn't have much dependencies. I am currently hacking it bit to fit my needs. I plan to expose hardware directly to emulator, probaly by memory pointers that Genode sets up. First step is the all important debug uart. As for Genode I think the soc would be a great platform for Sculpt. However I have no interest in Sculpt , so will not do that. But since I will do the basics I guess that someone can do Sculpt on top of that. Cheers! -- Best regards, Michael Grunditz ** **

3 16

scripts/extract_cert failed OpenSSL/bio.h no file
by Maigurs Stalidzans 14 Oct '22

14 Oct '22

Hi all, I’m new to Genode and Sculpt, I am trying to build Sculpt from source as described here: https://genode.org/documentation/articles/sculpt-22-04#Building_the_boot_im…, but it always fails, when starting to build linux components. Failing begins when I add sculpt_distribution-pc. What I am doing wrong? Regards Maigurs

2 3

dde_linux: trying to port the emmc for arm_v8a driver from linux
by Jean-Adrien Domage 22 Sep '22

22 Sep '22

Dear Genodians, I am currently porting the emmc driver from the compulab's Linux source tree [1]. [1] https://github.com/compulab-yokneam/meta-bsp-imx8mm/blob/iot-gate-imx8_r3.0… Everything went more or less smoothly until I got to this assembler error: ``` /tmp/ccOLpMJW.s: Assembler messages: /tmp/ccOLpMJW.s:987: Error: section name '__irqchip_of_table' already defined as another symbol ``` This error message indicates a rather obvious error: It seems the symbol with that name is defined twice with different 'type' in different compilation units. However, when using grep I can find the symbol within `repos/dde_linux/src/lib/lx_emul/spec/arm/irqchip.c` but it is not that clear within the Linux source where it is defined. I assume in a linker script but I'm not sure at all. I couldn't find it using grep (not event a declaration, maybe some macro magic happen here). Which let me think that the error might not be due to what I actually think... I tried with nm & grep on each generated object in the build directory, but couldn't find the culprit either. I wonder if someone has some experience with dde_linux, whom may have some idea of what could be the causes? Or what I can try to debug it harder... PS: I am aware that some parts of the lx_emul layer may not work with this source tree, as it has a different version (5.10.72) from the one in use by dde_linux. I expect to have some trouble with this at some point, maybe this is the case already? Many thanks for reading me! Cheers, Jean-Adrien

4 4

Rust bindings?
by Sam Crow 08 Sep '22

08 Sep '22

Hello again!I was going to try to install Wasmer to Genode but it is written in Rust. Are there Rust bindings for Genode yet? If not, can I help get them going?

3 2

Using Quectel EG25-G in ECM mode on PC
by Duss Pirmin 04 Sep '22

04 Sep '22

Hello Genodians In the Release notes, I read that on the Pinephone it is possible to use the Quectel EG25-G in ECM mode to communicate over LTE. Which I find is a really great feature. We have a hardware (UP-Xtreme i7 8th gen) which comes with the same modem. I really like the idea of using the modem in this way. As far as I understand, the run script `run/modem_pinephone.run` of the `genode-allwinner` repository does exactly that. My plan is to create a PC version of `pinephone_modem` that controls the modem. Do you think, this is possible? Currently I do not have a idea what serial port I should use to connect to the command channel of the modem. On the Pinephone, `ns16550_uart` is used to do that. Which serial port should be used on the PC platform? Regards, Pirmin

2 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users