users July 2017

users@lists.genode.org

16 participants
17 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

Boot problems using Genode 16.08 with Fiasco.OC r67 on a RPi Model B
by Alexander Weidinger 27 Nov '17

27 Nov '17

Dear Genode community, we are currently trying to get a Raspberry Pi 1 Model B running with Genode 16.08 and Fiasco.OC r67 from https://github.com/skalk/foc/. We made changes to both, genode and foc but the basis are the two mentioned versions. Trying to boot the RPi, we are left with the following message, the board resets itself? and again tries to boot: > ... > reading genode.img > 2060288 bytes read in 331 ms (5.9 MiB/s) > Kernel image @ 0x1000000 [ 0x1000000 - 0x11f7000 ] > > Starting k > L4 Bootstrapper > Build: #5 Wed Jul 5 17:34:36 CEST 2017, 4.9.2 > Scanning up to 512 MB RAM, starting at offset 32MB > > > U-Boot 2014.07-rc3-gd4614d4 (Jun 14 2014 - 01:23:23) > ... (Trying to boot vanilla genode 16.08 with vanilla foc r67 (from skalk) leads to the same behavior.) We were successful in running our setup (foc r67 and genode 16.08 both with our changes) on a pandaboard (real hardware) and on pbxa9 (qemu). Additionally we are able to successfully boot the RPi using vanilla genode 16.08 with the provided foc version (r56), using our u-boot configuration. Do we need to make additional changes to foc and/or genode to be able to boot the RPi using r67 of foc? Any hints or information are very welcomed! Regards, Alexander

2 4

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

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

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

Blocking wait for interrupt
by Johannes Kliemann 08 Aug '17

08 Aug '17

Hi, I'm currently writing a dde_linux driver that requires to wait for an interrupt to be handled. It basically initializes the hardware and then waits for an event to occur. This event is usually triggered by the interrupt (respectively its handler) which occurs after hardware initialization. My problem is that this interrupt doesn't appear while the function triggering it didn't return. So when this function blocks to wait for the interrupt, a deadlock is created. Besides using the timer I tried to block the execution with a semaphore creating the same problem. Creating an async version is no option due to the architecture of the Linux driver. How are interrupts handled in this case? What causes them to block and how can I work around this? Regards, JK

2 7

Any genodians attending SHA2017?
by Jean-Philippe Ouellet 02 Aug '17

02 Aug '17

Hello all, Long time lurker, first time poster. I will be attending SHA2017 [1] next week to give a talk about Qubes OS [2]. I see there was at least some mention of SHA among you [3], so perhaps some Genode people plan to attend? I've long been a fan of what Genode is working towards, and I would definitely be interested in exploring the possibility of a collaboration between Genode and Qubes at some point. To be clear, I do not represent Qubes in any official way, and I'm reaching out only as myself. Regards, Jean-Philippe [1]: https://sha2017.org/ [2]: https://www.qubes-os.org/ [3]: https://github.com/genodelabs/genode/issues/1985#issuecomment-290227597

3 3

lwip and seL4
by Steven Harp 01 Aug '17

01 Aug '17

Observed a problem testing lwip under seL4 (run/lwip). This succeeds with kernels okl4, foc, and nova, but under seL4 there are complaints from acpi_drv (see below). The "Error: I/O memory [1ffe1000,1ffe2000) not available" seems most concerning. Build architecture is x86_32, relying on drivers dde_ipxe, testing in qemu on Xenial. Theories / workarounds (seL4)? // Steve > [init -> nic_drv] --- iPXE NIC driver started --- > [init -> nic_drv] -- init iPXE NIC > [init -> acpi_drv] Error: ROM-session creation failed (ram_quota=6144, cap_quota=3, label="platform_info") > [init -> acpi_drv] Error: Could not open ROM session for "platform_info" > [init] child "timer" announces service "Timer" > [init] child "acpi_report_rom" announces service "Report" > Warning: void Genode::Rpc_cap_factory::free(Genode::Native_capability) not implemented - resources leaked: 0x10 > [init] child "acpi_report_rom" announces service "ROM" > Error: I/O memory [1ffe1000,1ffe2000) not available > Error: Local MMIO mapping failed! > [init -> acpi_drv] Error: IO_MEM-session creation failed (cap_quota=3, ram_quota=6K, base=0x1ffe1000, size=0x1000, wc=no) > [init -> acpi_drv] Warning: 1 dangling allocation at allocator destruction time > Warning: unmapping of managed dataspaces not yet supported > [init -> acpi_drv] Error: Unknown exception occured - failure > [init -> acpi_drv] Error: __cxa_guard_abort called > Kernel: Thread 'ep' died because of an uncaught exception > [init -> acpi_drv] Error: Uncaught exception of type 'Genode::Service_denied' > [init -> acpi_drv] Warning: abort called - thread: ep > [init] child "acpi_drv" exited with exit value 1 > Error: Test execution timed out > Makefile:309: recipe for target 'run/lwip' failed

