users August 2017

users@lists.genode.org

20 participants
30 discussions

ffat_fs server build in 17.08?
by Bob Stewart 30 Aug '17

30 Aug '17

Hi, I migrated to 17.08 from 17.05 this morning. One system I routinely build on prior releases fails with the 'server/ffat_fs' does not exist error. The prepare_tool was run to get the source, as usual. I've either forgotten a step or the current build is broken for users of the old ffat_fs server. The complete make output is: make run/rico_no_usb KERNEL=hw | tee build.log including /Work/Genode/genode-17.08/tool/run/boot_dir/hw including /Work/Genode/genode-17.08/tool/run/image/uboot including /Work/Genode/genode-17.08/repos/os/run/rico_no_usb.run building targets: core init server/pin_mux_ctl server/shared_mem drivers/platform/spec/437x drivers/platform/spec/437x/client drivers/timer drivers/gpio/spec/437x drivers/pwm drivers/i2c drivers/uart drivers/sd_card drivers/pruss app/soc_leds server/ffat_fs app/motor_control app/ap_cli app/ap_sensors app/autopilot spawn make core init server/pin_mux_ctl server/shared_mem drivers/platform/spec/437x drivers/platform/spec/437x/client drivers/timer drivers/gpio/spec/437x drivers/pwm drivers/i2c drivers/uart drivers/sd_card drivers/pruss app/soc_leds server/ffat_fs app/motor_control app/ap_cli app/ap_sensors app/autopilot make[1]: Entering directory '/Work/Genode/genode-17.08/build/437x' Error: target 'server/ffat_fs' does not exist Makefile:211: recipe for target 'error_missing_targets' failed make[1]: *** [error_missing_targets] Error 1 make[1]: Leaving directory '/Work/Genode/genode-17.08/build/437x' Error: Genode build failed make: *** [run/rico_no_usb] Error 252 Makefile:309: recipe for target 'run/rico_no_usb' failed. Thanks, Bob Stewart

1 0

Genode OS Framework version 17.08 released
by Norman Feske 30 Aug '17

30 Aug '17

I am happy to announce the version 17.08 of the Genode OS Framework. After the huge infrastructural changes of the previous two releases, we took the current release cycle as an opportunity to let things settle down and concentrate on Genode Labs' internal continuous-integration infrastructure. This resulted in countless gradual refinements such as improved timing accuracy or the increased POSIX compliance of our libc. That said, the highlight of the new version is something completely different: The result of our thorough investigation of hardware-accelerated graphics on modern Intel platforms over the course of the past year. With our new GPU multiplexer developed from scratch, Genode becomes able to leverage GPU resources at only a marginal increase of the system's trusted computing base. Another compelling feature of the new version is the upgraded seL4 support that covers ARM and 64-bit x86. A summary of changes: - Hardware-accelerated graphics for Intel Gen-8 GPUs - The seL4 6.0 kernel on ARM and 64-bit x86 hardware - Genode as Xen DomU - Preliminary UEFI support for NOVA, base-hw, and seL4 - New server for capturing reports to files - New runtime for the sequential execution of components - Support for boot-time initialized frame buffer - FatFS-based VFS plugin - Extended non-blocking operation of the VFS - Refined time handling - Updated Muen separation kernel The long version in the form of the official release documentation: http://genode.org/documentation/release-notes/17.08 Have fun with exploring the new version! Norman -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Qt Virtualkeyboard example
by Johannes Kliemann 28 Aug '17

28 Aug '17

Hi, I tried to build the Qt Virtualkeyboard example. I adapted the target.mk of the calculatorform example to point to the correct project file. Make fails at the project file at line 6 with missing separator. This part contains the following: static { QT += svg QTPLUGIN += qtvirtualkeyboardplugin } Is there an additional flag required? Manually running qmake && make works fine. Regards, JK

5 15

ld.lib.so missing
by Stephan Lex 25 Aug '17

25 Aug '17

2 1

Re: create_uboot dependencies?
by Martin Stein 25 Aug '17

