users March 2017

users@lists.genode.org

35 participants
27 discussions

foc_odroid_x2 with tftp boot via uboot on odroid u3
by Bernhard Blieninger 22 Nov '17

22 Nov '17

Hi guys, we are trying to get genode running on an odroid u3 which should be quite similar to the foc_odroid_x2. I followed the instructions from here: http://odroid.com/dokuwiki/doku.php?id=en:u3_building_u-boot and here: http://forum.odroid.com/viewtopic.php?f=82&t=9128 And i used the newest version of u-boot from hardkernel here: https://github.com/hardkernel/u-boot/tree/odroid-v2015.10 I wanted to use tftp boot so and did not really know how to start at first place, so i picked up the ubuntu image from here: http://odroid.com/dokuwiki/doku.php?id=en:u3_release_linux_ubuntu and copied it via dd to the sd card. Then I just let the sd_fuse script from the first link overwrite the bootcode on the sdcard. And wrote into the boot.txt at the first partition the bootcode which it should execute, in my case something like this: |setenv ethact sms0| |setenv ethaddr 00:10:75:2A:AE:E0| |setenv gatewayip 192.168.4.1| |setenv netmask 255.255.255.0| |setenv serverip 192.168.4.2| |setenv usbethaddr 00:10:75:2A:AE:E0| |setenv ipaddr 192.168.4.43| || |usb start| |tftp 0x70000000 odroid/uImage| |bootm| | |Where uImage is the uImage created from the foc_odroid build. Then I used ||| | ||mkimage -A arm -C none -T script -n 'Custom Boot Script' -d boot.txt boot.scr|| |||| || ||to build the boot.scr and booted the odroid u3.|| || Problem now is that is says something like: || *ERROR: booting os 'Unknown OS' (3) is not supported* Where 3 means something like Checksum OK as the uboot manual states. Now I took the zImage from the ubuntu on the sd card and converted it to a uImage with the mkimage program. Put both on the tftp server and changed the boot.txt accordingly. If i select zImage the ubuntu kernel boots up and gets a kernel panic, if i select uImage(now from Ubuntu) i get the same unknown OS error. Does someone have similar issues and can tell me how to fix it? Is it even possible to use the foc_odroid_x2 on u3, they share the same hardware so it should be? Thanks in advance. Best regards, Bernhard.| | -- Bernhard Blieninger, B.Sc. Technische Universität München Fakultät für Informatik Lehrstuhl für Betriebssysteme Boltzmannstraße 3 85748 Garching Tel. +49 89 289 18795 Fax +49 89 289 18557 bliening@...389... www.os.in.tum.de

6 14

Restoring child with checkpointed state
by Denis Huber 15 Nov '17

15 Nov '17

Dear Genode community, thanks to you [1], I could implement my Checkpoint/Restore mechanism on Genode/Fiasco.OC. I also added the incremental checkpoint optimization, to stored only changed memory regions compared to the last checkpoint (although this is not working reliably due to a Fiasco.OC bug, which Stefan Kalkowski found for me [2]). I also managed to checkpoint the capability map and restore it with new badges and insert missing capabilities into the capability space of Fiasco.OC. [1] https://sourceforge.net/p/genode/mailman/message/35322604/ [2] https://sourceforge.net/p/genode/mailman/message/35377269/ My problem is, although I restore all RPC objects, especially the instruction and stack pointer of the main thread, and the capability map and space, the target component just starts its execution from the beginning of its Component::construct function. My approach: For the restore phase, I use Genode's native bootstrap mechanism (i.e. I create a Genode::Child object) until it requests a LOG session from my Checkpoint/Restore component. I force a LOG session request in ::Constructor_component::construct() just before "Genode::call_component_construct(env);" in https://github.com/genodelabs/genode/blob/16.08/repos/base/src/lib/base/ent… Until the session request several RAM dataspaces are created, among other RPC objects, and attached to the address space. In my restore mechanism I identify the RPC objects, which were created by the bootstrap/startup mechanism, and only restore their state. After that point, I recreate and restore the state of all other RPC objects which are known by the child component. At last, I restore the capability map and space. During that process the mandatory CPU threads are identified (three of them: "ep", "signal_handler", and "childs_rom_name") and restored to their checkpointed state, especially the ip and sp registers. I did that through the use of Cpu_thread::state(Thread_state), but without luck. Also, although I know that the CPU threads were already started, I tried to call Cpu_thread::start(ip, sp), but without success. After the restoration which happens entirely during the LOG session request of the child, my component returns with a valid session object to the child. Now the child should continue the work from the point where it was checkpointed, but it continues its execution right after the LOG session request, ignoring the setting of the instruction pointer. The source code of the restore CPU thread state is found in [3]. I used run script [4] for the tests. [3] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/660a… [4] https://github.com/702nADOS/genode-CheckpointRestore-SharedMemory/blob/660a… Curiously, the child runs just as nothing happened, although its stack area was also manipulated. Perhaps my approach by reusing the bootstrap/startup mechanism is not destined to work, or maybe I have missed some important points in this mechanism. If so, please point me to the problem. I would also consider other restoration approaches, for example, by recreating all RPC objects manually and insert them into the capability map/space. What are your thoughts on my approach? Can it work? Does something else work better? Kind regards, Denis

