users January 2019

users@lists.genode.org

21 participants
16 discussions

usb_drv error -92 for RPi | Genode 18.05 with Fiasco.OC 79
by Alexander Weidinger 18 Apr '19

18 Apr '19

Hello everyone, when executing 'lwip' on the RPi 2, I get the following output for the usb_drv: > [init -> usb_drv] dev_info: DWC OTG Controller > [init -> usb_drv] dev_info: new USB bus registered, assigned bus number 1 > [init -> usb_drv] dev_info: irq 9, io mem 0x00000000 > [init -> usb_drv] dev_info: USB hub found > [init -> usb_drv] dev_info: 1 port detected > [init -> usb_drv] dev_info: new high-speed USB device number 2 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/all, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 3 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/all, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 4 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_info: new high-speed USB device number 5 using dwc_otg > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: device descriptor read/8, error -92 > [init -> usb_drv] dev_error: unable to enumerate USB device Does anyone have an idea what I can do, to get the Ethernet adapter working? Any help is appreciated! I don't really understand the problem here, since the driver works flawlessly for the RPi 1 B+ (using foc_rpi as platform) - which uses the same chip as the RPi 2 (SMSC LAN9514). My Genode version [2] and Fiasco.OC version [3]. To the backstory: ----------------- I am currently in the process of "porting" Fiasco.OC/Genode to the Raspberry Pi 2 (Model B). As a basis I use Genode in the version 18.05 and Fiasco.OC in the version 79. I created a new device, the rpi2, and based it on the already available rpi model. The main changes I did for the rpi2 platform [1] are - the different arm architecture - from armv6 to armv7a in a few files - the different physical base address - from 0x2000:0000 to 0x3f00:0000 - a RAM size of 1008 MB starting at 0x0000:0000 (1024 MB - 16 MB for peripherals) I use version 79 of the Fiasco.OC kernel since it adds support for the three different BCM283X platforms. In order to get version 79 of the kernel running with Genode, I used the official 79 as a basis and cherry-picked commits from Genode's version of Fiasco.OC (72). [0] My setup works completely fine for the RPi 1 (Model B+), even for the usb/nic driver. As the RPi 1 (Model B+) makes use of the SMSC LAN9514, instead of the SMSC LAN9512 (used in RPi Model B) it should also work for the RPi 2 (Model B), since this SBC also uses the SMSC LAN9514. [0] https://github.com/skalk/foc/commits/r72 [1] https://github.com/irgendwie/genode/commits/foc-rpi2 [2] https://github.com/irgendwie/genode/tree/foc-rpi2 [3] https://github.com/irgendwie/foc/tree/genode-r79-rpi2 ----------------- Best regards Alexander

5 15

Genodians.org BETA is live
by Josef Söntgen 30 Jan '19

30 Jan '19

Hello fellow Genodians, as already hinted to by Norman in the roadmap discussion, the Genodian's website [1] is now live. It is a federated microblogging platform operated by Genode Labs and running on a Genode system (it uses base-hw and runs within an KVM-based VM). All recipes needed for building the system image are available in the genodians.org repository [2]. [1] http://genodians.org [2] https://github.com/genodelabs/genodians.org The repository also contains the list of all authors whose content is aggregated and published on the website. For more information, e.g. how to participate, please look into the README file. Since there is probably one or the other rough edge left and we have not yet decided on a plan to replace the self-signed certificate, the current version should be treated as BETA - stuff is allowed to fall off :-). Regards Josef -- Josef Söntgen Genode Labs http://www.genode-labs.com/ · http://genode.org/

4 4

Amateur Radio
by Tyrell Jentink 30 Jan '19

30 Jan '19