25 Aug '17

We have a Serial-to-USB cable connected to the Serial interface of the board and a USB port of the testing machine. Then you can catch the output via 'picocom' for instance. The implementation of the UART driver is [1]. It uses 1 stop bit, a baudrate of 115200, and no parity. So, the following works for me: sudo picocom -p n -b 115200 /dev/ttyUSB0 Even if your Genode doesn't come up you should at least see some output from the Uboot like this: U-Boot 2015.10-00237-g92e40f5-dirty (Dec 04 2015 - 15:37:04 +0100) CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: Wandboard rev B1 I2C: ready DRAM: 2 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 No panel detected: default to HDMI Display: HDMI (1024x768) In: serial Out: serial Err: serial Net: FEC [PRIME] Hit any key to stop autoboot: 1 U-Boot SPL 2015.10-00237-g92e40f5-dirty (Dec 04 2015 - 15:37:04) Did this help? [1] base/include/drivers/uart/imx.h Am 18.08.2017 um 18:03 schrieb Steven Harp: > Martin: > > Yes, that worked well. Happily I had the older toolchain handy, > and it compiles uboot without error. > > Unfortunately, the output is not yet working for me (no serial out). > I'm still trying to puzzle out the recipe to get Genode images running > on the Wand Quad. Genode Labs perhaps has a preferred solution for > testing on this platform--is there a web page or README that discusses? > Maybe tftpboot from one of the Wand linux/uboot images could work? > > Any advice or examples would be much appreciated. > > Thanks, > Steve > > > On 08/18/2017 07:10 AM, Martin Stein wrote: >> Hi Steven Harp, >> >> Thank you for this hint! >> It's obviously a bug in the 'create_uboot' tool. The tool uses the Genode tool >> chain and since the last update of this tool cain I didn't test whether they're >> still fine with each other. >> >> One quick work-around for you would be to download the 16.05 toolchain [1], >> unpack it to an individual directory (no 'P' flag) [2], and adapt your >> create_uboot to use the other tool chain [3]. >> >> I will have a more detailed look at the problem these days and provide a >> long-term fix as soon as possible. >> >> I hope this helped? >> >> Cheers, >> Martin

2 2

An ISO Image Related Remark
by Martin Vahi 22 Aug '17

22 Aug '17

Dear whoever reads this, The only purpose of my current letter is to note that the GenodeOS gets beaten by the MINIX3 at getting newcomers on-board due to the fact that the MINIX3 has an ISO image that people can install to VirtualBox and the GenodeOS lacks such downloadable image. Actually, I once obtained one such GenodeOS image in 2010, but today is 2017. I haven't exhaustively tested the GenodeOS book, but at first glance it seems that the book assumes, at least from paths' point of view, a person is required to run a copy of the GenodeOS before building the GenodeOS. For example, after cloning the https://github.com/genodelabs/genode and following instructions on page 24 of the 2017_08_22 version of the (Chapter 2.3, "Using the build system") http://genode.org/documentation/genode-foundations-17-05.pdf namely ./tool/create_builddir x86_64 cd ./build/x86_64 nice -n20 make I get an error message ---citation---start---- /bin/bash: /usr/local/genode-gcc/bin/genode-x86-g++: No such file or directory ---citation---end------ Obviously I AM NOT running GenodeOS, if I'm a newcomer and want to try out the GenodeOS for the very first time. As I wasn't given an ISO image to to try the GenodeOS, then my next step is to follow the official instructions, which in this case is to build the GenodeOS myself. Yet, the build system assumes that I'm building the GenodeOS WHILE RUNNING GENODEOS, because hardly any Linux or BSD distribution has a path like /usr/local/genode-gcc available by default. A chicken and an egg. There's a need for a grown up bird to lay the egg, but if the whole path of software-/bio-evolution is to be skipped, then a lamb must be able to give birth to a non-mammal, a lizard, a bird, a fish, to make fast bootstrapping possible, not to mention "The Alien Option": https://youtu.be/zCqoA-FGgoc?t=20s Thank You for reading my comment :-)