2 2

Celebrate Genode's 9th anniversary with us!
by Norman Feske 31 Jul '17

31 Jul '17

Dear Genode community, to continue our tradition of celebrating our accomplishments in the form of a seasonal barbecue and camp fire, we invite Genode's friends and community to the banks of the river Elbe in Dresden/Germany. Unlike previous years, which were focused on technical breakthroughs, the leitmotif of the past year was Genode's long-term sustainability, maturity, and scalability. On that account, we streamlined key infra- structure (such as the VFS), and profoundly revisited the framework's architectural foundations and lowest-level protocols. This line of development eventually culminated in the application-binary compatibility across kernels as different as seL4, NOVA, or Linux. The practiced continuity of development was underlined by the third edition of the "Genode Foundations" book. With regard to Genode's role within the open-source community, we had the honor of hosting the microkernel devroom at this year's FOSDEM, and are very happy about the fruitful relationships with sister projects like the Muen separation kernel and the seL4 microkernel community. Business-wise, we are delighted about the growing use of Genode in commercial products, and about Genode's role as the technological basis for entirely new ventures, pursued independent from our company. Let us meet together to celebrate the past, present, and future of our project, and enjoy the get-together of the Genode team and collaborators. We will hold the anniversary party at the river bank of the Elbe: Google Maps: http://goo.gl/maps/C0luj 31st of August, 6 pm near Eisenberger Strasse in Dresden Enjoy the atmosphere at the river bank with tasty barbecue of vegetarian and non-vegetarian food, and a nice selection of beverages! If you are going to attend, please let us know by writing a short note to: info@...1... Cheers 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

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

Genode 17.05 dde_rump ISO filesystem
by Steven Harp 26 Jul '17

26 Jul '17

Hi: While evaluating file system alternatives, I ran some tests of the dde_rump file system code (Genode 17.05 master/HEAD on Ubuntu 16.04 / x86_64). The EXT2 and FAT file system tests work as expected (although the latter benefited from a <default caps="256">). The ISO file system however left me a puzzle (trace below; default caps line added to run file.) The same results appear under builds x86_{32,64} x KERNEL={linux,nova}. Any ideas regarding what might be going wrong? The prepared test image fs.iso appears to have the intended file "test.txt" on it. Best, Steve > > make run/rump_iso > ... > [init] child "rom_blk" announces service "Block" > [init] child "timer" announces service "Timer" > [init -> rom_blk] Using file=fs.iso as device with block size 2048. > [init -> rump_fs] Using cd9660 as file system > [init -> rump_fs] RUMP ver: 17 > [init -> rump_fs] RUMP_THREADS > [init -> rump_fs] RUMP_VERBOSE > [init -> rump_fs] _RUMPUSER_NCPU > [init -> rump_fs] RUMP_MEMLIMIT > [init -> rump_fs] asserting rump kernel 4064 KB of RAM > [init -> rump_fs] BOOTSTRAP > [init -> rump_fs] RUMP_NVNODES > [init -> rump_fs] RUMP_BLKFAIL > [init -> rump_fs] RUMP_BLKSECTSHIFT > [init -> rump_fs] RUMP_MODULEBASE > [init -> rump_fs] _RUMPUSER_HOSTNAME > [init] child "rump_fs" announces service "File_system" > [init] child "fs_rom" announces service "ROM" > [init -> fs_rom] request for test-iso > [init -> fs_rom] Error: /test-iso: lookup_failed > [init -> fs_rom] request for ld.lib.so > [init -> fs_rom] Error: /ld.lib.so: lookup_failed > [init -> fs_rom] Error: /ld.lib.so: lookup_failed > [init -> fs_rom] Error: /ld.lib.so: lookup_failed > [init -> fs_rom] Error: /test-iso: lookup_failed > [init -> fs_rom] Error: /test-iso: lookup_failed > ... > (timeout)

