users November 2020

users@lists.genode.org

14 participants
21 discussions

Running Genode on a Raspberry Pi 3
by Simon Himmelbauer 11 Nov '20

11 Nov '20

Hi Genodians, I am trying to get a Genode image using the Fiasco.OC-kernel running on an RPi 3. I created an arm_v8a build directory and accordingly set the KERNEL and BOARD variable. I also compiled a u-boot image from the upstream repository. When I attempt to boot the image from the u-boot prompt, I receive the output below with no further reaction. I am still on Genode 19.05 because of a few modifications so I unless there is no other solution, I would like to avoid upgrading to a newer version. I also tried to run a few L4Re images provided here [0] with the same result, so the problem might not even be specific to Genode. Does anyone else have experiences with running on an RPi 3? Is there anything I am missing here? Best regards, Simon [0] https://l4re.org/download/snapshots/pre-built-images/arm64/ U-Boot 2021.01-rc1-00243-g7a8ac9df5d (Nov 04 2020 - 01:56:08 +0100) DRAM: 948 MiB RPI 3 Model B (0xa22082) MMC: mmc@7e202000: 0, sdhci@7e300000: 1 Loading Environment from FAT... *** Warning - bad CRC, using default environment In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e980000: USB DWC2 scanning bus usb@7e980000 for devices... 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 U-Boot> fatload mmc 0 $loadaddr image.elf 3208480 bytes read in 137 ms (22.3 MiB/s) U-Boot> bootelf ## Starting application at 0x01000000 ^��Z��%��XE��TmyAEDMe�@�*`)5��R[qP�� ?�RQ@��VRY��5� �R A!��y=AA!y5YE)�}AG@A�Ţ�A��ӉR

4 7

Re: Running Genode on a Raspberry Pi 3
by Simon Himmelbauer 10 Nov '20

10 Nov '20

Hi Stefan, > I do not understand what you mean with: "directly launch the image from > the Pi". What did you do in contrast to reading the image from sd-card? > > I wouldn't wonder if the HDMI output keeps blank when booting some > scenario. Or is the image you try to boot known to work interactively > with a graphical user-interface? > Anyway, without having at least a serial line output, it will be > impossible to find potential problems here. sorry, I should have clarified my approach in more detail. With "directly launching", I meant that I simply connected a regular keyboard and HDMI-display so that I don't have to deal with the UART. u-boot successfully launches but booting the image results in the output remaining blank. The reason for this could be missing framebuffer support which the developers at least mentioned in 2014 [0]. > I can remember in the back of my head that there are_two_ UART > devices Pl011 and some SoC specific miniuart. Maybe Fiasco.OC and > u-boot use different once? This is correct, according to the Raspberry documentation [1], this is the reason why "enable_uart=1" is required in the config.txt of the raspberry pi in order to change the PL011 to the primary UART. > If you do not think it is UART-related, you have to inspect whether > the binary you load is correctly copied to the right memory location, > and the bootelf command addresses that same location. I have no clue anymore but I now think that it might actually be UART related as I described in the reply to Tomasz. The fiasco.OC build system compiles the driver for a 16550 instead of the PL011 when using the build configuration for the RPi3. I modified the sources accordingly but the PL011-driver still resulted in garbage output. The load address is definitely fine (I use the default value of the $loadaddr which is 0x200000). > We typically, do not use 'bootelf' in u-boot, but bootm instead. In > that case, you should add '--include image/uboot' to the RUN_OPT > variable in your Genode build environment, e.g., in 'etc/build.conf'. > The resulting uImage will reside in 'var/run/[run-script-name]/uImage' > in your build-directory. Thanks for the tip, I added the command and used the uImage instead but it lead to the same problem of random output on the UART. Does it help you to share one of my compiled Genode images? If yes, should I simply attach them to the mail (~ 1.2 MB in size) or upload them somewhere else? Best regards, Simon [0] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006246.html [1] https://www.raspberrypi.org/documentation/configuration/uart.md

2 1

bringup on RK3399
by Michael Grunditz 10 Nov '20

10 Nov '20

