users

users@lists.genode.org

2325 discussions

booting the SABRE tablet from SD card
by Rijurekha Sen 13 Sep '16

13 Sep '16

Hi, I compiled the demo according to https://github.com/skalk/genode/blob/i.MX53_tablet_demo/os/src/server/vmm/i…. Next to run the demo in the SABRE tablet, I followed the instruction in http://genode-main.narkive.com/qJXUD6w5/arm-trustzone-demo-in-i-mx53-sabre-…. Created the u-boot.imx using https://eewiki.net/display/linuxonarm/i.MX53+Quick+Start#i.MX53QuickStart-B… for the step 2) 2) sudo dd if=$(U-BOOT-DIR)/u-boot.imx of=/dev/sdb seek=2 bs=512 conv=fsync But when I put in the MMC card in the tablet with the SD card in it and restart the tablet, it just powers on to the default Android which it came with. How to get the u-boot prompt, as mentioned in step 4)? 4) After power up the tablet, U-BOOT prompt (u-boot from MMC is not used), I did as follows: MX53-SMD U-Boot > ext2load mmc 0:1 0x70800000 image.bin How to get this u-boot prompt? https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0ahUKEwi… has a chapter 3 on various boot options. http://cache.freescale.com/files/32bit/doc/user_guide/IMX53SMDHUG.pdf shows the location of the switches sw26 and sw28 at the back of the board. Does that mean, I should open the back cover of the tablet to change these? Is this what http://genode-main.narkive.com/qJXUD6w5/arm-trustzone-demo-in-i-mx53-sabre-… did? Want to verify the correct thing to do as the tablet is expensive. Thanks! Riju

3 8

VirtualBox on Genode
by Yevgeny Lavrov 10 Sep '16

10 Sep '16

Hello I'm currently trying to reproduce VertualBox with Tinycore Linux running on top of NOVA hypervisor scenario on x86-64 hardware. The steps I've taken so far are: 1) ./tool/ports/prepare_ports for nova and virtualbox 2) ./tool/create_builddir nova_x86_64 3) uncommented REPOSITORIES += $(GENODE_DIR)/repos/libports line in <Genode-dir>/build/nova_x86_64/etc/build.conf 4) Downloaded Tinycore Linux .iso image Questions: 1) Where should I put Tinycore Linux .iso file? It says save it as bin/test.iso in the similar thread "running VirtualBox on Genode" on Genode mailing lists. Is it <Genode-dir>/build/nova_x86_64/bin directory that gets created after executing make run/demo? 2) Where should I add "<config><image type="iso" file="/iso/test.iso"/></config>" ? 3) Where to execute make run/virtualbox? I assume it's my build directory. However, executing it in my build directory results in Error: no run script for virtualbox. Please advise Thank you

3 7

Basic ISO Boot to Command Prompt
by Chris Rothrock 09 Sep '16

09 Sep '16

I am trying to build the most basic Genode build that creates a bootable ISO image that, once booted, brings me to a command prompt and outputs to a screen, not to a serial connection. I'm fairly familiar with the build process and I have made numerous demo builds work from within qemu but I am trying to make a stand-alone bootable image. So far I am only getting the boot loader message where the kernel loads (in this round I am simply using the Nova hypervisor but any kernel is fine for my demo boot). What am I missing to make this happen? Chris -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

2 4

Partitioned Scheduling
by Edinger, Stefan 05 Sep '16

05 Sep '16

Hi, we are using Genode on Fiasco.OC and want to use different Scheduler for different CPU-Cores. Is there a way to assign a Scheduler to a CPU-Core in Genode? Thank you Stefan Edinger

3 2

Segfault when calling (Cancelable)Lock.unlock?
by Menno Valkema 31 Aug '16

31 Aug '16

