users

users@lists.genode.org

1 participants
2310 discussions

make run/rump_ext2 fails
by Adrian 22 Jan '15

22 Jan '15

Hello, I am trying to explore the rump_fs facilities. I followed the repos/dde_rump/README and failed when executing make run/rump_ext2. Following is a pasted-in terminal output. Any help would be appreciated. adrian@...295...:~/genode-14.11/build/build.fs$ make run/rump_ext2 using run script /home/adrian/genode-14.11/repos/base-nova/run/env using run script /home/adrian/genode-14.11/repos/dde_rump/run/rump_ext2.run building targets: core init drivers/timer server/ram_blk server/rump_fs test/libc_vfs spawn make core init drivers/timer server/ram_blk server/rump_fs test/libc_vfs make[1]: Betrete Verzeichnis '/home/adrian/genode-14.11/build/build.fs' Error: target 'test/libc_vfs' does not exist make[1]: *** [error_missing_targets] Fehler 1 make[1]: Verlasse Verzeichnis '/home/adrian/genode-14.11/build/build.fs' Error: Genode build failed make: *** [run/rump_ext2] Fehler 252 adrian@...295...:~/genode-14.11/build/build.fs$ Regards, Adrian Schuur

3 2

[HEADS UP] Refactored run tool on staging
by Josef Söntgen 22 Jan '15

22 Jan '15

Hello, tl;dr we merged the modularized version of our run tool to the staging branch. This version requires changes in the build directory, e.g., changes to 'etc/build.conf' and it is therefore advised to remake all used build directories if one uses the current staging branch. There is also 'tool/run/README', which explains the usage and the architecture in more detail. In addition you can take a look at the corresponding issue [1]. The run tool served us well over the years and by continously extending its functionality it met our daily requirements. The way it was extended up to now, however, was in an ad-hoc fashion that made future changes and maintaining more time-consuming. We addressed these problems by refactoring the run tool: * Modularizing the run tool: each step (building/loading components, execution scenarios and so) is now implemented by a module. All of the common use cases, that were handled by the old run tool, are now covered by combining these modules. This makes the actual run tool more managable and makes future extensions easier. * Unifying the argument handling of the run tool: each module is configured explicitly in the same fashion. That makes configuration failures more visible. To just give an example on how the interface of the run tool changed, here is a comparison of the old way and the new way to handle a common use case: In this case, we want to reset the target system and caputure the LOG output via AMT. The target system loads all files it needs to execute the scenario via TFTP: * Old (changes in nova_x86_64/etc/build.conf): RUN_OPT = --target amt --tftp-absolute export AMT_TEST_MACHINE_IP = 10.23.42.51 export AMT_TEST_MACHINE_PWD = secret export PXE_TFTP_DIR_BASE = /var/lib/tftpboot export PXE_TFTP_DIR_OFFSET = /x86 * New (changes in nova_x86_64/etc/build.conf): RUN_OPT = --include boot_dir/nova AMT_HOST = 10.23.42.51 AMT_PASSWORD = secret RUN_OPT += --include power_on/amt \ --power-on-amt-host $(AMT_HOST) \ --power-on-amt-password $(AMT_PASSWORD) RUN_OPT += --include log/amt \ --log-amt-host $(AMT_HOST) \ --log-amt-password $(AMT_PASSWORD) RUN_OPT += --include load/tftp \ --load-tftp-base-dir /var/lib/tftpboot \ --load-tftp-offset-dir /x86 --load-tftp-absolute The new way is arguably more verbose but also makes the configuration more clear, which is more important in our opinion. In addition, it is possible to capture the LOG output, i.e., via an USB-serial adapter by replacing 'log/amt' with 'log/serial'. That is something, that was more difficult to achieve with the old tool. When creating a new build dir, a default RUN_OPT configuration is added to the generated 'build.conf'. In most cases this means creating an ISO image and starting the scenario in Qemu like the old tool did in the default configuration. As I have said before, there is a README file, that hopefully provides all information that is needed to get you started with the new tool. If you think there is something that is missing from this documentation, please drop a note either via E-Mail or github. Cheers Josef [1] https://github.com/genodelabs/genode/issues/1355

1 0

Run script issue
by chirag garg 20 Jan '15

20 Jan '15

Hi all, I created one run script "switch" which gives me the following error at compilation at the last stage. make[1]: Leaving directory `/home/chirag/genode-ns/build6' cp: cannot stat `bin/switch': No such file or directory while executing "exec cp bin/$binary [run_dir]/genode" (procedure "copy_and_strip_genode_binaries_to_run_dir" line 4) invoked from within "copy_and_strip_genode_binaries_to_run_dir $binaries" (procedure "build_boot_image" line 16) invoked from within "build_boot_image "core init switch"" (file "/home/chirag/genode-ns/repos/os/run/switch.run" line 37) invoked from within "source $include_name" ("foreach" body line 3) invoked from within "foreach include_name [get_cmd_arg --include ""] { puts "using run script $include_name" source $include_name }" (file "/home/chirag/genode-ns/tool/run" line 1004) make: *** [run/switch] Error 1 Like error message says that it is not able to copy switch file from the bin folder because it is not there. WHY this script is failed to create the bin/switch file ? Please let me know the all possible reason behind it. I am attaching switch.run script in the mail. Thanks in advance. Regards Chirag Garg IIT Madras , Rise Lab