2 1

Fwd: Re: create_uboot dependencies?
by Martin Stein 18 Aug '17

18 Aug '17

Hi Steven, Thank you for this hint! It's obviously a bug in the 'create_uboot' tool. The tool uses the Genode tool chain and since the last update of this tool cain I didn't test whether they're still fine with each other. One quick work-around for you would be to download the 16.05 toolchain [1], unpack it to an individual directory (no 'P' flag) [2], and adapt your create_uboot to use the other tool chain [3]. I will have a more detailed look at the problem these days and provide a long-term fix as soon as possible. I hope this helped? Cheers, Martin [1] https://sourceforge.net/projects/genode/files/genode-toolchain/16.05/ [2] tar xfj genode-toolchain-<version>-<arch>.tar.bz2 [3] diff --git a/tool/create_uboot b/tool/create_uboot index f52d8e0..0e6490c 100755 --- a/tool/create_uboot +++ b/tool/create_uboot @@ -59,7 +59,7 @@ endif UBOOT_MAKE := \ $(VERBOSE)make ARCH=$(ARCH) \ - CROSS_COMPILE=/usr/local/genode-gcc/bin/genode-$(ARCH)- \ + CROSS_COMPILE=<YOUR_GENODE_GCC_16_05_DIR>/bin/genode-$(ARCH)- \ O=$(UBOOT_BUILD_DIR) \ -j4 Am 16.08.2017 um 19:53 schrieb Steven Harp: > > In genode 17.05, I'm having difficulties with tool "create_uboot". > Perhaps there are some preparatory steps or usage guidelines > that I am missing.... The error manifests as (below). > Any suggestions about what might be amiss? (Goal is preparing an > image for wand quad.) > > > $ ~/genode/tool/create_uboot wand_quad > Already on 'genode_wand_quad' > Your branch is up-to-date with 'origin/genode_wand_quad'. > Building U-Boot config... > make[1]: Entering directory '/home/user/genode/contrib/uboot' > make[2]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' > GEN ./Makefile > # > # configuration written to .config > # > make[2]: Leaving directory '/home/user/genode/contrib/uboot/build/wand_quad' > make[1]: Leaving directory '/home/user/genode/contrib/uboot' > Building U-Boot images... > make[1]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' > GEN ./Makefile > scripts/kconfig/conf --silentoldconfig Kconfig > CHK include/config.h > GEN include/autoconf.mk > GEN include/autoconf.mk.dep > GEN spl/include/autoconf.mk > In file included from /home/user/genode/contrib/uboot/include/linux/compiler.h:54:0, > from /home/user/genode/contrib/uboot/include/linux/byteorder/little_endian.h:12, > from /home/user/genode/contrib/uboot/arch/arm/include/asm/byteorder.h:29, > from /home/user/genode/contrib/uboot/include/compiler.h:125, > from /home/user/genode/contrib/uboot/include/image.h:19, > from /home/user/genode/contrib/uboot/include/common.h:82: > /home/user/genode/contrib/uboot/include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc6.h: No such file or directory > #include gcc_header(__GNUC__) > ^ > compilation terminated. > > ... Repeats ...

1 0

create_uboot dependencies?
by Steven Harp 16 Aug '17

16 Aug '17

