users

users@lists.genode.org

1 participants
2322 discussions

Re: users Digest, Vol 30, Issue 4
by Simon Himmelbauer 06 Oct '20

06 Oct '20

Hi Norman, >> Anyways, regarding your timing problems, how exactly did you measure >> them? My current setup consists of taking a start and stop timestamp via >> a timer-connection but I only seem to get milliseconds-precision (I >> tried using elapsed_us() but it seems to always produce >> "microsecond"-values ending with three zeroes.). I currently run >> everything inside QEMU so I don't know whether real hardware will simply >> fix this. > apart from the lack of precision, the 'Timer::Session::elapsed_ms()' RPC > function induces unwelcome overhead, in particular the context switch > forth-and-back between your component and the timer driver and the timer > driver's interaction with the physical timer device. > > For capturing timing behavior at a higher precision and with much less > overhead, you may find the 'Trace::timestamp()' utility useful. The > function returns a platform-dependent timer tick value. On x86, this > would be the time-stamp counter (TCS), on ARM it returns a CPU counter > value. > > As the value returned by 'Trace::timestamp()' depends on the platform > (e.g., the CPU frequency), you will need to apply some kind of > calibration. To determine the calibration factor, you may use the > 'Timer::elapsed_ms' or 'Timer::elapsed_us' functions before running your > actual tests, e.g., by measuring the number of timer ticks passed within > one second. > > As a heads-up, please regard the 'Trace::timestamp()' with a healthy > dose of skepticism. In our experience, the values are not always > perfectly proportional to real-world time. In particular, > > - On the ARMv6-based Raspberry Pi, the counter value is increased only > if the CPU is not idle. > > - On some x86 platforms, the TCS values are not perfectly stable. > In particular, the TCS values taken with different CPU cores cannot > be assumed to correlate. > > You can find the implementations of the 'Trace::timestamp' function at > the base/include/spec/<arch>/trace/timestamp.h header, where <arch> is > the CPU architecture (like arm_64 or x86_64). > > Cheers > Norman > thanks for the input, I might have a look at this once I get to real-hardware testing. Cheers, Simon

1 0

No output with Genode::raw and Fiasco.OC
by Simon Himmelbauer 05 Oct '20

05 Oct '20

Hi Genodians, I'm currently writing a time sensitive-program using Fiasco.OC as a kernel. For debugging purposes I wanted to use Genode::raw in order to avoid the overhead of Genode::log. However, my calls to raw() don't seem to print anything on the console. Is there something I need to enable/configure first? Thanks in advance! Cheers, Simon

4 6

Re: No output with Genode::raw and Fiasco.OC
by Simon Himmelbauer 02 Oct '20

02 Oct '20

Hi Christian, > For Genode::raw() to work on Fiasco.OC, the component needs the debug > capability to access the kernel debugger for output. This may be a > robustness/security risk in production systems and is, therefore, not > enabled by default. The access can be enabled by adapting the code > [1] and after recompilation all components can access the Fiasco > kernel debugger. Your solution worked, thanks for the help! Cheers, Simon Himmelbauer

1 0

Out of tree hardware platforms
by Duss Pirmin 02 Oct '20

02 Oct '20

Hi Genodians I'm enabling base-hw on the IoT gateway of CompuLab [1]. I do this in a separate repository in the same way as arndale, panda etc are done in genode-world. This works well apart from some minor modifications on the imx8q_evk (for which I will create an issue as soon everything is finalized and cleaned up). The only thing I'm struggling with is that /tool/run/boot_dir/hw isn't used. This leads to the error unknown platform no linker address known If I add the platform to genode/tool/run/boot_dir/hw building works. But as with the other out of tree platforms I'd like to keep the platform out of the Genode repository, for cleanness. The repository is linked to genode/repos/... and added to REPOSITORIES in build/arm_v8a/etc/build.conf. [1] https://www.compulab.com/products/iot-gateways/iot-gate-imx8-industrial-arm… Best regards, Pirmin

3 2

The Falkon browser / Chromium engine running natively on Genode is absolutely beautiful
by baconicsynergy＠protonmail.ch 29 Sep '20

29 Sep '20

I can't access my Gmail or Protonmail yet (it says the engine isn't up to date), but I don't care - this is a huge step forward for Genode's web capabilities! I can't tell you how excited this makes me. Considering that Firefox usage is much lower lately (unfortunately :/) investing in a Chromium based web browser is wise. It's also going to be very nice not needing to spin up a virtual machine to use a feature-filled web browser Looking forward to future updates!

1 0

Announcement: Sculpt OS 20.08 released
by Norman Feske 17 Sep '20

17 Sep '20

Hello everyone, I'm pleased to announce the release of Sculpt OS 20.08, along with a ready-to-use system image and OVA appliance: https://genode.org/download/sculpt Please refer to the updated documentation when using this version: https://genode.org/documentation/articles/sculpt-20-08 https://genode.org/documentation/sculpt-20-08.pdf (PDF) You can find a short summary of the changes in the following article: https://genodians.org/nfeske/2020-09-17-sculpt-os Have fun sculpting! 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

