users June 2017

users@lists.genode.org

19 participants
27 discussions

Individual file access
by Nobody III 16 Mar '18

16 Mar '18

To start off, I'm planning on building a component that handles file open/save requests for other components, primarily graphical applications. My plan is to use a qt5 QFileDialog for the user to select one or more files, then modify the vfs server's configuration to attach the selected file(s) to the component's filesystem. To attach individual files to a component's filesystem, it seems like I should write a server-side link vfs plugin. The plugin would be like a symlink, but would transparently resolve the link within the vfs server, providing access to otherwise inaccessible files. Is this possible? If so, can you give me some tips on how to implement it?

2 7

Raspberry Pi B+ with uboot and genode
by Bernhard Blieninger 24 Nov '17

24 Nov '17

Hi, I am currently working to get the raspberry pi b+ working with genode. I started with an raspberry pi uboot and a tftp server where genode.img lies on. The sd card was flashed via dd and the sd card image from here: http://wiki.beyondlogic.org/index.php?title=Compiling_uBoot_RaspberryPi For the genode image I used the newest version of genode on github and compiled a foc_rpi and an rpi with this command: ./tool/create_builddir foc_rpi BUILD_DIR=buildrpi or that ./tool/create_builddir rpi BUILD_DIR=./build-rpi and the command make run/demo This is working with the Raspberry Pi B(!) but when i put the sd card in the Raspberry Pi B +(!) it is not even booting. Therefore i prepared a sd card with raspbian and changed the kernel.img with the newly compiled u-boot.bin from http://git.denx.de/u-boot.git The sd card now boots again and shows u-boot but if I want to load genode.img it does not continue. If genode is loaded, for example by manually triggering it with bootz, the serial connected minicom screen shows encoding problem nonsense. Starting up a linux kernel works. If I start genode.img directly from the sd card it is not working either. If I try this sd card with the Raspberry Pi B(!) it is not working. What I have tested in a last step is, what happens if I substitute the u-boot.bin with the genode.img while using the sd card image that was provided by beyondlogic in the first place, this is working for the B model but not for the B +. Also tried a fresh sd card format it to fat16 and put all the stuff on it, which is in the boot folder from https://github.com/raspberrypi/firmware , but that is also not working. So I assume, that either the bootcode.bin and/or start.elf provided by raspberry are too new to use them with genode. I could maybe find older versions but I would just like to ask if this will help, maybe genode was never (meant to) run with some raspberry boot code that is newer then 2013.11 (http://genode.org/documentation/release-notes/13.11#Raspberry_Pi). Thanks in Advance for your help. Best Regards, Bernhard.

6 8

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 unknown＠example.com 10 Nov '17

10 Nov '17

Hi, Alex Yes, default_log.cc is listed in core-sel4.mk file. However, I've recently noticed that not all of the components listed in SRC_CC actually get to compile (including default_log.cc), which results in incomplete core-sel4 library. After taking a closer look, it turned out that io_port_session_support.cc and io_port_session_component.cc are the source of this problem. I had them out commented for my sabre_lite build as you've previously suggested. Removing them from core-sel4.mk for seL4_x86_32 build gave me the same results as for sabre_lite: incomplete core-seL4 library Library core-sel4 COMPILE cpu_session_component.o COMPILE cpu_session_support.o COMPILE cpu_thread_component.o COMPILE io_mem_session_component.o COMPILE io_mem_session_support.o COMPILE main.o COMPILE pd_assign_pci.o COMPILE pd_session_component.o COMPILE pd_upgrade_ram_quota.o COMPILE ram_session_component.o COMPILE ram_session_support.o COMPILE rom_session_component.o COMPILE rpc_cap_factory.o COMPILE version.o MERGE core-sel4.lib.a and the same "undefined reference" errors at the end. Now that I know where the problem is: what can I do from here? >>Please check that you compile and link the >>file to core. Check that the symbol actually shows up as symbol in >>core.o, e.g. by examining the output of "readelf -s >>build/<arch>/core/sel4/core.o". Not sure what you mean by the symbol. "readelf -s core.o | grep -i log" gave me the following output: 10311: 00000000 0 FILE LOCAL DEFAULT ABS log.cc Comparing to successful build for x86_32: 8733: 00000000 0 FILE LOCAL DEFAULT ABS log.cc 9028: 00000000 0 FILE LOCAL DEFAULT ABS core_log.cc 9175: 00000000 0 FILE LOCAL DEFAULT ABS default_log.cc Thanks