Hello everyone, I am new to this mailing list, and to Genode generally; I will probably be doing most of my experiments in the near future with a Raspberry Pi, and I'm likely to be fairly quiet about it, but I haven't actually fired anything up yet. My background is with Linux, and I anticipate a bit of discomfort as I try to adapt to the Genode Way... My interest is largely in Amateur Radio; The Linux community has a long history of supporting Amateur Radio with protocol stacks (Such as AX.25) and both hardware and virtual Terminal Node Controllers in the kernel. There are also userland implimentations. Some of those run on Windows... some are open source... In other words, lots of code is out there... In various levels of loyalty to the Unix philosophy... Putting it in the kernel may have never made sense... And the "Genode Way" has value in organizing the complexity of the AX.25 networking stack, similar to how it separates the organization of the Ethernet stack... How much, if any, actually belongs in Genode and/or Sculpt OS is beyond me... It all probably deserves to be an installable package, rather than a core package... But it probably also benefits from Capabilities, as it will interface with hardware, so probably more than just an untrusted Linux instance... Fldigi also seems like it could benefit from being broken apart into smaller components, with a stronger capability based trust model... Or not, I really don't know... Anyway... I'm new... And I'm still trying to wrap my head around the "Right" way to think about these things... Are there any other hams out there interested in bouncing around ideas? 73, Tyrell Jentink, KD7TKJ

2 1

Genode on RPI
by Tomasz Gajewski 29 Jan '19

29 Jan '19

Hi, I'll try to quickly move discussion about rpi to new thread to not pollute thread about Roadmap 2019. Bob Stewart <robjsstewart(a)gmail.com> writes: > I'm working on implementing a base-hw kernel on a Cortex A53 platform > (not Rpi) which is what the Rpi 3x is based on. So, that means a > significant amount of work to convert from the existing Genode code > supporting the armv7 architecture to support the armv8 > architecture. I'm focused initially on only the aarch64 instruction > set, but will later add support for aarch32. This is a retirement > project for me so my progress is not driven by any great need and is > slow. After about six months of casual working I'm at the stage of > debugging a virtual memory translation table enhancements need to > support 64-bit memory (a new Level-0 table in the page table code in > lpae.h). The means all the assembly code changes required have been > made (and about 12 other areas of change) and I clean compile a from a > log run script. My plans did not include targetting 64 bit implementation as seems to be too big target for amount of time I can devote to it. I just wanted to fix/workaround some problems which I expected to find when dealing with device drivers - not earlier. And only trying to use code available in Genode already (so 32bit for ARMv7). If I correctly understand 32bit instruction set for ARMv8 should be compatible with ARMv7. Am I wrong with this assumption? > For debugging at this level, you really only have two choices: Either > delve into the ARM hardware debugging facilites (CoreSight) or insert > small pieces of code to poke variable values or a trace number into a > currently unused region of memory. Code like: > > using ull = unsigned long long; > ull volatile * debug_ptr = (ull *)0x91000600; > *debug_ptr = MAX_ENTRIES; > debug_ptr += 0x01; > *debug_ptr = BLOCK_SIZE_LOG2; > debug_ptr += 0x01; > > if your booting into uboot to start up, you can inspect the memory > region through uboots' md command. Breakpoints can be implemented with > the assembly code line: asm volatile("hlt #01\n"); . Objdump gives > you the assembly code listing if you need it. Do I correctly understand, that I can go back to u-boot after running Genode with 'hlt #01' and analyze content of memory there? I would be surprised but definitely it would be useful. > I sincerely hope Genode does not implement a version of the Linux > DT. It is an error prone approach developed many years ago in the > embedded world. There are more elegant, syntax checkable, > configuration description approaches available today. Could you give some hints about those alternatives? I have no experience in this area and what seems to be tempting in device tree is that when you look into linux sources there are already dts files for all flavours of RPI including mine. U-boot uses this too - I wanted to use source from this due to smaller amount of code but that probably doesn't matter much. > Let me know if I can help with any compile/link issues you have, I > probably came across most of them in my work to-date. I'm using a > Linaro tool chain for aarch64. There is a separate one for aarch32 > which I don't currently use. Currently my "problem" is that my RPI doesn't pass through marked line in crt0.s /***************************************************** ** Setup multiprocessor-aware kernel stack-pointer ** *****************************************************/ mov sp, #0 /* for boot cpu use id 0 */ --> cps #31 /* change to system mode */ .global _start_setup_stack /* entrypoint for all cpus */ _start_setup_stack: I think it is due to RPI firmware is leaving processor in HYP mode - not SVC. But currently this is all I know. I tried to put code from FOC that is used switch processor back to SVC mode but as I don't understand details of it yet something is not working. There is some similar code in Genode implementation for Arndale board. On the other hand - maybe running in HYP mode is what is better for Genode? Some hints? If I comment out section with 'cps #31' it goes further and I it does not return from 'Bootstrap::Platform & p = Bootstrap::platform();' in 'extern "C" void init()' and last place which I found that is executing is constructor: Bootstrap::Platform::Board::Board in 'repos/base-hw/src/bootstrap/spec/rpi/platform.cc' I'll try to find out more and ask more specific questions about this part. Tomasz Gajewski