Hi, I am thinking on doing a super quick bringup of base-hw on RK3399 SoC. But obvisually not if someone already do this. So step forward if you do that! The SoC has a GIC500 , but I think it can be used in compat mode. In my first RISC OS effort I simply used the cpu interface (ARM regs).. so I guess that could be done. really simple only a few instructions. THe Boot cpu is A53. Is SoC timers used in Genode or is it ARM timers? It looks like that. The purpose of bringup is: 1) I want to learn the craft 2) I need material to a online talk about bringing up SoCs , and I want to use something that is not pure assembler. Cheers Michael

2 16

partial free/split for ds
by Alexander Tormasov 09 Nov '20

09 Nov '20

I have a physical memory which is used for populated managed dataspace, like Dataspace_capability ds = env.ram().alloc(SIZE); void * base_rw = env.rm().attach(ds); memset(base_rw, 0xff, SIZE); env.rm().detach(base_rw); I use it as backend for mmap and found, that I need to be able to change mapping in the standard way which used for this mmap/munmap interface. Typically, I want to free a part of this ds, e.g., in the middle of it. Like UUUUUU -> UUUFFU (where Used and Free abbreviation used), keeping mapping and content for all old addresses except freed ones, in the «middle» of area [base_rw, base_rw+SIZE) from above. How I can do this? Probably after operation I will have 2 ds instead of original one; Anyway, I do not want to loose the content of old ds during this procedure, and want to get rid of copy of old content to new one. Is it possible to split ds in such a way? From code of Region_map_component::detach I see that I can detach only from the beginning of the region. May be you can point me to the proper example? Sincerely, Alexander

3 5

clear cache
by Michael Grunditz 06 Nov '20

06 Nov '20

Hi I am wondering if there is a "system friendly" way to invalidate caches? I am running self compiling instructions that needs it. Right now (on aarch64 Genode/Linux) I use __internal___clear_cache but that is unbelievable slow. I use genode api to allocate executable ram. Br Michael

2 2

Re: Running Genode on a Raspberry Pi 3
by Simon Himmelbauer 06 Nov '20

06 Nov '20

Hi Stefan, > My first suspicion would be that u-boot and Fiasco.OC are using > different UART settings, e.g., the baudrate might be different. With > which baudrate do you connect to the serial line? I would expect > Fiasco.OC to use 115200. > > You could also try to find the place in Fiasco.OC/bootstrap where the > UART gets configured, and comment out any hardware access there, to > verify/falsify my idea. The UART is already configured properly by > u-boot, so Fiasco.OC should be able to send characters successfully > over serial line. Thanks, I will try this once I have slightly more time. Noteworthy, the UART is indeed configured to 115200. I have also tried to directly launch the image from the Pi to compare the output on a regular HDMI-screen. However, in this case, I receive no output at all after booting the image in uboot so I am not sure whether the source of the error is really the UART. Best regards, Simon On 05.11.20 12:00, users-request(a)lists.genode.org wrote: > Send users mailing list submissions to > users(a)lists.genode.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.genode.org/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request(a)lists.genode.org > > You can reach the person managing the list at > users-owner(a)lists.genode.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of users digest..." > > > Today's Topics: > > 1. Re: Running Genode on a Raspberry Pi 3 (Stefan Kalkowski) > 2. Re: partial free/split for ds (Christian Helmuth) > 3. Re: partial free/split for ds (Alexander Tormasov) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 4 Nov 2020 13:10:40 +0100 > From: Stefan Kalkowski <stefan.kalkowski(a)genode-labs.com> > To: Genode users mailing list <users(a)lists.genode.org> > Subject: Re: Running Genode on a Raspberry Pi 3 > Message-ID: <20201104121040.43fbqvh3yju4mwp3(a)genode-labs.com> > Content-Type: text/plain; charset=utf-8 > > Hello Simon, > > On Wed, Nov 04, 2020 at 11:54:01AM +0100, Simon Himmelbauer wrote: >> Hi Genodians, >> >> I am trying to get a Genode image using the Fiasco.OC-kernel running on an >> RPi 3. I created an arm_v8a build directory and accordingly set the KERNEL >> and BOARD variable. I also compiled a u-boot image from the upstream >> repository. >> >> When I attempt to boot the image from the u-boot prompt, I receive the >> output below with no further reaction. I am still on Genode 19.05 because of >> a few modifications so I unless there is no other solution, I would like to >> avoid upgrading to a newer version. >> >> I also tried to run a few L4Re images provided here [0] with the same >> result, so the problem might not even be specific to Genode. >> >> Does anyone else have experiences with running on an RPi 3? Is there >> anything I am missing here? > My first suspicion would be that u-boot and Fiasco.OC are using > different UART settings, e.g., the baudrate might be different. With > which baudrate do you connect to the serial line? I would expect > Fiasco.OC to use 115200. > > You could also try to find the place in Fiasco.OC/bootstrap where the > UART gets configured, and comment out any hardware access there, to > verify/falsify my idea. The UART is already configured properly by > u-boot, so Fiasco.OC should be able to send characters successfully > over serial line. > > Regards > Stefan > >> Best regards, >> >> Simon >> >> [0] https://l4re.org/download/snapshots/pre-built-images/arm64/ >> >> U-Boot 2021.01-rc1-00243-g7a8ac9df5d (Nov 04 2020 - 01:56:08 +0100) >> >> DRAM: 948 MiB >> RPI 3 Model B (0xa22082) >> MMC: mmc@7e202000: 0, sdhci@7e300000: 1 >> Loading Environment from FAT... *** Warning - bad CRC, using default >> environment >> >> In: serial >> Out: vidconsole >> Err: vidconsole >> Net: No ethernet found. >> starting USB... >> Bus usb@7e980000: USB DWC2 >> scanning bus usb@7e980000 for devices... 3 USB Device(s) found >> scanning usb for storage devices... 0 Storage Device(s) found >> Hit any key to stop autoboot: 0 >> U-Boot> fatload mmc 0 $loadaddr image.elf >> 3208480 bytes read in 137 ms (22.3 MiB/s) >> U-Boot> bootelf >> ## Starting application at 0x01000000 ^��Z��%��XE��TmyAEDMe�@�*`)5��R[qP�� >> ��?�RQ@��VRY��5� �R A!��y=AA!y5YE)�}AG@A�Ţ�A��ӉR >> >> >> _______________________________________________ >> Genode users mailing list >> users(a)lists.genode.org >> https://lists.genode.org/listinfo/users