Hi Everyone, I'm currently using a Nic_connection to exchange data data between components on linux_x86. Before sending data from the Nic server I first check whether any data can be freed. Even before the first packet is send out, using the code below: while ( _rx.source()->ack_avail() ) { _rx.source()->release_packet( _rx.source()->get_acked_packet() ); } Whenever I'm sending data out from an extern "C" method (callback passed to a c library), the application crashes. Looking with GDB, the issues seems to be with the destructor of the lock guard from the code from packet_stream.h (full GDB output at the bottom of this email). bool ready_for_rx() { Genode::Lock::Guard lock_guard(_rx_queue_lock); return !_rx_queue->empty(); } The destructor of the Guard simply calls the unlock method for the lock. However this crashes. Could it be that the unlock method throws an exception in the destructor, or that there might be uninitialized variables within the lock itself? I'm sort of lost here, because I've used the Nic_connection in similar settings in the past (also called from an extern "C" context as a c code callback). However this time it consistently breaks, whenever I try to sent out the first packet from an extern "c" context (it does work when sending the packet out from normal c++ code. Any suggestions what might causes the crash in my application? Cheers, Menno Program received signal SIGSEGV, Segmentation fault. 0x0000000001143c22 in ~Lock_guard (this=<optimized out>, __in_chrg=<optimized out>) at <project-path...>/repos/base/include/base/lock_guard.h:42 42 ~Lock_guard() { _lock.unlock(); } (gdb) bt #0 0x0000000001143c22 in ~Lock_guard (this=<optimized out>, __in_chrg=<optimized out>) at <project-path...>/repos/base/include/base/lock_guard.h:42 #1 ready_for_rx (this=<optimized out>) at <project-path...>/repos/os/include/os/packet_stream.h:400 #2 ack_avail (this=<optimized out>) at <project-path...>/repos/os/include/os/packet_stream.h:686 ....

2 3

Announcement: Genode OS Framework version 16.08 released
by Christian Helmuth 31 Aug '16

31 Aug '16

This release is packed with lots of improvements in areas ranging from extended base-platform support over networking and virtualization to new tools for statistical profiling. We quite proudly announce extended support for the seL4 kernel as a platform for dynamic and interactive Genode scenarios on x86. The new version enables users of seL4 to compose dynamic operating systems from a plethora of ready-to-use Genode components. Further, the developers from Codelabs contribute their efforts in running unmodified guest operating systems on top their Muen separation kernel with a port of VirtualBox 4. As we consider VirtualBox as key feature of Genode, this release also includes a first experimental version of VirtualBox 5 on top of the NOVA kernel. Another highlight of the new version is a virtual networking component for routing and NAT accompanied by the ability to use the TOR network. The current release contains the following changes and new features. - Base platforms - Interactive and dynamic workloads on top of the seL4 kernel - Binary compatibility across all supported kernels - Xilinx Zynq board support for Parallela, Zedboard, ZC706, ZC702 - Networking - Virtual networking (routing, NAT) - New TOR component - ROM sessions in a network-distributed Genode system - Virtualization - VirtualBox 4 on top of the Muen separation kernel - Experimental version of VirtualBox 5 for NOVA - Libraries and components - Improved ACPI integration - Growing library of "shim" services such as a framebuffer scaler, an input remapper, a ROM fallback service, and a LOG duplicator - Ported 3rd-party software such as diffutils, less, mbed TLS, libxml2, RISC-V front-end server - New file-downloading component - Statistical profiling Find the complete release documentation for the version 16.08 at https://genode.org/documentation/release-notes/16.08 Happy hacking with Genode! -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Stack overflow protection/detection
by Johannes Schlatow 31 Aug '16

31 Aug '16

Hi all, I guess you are familiar with the problem of stack overflows in multi-threaded components. I already encountered a bunch of weird errors that were hard to track down until I remembered that it could simply be caused by a too small stack. I know that Genode's policy is to use single-threaded components. Occasionally, however, one needs additional threads, especially when using 3rd party libraries. Stack overflows are not only very annoying and time consuming but can (imo) also be mitigated rather easily. I therefore think it would be worth implementing a protection or detection mechanism for this in Genode. The "problem" here is actually the `Stack_allocator` which places the stacks of the component threads consecutively in memory. I.e. if one thread exceeds its allocated stack area, it likely corrupts the stack of another thread (of the same component). Hence, one could improve the `Stack_allocator` so that it keeps a guard page between the stacks in order to cause a page fault on any stack overflow. This comes at the cost of a slightly increased complexity and possibly also an increased memory consumption (because it requires a second-level translation table). Alternatively, I can imagine a kernel-level (base-hw) approach which uses canaries at the top of each stack. Every time the kernel switches to a user thread, it checks whether the canary is still alive. If not, another thread's stack must have overflowed. Of course, this method is only reliable if we can assume that every memory word on the stack will be initialised (preferably sequentially). Note that I'm not eager to implement these techniques in the near future. Nevertheless, I thought it would be great to start a discussion and collect comments and additional ideas. Looking forward to your feedback! Cheers Johannes

3 4

Genode 16.05 Fault handler
by Denis Huber 30 Aug '16

30 Aug '16

Dear Genode community, in Genode 16.05 the old usage of Signal_receivers and Signal_contexts is considered deprecated. Instead Signal_handler and Signal_transmitter shall be used. I am trying to use a Signal_handler as a fault handler for env's address space. I wrote a short test to illustrate the problem [1]. [1] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/c9a5… The output of [1] is as follows: " [init -> pf-signal_handler] --- pf-signal_handler started --- no RM attachment (WRITE pf_addr=1000 pf_ip=100061c from 2ae000) Genode::Pager_entrypoint::entry()::<lambda(Genode::Pager_object*)>: Could not resolve pf=1000 ip=100061c " The signal handler was registered correctly, because the line " Genode::Core_pd_session_component::submit(Genode::Capability<Genode::Signal_context>, unsigned int)::<lambda(Genode::Signal_context_component*)>: invalid signal-context capability " is missing. However, the method _handle_fault() is never entered. What am I doing wrong? Kind regards, Denis

3 11

Upgrade session before quota exceedes
by Denis Huber 25 Aug '16

25 Aug '16

Dear Genode community, I want to dynamically create Region maps through an RM session (amount not known at compile time). If the RAM quota of the session exceedes, I want to upgrade the RAM quota of the session. For this case I wrote a small test [1] which creates Region maps until an exception is thrown and I tried to catch it. I realized that the exception was thrown in another thread (core's entrypoint probably), meaning I cannot catch it in my test component's thread. [1] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/0a78… For a better insight I logged the RAM quota consumption in Rm_session_component::create. The output of my test looks as follows: [init -> rm_stresser] --- Rm-creation-stresser started --- [init -> rm_stresser] Round 0 Alloc avail: 49152 [init -> rm_stresser] Round 1 Alloc avail: 36864 [init -> rm_stresser] Round 2 Alloc avail: 24576 [init -> rm_stresser] Round 3 Alloc avail: 12288 [init -> rm_stresser] Round 4 Alloc avail: 0 [init -> rm_stresser] Round 5 Quota exceeded! amount=61440, size=8192, consumed=61440 Uncaught exception of type 'Genode::Allocator::Out_of_memory' Warning: abort called - thread: entrypoint Is there an easy way to upgrade a session's RAM quota before allocating objects with no available RAM? If there is already a component in Genode which solves my problem, I would love to see the source code :) Kind regards, Denis

2 2

partition table error
by john stokes 24 Aug '16

24 Aug '16

i am trying to run my l4android run script for the target kernel as fiasco.oc microkernel but when i try to access my android system image (system-ginger.img) from run script it shows error "sda:unknown partition table" my hard drive is GPT based. is this error mean that it is trying to access image from MBR based hard drive.please help me . my run script is being attached with the mail.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users