4 19

Genode on i.MX6Q Sabre Lite
by Yevgeny Lavrov 19 Jun '17

19 Jun '17

Hello Is there anything from Genode that I can try on i.MX6Q Sabre Lite development board? So far I've already attempted *log* image that I've obtained from compiling Genode for i.MX6 based Wandboard. The fastboot option that gets executed after *$ make run/log *resulted in nothing, so I've also tried to copy the created images onto SD Card and run them directly on the board. Steps: Once in u-boot prompt => fatload mmc 0 0x30000000 image.elf reading image.elf 1716880 bytes read in 107 ms (15.3 MiB/s) => bootelf 0x30000000 ## Starting application at 0x10001000 ... Then the terminal hangs w/o any output. Same thing happens when executing uImage => fatload mmc 0 0x30000000 uImage reading uImage 594679 bytes read in 48 ms (11.8 MiB/s) => bootm 0x30000000 Terminal hangs once it reaches: Starting kernel ... Any suggestions on what's wrong? Thank you

7 22

Socket fs
by Boris Mulder 13 Apr '17

13 Apr '17

Hi all, I've managed to port one of our existing network applications to use the socket fs from 17.02 now, starting from the echo_udp scenario and got it working. It looks a lot better now. Following this, we would like to share our findings about the socket fs so far: 1. In the release notes you describe the support for async file I/O. However, it seems that while asynchronous I/O works now, synchronous I/O is no longer possible. When I remove the select() call in the echo scenario, the call to recvfrom() will fail saying the socket is not connected (even though it is an UDP socket and should not have the notion of connections at all). Of course this means it is not posix compatible; the intended behaviour is to block until data becomes available. 2. Currently there are two ways an application can use tcp/ip sockets from the lxip stack: By using libc sockets, and by directly opening a file system session and writing to the right socket files. For any new Genode application that does not already depend on libc, the first way means you unnecessarily add the entirety of libc to your component. So the second way seems preferred. However, when programming an application using a file system session directly adds a lot of code with many open()s, read()s and write()s that could be abbreviated into single calls such as connect() and recv(). Have you thought of providing a more convenient API (such an object-oriented Socket class that hides the vfs calls from the application programmer)? Or do you consider using the fs session interface to be better? If so, why? -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

3 3

[GSoC] UEFI framebuffer task
by Philipp Kerling 31 Mar '17

31 Mar '17

Hi, I'm interested in participating in the Genode project as GSoC student, specifically the UEFI framebuffer task, so I am writing to you to briefly introduce myself and discuss the project idea. I am currently a student of Computer Engineering (MSc) at Ilmenau University of Technology in Germany in my second master semester. I've chosen computer engineering over computer science out of interest for low- level topics, which I think fits nicely with Genode. I worked on a toy x86 operating system with a friend some years ago, which was a good learning experience. It naturally did not go very far, but it did at least have basic multitasking and virtual memory :-) So, about the UEFI framebuffer proposal: Is the overall goal to have Genode/Nova running as bare UEFI application (without any OS Loader) or to have it loaded by GRUB (or similar) but not rely on outdated BIOS features (such as VBE) any more? Or support both like e.g. the Linux kernel does? This heavily influences the options available for framebuffer output, since the UEFI GOP (Graphics Output Protocol) that I assume you are referring to as one of the alternative/modern ways to access the framebuffer is only available as UEFI boot service. When being booted from an OS loader, usually only UEFI run-time services are available. In that case, the OS loader has to convey some information (mainly memory address, width/stride, height, depth) about the linear GOP framebuffer that the loader (or the firmware, for that matter) initialized to the kernel. multiboot2 does this for example with the framebuffer boot info tag. So to use this it would be sufficient to write a generic framebuffer driver operating on that information that is not specific to UEFI at all. It could probably also use the VBE framebuffer provided the OS loader initialized it. The "problem" with this is that it is probably not enough work to justify a 3-month GSoC proposal. I hope that the questions at least touch the right topics but do feel free to say so if you had something different in mind altogether. Best regards, Philipp