3 4

Network Performance in Genode
by Mohammad Hamad 18 Jan '15

18 Jan '15

HI, I am studying the network performance (with lwip) of Genode with different kernels such as linux and base_hw. Genode ported netperf as tool to measure the performance with many tests ( TCP_RR , TCP_STREAM and etc). there is run file (netperf_lwip) working with linux kernel . I made some changes to make it run for Raspberry bi but i still have some questions . - is netpperf ported to genode for measuring the performance on the linux kernel or it is accepted tools for Raspberry bi too, can I trust it with Raspberry? - each time i run the TCP_RR test I get different results . while it is almost stable when i run the same test between two linux machines . - should i accept the result for one test or i should calculate the average of many tests for the same parameters best, Mohammad

1 0

Juno Development Platform and Genode
by Stefan Brenner 15 Jan '15

15 Jan '15

Hi guys, just a short question, are there any experiences to run Genode on top of the Juno ARM Development Platform (http://www.arm.com/products/tools/development-boards/versatile-express/juno… Best, Stefan

1 0

Genode at FOSDEM 2015
by Norman Feske 14 Jan '15

14 Jan '15

Hello again, I am happy to announce that there will be three Genode-related talks at FOSDEM this year: "Genode - OS security by design" Sunday 12:00 - 12:25 Security devroom (AW1.120) "Transplantation of VirtualBox to the NOVA microhypervisor" Sunday 14:20 - 15:00 Virtualization devroom (UD2.120) "Introducing a radically componentized GUI architecture" Sunday 15:30 - 16:15 Microkernel devroom (K.3.201) More information about the talks (including abstracts) are available at the FOSDEM website: https://fosdem.org/2015/schedule/speaker/norman_feske/ 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

Exploring Genode
by Norman Feske 14 Jan '15

14 Jan '15

[my third attempt to post this message on the mailing list...] Thanks Tim, for featuring Genode on your blog! http://thenewsh.blogspot.de/2015/01/exploring-genode.html I think that your assessment of our project is fairly accurate. Cheers Norman

1 0

Re: Roadmap 2015
by unknown＠example.com 14 Jan '15

14 Jan '15

I've been looking from outside the fence what's happening inside the Genode garden with great interest. To me, great incentives to step inside would be: * toolchain with full Ada support * touch and pen input device support * a structured handbook (PDF, EPUB) * a bootable live system image suitable for development As concerns platform support, it would be nice to have Genode running on cheap hardware. Particularly interesting to me would be: * Allwinner A20 SoC support for development boards * Freescale i.MX 507 support for eBook readers I should detail some further thoughts in a later mail. There's still a lot to say, but Genode in general seems to be on a good path. Not directly related to the software itself, is there a way to display the mailing list archive in a nicer look? If I remember correctly, it was around the time of the move to github or some other infrastructural change, that the old view was changed. I think, back then, the theme was similar to the look of http://www.mail-archive.com/fpc-devel@...283.../. It would be great, if the old look could be restored.

3 2

Mailing-list issues
by Christian Helmuth 13 Jan '15

13 Jan '15

Hello all, if I'm lucky this mail reaches the list. Again, we experience mailing-list issues at Sourceforge. Unfortunately, we don't get any response from SF staff on our reported issue https://sourceforge.net/p/forge/site-support/9440/ So, please be patient and (like me) cross fingers that we get back operational soon. Regards -- 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

2 1

bare-hw trustzone on the Freescale i.MX 6 Sabre SD board
by Mahdi Aichouch 13 Jan '15

13 Jan '15

Hello, I am trying to port the bare-hw trustzone to the Freescale i.MX 6 quad-core Sabre SD board. I started from the source code given in this repository: https://github.com/decaprox/genode I adapted the TSC-380 driver from the versatile express version as a TZASC to the i.MX-6 board. At this moment, I just configure the existing TSC-380 with the right base address, but I did not yet configured it to secure any memory region. Also, I did not yet used the CSU that was implemented for the i.MX53 to secure any device. I partitioned the the memory space into two parts: 0x1000 0000 - 0x2000 0000 : as a secure memory space 0x2000 0000 - 0x4000 0000 : as a non secure memory space I implemented a small kernel in order to test the implementation. My simple kernel is just an assembly code that call C function, that prints a message on the serial port. I get an error after running the run/vmm test case. Here are the debug messages that I get void Kernel::trustzone_initialization(Kernel::Pic*): --- IMX6 trustzone INIT --- Core memory allocator --------------------- Allocator 102d46c0 dump: Block: [10000000,1000001c) size=0000001c avail=00000000 max_avail=00000000 Block: [1000001c,10000038) size=0000001c avail=00000000 max_avail=00000000 Block: [10000038,10000054) size=0000001c avail=00000000 max_avail=1fd28000 Block: [10000054,10000070) size=0000001c avail=00000000 max_avail=00000000 Block: [10000070,1000008c) size=0000001c avail=00000000 max_avail=00000000 Block: [1000008c,10001000) size=00000f74 avail=00000f74 max_avail=1fd28000 Block: [102d8000,30000000) size=1fd28000 avail=1fd28000 max_avail=1fd28000 => mem_size=533893120 (509 MB) / mem_avail=533892980 (509 MB) IO memory allocator ------------------- Allocator 102d4b1c dump: Block: [00000000,02020000) size=02020000 avail=02020000 max_avail=02020000 Block: [02024000,020d0000) size=000ac000 avail=000ac000 max_avail=0df2c000 Block: [020d4000,10000000) size=0df2c000 avail=0df2c000 max_avail=0df2c000 Block: [100ec000,100f0000) size=00004000 avail=00004000 max_avail=20000000 Block: [20000000,40000000) size=20000000 avail=20000000 max_avail=20000000 => mem_size=805289984 (767 MB) / mem_avail=805289984 (767 MB) IRQ allocator ------------------- Allocator 102d53d4 dump: Block: [00000000,0000003a) size=0000003a avail=0000003a max_avail=0000003a Block: [0000003b,00000058) size=0000001d avail=0000001d max_avail=000003a7 Block: [00000059,00000400) size=000003a7 avail=000003a7 max_avail=000003a7 => mem_size=1022 (0 MB) / mem_avail=1022 (0 MB) ROM filesystem -------------- Rom_fs 102d5814 dump: Rom: [100a5000,100a5358) linux Rom: [1004f000,1007fedc) init Rom: [100a7000,100a71ef) config Rom: [100a6000,100a601f) initrd.gz Rom: [10080000,100a409c) vmm int main(): --- create local services --- int main(): --- start init --- int main(): transferred 508 MB to init int main(): --- init created, waiting for exit condition --- [init] Could not open file "ld.lib.so" [init] parent provides [init] service "ROM" [init] service "RAM" [init] service "IRQ" [init] service "IO_MEM" [init] service "CAP" [init] service "PD" [init] service "RM" [init] service "CPU" [init] service "LOG" [init] service "SIGNAL" [init] service "VM" [init] child "vmm" [init] RAM quota: 3932160 [init] ELF binary: vmm [init] priority: 0 [init -> vmm] Start virtual machine [init -> vmm] Curious exception occurred [init -> vmm] Cpu state: [init -> vmm] r0 = 00000000 [init -> vmm] r1 = 000008e0 [init -> vmm] r2 = 20000100 [init -> vmm] r3 = 00000000 [init -> vmm] r4 = 00000000 [init -> vmm] r5 = 00000000 [init -> vmm] r6 = 00000000 [init -> vmm] r7 = 00000000 [init -> vmm] r8 = 00000000 [init -> vmm] r9 = 00000000 [init -> vmm] r10 = 00000000 [init -> vmm] r11 = 00000000 [init -> vmm] r12 = 00000000 [init -> vmm] sp = 00000000 [init -> vmm] lr = 00000000 [init -> vmm] ip = 20000100 [init -> vmm] cpsr = 00000093 [init -> vmm] sp_und = 00000000 [init -> vmm] lr_und = 00000000 [init -> vmm] spsr_und = 00000000 [init -> vmm] sp_svc = 00000000 [init -> vmm] lr_svc = 00000000 [init -> vmm] spsr_svc = 00000000 [init -> vmm] sp_abt = 00000000 [init -> vmm] lr_abt = 00000000 [init -> vmm] spsr_abt = 00000000 [init -> vmm] sp_irq = 00000000 [init -> vmm] lr_irq = 00000000 [init -> vmm] spsr_irq = 00000000 [init -> vmm] sp_fiq = 00000000 [init -> vmm] lr_fiq = 00000000 [init -> vmm] spsr_fiq = 00000000 [init -> vmm] exception = reset virtual void Genode::Signal_session_component::free_context(Genode::Signal_context_capability): Not implemented Note: The file linux and initrd.gz showed here are not real. I named my simple kernel as linux, and the initrd.gz file is an empty file. The VMM version I am using loads an elf binary kernel. I attached the assembly file of my simple kernel. From the dump of the CPU state, we can see that the IP register shows the first instruction of the kernel, which apparently generates an exception. Could someone tell me how to track down the source of the error and help me to debug it. Thanks very much in advance. Kind regards, Mahdi

5 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users