- Devel - lists.sel4.systems

Public TSC meeting on Fri, 29 Jan
by Gerwin Klein 07 Feb '21

07 Feb '21

The Technical Steering Committee (TSC) of the seL4 Foundation will hold its next public meting on: Fri 29 Jan 2021 15:30-17:00 Sydney time (5:30am in Berlin, 8:30pm in San Francisco). The meeting is by Zoom, and you can register here: https://unsw.zoom.us/meeting/register/tZ0ocO6hrDwiGtTYlzULbKeTK8ybYJyCC7_p Anyone interested can join the meeting and listen to the discussion and request to speak, which will be granted if time permits. Only TSC members can vote. The seL4 code of conduct applies to the meeting [1]. Sorry about the very early time for Europe, but there are no time slots that work for the US, Australia, and Europe at the same time. We are planning to swap between better times for Europe and the US for the next meetings. The TSC is the body that decides on the technical direction of seL4: https://sel4.systems/Foundation/TSC/ The agenda for the meeting so far is: - updates from the TSC chair and committees: - seL4 public Jira - Jira + GitHub sync - reviewers who have joined - more GitHub tests - discussion points: - do we have too many different forums? - bug/issue classification (Jira is now public, we shouldn't call everything a bug) - more in-tree docs - test infrastructure - extend RFC process slightly? (see https://sel4.atlassian.net/browse/RFC-6?focusedCommentId=14886& ) - when/how should Committer/Admin role change for people who have left D61 and had the role based on org membership - endorsement process for training and products - vote on: - Platform Owner proposal - discuss, potentially vote on RFC proposals: - https://sel4.atlassian.net/browse/RFC-4 - https://sel4.atlassian.net/browse/RFC-5 - https://sel4.atlassian.net/browse/RFC-6 This is probably already too much for 90min and we may have to prioritise, but we will see how far we get. If there are other items that I missed or you think should be on the agenda, please let me know. If we can't get to an item this time, we can still schedule another meeting. Cheers, Gerwin (TSC chair) [1]: https://docs.sel4.systems/processes/conduct.html

2 5

Errors while running Virtual Machines on SeL4;
by Jorge Pereira 07 Feb '21

07 Feb '21

Hi all, I’m getting familiar with SeL4 build system and I’ve been running several application examples and also creating my own on top of the kernel using CAmKES. Very good. $ mkdir camkes-project; $ cd camkes-project; $ repo init -u https://github.com/seL4/camkes-manifest.git; $ repo sync; $ ../init-build.sh -DPLATFORM=sabre -DAARCH32=1 -DCAMKES_APP=helloworld -DSIMULATION=1 $ ninja $ ./simulate Again, so far, so good! Several CAmKES examples up and running. Now, I want to run virtual machines on top of it, I’ve seen several posts on internet and even in the official SeL4 website and none of them are working on my side. Can you please give me some pointers to be able to do so? We really want to start using SeL4 in our products with virtual machines, but current documentation is not ideal. I don’t have experience in CMAKE and that might be the real problem 😊. I need your help to ramp up in the SeL4 project! https://docs.sel4.systems/projects/camkes-arm-vm/ repo init -u https://github.com/seL4/camkes-vm-examples-manifest repo sync mkdir build cd build ../init-build.sh -DCAMKES_VM_APP=vm_minimal -DPLATFORM=tk1 When running ../init-build.sh I get the following: “ CMake Error at /home/jorge/hdd/work/projects/vm/Findcamkes-arm-vm.cmake:39 (find_package): By not providing "Findcamkes-vm-images.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "camkes-vm-images", but CMake did not find one. Could not find a package configuration file provided by "camkes-vm-images" with any of the following names: camkes-vm-imagesConfig.cmake camkes-vm-images-config.cmake Add the installation prefix of "camkes-vm-images" to CMAKE_PREFIX_PATH or set "camkes-vm-images_DIR" to a directory containing one of the above files. If "camkes-vm-images" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:19 (camkes_arm_vm_setup_arm_vm_environment) -- Configuring incomplete, errors occurred! See also "/home/jorge/hdd/work/build/CMakeFiles/CMakeOutput.log". “ Best, Jorge

1 0

seek for some help
by abdi mahmud haji 01 Feb '21

01 Feb '21

hi sorry for bothering you but i get some problem with sel4 tutorial when i trying to get starting with "repo init -u https://github.com/SEL4PROJ/sel4-tutorials-manifest" i got down bellow error and how can i fix it pls Traceback (most recent call last): File "/home/sel4/sel4-tutorials-manifest/.repo/repo/main.py", line 56, in <module> from subcmds.version import Version File "/home/sel4/sel4-tutorials-manifest/.repo/repo/subcmds/__init__.py", line s 38, in <module> ['%s' % name]) File "/home/sel4/sel4-tutorials-manifest/.repo/repo/subcmds/upload.py", line 27, in <module> from hooks import RepoHook File "/home/sel4/sel4-tutorials-manifest/.repo/repo/hooks.py", line 472 file=sys.stderr) ^ SyntaxError: invalid syntax tnks

3 2

Fwd: Regarding Ken Thompson's Reflecting on trusting trust...
by Bora Agca 30 Jan '21

30 Jan '21

Hi, i have one question: since the seL4 was written with a C compiler and it is possible that this compiler has an in-built backdoor, how can you still claim, that seL4 is "safe", i.e. non-hackable. Best regards and thanks in advance ___________________________ Bora Agca Diplom Informatiker Oracle Certified Programmer Java SE 6

2 1

Request for Speakers/Collaboration with WASI
by Zach Lym 29 Jan '21

29 Jan '21

I'm a community organizer for WASI <https://wasi.dev/>, a post-POSIX runtime with features that I think make it suitable for SeL4's planned post-POSIX runtime: * Fast and fine grained SFI via WASM. * Fast IPC and capability oriented security via WASM Reference Types <https://github.com/WebAssembly/reference-types/blob/master/proposals/refere…> . * High level interoperability across programming languages via WASI Interface Types <https://hacks.mozilla.org/2019/08/webassembly-interface-types/> and shared garbage collection <https://github.com/WebAssembly/gc/blob/master/proposals/gc/Overview.md>. * Wide range of targets: embedded, TEE, blockchain, browser, server, and (eventually) consumer operating systems. Industry cooperation is happening through the Bytecode Alliance <https://bytecodealliance.org/>, with partners like Red Hat ensuring commercial viability [1 <https://github.com/bytecodealliance/wasmtime/issues/70#issuecomment-4773292…> , 2 <https://github.com/bytecodealliance/wasmtime/issues/71#issuecomment-5180066…>]. Fastly is already using it for their serverless offering <https://www.youtube.com/watch?v=QdWaQOgvd-g>, which can scale to 20K processes/machine with a 35.4 microsecond cold start time. However, I believe the project would benefit *greatly* from the SeL4 community's experience architecting high-performance/high-assurance microkernels, IPC, and capability based security models. SOIL <https://soil-initiative.org/> is an academic effort to foster cross-pollination through biweekly seminars <https://soil-initiative.org/seminar/>. *We are seeking presenters from the SeL4 to better understand your needs and potential areas of collaboration*. Please contact Ross Tate (ross(a)cs.cornell.edu) if you are interested in presenting and jump on our Zulip Channel <https://bytecodealliance.zulipchat.com/> if you have any questions! Thank you, -Zach Lym

1 0

Accessing GPIOs on Raspberry Pi
by Zohra Charania 29 Jan '21

29 Jan '21