In genode 17.05, I'm having difficulties with tool "create_uboot". Perhaps there are some preparatory steps or usage guidelines that I am missing.... The error manifests as (below). Any suggestions about what might be amiss? (Goal is preparing an image for wand quad.) $ ~/genode/tool/create_uboot wand_quad Already on 'genode_wand_quad' Your branch is up-to-date with 'origin/genode_wand_quad'. Building U-Boot config... make[1]: Entering directory '/home/user/genode/contrib/uboot' make[2]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' GEN ./Makefile # # configuration written to .config # make[2]: Leaving directory '/home/user/genode/contrib/uboot/build/wand_quad' make[1]: Leaving directory '/home/user/genode/contrib/uboot' Building U-Boot images... make[1]: Entering directory '/home/user/genode/contrib/uboot/build/wand_quad' GEN ./Makefile scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config.h GEN include/autoconf.mk GEN include/autoconf.mk.dep GEN spl/include/autoconf.mk In file included from /home/user/genode/contrib/uboot/include/linux/compiler.h:54:0, from /home/user/genode/contrib/uboot/include/linux/byteorder/little_endian.h:12, from /home/user/genode/contrib/uboot/arch/arm/include/asm/byteorder.h:29, from /home/user/genode/contrib/uboot/include/compiler.h:125, from /home/user/genode/contrib/uboot/include/image.h:19, from /home/user/genode/contrib/uboot/include/common.h:82: /home/user/genode/contrib/uboot/include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc6.h: No such file or directory #include gcc_header(__GNUC__) ^ compilation terminated. ... Repeats ...

1 0

ACPI _PS0 failing with UNINITIALIZED_ARG
by Johannes Kliemann 16 Aug '17

16 Aug '17

Hi again, first, I have posted this question already on Stackoverflow [1] and Reddit [2] but forgot to put it on the mailing list. > I have a touchscreen controller (which is an I2C slave) that I need to enable via APCI. This should be done by calling the _PS0 ACPI method. I call this method by using AcpiEvaluateObject with no arguments and no return values. > > When calling this method on the parent object (I2C4), everything goes fine but calling it on the touch screen controller (TCS2), it fails. What also makes me wonder is that it returns AE_AML_UNINITIALIZED_ARG even though it doesn't take any args (according to the DSDT). > > Calling the _CRS method on the same object also works without any problems. I also looked into the Linux kernel source how they change ACPI power states and they use the exact same mechanism. It boils down to the use of acpi_evaluate_object in acpi_dev_pm_explicit_set which also seems to work on the touchscreen device. > > what am I missing to successfully enable the touchscreen device via ACPI? Is there something the Linux kernel is initializing implicitly (I couldn't find something like this)? The current workaround for this issue is to use the GPIO pins to enable the controller. But this isn't the desired way since it requires an additional GPIO driver that takes ~100 LOC and also a separate ACPI initialization for this driver. Besides that other functions that are needed to get initial parameters return errors. On the specific device I have the following examples: > \_SB_.I2C4.SSCN > \_SB_.I2C4.FMCN > \_SB_.I2C4.FPCN > \_SB_.I2C4.HSCN Similar things also happen on the GPIO device (\_SB_.GPO1). Regards, Johannes [1]: https://stackoverflow.com/questions/44382881/acpi-ps0-failing-with-uninitia… [2]: https://www.reddit.com/r/osdev/comments/6mtlv7/acpi_psx_function_returns_ae… DSDT: https://gist.github.com/jklmnn/15ed561202e04390e7bc366c0f803577#file-dsdt-d…

2 3

Receiving message written by writev() in multiple chunks
by Alexander Senier 16 Aug '17

16 Aug '17

Hi all, when using writev() on a TCP socket, I get a behavior that is unexpected, although it may OK by the specification. My test program is using the libc_lwip_loopback plugin. I create a TCP socket, bind it so some address/port and put it into listening mode. Then, I create another socket, connect to that port and write and IOVEC referencing 3 buffers using writev(). The buffers have a total length of 17 which is returned as a length by the writev(). When reading from the socket using recv(), I'd expect it to return 17 bytes with are identical with the content of the IOVEC. Instead, I need to perform two recv() calls, the first returning the first buffer of the IOVEC and the second returning the buffers 2 and 3 of the IOVEC concatenated. Find example code here [1]. As I said, this may be perfectly legal behavior. OTOH, Linux and Android behave as expected and there may be code relying on it. Any thoughts on this issue? Thanks! Cheers, Alex [1] https://github.com/senier/componolit/blob/issue16/src/test/mfe/writev_socke…

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users August 2017