2 2

Using Genode 17.05 with Fiasco.OC
by Jörg-Christian Böhme 26 Jul '17

26 Jul '17

Hello, first, thanks for your effort guys. I'm very glad to see that a microkernel architecture/framework is exists in C++ :-) A short description about me: I'm C++ enthusiasts (C++ User Group Duesseldorf and Meeting C++ stuff member) and also very interested about operating systems. I pay attention to security feature. For some year, Blackberry announced that they discontinued BB10. I was very disappointed about that because BB10 is developed in Qt/C++ and focuses in security because they based on a microkernel architecture from QNX as operating system. After the announcement from Blackberry, I was thinking about to write a microkernel architecture in C++ but I checked if they exists a microkernel architecture in C++ and I was very happy about that they really exists. I started first with Fiasco.OC but I found out that in Genode it uses the new C++ Standard so here I'm :-) I started a month ago with Gnode hello tutorial and play around with them. Therefore, I call myself a newbie :-) But at the end, I will use Genode on my laptop (like turmvilla example) and start to develop some application on it :-). But first, I think about to start with a small server. The host provider that I use, use a QEMU with KVM enable as virtual server. So it is not possilbe to use NOVA on it because of the KVM enabled featuer (I think) but Fiasco.OC works. The problem: So I try to build/create a image from the lighttpd example with Fiasco.OC kernel. The image started but the lighttpd does not work. Also the hello tutorial with Fiasco.OC does not work anymore. I checked the issue tracker on github but I didn't find any issue about that. What I figure out: - Hello tutorial When I increase in the hello tutorial the "default caps" from 50 to 54 in the config, then the tutorial is working with Fiasco.OC kernel. - lighttpd Here I must first "move" the timer service in the config (see my commit on github [1]) then it works with the NOVA kernel. With Fiasco.OC I get following error: Error: nic_drv -> : environment ROM session denied (label="device_pd", ram_quota=6144, cap_quota=3, diag=0) I try to add "device_pd" in the boot modules because it is missing in the rom fs but device_pd is not compile for the Fiasco.OC, only for NOVA. I found out following in: genode-src/repos/os/src/drivers/platform/spec/x86/device_pd/target.mk It looks like device_pd is only build for NOVA. Is this a known issue or somebody working on it ? Or works the lighttpd example with Fiasco.OC kernel for anyone ? If you still need additional infos, let me know. Regards, Jörg [1] https://github.com/Bjoe/genode/commit/8522e1b06c62e33988a03c5f308f16fad5250…

2 3

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

Re: Genode on i.MX6
by Alexander Boettcher 07 Jul '17

07 Jul '17

Hi Hinnerk and Yevgeny, On 06.07.2017 03:06, Hinnerk van Bruinehsen wrote: > On Wed, Jul 05, 2017 at 12:43:29PM +0200, Alexander Boettcher wrote: >> Thanks to your work I could get the tool integrated into the run tool >> infrastructure of Genode in within one day. And the best, it boots and I >> get the serial life sign of Genode/seL4 on ARM. > nice to hear thank it helps. I guess the next step will be to split out > the x86 specific code from the generic parts and implement arm specific > stuff. this is now done, see the issue 2451 [0] and the referenced branch. > Let me know if I can help. I'm kind of fiddling around with this for > quite a while now. You may now try to re-add your desired board. In theory you should just add some *.mk files at the right places, some minor patches to the autoconfig.h, but without actually changing (hopefully) the code of 'core' on Genode/seL4. I'm interested to hear from you, whether my assumption is right in that regard. Cheers, Alex. [0] https://github.com/genodelabs/genode/issues/2451 -- Alexander Boettcher Genode Labs http://www.genode-labs.com - http://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users July 2017