Hello All, I am new to seL4. I want to use seL4 in my project. As a starting point, I have compiled seL4 for Raspberry pi 3. As a next step, I have been trying to access GPIOs on Raspberry Pi. I used gpio.h from util_libs/libplatsupport/arch_include/arm/platsupport. I could not find any gpio.c for Rpi3/bcm2837 platform. When I compile the code, I am getting error: undefined reference to `gpio_sys_init'. Is there any support for GPIO access already available for Raspberry Pi? Could you please provide me guidance on how I can work with the Raspberry Pi GPIOs with seL4. Best Regards Zohra

1 0

Re: Cross VM Connectors
by PityTheFool 28 Jan '21

28 Jan '21

I discovered the answer by looking at the optiplex9020 example. Because the tutorial used the old modules, I had not fully integrated the new connector module into my project.

1 0

Re: Ethernet device module for odroidc2
by Todd Carpenter 28 Jan '21

28 Jan '21

I've been following this exchange with some interest, since I also could use an odroidc2 ethernet driver supported by camkes. > From: "Lee, Damon (Data61, Eveleigh)" > The issue is more clear now, the issue lies with the fact that the Ethernet > driver structure layout is different from the expected layout in libethdrivers. Yes, very much so. I had looked at this awhile ago, and the differences seemed daunting. > If aren't in a rush to solve these issues, the team is considering porting over > the AOS Ethernet driver for the C2 over to libethdrivers in the next few days. > Though this would take a few days to do, review, and have it pushed out to > upstream. I would really appreciate a this. Two thumbs up!

1 0

RFC discussion before vote
by Gerwin Klein 27 Jan '21

27 Jan '21

If you have an opinion on any of these RFCs before we vote on them on Fri, please comment on the Jira issue: - Ability to build additional bootloaders inside the seL4 build system https://sel4.atlassian.net/browse/RFC-4 - The seL4 Core Platform https://sel4.atlassian.net/browse/RFC-5 - The seL4 Core https://sel4.atlassian.net/browse/RFC-6 Cheers, Gerwin

1 0

Cross VM Connectors
by ndaughety13＠gmail.com 26 Jan '21

26 Jan '21

**Problem:** In my unsuccessful attempt to complete the cross vm connectors tutorial, [1](https://docs.sel4.systems/Tutorials/camkes-vm-crossvm.html), I discovered [2](https://github.com/seL4/sel4-tutorials/issues/49). I am now trying to use [3](https://github.com/seL4/camkes-vm-examples/tree/master/apps) with the new connection module which I thought would expose the dataport device to the VM but the corresponding device does not exist in */dev*. I have confirmed that the module is loaded with *lsmod* in the guest. The original tutorial uses an executable *dataport_init*, which is called from the *camkes_init* script. I assume that this executable would provide the setup for the dataport, however the executable *dataport_init* is not in the *default_buildroot_rootfs.cpio* (note: *consumes_event_init* and *emits_event_init* do exist in the rootfs archive) or as a project anywhere in the project files to be overlayed. Because I could not find this executable in the arm example, I assumed that the connection module aided in the dataport initialization process. **Questions:** 1. Where and how is the dataport device (*/dev/uio0* in this case) exposed/initialized so that read/write can occur? 2. Is there an up-to-date version of the Cross VM Connectors tutorial for x86? I have limited knowledge on this and I may not even be asking the right questions -- therefore any feed back and responses are welcome, thanks. **References:** [1]: https://docs.sel4.systems/Tutorials/camkes-vm-crossvm.html [2]: https://github.com/seL4/sel4-tutorials/issues/49 [3]: https://github.com/seL4/camkes-vm-examples/tree/master/apps

1 0

Cross VM Connectors
by Nathan Daughety 25 Jan '21

25 Jan '21

To whom it may concern, I am looking at https://github.com/seL4/camkes-vm-examples repo, specifically, vm_cross_connectors. Side note, I am just learning CAmkES and seL4 so my knowledge is limited. Looking at the connection kernel module, it looks like it should be initializing the dataport device in /dev but when I run the example, it does not appear that the device has been exposed (no uio0 in /dev) which is what I thought the module did. I confirmed with lsmod that the connection module (connection.ko) is loaded. What do I need to do to expose /dev/uio0 (or any device name that refers to the dataport)? I am looking at seL4HardwareMMIO but I noticed that the example does not use it. If you could point me in the right direction I would really appreciate it. Thanks, Nathan

1 0

Ethernet device module for odroidc2
by ogosinkem＠gmail.com 22 Jan '21

22 Jan '21

Im having trouble with creating a ethernet driver device module for odroid c2. I have tried to create one based on the examples that exists in "/util_libs/libethdrivers/src/plat" to no avail. Looking at it, it does not seem to call the function to intialise the module. This is also evident when I step through the "find_compatible_driver_module" function in the "/camkes-tool/libsel4camkes/src/io.c" file as it does not go in to the loop that, from my understanding, should cycle through a list of modules in order to select an appropriate one. Any suggestions to what I may be missing or any references that would help point me in the right direction will be much appreciated.

3 2

Re: Rust bindings, was: Re: What do you want from the next seL4 Summit?
by Andrew Warkentin 13 Jan '21

13 Jan '21

On 1/12/21, Jimmy Brush <code(a)jimmah.com> wrote: > > Based on these discussions we have started prototyping a > procedurally-generated native rust seL4 library built from a complete > seL4 IDL specification. > > Once we have built this out we intend to share our learnings and > continue to advocate for changes to seL4 and/or upstream work that > improves the experience for everyone building their own language > bindings or dynamic systems on seL4. > Is there any particular reason why you didn't just port your bindings to feL4? It does use the C bindings underneath (through bindgen), but I don't think that's a big problem, as they don't have much room for memory bugs (and UX/RT is not meant to be a "Rust OS" like Redox and Robigalia; it will just be an OS that has a lot of subsystems written in Rust, but there will still be a lot of third-party C code). It was relatively easy for me to port your old bindings and allocators to my fork of feL4. Here is the UX/RT subproject with the bindings and allocators (rust-bitmap, rust-sel4, and sel4-alloc are forked from Robigalia; the rest is from feL4 except for sel4-slabmalloc): https://gitlab.com/uxrt/core-supervisor/fel4/

1 0

What do you want from the next seL4 Summit?
by Gernot Heiser 12 Jan '21

12 Jan '21

Dear seL4 community, A couple months ago we had a successful 3rd seL4 Summit. Despite having to revert to virtual format, it was a very good event, and I’m sure I’m not the only one who enjoyed it. Thanks for the great work to our friends at IAI, Siege Technologies and the Griffiss Institute for the organisation, and DARPA and AFRL for funding the Summit in particular, and seL4 in general for many years. DARPA funding for the seL4 Summits is coming to an end, and, as you know, the seL4 Foundation has been created as the community-driven guardians of seL4. Among others, this means it is time to think about how future summits will look like. For example, much of the funding for seL4 has come from defence budgets, but the technology is equally important for critical civilian systems, and the Summit should reflect this. We would also like to see broadened community participation, maybe a flavour of FODSEM or LCA, while continuing to involve our corporate partners, who are key to financial support and widespread deployment. So we are asking you, the seL4 developer community, what you would like to see at the next summit, in content and format. After this informal community consultation we expect to issue an EOI for organising the next Summit, anticipated timeframe is similar as in the past, Sep–Nov. Please make/discuss suggestions via reply email within a month (and note that I’ll be off-lline for a fair chunk of this). Gernot PS: For those who have missed it, the Summit presentations are still available for about another month to those registered, see https://www.sel4-us.org/summit2020/

4 4

Ethdriver OdroidC2
by Nkem Ogosi 05 Jan '21

05 Jan '21

I have been trying to get an example sel4 programs that demonstrate a network connection, most notably picoserver, to work on an odroid board. Many resources were referenced such as an eth driver and the types of files I needed to get a camkes implementation to work. However, I haven't been very successful. I don't really understand what I am supposed to be included in some of the files or more importantly where to find the information I need to populate the file specifically for odroid as similar files for other boards have other files as dependecies. Sincerly, Nkem

1 0

seL4 YouTube Channel
by Gernot Heiser 31 Dec '20

31 Dec '20

Dear seL4 community, As some of you have already noticed, we now have a YouTube channel run by the seL4 Foundation: https://www.youtube.com/channel/UCIqVY1XFPOPIZ1z2A9TrmMA/about. It presently has two playlists, one with the recordings of the seL4 material from this year’s UNSW Advanced Operating Systems course, and one with seL4 Summit talks from Trustworthy Systems. More to come, enjoy Gernot

2 2

Debugging seL4 for RISC-V
by porter.188＠osu.edu 23 Dec '20

23 Dec '20

I'm building a simple "hello, world" project and running into some bugs. The code works, but the after execution there is an exception. It appears to be in restore_user_context or nearby. Can anyone point out what the problem could be here? user@user-KVM:/mnt/data/sel4hello_manifest/build$ qemu-system-riscv64 --machine spike --nographic --serial mon:stdio --m size=4095M --bios images/hello-image-riscv-spike bbl loader ELF-loader started on (HART 0) (NODES 1) paddr=[80200000..80312d0f] Looking for DTB in CPIO archive...found at 802e5910. Loaded DTB from 802e5910. paddr=[8401e000..8401efff] ELF-loading image 'kernel' paddr=[84000000..8401dfff] vaddr=[ffffffff84000000..ffffffff8401dfff] virt_entry=ffffffff84000000 ELF-loading image 'hello' paddr=[8401f000..84157fff] vaddr=[10000..148fff] virt_entry=14aa4 Jumping to kernel-image entry point... Init local IRQ Initialing PLIC... Booting all finished, dropped to user space hello, world! Warning: using printf before serial is set up. This only works as your printf is backed by seL4_Debug_PutChar() hrintf is bac Caught cap fault in send phase at address 0 while trying to handle: vm fault on code at address 0 with status 0x1 in thread 0xffffffc17fee8200 "rootserver" at address 0 With stack: 0x143ea0: 0x143ec0 0x143ea8: 0x101ea 0x143eb0: 0x143f00 0x143eb8: 0x14b90 0x143ec0: 0x0 0x143ec8: 0x143f30 0x143ed0: 0x143f20 0x143ed8: 0x143f10 0x143ee0: 0x1 0x143ee8: 0x101d6 0x143ef0: 0x144000 0x143ef8: 0x14cbc 0x143f00: 0x0 0x143f08: 0x14a000 0x143f10: 0x20110 0x143f18: 0x0

1 0

I.MX7, Timeout in SEL4 USB driver
by MOHAMAD REZA SHAFIEI 16 Dec '20

16 Dec '20

Hi there, I'm working on USB Storage in Sel4 on I.MX7, when I read/write some block of data from/to USB Driver , sometimes US‌‌‌B Driver fails with this output by this output: ehci_wait_for_completion@async.c:594 Timeout this error happened in ehci_schedule_xact function that waiting for transaction completion. I port USB Driver on I.MX7 but because of above bug, it isn't Stable. Can anyone help me how to fix this bug? regards, Mohamad -- This email was Anti Virus checked by Security Gateway.

1 0

[Camkes] Access control for memory or the entire component?
by Seo Yeon Hwang 11 Dec '20

11 Dec '20

Hello all, I wonder if it is possible for a component to directly access some specific part of memory with an address or access the whole component (not some dataports) using Camkes. I can see how to set up the permissions (R/W) for each dataport in the tutorial #port_privileges part, but I wonder if one component can read some specific memory region with starting and ending addresses, or read the whole memory where another component is located. Thanks for your help! Best regards, Seoyeon

2 1

CfP: FOSDEM 2021 - Microkernel Devroom
by Martin Decky 08 Dec '20

08 Dec '20

Microkernel Devroom at FOSDEM 2021 CALL FOR PARTICIPATION On-line version of this CfP: http://fosdem.microkernel.info/ The developers and users of several free and open source microkernel-based operating systems will meet on-line as part of FOSDEM 2021 [1] and will share a developer room. The devroom is currently looking for content in the form of talks and activities related to the area of microkernel-based, unikernel-based, component-based operating systems and similar topics. The devroom has been preliminarily scheduled to Saturday February 6th 2021. The devroom will take place during European day hours. Possible topics of the devroom include, but are not limited to: * introduction of a specific OS or framework * design of subsystems and the general architecture of an OS * used languages, tools and toolchains * enabling support for hardware (architectures, device drivers) * enabling support for programming languages * development processes, debugging * maintenance, testing and release engineering * security and robustness * trends and challenges * community and governance * use cases, experiences and status updates * best practices, lessons learned and demos This is a call for your participation. We kindly ask you to submit your proposals no later than on December 26th 2020. Please use the Pentabarf website [2] to submit your proposals. If you already have a user account in Pentabarf, please do not create a new one. Please make sure to select the Microkernel devroom as the track when submitting your talk and include at least the following information in your proposal: * title of your talk * your full name * short abstract of your talk (one or two paragraphs) * duration of your talk (at least 20 minutes and no longer than 50 minutes), excluding a Q&A part * your short bio * your photo The talks will be pre-recorded in advance in January and streamed during the event. This means that you will need to complete and submit your talk by around mid January. However, each speaker should be also present on-line just after the streaming of the talk for a live Q&A. You can specify your prefered time slot of your talk. The communication language of the devroom is English. The official devroom schedule (along with the accepted talks) will be announced on December 31st 2020 on the devroom's mailing list [3] and the speakers will be notified via e-mail. The schedule will also be published on the FOSDEM website. You are also invited to send any other suggestions for what you want to see or do at the devroom to the mailing list. About the Devroom Since the first Microkernel devroom at FOSDEM 2012 [4], this devroom has been part of each following FOSDEM. The focus gradually widened to include component-based and unikernel-based operating systems. By now it has become a somewhat institutionalized tradition for the community to meet there. To this date, over a dozen projects have participated in one way or another. Each of the projects face similar challenges but come up with partially different solutions. Therefore, the goal of the devroom is to bring the various projects together, let them exchange ideas, cross-pollinate and socialize. Extraordinary Circumstances in 2021 Due to the extraordinary mode of organization of FOSDEM 2021 (being an on-line event for the first time), many practical aspects of the devroom are still in the process of determination. For example, the devroom talks will be required to be pre-recorded in January and streamed during the event (with a live Q&A), but the technical details are still sketchy at this moment. The talk videos will be published under Creative Commons license by FOSDEM. By submitting a recorded talk, the speaker agrees to have it made available publicly indefinitively. For organizational purposes, we also need contact information of the speakers of accepted talks. Please check the official CfP page [5] of our devroom regularly. We will keep updating it as new guidelines will be determined by the FOSDEM organizers. Sadly, it will not be possible to arrange our traditional microkernel dinner and other in-person social gatherings in Brussels this time. However, we plan to organize an on-line replacement. The details will be announced later in January. On the other hand, the on-line nature of the devroom allows us to "overflow" to a second day in case we receive a substatial number of quality proposals. About FOSDEM FOSDEM [6] is a two-day event organised by volunteers to promote the widespread use of free and open source software. FOSDEM is widely recognised as one of the best such conferences worldwide. FOSDEM covers a wide spectrum of free and open source software and hardware projects and offers a platform for people to collaborate. To this end, FOSDEM has set up developer rooms (devrooms) where teams can meet and showcase their projects. Devrooms are a place for teams to discuss, hack and publicly present latest directions, lightning talks, news and proposals. Besides developer rooms, FOSDEM also offers main tracks, lightning talks, and in the past instances certification exams and project stands. In recent years, FOSDEM has been hosting more than 5000 developers at the ULB Solbosch campus. Due to the circumstances, FOSDEM 2021 will be organized as an on-line event. Despite this, the participation in FOSDEM is still totally free, although the organisers gratefully accept donations and sponsorship. No registration is necessary, but attendees are expected to follow the FOSDEM's code of conduct [7]. Important Dates Recap * 2020-12-26: Deadline for talk proposal submission * 2020-12-31: Schedule published and speakers notified of acceptance * mid January 2021: Time frame for talk pre-recoding * 2021-02-06: Devroom taking place on-line Contact In case of any questions, comments and suggestions, please do not hesitate to contact the devroom organizers via the devroom's mailing list [3]. The primary organizers of the devroom in 2021 are: * Martin Decky * Jakub Jermar Links [1] https://fosdem.org/2021/ [2] https://penta.fosdem.org/submission/FOSDEM21/ [3] https://lists.fosdem.org/listinfo/microkernel-devroom [4] https://archive.fosdem.org/2012/schedule/track/microkernel_os_devroom.html [5] http://fosdem.microkernel.info/ [6] https://fosdem.org/ [7] https://fosdem.org/2021/practical/conduct/

1 0

More enhancements for general-purpose systems that wouldn't be accepted into seL4?
by Andrew Warkentin 05 Dec '20

05 Dec '20

Am I correct to assume that support for running 32-bit code on a 64-bit kernel using compatibility mode rather than virtualization and support for (presumably limited) direct system calls from VMs, bypassing any user-mode VMM (using something like Xen's trampoline page) wouldn't be accepted into seL4? These are yet more things that I am going to want at some point and can't think of any other way to do them (besides adding them to the kernel) without significant penalties to hardware compatibility (in the case of the 32-bit support; while UX/RT will mostly be focused on 64-bit systems, it will support 32-bit Linux programs in its compatibility layer) or performance (in the case of direct kernel traps from VMs; I am planning to write a dynamic general-purpose hypervisor to go with UX/RT eventually, and adding an extra trap into the VMM on every IPC would likely add a fair bit of overhead).

4 8

whether seL4 support c++ code
by yadong.li 02 Dec '20

02 Dec '20

Hi， I have two questions about whether seL4 support C++: 1. When we create a component, whether the src file of component can be c++ style file like **.cxx, or **.cpp ? I found it will print “camkes.environment.c : undefined reference to run” error when compile 2. If our app code write by c++, how can I use it in seL4 environment as native component？Is there some example ？ Thank you very much.

3 2

repo move from sel4proj to sel4 on github
by Klein, Gerwin (Data61, Kensington NSW) 01 Dec '20

01 Dec '20

As some may have already noticed, we have moved a few repositories from github.com/sel4proj/ to github.com/seL4/ recently, This is part of the hand-over of these repositories to the seL4 foundation. Github will forward all related URLs and git operations etc, so there is nothing really that you need to do, and old manifests and repo collections should continue to work as before. For those who would still like to update their mirrors or own manifests to avoid the redirect, below the list of repos that were moved: sel4-tutorials-manifest polyml seL4-CAmkES-L4v-dockerfiles camkes-arm-vm-manifest sel4webserver-manifest rumprun-sel4-demoapps camkes-vm-linux riscv-pk camkes-arm-vm cakeml_libs rumprun-packages seL4_projects_libs sel4-tutorials global-components camkes-vm-images projects_libs sel4webserver sel4runtime rumprun HOL camkes-vm-apps mcs-examples-manifest mcs-examples picotcp picotcp-bsd Cheers, Gerwin

1 0

Building a simple RISC-V project
by porter.188＠osu.edu 30 Nov '20

30 Nov '20

I am trying to build a simple RISC-V seL4 project. I mean "hello world" simple. I using version 12.0.0. I looked at the documentation here https://docs.sel4.systems/projects/buildsystem/incorporating.html to follow what the project layout is. I also followed this project for x86 v10.0.0. https://github.com/manu88/SeL4_101 I was able rebuild this last one for RISC-V after modifying the CMakeLists.txt to include the proper libraries in my hello project. When I try to use the seL4 12.0.0 kernel there are some configuration differences that I haven't figured out yet. Can anyone shed some light on what the parameters are that need to be set for RISC-V? The verified config in ../kernel/configs/RISCV64_verified.cmake are this, is this all that need set? I suppose these could be modified as necessary. 12 set(KernelSel4Arch "riscv64" CACHE STRING "") 13 set(KernelPlatform "hifive" CACHE STRING "") 14 set(KernelPTLevels "3" CACHE STRING "") 15 set(KernelVerificationBuild ON CACHE BOOL "") 16 set(KernelMaxNumNodes "1" CACHE STRING "") 17 set(KernelOptimisation "-O2" CACHE STRING "") 18 set(KernelRetypeFanOutLimit "256" CACHE STRING "") 19 set(KernelBenchmarks "none" CACHE STRING "") 20 set(KernelDangerousCodeInjection OFF CACHE BOOL "") 21 set(KernelFastpath ON CACHE BOOL "") 22 set(KernelPrinting OFF CACHE BOOL "") 23 set(KernelNumDomains 16 CACHE STRING "") 24 set(KernelMaxNumBootinfoUntypedCap 166 CACHE STRING "") 25 set(KernelRootCNodeSizeBits 19 CACHE STRING "") 26 set(KernelMaxNumBootinfoUntypedCaps 50 CACHE STRING "")

2 1

CAmKes Ethdriver Odroid-C2
by Nkem Ogosi 26 Nov '20

26 Nov '20

Hi all, I'm trying to add an odroid-c2 ethdriver implementation and I'm quite confused bout an error im getting. ERROR:CAmkES:CPP failed: /home/nkem/learningHydra/projects/global-components/components/Ethdriver/Ethdriver.camkes:13:10: fatal error: plat/eth_devices.h: No such file or directory ERROR:CAmkES: #include <plat/eth_devices.h> ERROR:CAmkES: ^~~~~~~~~~~~~~~~~~~~ ERROR:CAmkES:compilation terminated. ERROR:CAmkES: CMake Error at /home/nkem/learningHydra/projects/camkes-tool/camkes.cmake:545 (message): Failed to generate /home/nkem/learningHydra/build/ast.pickle Call Stack (most recent call first): It suggests I'm missing the eth_devices header for the odroid-c2 platform but I think I have added all the necessary files in the correct folders. Is there any way to know exactly what files I need or where to look to debug this issue. Thanks, Nkem

2 1

Re: Quotation
by Chubb, Peter (Data61, Kensington NSW) 24 Nov '20

24 Nov '20

>>>>> "Andrew" == Andrew Warkentin <andreww591(a)gmail.com> writes: Andrew> How are these spammers getting onto the list? Is there some Andrew> kind of configuration issue? The person sending it subscribed then unsubscribed. I've temporarily set all messages to moderated to try to catch any others who are doing this. PeterC -- Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group CSIRO's Data61

1 0

Connectivity of 2 sel4 powered systems
by ogosinkem＠gmail.com 23 Nov '20

23 Nov '20

Hi all, I asked earlier about how to connect the odroid-c2 board via Ethernet and I was wondering what additional files I would need to get a CAmkES implementation of an ethernet driver working for this board. Thanks, Nkem Ogosi

1 0

Possibility of adding a system call origin limit similar to that of OpenBSD?
by Andrew Warkentin 23 Nov '20

23 Nov '20

I am wanting to implement a system call origin limit (akin to that of OpenBSD) in UX/RT. This could probably be accomplished by adding a "set system call range" TCB method that takes the start and end addresses of the range in which system calls will be permitted without interception. Any system call issued from code outside this range would incur a user exception (which would provide all the state required for user code to handle the system call and resume the thread if desired). UX/RT will require all binaries to be dynamically linked with a minimal "libroot" library that will contain an IPC transport layer that will be the only part of the system outside the root server that makes direct system calls. This will make it easier for later versions to retain backwards compatibility. Limiting system call origin should also make certain kinds of attacks more difficult. I am also planning to use the system call origin limit in the Linux compatibility environment in order to distinguish Linux syscalls from seL4 ones, since Linux syscalls will never come from libroot. Each process in the Linux compatibility environment will have a fault handler thread that looks up the syscall and calls the corresponding UX/RT APIs, and will also replace the trap with a call to a jump table if the function containing it is a known syscall wrapper in order to cut down on the number of trips through the kernel. Would it be possible to add something like this to the mainline seL4 tree?

4 7

Proposed future Core Platform extension: hosting other seL4-native OSs
by Demi M. Obenour 23 Nov '20

23 Nov '20

While reading Andrew’s message on syscall origin checking, I realized that UX/RT could potentially replace Linux VMs in Core Platform applications. I imagine that this would require changes to both the Core Platform and UX/RT. Andrew, would you be interested in adding a hosting interface to UX/RT, so that static systems such as the Core Platform can use UX/RT as a Linux VM replacement? UX/RT seems like a fantastic alternative, with both better security and (eventually) better performance. I would imagine that it also would use less memory than a Linux VM. Gernot (and the rest of the seL4 team): would it be possible to support running other seL4-based systems as protection domains in a future version of the Core Platform? Such systems would be opaque from the Core Platform’s perspective, but they might need capabilities that normal protection domains are not provided. Of course, they would not be granted any capabilities that would allow them to violate system security. Yes, I know that one can run seL4 in a VM, but it seems rather wasteful to do so. Sincerely, Demi

3 2

RFC-5: seL4 Core Platform
by Gernot Heiser 23 Nov '20

23 Nov '20

Dear seL4 Community, Those who attended today’s closing session at the seL4 Summit have heard about this, for the rest I’m pleased to announce that we have an RFC out for the seL4 Core Platform, a minimal seL4-based OS for embedded/cyberphysical/IoT applications, see https://sel4.atlassian.net/browse/RFC-5 Feedback welcome. Gernot

6 16

Issues with PR
by Iker Galardi 22 Nov '20

22 Nov '20

Hi! I'm having certain issues with the PR where I propose another way to get the gic cpu id directly from hardware registers instead of guessing like before. First of all, inside CI/Links some errors appear about sel4 webpage links that I haven't touched, how can I solve this? At last, on the PR/Preprocess test failure appears but it's not clear what the problem is and after the compilation test is successful. Thanks for your time. Sincerely, Iker Galardi.

3 4

RCF-6: seL4 Core
by Gernot Heiser 22 Nov '20

22 Nov '20

Dear seL4 Community, There is a second RFC just released, for the seL4 Core, a policy-free runtime and build environment for “plain” seL4, see https://sel4.atlassian.net/browse/RFC-6 Again, we are looking for feedback. Gernot

3 2

QEMU vs Spike on RISC-V Debugging
by Porter, Jeremy 19 Nov '20

19 Nov '20

I've built a simple hello for RISC-V. It runs in Spike as expected. In QEMU it doesn't run. It stops at loading the kernel in elfloader/src/common.c at the lines below: 199 printf("ELF-loading 199\n"); 200 /* Copy the data. */ 201 unpack_elf_to_paddr(elf, dest_paddr); I'd really like to use QEMU/GDB to debug my kernel. Can anyone shed some light on what's happening here? The failed output from QEMU looks like this: user@user-KVM:/mnt/data/femur/build$ qemu-system-riscv64 --machine spike --nographic --bios images/hello-image-riscv-spike bbl loader ELF-loader started on paddr=[80200000..802fb90f] ELF-loading image 'kernel' paddr=[c0000000..c0026fff] vaddr=[ffffffff80000000..ffffffff80026fff] virt_entry=ffffffff80000000 ELF-loading 187 ELF-loading 195 ELF-loading 199 The output from spike is the same but complete: ser@user-KVM:/mnt/data/femur/build$ /mnt/data/rocket-tools/bin/spike images/hello-image-riscv-spike bbl loader ELF-loader started on paddr=[80200000..802fb90f] ELF-loading image 'kernel' paddr=[c0000000..c0026fff] vaddr=[ffffffff80000000..ffffffff80026fff] virt_entry=ffffffff80000000 ELF-loading 187 ELF-loading 195 ELF-loading 199 ELF-loading 203 ELF-loading 211 ELF-loading image 'hello' paddr=[c0027000..c013afff] vaddr=[10000..123fff] virt_entry=10216 ELF-loading 187 ELF-loading 195 ELF-loading 199 ELF-loading 203 ELF-loading 211 Jumping to kernel-image entry point... Booting all finished, dropped to user space hello, world! Warning: using printf before serial is set up. This only works as your printf is backed by seL4_Debug_PutChar() hrintf is bac seL4 root server abort()ed Debug halt syscall from user thread 0xffffffc0bffd8a00 "rootserver" halting...Power off

3 4

Re: [seL4] Simple hello for RISC-V/spike
by Porter, Jeremy 10 Nov '20

10 Nov '20

Answering my own question here--maybe this will help someone else trying to get this kind of setup running. The problem is that there are additional libraries required. The CMakeLists.txt for the hello project looks like this: cmake_minimum_required(VERSION 3.7.2) project(hello C) # create a new C project called 'Hello' add_executable(hello src/main.c) # add files to our project. Paths are relative to this file. target_link_libraries(hello sel4platsupport sel4muslcsys ) # we need to link against the standard C lib for printf # Set this image as the rootserver DeclareRootserver(hello) ---------------------------------- This works for the debug build. For the release build there is a dependency on some debugging for early print functions. I think if those are removed it might work ok.

1 0

Odroid-C2 help
by ogosinkem＠gmail.com 06 Nov '20

06 Nov '20

Hi, Ive been following all the steps at https://www.cse.unsw.edu.au/~cs9242/19/project/linux.shtml and I'm not too clear on how to put a built image on the board. Or even if I've done the whole setup correctly for that matter. Any tips would be appriecated? Thanks, Nkem Ogosi

1 0

How is CMake told to build a given app.
by Chris Koziarz 06 Nov '20

06 Nov '20

I'm setting up a new application (and the libraries coming with it) but I have hard time figuring out the process of building, esp. how CMake knows where to start building from.. By way of example, I'm trying to follow the process of setting up and building sel4test. Setting up the source dir structure: repo init -u https://github.com/seL4/sel4test-manifest.git & repo sync and creating the build dir md build & cd build Are perfectly understandable steps: create source tree that includes the app sources (./projects/sel4test/apps/sel4test-driver/ in this case) kernel (./kernel/) libraries (other subdirs under ./projects/) and misc tools (./tools/) and an extra subdir for build output The third "magic" CMake setup step ../init-build.sh -DPLATFORM=<platform> -DRELEASE=FALSE -DSIMULATION=TRUE enables a simple "ninja" command (without any params) to build an application from the sources at ./projects/sel4test/apps/sel4test-driver/ This is a mystery to me. Where is the target (sel4test-driver) specification in these steps? I looked into init-build.sh and my understanding is the CMake setup must be carried by this command: cmake -G Ninja "$@" -DSEL4_CACHE_DIR="$CACHE_DIR" -C "$project_dir/settings.cmake" "$project_dir" but I cannot figure how said command finds that the application we are trying to build is located in ./projects/sel4test/apps/sel4test-driver/ Now, when I try to setup my own app, how do I tell init-build.sh command where my app is? Thanks for any clarification, Chris

2 1

what does "#include <autoconf.h>" do and how to set the path to include it ?
by Chris Koziarz 05 Nov '20

05 Nov '20

I'm creating a new project that uses existing libraries, e.g. seL4_libs/libsel4utils, a header page_dma.h, because I want to use dma in my IO transfer. When I include header page_dma.h in question, at line 15, <autoconf.h> is pulled in. There are 100s of autoconf.h files (usually auto-generated ones in kernel binaries) and I have no idea which one should be included and how to setup -I option for gcc to include it. Can anyone educate me on it? Thanks very much! Chris ninja output: [1/9] Building C object apps/sel4test-driver/fat32-sel4/CMakeFiles/fat32-sel4.dir/src/interfaces/sel4.c.obj FAILED: apps/sel4test-driver/fat32-sel4/CMakeFiles/fat32-sel4.dir/src/interfaces/sel4.c.obj /usr/bin/ccache /usr/bin/aarch64-linux-gnu-gcc --sysroot=/home/chris/sel4_test/tqma8xqp_build -I/home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/inc -I/home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/config -I/home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/../../../sel4_projects_libs/libsdhcdrivers/include/sdhc -I/home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/../../../util_libs/libplatsupport/include -I/home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/../../../util_libs/libutils/include -Iapps/sel4test-driver/musllibc/build-temp/stage/include -march=armv8-a -D__KERNEL_64__ -g -nostdinc -fno-pic -fno-pie -fno-stack-protector -fno-asynchronous-unwind-tables -ftls-model=local-exec -mstrict-align -std=gnu11 -MD -MT apps/sel4test-driver/fat32-sel4/CMakeFiles/fat32-sel4.dir/src/interfaces/sel4.c.obj -MF apps/sel4test-driver/fat32-sel4/CMakeFiles/fat32-sel4.dir/src/interfaces/sel4.c.obj.d -o apps/sel4test-driver/fat32-sel4/CMakeFiles/fat32-sel4.dir/src/interfaces/sel4.c.obj -c /home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/src/interfaces/sel4.c In file included from /home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/src/interfaces/sel4.c:12: /home/chris/sel4_test/projects/sel4test/apps/fat32-sel4/src/interfaces/../../../../../seL4_libs/libsel4utils/include/sel4utils/page_dma.h:15:10: fatal error: autoconf.h: No such file or directory 15 | #include <autoconf.h>

2 2

raspberry pi 4
by Sachin More 03 Nov '20

03 Nov '20

Hi: Thanks to Nick and Peter. I have made some progress: 1. For the kernel code, used origin/rpi4 branch from https://github.com/nspin/seL4.git 2. Used https://github.com/seL4/camkes.git for the build and replaced the kernel with the one in step 1. 3. There is no bcm2711.dts in origin/rpi4, so got one one from linux. The final version, called rpi4.dts is listed at the end this email. 4. Made changes to add rpi4 as a new platform. However, I am stumped trying to reconcile rpi4.dts and overlay-rpi4.dts. The latter contains a reference to a node /soc/gic400@40041000. The equivalent node in rpi4.dts is /sic/gicv2. But I am getting the following error from init-build.sh when it is trying to create kernel.dtb: /host/VPI/camkes-project/build/kernel/kernel.dtb: ERROR (path_references): /chosen: Reference to non-existent node or label "/soc/gicv2" Any ideas? thanks, Sachin -------------------- rpi4.dts ----------------------------- /dts-v1/; /memreserve/ 0x00000000 0x00001000; / { compatible = "brcm,bcm2835"; model = "BCM2835"; #address-cells = <1>; #size-cells = <1>; aliases { serial0 = &uart0; serial1 = &uart1; }; chosen { stdout-path = "serial0:115200n8"; }; rmem: reserved-memory { #address-cells = <1>; #size-cells = <1>; ranges; cma: linux,cma { compatible = "shared-dma-pool"; size = <0x4000000>; reusable; linux,cma-default; }; }; thermal-zones { cpu_thermal: cpu-thermal { polling-delay-passive = <0>; polling-delay = <1000>; trips { cpu-crit { temperature = <90000>; hysteresis = <0>; type = "critical"; }; }; cooling-maps { }; }; }; soc { compatible = "simple-bus"; #address-cells = <1>; #size-cells = <1>; system_timer: timer@7e003000 { compatible = "brcm,bcm2835-system-timer"; reg = <0x7e003000 0x1000>; interrupts = <1 0>, <1 1>, <1 2>, <1 3>; clock-frequency = <1000000>; }; txp: txp@7e004000 { compatible = "brcm,bcm2835-txp"; reg = <0x7e004000 0x20>; interrupts = <1 11>; }; clocks: cprman@7e101000 { compatible = "brcm,bcm2835-cprman"; #clock-cells = <1>; reg = <0x7e101000 0x2000>; clocks = <&clk_osc>, <&dsi0 0>, <&dsi0 1>, <&dsi0 2>, <&dsi1 0>, <&dsi1 1>, <&dsi1 2>; }; mailbox: mailbox@7e00b880 { compatible = "brcm,bcm2835-mbox"; reg = <0x7e00b880 0x40>; interrupts = <0 1>; #mbox-cells = <0>; }; gpio: gpio@7e200000 { compatible = "brcm,bcm2835-gpio"; reg = <0x7e200000 0xb4>; interrupts = <2 17>, <2 18>, <2 19>, <2 20>; gpio-controller; #gpio-cells = <2>; interrupt-controller; #interrupt-cells = <2>; dpi_gpio0: dpi_gpio0 { brcm,pins = <0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27>; brcm,function = <6>; }; emmc_gpio22: emmc_gpio22 { brcm,pins = <22 23 24 25 26 27>; brcm,function = <7>; }; emmc_gpio34: emmc_gpio34 { brcm,pins = <34 35 36 37 38 39>; brcm,function = <7>; brcm,pull = <0 2 2 2 2 2>; }; emmc_gpio48: emmc_gpio48 { brcm,pins = <48 49 50 51 52 53>; brcm,function = <7>; }; gpclk0_gpio4: gpclk0_gpio4 { brcm,pins = <4>; brcm,function = <4>; }; gpclk1_gpio5: gpclk1_gpio5 { brcm,pins = <5>; brcm,function = <4>; }; gpclk1_gpio42: gpclk1_gpio42 { brcm,pins = <42>; brcm,function = <4>; }; gpclk1_gpio44: gpclk1_gpio44 { brcm,pins = <44>; brcm,function = <4>; }; gpclk2_gpio6: gpclk2_gpio6 { brcm,pins = <6>; brcm,function = <4>; }; gpclk2_gpio43: gpclk2_gpio43 { brcm,pins = <43>; brcm,function = <4>; brcm,pull = <0>; }; i2c0_gpio0: i2c0_gpio0 { brcm,pins = <0 1>; brcm,function = <4>; }; i2c0_gpio28: i2c0_gpio28 { brcm,pins = <28 29>; brcm,function = <4>; }; i2c0_gpio44: i2c0_gpio44 { brcm,pins = <44 45>; brcm,function = <5>; }; i2c1_gpio2: i2c1_gpio2 { brcm,pins = <2 3>; brcm,function = <4>; }; i2c1_gpio44: i2c1_gpio44 { brcm,pins = <44 45>; brcm,function = <6>; }; jtag_gpio22: jtag_gpio22 { brcm,pins = <22 23 24 25 26 27>; brcm,function = <3>; }; pcm_gpio18: pcm_gpio18 { brcm,pins = <18 19 20 21>; brcm,function = <4>; }; pcm_gpio28: pcm_gpio28 { brcm,pins = <28 29 30 31>; brcm,function = <6>; }; sdhost_gpio48: sdhost_gpio48 { brcm,pins = <48 49 50 51 52 53>; brcm,function = <4>; }; spi0_gpio7: spi0_gpio7 { brcm,pins = <7 8 9 10 11>; brcm,function = <4>; }; spi0_gpio35: spi0_gpio35 { brcm,pins = <35 36 37 38 39>; brcm,function = <4>; }; spi1_gpio16: spi1_gpio16 { brcm,pins = <16 17 18 19 20 21>; brcm,function = <3>; }; spi2_gpio40: spi2_gpio40 { brcm,pins = <40 41 42 43 44 45>; brcm,function = <3>; }; uart0_gpio14: uart0_gpio14 { brcm,pins = <14 15>; brcm,function = <4>; }; uart0_ctsrts_gpio16: uart0_ctsrts_gpio16 { brcm,pins = <16 17>; brcm,function = <7>; }; uart0_ctsrts_gpio30: uart0_ctsrts_gpio30 { brcm,pins = <30 31>; brcm,function = <7>; brcm,pull = <2 0>; }; uart0_gpio32: uart0_gpio32 { brcm,pins = <32 33>; brcm,function = <7>; brcm,pull = <0 2>; }; uart0_gpio36: uart0_gpio36 { brcm,pins = <36 37>; brcm,function = <6>; }; uart0_ctsrts_gpio38: uart0_ctsrts_gpio38 { brcm,pins = <38 39>; brcm,function = <6>; }; uart1_gpio14: uart1_gpio14 { brcm,pins = <14 15>; brcm,function = <2>; }; uart1_ctsrts_gpio16: uart1_ctsrts_gpio16 { brcm,pins = <16 17>; brcm,function = <2>; }; uart1_gpio32: uart1_gpio32 { brcm,pins = <32 33>; brcm,function = <2>; }; uart1_ctsrts_gpio30: uart1_ctsrts_gpio30 { brcm,pins = <30 31>; brcm,function = <2>; }; uart1_gpio40: uart1_gpio40 { brcm,pins = <40 41>; brcm,function = <2>; }; uart1_ctsrts_gpio42: uart1_ctsrts_gpio42 { brcm,pins = <42 43>; brcm,function = <2>; }; }; uart0: serial@7e201000 { compatible = "arm,pl011", "arm,primecell"; reg = <0x7e201000 0x200>; interrupts = <2 25>; clocks = <&clocks 19>, <&clocks 20>; clock-names = "uartclk", "apb_pclk"; arm,primecell-periphid = <0x00241011>; }; sdhost: mmc@7e202000 { compatible = "brcm,bcm2835-sdhost"; reg = <0x7e202000 0x100>; interrupts = <2 24>; clocks = <&clocks 20>; status = "disabled"; }; i2s: i2s@7e203000 { compatible = "brcm,bcm2835-i2s"; reg = <0x7e203000 0x24>; clocks = <&clocks 31>; status = "disabled"; }; spi: spi@7e204000 { compatible = "brcm,bcm2835-spi"; reg = <0x7e204000 0x200>; interrupts = <2 22>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; i2c0: i2c@7e205000 { compatible = "brcm,bcm2835-i2c"; reg = <0x7e205000 0x200>; interrupts = <2 21>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; dpi: dpi@7e208000 { compatible = "brcm,bcm2835-dpi"; reg = <0x7e208000 0x8c>; clocks = <&clocks 20>, <&clocks 44>; clock-names = "core", "pixel"; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; dsi0: dsi@7e209000 { compatible = "brcm,bcm2835-dsi0"; reg = <0x7e209000 0x78>; interrupts = <2 4>; #address-cells = <1>; #size-cells = <0>; #clock-cells = <1>; clocks = <&clocks 32>, <&clocks 47>, <&clocks 49>; clock-names = "phy", "escape", "pixel"; clock-output-names = "dsi0_byte", "dsi0_ddr2", "dsi0_ddr"; status = "disabled"; }; aux: aux@7e215000 { compatible = "brcm,bcm2835-aux"; #clock-cells = <1>; reg = <0x7e215000 0x8>; clocks = <&clocks 20>; }; uart1: serial@7e215040 { compatible = "brcm,bcm2835-aux-uart"; reg = <0x7e215040 0x40>; interrupts = <1 29>; clocks = <&aux 0>; status = "disabled"; }; spi1: spi@7e215080 { compatible = "brcm,bcm2835-aux-spi"; reg = <0x7e215080 0x40>; interrupts = <1 29>; clocks = <&aux 1>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; spi2: spi@7e2150c0 { compatible = "brcm,bcm2835-aux-spi"; reg = <0x7e2150c0 0x40>; interrupts = <1 29>; clocks = <&aux 2>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; pwm: pwm@7e20c000 { compatible = "brcm,bcm2835-pwm"; reg = <0x7e20c000 0x28>; clocks = <&clocks 30>; assigned-clocks = <&clocks 30>; assigned-clock-rates = <10000000>; #pwm-cells = <2>; status = "disabled"; }; sdhci: sdhci@7e300000 { compatible = "brcm,bcm2835-sdhci"; reg = <0x7e300000 0x100>; interrupts = <2 30>; clocks = <&clocks 28>; status = "disabled"; }; hvs@7e400000 { compatible = "brcm,bcm2835-hvs"; reg = <0x7e400000 0x6000>; interrupts = <2 1>; }; dsi1: dsi@7e700000 { compatible = "brcm,bcm2835-dsi1"; reg = <0x7e700000 0x8c>; interrupts = <2 12>; #address-cells = <1>; #size-cells = <0>; #clock-cells = <1>; clocks = <&clocks 35>, <&clocks 48>, <&clocks 50>; clock-names = "phy", "escape", "pixel"; clock-output-names = "dsi1_byte", "dsi1_ddr2", "dsi1_ddr"; status = "disabled"; }; i2c1: i2c@7e804000 { compatible = "brcm,bcm2835-i2c"; reg = <0x7e804000 0x1000>; interrupts = <2 21>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; vec: vec@7e806000 { compatible = "brcm,bcm2835-vec"; reg = <0x7e806000 0x1000>; clocks = <&clocks 24>; interrupts = <2 27>; status = "disabled"; }; usb: usb@7e980000 { compatible = "brcm,bcm2835-usb"; reg = <0x7e980000 0x10000>; interrupts = <1 9>; #address-cells = <1>; #size-cells = <0>; clocks = <&clk_usb>; clock-names = "otg"; phys = <&usbphy>; phy-names = "usb2-phy"; }; }; clocks { clk_osc: clk-osc { compatible = "fixed-clock"; #clock-cells = <0>; clock-output-names = "osc"; clock-frequency = <19200000>; }; clk_usb: clk-usb { compatible = "fixed-clock"; #clock-cells = <0>; clock-output-names = "otg"; clock-frequency = <480000000>; }; }; usbphy: phy { compatible = "usb-nop-xceiv"; #phy-cells = <0>; }; }; / { compatible = "brcm,bcm2711"; #address-cells = <2>; #size-cells = <1>; interrupt-parent = <&gicv2>; vc4: gpu { compatible = "brcm,bcm2711-vc5"; status = "disabled"; }; clk_27MHz: clk-27M { #clock-cells = <0>; compatible = "fixed-clock"; clock-frequency = <27000000>; clock-output-names = "27MHz-clock"; }; clk_108MHz: clk-108M { #clock-cells = <0>; compatible = "fixed-clock"; clock-frequency = <108000000>; clock-output-names = "108MHz-clock"; }; soc { ranges = <0x7e000000 0x0 0xfe000000 0x01800000>, <0x7c000000 0x0 0xfc000000 0x02000000>, <0x40000000 0x0 0xff800000 0x00800000>; dma-ranges = <0xc0000000 0x0 0x00000000 0x40000000>; local_intc: local_intc@40000000 { compatible = "brcm,bcm2836-l1-intc"; reg = <0x40000000 0x100>; }; gicv2: interrupt-controller@40041000 { interrupt-controller; #interrupt-cells = <3>; compatible = "arm,gic-400"; reg = <0x40041000 0x1000>, <0x40042000 0x2000>, <0x40044000 0x2000>, <0x40046000 0x2000>; interrupts = <1 9 ((((1 << (4)) - 1) << 8) | 4)>; }; avs_monitor: avs-monitor@7d5d2000 { compatible = "brcm,bcm2711-avs-monitor", "syscon", "simple-mfd"; reg = <0x7d5d2000 0xf00>; thermal: thermal { compatible = "brcm,bcm2711-thermal"; #thermal-sensor-cells = <0>; }; }; dma: dma@7e007000 { compatible = "brcm,bcm2835-dma"; reg = <0x7e007000 0xb00>; interrupts = <0 80 4>, <0 81 4>, <0 82 4>, <0 83 4>, <0 84 4>, <0 85 4>, <0 86 4>, <0 87 4>, <0 87 4>, <0 88 4>, <0 88 4>; interrupt-names = "dma0", "dma1", "dma2", "dma3", "dma4", "dma5", "dma6", "dma7", "dma8", "dma9", "dma10"; #dma-cells = <1>; brcm,dma-channel-mask = <0x07f5>; }; pm: watchdog@7e100000 { compatible = "brcm,bcm2835-pm", "brcm,bcm2835-pm-wdt"; #power-domain-cells = <1>; #reset-cells = <1>; reg = <0x7e100000 0x114>, <0x7e00a000 0x24>, <0x7ec11000 0x20>; clocks = <&clocks 21>, <&clocks 29>, <&clocks 23>, <&clocks 22>; clock-names = "v3d", "peri_image", "h264", "isp"; system-power-controller; }; rng@7e104000 { compatible = "brcm,bcm2711-rng200"; reg = <0x7e104000 0x28>; }; uart2: serial@7e201400 { compatible = "arm,pl011", "arm,primecell"; reg = <0x7e201400 0x200>; interrupts = <0 121 4>; clocks = <&clocks 19>, <&clocks 20>; clock-names = "uartclk", "apb_pclk"; arm,primecell-periphid = <0x00241011>; status = "disabled"; }; uart3: serial@7e201600 { compatible = "arm,pl011", "arm,primecell"; reg = <0x7e201600 0x200>; interrupts = <0 121 4>; clocks = <&clocks 19>, <&clocks 20>; clock-names = "uartclk", "apb_pclk"; arm,primecell-periphid = <0x00241011>; status = "disabled"; }; uart4: serial@7e201800 { compatible = "arm,pl011", "arm,primecell"; reg = <0x7e201800 0x200>; interrupts = <0 121 4>; clocks = <&clocks 19>, <&clocks 20>; clock-names = "uartclk", "apb_pclk"; arm,primecell-periphid = <0x00241011>; status = "disabled"; }; uart5: serial@7e201a00 { compatible = "arm,pl011", "arm,primecell"; reg = <0x7e201a00 0x200>; interrupts = <0 121 4>; clocks = <&clocks 19>, <&clocks 20>; clock-names = "uartclk", "apb_pclk"; arm,primecell-periphid = <0x00241011>; status = "disabled"; }; spi3: spi@7e204600 { compatible = "brcm,bcm2835-spi"; reg = <0x7e204600 0x0200>; interrupts = <0 118 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; spi4: spi@7e204800 { compatible = "brcm,bcm2835-spi"; reg = <0x7e204800 0x0200>; interrupts = <0 118 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; spi5: spi@7e204a00 { compatible = "brcm,bcm2835-spi"; reg = <0x7e204a00 0x0200>; interrupts = <0 118 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; spi6: spi@7e204c00 { compatible = "brcm,bcm2835-spi"; reg = <0x7e204c00 0x0200>; interrupts = <0 118 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; i2c3: i2c@7e205600 { compatible = "brcm,bcm2711-i2c", "brcm,bcm2835-i2c"; reg = <0x7e205600 0x200>; interrupts = <0 117 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; i2c4: i2c@7e205800 { compatible = "brcm,bcm2711-i2c", "brcm,bcm2835-i2c"; reg = <0x7e205800 0x200>; interrupts = <0 117 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; i2c5: i2c@7e205a00 { compatible = "brcm,bcm2711-i2c", "brcm,bcm2835-i2c"; reg = <0x7e205a00 0x200>; interrupts = <0 117 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; i2c6: i2c@7e205c00 { compatible = "brcm,bcm2711-i2c", "brcm,bcm2835-i2c"; reg = <0x7e205c00 0x200>; interrupts = <0 117 4>; clocks = <&clocks 20>; #address-cells = <1>; #size-cells = <0>; status = "disabled"; }; pixelvalve0: pixelvalve@7e206000 { compatible = "brcm,bcm2711-pixelvalve0"; reg = <0x7e206000 0x100>; interrupts = <0 109 4>; status = "disabled"; }; pixelvalve1: pixelvalve@7e207000 { compatible = "brcm,bcm2711-pixelvalve1"; reg = <0x7e207000 0x100>; interrupts = <0 110 4>; status = "disabled"; }; pixelvalve2: pixelvalve@7e20a000 { compatible = "brcm,bcm2711-pixelvalve2"; reg = <0x7e20a000 0x100>; interrupts = <0 101 4>; status = "disabled"; }; pwm1: pwm@7e20c800 { compatible = "brcm,bcm2835-pwm"; reg = <0x7e20c800 0x28>; clocks = <&clocks 30>; assigned-clocks = <&clocks 30>; assigned-clock-rates = <10000000>; #pwm-cells = <2>; status = "disabled"; }; pixelvalve4: pixelvalve@7e216000 { compatible = "brcm,bcm2711-pixelvalve4"; reg = <0x7e216000 0x100>; interrupts = <0 110 4>; status = "disabled"; }; hvs: hvs@7e400000 { compatible = "brcm,bcm2711-hvs"; interrupts = <0 97 4>; }; pixelvalve3: pixelvalve@7ec12000 { compatible = "brcm,bcm2711-pixelvalve3"; reg = <0x7ec12000 0x100>; interrupts = <0 106 4>; status = "disabled"; }; dvp: clock@7ef00000 { compatible = "brcm,brcm2711-dvp"; reg = <0x7ef00000 0x10>; clocks = <&clk_108MHz>; #clock-cells = <1>; #reset-cells = <1>; }; hdmi0: hdmi@7ef00700 { compatible = "brcm,bcm2711-hdmi0"; reg = <0x7ef00700 0x300>, <0x7ef00300 0x200>, <0x7ef00f00 0x80>, <0x7ef00f80 0x80>, <0x7ef01b00 0x200>, <0x7ef01f00 0x400>, <0x7ef00200 0x80>, <0x7ef04300 0x100>, <0x7ef20000 0x100>; reg-names = "hdmi", "dvp", "phy", "rm", "packet", "metadata", "csc", "cec", "hd"; clock-names = "hdmi", "bvb", "audio", "cec"; resets = <&dvp 0>; ddc = <&ddc0>; dmas = <&dma 10>; dma-names = "audio-rx"; status = "disabled"; }; ddc0: i2c@7ef04500 { compatible = "brcm,bcm2711-hdmi-i2c"; reg = <0x7ef04500 0x100>, <0x7ef00b00 0x300>; reg-names = "bsc", "auto-i2c"; clock-frequency = <97500>; status = "disabled"; }; hdmi1: hdmi@7ef05700 { compatible = "brcm,bcm2711-hdmi1"; reg = <0x7ef05700 0x300>, <0x7ef05300 0x200>, <0x7ef05f00 0x80>, <0x7ef05f80 0x80>, <0x7ef06b00 0x200>, <0x7ef06f00 0x400>, <0x7ef00280 0x80>, <0x7ef09300 0x100>, <0x7ef20000 0x100>; reg-names = "hdmi", "dvp", "phy", "rm", "packet", "metadata", "csc", "cec", "hd"; ddc = <&ddc1>; clock-names = "hdmi", "bvb", "audio", "cec"; resets = <&dvp 1>; dmas = <&dma 17>; dma-names = "audio-rx"; status = "disabled"; }; ddc1: i2c@7ef09500 { compatible = "brcm,bcm2711-hdmi-i2c"; reg = <0x7ef09500 0x100>, <0x7ef05b00 0x300>; reg-names = "bsc", "auto-i2c"; clock-frequency = <97500>; status = "disabled"; }; }; emmc2bus: emmc2bus { compatible = "simple-bus"; #address-cells = <2>; #size-cells = <1>; ranges = <0x0 0x7e000000 0x0 0xfe000000 0x01800000>; dma-ranges = <0x0 0xc0000000 0x0 0x00000000 0x40000000>; emmc2: emmc2@7e340000 { compatible = "brcm,bcm2711-emmc2"; reg = <0x0 0x7e340000 0x100>; interrupts = <0 126 4>; clocks = <&clocks 51>; status = "disabled"; }; }; arm-pmu { compatible = "arm,cortex-a72-pmu", "arm,armv8-pmuv3"; interrupts = <0 16 4>, <0 17 4>, <0 18 4>, <0 19 4>; interrupt-affinity = <&cpu0>, <&cpu1>, <&cpu2>, <&cpu3>; }; timer { compatible = "arm,armv8-timer"; interrupts = <1 13 ((((1 << (4)) - 1) << 8) | 8)>, <1 14 ((((1 << (4)) - 1) << 8) | 8)>, <1 11 ((((1 << (4)) - 1) << 8) | 8)>, <1 10 ((((1 << (4)) - 1) << 8) | 8)>; arm,cpu-registers-not-fw-configured; }; cpus: cpus { #address-cells = <1>; #size-cells = <0>; enable-method = "brcm,bcm2836-smp"; cpu0: cpu@0 { device_type = "cpu"; compatible = "arm,cortex-a72"; reg = <0>; enable-method = "spin-table"; cpu-release-addr = <0x0 0x000000d8>; }; cpu1: cpu@1 { device_type = "cpu"; compatible = "arm,cortex-a72"; reg = <1>; enable-method = "spin-table"; cpu-release-addr = <0x0 0x000000e0>; }; cpu2: cpu@2 { device_type = "cpu"; compatible = "arm,cortex-a72"; reg = <2>; enable-method = "spin-table"; cpu-release-addr = <0x0 0x000000e8>; }; cpu3: cpu@3 { device_type = "cpu"; compatible = "arm,cortex-a72"; reg = <3>; enable-method = "spin-table"; cpu-release-addr = <0x0 0x000000f0>; }; }; scb { compatible = "simple-bus"; #address-cells = <2>; #size-cells = <1>; ranges = <0x0 0x7c000000 0x0 0xfc000000 0x03800000>, <0x6 0x00000000 0x6 0x00000000 0x40000000>; pcie0: pcie@7d500000 { compatible = "brcm,bcm2711-pcie"; reg = <0x0 0x7d500000 0x9310>; device_type = "pci"; #address-cells = <3>; #interrupt-cells = <1>; #size-cells = <2>; interrupts = <0 148 4>, <0 148 4>; interrupt-names = "pcie", "msi"; interrupt-map-mask = <0x0 0x0 0x0 0x7>; interrupt-map = <0 0 0 1 &gicv2 0 143 4>; msi-controller; msi-parent = <&pcie0>; ranges = <0x02000000 0x0 0xf8000000 0x6 0x00000000 0x0 0x04000000>; dma-ranges = <0x02000000 0x0 0x00000000 0x0 0x00000000 0x0 0xc0000000>; brcm,enable-ssc; }; genet: ethernet@7d580000 { compatible = "brcm,bcm2711-genet-v5"; reg = <0x0 0x7d580000 0x10000>; #address-cells = <0x1>; #size-cells = <0x1>; interrupts = <0 157 4>, <0 158 4>; status = "disabled"; genet_mdio: mdio@e14 { compatible = "brcm,genet-mdio-v5"; reg = <0xe14 0x8>; reg-names = "mdio"; #address-cells = <0x0>; #size-cells = <0x1>; }; }; }; }; &clk_osc { clock-frequency = <54000000>; }; &clocks { compatible = "brcm,bcm2711-cprman"; }; &cpu_thermal { coefficients = <(-487) 410040>; thermal-sensors = <&thermal>; }; &dsi0 { interrupts = <0 100 4>; }; &dsi1 { interrupts = <0 108 4>; }; &gpio { compatible = "brcm,bcm2711-gpio"; interrupts = <0 113 4>, <0 114 4>, <0 115 4>, <0 116 4>; gpclk0_gpio49: gpclk0_gpio49 { pin-gpclk { pins = "gpio49"; function = "alt1"; bias-disable; }; }; gpclk1_gpio50: gpclk1_gpio50 { pin-gpclk { pins = "gpio50"; function = "alt1"; bias-disable; }; }; gpclk2_gpio51: gpclk2_gpio51 { pin-gpclk { pins = "gpio51"; function = "alt1"; bias-disable; }; }; i2c0_gpio46: i2c0_gpio46 { pin-sda { function = "alt0"; pins = "gpio46"; bias-pull-up; }; pin-scl { function = "alt0"; pins = "gpio47"; bias-disable; }; }; i2c1_gpio46: i2c1_gpio46 { pin-sda { function = "alt1"; pins = "gpio46"; bias-pull-up; }; pin-scl { function = "alt1"; pins = "gpio47"; bias-disable; }; }; i2c3_gpio2: i2c3_gpio2 { pin-sda { function = "alt5"; pins = "gpio2"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio3"; bias-disable; }; }; i2c3_gpio4: i2c3_gpio4 { pin-sda { function = "alt5"; pins = "gpio4"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio5"; bias-disable; }; }; i2c4_gpio6: i2c4_gpio6 { pin-sda { function = "alt5"; pins = "gpio6"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio7"; bias-disable; }; }; i2c4_gpio8: i2c4_gpio8 { pin-sda { function = "alt5"; pins = "gpio8"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio9"; bias-disable; }; }; i2c5_gpio10: i2c5_gpio10 { pin-sda { function = "alt5"; pins = "gpio10"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio11"; bias-disable; }; }; i2c5_gpio12: i2c5_gpio12 { pin-sda { function = "alt5"; pins = "gpio12"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio13"; bias-disable; }; }; i2c6_gpio0: i2c6_gpio0 { pin-sda { function = "alt5"; pins = "gpio0"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio1"; bias-disable; }; }; i2c6_gpio22: i2c6_gpio22 { pin-sda { function = "alt5"; pins = "gpio22"; bias-pull-up; }; pin-scl { function = "alt5"; pins = "gpio23"; bias-disable; }; }; i2c_slave_gpio8: i2c_slave_gpio8 { pins-i2c-slave { pins = "gpio8", "gpio9", "gpio10", "gpio11"; function = "alt3"; }; }; jtag_gpio48: jtag_gpio48 { pins-jtag { pins = "gpio48", "gpio49", "gpio50", "gpio51", "gpio52", "gpio53"; function = "alt4"; }; }; mii_gpio28: mii_gpio28 { pins-mii { pins = "gpio28", "gpio29", "gpio30", "gpio31"; function = "alt4"; }; }; mii_gpio36: mii_gpio36 { pins-mii { pins = "gpio36", "gpio37", "gpio38", "gpio39"; function = "alt5"; }; }; pcm_gpio50: pcm_gpio50 { pins-pcm { pins = "gpio50", "gpio51", "gpio52", "gpio53"; function = "alt2"; }; }; pwm0_0_gpio12: pwm0_0_gpio12 { pin-pwm { pins = "gpio12"; function = "alt0"; bias-disable; }; }; pwm0_0_gpio18: pwm0_0_gpio18 { pin-pwm { pins = "gpio18"; function = "alt5"; bias-disable; }; }; pwm1_0_gpio40: pwm1_0_gpio40 { pin-pwm { pins = "gpio40"; function = "alt0"; bias-disable; }; }; pwm0_1_gpio13: pwm0_1_gpio13 { pin-pwm { pins = "gpio13"; function = "alt0"; bias-disable; }; }; pwm0_1_gpio19: pwm0_1_gpio19 { pin-pwm { pins = "gpio19"; function = "alt5"; bias-disable; }; }; pwm1_1_gpio41: pwm1_1_gpio41 { pin-pwm { pins = "gpio41"; function = "alt0"; bias-disable; }; }; pwm0_1_gpio45: pwm0_1_gpio45 { pin-pwm { pins = "gpio45"; function = "alt0"; bias-disable; }; }; pwm0_0_gpio52: pwm0_0_gpio52 { pin-pwm { pins = "gpio52"; function = "alt1"; bias-disable; }; }; pwm0_1_gpio53: pwm0_1_gpio53 { pin-pwm { pins = "gpio53"; function = "alt1"; bias-disable; }; }; rgmii_gpio35: rgmii_gpio35 { pin-start-stop { pins = "gpio35"; function = "alt4"; }; pin-rx-ok { pins = "gpio36"; function = "alt4"; }; }; rgmii_irq_gpio34: rgmii_irq_gpio34 { pin-irq { pins = "gpio34"; function = "alt5"; }; }; rgmii_irq_gpio39: rgmii_irq_gpio39 { pin-irq { pins = "gpio39"; function = "alt4"; }; }; rgmii_mdio_gpio28: rgmii_mdio_gpio28 { pins-mdio { pins = "gpio28", "gpio29"; function = "alt5"; }; }; rgmii_mdio_gpio37: rgmii_mdio_gpio37 { pins-mdio { pins = "gpio37", "gpio38"; function = "alt4"; }; }; spi0_gpio46: spi0_gpio46 { pins-spi { pins = "gpio46", "gpio47", "gpio48", "gpio49"; function = "alt2"; }; }; spi2_gpio46: spi2_gpio46 { pins-spi { pins = "gpio46", "gpio47", "gpio48", "gpio49", "gpio50"; function = "alt5"; }; }; spi3_gpio0: spi3_gpio0 { pins-spi { pins = "gpio0", "gpio1", "gpio2", "gpio3"; function = "alt3"; }; }; spi4_gpio4: spi4_gpio4 { pins-spi { pins = "gpio4", "gpio5", "gpio6", "gpio7"; function = "alt3"; }; }; spi5_gpio12: spi5_gpio12 { pins-spi { pins = "gpio12", "gpio13", "gpio14", "gpio15"; function = "alt3"; }; }; spi6_gpio18: spi6_gpio18 { pins-spi { pins = "gpio18", "gpio19", "gpio20", "gpio21"; function = "alt3"; }; }; uart2_gpio0: uart2_gpio0 { pin-tx { pins = "gpio0"; function = "alt4"; bias-disable; }; pin-rx { pins = "gpio1"; function = "alt4"; bias-pull-up; }; }; uart2_ctsrts_gpio2: uart2_ctsrts_gpio2 { pin-cts { pins = "gpio2"; function = "alt4"; bias-pull-up; }; pin-rts { pins = "gpio3"; function = "alt4"; bias-disable; }; }; uart3_gpio4: uart3_gpio4 { pin-tx { pins = "gpio4"; function = "alt4"; bias-disable; }; pin-rx { pins = "gpio5"; function = "alt4"; bias-pull-up; }; }; uart3_ctsrts_gpio6: uart3_ctsrts_gpio6 { pin-cts { pins = "gpio6"; function = "alt4"; bias-pull-up; }; pin-rts { pins = "gpio7"; function = "alt4"; bias-disable; }; }; uart4_gpio8: uart4_gpio8 { pin-tx { pins = "gpio8"; function = "alt4"; bias-disable; }; pin-rx { pins = "gpio9"; function = "alt4"; bias-pull-up; }; }; uart4_ctsrts_gpio10: uart4_ctsrts_gpio10 { pin-cts { pins = "gpio10"; function = "alt4"; bias-pull-up; }; pin-rts { pins = "gpio11"; function = "alt4"; bias-disable; }; }; uart5_gpio12: uart5_gpio12 { pin-tx { pins = "gpio12"; function = "alt4"; bias-disable; }; pin-rx { pins = "gpio13"; function = "alt4"; bias-pull-up; }; }; uart5_ctsrts_gpio14: uart5_ctsrts_gpio14 { pin-cts { pins = "gpio14"; function = "alt4"; bias-pull-up; }; pin-rts { pins = "gpio15"; function = "alt4"; bias-disable; }; }; }; &rmem { #address-cells = <2>; }; &cma { alloc-ranges = <0x0 0x00000000 0x40000000>; }; &i2c0 { compatible = "brcm,bcm2711-i2c", "brcm,bcm2835-i2c"; interrupts = <0 117 4>; }; &i2c1 { compatible = "brcm,bcm2711-i2c", "brcm,bcm2835-i2c"; interrupts = <0 117 4>; }; &mailbox { interrupts = <0 33 4>; }; &sdhci { interrupts = <0 126 4>; }; &sdhost { interrupts = <0 120 4>; }; &spi { interrupts = <0 118 4>; }; &spi1 { interrupts = <0 93 4>; }; &spi2 { interrupts = <0 93 4>; }; &system_timer { interrupts = <0 64 4>, <0 65 4>, <0 66 4>, <0 67 4>; }; &txp { interrupts = <0 75 4>; }; &uart0 { interrupts = <0 121 4>; }; &uart1 { interrupts = <0 93 4>; }; &usb { interrupts = <0 73 4>; }; &vec { interrupts = <0 123 4>; }; / { leds { compatible = "gpio-leds"; act { label = "ACT"; default-state = "keep"; linux,default-trigger = "heartbeat"; }; }; soc { firmware: firmware { compatible = "raspberrypi,bcm2835-firmware", "simple-mfd"; #address-cells = <1>; #size-cells = <1>; mboxes = <&mailbox>; dma-ranges; }; power: power { compatible = "raspberrypi,bcm2835-power"; firmware = <&firmware>; #power-domain-cells = <1>; }; vchiq: mailbox@7e00b840 { compatible = "brcm,bcm2835-vchiq"; reg = <0x7e00b840 0x3c>; interrupts = <0 2>; }; }; }; &gpio { pinctrl-names = "default"; gpioout: gpioout { brcm,pins = <6>; brcm,function = <1>; }; alt0: alt0 { brcm,pins = <4 5 7 8 9 10 11>; brcm,function = <4>; }; }; &i2c0 { pinctrl-names = "default"; pinctrl-0 = <&i2c0_gpio0>; status = "okay"; clock-frequency = <100000>; }; &i2c1 { pinctrl-names = "default"; pinctrl-0 = <&i2c1_gpio2>; status = "okay"; clock-frequency = <100000>; }; &usb { power-domains = <&power 6>; }; &vec { power-domains = <&power 7>; status = "okay"; }; &dsi0 { power-domains = <&power 17>; }; &dsi1 { power-domains = <&power 18>; }; &usb { dr_mode = "peripheral"; g-rx-fifo-size = <256>; g-np-tx-fifo-size = <32>; g-tx-fifo-size = <256 256 512 512 512 768 768>; }; / { compatible = "raspberrypi,4-model-b", "brcm,bcm2711"; model = "Raspberry Pi 4 Model B"; chosen { stdout-path = "serial1:115200n8"; }; memory@0 { device_type = "memory"; reg = <0 0 0>; }; aliases { emmc2bus = &emmc2bus; ethernet0 = &genet; pcie0 = &pcie0; }; leds { act { gpios = <&gpio 42 0>; }; pwr { label = "PWR"; gpios = <&expgpio 2 1>; default-state = "keep"; linux,default-trigger = "default-on"; }; }; wifi_pwrseq: wifi-pwrseq { compatible = "mmc-pwrseq-simple"; reset-gpios = <&expgpio 1 1>; }; sd_io_1v8_reg: sd_io_1v8_reg { compatible = "regulator-gpio"; regulator-name = "vdd-sd-io"; regulator-min-microvolt = <1800000>; regulator-max-microvolt = <3300000>; regulator-boot-on; regulator-always-on; regulator-settling-time-us = <5000>; gpios = <&expgpio 4 0>; states = <1800000 0x1 3300000 0x0>; status = "okay"; }; sd_vcc_reg: sd_vcc_reg { compatible = "regulator-fixed"; regulator-name = "vcc-sd"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-boot-on; enable-active-high; gpio = <&expgpio 6 0>; }; }; &ddc0 { status = "okay"; }; &ddc1 { status = "okay"; }; &firmware { firmware_clocks: clocks { compatible = "raspberrypi,firmware-clocks"; #clock-cells = <1>; }; expgpio: gpio { compatible = "raspberrypi,firmware-gpio"; gpio-controller; #gpio-cells = <2>; gpio-line-names = "BT_ON", "WL_ON", "PWR_LED_OFF", "GLOBAL_RESET", "VDD_SD_IO_SEL", "CAM_GPIO", "SD_PWR_ON", ""; status = "okay"; }; reset: reset { compatible = "raspberrypi,firmware-reset"; #reset-cells = <1>; }; }; &gpio { gpio-line-names = "ID_SDA", "ID_SCL", "SDA1", "SCL1", "GPIO_GCLK", "GPIO5", "GPIO6", "SPI_CE1_N", "SPI_CE0_N", "SPI_MISO", "SPI_MOSI", "SPI_SCLK", "GPIO12", "GPIO13", "TXD1", "RXD1", "GPIO16", "GPIO17", "GPIO18", "GPIO19", "GPIO20", "GPIO21", "GPIO22", "GPIO23", "GPIO24", "GPIO25", "GPIO26", "GPIO27", "RGMII_MDIO", "RGMIO_MDC", "CTS0", "RTS0", "TXD0", "RXD0", "SD1_CLK", "SD1_CMD", "SD1_DATA0", "SD1_DATA1", "SD1_DATA2", "SD1_DATA3", "PWM0_MISO", "PWM1_MOSI", "STATUS_LED_G_CLK", "SPIFLASH_CE_N", "SDA0", "SCL0", "RGMII_RXCLK", "RGMII_RXCTL", "RGMII_RXD0", "RGMII_RXD1", "RGMII_RXD2", "RGMII_RXD3", "RGMII_TXCLK", "RGMII_TXCTL", "RGMII_TXD0", "RGMII_TXD1", "RGMII_TXD2", "RGMII_TXD3"; }; &hdmi0 { clocks = <&firmware_clocks 13>, <&firmware_clocks 14>, <&dvp 0>, <&clk_27MHz>; clock-names = "hdmi", "bvb", "audio", "cec"; status = "okay"; }; &hdmi1 { clocks = <&firmware_clocks 13>, <&firmware_clocks 14>, <&dvp 1>, <&clk_27MHz>; clock-names = "hdmi", "bvb", "audio", "cec"; status = "okay"; }; &hvs { clocks = <&firmware_clocks 4>; }; &pixelvalve0 { status = "okay"; }; &pixelvalve1 { status = "okay"; }; &pixelvalve2 { status = "okay"; }; &pixelvalve4 { status = "okay"; }; &pwm1 { pinctrl-names = "default"; pinctrl-0 = <&pwm1_0_gpio40 &pwm1_1_gpio41>; status = "okay"; }; &sdhci { #address-cells = <1>; #size-cells = <0>; pinctrl-names = "default"; pinctrl-0 = <&emmc_gpio34>; bus-width = <4>; non-removable; mmc-pwrseq = <&wifi_pwrseq>; status = "okay"; brcmf: wifi@1 { reg = <1>; compatible = "brcm,bcm4329-fmac"; }; }; &emmc2 { vqmmc-supply = <&sd_io_1v8_reg>; vmmc-supply = <&sd_vcc_reg>; broken-cd; status = "okay"; }; &genet { phy-handle = <&phy1>; phy-mode = "rgmii-rxid"; status = "okay"; }; &genet_mdio { phy1: ethernet-phy@1 { reg = <0x1>; }; }; &pcie0 { pci@1,0 { #address-cells = <3>; #size-cells = <2>; ranges; reg = <0 0 0 0 0>; usb@1,0 { reg = <0x10000 0 0 0 0>; resets = <&reset 0>; }; }; }; &uart0 { pinctrl-names = "default"; pinctrl-0 = <&uart0_ctsrts_gpio30 &uart0_gpio32>; uart-has-rtscts; status = "okay"; bluetooth { compatible = "brcm,bcm43438-bt"; max-speed = <2000000>; shutdown-gpios = <&expgpio 0 0>; }; }; &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_gpio14>; status = "okay"; }; &vchiq { interrupts = <0 34 4>; }; &vc4 { status = "okay"; }; &vec { status = "disabled"; };

3 5

Odroid-C2 help
by ogosinkem＠gmail.com 02 Nov '20

02 Nov '20

Hi, I was wondering if there were any verbose guides that explain how to setup an odroid c2 board to run sel4. As a side note, are there any tools that i could use to simulate this board if need be? Thanks, Nkem Ogosi

1 0

Simple hello for RISC-V/spike
by Porter, Jeremy 02 Nov '20

02 Nov '20

I'm trying to build a simple hello world project for RISC-V/spike. I've been through the tutorials and through the sel4test for RISC-V/spike. That project is too large for what I need. I tried following this: https://github.com/manu88/SeL4_101 and modified the CMakeLists.txt to configure as required: ### SeL4_101 CMakeLists.txt ### cmake_minimum_required(VERSION 3.7.2) #message(STATUS "Femur print " ${KernelX86Sel4Arch_all_strings}) #if (${PLATFORM} IN_LIST KernelRiscVSel4Arch_all_strings) if (${PLATFORM} IN_LIST KernelRiscVPlatform_all_strings) #if (${PLATFORM} IN_LIST ${KernelX86Sel4Arch_all_strings} ${KernelARMPlatform_all_strings} ${KernelRiscVPlatform_all_strings}) set(KernelArch riscv CACHE STRING "" FORCE) set(KernelRiscVSel4Arch riscv64 CACHE STRING "" FORCE) endif() include(tools/cmake-tool/default-CMakeLists.txt) if(SIMULATION) ApplyCommonSimulationSettings("riscv64") else() if(KernelArchX86) set(KernelIOMMU ON CACHE BOOL "" FORCE) endif() endif() # We must build the debug kernel because the tutorials rely on seL4_DebugPutChar # and they don't initialize a platsupport driver. ApplyCommonReleaseVerificationSettings(FALSE FALSE) GenerateSimulateScript() ############################################################################## When I build, I get the following error: user@user-KVM:/mnt/data/femur/build$ ninja [55/90] Building C object projects/util_libs/libplatsupport/CMakeFiles/platsupport.dir/src/plat/spike/serial.c.obj ../projects/util_libs/libplatsupport/src/plat/spike/serial.c:18:28: warning: 'struct dev_defn' declared inside parameter list will not be visible outside of this definition or declaration int uart_init(const struct dev_defn* defn, ^~~~~~~~ [73/90] Linking C executable projects/hello/hello FAILED: projects/hello/hello : && ccache /mnt/data/rocket-tools/bin/riscv64-unknown-elf-gcc --sysroot=/mnt/data/femur/build -march=rv64imac -mabi=lp64 -D__KERNEL_64__ -g -D__KERNEL_64__ -static -nostdlib -z max-page-size=0x1000 -u _sel4_start -e _sel4_start -T /mnt/data/femur/tools/cmake-tool/tls_rootserver.lds /mnt/data/femur/build/lib/crt1.o /mnt/data/femur/build/lib/crti.o /mnt/data/rocket-tools/lib/gcc/riscv64-unknown-elf/7.2.0/rv64imac/lp64/crtbegin.o projects/hello/CMakeFiles/hello.dir/src/main.c.obj -lgcc projects/seL4_libs/libsel4muslcsys/libsel4muslcsys.a projects/seL4_libs/libsel4utils/libsel4utils.a projects/util_libs/libcpio/libcpio.a projects/seL4_libs/libsel4platsupport/libsel4platsupport.a projects/util_libs/libplatsupport/libplatsupport.a projects/seL4_libs/libsel4simple-default/libsel4simple-default.a projects/seL4_libs/libsel4vspace/libsel4vspace.a projects/seL4_libs/libsel4simple/libsel4simple.a projects/seL4_libs/libsel4vka/libsel4vka.a projects/seL4_libs/libsel4debug/libsel4debug.a libsel4/libsel4.a projects/util_libs/libutils/libutils.a projects/util_libs/libelf/libelf.a projects/musllibc/build-temp/lib/libc.a -lgcc projects/seL4_libs/libsel4muslcsys/libsel4muslcsys.a projects/seL4_libs/libsel4utils/libsel4utils.a projects/util_libs/libcpio/libcpio.a projects/seL4_libs/libsel4platsupport/libsel4platsupport.a projects/util_libs/libplatsupport/libplatsupport.a projects/seL4_libs/libsel4simple-default/libsel4simple-default.a projects/seL4_libs/libsel4vspace/libsel4vspace.a projects/seL4_libs/libsel4simple/libsel4simple.a projects/seL4_libs/libsel4vka/libsel4vka.a projects/seL4_libs/libsel4debug/libsel4debug.a libsel4/libsel4.a projects/util_libs/libutils/libutils.a projects/util_libs/libelf/libelf.a projects/musllibc/build-temp/lib/libc.a /mnt/data/rocket-tools/lib/gcc/riscv64-unknown-elf/7.2.0/rv64imac/lp64/crtend.o /mnt/data/femur/build/lib/crtn.o -o projects/hello/hello && : /mnt/data/rocket-tools/lib/gcc/riscv64-unknown-elf/7.2.0/../../../../riscv64-unknown-elf/bin/ld: projects/seL4_libs/libsel4platsupport/libsel4platsupport.a(common.c.obj): in function `vspace_map_pages': /mnt/data/femur/build/../projects/seL4_libs/libsel4vspace/include/vspace/vspace.h:492: undefined reference to `__ctzdi2' /mnt/data/rocket-tools/lib/gcc/riscv64-unknown-elf/7.2.0/../../../../riscv64-unknown-elf/bin/ld: projects/seL4_libs/libsel4platsupport/libsel4platsupport.a(common.c.obj): in function `platsupport_alloc_device_vaddr': /mnt/data/femur/build/../projects/seL4_libs/libsel4platsupport/src/common.c:83: undefined reference to `__ctzdi2' collect2: error: ld returned 1 exit status ninja: build stopped: subcommand failed. The missing symbol is in fact in the build, it shows up in kernel_all_pp.c etc. user@user-KVM:/mnt/data/femur/build$ grep -r ctzdi2 kernel/kernel_all_pp.c:uint32_t __ctzdi2(uint64_t x); kernel/kernel_all_pp.c:uint32_t __ctzdi2(uint64_t x) kernel/kernel_all_copy.c:uint32_t __ctzdi2(uint64_t x) kernel/kernel_all.i:uint32_t __ctzdi2(uint64_t x); kernel/kernel_all.i:uint32_t __ctzdi2(uint64_t x) Binary file kernel/kernel.elf matches kernel/kernel_all_pp_prune_wrapper_temp.c:uint32_t __ctzdi2(uint64_t x) kernel/CMakeFiles/kernel_i_wrapper_temp_lib.dir/kernel_all_copy.c.obj:uint32_t __ctzdi2(uint64_t x); kernel/CMakeFiles/kernel_i_wrapper_temp_lib.dir/kernel_all_copy.c.obj:uint32_t __ctzdi2(uint64_t x) Binary file kernel/CMakeFiles/kernel.elf.dir/kernel_all.i.obj matches kernel/CMakeFiles/kernel_all_pp_prune_wrapper_temp_lib.dir/kernel_all_pp_prune_wrapper_temp.c.obj:uint32_t __ctzdi2(uint64_t x); kernel/CMakeFiles/kernel_all_pp_prune_wrapper_temp_lib.dir/kernel_all_pp_prune_wrapper_temp.c.obj:uint32_t __ctzdi2(uint64_t x) kernel/kernel_all.c:uint32_t __ctzdi2(uint64_t x) kernel/kernel_all_pp_prune.c:uint32_t __ctzdi2(uint64_t x); kernel/kernel_all_pp_prune.c:uint32_t __ctzdi2(uint64_t x) Binary file projects/seL4_libs/libsel4utils/CMakeFiles/sel4utils.dir/src/irq_server/irq_server.c.obj matches Binary file projects/seL4_libs/libsel4utils/libsel4utils.a matches Binary file projects/seL4_libs/libsel4platsupport/libsel4platsupport.a matches Binary file projects/seL4_libs/libsel4platsupport/CMakeFiles/sel4platsupport.dir/src/common.c.obj matches What am I missing here?