4 15

Amateur Radio
by Tyrell Jentink 29 Jan '19

29 Jan '19

1 0

target 'lib/ld/linux' does not exist
by Wouter van Oijen 28 Jan '19

28 Jan '19

Hi, When I try to run a scenario with "KERNEL=nova" on platform "linux", in most cases I get the following error: Error: target 'lib/ld/linux' does not exist Does anybody know what causes this and how I can resolve this error? (NB: I'm currently working with Genode 18.08 on Ubuntu 16.04.10) Kind regards, Wouter van Oijen

2 3

Networking under linux platform
by Chris 28 Jan '19

28 Jan '19

Dear Genodians, I have been successfully playing around with Networking in the 16.XX releases using the linux_x86 platform as a target. My genode instance used to run in a Ubuntu 14.04 LTS VM with a Windows host. Despite the "creative" setup, the tun/tap setup bridged with one of the VM's adapters worked like a charm. After a jump to 18.11, using the linux platform as a target, I am experiencing troubles with the linux_nic_drv: The creation the driver component seems to fail during the creation of the file descriptors for its dataspaces: lx_mmap in _map_local fails with 22 (EINVAL) (see attached console output from the lwip_lx example). I tested under Ubuntu 14.04 LTS in my old build environment as well as on a vanilla 16.04 LTS with a freshly installed genode toolchain & the current master. Other examples, such as the demo scenario, run without any problems. I have found an older discussion on the list from 2014 about failed memory mappings, but the thread ended without coming to a real conclusion. I'd be more than glad for any idea what where to look for possible reasons for this behavior. Best regards, Chris ======= console log, for run/lwip_lx =========== using 'core-linux' as 'core' using 'linux_timer_drv' as 'timer' using 'ld-linux.lib.so' as 'ld.lib.so' spawn ./core Genode 18.11-117-ged65267 <local changes> 17592186044415 MiB RAM and 8998 caps assigned to init [init] parent provides [init] service "ROM" [init] service "IRQ" [init] service "IO_MEM" [init] service "IO_PORT" [init] service "PD" [init] service "RM" [init] service "CPU" [init] service "LOG" [init] child "timer" [init] RAM quota: 776K [init] cap quota: 68 [init] ELF binary: timer [init] priority: 0 [init] provides service Timer [init] child "linux_nic_drv" [init] RAM quota: 3848K [init] cap quota: 68 [init] ELF binary: linux_nic_drv [init] priority: 0 [init] provides service Nic [init] child "test-lwip_httpsrv" [init] RAM quota: 4872K [init] cap quota: 68 [init] ELF binary: test-lwip_httpsrv [init] priority: 0 [init -> linux_nic_drv] Error: _map_local: lx_mmap failed(addr_in=0x0, addr_out=0xffffffffffffffea/-22) overmap=0 [init -> linux_nic_drv] Error: LD: exception during program load: 'Genode::Region_map::Region_conflict' [init -> linux_nic_drv] Error: Uncaught exception of type 'Genode::Region_map::Region_conflict' [init -> linux_nic_drv] Warning: abort called - thread: ep Warning: blocking canceled in entrypoint constructor [init] child "linux_nic_drv" exited with exit value 1 [init -> test-lwip_httpsrv] Error: LD: symbol not found: '_nsyyin' [init -> test-lwip_httpsrv] Error: Uncaught exception of type 'Linker::Not_found' [init -> test-lwip_httpsrv] Warning: abort called - thread: ep [init] child "test-lwip_httpsrv" exited with exit value 1 [init] child "timer" announces service "Timer"

2 1

create_uboot for wand_quad
by Pirmin Duss 24 Jan '19

24 Jan '19

Hello Genodeans I'm currently porting Genode to the Apalis iMX6 board of Toradex. As a starting point I used the wand_quad. Currently I'm able to build run/log for both base-hw and base-sel4. My problem arises when I run tool/create_uboot I get the following error: In file included from /var/cache/genode_contrib/uboot/include/linux/compiler.h:54:0, from /var/cache/genode_contrib/uboot/include/linux/byteorder/little_endian.h:12, from /var/cache/genode_contrib/uboot/arch/arm/include/asm/byteorder.h:29, from /var/cache/genode_contrib/uboot/include/compiler.h:125, from /var/cache/genode_contrib/uboot/include/image.h:19, from /var/cache/genode_contrib/uboot/include/common.h:82: /var/cache/genode_contrib/uboot/include/linux/compiler-gcc.h:114:30: fatal error: linux/compiler-gcc6.h: No such file or directory #include gcc_header(__GNUC__) ^ I have a work around, for compiling Uboot. By using the uboot tree provided by Toradex (see: https://github.com/trimpim/genode/blob/apalis_imx6/tool/create_uboot) the Image is created. Does Martin's uboot tree do some special configuration things? the only change I see is that it adds an empty file. Best regards, Pirmin

2 1

This year's Genode Hack'n'Hike
by Norman Feske 23 Jan '19

23 Jan '19

Hello, there will be another Genode Hack'n'Hike this year! Besides FOSDEM, this annual event is certainly one the Genode highlights of the year. It is a small gathering of around 10 to 20 developers and enthusiasts of Genode and provides a healthy mix of daylight outdoor activities and candlelight hacking activities. The informal character of the Hack'n'Hike presents a great opportunity for newcomers to get acquainted with the people behind Genode. This year, it will take place during May 10 to 13 in Königstein nearby Dresden/Germany. The event is sponsored by Genode Labs. There is no registration fee. If you like to participate, please register by commenting at the corresponding topic on our issue tracker linked below. There you can also find the most up-to-date information about traveling arrangements and the exact location: https://github.com/genodelabs/genode/issues/2841 Cheers Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Error: hammer ABI contains Genode-internal symbol '__bss_start'
by Guido Witmond 18 Jan '19

18 Jan '19

Dear Genodians, I'm back at learning how to do packaging. By following the developer-resources/porting_libraries guide, I ported the Hammer parser combinator library into a Genode port [1]. It builds and runs a simple test. (commit 665e71d). Now I want to make it a depot package. I copied the structure from libports/expat and adapted it. I have a recipes/{api,src}/content.mk (commit XXXXXX) I created the lib/symbols/hammer file by ! tool/abi_symbols bin/hammer.lib.so Then I run the build: ! ~/genode/tool/depot/create guido/bin/x86_64/hammer UPDATE_VERSIONS=1 FORCE=1 KEEP_BUILD_DIR=1 It starts good: ! created guido/api/base/2018-11-23 ! created guido/api/hammer/2019-01-08 ! created guido/api/libc/2018-11-26 ! created guido/src/hammer/2019-01-08-a However, I get this error during the compile of hammer. ! MERGE hammer.lib.so ! Error: hammer ABI contains Genode-internal symbol '__bss_start', ! Error: hammer ABI contains Genode-internal symbol '__eh_frame_start__' all from the symbol_blacklist defined in check_abi. It ends with this error: recipe for target 'hammer.lib.checked' failed So where did I go wrong? (Maybe this is an item for the list of missing documentation). 1: https://github.com/gwitmond/genode-hammer-library

3 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users January 2019