users

users@lists.genode.org

2285 discussions

Genode and clang
by Piotr Tworek 13 Nov '20

13 Nov '20

Hello Genodians, A couple of months ago I started wondering how hard would it be to add Genode support to clang. Since I nowadays have bit of extra free time on my hands I decided to give this a try. As one may guess adding support for a new platform to a complex codebase like llvm/clang is a relatively big undertaking so I decided that for the first stage I want to limit the scope of the work a bit. 1. Clang running on already supported "host" platform (in my case Linux) to compile code for Genode on x86_64, x86_32, arm_v7a and arm_v8a architectures. No support for running clang and all the llvm utils on Genode itself. 2. Try to use as many llvm tools as possible (llvm-ar instead of GNU ar, llvm-objcopy instead of GNU objcopy, etc), but don't try to replace GCC toolchain completely if it requires major effort (ex clang integrated as instead of GNU as, ld.lld instead of ld.bfd, etc). 3. Use libstdc++, libsupc++, libgcc instead of respective llvm replacements. With those goals I started hacking and fast forwards those few months I've mostly achieved my goal. I currently have Clang 11.0.0 port able to compile working binaries for all the target architectures when using base-hw and base-linux. Obviously this did require a bunch of changes in Genode codebase itself, but most issues found were relatively simple and generally not specific to clang itself. For example clang is much better at spotting unused variables in the code, see the following PR: https://github.com/genodelabs/genode/pull/3938 When using clang I also managed to stumble upon some code relying on undefined behaviour, which happens to produce different results in clang than it does in GCC, ex: https://github.com/genodelabs/genode/pull/3941 Overall the number of problems encountered was lower than I expected, which I think puts Genode codebase in very positive light. As one may easily guess there is still a lot of code Genode project consists of which I haven't even tried building, yet. The reaason I'm writing this email is to ask if Genode project would be potentially interested in having clang support in the main repo? I know that officialy supporting another compiler might not be an interesting prospect for the project and I won't mind if the answer is no. Its enough for me if generic fixes I make get merged :). If there is an interest in clang support however, I'll be happy to spend a few evenings cleaning up my work and making a few more PRs out of it. If needed I can also push my remaing clang support patches in the existing, slightly chaotic form, to some branch so Genode developers can see how much work having clang support in Genode would entail. /ptw

2 2

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

13 Nov '20

> Hi Simon, > > On 10.11.20 21:12, Simon Himmelbauer wrote: >> config.txt: >> >> enable_uart=1 >> arm_64bit=1 >> init_uart_baud=115200 >> kernel=u-boot.bin >> > does it work with the following line? > > init_uart_clock=3000000 > > I remembered it being mentioned on the mailing list in the past with regard to serial output issues. > > Christian Hi Christian, yeah, I have tried to add this line as well but it didn't make any difference. I followed Tomasz suggestion and set up a Genode 20.08 environment. I used the provided "hello_tutorial" as a test image and unfortunately, I still receive garbage output on the uart, even when changing the Fiasco.OC kernel to the Genode ("hw") kernel. Is there anything else I can try? My next idea would be to compile some older version of u-boot in order to see whether this fixes my problem. Other than that, I don't really know where to look at anymore. Best regards, Simon

1 0

armemu: grabbing file
by Michael Grunditz 13 Nov '20

13 Nov '20

Hi I have started on my arm32 emulator. Since I had problems with calling outside world from assembler, I start with pure c/c++. It is dead slow , but one thing is really promising. The code runs twice as fast on hw than on linux (same cpu) and in hw case the cpu is running on half speed. Now on to my question: I need to get my executable (32 bit binary) into a ds. Do I need to do read() / copy everything in or is there some magic bits I can use? Michael

2 2

Unable to build drivers/timer
by fixed-term.christo.bita＠sojus-software.de 12 Nov '20

12 Nov '20

Hello all, in the Genode OS 20.05 documentation, section "Using the build system/Building components", it says that the timer driver is build with the "make drivers/timer" command. In my case I get the following error "target 'drivers/timer' does not exist" as I tried the second part of the "hello world" lab. May the reason be that there is no "timer" directory, with the corresponding files, in the "os/src/drivers" directory? Best regards, Christo

2 2

Hello from RK3399! (including odd debug messages!)
by Michael Grunditz 11 Nov '20

11 Nov '20

Starting kernel ... xaydzKernel: cpu pool1 Kernel: cpu constructor Kernel: arch_init Kernel: cpu pool1 kernel initialized ROM modules: ROM: [0000000002212000,0000000002212184) config ROM: [000000000249c000,000000000249d000) core_log ROM: [000000000220f000,0000000002211698) hello ROM: [00000000021bd000,00000000021fe278) init ROM: [0000000002108000,00000000021bc570) ld.lib.so ROM: [000000000249a000,000000000249b000) platform_info ROM: [00000000021ff000,000000000220e9c0) timer Genode sculpt-20.08-72-g5be1c793a <local changes> 507 MiB RAM and 64533 caps assigned to init [init -> hello] Hello world from RK3399!

2 2

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users