1 0

Docker / gnat
by dave＠synergy.org 01 Nov '20

01 Nov '20

Hello, I converted over from my old development environment to the docker-based version this weekend. Everything worked fine, except for one thing. I was using the gnat-6-aarch64-linux-gnu and gnat-6-arm-linux-gnueabihf packages to compile Ada code. Ada is not installed by default in the docker container. I can install it, but it goes away when the container terminates. I am brand new to docker. Can I make these changes permanent myself or does it require the container provider to do so? Thanks! Dave

2 2

raspberry pi 4
by Sachin More 31 Oct '20

31 Oct '20

Hi: Has anyone tried to use seL4 on a raspberry pi 4? thanks, Sachin

4 7

Re: [seL4] Devel Digest, Vol 77, Issue 11
by Chris Koziarz 29 Oct '20

29 Oct '20

Thanks Damon for your help! I've added the required "simple" attribute to the assembly configuration: assembly { composition { [...] component Client client; } configuration { [....] client.simple = true; } } But the usage generates: implicit declaration of function ‘camkes_make_simple’ and I don't know what header(s) I should include and/or any library I should link to get ‘camkes_make_simple’ decl/def. camkes_make_simple() function does not exist in any of simple camkes tutorials to figure out the required headers, while your example has too many headers to figure out what headers are really needed. Further help with it is greatly appreciated. Thanks. Chris On Thu, Oct 29, 2020 at 4:36 PM <devel-request(a)sel4.systems> wrote: > Send Devel mailing list submissions to > devel(a)sel4.systems > > To subscribe or unsubscribe via the World Wide Web, visit > https://sel4.systems/lists/listinfo/devel > or, via email, send a message with subject or body 'help' to > devel-request(a)sel4.systems > > You can reach the person managing the list at > devel-owner(a)sel4.systems > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Devel digest..." > > > Today's Topics: > > 1. seL4_BootInfo in Camkes environment (Chris Koziarz) > 2. Re: seL4_BootInfo in Camkes environment > (Lee, Damon (Data61, Kensington NSW)) > 3. Re: raspberry pi 4 (Jose A. Pascual) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Oct 2020 13:39:12 +1100 > From: Chris Koziarz <chris(a)breakawayconsulting.com.au> > To: devel(a)sel4.systems > Subject: [seL4] seL4_BootInfo in Camkes environment > Message-ID: > <CAMuEnL6VH8xYxK9SR64Sc65onK7By= > 66XkiPHhgMzu4rjDgnRg(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > In a regular seL4 PD, I always have seL4_BootInfo available > via platsupport_get_bootinfo(), and all goodies that I can learn from > therein are available. > > But it appears that the camkes components (probably we should talk about > "client components", i.e. the ones with "control;" attribute and an entry > point: int run(void)), > are started as a typical root task, with a call: > void __sel4_start_root(seL4_BootInfo *boot_info) > however boot_info is passed herein as NULL. > At least boot_info appears NULL for me on ARM64. > So, is the access to seL4_BootInfo disallowed in camkes env? Or how can I > access seL4_BootInfo in camkes? > > Chris > > > ------------------------------ > > Message: 2 > Date: Thu, 29 Oct 2020 04:28:56 +0000 > From: "Lee, Damon (Data61, Kensington NSW)" > <Damon.Lee(a)data61.csiro.au> > To: "devel(a)sel4.systems" <devel(a)sel4.systems> > Subject: Re: [seL4] seL4_BootInfo in Camkes environment > Message-ID: <tfbft5x4pve.fsf(a)coopers.keg.data61.csiro.au> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Chris, > > > In a regular seL4 PD, I always have seL4_BootInfo available > > via platsupport_get_bootinfo(), and all goodies that I can learn > > from > > therein are available. > > > > But it appears that the camkes components (probably we should > > talk about > > "client components", i.e. the ones with "control;" attribute and > > an entry > > point: int run(void)), > > are started as a typical root task, with a call: > > void __sel4_start_root(seL4_BootInfo *boot_info) > > however boot_info is passed herein as NULL. > > At least boot_info appears NULL for me on ARM64. > > So, is the access to seL4_BootInfo disallowed in camkes env? Or > > how can I > > access seL4_BootInfo in camkes? > > The bootinfo isn't disallowed in a CAmkES environment but parts of > it > is gutted out (untyped information, IRQ control cap etc.) > depending on > the configuration of the CAmkES application. To access the > bootinfo, > you could append this configuration option for a specific > component in > the "configuration" block in the ".camkes" file of your > application: > > <component_name>.simple = true; > > The simple_t interface which abstracts the bootinfo can then be > grabbed via the 'camkes_make_simple()' function. > > There are examples of the bootinfo usage in our CAmkES VM > repositories > that you can checkout here: > > https://github.com/seL4/camkes-vm/blob/master/components/VM_Arm/src/main.c#… > > Regards, > Damon > > > ------------------------------ > > Message: 3 > Date: Thu, 29 Oct 2020 06:45:16 +0100 > From: "Jose A. Pascual" <joseantonio.pascual(a)ehu.eus> > To: Nick Spinale <Nick.Spinale(a)arm.com> > Cc: Sachin More <sachinsureshmore(a)gmail.com>, "devel(a)sel4.systems" > <devel(a)sel4.systems> > Subject: Re: [seL4] raspberry pi 4 > Message-ID: > <CAK8ti4+QiFTDnBKRfZYWQ-XXAT_= > MnTr_+jHJRfmwZQ-w6W6NA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi, > We are also running seL4 on the RPI4 and we managed to run "sel4test" > passing all the tests. > Basically, you can build the sel4test project and execute all the tests > without errors as in the Rpi3. > We are using it in an OS course to build a very simple OS on top of seL4. > I'll try to open a PR in the following days. > Nick, if you don't mind, I'll compare our patch with yours to check if we > are doing everything the same way. > I'll keep you informed. > > Jose (& Mikel) > > > On Thu, Oct 29, 2020 at 1:29 AM Nick Spinale <Nick.Spinale(a)arm.com> wrote: > > > > Can I prepare, say seL4 11.0 and then apply your patches and then > > compile using seL4's build system (or your build system if it is in > public > > domain)? > > > > At the moment, I?m unable to share the rest of the code for this > > particular project. I have, however, published our Raspberry Pi 4-related > > patches to public branches of 'seL4' [1] and ?seL4_tools' [2]. These > > patches, which are the extent of our Raspberry Pi 4-related patches for > > upstream seL4 repositories, only encompasses the bootloader (?elfloader?) > > and the seL4 kernel itself. The projects that you might use for getting > > started, such as ?sel4test? [3], depend on platform support for userland > > libraries such as those found in ?seL4_libs? [4]. > > > > If you decide to add Raspberry Pi 4 support to those userland libraries, > > I?d be happy to help out with that. > > > > > > [1] https://github.com/nspin/seL4/tree/rpi4 > > [2] https://github.com/nspin/seL4_tools/tree/rpi4 > > [3] https://github.com/seL4/sel4test-manifest > > [4] https://github.com/seL4/seL4_libs > > > > > > - - - - > > Nick Spinale (nickspinale.com) > > Arm Research, Cambridge UK > > - - - - > > > > IMPORTANT NOTICE: The contents of this email and any attachments are > > confidential and may also be privileged. If you are not the intended > > recipient, please notify the sender immediately and do not disclose the > > contents to any other person, use it for any purpose, or store or copy > the > > information in any medium. Thank you. > > _______________________________________________ > > Devel mailing list > > Devel(a)sel4.systems > > https://sel4.systems/lists/listinfo/devel > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Devel mailing list > Devel(a)sel4.systems > https://sel4.systems/lists/listinfo/devel > > > ------------------------------ > > End of Devel Digest, Vol 77, Issue 11 > ************************************* >