8 21

Networking Support in VirtualBox
by Chris Rothrock 27 Jul '17

27 Jul '17

I'm working with the VirtualBox run recipe where I have set use_net 1, added the repositories for dde_linux and dde_ipxe for the NIC driver. The build runs successfully and I can boot to the 2 virtual machines (I have one as TinyCore and one as DSL - Damn Small Linux) and interact with the OS's but there is no network adapter detected. To resolve this, I set the Adapter 0 to enabled in the test.vbox file but when I do this, I no longer get any video within the frame for the virtual machine (not even the bootloader for that frame). I have tried increasing the cap for the virtualbox module in the virtualbox.run recipe but still have nothing. I need to be able to test network communication between the two virtual machines (and to the wider network on which they are attached) but this is preventing me from this process. Any help in this would be greatly appreciated. -- Thank You, Chris Rothrock Senior System Administrator (315) 308-1637

4 19

Writing to UART mapped memory address
by Abhishek Kumar 24 Jul '17

24 Jul '17

Hello I am running trustzone Genode, with linux in normal world. I have made UART secure and I'm getting the fault address in DFAR register in dump in VM monitor. I want to write to a memory address which is mapped to UART i.e. physical address is in range [53FBC000, 53FFFFFF]. I am getting following error when I try to access the address: ``` no RM attachment (faulter 203128 with IP 7001e7d0 attempts to read from address 53fbc080) init -> tz_vmm -> vmm: unresolved pagefault at ip=7001e7d0 sp=e01fed10 fault address=53fbc080 core -> pager_ep: cannot submit unknown signal context ``` I'm using va_to_pa to get the physical address. I'm not sure how Genode maps the virtual addresses to I/O mapped physical region, or how can I write to UART mapped physical address? Thanks Abhishek

3 10

libc blocking functions/with_libc inside thread
by Boris Mulder 29 Jun '17

29 Jun '17

Hi all, We are trying to get openVPN to work under 17.05 again. One issue we encountered was that lwip sockets seem to function incorrectly; so we tried switching to lxip sockets. However, sockets in lxip require the use of the with_libc() function. When I put this around the openvpn_main() call it gives me the error: Error: void Libc::Kernel::run(Libc::Application_code&) called from non-kernel context The catch here is that I'm calling all this from inside the code of a Genode::Thread which executes the main function of openvpn. It seems that I cannot use with_libc inside another thread than the entrypoint thread. calling with_libc inside Component::construct() does not work for the new thread. It will fail when calling socket(). Is there any way of using sockets correctly inside another thread? -- 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 9

Query regarding extracting instruction which caused a data-abort exception
by Abhishek Kumar 26 Jun '17

26 Jun '17

Hello I am trying to modify genode trustzone. I want to read the instruction which lead to data abort exception in normal world, in the `dump` function in tz_vmm. I have value of all the registers through `_state` register. We tried with `_state->ip`. On converting 16 bits stored at the address pointed by _state->ip, we got ARM Thumb instruction: STRH R0, [R0, #6] > But the value (R0) + 6, doesn't match dfar. We're not sure if _state->ip is the register to go with. We tried with _state->mode[2].lr which is lr_abt register. But the address stored in lr_abt, lr_abt-16, lr_abt-32 all have 0s. Which is right register to get the address of the instruction which caused the data-abort exception? Thanks Abhishek

3 20

Mmiotrace for Genode
by Johannes Kliemann 19 Jun '17

19 Jun '17

Hi, I was told that there was a discussion about tracing mmio on the mailing list but I couldn't find it in the archive. So is there a tool for Genode that traces mmio accesses (like mmiotrace for Linux [1])? If not would there be a need for such a tool? Regards, JK [1]: https://www.kernel.org/doc/Documentation/trace/mmiotrace.txt

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users June 2017