Re: Turmvilla scenario
Hello, On 19.10.2015 12:30, Vincent Digital wrote: > Can anyone help. Thanks in advance. > > I've set up the Turmvilla scenario on a Lenovo X201 as much as I can based > on the documentation stated by everyone else that contributed. On boot-up I > could get the CLI_Monitor and upon entering "start linux" subsystem, I've a > pop-up window that just hang. I could not kill it too from the CLI_Monitor. the log output of the starting Vbox VM is available via the noux subsystem. Please start the noux subsystem and monitor the file /shared/log. It should give you some useful information about what went wrong during VM startup. Cheers, Alex. -- ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: genode bare hardware on the odroids - howto?
Hi Suriyan On 14/10/15 01:17, Suriyan Ramasami wrote: Hello wonderful people! Greetings and thanks for the awesome work with genode. I have been trying to run genode on bare hardware on the odroids -> odroid-x2/odroid-xu for which I presume - they are already supported (the release notes mention them). In the case of ODROID-x2 does not support bw. Support for ODROID-x2 mentioned in the release notes is using the microkernel Fiasco.OC. What is missing is a step by step guide of building say, nested_init or a simpler printf application which shows some output when run from the uboot prompt. I tried following the instructions as mentioned in http://genode.org/documentation/platforms/hw (it generates an elf file, but then passing RUN_OPT="--target uboot" did not create the uImage file. Well, I did convert the elf to a bin file with objcopy and then converted that to an uImage file with mkimage. Am not sure if that is correct. The guide for the compilation of genodeOS to bw must change the following line /tool/create_builddir hw_ BUILD_DIR= by this line /tool/create_builddir foc_odroid_x2 BUILD_DIR= in case you want to use the ODROID-x2 What, I ask is, is there a step by step which will get me an UART output from genode on any of the supported odroid's using the latest genode code from git? Any pointers to such a doc would be immensely helpful to me as I would like to explore genode. Thanks in advance! Regards - Suriyan best regards Alexy -- ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main -- ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Re: Noux application
Hello Joseph, On Sat, Oct 17, 2015 at 12:31:09PM +0200, Joseph Lee wrote: > I am running a simple "tz_vmm" example in Genode on imx53 qsb. I have Noux > application which runs on top of Noux runtime inside the secure world. I > wanted to access this Noux applications inside tz_vmm application, calling > a function of Noux application from tz_vmm code. But i have no idea how to > do that. Could anyone please give me some hint? What you're trying to achieve is to run two components (tz_vmm and a Noux process) and trigger the execution of a function in the Noux process by the tz_vmm component, right? I fear that my rephrasing does not make anything more clear in your application scenario but I will nevertheless try to propose a direction to follow. The Noux environment provides a POSIX runtime and POSIX (pthreads etc. aside) is all about files when it comes to data exchange. So, you may monitor a file (e.g., via select()) in the program. If you place the file in a ram_fs and permit access to the file system to both, the Noux process and tz_vmm, tz_vmm could trigger code execution in the Noux process by writing into the file that is monitored. This scenario should also work on any POSIX system where you may implement a prototype. In case I got you wrong, please try to elaborate more on your goals or give more details about your scenario. 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 -- ___ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
Turmvilla scenario
Hi, Can anyone help. Thanks in advance. I've set up the Turmvilla scenario on a Lenovo X201 as much as I can based on the documentation stated by everyone else that contributed. On boot-up I could get the CLI_Monitor and upon entering "start linux" subsystem, I've a pop-up window that just hang. I could not kill it too from the CLI_Monitor. Attached are the log messages captured via AME : Bender: Hello World. Need 043fb000 bytes to relocate modules. Relocating to 7bc05000: Copying 679780 bytes... Copying 679436 bytes... Copying 677296 bytes... Copying 454608 bytes... Copying 362676 bytes... Copying 402116 bytes... Copying 4604 bytes... Copying 87208 bytes... Copying 1470576 bytes... Copying 475500 bytes... Copying 224656 bytes... Copying 438044 bytes... Copying 1893512 bytes... Copying 28508 bytes... Copying 370384 bytes... Copying 87208 bytes... Copying 354672 bytes... Copying 61056 bytes... Copying 342200 bytes... Copying 350488 bytes... Copying 19947520 bytes... Copying 9277440 bytes... Copying 3553280 bytes... Copying 293864 bytes... Copying 89428 bytes... Copying 409848 bytes... Copying 481064 bytes... Copying 401276 bytes... Copying 353540 bytes... Copying 396456 bytes... Copying 432804 bytes... Copying 410028 bytes... Copying 417088 bytes... Copying 367220 bytes... Copying 525284 bytes... Copying 530188 bytes... Copying 392112 bytes... Copying 396952 bytes... Copying 344028 bytes... Copying 584836 bytes... Copying 466468 bytes... Copying 331312 bytes... Copying 1203316 bytes... Copying 398804 bytes... Copying 9363900 bytes... Copying 156212 bytes... Copying 1383460 bytes... Copying 1268380 bytes... Copying 876148 bytes... Copying 936560 bytes... Copying 76240 bytes... Copying 18900 bytes... Copying 33744 bytes... Copying 157940 bytes... Copying 1026384 bytes... Copying 610304 bytes... Copying 490884 bytes... Copying 389368 bytes... Copying 388140 bytes... Copying 402136 bytes... Copying 16433 bytes... Copying 852656 bytes... Copying 1264272 bytes... NOVA Microhypervisor v7-a4a926a (x86_32): Oct 10 2015 18:00:57 [gcc 4.9.2] [ 0] CORE:0:0:0 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU M 580 @ 2.67GHz [ 1] CORE:0:0:1 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU M 580 @ 2.67GHz [ 3] CORE:0:2:1 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU M 580 @ 2.67GHz [ 2] CORE:0:2:0 6:25:5:4 [2] Intel(R) Core(TM) i5 CPU M 580 @ 2.67GHz [ 0] DMAR:0xc23c5060 FRR:0 FR:0x5 BDF:0:2:0 FI:0xb56b4000 Hypervisor features VMX Hypervisor reports 4x1 CPUs - boot CPU is 0 Hypervisor info page contains 99 memory descriptors: detected physical memory: 0x - size: 0x9e800 use physical memory: 0x - size: 0x9e000 detected physical memory: 0x0010 - size: 0xbb17c000 use physical memory: 0x0010 - size: 0xbb17c000 detected physical memory: 0xbb282000 - size: 0xdd000 use physical memory: 0xbb282000 - size: 0xdd000 detected physical memory: 0xbb40f000 - size: 0x6 use physical memory: 0xbb40f000 - size: 0x6 detected physical memory: 0xbb70f000 - size: 0x8000 use physical memory: 0xbb70f000 - size: 0x8000 detected physical memory: 0xbb71f000 - size: 0x4c000 use physical memory: 0xbb71f000 - size: 0x4c000 detected physical memory: 0xbb7ff000 - size: 0x1000 use physical memory: 0xbb7ff000 - size: 0x1000 detected physical memory: 0x0001 - size: 0xfc00 detected physical memory: 0x0002 - size: 0x3c00 map multi-boot module: physical 0x7bd3a000 -> [0x001d-0x002a02b0) - core map multi-boot module: physical 0x7be0b000 -> [0x2000-0x6031) - config map multi-boot module: physical 0x7be1 -> [0xa000-0x0006c2d8) - init map multi-boot module: physical 0x7be73000 -> [0x0007-0x000cec2c) - timer map multi-boot module: physical 0x7bed2000 -> [0xb000-0xb005f0f8) - part_blk map multi-boot module: physical 0x7bf32000 -> [0x002a4000-0x0031bd84) - ahci_drv map multi-boot module: physical 0x7bfaa000 -> [0xb0061000-0xb00f6000) - ld.lib.so map multi-boot module: physical 0x7c04 -> [0xb00f6000-0xb01f0950) - libc.lib.so map multi-boot module: physical 0x7c13b000 -> [0xb01f2000-0xb02188f4) - libm.lib.so map multi-boot module: physical 0x7c162000 -> [0x000dd000-0x000e53d0) - pthread.lib.so map multi-boot module: physical 0x7c16b000 -> [0x000e9000-0x000ed9d4) - libc_lock_pipe.lib.so map multi-boot module: physical 0x7c17 -> [0xb021a000-0xb022c9d0) - libc_terminal.lib.so map multi-boot module: physical 0x7c183000 -> [0xb022e000-0xb0312a70) - libiconv.lib.so map multi-boot module: physical 0x7c268000 -> [0xb0314000-0xb03e9e74) - stdcxx.lib.so map multi-boot module: physical 0x7c33e000 -> [0xb03eb000-0xb0520a9c) - rump.lib.so map multi-boot module: physical 0x7c474000 -> [0xb0522000-0xb0673c24) - rump_fs.lib.so map multi-boot module: physical 0x7c5c6000 ->