2 2

seL4_BootInfo in Camkes environment
by Chris Koziarz 29 Oct '20

29 Oct '20

In a regular seL4 PD, I always have seL4_BootInfo available via platsupport_get_bootinfo(), and all goodies that I can learn from therein are available. But it appears that the camkes components (probably we should talk about "client components", i.e. the ones with "control;" attribute and an entry point: int run(void)), are started as a typical root task, with a call: void __sel4_start_root(seL4_BootInfo *boot_info) however boot_info is passed herein as NULL. At least boot_info appears NULL for me on ARM64. So, is the access to seL4_BootInfo disallowed in camkes env? Or how can I access seL4_BootInfo in camkes? Chris

2 1

seL4 on gem5
by Bodun Hu 28 Oct '20

28 Oct '20

Hello, I'm currently trying to set up seL4 inside the gem5 simulator to get some benchmark results. Are there any tutorials or instructions regarding how to set it up? Any tip will be appreciated! *Edward Hu* The University of Texas at Austin | Computer Science | Homepage: https:// <http://goog_1605193962>bodunhu.com

2 1

Adding a library to the camkes project
by Chris Koziarz 28 Oct '20

28 Oct '20

Camkes CMakefiles are quite different to the non-camkes ones that I've learned recently. For starters, I cannot figure out a simple step of adding an include path & a static library to a camkes project. For example, I want to expand projects/camkes/apps to include an extra file that calls functions from libsel4vka. Adding a source file is easy: just expand SOURCES list, e.g.: DeclareCAmkESComponent(Driver SOURCES components/Driver/src/driver.c components/Driver/src/sel4vka-caller.c) But sel4vka-caller.c needs the include paths to seL4_libs/libsel4vka/include. And the libsel4vka.a needs to be built and linked to the executable. I don't know how I can achieve it. The CMakefile original (trivial) content is: project(uart C) DeclareCAmkESComponent(Client SOURCES components/Client/src/client.c) DeclareCAmkESComponent(Driver SOURCES components/Driver/src/driver.c) DeclareCAmkESRootserver(uart.camkes) I try to add the libsel4vka.a to the linker via appending to it: target_link_libraries( uart PUBLIC sel4vka ) But I get: /usr/bin/cmake -S/home/chris/camkes_brkwy/projects/camkes -B/home/chris/camkes_brkwy/uart_tqma8xqp-build ninja: error: rebuilding 'build.ninja': subcommand failed chris@ubuntu:~/camkes_brkwy/uart_tqma8xqp-build$ ninja CMake Error at apps/uart/CMakeLists.txt:35 (target_link_libraries): Cannot specify link libraries for target "uart" which is not built by this project. I don't understand why "uart" is not a target, given the statement: project(uart C) So given target_link_libraries() fails me here, what am I doing wrong? what's the proper way of including -I paths and *.a files in Camkes-type CMakefile? Thanks for your help! Chris

2 1

3rd seL4 Summit - Tutorial
by Cedric MAIRE 23 Oct '20

23 Oct '20

Dear seL4 developers, I would be happy to get more information about the presented tutorial during the 3rd seL4 summit. What will it be about? Is this tutorial already available on the website or exclusive to the summit attendees? I looked through the given PDF (https://na.eventscloud.com/file_uploads/a236a51b4b76609e82fcc316992b73f4_20…) but didn't find any information regarding the tutorial. Best regards, Cedric Maire <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <STYLE type="text/css">  </STYLE> </head> <body> <hr style="color: #000000;background-color: #000000;height: 1px;"/> <p>The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: <a href="http://www.icrc.org">www.icrc.org</a><p> <p>This e-mail is intended for the named recipient(s) only.<br> Its contents are confidential and may only be retained by the named recipient(s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. </p> <hr style="color: #000000;background-color: #000000;height: 1px;"/> </body> </html>

1 0

Adding a library to the executable
by Chris Koziarz 22 Oct '20

22 Oct '20

Hi all, This might be a CMake rather than seL4 question, but bear with me because I'm new to CMake so still I don't understand how seL4 is being built. I don't know how to add and link a piece of new code (a static library) to the executable. I add the statements to the CMakeList.txt: add_library(chrises_lib STATIC ${sources}) target_link_libraries(chrises_lib ...) and I can see libchrises_lib.a being built. By examining build.ninja, I can see the whole bunch of libraries (.a files) being pulled in by the linker, but there is no chrises_lib.a in the long list of .a files. And the result is obviously 'undefined reference to' all symbols that are im[lemented in chrises_lib.a. What am I missing? What do I have to add to the series of CMakeList.txt and where I need to add (besides add_library and target_link_libraries that I'm already using per above), in order for my chrises_lib.a be included in the list at static libs below? ############################################# # Link the executable apps/sel4test-driver/sel4test-driver build apps/sel4test-driver/sel4test-driver: C_EXECUTABLE_LINKER__sel4test-driver apps/sel4test-driver/archive.o apps/sel4test-driver/CMakeFiles/sel4test-driver.dir/src/arch/arm/arch.c.obj apps/sel4test-driver/CMakeFiles/sel4test-driver.dir/src/main.c.obj apps/sel4test-driver/CMakeFiles/sel4test-driver.dir/src/tests/interrupt.c.obj apps/sel4test-driver/CMakeFiles/sel4test-driver.dir/src/tests/syscall.c.obj apps/sel4test-driver/CMakeFiles/sel4test-driver.dir/src/tests/timer.c.obj apps/sel4test-driver/CMakeFiles/sel4test-driver.dir/src/testtypes.c.obj apps/sel4test-driver/CMakeFiles/sel4test-driver.dir/src/timer.c.obj | libsel4/libsel4.a apps/sel4test-driver/sel4runtime/libsel4runtime.a apps/sel4test-driver/seL4_libs/libsel4allocman/libsel4allocman.a apps/sel4test-driver/seL4_libs/libsel4vka/libsel4vka.a apps/sel4test-driver/seL4_libs/libsel4utils/libsel4utils.a apps/sel4test-driver/sel4_projects_libs/libsel4rpc/libsel4rpc.a apps/sel4test-driver/seL4_libs/libsel4test/libsel4test.a apps/sel4test-driver/seL4_libs/libsel4platsupport/libsel4platsupport.a apps/sel4test-driver/seL4_libs/libsel4muslcsys/libsel4muslcsys.a apps/sel4test-driver/libsel4testsupport/libsel4testsupport.a apps/sel4test-driver/seL4_libs/libsel4test/libsel4test.a apps/sel4test-driver/sel4_projects_libs/libsel4rpc/libsel4rpc.a apps/sel4test-driver/sel4_projects_libs/libsel4nanopb/libsel4nanopb.a apps/sel4test-driver/sel4_projects_libs/libsel4nanopb/libnanopb.a apps/sel4test-driver/seL4_libs/libsel4sync/libsel4sync.a apps/sel4test-driver/seL4_libs/libsel4serialserver/libsel4serialserver.a apps/sel4test-driver/seL4_libs/libsel4utils/libsel4utils.a apps/sel4test-driver/util_libs/libelf/libelf.a apps/sel4test-driver/util_libs/libcpio/libcpio.a apps/sel4test-driver/seL4_libs/libsel4platsupport/libsel4platsupport.a apps/sel4test-driver/sel4runtime/libsel4runtime.a apps/sel4test-driver/util_libs/libplatsupport/libplatsupport.a apps/sel4test-driver/util_libs/libfdt/libfdt.a apps/sel4test-driver/seL4_libs/libsel4simple-default/libsel4simple-default.a apps/sel4test-driver/seL4_libs/libsel4debug/libsel4debug.a apps/sel4test-driver/seL4_libs/libsel4vspace/libsel4vspace.a apps/sel4test-driver/seL4_libs/libsel4simple/libsel4simple.a apps/sel4test-driver/seL4_libs/libsel4vka/libsel4vka.a libsel4/libsel4.a apps/sel4test-driver/util_libs/libutils/libutils.a apps/sel4test-driver/musllibc/build-temp/stage/lib/libc.a || apps/sel4test-driver/libsel4testsupport/libsel4testsupport.a apps/sel4test-driver/musllibc/muslc_gen apps/sel4test-driver/seL4_libs/libsel4allocman/libsel4allocman.a apps/sel4test-driver/seL4_libs/libsel4debug/libsel4debug.a apps/sel4test-driver/seL4_libs/libsel4debug/sel4debug_Gen apps/sel4test-driver/seL4_libs/libsel4muslcsys/libsel4muslcsys.a apps/sel4test-driver/seL4_libs/libsel4muslcsys/sel4muslcsys_Gen apps/sel4test-driver/seL4_libs/libsel4platsupport/libsel4platsupport.a apps/sel4test-driver/seL4_libs/libsel4platsupport/sel4platsupport_Gen apps/sel4test-driver/seL4_libs/libsel4serialserver/libsel4serialserver.a apps/sel4test-driver/seL4_libs/libsel4serialserver/sel4serialserver_Gen apps/sel4test-driver/seL4_libs/libsel4simple-default/libsel4simple-default.a apps/sel4test-driver/seL4_libs/libsel4simple/libsel4simple.a apps/sel4test-driver/seL4_libs/libsel4sync/libsel4sync.a apps/sel4test-driver/seL4_libs/libsel4test/libsel4test.a apps/sel4test-driver/seL4_libs/libsel4test/sel4test_Gen apps/sel4test-driver/seL4_libs/libsel4utils/libsel4utils.a apps/sel4test-driver/seL4_libs/libsel4utils/sel4utils_Gen apps/sel4test-driver/seL4_libs/libsel4vka/libsel4vka.a apps/sel4test-driver/seL4_libs/libsel4vka/sel4vka_Gen apps/sel4test-driver/seL4_libs/libsel4vspace/libsel4vspace.a apps/sel4test-driver/sel4_projects_libs/libsel4nanopb/libnanopb.a apps/sel4test-driver/sel4_projects_libs/libsel4nanopb/libsel4nanopb.a apps/sel4test-driver/sel4_projects_libs/libsel4rpc/libsel4rpc.a apps/sel4test-driver/sel4runtime/libsel4runtime.a apps/sel4test-driver/sel4runtime/sel4runtime_Gen apps/sel4test-driver/sel4test-driver_Gen apps/sel4test-driver/sel4test-tests/sel4test-tests apps/sel4test-driver/util_libs/libcpio/libcpio.a apps/sel4test-driver/util_libs/libelf/libelf.a apps/sel4test-driver/util_libs/libfdt/libfdt.a apps/sel4test-driver/util_libs/libplatsupport/libplatsupport.a apps/sel4test-driver/util_libs/libplatsupport/platsupport_Gen apps/sel4test-driver/util_libs/libutils/libutils.a apps/sel4test-driver/util_libs/libutils/utils_Gen kernel/kernel_Gen libsel4/libsel4.a libsel4/sel4_Gen libsel4/sel4_autoconf_Gen