3 12

GSoC 2017 Consideration - Qemu
by Aaron 30 Mar '17

30 Mar '17

Hello, My name is Aaron. I am writing this letter because I would like to enter my name consideration in your [possible specificity] project. I did not participate in the pre-application phase, which I know places me at a disadvantage, and as a result I am sending this email to probe your interest. Your organization's participation in the Summer of Code is somewhat serendipitous for me. I had previously been communicating with the Qemu organization about the possibility of porting their software to additional platforms, but they were not receptive (possibly even planning to remove platform support). Porting qemu, is exactly what I've been wanting to do. I've also read through some of your mailing lists and I don't believe that anyone else is taking this task on. With all of that said: are you willing to accept new candidates, or are you only selecting from those that have already communicated? Thank you for any thoughts you might have, Aaron Hudson P.S. I made the mistake of emailing the main gsoc@...489..., which has only exacerbated the issue. The message above was the original message sent to that mailing list.

2 1

run/noux_bash
by Prashanth Mundkur 30 Mar '17

30 Mar '17

Hi, I'm trying to run noux_bash on Linux on today's master genode branch, and running into some issues. When I make run/noux_bash, I can see a x-window pop-up with the bash root prompt, and can extract using echo the following responses from bash: bash-4.1# echo $PATH /usr/gnu/bin:/usr/local/bin:/bin:/usr/bin:. bash-4.1# echo $SHELL /bin/bash bash-4.1# echo $TERM linux However, any non-shell command causes a dead unresponsive shell, with "Kernel: ipc_cap_data nullptr" output on the screen running the run script: [init] child "fb_sdl" announces service "Framebuffer" [init] child "fb_sdl" announces service "Input" [init] child "terminal" announces service "Terminal" [init -> terminal] create terminal session [init -> terminal] new terminal session: [init -> terminal] framebuffer has mode 1024x768@...487... [init -> terminal] character size is 6x14 pixels [init -> terminal] terminal size is 170x54 characters [init -> noux] Warning: stdin VFS path not defined, connecting to terminal session [init -> noux] Warning: stdout VFS path not defined, connecting to terminal session [init -> noux] Warning: stderr VFS path not defined, connecting to terminal session [init -> noux] --- noux started --- Kernel: ipc_cap_data nullptr The terminal doesn't recognize the '/' of my keyboard, and so I cannot try giving full paths to the various executables like /bin/env. Is this an issue with my local setup, or running a non-released genode version, or a bug? The broader question I had is: what would be needed to run bash from within a non-graphical terminal, as in via an ssh server. I have a very basic and incomplete sshd server running in genode linux [1], and need to fulfill, on the server end, the pty_request and shell_request sent by the ssh client. I notice that the bash port is built using: repos/ports/src/noux-pkg/bash/target.mk: # Prevent interactions with nonexisting tty driver CFLAGS += -DNO_TTY_DRIVER and a repos/ports/src/noux-pkg/bash/check_dev_tty.patch which removes a bash call to check_dev_tty(). Would this affect the above goal? Thanks, --prashanth [1] https://github.com/pmundkur/genode/commits/ssh_terminal

2 1

Genode on i.MX6 (eMMC Flash)
by Kranthi Tej 29 Mar '17

29 Mar '17

Hello, We are using a i.MX6 based board. We have been able to run Android successfully on the board. I've built the Genode demo image for the ARM processor by using the Wandboard build configuration (hw_wand_quad). I have successfully generated an image of Genode demo in the build directory named "demo.img". Can I load the generated Genode image onto the eMMC flash of the board using MfgTool? If so, can you please guide me on how it can be done? Thanks in advance, Kranthi

2 3

Genode and Android
by Steven Harp 28 Mar '17

28 Mar '17

If one wanted to run Android OS on ARM hardware with Genode underneath, what are the available options? On x86, Virtualbox ought to be up to the job, but without something like the (seemingly offline) L4Android port, the options for virtualizing Android on Genode appear limited. Has anyone tried this recently, and if nothing off the shelf will do it now, what path looks most promising? Steve Harp

2 1

genode and Android
by Steven Harp 27 Mar '17

27 Mar '17

If one wanted to run Android OS on ARM-based hardware with Genode underneath, what are the available options? On x86, Virtualbox ought to be up to the job, but without something like the (seemingly offline) L4Android port, the options for virtualizing on Genode appear limited. Has anyone tried this recently? If nothing off the shelf will do it now, what path looks most promising? Steve Harp

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users March 2017