users

users@lists.genode.org

6 participants
2306 discussions

Wandboard Quad GPIO mapping
by Edward Sandberg 30 Aug '18

30 Aug '18

I'm working with the imx6 GPIO driver on Wandboard Quad, using the gpio_led run file as a smoke test. Unfortunately, I've had only limited success controlling the GPIO pins exported to the Wandboard's JP-4. It is unclear where these pins map in the Genode imx6 driver (18.05, nova). In Linux, I can successfully toggle them all via /sys/class/gpio. The imx6 driver allows for 32 pins to be set to high or low and I have modified the run file and the main.cc file to blink sets of pins rather than just a single pin. If I set all 32 pins as output with an initial value of "0" in the run file and then blink the following sets of pins I see these results: 0-31: I read 3 pins blinking with a voltage meter 0-15: I read 2 pins blinking 0-6: I read no pins blinking 7-15: I read no pins blinking It seems as though it takes combinations of pins set to high and low at the same time to get a reading of high or low off of a particular pin, but I cannot divine the pattern. This leads me to think that there is a step missing in the initial configuration. Does anyone have a suggestion of what step I am missing to get predictable results? -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

2 1

Announcement: Genode OS Framework version 18.08 released
by Norman Feske 30 Aug '18

30 Aug '18

I have the pleasure to announce the release of Genode 18.08, which continues our story of sculpting Genode into a general-purpose OS. The release specifically addresses the device-driver support of modern PC hardware, the concern of applying microcode updates to Intel CPUs in a timely fashion, the scalability of application workloads, and the interactive usability of the system. The highlights of Genode 18.08 are: - Sculpt OS with live runtime view - Device drivers - Linux device-driver environment based on kernel 4.16.3 - Updated and enhanced Intel framebuffer and wireless drivers - De-componentized USB stack, support for isochronous devices - Improved device compatibility of NIC and PS/2 drivers - Experimental runtime for Zircon-based drivers - Base framework and OS-level infrastructure - NIC-router support for multiple uplinks - New VFS plugin for using LwIP as TCP/IP stack - Cached file-system-based ROM service - VFS plugin for importing initial content - Enhanced Ada language support - Libraries and applications - Python 3 - VirtualBox 5.1.38 - Platforms - New Intel Microcode update mechanism - Multiprocessor support for our custom kernel on x86 - Updated NOVA and Fiasco.OC kernels All of these and more improvements are covered in detail by the release documentation: https://genode.org/documentation/release-notes/18.08 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

endless repeating message when starting vbox with RAW format diks
by Pirmin Duss 27 Aug '18

27 Aug '18

Hello Genodeans I Try to run a Linux in a RAW disk partition. The boot loader runs and starts the kernel but then something goes wrong. [runtime -> work -> vbox] Warning: VMM: map_memory - write fault on ROM region!? gp=0xffff0000 [runtime -> work -> vbox] Warning: VMM: map_memory - write fault on ROM region!? gp=0xffff0000 [runtime -> work -> vbox] VMM: error: unmap not implemented The last line is endlessly repeating. If I let the guest run, like this, for about 1 minute, the whole system becomes unusable. If I dd a Windows 10 image in to the partition the guest boots without any problem. Does anybody have an idea, what could cause this issue? Attached are the VBOX and VMDK-template file. We have a small component, that creates the VMDK file form the template with the size of the partition. Best regards, Pirmin

1 0

Expanding an NVME partition to 1T hangs
by Duss Pirmin 27 Aug '18

27 Aug '18

Hello Genodeans I have upgraded my Sculpt notebook with a 1T NVME disk as I want to use different virtual machines. When I hit expand and configm, the expansion starts and about 20 seconds later the following message is printed: [runtime -> nvme-0.3.resize2fs] resource_request: ram_quota=30535680 [runtime] child "nvme-0.3.resize2fs" requests ressource: ram=30535680 A reboot is required, to use the disk again. If I boot the system afterwards, the partition is resized to 1T. Best regards Pirmin

3 4

Change to usb_drv? (17.11 -> 18.05)
by Steven Johnston 16 Aug '18

16 Aug '18

Hi All: One of my components that handles a USB device was working in 17.11 (x86_32, nova), but is causing problems when I attempt to run it in 18.05. The device is an FTDI-based USB-GPIO adapter (FT232H chip), along with a port of libftdi. The USB hub setup seems to work, but the FTDI setup generates an error in the log "ftdi_usb_reset failed", occurring when libusb_control_transfer() fails during a USB reset. There is a similar sounding issue mentioned in the release notes regarding usb_block_drv. Might it be the same? If so, has this been resolved in some general way? Thank you for any input, Steven

3 2

Genode Foundations book format
by astian 14 Aug '18

14 Aug '18

Hi, Looking for interesting things to read I came across this book, but would like to know if the last version (apparently 18.05) is available in some format less damned inflexible than PDF. Searching around turned up this URL: https://genode.org/documentation/genode-foundations-16-05.epub Which is ideal, except that an "...-18-05.epub" does not seem to exist. Thanks.

2 2

gdb_monitor does not work
by Alexander Senier 09 Aug '18

09 Aug '18