2 2

Connectivity of 2 sel4 powered systems
by ogosinkem＠gmail.com 21 Oct '20

21 Oct '20

Hi all, I wanted to ask what the best way to connect to Odroid-C2 boards that run the sel4 microkernel to each other using picotcp or the preferred library for network connectivity. Is there a way to connect them wirelessly or is an ethernet connection a must?. I'm very new to the sel4 kernel so I apologise if these questions seem basic and generic. Sincerely, Nkem Ogosi

2 1

Camkes-arm-vm + MCS?
by Jim McColl 19 Oct '20

19 Oct '20

So I have been messing with seL4 for about a month now and I have been having a wonderful time! But I would like to do something kind of wacky. I’d like to run a couple of virtual machines like in the vm_multi example…but with MCS. I remember reading on the website a while back that virtualization + MCS was not supported, but then all the seL4 Foundation changes happened and I can no longer find that reference. So I was wondering if there is virtualization support with MCS on the public seL4 side yet? (Or maybe the private side github? If so I’d be more than happy to write a toy to test it out on some of the hardware (TK1SOM, TX2) I have here at the house [image: :smile:]) I decided to take a day and play with trying to get the vm_cross_connector and MCS (using the mcs-examples) to play nice together using platform qemu-arm-virt…but I’m currently stuck on a seL4_recv in vm_run_arch after getting a handle_async_event@main.c:909 Not IRQ Message: Unknown label (8) which I suspect is a seL4_Fault_VCPUFault from the MCS telling the thread its budget is up, but honestly I don’t have enough experience yet to really know…so its kind of a guess. I put a bunch of prints in there and I know the Linux Kernel is loaded its almost like its getting right up to the entry point and then faulting. Anyways any help anyone can provide would be awesome and thanks in advance for any help!

1 0

Invitation to Attend the 3rd seL4 Summit
by Heiser, Gernot (Data61, Kensington NSW) 15 Oct '20

15 Oct '20

Dear seL4 Community, The 3rd seL4 Summit will take place (virtually) on 15–18 November (US East Coast time). The program features a tutorial and 3 days packed with great talks and panels, see https://na.eventscloud.com/file_uploads/a236a51b4b76609e82fcc316992b73f4_20… Presentations will be streamed according to the schedule and available for download right after, and there will be an on-line discussion forum. Registration is only $80US: https://na.eventscloud.com/ereg/index.php?eventid=579066& Gernot

1 0

Mailing list delivery problems ...
by Chubb, Peter (Data61, Kensington NSW) 14 Oct '20

14 Oct '20

Hi Folks, Some time over the last few weeks, the DNS config on our mail server changed such that we ended with a mail loop. The result is that email sent to the list between September 25 and October 11 may have been lost. So if you sent email to devel(a)sel4.systems during that time, we're not ignoring you -- we never saw the email. Peter C -- Peter Chubb Tel: +61 2 9490 5852 http://ts.data61.csiro.au/ Trustworthy Systems Group CSIRO's Data61

1 0

Userland components in Ring 1/2 (where kernel is in ring 0) to provide protection from less trusted components
by Isaac Beckett 18 Sep '20

18 Sep '20

Hey all, I was wondering if it makes sense for someone building a system on seL4 to run certain drivers or other critical components in a more privileged environment, but still outside the kernel. Does using a different CPU mode in this context make sense? My hunch is that the case is no, because x86 has those extra rings, but ARM only has two modes, Supervisor/System and User mode, which would make it hard to provide any mechanism for the kernel to manage privileged components, because of the differences between platforms.

6 6

capability name change
by Sachin More 17 Sep '20

17 Sep '20

Hi: Between version 9.0.1 and 10.0.0, the capability name seL4_CapIOPort changed to seL4_CapIOPortControl in the file seL4/libsel4/include/sel4/bootinfo_types.h. I have some legacy code written for 9.0.1 that I want to port to 10.0.0. When I changed the occurrences of seL4_CapIOPort to seL4_CapIOPortControl, I am getting the following: Warning: copy: seL4_CNode_Copy (0x7) returned 3 followed some time later by: Warn<<seL4(CPU 0) [decodeInvocation/530 T0xffffff80002de400 "child of: 'child of: 'rootserver''" @20f27a4]: Attempted to invoke a null cap #7.>> What am I doing wrong? thanks in advance, Sachin

2 2

Re: [seL4] Devel Digest, Vol 76, Issue 8
by Chris Koziarz 16 Sep '20

16 Sep '20

Thanks Damon for your help. I've reinstalled Haskell stack this morning> This time I tried fault-handlers tutorial. It appears the reinstall had made the difference as ninja indeed spawned the process: $ stack build --fast and after just a minute or two (yesterday the whole thing was hanging for a good 20-30min before I lost patience), a long log was produced. Among tons of messages, I found this warning: Copied executables to /home/chris/sel4_tutorials/fault-handlers_build/capDL-tool: - parse-capDL Warning: Installation path /home/chris/sel4_tutorials/fault-handlers_build/capDL-tool not found on the PATH environment variable. I hope the warning won't stop me, although I'm curious why capDL wants to live in (and have a path to) a tutorial build directory rather than some common bin dirs like /usr/bin:/snap/bin or such... Thanks again, Chris On Tue, Sep 15, 2020 at 10:53 PM <devel-request(a)sel4.systems> wrote: > Send Devel mailing list submissions to > devel(a)sel4.systems > > To subscribe or unsubscribe via the World Wide Web, visit > https://sel4.systems/lists/listinfo/devel > or, via email, send a message with subject or body 'help' to > devel-request(a)sel4.systems > > You can reach the person managing the list at > devel-owner(a)sel4.systems > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Devel digest..." > > > Today's Topics: > > 1. Re: CAmkES Linux VM Tutorial/Minimal Build Issue > (Lee, Damon (Data61, Kensington NSW)) > 2. Re: ADL tool hangs (Lee, Damon (Data61, Kensington NSW)) > 3. capability name change (Sachin More) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Sep 2020 02:16:43 +0000 > From: "Lee, Damon (Data61, Kensington NSW)" > <Damon.Lee(a)data61.csiro.au> > To: "devel(a)sel4.systems" <devel(a)sel4.systems> > Subject: Re: [seL4] CAmkES Linux VM Tutorial/Minimal Build Issue > Message-ID: <tfbr1r3vl6e.fsf(a)coopers.keg.data61.csiro.au> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Jim, > > > So there I was having a lovely time doing the seL4 > > Tutorials...and I got > > hit with debug output #1 below, so I confirmed that I indeed had > > nested > > virtualization working by making an running an Ubuntu VM in side > > of an > > Ubuntu VM on an Ubuntu box in using kvm and qemu, so I do not > > think it is > > that. I tried passing the host processor through just to see if > > there > > something was getting in the way to no avail. > > I took a look at the debug output and it looks like there's > something funny > going on with the kernel and the VMM. I was able to replicate your > issue using > the manifest available on GitHub, but it was working fine using > our internal > manifests. So I suspect there were probably fixes that haven't > been propagated > to GitHub yet via our internal CI processes. > > I'll take a look at why our CI haven't propagated changes to > GitHub and in the > meantime, I've created a fork[1] on GitHub of our internal > tutorial manifest so > you can use that instead. > > [1] https://github.com/nomadeel/sel4-tutorials-manifest > > Hope this helps, > Damon > > > ------------------------------ > > Message: 2 > Date: Tue, 15 Sep 2020 02:25:57 +0000 > From: "Lee, Damon (Data61, Kensington NSW)" > <Damon.Lee(a)data61.csiro.au> > To: "devel(a)sel4.systems" <devel(a)sel4.systems> > Subject: Re: [seL4] ADL tool hangs > Message-ID: <tfbo8m7vkr0.fsf(a)coopers.keg.data61.csiro.au> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Chris, > > > I have recently messed up my ubuntu host seL4 building machine > > and I had to > > recreate it from scratch. But I have missed something on the > > way. So I have > > a problem building anything that involves Camkes components. It > > appears > > that a tool generating ADL or linking capDL or something along > > is missing > > and results in a hang during building. For example when building > > ipc > > tutorial (for x85 platform): > > > > root@ubuntu:/home/chris/sel4_tutorials/ipc_build# ninja > > [0/8] Generating capDL-tool/parse-capDL^C > > ninja: build stopped: interrupted by user. > > > > Or mcs tutorial: > > > > root@ubuntu:/home/chris/sel4_tutorials/mcs_build# ninja > > [0/8] Generating capDL-tool/parse-capDL^C > > ninja: build stopped: interrupted by user. > > This build step builds the capDL-tools which is written in > Haskell. 'stack' is > the toolchain used to build the capDL-tools and we've seen > examples of it taking > a *very* long time on specific distributions like Ubuntu. To > verify this, > perhaps try `ps aux | grep stack` or similar to see if 'stack' is > being run. > > We do cache the build after the first time it's being run, so > subsequent builds > shouldn't take too long. If this build step doesn't finish even > after waiting > for a long time (30 minutes or so), let us know and we'll be happy > to help. > > Regards, > Damon > > > ------------------------------ > > Message: 3 > Date: Tue, 15 Sep 2020 08:51:15 -0400 > From: Sachin More <sachinsureshmore(a)gmail.com> > To: devel(a)sel4.systems > Subject: [seL4] capability name change > Message-ID: > <CAH36oswCDPRDFeNbgFPVnKvgapFyo= > BbsiNRuf+FjqrBaquegg(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi: > > Between version 9.0.1 and 10.0.0, the capability name seL4_CapIOPort > changed to seL4_CapIOPortControl in the file > seL4/libsel4/include/sel4/bootinfo_types.h. > I have some legacy code written for 9.0.1 that I want to port to 10.0.0. > When I changed the occurrences of seL4_CapIOPort to seL4_CapIOPortControl, > I am getting the following: > > Warning: copy: seL4_CNode_Copy (0x7) returned 3 > > followed some time later by: > > Warn<<seL4(CPU 0) [decodeInvocation/530 T0xffffff80002de400 "child of: > 'child of: 'rootserver''" @20f27a4]: Attempted to invoke a null cap #7.>> > > What am I doing wrong? > > thanks in advance, > Sachin > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Devel mailing list > Devel(a)sel4.systems > https://sel4.systems/lists/listinfo/devel > > > ------------------------------ > > End of Devel Digest, Vol 76, Issue 8 > ************************************ >

2 1

Subject=Re: CAmkES Linux VM Tutorial/Minimal Build Issue
by Jim McColl 15 Sep '20

15 Sep '20

Damon, Too easy, worked on the first go! Thank you for the help! -Jim Evidence: Welcome to Buildroot buildroot login: [ 2.627354] random: fast init done Welcome to Buildroot buildroot login: root Password: # ls -ali total 4 108 drwx------ 2 root root 0 Sep 15 15:20 . 1 drwxrwxr-x 17 root root 0 Jan 8 2020 .. 1114 -rw------- 1 root root 11 Sep 15 15:20 .ash_history #

1 0

ADL tool hangs
by Chris Koziarz 15 Sep '20

15 Sep '20

Hi all, I have recently messed up my ubuntu host seL4 building machine and I had to recreate it from scratch. But I have missed something on the way. So I have a problem building anything that involves Camkes components. It appears that a tool generating ADL or linking capDL or something along is missing and results in a hang during building. For example when building ipc tutorial (for x85 platform): root@ubuntu:/home/chris/sel4_tutorials/ipc_build# ninja [0/8] Generating capDL-tool/parse-capDL^C ninja: build stopped: interrupted by user. Or mcs tutorial: root@ubuntu:/home/chris/sel4_tutorials/mcs_build# ninja [0/8] Generating capDL-tool/parse-capDL^C ninja: build stopped: interrupted by user. Looking into build.ninja script, I think the problem command be this one: build capDL-tool/parse-capDL: CUSTOM_COMMAND COMMAND = cd /home/chris/sel4_tutorials/mcs_build/capDL-tool && printf capDL-tool/parse-capDL:\ > /home/chris/sel4_tutorials/mcs_build/capDL-tool/parse-capDL.d && find -L /home/chris/sel4_tutorials/projects/capdl/capDL-tool/ -type f -printf %p\ >> /home/chris/sel4_tutorials/mcs_build/capDL-tool/parse-capDL.d && cp -a /home/chris/sel4_tutorials/projects/capdl/capDL-tool/* . && /usr/bin/cmake -E env make DESC = Generating capDL-tool/parse-capDL depfile = /home/chris/sel4_tutorials/mcs_build/capDL-tool/parse-capDL.d restat = 1 but I don't know why it would be hanging my build and how I should fix it. Any help greatly appreciated. Chris.

2 1

CAmkES Linux VM Tutorial/Minimal Build Issue
by Jim McColl 15 Sep '20

15 Sep '20

So there I was having a lovely time doing the seL4 Tutorials...and I got hit with debug output #1 below, so I confirmed that I indeed had nested virtualization working by making an running an Ubuntu VM in side of an Ubuntu VM on an Ubuntu box in using kvm and qemu, so I do not think it is that. I tried passing the host processor through just to see if there something was getting in the way to no avail. That was when I decided to go through the devel archives and the closest similar post I could find was 07 Aug 2020 ( https://sel4.systems/pipermail/devel/2020-August/002845.html) unfortunately there's no debug output so I cannot confirm is it is the same issue. There was also an issue in April ( https://sel4.systems/pipermail/devel/2020-April/002781.html) that also looked similar but I grep'd through the source and could not find the line referenced line from the commit. Finally I natively built minimal from https://github.com/seL4/camkes-vm-examples in the hopes that it was an issue with the tutorial docker container which led to output #2 below. Which brings me to now humbly request for help so I can finish up the tutorials. Thank you advance for any help anyone can provide, hopefully it is a simple mistake on my part. -Jim ====== VERY LONG DEBUG STUFF BELOW ====== - Debug Output #1: ./simulate: qemu-system-x86_64 -machine q35,accel=kvm,kernel-irqchip=split -cpu Nehalem,+vme,+pdpe1gb,-xsave,-xsaveopt,-xsavec,-fsgsbase,-invpcid,enforce,+vmx -nographic -serial mon:stdio -m size=2G -enable-kvm -device intel-iommu,intremap=off -net nic,model=e1000 -net tap,script=no,ifname=tap0 -kernel images/kernel-x86_64-pc99 -initrd images/capdl-loader-image-x86_64-pc99 Boot config: debug_port = 0x3f8 Boot config: disable_iommu = false Detected 1 boot module(s): module #0: start=0xa1d000 end=0x1e366e0 size=0x14196e0 name='images/capdl-loader-image-x86_64-pc99' Parsing GRUB physical memory map Physical Memory Region from 0 size 9fc00 type 1 Physical Memory Region from 9fc00 size 400 type 2 Physical Memory Region from f0000 size 10000 type 2 Physical Memory Region from 100000 size 7fedf000 type 1 Adding physical memory region 0x100000-0x7ffdf000 Physical Memory Region from 7ffdf000 size 21000 type 2 Physical Memory Region from b0000000 size 10000000 type 2 Physical Memory Region from fed1c000 size 4000 type 2 Physical Memory Region from feffc000 size 4000 type 2 Physical Memory Region from fffc0000 size 40000 type 2 Multiboot gave us no video information ACPI: RSDP paddr=0xf68d0 ACPI: RSDP vaddr=0xf68d0 ACPI: RSDT paddr=0x7ffe210d ACPI: RSDT vaddr=0x7ffe210d Kernel loaded to: start=0x100000 end=0xa1c000 size=0x91c000 entry=0x10125e ACPI: RSDT paddr=0x7ffe210d ACPI: RSDT vaddr=0x7ffe210d ACPI: FADT paddr=0x7ffe1ee5 ACPI: FADT vaddr=0x7ffe1ee5 ACPI: FADT flags=0x84a5 ACPI: DMAR paddr=0x7ffe20c5 ACPI: DMAR vaddr=0x7ffe20c5 ACPI: IOMMU host address width: 39 ACPI: 1 IOMMUs detected ACPI: MADT paddr=0x7ffe1fd9 ACPI: MADT vaddr=0x7ffe1fd9 ACPI: MADT apic_addr=0xfee00000 ACPI: MADT flags=0x1 ACPI: MADT_APIC apic_id=0x0 ACPI: MADT_IOAPIC ioapic_id=0 ioapic_addr=0xfec00000 gsib=0 ACPI: MADT_ISO bus=0 source=0 gsi=2 flags=0x0 ACPI: MADT_ISO bus=0 source=5 gsi=5 flags=0xd ACPI: MADT_ISO bus=0 source=9 gsi=9 flags=0xd ACPI: MADT_ISO bus=0 source=10 gsi=10 flags=0xd ACPI: MADT_ISO bus=0 source=11 gsi=11 flags=0xd ACPI: 1 CPU(s) detected ELF-loading userland images from boot modules: size=0x289a000 v_entry=0x4083af v_start=0x400000 v_end=0x2c9a000 p_start=0x1e37000 p_end=0x46d1000 Moving loaded userland images to final location: from=0x1e37000 to=0xa1c000 size=0x289a000 Starting node #0 with APIC ID 0 Mapping kernel window is done vt-x: Load IA32_PERF_GLOBAL_CONTROL not supported. Hardware debugging may not work IOMMU 0x0: 16-bit domain IDs supported IOMMU: Using 3 page-table levels (max. supported:3) IOMMU: Create VTD context table for PCI bus 0x0 (pptr=0xffffff807e01d000) ===== SNIP ====== IOMMU: Create VTD context table for PCI bus 0xfe (pptr=0xffffff807e11b000) IOMMU: Create VTD context table for PCI bus 0xff (pptr=0xffffff807e11c000) IOMMU 0x0: enabling... enabled Booting all finished, dropped to user space Single bus detected lib_pci_scan_dev found pci device 0 0 PCI :: 00.00.00 : intel Unknown device ID. (vid 0x8086 did 0x29c0) line0 pin0 lib_pci_scan_dev found pci device 0 1 PCI :: 00.01.00 : Unknown vendor ID. Unknown device ID. (vid 0x1234 did 0x1111) line0 pin0 BAR0 : [ mem 0xfd000000 sz 0x1000000 szmask 0xff000000 prefetch ] BAR2 : [ mem 0xfebb0000 sz 0x1000 szmask 0xfffff000 ] lib_pci_scan_dev found pci device 0 2 PCI :: 00.02.00 : intel Unknown device ID. (vid 0x8086 did 0x100e) line11 pin1 BAR0 : [ mem 0xfeb80000 sz 0x20000 szmask 0xfffe0000 ] BAR1 : [ io 0xc000 sz 0x40 szmask 0xffffffc0 ] lib_pci_scan_dev found pci device 0 31 PCI :: 00.1f.00 : intel intel_ich9_8 (vid 0x8086 did 0x2918) line0 pin0 lib_pci_scan_dev found multi function device 0 31 PCI :: 00.1f.02 : intel Unknown device ID. (vid 0x8086 did 0x2922) line10 pin1 BAR4 : [ io 0xc080 sz 0x20 szmask 0xffffffe0 ] BAR5 : [ mem 0xfebb1000 sz 0x1000 szmask 0xfffff000 ] PCI :: 00.1f.03 : intel intel_ich9_6 (vid 0x8086 did 0x2930) line10 pin1 BAR4 : [ io 0x700 sz 0x40 szmask 0xffffffc0 ] ========== KERNEL EXCEPTION ========== Vector: 0xd ErrCode: 0x0 IP: 0xffffffff8080d2e9 SP: 0xffffffff80a0bd88 FLAGS: 0x10002 CR0: 0x8001003b CR2: 0x0 (page-fault address) CR3: 0xa17000 (page-directory physical address) CR4: 0x2220 Stack Dump: *0xffffffff80a0bd88 == 0xffffff807c052880 *0xffffffff80a0bd90 == 0xffffff80318c1400 *0xffffffff80a0bd98 == 0x1 *0xffffffff80a0bda0 == 0xffffffff80812415 *0xffffffff80a0bda8 == 0xffffff8020001580 *0xffffffff80a0bdb0 == 0x1000ff8029831000 *0xffffffff80a0bdb8 == 0xc *0xffffffff80a0bdc0 == 0xffffffff8081eeb8 *0xffffffff80a0bdc8 == 0xc *0xffffffff80a0bdd0 == 0xffffff8020002560 *0xffffffff80a0bdd8 == 0xffffff8029831000 *0xffffffff80a0bde0 == 0x0 *0xffffffff80a0bde8 == 0x1ffed6 *0xffffffff80a0bdf0 == 0xffffff8029831000 *0xffffffff80a0bdf8 == 0xffffff80318c1c00 *0xffffffff80a0be00 == 0xffffff8020002540 *0xffffffff80a0be08 == 0xffffffff80a0be60 *0xffffffff80a0be10 == 0xffffff8020002540 *0xffffffff80a0be18 == 0xffffff80318c18a0 *0xffffffff80a0be20 == 0xffffff8029831000 Halting... halting... Kernel entry via Syscall, number: 1, Call Cap type: 12, Invocation tag: 54 - Debug Output #2: ===== SNIP: Same as above ===== IOMMU: Create VTD context table for PCI bus 0xff (pptr=0xff10d000) IOMMU 0x0: enabling... enabled Booting all finished, dropped to user space <<seL4(CPU 0) [decodeUntypedInvocation/208 T0xff10e400 "rootserver" @8048495]: Untyped Retype: Insufficient memory (1 * 8388608 bytes needed, 0 bytes available).>> Single bus detected lib_pci_scan_dev found pci device 0 0 PCI :: 00.00.00 : intel Unknown device ID. (vid 0x8086 did 0x29c0) line0 pin0 lib_pci_scan_dev found pci device 0 1 PCI :: 00.01.00 : Unknown vendor ID. Unknown device ID. (vid 0x1234 did 0x1111) line0 pin0 BAR0 : [ mem 0xfd000000 sz 0x1000000 szmask 0xff000000 prefetch ] BAR2 : [ mem 0xfebb0000 sz 0x1000 szmask 0xfffff000 ] lib_pci_scan_dev found pci device 0 2 PCI :: 00.02.00 : intel Unknown device ID. (vid 0x8086 did 0x100e) line11 pin1 BAR0 : [ mem 0xfeb80000 sz 0x20000 szmask 0xfffe0000 ] BAR1 : [ io 0xc000 sz 0x40 szmask 0xffffffc0 ] lib_pci_scan_dev found pci device 0 31 PCI :: 00.1f.00 : intel intel_ich9_8 (vid 0x8086 did 0x2918) line0 pin0 lib_pci_scan_dev found multi function device 0 31 PCI :: 00.1f.02 : intel Unknown device ID. (vid 0x8086 did 0x2922) line10 pin1 BAR4 : [ io 0xc080 sz 0x20 szmask 0xffffffe0 ] BAR5 : [ mem 0xfebb1000 sz 0x1000 szmask 0xfffff000 ] PCI :: 00.1f.03 : intel intel_ich9_6 (vid 0x8086 did 0x2930) line10 pin1 BAR4 : [ io 0x700 sz 0x40 szmask 0xffffffc0 ] seL4 failed assertion '(cte_t *)mdb_node_get_mdbNext(destSlot->cteMDBNode) == NULL && (cte_t *)mdb_node_get_mdbPrev(destSlot->cteMDBNode) == NULL' at /home/user/Documents/labs/rr/os/seL4-AUS/camkes_vm_examples/kernel/src/object/cnode.c:428 in function cteInsert halting... Kernel entry via Syscall, number: 1, Call Cap type: 12, Invocation tag: 53