fs_rom "follows" files
by Roman Iten 10 Sep '20

10 Sep '20

Hello Genodians I use `run/bash` and added a simple component that logs the content of a ROM module: ```xml <start name="test-update"> <resource name="RAM" quantum="2M"/> <route> <service name="ROM" label="test.config"> <child name="vfs_rom" label="tmp/test.config"/> </service> <any-service> <parent/> <any-child/> </any-service> </route> </start> ``` Then, I execute the following commands on the interactive shell: ```bash > echo "1st-cfg" > /tmp/test.config` # "1st-cfg" is logged > mv /tmp/test.config /tmp/test.backup` # nothing is logged > echo "2nd-cfg" > /tmp/test.config` # nothing is logged > echo "3rd-cfg" > /tmp/test.backup` # "3rd-cfg" is logged ``` Is it the intended behavior that `fs_rom` "follows" the file or should it always provide the ROM content of the file with the specified name instead? The background of this question is that in fact, `test-update` for example could be a component that consumes the `test.config` and is supposed to react on configuration updates. Cheers, Roman

2 2

Attached_mmio with platform_drv
by Pirmin Duss 03 Sep '20

03 Sep '20

Hello Genodians I'm currenty working on a I2C driver for the iMX8 processor. I actually started this before the 20.08 release. But when I read that the new platform driver for the iMX8 SoC can automatically enable/disable clocks for subsystems, I decided to use this new feature, as I had problems enabling the clocks before. If my assumptions are correct (by reading the code of the usb_host_drv), one is able to get a capability to the IOMEM that the platform driver has mapped via `acquire_device().io_mem_dataspace()`. What is currently not clear to me, is how to map the `Attached_mmio` of the driver use the mapped IOMEM, to be able to use the register definitions? Or does a driver that uses the `platform_drv` component require an other way to access the registers? My current work in progress code (with lots debug stuff in it) can be found at [1]. Best regards, Pirmin [1] https://github.com/trimpim/genode/tree/i2c_dirver_imx8q_evk_20.08

3 6

Announcement: Genode OS Framework version 20.08 released
by Norman Feske 28 Aug '20

28 Aug '20

I'm happy to announce today's release of Genode 20.08. The two most prominent topics of the new version are our port of the Chromium web engine and the redesign of the low-level GUI stack. With the Chromium engine, we expose Genode to an extremely heavy-weight workload, which stresses the framework like never before on many levels, from the quality of our POSIX runtime, the ability to bridge 3rd-party build systems with Genode, to the performance and robustness of our native protocol stacks (TCP/IP, graphics, file-system access). So the collateral improvements while porting this behemoth of software are valuable for the users of the framework at large. The rework of the framework's low-level GUI stack is the result of a design and planning phase of over two years. With the architectural change conducted during this release cycle, we clear the path for the ability to swap-out graphics and input drivers on the fly without reboot, and to realize features like screen capturing and remote desktop scenarios in a privacy-protecting way. Besides these highlights, the release comes with plentiful improvements ranging from hardware-support (i.MX8), over the modularisation of CBE block encryptor, to CPU-affinity management for Sculpt OS. A quick summary of the most visible topics: - Redesigned low-level GUI stack - Removal of drivers from the trusted computing base - Consistent use of 32 bits per pixel - Improved Qt5 integration and work flows - Chromium engine and Falkon web browser - Pluggable crypto and trust anchor for the CBE block encrypter - Device drivers and platforms - ARM Trusted Firmware access - Power and clock management for i.MX 8M Quad SoC - New block server backed by VFS content - New port of SDL2 library - Interactive CPU-affinity management for Sculpt OS You can find all the details in the release documentation at https://genode.org/documentation/release-notes/20.08 Enjoy! 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 1

Unable to read from socket
by Daly, Connor G. 24 Aug '20

24 Aug '20

Hi all, Quick thanks to Alex for helping me get started a couple weeks ago. I'm trying to port/rewrite a C++ program I wrote to Genode and am running into a networking issue. The program is a server and accepts TCP connections from clients that do not wait for a response. I'm sending my data via a python 3.7 script that works with the Linux native version of the application and is essentially: import socket sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM) sock.connect(('127.0.0.1', 5555)) sock.sendall(b"test\r\n") sock.close() Basically, I've been unable to read from my listen sockets. I'm able to bind, listen for connections, accept an incoming connection, and call socket read(), but then it just hangs. I saw something in the 18.08 release notes that made me think LwIP might only support asynchronous mode, so I tried nonblocking sockets. Those no longer hang, but they also don't read any data. Next, I tried using tcp_terminal and modifying the tcp_terminal_echo program to fit my needs. This program also can't read any of the data I send it. It accepts the incoming connection, but never logs that any bytes are read. However, TCP terminal does accept telnet connections like in the example program. I then discovered that my synchronous socket reading would actually work for a telnet connection as well. Any idea what is going on here? For reference, my run script is essentially the same as tcp_terminal.run. Failing that, does anyone know what I would need to do to modify tcp_terminal/tcp_terminal_echo to make it accept regular tcp socket connections and not just telnet? Thanks so much! -Connor

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users