Hi all, I'm debugging an application on base-nova and trying to get remote gdb set up for that. Using gdb on base-linux is not an option right now, as the application exposes a different issue there. To verify that gdb works, I adapted the simple run/log example (see the attached delta). I'm using current master (f4ea50c6). When starting the run file, I see: [snip] Genode 18.05-203-gf4ea50c6f <local changes> 469 MiB RAM and 63253 caps assigned to init [init -> uart_drv] --- UART driver started --- [init -> gdb_monitor] using the pipe libc plugin [init -> gdb_monitor] Warning: sigaction: sigaction not implemented [init -> gdb_monitor] Process target created; pid = 1 [init -> gdb_monitor] Warning: unsupported ioctl (request=0x40047477) [init -> gdb_monitor] Warning: unsupported ioctl (request=0x80047476) [init -> uart_drv] open IRQ 3 [init -> uart_drv] [init -> gdb_monitor] Remote debugging using /dev/terminal [init -> gdb_monitor] Warning: fcntl(): command 4 args 66 not supported - terminal [init -> gdb_monitor] Warning: fcntl(): command 6 args 4294967295 not supported - terminal Then, I start gdb on the host from within the debug directory of the build: $ ln -s ld-nova.lib.so ld.lib.so $ genode-x86-gdb test-log GNU gdb (GDB) 7.3.1 Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=x86_64-pc-elf". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/alex/Documents/Componolit_GmbH/Devel/src/genode-master/build/x86_64/debug/test-log...done. (gdb) target remote localhost:5555 Remote debugging using localhost:5555 Reading symbols from ld.lib.so...done. Loaded symbols for ld.lib.so warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. _start () at /home/alex/Documents/Componolit_GmbH/Devel/src/genode-master/repos/base/src/lib/startup/spec/x86_64/crt0.s:43 43 leaq _GLOBAL_OFFSET_TABLE_(%rip), %r15 (gdb) The Genode log says: [init -> gdb_monitor] Warning: ptrace(PTRACE_GETREGSET (0x4204)) called - not implemented! [init -> gdb_monitor] Warning: read: no memory at address 0x1005d08 [init -> gdb_monitor] Warning: read: no memory at address 0x1005d08 [init -> gdb_monitor] Warning: read: no memory at address 0x1005d08 GDB does not seem to work correctly: (gdb) bt #0 _start () at /home/alex/Documents/Componolit_GmbH/Devel/src/genode-master/repos/base/src/lib/startup/spec/x86_64/crt0.s:43 Cannot access memory at address 0x0 [init -> gdb_monitor] Warning: read: no memory at address 0x0 Any ideas what's wrong here? Cheers, Alex -- Componolit GmbH · Königsbrücker Straße 124 · 01099 Dresden · Germany Amtsgericht Dresden · HRB 36670 · Sitz Dresden Geschäftsführer: Alexander Senier · USt-IdNr. (EU VATIN): DE312113634 http://componolit.com · @Componolit

2 2

loading core symbols for debugging purpose
by Parfait Tokponnon 08 Aug '18

08 Aug '18

Hello, My goal is to set breakpoint at some instruction address in the core process to trace its execution. To achieve this, I use this command in gdb. *add-symbol-file <filename> <load address>* But I cannot access the core load address. *objdump -h debug/core-nova.o *yields LMA for the .text section : 0x0000000000000000 And the ld-nova.lib.so does not help too. Can someone point me, in order to trace the core process execution, at which address to load the core symbols file? Thanks, -- Parfait T.

2 2

width of log window in sculpt 18.06
by Pirmin Duss 07 Aug '18

07 Aug '18

Hello Genodeans Today I switched from Sculpt 18.05 to 18.06. The automatic arrangement of the inspect window inside the free area of the Leitzentrale is very convenient. Only one thing doesn't work for me at the moment. In 18.05 it was possible to increase the width of the log window by changing the configuration for log_nit_fb in /config/leitzentrale. I used this a lot for better readability of the log. Best regards, Pirmin

2 1

ARM/sel4 compatibility
by Edward Sandberg 07 Aug '18

07 Aug '18

Hello, Can someone please provide an up-to-date ARM hardware compatibility list for Genode 18.05 and seL4: boards and drivers? Which boards are tested regularly? We have tried building run/demo for several ARM boards without a lot of luck: * Raspbery Pi Build fails with: Library-description file rpi_usb.mk is missing make[2]: *** No rule to make target 'rpi_usb.lib', needed by 'usb.lib'. Stop. I got past this by running: cp ./dde_linux/lib/mk/spec/foc/rpi_usb.mk ./dde_linux/lib/mk/spec/sel4/ but then I hit: Library-description file kernel-sel4.mk is missing Library-description file syscall-sel4.mk is missing make[2]: *** No rule to make target 'syscall-sel4.lib', needed by 'startup-sel4.lib'. Stop. * Wandboard Quad Build completes, but when loading UImage all we see is: ## Booting kernel from Legacy Image at 12000000 ... Image Name: Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 697455 Bytes = 681.1 KiB Load Address: 10001000 Entry Point: 10001000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK So it is unclear whether sel4 has started or not. * Arndale Build fails with: Library-description file syscall-sel4.mk is missing var/libdeps:21: *** Recursive variable 'DEP_A_kernel-sel4' references itself (eventually). Stop. For each of these we had the following repositories enabled: REPOSITORIES += $(GENODE_DIR)/repos/base REPOSITORIES += $(GENODE_DIR)/repos/os REPOSITORIES += $(GENODE_DIR)/repos/demo REPOSITORIES += $(GENODE_DIR)/repos/libports REPOSITORIES += $(GENODE_DIR)/repos/ports REPOSITORIES += $(GENODE_DIR)/repos/dde_linux Thanks! -- Edward Sandberg Adventium Labs 111 3rd Avenue S. Suite #100 Minneapolis, MN 55401 ed.sandberg(a)adventiumlabs.com

4 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users