2 1

Unable to setup Camkes VM tutorial
by Chris Koziarz 11 Sep '20

11 Sep '20

There is something wrong with Camkes VM repo or with my Linux machine. I am able to setup repo of other tutorials, i.e. repo init -u https://github.com/SEL4PROJ/sel4-tutorials-manifest works. However when I continue into Camkes VM: root@ubuntu:~/lv4_repo# mkdir camkes_VM root@ubuntu:~/lv4_repo# cd camkes_VM root@ubuntu:~/lv4_repo/camkes_VM# repo init -u https://github.com/sel4/camkes-vm-examples-manifest.git -b tipc-stage I get the following error: Downloading Repo source from https://gerrit.googlesource.com/git-repo fatal: Cannot get https://gerrit.googlesource.com/git-repo/clone.bundle fatal: error [Errno -3] Temporary failure in name resolution fatal: cloning the git-repo repository failed, will remove '.repo/repo' What might be going wrong? As can be seen, I'm running on ubuntu v20.04 Any help appreciated. Chris

2 1

seL4 Summit 2020 - Call for Presentations *extended* to Sep 15.
by Kuz, Ihor (Data61, Kensington NSW) 10 Sep '20

10 Sep '20

Hi, For people not on the seL4 announce list: the 3rd annual seL4 Summit will be held online on November 15-18, 2020. A call for presentations is out, and the deadline for submissions has been extended to September 15, 2020. Please consider submitting something about seL4-based work that you are doing or other seL4/microkernel/trustworthy systems topics. Submission only requires a title and abstract, so it’s pretty low overhead. Submit by email to Summit2020(a)sel4-us.org. See more detail on the announce list[1]. Ihor. [1] https://sel4.systems/pipermail/announce/2020/000036.html

1 0

CAmkES Linux VM - Networking
by Cedric MAIRE 03 Sep '20

03 Sep '20

Dear seL4 developers, I am running the CAmkES VM examples from `https://github.com/seL4/camkes-vm-examples` and am able to boot the `minimal` example with: ``` $ ../init-build.sh -DSIMULATION=TRUE -DCAMKES_VM_APP=minimal $ ninja $ qemu-system-x86_64 -m 512 -kernel images/kernel-ia32-pc99 -initrd images/capdl-loader-image-ia32-pc99 --enable-kvm -smp 2 -cpu Nehalem,+vmx -nographic ``` However this example does not provide networking capabilities due to missing drivers (is that correct?). Is there a simple way I may add networking? Simply put I would like the Linux guest to be able to connect to the internet. I tried passing the QEMU parameters to setup a tap interface, which didn't help. I also tried to use the example `cma34cr_centos` which should already provide networking but when I try to boot this example using `qemu-system-x86_64 -m 2048 -kernel images/kernel-x86_64-pc99 -initrd images/capdl-loader-image-x86_64-pc99 --enable-kvm -smp 2 -cpu Nehalem,+vmx -nographic` I get the following error: `create_objects@main.c:794 Ran out of untyped memory while creating objects.`. Full log output in the `.log` file. Thanks in advance, Best regards, Cedric Maire =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. ===============================================================================

1 0

Running RISC-V sel4 in QEMU/Spike
by Porter, Jeremy 02 Sep '20

02 Sep '20

I'm following the steps to build sel4 for QEMU and Spike here: https://docs.sel4.systems/Hardware/spike.html Spike - seL4 Docs | seL4 docs<https://docs.sel4.systems/Hardware/spike.html> If you plan to use the ./simulate script, please be sure to add the -DSIMULATION=1 argument when running cmake. Generated binaries can be found in the images/ directory.. You can also use run the tests on the 32-bit spike platform by replacing the -DRISCV64=TRUE option with -DRISCV32=TRUE. docs.sel4.systems Since my system doesn't have QEMU 4.2 or better I built the latest version of QEMU and use that instead. I get the following error from QEMU: /mnt/data/qemu/build/riscv64-softmmu/qemu-system-riscv64 -machine spike -nographic -serial mon:stdio -m size=4095M -kernel images/sel4test-driver-image-riscv-spikeqemu-system-riscv64: Unable to load the RISC-V firmware "opensbi-riscv64-spike-fw_jump.elf" In Spike this happens: /mnt/data/rocket-tools/bin/spike images/sel4test-driver-image-riscv-spike bbl loader ELF-loader started on (HART 0) (NODES 1) paddr=[80200000..8064d4d7] Looking for DTB in CPIO archive...found at 802cb1a0. Loaded DTB from 802cb1a0. paddr=[8402a000..8402afff] ELF-loading image 'kernel' paddr=[84000000..84029fff] vaddr=[ffffffff84000000..ffffffff84029fff] virt_entry=ffffffff84000000 ELF-loading image 'sel4test-driver' paddr=[8402b000..84401fff] vaddr=[10000..3e6fff] virt_entry=1b540 Jumping to kernel-image entry point... Init local IRQ Initialing PLIC... The tutorials lead me to believe this should go to user space. i.e. 327 printf("Booting all finished, dropped to user space\n"); in kernel/src/arch/riscv/kernel/boot.c Can anyone point out what's going wrong here in these two cases? Thank you! Jeremy

2 1

CAmkES Linux VM - Networking
by Cedric MAIRE 27 Aug '20

27 Aug '20

Dear seL4 developers, I am running the CAmkES VM examples from `https://github.com/seL4/camkes-vm-examples` and am able to boot the `minimal` example with: ``` $ ../init-build.sh -DSIMULATION=TRUE -DCAMKES_VM_APP=minimal $ ninja $ qemu-system-x86_64 -m 512 -kernel images/kernel-ia32-pc99 -initrd images/capdl-loader-image-ia32-pc99 --enable-kvm -smp 2 -cpu Nehalem,+vmx -nographic ``` However this example does not provide networking capabilities due to missing drivers (is that correct?). Is there a simple way I may add networking? Simply put I would like the Linux guest to be able to connect to the internet. I tried passing the QEMU parameters to setup a tap interface, which didn't help. I also tried to use the example `cma34cr_centos` which should already provide networking but when I try to boot this example using `qemu-system-x86_64 -m 2048 -kernel images/kernel-x86_64-pc99 -initrd images/capdl-loader-image-x86_64-pc99 --enable-kvm -smp 2 -cpu Nehalem,+vmx -nographic` I get the following error: `create_objects@main.c:794 Ran out of untyped memory while creating objects.`. Full log output in the `.log` file. Thanks in advance, Best regards, Cedric Maire =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. ===============================================================================

1 0

some question about sched_ctrl of mcs答复: some question about mcs
by yadong.li 26 Aug '20

26 Aug '20

Hi Kent： Firstly，thank you for your information. I found the test code call "simple_get_sched_ctrl(&env->simple, 0)" function to get sched_ctrl cap, but I feel confused about env->simple. I have two question about sched_ctrl when I want to add mcs call function for camkes-arm-vm project Background: I try to add get sched_ctrl cap before seL4_TCB_Configure of vm_create_vcpu_arch(projects/seL4_projects_libs/libsel4vm/src/arch/arm/boot.c) 1. I try use "simple_get_sched_ctrl(vm->simple, affinity);" or " simple_default_init_bootinfo(&simple, platsupport_get_bootinfo()) simple_get_sched_ctrl(simple, affinity);" But they all failed What "simple" should I used to get sched_ctl in this project. 2. I found camkes_simple_sched_ctrl in component.simple.c generate C code, have below code: /*- if 'sched_ctrl' in configuration[me.name].keys() -*/ But I did not found camkes configurations have "sched_ctrl" field in project or your examples in CAmkES Thank you very much -----邮件原件----- 发件人: Kent Mcleod [mailto:kent.mcleod72@gmail.com] 发送时间: 2020年8月25日 10:37 收件人: yadong.li 抄送: devel(a)sel4.systems 主题: Re: [seL4] some question about mcs > > Hi, > 1.Did seL4-11.0.0<https://docs.sel4.systems/releases/sel4/11.0.0> support mcs, I found some CONFIG_KERNEL_MCS in this release version ? or must use seL4 10.1.1-mcs <https://docs.sel4.systems/releases/sel4/10.1.1-mcs.html> branch? > 2'Where I can find some example about mcs in project? The introduction of Wiki is too simple , I can 't make the param of seL4_SchedControl_Configure is correct? > > Thank you very much 11.0.0 does introduce a config option CONFIG_KERNEL_MCS (KernelIsMCS in CMake). You could start with the MCS tutorial: https://docs.sel4.systems/Tutorials/mcs.html. Alternatively, there are MCS tests in seL4test: https://github.com/seL4/sel4test/blob/master/apps/sel4test-tests/src/tests/… or examples in CAmkES: - https://github.com/seL4/camkes/tree/master/apps/cms-donate - https://github.com/seL4/camkes/tree/master/apps/cs-donate - https://github.com/seL4/camkes/tree/master/apps/cs-nodonate - https://github.com/seL4/camkes/tree/master/apps/periodic - https://github.com/seL4/camkes/tree/master/apps/event-driven - https://github.com/seL4/camkes/tree/master/apps/mcs-donate - https://github.com/seL4/camkes/tree/master/apps/mcs-nodonate I'm not aware if there is any documentation about the CAmkES app examples, but I believe they are supposed to demonstrate different scheduling scenarios using MCS. > > _______________________________________________ > Devel mailing list > Devel(a)sel4.systems > https://sel4.systems/lists/listinfo/devel

1 0

"Ran out of untyped memory"
by Michael Neises 26 Aug '20

26 Aug '20

Hello, I'm trying to build a camkes app, but when I attempt to run it on an Odroid-xu4, I get the following error just before the boot halts: "Ran out of untyped memory while creating objects" I've narrowed the error down to two calls to a this function: https://github.com/SEL4PROJ/camkes-vm-linux/blob/dc354df3222766b9d366725751… When I use only one call, the image boots nicely. If I use both calls, I get the above error. My understanding is that this function simply adds an executable to the filesystem, so I'm not sure how to begin debugging this. Is it possible that the filesystem is actually "too big" for sel4 to boot successfully? Please advise! Best, Michael Neises

3 4

some question about mcs
by yadong.li 25 Aug '20

25 Aug '20

Hi, 1.Did seL4-11.0.0<https://docs.sel4.systems/releases/sel4/11.0.0> support mcs, I found some CONFIG_KERNEL_MCS in this release version ? or must use seL4 10.1.1-mcs <https://docs.sel4.systems/releases/sel4/10.1.1-mcs.html> branch? 2'Where I can find some example about mcs in project? The introduction of Wiki is too simple , I can 't make the param of seL4_SchedControl_Configure is correct? Thank you very much

2 1

Trouble getting a custom kernel to boot under sel4 on a tk1 board
by Travis Wheatley 24 Aug '20

24 Aug '20

I am having difficulty getting a custom kernel to boot under sel4 on a tk1 board. I have no problems building and booting an image that uses the pre-built linux-tk1-initrd file found in the projects/vm/linux folder. Howoever, when I build a “custom” kernel using buildroot-2016.08.1 as specified in this<https://docs.sel4.systems/projects/camkes-arm-vm/> the boot process hangs shortly after it loads the dtb. <<seL4(CPU 0) [decodeUntypedInvocation/212 T0xffc2d400 "rootserver" @106f0]: Untyped Retype: Insufficient memory (1 * 2097152 bytes needed, 0 bytes available).>> Loading Linux: 'linux' dtb: 'linux-dtb' install_linux_devices(a)main.c<mailto:install_linux_devices@main.c>:605 module name: map_frame_hack install_linux_devices(a)main.c<mailto:install_linux_devices@main.c>:605 module name: plat I am using the buildroot_tk1_initrd_defconfig file, also located in the projects/vm/linux folder. I am simply replacing the linux-tk1-initrd file in projects/vm/linux with the image file that gets created in the buildroot-2016.08.1/output/build/linux-custom/arch/arm/boot folder. I then clean my build directory and do the requisite “../init-build.sh -DPLATFORM=tk1 -DCAMKES_VM_APP=vm_minimal” followed by “ninja”. I then put the capdl-loader-image-arm-tk1 file on an SD card, put it in the Tk1 and do: “fatload mmc 1 0x82000000 <filename>” followed by “bootefi 0x82000000” Assuming the guidance on buildroot and the defconfig supplied match what was used to create the working pre-built linux-tk1-initrd kernel the “custom” kernel I built should be very similar. So, what am I missing? Why would a custom kernel hang at the above mentioned point in the boot process?

1 0

Porting Sel4 with RPi 3B+
by 萧琒 20 Aug '20

20 Aug '20

Hi, Professional Devel Support of Sel4, We are porting Sel4 with RPi 3B+, but we fail to boot RPi 3B+ with Sel4 successfully. We cann't find the problem, please help us. we follow the Steps: 1. Use Raspberry Pi Imager v1.4 to burn the operation system (Raspberry Pi OS Lite 32bit) on SD card, and it works well with hardware of RPi 3B+. 2. Build Sel4test-manifest: 2.1 clone the repo of https://github.com/seL4/sel4test-manifest.git 2.2 build image with ../init-build.sh -DPLATFORM=rpi3 -DAARCH32=1 2.3 the image file (sel4test-driver-image-arm-bcm2837) is produced successfully. 3. Following the SD card setup, Copy the following files to root direcctory of SD. 3.1 sel4test-driver-image-arm-bcm2837 3.2 bootcode.bin and start.elf from https://github.com/raspberrypi/firmware/tree/master/boot 3.3 u-boot.bin downloaded from https://sel4.systems/Info/Docs/u-boot-working-rpi3-32bit-v2017.11.bin 3.4 Add enable_uart=1 and kernel=u-boot.bin to the bottom of config.txt 3.5 uboot.env, we fail to find the file, so we don't use the file. if you know the step to produce uboot.env, please lead us. 4. Re-insert SD into the RPi3B+, and power the RPi3B+ on, the RPi3B+ shows the U-Boot successfully. 4.1 sel4test-driver-image-arm-bcm2837 image file’s name printed out with the command of "fatls mmc 0" 4.2 fatload the image with command of "fatload mmc 0 0x10000000 sel4test-driver-image-arm-bcm2837", the result: reading sel4test-driver-image-arm-bcm2837 4791000 bytes read in 406 ms (11.3 MiB/s) 4.3 bootelf 0x10000000, the result: CACHE: Misaligned operation at range [0082a000, 0082a034] CACHE: Misaligned operation at range [0082b000, 00834fcc] CACHE: Misaligned operation at range [00834fcc, 00835b07] CACHE: Misaligned operation at range [00c9be40, 00c9be9c] CACHE: Misaligned operation at range [00c9be9c, 00c9bec8] ## Starting application at 0x0082a000 ... Then, RPi3B+ is blocked and without anything else to display ! ---- Thanks, Alen 肖月振（萧琒）阿里云事业群-IOT事业部-飞天六十四部电话：13391191786 邮箱：yuezhen.xyz(a)alibaba-inc.com

2 1

Re: [seL4] Devel Digest, Vol 75, Issue 8
by Cedric MAIRE 19 Aug '20

19 Aug '20

Hi Luke, Thanks for your help! I just tried out your solution and get back the following error: `groupmod: GID '1000' already exists`. Here is the workflow that I follow: ``` $ git clone https://github.com/SEL4PROJ/seL4-CAmkES-L4v-dockerfiles.git $ cd ~/sel4/seL4-CAmkES-L4v-dockerfiles/ $ git pull # Make sure to be up-to-date. $ git checkout fix_rust $ git pull # Make sure to be up-to-date. `fix_rust` is ahead of `master` so no missing commits. $ ./build.sh -p -b camkes -s rust $ make user CAMKES_IMG=camkes-rust HOST_DIR="~/sel4/" ``` I attached a more detailed log of the error I get. The command throwing this is (full command in log file): `/bin/sh -c groupadd -fg ${GID} ${GROUP} [...] && chmod -R ug+rw /home/${UNAME}` Does this look familiar to you? Best, Cedric -----Original Message----- From: Devel <devel-bounces(a)sel4.systems> On Behalf Of devel-request(a)sel4.systems Sent: samedi, 15 août 2020 04:00 To: devel(a)sel4.systems Subject: Devel Digest, Vol 75, Issue 8 Send Devel mailing list submissions to devel(a)sel4.systems To subscribe or unsubscribe via the World Wide Web, visit https://sel4.systems/lists/listinfo/devel?mc_phishing_protection_id=28047-b… or, via email, send a message with subject or body 'help' to devel-request(a)sel4.systems You can reach the person managing the list at devel-owner(a)sel4.systems When replying, please edit your Subject line so it is more specific than "Re: Contents of Devel digest..." Today's Topics: 1. Re: Dockerfiles - "camkes-rust" Image (Mondy, Luke (Data61, Kensington NSW)) ---------------------------------------------------------------------- Message: 1 Date: Fri, 14 Aug 2020 06:29:32 +0000 From: "Mondy, Luke (Data61, Kensington NSW)" <Luke.Mondy(a)data61.csiro.au> To: "devel(a)sel4.systems" <devel(a)sel4.systems> Subject: Re: [seL4] Dockerfiles - "camkes-rust" Image Message-ID: <SYAPR01MB25284E1D39674828FDC11EBED5400(a)SYAPR01MB2528.ausprd01.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hello Cedric, Thanks for the report. I believe the best way to use the camkes-rust image is to run this: make user CAMKES_IMG=camkes-rust However, in saying that, it unfortunately does not perform quite as hoped. Because of the way the code is built, it ends up putting the Cargo/Rust content into /root/.cargo, which is inaccessible to you as a non-root user. This is an oversight on my part, as unfortunately these interactive bits of the Dockerfile system don't get tested automatically. I've made a PR on GitHub, which shows the fixes needed: https://github.com/SEL4PROJ/seL4-CAmkES-L4v-dockerfiles/pull/24 Note that the master branch has also been recently updated, so you may need to pick further commits from there (or simply pull them all down first) for things to work. Let me know if that helps. Cheers, Luke -- Dr Luke Mondy, Systems Administrator, P +61 2 9490 5773 | https://ts.data61.csiro.au/?mc_phishing_protection_id=28047-bsrk3aadu815grd… Trustworthy Systems | DATA61 | CSIRO CSIRO Staff Association Delegate Hours at CSIRO Monday: 9:00am to 5pm Tues, Wed, Fri: 1:30pm to 5pm ________________________________________ From: Devel <devel-bounces(a)sel4.systems> on behalf of Cedric MAIRE <cmaire(a)icrc.org> Sent: Friday, 14 August 2020 2:42 AM To: devel(a)sel4.systems Subject: [seL4] Dockerfiles - "camkes-rust" Image Dear seL4 developers, I am using the provided dockerfiles repository to build the docker images in order to compile seL4. I would like to add a rust compiler to my docker image, which I do with "./build.sh -p -b camkes -s rust". This builds an image tagged "trustworthysystems/camkes-rust". I would like to launch this image in a container using the "Makefile" as I would do for the "trustworthysystems/camkes" image (using "make user"). I tried adding targets to the "Makefile" file changing the "USER_BASE_IMG" variable to use "trustworthysystems/camkes-rust" instead of "trustworthysystems/camkes", without success. I also tried to force the image by renaming/retagging "trustworthysystems/camkes " to "trustworthysystems/camkes-old" and "trustworthysystems/camkes-rust" to "trustworthysystems/camkes ". I also forced every base image to be the one containing the Rust compiler (in "Makefile"). All without success. For some reason "trustworthysystems/camkes-rust" image is never used. If I start it manually using docker commands I am able to launch and attach to it, getting the expected Rust compiler. Through the "Makefile" it ever only uses "trustworthysystems/camkes" without the Rust compiler. Is there an easy way to get this to work? What am I missing? Best regards, Cedric =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. =============================================================================== _______________________________________________ Devel mailing list Devel(a)sel4.systems https://sel4.systems/lists/listinfo/devel?mc_phishing_protection_id=28047-b… ------------------------------ Subject: Digest Footer _______________________________________________ Devel mailing list Devel(a)sel4.systems https://sel4.systems/lists/listinfo/devel?mc_phishing_protection_id=28047-b… ------------------------------ End of Devel Digest, Vol 75, Issue 8 ************************************ =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. ===============================================================================

2 1

Dockerfiles - "camkes-rust" Image
by Cedric MAIRE 14 Aug '20

14 Aug '20

Dear seL4 developers, I am using the provided dockerfiles repository to build the docker images in order to compile seL4. I would like to add a rust compiler to my docker image, which I do with "./build.sh -p -b camkes -s rust". This builds an image tagged "trustworthysystems/camkes-rust". I would like to launch this image in a container using the "Makefile" as I would do for the "trustworthysystems/camkes" image (using "make user"). I tried adding targets to the "Makefile" file changing the "USER_BASE_IMG" variable to use "trustworthysystems/camkes-rust" instead of "trustworthysystems/camkes", without success. I also tried to force the image by renaming/retagging "trustworthysystems/camkes " to "trustworthysystems/camkes-old" and "trustworthysystems/camkes-rust" to "trustworthysystems/camkes ". I also forced every base image to be the one containing the Rust compiler (in "Makefile"). All without success. For some reason "trustworthysystems/camkes-rust" image is never used. If I start it manually using docker commands I am able to launch and attach to it, getting the expected Rust compiler. Through the "Makefile" it ever only uses "trustworthysystems/camkes" without the Rust compiler. Is there an easy way to get this to work? What am I missing? Best regards, Cedric =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. ===============================================================================

2 1

QEMU, seL4, CAmkES and Linux VM - Insufficient Memory
by Cedric MAIRE 13 Aug '20

13 Aug '20

Dear seL4 developers, I am trying to setup a stack of QEMU, seL4, CAmkES and a Linux VM. I am following the tutorial on "https://docs.sel4.systems/Tutorials/camkes-vm-linux.html" and also the example on "https://github.com/seL4/camkes-vm-examples". I am running in different errors depending on which path I follow. The machine is an old MacBook Pro (running Linux, exact specs are in the main log file). - Main log file: "intel.log", contains steps and workflows - Tests: All tests seem to pass. - CAmkES VM - Tutorial Version: doesn't start QEMU because of unsupported host flags (warnings) or some failing script - CAmkES VM - Example Version: seems to boot into seL4 or even the Linux VM, but fails because of some memory error Does this look familiar to you? Best regards, Cedric Maire =============================================================================== The ICRC - working to protect and assist people affected by armed conflict and other situations of violence. Find out more: www.icrc.org This e-mail is intended for the named recipient(s) only. Its contents are confidential and may only be retained by the named recipient (s) and may only be copied or disclosed with the consent of the International Committee of the Red Cross (ICRC). If you are not an intended recipient please delete this e-mail and notify the sender. ===============================================================================

2 2

Hins for an seL4 virtio pci driver?
by Radev, Martin 10 Aug '20

10 Aug '20

Hello seL4 community, I am currently examining the possibility of using seL4 in a VM and writing a virtio driver to communicate with a virtio pci device in the HV. I looked around the available seL4 projects, and I noticed that there is the `libvirtqueue` and `libpci` projects which should come handy. However, I haven't been able to to find any other project which uses either of the libraries and I haven't found any tests for the two projects. Can you point me to projects which use these two libraries? Kind regards, Martin

2 1

SeL4 Raspberry Pi -- QEMU support
by Brendan Morgenstern 07 Aug '20

07 Aug '20

Hello, I hope all is well. I am interested in running seL4 on the Raspberry Pi, and have been following this guide<https://research.csiro.au/tsblog/sel4-raspberry-pi-3/>. I have followed the instructions and am able to generate an seL4 image correctly, however the guide is geared towards running on hardware and in fact when I run the resulting 'simulate' script I get the following. "Unsupported platform or architecture for simulation". I can run it manually under qemu to an extent with raspi2 as a machine type (): qemu-system-arm -serial null -serial mon:stdio -nographic -M raspi2 -kernel sel4test-driver-image-arm-bcm2837 And it produces this output<https://pastebin.com/LLuum55T>. It seems the image can be *run*, but it doesn't seem to work; it gets stuck on the TIMER0001 test and the previous tests produce errors. It seems that qemu can't quite emulate the raspberry pi hardware. Is there a way to run the seL4 image on the Raspberry Pi in QEMU, or can you provide an alternative for emulation, or any help whatsoever on this matter? Thank you for your time, Brendan Morgenstern ________________________________ This message and all attachments are PRIVATE, and contain information that is PROPRIETARY to Intelligent Automation, Inc. You are not authorized to transmit or otherwise disclose this message or any attachments to any third party whatsoever without the express written consent of Intelligent Automation, Inc. If you received this message in error or you are not willing to view this message or any attachments on a confidential basis, please immediately delete this email and any attachments and notify Intelligent Automation, Inc.

2 2

Re: [seL4] [seL4 Announce] UNSW seL4 teaching videos available
by Heiser, Gernot (Data61, Kensington NSW) 02 Aug '20

02 Aug '20