2 1

Running seoul-disc script
by Parfait Tokponnon 06 Nov '20

06 Nov '20

Hello, I want to boot a guest OS from hard (rather than ram disc and I think the seoul-disc scenario is the best choice to start. When reading the following part of the script, > <config> > <policy label="seoul -> VirtualDisk 0" partition="5" writeable="yes"/> > <policy label="rump_fs -> " partition="4" writeable="yes"/> > </config> > I guess it expect to locate the guest OS boot disk on partition 5, but I cannot figure out what would be placed on partition 4. assuming the script generates the Genode image disk with 3 partitions. How is it supposed to work? Please, find attached the output log as well as the script files I used. -- Parfait T.

2 1

Reporting use-after-free type bugs in Genode.
by Piotr Tworek 05 Nov '20

05 Nov '20

Hello Genodians, I've recently stumbled upon a use-after-free bug in one of the Genode core base classes. I think I have a pretty good understanding of the problem and would like to fill a bug report with my findings. Given the potential security implications of UAF type bugs I'm not sure what it the best course of action here. Should I report this using github issue tracker which AFAIU will result in the report being public? Or is there some other way to report bugs like this? /ptw

2 2

fs_rom closing and re-opening watches
by Pirmin Duss 04 Nov '20

04 Nov '20

Hello Genodians While debugging an error int the watch implementation of lx_fs, I observed, that fs_rom often closes and re-opens the watch handles. Whenever the file is read, the watch is closed and then re-opened. This also happens, when the read was triggered by a watch notification from the file system. Is there a special reason for that? Or is this an oversight? In https://github.com/genodelabs/genode/issues/3897 Norman already stated, that fs_rom will probably undergo a rework to clean up some design issues he has spotted. If this is an oversight, I think it would be best to fix this when the rework is done. Best regards, Pirmin

2 2

SYS_ioperm aarch64
by Michael Grunditz 03 Nov '20

03 Nov '20

Hi! I am trying to bringup Genode/Linux on aarch64. I have ported the syscall*.S files. But many of the SYS_ defines areen't defined, SYS_ioperm for example. I checked with x86_64 and it built. In both x86_64 and aarch64 it isn't defined in toolchain or Genode. In system includes both platforms has a #Ifdef __NR_ etc. But neither of the systems define that. I am all confused! Michael

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users November 2020