users

users@lists.genode.org

7 participants
2332 discussions

Affinity Subspace Mapping
by Lex, Stephan 06 Sep '17

06 Sep '17

I am working with affinities in order to start and bind various components on different cores. I am using QEMU as emulation platform to start the system with four cores. My situation looks as follows: I have one parent component which creates two more children. Each of these including the init component should be assigned to a different core. The idea was to start init with an affinity configuration 4x1 in the run script: => <affinity-space width="4" height="1"/> The custom parent component should be configured to get a affinity subspace of 3x1 beginning from the second core like: => <affinity xpos="1" ypos="0" width="3" height="1"/> The next idea was to create two affinities with a subspace of 1x1 for the two children and start them within the parent component. The two children should be working on the third and fourth core respectively, so my intention was to declare them as xpos 1 and 2 relative to the parents subspace of 3x1: => const Genode::Affinity &aff_count{Genode::Affinity::Space(1), Genode::Affinity::Location(1, 0)}; => const Genode::Affinity &aff_val{Genode::Affinity::Space(1), Genode::Affinity::Location(2, 0)}; To check this attempt i inserted a log call in the constructor of core's Cpu_session_component: => log("CORE ",__func__,": Affinity location: xpos: ",_location.xpos()," ypos: ",_location.ypos()," width: ",_location.width()," height: ",_location.height()); The log outputs seem relatively coherent with what was originally planned: => init cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 0 ypos: 0 width: 4 height: 1" => parent cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 1 ypos: 0 width: 3 height: 1" => child_1 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 2 ypos: 0 width: 3 height: 1" => child_2 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 3 ypos: 0 width: 3 height: 1" Unfortunately right after the second child gets started, the program loops and does not terminate. If i change the affinity for the children to => const Genode::Affinity &aff_count{Genode::Affinity::Space(1), Genode::Affinity::Location(0, 0)}; => const Genode::Affinity &aff_val{Genode::Affinity::Space(1), Genode::Affinity::Location(1, 0)}; the log outputs also change to => child_1 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 1 ypos: 0 width: 3 height: 1" => child_2 cpu_session: "CORE Cpu_session_component: Affinity location: xpos: 2 ypos: 0 width: 3 height: 1" and the program continues its work as intended. If you could tell me my thinking errors, if there are any, or how to achieve that each component gets assigned to their respective cores, i would appreciate it a lot. -- Thank you, Stephan Lex

3 5

Genode on Odroid XU4
by Hornemann Steve 04 Sep '17

04 Sep '17

Hey Guys, I'm really happy opening my first discussion. :D I take part on a research by using Genode on Odroid_xu4. Had some problems creating images but I got one for XU3, created as "uimage" put on SD-Card. Now I have several information: https://github.com/genodelabs/genode/issues/991, not understand,yet. https://sourceforge.net/p/genode/mailman/message/31693682/, think the next steps. And https://en.wikipedia.org/wiki/ODROID in which Genode is declared as "NO" in working as OS with XU4. In Wikipedia-Talk I questioned it. I hope, somebody can give a clear answer for that. Also I believe, Yevgeny made good work, but more I want to know, why he interrupted the project. Well, after connecting this is my first Issue :D, This is the first statement from XU4 via "gtkterm" connected UART: U-Boot 2012.07-00036-g4d29c46-dirty (Dec 04 2015 - 15:52:26) for Exynos5422 CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7] APLL = 800MHz, KPLL = 800MHz MPLL = 532MHz, BPLL = 825MHz Board: HardKernel ODROID DRAM: 2 GiB WARNING: Caches not enabled TrustZone Enabled BSP BL1 version: ï¿½/ï¿½ï¿½ VDD_KFC: 0x44 LDO19: 0xf2 Checking Boot Mode ... SDMMC MMC: S5P_MSHC2: 0, S5P_MSHC0: 1 MMC Device 0: 14.8 GiB MMC Device 1: 29.1 GiB MMC Device 2: MMC Device 2 not found there are pending interrupts 0x00000001 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Press quickly 'Enter' twice to stop autoboot: 0 Unable to use mmc 0:1 for fatload Unknown command 'ext4load' - try 'help' Unknown command 'ext4load' - try 'help' Load Boot Script from mmc 0:1 <<< Unable to use mmc 0:1 for fatload Load Boot Script from mmc 0:2 <<< Unable to use mmc 0:2 for fatload Run Default Bootcmd <<< reading kernel..device 0 Start 1263, Count 16384 MMC read: dev # 0, block # 1263, count 16384 ... 16384 blocks read: OK completed reading RFS..device 0 Start 17647, Count 2048 MMC read: dev # 0, block # 17647, count 2048 ... 2048 blocks read: OK completed Bad Linux ARM zImage magic! Sorry for missing information for better understanding the Issue. May I can complete them next time. Thanks for any help! Steve

1 0

need help to understand piece of the doc
by Naiji Ma 01 Sep '17

01 Sep '17

Hi everybody, I would like to quote part of the official doc from [1]: *As illustrated in the figure, from an organizational point of view, a virtual machine is implemented as a leaf node in Genode's process tree. Genode not only facilitates the use of virtual machines for application compatibility but also the re-use of existing device drivers. The baby Tux in the figure symbolizes an original Linux device driver being executed in a device-driver environment.* [1] http://genode.org/documentation/general-overview/index How to understand the 're-use' ? Does it mean that an original(unmodified) Linux device driver could be placed into a 'device-driver environment' and also function correctly in Genode, or does it mean an original Linux device driver could be taken out from the Linux virtual machine (the big Tux) and executed as a leaf node in Genode, consequently serve Genode as well as the big Tux at the same time? Regards, Naiji

2 1

Qt5 Threads
by Johannes Kliemann 01 Sep '17

01 Sep '17

Hi, is anyone using threads in Qt5 applications on Genode? Is it possible to use QThreads or are Genodes own threads required? If so, how would I get an instance of Genode::Env in a Qt application (which I would need for the thread). Regards, Johannes

2 2

Re: ffat_fs server build in 17.08?
by Nobody III 31 Aug '17

31 Aug '17

The release notes say that ffat_fs is deprecated in favor of a vfs plugin. I'd recommend reading the release notes to see how to adapt your scenario. On Aug 30, 2017 11:58 AM, "Bob Stewart" <robjsstewart@...9...> wrote: 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 ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ genode-main mailing list genode-main(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main

3 3

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 24 Aug '17

24 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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users