I’ve (almost) finished teaching and all seL4-related videos from my Advanced OS course are now up on YouTube, details below. Gernot > On 2 Jun 2020, at 10:50, Announcements about seL4 -- low volume list <announce(a)sel4.systems> wrote: > > Dear seL4 community, > > I’m pleased to announce yet another contribution of UNSW Sydney to the seL4 community: This year I’m making the seL4-related videos from my UNSW Advanced Operating Systems class freely available. You’ll find them at the UNSW CSeLearning COMP9242 YouTube channel: https://www.youtube.com/playlist?list=PLbSaCpDlfd6qLbEsKquVo3--0gwYBmrUV > > At present there are the first two modules, which provide some background on microkernels and seL4, and discuss the seL4 API. More material will show up over the next two months. > > The complete course material, including all lecture slides, the project spec and code, are available, as always, from the COMP9042 web site: https://www.cse.unsw.edu.au/~cs9242/current/ > > Enjoy, > Gernot

1 0

help with tutorial
by Sachin More 02 Jul '20

02 Jul '20

Hi: I am new to L4 and have been working through the tutorials. However, I am having a problem doing the hello-camkes-0 tutorial. When I try to install the tutorial, I get the output below. Looks like a file hello-camkes-0_build/camkes_gen/deps_1 is not there. Any help would be greatly appreciated! thanks, Sachin $ ./init --tut hello-camkes-0 loading initial cache file ../projects/sel4-tutorials/settings.cmake -- Found capdl: /compile/sel4-tutorials-manifest/projects/capdl CMake Warning (dev) at /usr/share/cmake3/Modules/FindPackageHandleStandardArgs.cmake:272 (message): The package name passed to `find_package_handle_standard_args` (camkes-tool) does not match the name of the calling package (sel4-tutorials). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /compile/sel4-tutorials-manifest/projects/sel4-tutorials/Findsel4-tutorials.cmake:67 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /compile/sel4-tutorials-manifest/projects/sel4-tutorials/settings.cmake:96 (find_package) This warning is for project developers. Use -Wno-dev to suppress it. -- Found camkes-tool: /compile/sel4-tutorials-manifest/projects/sel4-tutorials CMake Warning (dev) at /usr/share/cmake3/Modules/FindPackageHandleStandardArgs.cmake:272 (message): The package name passed to `find_package_handle_standard_args` (camkes-tool) does not match the name of the calling package (sel4-tutorials). This can lead to problems in calling code that expects `find_package` result variables (e.g., `_FOUND`) to follow a certain pattern. Call Stack (most recent call first): /compile/sel4-tutorials-manifest/projects/sel4-tutorials/Findsel4-tutorials.cmake:67 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) /compile/sel4-tutorials-manifest/projects/sel4-tutorials/settings.cmake:96 (find_package) CMakeLists.txt:3 (include) This warning is for project developers. Use -Wno-dev to suppress it. -- The C compiler identification is GNU 7.3.1 -- The ASM compiler identification is GNU -- Found assembler: /opt/rh/devtoolset-7/root/usr/bin/gcc -- Check for working C compiler: /opt/rh/devtoolset-7/root/usr/bin/gcc -- Check for working C compiler: /opt/rh/devtoolset-7/root/usr/bin/gcc - works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Found camkes-tool: /compile/sel4-tutorials-manifest/projects/camkes-tool -- Found seL4: /compile/sel4-tutorials-manifest/kernel -- Found elfloader-tool: /compile/sel4-tutorials-manifest/tools/seL4/elfloader-tool -- Found musllibc: /compile/sel4-tutorials-manifest/projects/musllibc -- Found util_libs: /compile/sel4-tutorials-manifest/projects/util_libs -- Found seL4_libs: /compile/sel4-tutorials-manifest/projects/seL4_libs -- Found projects_libs: /compile/sel4-tutorials-manifest/projects/projects_libs -- Detecting cached version of: capDL-tool -- No cache path given. Set SEL4_CACHE_DIR to a path to enable caching binary artifacts. -- Found sel4runtime: /compile/sel4-tutorials-manifest/projects/sel4runtime -- Performing Test compiler_arch_test -- Performing Test compiler_arch_test - Success -- Detecting cached version of: musllibc -- No cache path given. Set SEL4_CACHE_DIR to a path to enable caching binary artifacts. -- /compile/sel4-tutorials-manifest/hello-camkes-0_build/ast.pickle is out of date. Regenerating... -- /compile/sel4-tutorials-manifest/hello-camkes-0_build/camkes-gen.cmake is out of date. Regenerating... CAmkES uses UTF-8 encoding, but your locale's preferred encoding is ansi_x3.4-1968. You can override your locale with the LANG environment variable. CMake Error at /compile/sel4-tutorials-manifest/tools/seL4/cmake-tool/helpers/make.cmake:13 (file): file failed to open for reading (No such file or directory): /compile/sel4-tutorials-manifest/hello-camkes-0_build/camkes_gen/deps_1 Call Stack (most recent call first): /compile/sel4-tutorials-manifest/tools/seL4/cmake-tool/helpers/make.cmake:71 (MakefileDepsToList) /compile/sel4-tutorials-manifest/projects/camkes-tool/camkes.cmake:503 (execute_process_with_stale_check) CMakeLists.txt:17 (GenerateCAmkESRootserver) /compile/sel4-tutorials-manifest/projects/sel4-tutorials/Findsel4-tutorials.cmake:29 (include) CMakeLists.txt:4 (sel4_tutorials_regenerate_tutorial) CMake Error at /compile/sel4-tutorials-manifest/projects/camkes-tool/camkes.cmake:523 (message): Failed to generate /compile/sel4-tutorials-manifest/hello-camkes-0_build/camkes-gen.cmake Call Stack (most recent call first): CMakeLists.txt:17 (GenerateCAmkESRootserver) /compile/sel4-tutorials-manifest/projects/sel4-tutorials/Findsel4-tutorials.cmake:29 (include) CMakeLists.txt:4 (sel4_tutorials_regenerate_tutorial) -- Configuring incomplete, errors occurred! See also "/compile/sel4-tutorials-manifest/hello-camkes-0_build/CMakeFiles/CMakeOutput.log". Traceback (most recent call last): File "./init", line 96, in <module> File "./init", line 85, in main File "/compile/sel4-tutorials-manifest/projects/sel4-tutorials/common.py", line 106, in init_directories return _init_build_directory(config, initialised, build_directory, tute_directory, output, config_dict=config_dict) File "/compile/sel4-tutorials-manifest/projects/sel4-tutorials/common.py", line 74, in _init_build_directory return sh.cmake(args + [tute_directory], _cwd=directory, _out=output, _err=output) File "/net/freenas/mnt/freenas-4TB/smore/.local/lib/python3.6/site-packages/sh.py", line 1549, in __call__ return RunningCommand(cmd, call_args, stdin, stdout, stderr) File "/net/freenas/mnt/freenas-4TB/smore/.local/lib/python3.6/site-packages/sh.py", line 793, in __init__ self.wait() File "/net/freenas/mnt/freenas-4TB/smore/.local/lib/python3.6/site-packages/sh.py", line 849, in wait self.handle_command_exit_code(exit_code) File "/net/freenas/mnt/freenas-4TB/smore/.local/lib/python3.6/site-packages/sh.py", line 877, in handle_command_exit_code raise exc sh.ErrorReturnCode_1: RAN: /bin/cmake -G Ninja -DTUT_BOARD=pc -DTUT_ARCH=x86_64 -DTUTORIAL_DIR=hello-camkes-0 -C ../projects/sel4-tutorials/settings.cmake /compile/sel4-tutorials-manifest/hello-camkes-0 STDOUT: STDERR:

2 2

Confirming correct syntax of items in devices.camkes.
by Travis Wheatley 01 Jul '20

01 Jul '20

