users November 2022

users@lists.genode.org

7 participants
7 discussions

Can Genode run on the Mixtile Blade 3?
by Jacek Rużyczka 06 May '23

06 May '23

Good evening Genodians, in a couple of months I'll receive a number of Mixtile Blade 3 SBCs (based on the RK3588) https://www.crowdsupply.com/mixtile-limited/mixtile-blade-3 and would like to (at least) try to equip them with the Genode OS. What's necessary for my project, is clustering four such nodes with a PCIe switch (supplied by Mixtile; see their web page) as well as using single SBCs as storage nodes, which will be connected to a hard drive. Is it possible to port Genode onto this platform, or is this impossible with the current version? I simply don't wanna start an infaust undertaking. Thank you. Regards Jacek Rużyczka

2 4

Regarding ARM on Genode
by Divya Sharma 10 Apr '23

10 Apr '23

hello genodians, I'm Trying to port Genode OS for i.MX 8MQ boards (arm_v8a). successfully generated .img file but don't know how to run this img file i don't have i.MX board so I have to run on Ubuntu (linux). I have tried qemu emulator but i think qemu doesn't supported board. (basically want to run genode os for ARM.) Please give some guidance on this. Thanks & Regards

6 25

using GOA to port libraries
by Pirmin Duss 10 Jan '23

10 Jan '23

Hello Genodians As part of a project, I will port WasmEdge [1] to Genode. As WasmEdge uses cmake as build system my idea is to use GOA to port it. There is already a port of WasmEdge to the SEL4 kernel [2]. WasmEdge uses several libraries of which some also use cmake as build system. To start small I first want to port the `spdlog` library. Before working on the big dependency in form of the `lld` library from the `llvm` project. If I issue `goa build` successfully runs `cmake` but building fails afterward. There are a lot of `[-Werror=effc++]`. I tired different ways to set `CC_CXX_WARN_STRICT=` in the files `cmake_args` and `make_args`. Unfortunately none of them helped. Can anybody give me some hints how I could achive this? My project is located at [3]. Regards, Pirmin [1] https://github.com/WasmEdge/WasmEdge [2] https://github.com/second-state/wasmedge-seL4.git [3] https://github.com/trimpim/wasmedge-genode

3 10

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

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users November 2022