I have been attempting to add support for both USB and SD persistent memory to my vm (See "Re: ramdisk vs. persistant rfs in VMs.” thread.). I seem to be having a problem with power management. In hopes of correcting this I wish to expose the power management unit to the VM. The related stanza looks like this in my device tree file. cci@fd6e0000 { compatible = "arm,cci-400"; reg = <0x0 0xfd6e0000 0x0 0x9000>; ranges = <0x0 0x0 0xfd6e0000 0x10000>; #address-cells = <0x1>; #size-cells = <0x1>; pmu@9000 { compatible = "arm,cci-400-pmu,r1"; reg = <0x9000 0x5000>; interrupt-parent = <0x4>; interrupts = <0x0 0x7b 0x4 0x0 0x7b 0x4 0x0 0x7b 0x4 0x0 0x7b 0x4 0x0 0x7b 0x4>; }; }; The PMU appears to be a child of cci. I am unsure of the proper syntax to use in my devices.camkes file. Since it is a child does one specify the path as /cci/pmu? Does the parent also have to be exposed to the vm? Here is what the related lines inmy devices.camkes look like. Is this correct? vm0.dtb = dtb([ {"path": "/cci@fd6e0000"}, {"path": "/cci/pmu@9000"},

1 0

Re: [seL4] ramdisk vs. persistant rfs in VMs.
by Zhuang, Siwei (Data61, Kensington NSW) 27 Jun '20

27 Jun '20

Hi Travis, It looks like the issue is related to the power management. You may need to read the board's manual(e.g UG1085) to find out if USB and SDHCI rely on any other devices which you also need to pass through to your Linux VM. You may also try to recompile your Linux kernel with PM disabled. If it doesn't work for you, then you'll have to debug your Linux kernel to find the root cause of the error. Good Luck. - Siwei ________________________________________ From: Travis Wheatley <travis.wheatley(a)emergentspace.com> Sent: Friday, 26 June 2020 6:25 AM To: devel(a)sel4.systems Cc: Zhuang, Siwei (Data61, Kensington NSW) Subject: Re: ramdisk vs. persistant rfs in VMs. I have made some good progress thanks to Siwei’s advice. I have modified my .dts file and have made a usb controller as well as the sdhci controller available to the VM. However, there still seems to be some issues at start up. Here is what dmesg has to say about the usb controller(s) root@xilinx-zcu102-2019_1:~# dmesg | grep usb [ 1.754678] usbcore: registered new interface driver usbfs [ 1.761934] usbcore: registered new interface driver hub [ 1.768958] usbcore: registered new device driver usb [ 3.827826] usbcore: registered new interface driver asix [ 3.834976] usbcore: registered new interface driver ax88179_178a [ 3.842998] usbcore: registered new interface driver cdc_ether [ 3.850682] usbcore: registered new interface driver net1080 [ 3.858146] usbcore: registered new interface driver cdc_subset [ 3.865948] usbcore: registered new interface driver zaurus [ 3.873301] usbcore: registered new interface driver cdc_ncm [ 3.895799] usbcore: registered new interface driver uas [ 3.902820] usbcore: registered new interface driver usb-storage [ 3.916716] usbcore: registered new interface driver uvcvideo [ 3.991358] usbcore: registered new interface driver bcm203x [ 3.998824] usbcore: registered new interface driver bpa10x [ 4.006182] usbcore: registered new interface driver bfusb [ 4.013424] usbcore: registered new interface driver btusb [ 4.028142] usbcore: registered new interface driver ath3k [ 4.201363] usbcore: registered new interface driver usbhid [ 4.208699] usbhid: USB HID core driver [ 4.224831] usbcore: registered new interface driver snd-usb-audio [ 5.181742] dwc3-of-simple ff9e0000.usb1: failed to add to PM domain domain3: -13 [ 5.191629] dwc3-of-simple: probe of ff9e0000.usb1 failed with error -13 Any clue? Regarding the SD card, it is partitioned with a boot partition where uboot and the .elf file live and the remainder is the free space I hope to use as the filesystem. Here is what dmesg has to say about the sdhc interface. root@xilinx-zcu102-2019_1:~# dmesg | grep sdhc [ 4.049894] sdhci: Secure Digital Host Controller Interface driver [ 4.058026] sdhci: Copyright(c) Pierre Ossman [ 4.063768] sdhci-pltfm: SDHCI platform and OF driver helper [ 5.209925] sdhci-arasan ff160000.mmc: failed to add to PM domain domain4: -13 [ 5.219468] sdhci-arasan: probe of ff160000.mmc failed with error -13 [ 5.351710] mmc0: sdhci: ============ SDHCI REGISTER DUMP =========== [ 5.360229] mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00000000 [ 5.368759] mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000 [ 5.377280] mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000 [ 290.055387] random: fast init done [ 5.385810] mmc0: sdhci: Present: 0x00000000 | Host ctl: 0x00000000 [ 5.394331] mmc0: sdhci: Power: 0x00000000 | Blk gap: 0x00000000 [ 5.402860] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x00000000 [ 5.411381] mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 [ 5.419902] mmc0: sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000 [ 5.428441] mmc0: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000 [ 5.436962] mmc0: sdhci: Caps: 0x00000000 | Caps_1: 0x00000000 [ 5.445491] mmc0: sdhci: Cmd: 0x00000000 | Max curr: 0x00000000 [ 5.454021] mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000 [ 5.462551] mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000 [ 5.471089] mmc0: sdhci: Host ctl2: 0x00000000 [ 5.477023] mmc0: sdhci: ============================================ Seems to be getting the same -13 error when setting up it’s domain. So… what do I need to do to make these devices accessible from the linux command line? On Jun 24, 2020, at 8:58 PM, Zhuang, Siwei (Data61, Kensington NSW) <Siwei.Zhuang(a)data61.csiro.au<mailto:Siwei.Zhuang@data61.csiro.au>> wrote: Hi Travis, The addresses are board specific. The document for your board is UG1085, https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultras… If all you need is a number, you can also find it in the dts files in u-boot, Linux kernel or seL4, https://github.com/seL4/seL4/blob/master/tools/dts/zynqmp.dts#L900, #L910 - Siwei ________________________________________ From: Travis Wheatley <travis.wheatley(a)emergentspace.com<mailto:travis.wheatley@emergentspace.com>> Sent: Thursday, 25 June 2020 5:49 AM To: devel(a)sel4.systems<mailto:devel@sel4.systems> Cc: Zhuang, Siwei (Data61, Kensington NSW) Subject: Re: ramdisk vs. persistant rfs in VMs. Thanks Siwei. This was very helpful. I do have a follow up question about the addresses used in the devices.camkes file. Are these board specific or standard locations for the microkernel? The board I am using is a zcu102. Not sure where/how to find the appropriate address to use for the sdhci device. — Travis On Jun 23, 2020, at 3:54 AM, Zhuang, Siwei (Data61, Kensington NSW) <Siwei.Zhuang(a)data61.csiro.au<mailto:Siwei.Zhuang@data61.csiro.au>> wrote: Hi Travis, If you only need one VM to access the SD card. You could pass-through the SD card controller to Linux, recompile the Linux kernel with the proper driver. Then passing your rootfs on SD card via Linux kernel boot parameters. An example can be found in the "camkes-arm-vm" repo. Have a read about the "TK1 configuration" on this page, https://docs.sel4.systems/projects/camkes-arm-vm/ The configuration code can be found here, https://github.com/SEL4PROJ/camkes-arm-vm/blob/master/apps/vm_minimal/tk1/d… https://github.com/SEL4PROJ/camkes-arm-vm/blob/master/apps/vm_minimal/tk1/d… If you need to share the SD card between an native seL4 application and a VM or among multiple VMs, you'll need a virtual SD card driver. We only have a virtual USB driver at the moment. Use it as a reference to make your virtual driver. The code can be found here, https://github.com/SEL4PROJ/seL4_projects_libs/blob/master/libsel4vmmplatsu… https://github.com/SEL4PROJ/camkes-arm-vm/blob/master/components/VM/src/mod… You can of course partition the SD card, if your board supports boot from SD card. Consult the board's manual regarding how to boot from SD card. Note that, the Linux VM would have the access to your boot partition, hence the seL4 boot image could be compromised. To avoid that, you'll need to intercept the SD card access from the VM. The code here demonstrates one way of doing it, https://github.com/SEL4PROJ/seL4_projects_libs/blob/master/libsel4vmmplatsu… Hope these helps. - Siwei ________________________________________ From: Devel <devel-bounces(a)sel4.systems<mailto:devel-bounces@sel4.systems>> on behalf of Travis Wheatley <travis.wheatley(a)emergentspace.com<mailto:travis.wheatley@emergentspace.com>> Sent: Tuesday, 23 June 2020 6:47 AM To: devel(a)sel4.systems<mailto:devel@sel4.systems> Subject: [seL4] ramdisk vs. persistant rfs in VMs. I’ve been working with VMs running under SEL4 on ARM hardware. I have been able to boot to a command prompt in a VM. However, the filesystem being used is a ramdisk. I need some sort of persistent storage, preferably a regular rfs that lives on an SD card. Not exactly sure what modifications to make and where to cause the kernel to use a persistent rfs rather than the ramdisk. Barring that, wondering if the SD card can be divided into multiple partitions such that one can be the boot partition and the other mounted to provide persistent storage space. Hoping one of y’all can point me in the right direction. — Travis _______________________________________________ Devel mailing list Devel(a)sel4.systems<mailto:Devel@sel4.systems> https://sel4.systems/lists/listinfo/devel

1 0

Re: [seL4] ramdisk vs. persistant rfs in VMs.
by Travis Wheatley 26 Jun '20

26 Jun '20

I have made some good progress thanks to Siwei’s advice. I have modified my .dts file and have made a usb controller as well as the sdhci controller available to the VM. However, there still seems to be some issues at start up. Here is what dmesg has to say about the usb controller(s) root@xilinx-zcu102-2019_1:~# dmesg | grep usb [ 1.754678] usbcore: registered new interface driver usbfs [ 1.761934] usbcore: registered new interface driver hub [ 1.768958] usbcore: registered new device driver usb [ 3.827826] usbcore: registered new interface driver asix [ 3.834976] usbcore: registered new interface driver ax88179_178a [ 3.842998] usbcore: registered new interface driver cdc_ether [ 3.850682] usbcore: registered new interface driver net1080 [ 3.858146] usbcore: registered new interface driver cdc_subset [ 3.865948] usbcore: registered new interface driver zaurus [ 3.873301] usbcore: registered new interface driver cdc_ncm [ 3.895799] usbcore: registered new interface driver uas [ 3.902820] usbcore: registered new interface driver usb-storage [ 3.916716] usbcore: registered new interface driver uvcvideo [ 3.991358] usbcore: registered new interface driver bcm203x [ 3.998824] usbcore: registered new interface driver bpa10x [ 4.006182] usbcore: registered new interface driver bfusb [ 4.013424] usbcore: registered new interface driver btusb [ 4.028142] usbcore: registered new interface driver ath3k [ 4.201363] usbcore: registered new interface driver usbhid [ 4.208699] usbhid: USB HID core driver [ 4.224831] usbcore: registered new interface driver snd-usb-audio [ 5.181742] dwc3-of-simple ff9e0000.usb1: failed to add to PM domain domain3: -13 [ 5.191629] dwc3-of-simple: probe of ff9e0000.usb1 failed with error -13 Any clue? Regarding the SD card, it is partitioned with a boot partition where uboot and the .elf file live and the remainder is the free space I hope to use as the filesystem. Here is what dmesg has to say about the sdhc interface. root@xilinx-zcu102-2019_1:~# dmesg | grep sdhc [ 4.049894] sdhci: Secure Digital Host Controller Interface driver [ 4.058026] sdhci: Copyright(c) Pierre Ossman [ 4.063768] sdhci-pltfm: SDHCI platform and OF driver helper [ 5.209925] sdhci-arasan ff160000.mmc: failed to add to PM domain domain4: -13 [ 5.219468] sdhci-arasan: probe of ff160000.mmc failed with error -13 [ 5.351710] mmc0: sdhci: ============ SDHCI REGISTER DUMP =========== [ 5.360229] mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00000000 [ 5.368759] mmc0: sdhci: Blk size: 0x00000000 | Blk cnt: 0x00000000 [ 5.377280] mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000000 [ 290.055387] random: fast init done [ 5.385810] mmc0: sdhci: Present: 0x00000000 | Host ctl: 0x00000000 [ 5.394331] mmc0: sdhci: Power: 0x00000000 | Blk gap: 0x00000000 [ 5.402860] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x00000000 [ 5.411381] mmc0: sdhci: Timeout: 0x00000000 | Int stat: 0x00000000 [ 5.419902] mmc0: sdhci: Int enab: 0x00000000 | Sig enab: 0x00000000 [ 5.428441] mmc0: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000 [ 5.436962] mmc0: sdhci: Caps: 0x00000000 | Caps_1: 0x00000000 [ 5.445491] mmc0: sdhci: Cmd: 0x00000000 | Max curr: 0x00000000 [ 5.454021] mmc0: sdhci: Resp[0]: 0x00000000 | Resp[1]: 0x00000000 [ 5.462551] mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000 [ 5.471089] mmc0: sdhci: Host ctl2: 0x00000000 [ 5.477023] mmc0: sdhci: ============================================ Seems to be getting the same -13 error when setting up it’s domain. So… what do I need to do to make these devices accessible from the linux command line?

1 0

ramdisk vs. persistant rfs in VMs.
by Travis Wheatley 25 Jun '20

25 Jun '20

I’ve been working with VMs running under SEL4 on ARM hardware. I have been able to boot to a command prompt in a VM. However, the filesystem being used is a ramdisk. I need some sort of persistent storage, preferably a regular rfs that lives on an SD card. Not exactly sure what modifications to make and where to cause the kernel to use a persistent rfs rather than the ramdisk. Barring that, wondering if the SD card can be divided into multiple partitions such that one can be the boot partition and the other mounted to provide persistent storage space. Hoping one of y’all can point me in the right direction. — Travis

2 3

CAmkES VM rootfs.cpio with Python3 Causes Error
by Turner, Ben 12 Jun '20

12 Jun '20

Hi, I have been attempting to create a VM to run as a CAmkES component, and it is a requirement that it has Python3. I have been using the vm_minimal app as a template to get started, and was successful at getting my own buildroot filesystem image running, however when I attempted to add the Python3 package, the resulting image resulted in the following error when it booted: ... <<seL4(CPU 0) [decodeInvocation/631 T0xfec34400 "rootserver" @106f0]: Attempted to invoke a null cap> create_objects@main.c:805 [Err seL4_InvalidCapability]: Untyped retype failed with unexpected error seL4 root server abort()ed Debug halt syscall from user thread 0xfec34400 "rootserver" halting... Kernel entry via Unknown syscall, word: 1 The only change I made to the image was to add the Python3 package, and that has caused this error. Is there something the vm_minimal app is missing that is required in order to get Python3 working? Kind regards, Ben Turner ________________________________________ Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom.Part of the Chemring Group. Registered in England & Wales. Registered No: 00267550 http://www.roke.co.uk _______________________________________ The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Limited and must not be passed to any third party without permission. This communication is for information only and shall not create or change any contractual relationship. ________________________________________

2 5

camkes-vm-linux tutorial issue
by Nanfang Hu 11 Jun '20

11 Jun '20

When I try to build the tutorial and run ninja I got the following error. [1/31] Performing build step for 'hello-app' ninja: no work to do. [3/31] Performing configure step for 'poke-module' FAILED: poke-module-stamp/poke-module-configure cd /home/weiqi/test/camkes-vm-linux_build/poke-module && /usr/local/bin/cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=/home/w eiqi/test/tools/seL4/cmake-tool/polly_toolchains/linux-gcc-32bit-pic.cmake -DLINUX_KERNEL_DIR=/home/weiqi/test/camkes-vm-linux_build/out/linux-4.8.16 -DMODULE_HELPERS_FILE=/home/weiqi/test/projects/camkes-vm-linux/linux-module-helpers.cmake -GNinja /home/weiqi/test/camkes-vm-linux/modules && /usr/local/bin/cmake -E touch /home/weiqi/test/camkes-vm-linux_build/poke-module-stamp/pok e-module-configure CMake Warning (dev) in CMakeLists.txt: No project() command is present. The top-level CMakeLists.txt file must contain a literal, direct call to the project() command. Add a line of code such as project(ProjectName) near the top of the file, but after cmake_minimum_required(). CMake is pretending there is a "project(Project)" command on the first line. This warning is for project developers. Use -Wno-dev to suppress it. -- [polly] Used toolchain: Linux / gcc / PIC / c++11 support / 32 bit CMake Error at CMakeLists.txt:11 (DefineLinuxModule): DefineLinuxModule Function invoked with incorrect arguments for function named: DefineLinuxModule -- Configuring incomplete, errors occurred! See also "/home/weiqi/test/camkes-vm-linux_build/poke-module/CMakeFil es/CMakeOutput.log". See also "/home/weiqi/test/camkes-vm-linux_build/poke-module/CMakeFil es/CMakeError.log". [4/31] Completed 'hello-app' ninja: build stopped: subcommand failed. >

2 2

question about creating threads in sel4 based system
by sergey volkovich 10 Jun '20

10 Jun '20

Cabulertion. I trying to create my own sel4 based system, and currently i cannot understand next thing after calling seL4_Untyped_Retype i will be must somehow put execution data in memory. It can be implemented by using seL4_TCB_WriteRegisters. -- sever99

2 1

RISC-V (RV64) is the third ISA with verified seL4
by Heiser, Gernot (Data61, Kensington NSW) 09 Jun '20

09 Jun '20

Dear seL4 community, I’m extremely pleased to announce that we have completed the functional correctness proof of seL4 on the RV64 ISA. Congratulations to our awesome Proof Engineering Team on achieving this major milestone for seL4! And many thanks to HENSOLDT Cyber for making it possible. My blog discusses provides a bit more context for this announcement: https://microkerneldude.wordpress.com/2020/06/09/sel4-is-verified-on-risc-v/ What we have now is the refinement proof from the seL4 formal spec to the C implementation, putting RV64 on the same level as x64 in terms of seL4 verification. The binary verification, which extends this refinement to the binary code of the kernel is progressing, stay tuned for more news on that in the foreseeable future. Gernot for the Trustworthy Systems team and the seL4 Foundation

1 0

seL4 + TrustZone: Spanning both worlds
by Nick Spinale 08 Jun '20

08 Jun '20

On TrustZone-enabled Arm systems, seL4 could span both the secure and normal worlds. To do so would require extending untyped and frame capabilities with a bit associating them with either the secure or non-secure physical address space. In this email, I’ll touch on what a software stack based on this idea might look like, why that’s interesting, and exactly what extensions to the kernel it would require. I’m interested in your thoughts and feedback on this informal proposal. If there’s interest, I’ll draft a patch to illustrate it more precisely. # TrustZone background The security of a TrustZone-enabled system is achieved by partitioning all of the SoC’s hardware and software resources so that they exist in one of two worlds - the secure world for the security subsystem, and the normal world for everything else. From the point of view of an ARMv8-A processor, the system has two physical address spaces: one for secure transactions and another for non-secure transactions. Page table entries contain a field called the NS (non-secure) bit, which determines whether a page is mapped from the secure or non-secure physical address space. Furthermore, the processor state contains a global NS bit, which can only be modified by software executing at the highest exception level, EL3. When the NS processor state bit is set, the processor is said to be executing in the non-secure state, and can’t issue secure bus transactions, regardless of the values of the NS bits in its translation tables. A typical TrustZone software stack hosts a TEE (Trusted Execution Environment) on secure-world resources, and a REE (Rich Execution Environment) on normal-world resources. A so-called “secure monitor” runs in EL3, and uses the NS processor state bit to implement a coarse context switch called a “world switch”. The simplicity of this coarse context switch minimizes the attack surface of the secure monitor. # seL4 + TrustZone A formally verified microkernel such as seL4 can be trusted to protect secure hardware resources, and the TEE they host, using translation tables alone. That is, seL4 allows for a design where the processor always runs in state NS=0 (“secure state”), and normal-world software is restricted to non-secure world hardware resources using just the NS bits in the translation tables controlled by seL4. Such a software stack, with seL4 spanning both the secure and non-secure worlds, is attractive on multiple fronts. seL4 provides a higher level of assurance than typical EL3 monitor firmware, which we can now eliminate from the TCB. seL4 also provides a richer API than typical EL3 firmware, allowing for security critical secure-world components to be developed and verified at a higher level of abstraction. Furthermore, while the two-world model is organized around just one strong security boundary, seL4 allows for an unbounded number of equally strong security boundaries, as isolation is based on translation tables rather than the less flexible NS processor state bit. This design allows a seL4-based system to utilize non-secure hardware resources, while protecting the kernel and sensitive components inside secure hardware resources. This permits a threat model similar to that of a typical TrustZone-based TEE (such as OP-TEE or Trusty), which includes some hardware attacks, but without limiting seL4 userland components to the secure world alone. Such a software stack has been especially interesting since the release of ARMv8.4-A, which enables EL2 in the secure state (S-EL2). seL4 running in S-EL2 can host a rich operating system such as Linux to drive non-secure hardware resources. Compare this to a seL4-based software stack running a Linux VM without the help of TrustZone. In particular, consider a case where the Linux VM drives most of the hardware platform’s devices via direct passthru access. Reasoning about the interactions between hardware components on a SoC is difficult. Even after correctly programming the SMMU, a great deal of SoC-specific detail must be covered in order to convince yourself that a driver or VM can’t violate its isolation indirectly through a device within its reach. This sort of reasoning is an active area of research (see, for example, the Barrelfish OS project). However, for use cases where the trust model aligns with the SoC’s boundary between secure and non-secure hardware resources, TrustZone provides a straightforward means of ensuring the protection of critical software components from those with access to non-secure devices. # Extending seL4 Currently, untyped objects are either general purpose memory or device memory. To support the design I’ve proposed, untyped objects would need to be extended with another dimension: secure memory or non-secure memory. Non-secure general purpose memory would be subject to the same restrictions as device memory, with the exception that frames derived from non-secure general purpose untyped may be used as IPC buffers. Unlike the general-purpose/device dimension, the secure/non-secure dimension affects the mapping of a frame. The kernel would set the NS bit in page table entries according to whether that frame is secure. This extension would require modifying just a few lines of code in the kernel itself and would, of course, be optional and configurable. - - - - Nick Spinale (nickspinale.com) Arm Research, Cambridge UK - - - - The ideas presented in this email constitute research activity at Arm rather than an official position or recommendation. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

3 3

Difficulty booting guest kernel on zcu102
by Travis Wheatley 04 Jun '20

04 Jun '20

I’ve been working with a VM and docker container created by the good folks at DornerWorks. I had a compile time error with the camkes-arm-vm-manafest tree called out in their "Getting Started” lab. However, I was able to successfully compile an image using the instructions and files in their single_vm_lab. I am loading that image onto an SD card with their pre-built boot.bin. At the U-boot prompt I load that image to 0x10000000 and subsequently type “go 0x10000000”. The image seems to start the initial boot just fine but I get an exception when it tries to jump to the kernel. image entry point. Looking at the value of esr_eli1 it appears that something is trying to write to a protected register. Wondering if there is some sort of switch setting on the board or special flags that need to be sent to u-boot to keep this from happening. Here is the console output: ZynqMP> fatload mmc 0 0x10000000 dorner 22183936 bytes read in 1472 ms (14.4 MiB/s) ZynqMP> go 0x10000000 ## Starting application at 0x10000000 ... ELF-loader started on CPU: ARM Ltd. Cortex-A53 r0p4 paddr=[10000000..1152e06f] No DTB passed in from boot loader. Looking for DTB in CPIO archive...found at 100f4058. Loaded DTB from 100f4058. paddr=[237000..23bfff] ELF-loading image 'kernel' paddr=[0..236fff] vaddr=[ff8000000000..ff8000236fff] virt_entry=ff8000000000 ELF-loading image 'capdl-loader' paddr=[23c000..1854fff] vaddr=[400000..1a18fff] virt_entry=4088d0 ELF loader relocated, continuing boot... Enabling MMU and paging Jumping to kernel-image entry point... ELF-LOADER: Synchronous exception received: esr_el1: 86000004 elr_el1: ff8000000000 spsr_el1: 600003c5 far_el1: ff8000000000 abort() called.

1 0

Builds
by Matt Youill 04 Jun '20

04 Jun '20

Hi, Am in the process of learning seL4 and have managed to get, build and run the tutorials, which is great. Now looking at creating an application and I have a question about seL4 builds. The documentation here... https://docs.sel4.systems/projects/buildsystem/incorporating.html refers to a build setup that AFAICT is different to the reference application, which I think is here... https://github.com/seL4proj/sel4webserver Which is the best approach to follow? Best, Matt

2 1

Re: [seL4] Threads tutorial fails to initialize
by Weiqi Hu 04 Jun '20

04 Jun '20

Thank you for the suggestion but it seems like I need to access the init file one directory above. In the case of seL4test and build-x86 it needs to be init-build.sh On Sun, May 31, 2020 at 9:14 AM laokz <laokz(a)foxmail.com> wrote: > Hi Weiqi, > > Did you try init-build.sh( > https://docs.sel4.systems/GettingStarted#setting-up-your-machine)? I > recall this like issue before. > > Regards, > laokz > > I tried adding the --plat argument but it's the same error. Also, no build > directory was created on the attempts. > > I didn't have the same problem with the capabilities, untyped, and mapping > tutorials but it appears something is different for the threads tutorial. > > On Sat, May 30, 2020 at 5:11 PM Chubb, Peter (Data61, Kensington NSW) < > Peter.Chubb(a)data61.csiro.au> wrote: > > > >>>>> "Weiqi" == Weiqi Hu <weiqi.hu(a)gmail.com> writes: > > > > Weiqi> Hi, I've tried to start the threads tutorial but it fails to > > Weiqi> initialize or create a build directory. Any hints for moving > > Weiqi> forward? > > > > Looks like you omitted the --plat argument. > > > > Try > > ../init --plat pc99 --tut threads --solution > > > > You may need to delete the build directory before this will work. > > > > -- > > Peter Chubb Tel: +61 2 9490 5852 > > http://ts.data61.csiro.au/ > > Trustworthy Systems Group CSIRO's > Data61 > _______________________________________________ > Devel mailing list > Devel(a)sel4.systems > https://sel4.systems/lists/listinfo/devel > >

2 2

constituting seL4 TSC meeting
by Klein, Gerwin (Data61, Kensington NSW) 03 Jun '20

03 Jun '20

The technical steering committee (TSC) of the seL4 Foundation had its constituting meeting on 20 May, and the meeting minutes [1] are now published on the TSC page of the foundation [2]. The TSC is the body that sets the technical direction of seL4 and its proofs, including processes, contributions, documentation, etc. This first TSC meeting was mostly about processes and setting things up — future TSC meetings are planned to be public, and will be announced on this mailing list. One of the first things the TSC would like to do is make seL4 and its related repositories easier to contribute to. You may have seen a few things that already have happened: - more content on the docs site at foundation launch - DCO instead of CLA - first direct github CI tests that run on pull requests for the seL4 and l4v repos Some of the things we are planning to do: - make seL4 code and proof regression tests available directly on github as much as possible, to make it easier to see what breaks verification and what not - open up issues and pull request management more to the community so that pull requests can become less of a bottleneck - publish the source of the sel4.systems site, so people can make contributions - more documentation for the proofs If you have ideas what else the TSC could do to encourage contributions, please let us know! Either here on the mailing list, or if you prefer, by email to me directly. Cheers, Gerwin (for the TSC) [1]: https://sel4.systems/Foundation/TSC/notes/tsc-meeting-2020-05-20.pdf [2]: https://sel4.systems/Foundation/TSC/

1 0

UNSW seL4 teaching videos available
by Heiser, Gernot (Data61, Kensington NSW) 02 Jun '20

02 Jun '20

Dear seL4 community, I’m pleased to announce yet another contribution of UNSW Sydney to the seL4 community: This year I’m making the seL4-related videos from my UNSW Advanced Operating Systems class freely available. You’ll find them at the UNSW CSeLearning COMP9242 YouTube channel: https://www.youtube.com/playlist?list=PLbSaCpDlfd6qLbEsKquVo3--0gwYBmrUV At present there are the first two modules, which provide some background on microkernels and seL4, and discuss the seL4 API. More material will show up over the next two months. The complete course material, including all lecture slides, the project spec and code, are available, as always, from the COMP9042 web site: https://www.cse.unsw.edu.au/~cs9242/current/ Enjoy, Gernot

2 1

mcs kernel compatible with camkes project
by Parvaneh Ahgajani 02 Jun '20

02 Jun '20

Hello all, I wanted to use camkes to create real-time application. In periodic application, it mentioned that "_period" and "_budget" only have affect on the MCS kernel. I tried to build application with kernel version 11.0.0-dev but it doesn't work. I wanted to know how I can have access to MCS kernel that is compatible with camkes project. Thank you, Parvaneh Aghajani.

2 1

Threads tutorial fails to initialize
by Weiqi Hu 31 May '20

31 May '20

Hi, I've tried to start the threads tutorial but it fails to initialize or create a build directory. Any hints for moving forward? weiqi@weiqi-ThinkPad-X250:~/sel4-tutorials-manifest-temp/threads$ sudo ../init --verbose --tut threads --solution Traceback (most recent call last): File "../init", line 96, in <module> sys.exit(main()) File "../init", line 85, in main args.task, initialised, tute_dir, build_dir, sys.stdout) File "/home/weiqi/sel4-tutorials-manifest-temp/projects/sel4-tutorials/common.py", line 100, in init_directories os.chdir(build_directory) FileNotFoundError: [Errno 2] No such file or directory: '/home/weiqi/sel4-tutorials-manifest-temp/threads_build'

2 2

Building picoserver example
by Russel emkil.minor 26 May '20

26 May '20

Dear seL4 developers, I am trying to built picoserver example https://github.com/seL4/camkes/tree/master/apps/picoserver <https://github.com/seL4/camkes/tree/master/apps/picoserver> using the following commands: $ ../init-build.sh -DPLATFORM=x86_64 -DCAMKES_APP=picoserver $ ninja But I am getting the following error: fatal error: pico_stack.h: No such file or directory Looks like I need to install libpicotcp. I found it here https://github.com/seL4/util_libs/tree/master/libpicotcp <https://github.com/seL4/util_libs/tree/master/libpicotcp> but no idea how to build and link to the example. Can you give me a hint how to proceed? Best regards, Ruslan Rezin.

2 1

seL4 Whitepaper Released
by Heiser, Gernot (Data61, Kensington NSW) 25 May '20

25 May '20

Dear seL4 community, I’m pleased to announce the seL4 Foundation whitepaper: The seL4 Microkernel – An Introduction This white paper provides an introduction to and overview of seL4. We explain what seL4 is (and is not) and explore its defining features. We explain what makes seL4 uniquely qualified as the operating-system kernel of choice for security- and safety- critical systems, and generally embedded and cyber-physical systems. In particular, we explain seL4’s assurance story, its security- and safety-relevant features, and its benchmark-setting performance. We also discuss typical usage scenarios, including incremental cyber retrofit of legacy systems. You can download it at https://sel4.systems/About/ Feedback welcome. Gernot PS: Some of you may have seen a pre-release version that was up on the Foundation web site since the Foundation launch. This is the complete version.

1 0

Trouble accessing linux guest through tun/tap
by Travis Wheatley 22 May '20

22 May '20

Greetings, I am working with the camkes-arm-vm qemu-arm-virt configuration. I started with the vm_minimal configuration and have added a tun/tap interface by creating the tap on my host thusly: # ip tuntap add tap0 mode tap # ip addr add 10.0.120.100/24 dev tap0 # ip link set dev tap0 up I have added support for what I beleive to be the appropriate interrupts by modifying my devices.camkes file thusly: vm0.untyped_mmios = [ "0x8040000:12", // Interrupt Controller Virtual CPU interface (Virtual Machine view) "0x10040000:17", // QEMU PCI MMIO "0x3eff0000:16", // QEMU PCI IO ports "0x40000000:29", // Linux kernel memory regions ]; vm0.dtb_irqs = [35, 36, 37, 38]; Additionally, I have modified the settings.camkes thusly: if(${PLATFORM} STREQUAL "qemu-arm-virt") # force cpu set(QEMU_MEMORY "2048") set(KernelArmCPU cortex-a53 CACHE STRING "" FORCE) set(VmInitRdFile ON CACHE BOOL "" FORCE) set(VmPCISupport ON CACHE BOOL "" FORCE) set(VmVirtioNetArping OFF CACHE BOOL "" FORCE) set(VmVirtioNetVirtqueue ON CACHE BOOL "" FORCE) # set(qemu_sim_extra_args "-netdev tap,id=mynet0,ifname=tap0,script=no,downscript=no -device virtio-net,netdev=mynet0,mac=52:55:00:d1:55:01") set(qemu_sim_extra_args "-net nic,model=e1000 -netdev tap,id=mynet0,script=no,ifname=tap0 -device virtio-net,netdev=mynet0,mac=52:55:00:d1:55:01") set(KernelArmExportPCNTUser ON CACHE BOOL "" FORCE) set(KernelArmExportPTMRUser ON CACHE BOOL "" FORCE) endif() This results in a tunl0 interface showing up on my linux guest. However, that interface does not have a mac address associated with it. I can use ifconfig to assign an IP address on the same subnet as the corresponding tap interface on the host. However, I can’t ping between the two. I thought this might be because I have VmVitruoNetArping set to OFF. However, I get compile time errors when I turn it on. Because the tunl0 inteface does not have the mac address specied in the qemu_sim_extra_args I am unsure of how to set up an arp table entry. Exctly what do I need to do to enable network communications between my linux guest and the host?

2 1

Help with creating a new project
by Yates, Tim 22 May '20

22 May '20

Hi, I am attempting to create a new CAmkES project. So far I have used the https://github.com/seL4/camkes-manifest.git repository and the https://github.com/SEL4PROJ/camkes-arm-vm-manifest repository and placed my .camkes file and components into the respective app folders for each. I then attempt to initialise my project as instructed here https://docs.sel4.systems/projects/camkes/ but it fails. It gives me the following error: hardware_gen.py: error: argument --dtb: can't open '/workspaces/microimpexor/seL4_build/build/kernel/kernel.dtb': [Errno 2] No such file or directory: '/workspaces/microimpexor/seL4_build/build/kernel/kernel.dtb' I am initialising my project with the following command: ../init-build.sh -DPLATFORM=qemu-arm-virt -DAARCH32=1 -DCAMKES_APP=appname -DSIMULATION=1 Some assistance on this matter would be greatly appreciated. Regards Tim Yates ________________________________________ Roke Manor Research Limited, Romsey, Hampshire, SO51 0ZN, United Kingdom.Part of the Chemring Group. Registered in England & Wales. Registered No: 00267550 http://www.roke.co.uk _______________________________________ The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Limited and must not be passed to any third party without permission. This communication is for information only and shall not create or change any contractual relationship. ________________________________________

2 1

some confuse about "bootstrap_use_current_simple" of bootstrap.c in libsel4allocman
by yadong.li 20 May '20

20 May '20

allocman_t *bootstrap_use_current_simple(simple_t *simple, size_t pool_size, void *pool) { allocman_t *allocman; int error; /* Initialize inside the current 1 level cspace as defined by simple */ allocman = bootstrap_use_current_1level(simple_get_cnode(simple), simple_get_cnode_size_bits(simple), simple_last_valid_cap(simple) + 1, BIT(simple_get_cnode_size_bits(simple)), pool_size, pool); if (!allocman) { LOG_ERROR("Failed to initialize an allocman"); return allocman; } ....... return allocman; } The params of "bootstrap_use_current_1level" below: cnode_size = simple_get_cnode_size_bits(simple), like 23, it is 8M endslot = BIT(simple_get_cnode_size_bits(simple)), also 8M I think we don't have so many endslot, because per slot is not only one byte Thank you very much

1 0

additional: some question about VisualCAmkES ？
by yadong.li 27 Apr '20

27 Apr '20

Hi， I found the VisualCAmkES tool can not parse grammar like import and marco in cmakes file, If I write very simple camkes file, only include one assembly and component. I want to know How can I use this VisualCAmkES tool to generate visual file in complex project like vm_minimal ? 发件人: yadong.li 发送时间: 2020年4月25日 21:06 收件人: 'devel(a)sel4.systems' 主题: some question about VisualCAmkES ？ Hi， I want to use VisualCAmkES for view，I follow the step of https://docs.sel4.systems/projects/camkes/visual-camkes/ I meet the below Problem， how can I resolve it ？ Thank you very much Syntax Error (u'/home/yadong.li/seL4_vm_11/ sel4_horizon/camkes-arm-vm/projects/vm/ apps/vm_cross_connector/vm_cross_connector.camkes:36:5: \x1b[31m\ x1b[1mVM_INIT_DEF\x1b[0m()', u' ', u"Syntax error in input at 'VM_INIT_DEF' (type ID) line 36 col 5", u"Syntax error in input at 'VM_GENERAL_COMPOSITION_DEF' (type ID) line 45 col 9", u"Syntax error in input at '(' (type _ANON_4) line 60 col 37")

1 0

some question about VisualCAmkES ？
by yadong.li 25 Apr '20

25 Apr '20

Hi， I want to use VisualCAmkES for view，I follow the step of https://docs.sel4.systems/projects/camkes/visual-camkes/ I meet the below Problem， how can I resolve it ？ Thank you very much Syntax Error (u'/home/yadong.li/seL4_vm_11/ sel4_horizon/camkes-arm-vm/projects/vm/ apps/vm_cross_connector/vm_cross_connector.camkes:36:5: \x1b[31m\ x1b[1mVM_INIT_DEF\x1b[0m()', u' ', u"Syntax error in input at 'VM_INIT_DEF' (type ID) line 36 col 5", u"Syntax error in input at 'VM_GENERAL_COMPOSITION_DEF' (type ID) line 45 col 9", u"Syntax error in input at '(' (type _ANON_4) line 60 col 37")

1 0

Re: [seL4] Trouble with the tun/tap interface in linux guest
by Travis Wheatley 22 Apr '20

22 Apr '20

Thank you for your reply Kent. I modified the devices.camkes in the corresponding project folder as suggested. However, I am still seeing the same behavior. Are there other items I need to add or is there something in the kernel that needs to be enabled? I tried swapping in an Ubuntu server 18.01 kernel. It boots, but I do not even see the tunl0 interface that I see when I boot the default vm_minimal image. Here is what the vm0.untyped_mmios block looks like in my devices.camakes file looks like vm0.untyped_mmios = [ "0x8040000:12", // Interrupt Controller Virtual CPU interface (Virtual Machine view) "0x10040000:17", // QEMU PCI MMIO "0x3eff0000:16", // QEMU PCI IO ports "0x40000000:29", // Linux kernel memory regions ]; vm0.dtb_irqs = [35, 36, 37, 38]; I found that the vm_multi project devices.camkes has similar stanzas in the vm0.untyped.mmios block. However, the Interrupt controller item has an additional 0x1000 token in it: "0x8040000:0x1000:12", // Interrupt Controller Virtual CPU interface (Virtual Machine view) I tried this in the vm_minimal configurationo but ../init.sh throws an error indicating that it doesn’t know how to parse that. I also was able to boot the vm_multi configuration in the emulator and noticed that it did, in fact, have both an eth0 and eth1 interface, but was not able to get them to work because the kernel seemed to be stuck in a loop looking for a non-existent DHCP server. Wondering if there is some other config somewhere that I need to get a working eth0 interface on the vm_minimal configuration? Message: 1 Date: Tue, 21 Apr 2020 20:57:24 +0000 From: Travis Wheatley <travis.wheatley(a)emergentspace.com<mailto:travis.wheatley@emergentspace.com>> To: "devel(a)sel4.systems<mailto:devel@sel4.systems>" <devel(a)sel4.systems<mailto:devel@sel4.systems>> Subject: [seL4] Trouble with the tun/tap interface in linux guest Message-ID: <207FF441-86A1-4CE3-88AD-8BACC908138D(a)emergentspace.com<mailto:207FF441-86A1-4CE3-88AD-8BACC908138D@emergentspace.com>> Content-Type: text/plain; charset="utf-8" Thanks to recent patches I have been able to build and boot the linux guest kernel under the simulator in the camkes-arm-vm project using the vm_minimal configuration. However, I am having trouble accessing it via the network interface. First I set up a tap interface as follows: # sudo ip tuntap add tap0 mode tap # sudo ip addr add 10.0.120.100/24 dev tap0 # sudo ip link set dev tap0 up Then I start the simulation using the following command line, which I believe should make the tap interface appear as an e1000 nic to the guest kernel: ./simulate --extra-qemu-args="-net nic,model=e1000 -net tap,script=no,ifname=tap0? In the linux guest the ?ip a? command shows that there is a tunl0 network device available. I have tried a couple of methods of activating it including using ifconfig to bring it up and assign it an ip address as well as the ?ip link set tun0 up? followed by the ?ip addr add 10.0.120.1/24 dev tunl0? command. According to ifconfig both of these bring the interface up and provide it with an ip address. However, I can?t ping the tap ip address from the guest nor can I ping the guest tunl0 interface from another console on the host. So, what am I missing? ------------------------------ Message: 2 Date: Tue, 21 Apr 2020 23:09:16 +0000 From: "Mcleod, Kent (Data61, Kensington NSW)" <Re: [seL4] Trouble with the tun/tap interface in linux guest> To: Travis Wheatley <travis.wheatley(a)emergentspace.com<mailto:travis.wheatley@emergentspace.com>>, "devel(a)sel4.systems<mailto:devel@sel4.systems>" <devel(a)sel4.systems<mailto:devel@sel4.systems>> Subject: Re: [seL4] Trouble with the tun/tap interface in linux guest Message-ID: <SYXPR01MB0832783D9CD6B3B03B0F04FFABD50(a)SYXPR01MB0832.ausprd01.prod.outlook.com<mailto:SYXPR01MB0832783D9CD6B3B03B0F04FFABD50@SYXPR01MB0832.ausprd01.prod.outlook.com>> Content-Type: text/plain; charset="iso-8859-1" It could be that the camkes configuration doesn't pass through the PCI device to the Linux guest? You need to add the Interrupts and PCI MMIO configurations below: ? ? ? ? vm0.untyped_mmios = [ ? ? ? ? ? ? ? ? ? ? "0x8040000:12", // Interrupt Controller Virtual CPU interface (Virtual Machine view) ? ? ? ? ? ? ? ? ? ? "0x10040000:17", // QEMU PCI MMIO ? ? ? ? ? ? ? ? ? ? "0x3eff0000:16", // QEMU PCI IO ports ? ? ? ? ? ? ? ? ? ? "0x40000000:29", // Linux kernel memory regions ? ? ? ? ? ? ? ? ? ? ]; ? ? ? ? vm0.dtb_irqs = ?[35, 36, 37, 38]; The device should then appear in the guest under eth0. Kent. ------------------------------ Subject: Digest Footer _______________________________________________ Devel mailing list Devel(a)sel4.systems<mailto:Devel@sel4.systems> https://sel4.systems/lists/listinfo/devel ------------------------------ End of Devel Digest, Vol 71, Issue 24 *************************************

1 0

Trouble with the tun/tap interface in linux guest
by Travis Wheatley 22 Apr '20

22 Apr '20

Thanks to recent patches I have been able to build and boot the linux guest kernel under the simulator in the camkes-arm-vm project using the vm_minimal configuration. However, I am having trouble accessing it via the network interface. First I set up a tap interface as follows: # sudo ip tuntap add tap0 mode tap # sudo ip addr add 10.0.120.100/24 dev tap0 # sudo ip link set dev tap0 up Then I start the simulation using the following command line, which I believe should make the tap interface appear as an e1000 nic to the guest kernel: ./simulate --extra-qemu-args="-net nic,model=e1000 -net tap,script=no,ifname=tap0” In the linux guest the “ip a” command shows that there is a tunl0 network device available. I have tried a couple of methods of activating it including using ifconfig to bring it up and assign it an ip address as well as the “ip link set tun0 up” followed by the “ip addr add 10.0.120.1/24 dev tunl0” command. According to ifconfig both of these bring the interface up and provide it with an ip address. However, I can’t ping the tap ip address from the guest nor can I ping the guest tunl0 interface from another console on the host. So, what am I missing?

2 1