Hi,
The problem is that there isn't any untyped memory available to make a 4K page
at address 0x4a101200 (if you notice carefully, this address isn't page
aligned).
The seL4DTBHardware connector doesn't support the AM335x board as the format of
the interrupt fields in the DTS doesn't follow
directory, depending on which manifest you initialised your project from.
Sincerely,
Damon
From: KAP Benjamin
Sent: Wednesday, 19 June 2019 11:34 AM
To: Lee, Damon (Data61, Kensington NSW); devel@sel4.systems
Subject: AW: Beaglebone Black: failed to find device frame
of the util_libs repository.
Sincerely,
Damon
From: KAP Benjamin
Sent: Tuesday, 25 June 2019 7:17 AM
To: Lee, Damon (Data61, Kensington NSW); devel@sel4.systems
Subject: AW: Beaglebone Black: failed to find device frame
Hello
Thank you for your help so far. I still have some
Hi yk,
The .camkes files can be preprocessed by the C preprocessor.
To do this, you'll need to turn on the CAmkESCPP CMake flag by appending this
line to the CMakeLists.txt file for your CAmkES component:
set(CAmkESCPP ON CACHE BOOL "" FORCE)
You could then define flags inside a header
_
From: yogidk
Sent: Monday, 20 May 2019 7:12 PM
To: Lee, Damon (Data61, Kensington NSW); devel@sel4.systems
Subject: Re: [seL4] How to add conditional compilation in .Camkes files
Hi Damon,
Thanks for the reply.
In my CmakeLists.txt, I have added the define as you mentioned:
Hi Benjamin,
The reason that you are getting those problems is because of the lack of
support for Beaglebone for the Ethdriver component. The picoserver application
uses the Ethdriver component to interface with the Ethernet device and the
component itself relies on the Ethernet drivers
Hi Amit,
I'd like to apologise first for errors in the tutorials. The first hint for
Task 8 of this tutorial should say: "use attributes ._access" instead.
As for the fault handler, I assume that you didn't get a fault where we
intended it to (writing to 'd_typed').
The checks aren't really
Hi Zippy,
> The assert is looking for the buffer to be a multiple of 16MiB but
> the ROUND_UP_UNSAFE is only doing working to a multiple of 4KiB.
> PAGE_SIZE_4K is hard coded in the template but the alignment has
> changed from 12bit to 24bit so CAmkES is aware of the large data
> structure.
>
> So a solution would be to pad and align the data structure to be a
> multiple of 16MiB or you could declare the backing dataport to be a
> 64MiB sized buffer and then cast it to be whatever you want in the C
> source code. E.g.
>
> component Foo {
> dataport Buf(67108864)
Hi Austin,
Glad to see that you resolved the locale issue.
> After the project built successfully, I tired executing ./simulate
> and I got the following assertion:
>
> Assertion failed: free_slot_end - free_slot_start >=
> CONFIG_CAPDL_LOADER_MAX_OBJECTS (../projects/camkes/capdl/capdl-
>
Hi yk,
> I would like to know if the CamkES has support for wait on multiple
> signal events ?
CAmkES currently does not have support for waiting on multiple signal
events on a single notification. It is however, possible to do so by
creating a new CAmkES connector.
You can take a look at the
with each other.
Sincerely,
Damon
From: Matthew Fernandez
Sent: Tuesday, 16 July 2019 10:32 AM
To: Amit Goyal
Cc: Mcleod, Kent (Data61, Kensington NSW); devel@sel4.systems; Lee, Damon
(Data61, Kensington NSW)
Subject: Re: [seL4] Understanding Camkes Dataport
Hi Austin,
The problem lies in this line:
> 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.
So if you override your locale to UTF-8, the problem should go away. A
possible solution would be:
Hi Zhonghao,
> It seems like there should be a file "menuconfig" or some other
> similar object I can modify. But I cannot find such an object. I
> would appreciate if you could give me any suggestions. Thank you!
Some of the information on that page is somewhat out of date, as we've
since
Hello Parvneneh,
> I am trying to implement a simple demo on sel4 using camkes.
> I need to add some external hardware like sensors to my demo.
> For this purpose I need GPIO programming.
> Could you please point me to some example GPIO components?
We do not have a GPIO component, but we are
Hello Parveneh,
> I am trying to implement a simple demo on sel4 using camkes.
> I need to add some external hardware like sensors to my demo.
> For this purpose I need GPIO programming.
> Could you please point me to some example GPIO components?
We do not have a GPIO component, but we are
Hello Parveneh,
> I am trying to implement a simple demo on sel4 using camkes.
> I need to add some external hardware like sensors to my demo.
> For this purpose I need GPIO programming.
> Could you please point me to some example GPIO components?
We do not have a GPIO component, but we are
Hello Abdi,
> I was trying to build camkes-vm-crossvm tutorials by using "./init --
> tut camkes-vm-crossvm" and it initiate some folder with some file and
> some folder is empty and some are missing.So can someone help me how
> to fix it,and this the following is it output.
This tutorial is
Hello yadong,
> Hi
> I compile camkes_arm_vm with tx1 vm_minimal
> Command:
> ../init-build.sh -DAARCH64=TRUE -DCAMKES_VM_APP=vm_minimal
> -DPLATFORM=tx1
> Buf output file is not elf
> # aarch64-linux-gnu-objcopy -O binary images/capdl-loader-image-arm-
> tx1 sel4-vmm-minimal
>
Hello Parvaneh, (sorry if I got your name wrong on my first response)
> I'm using Beaglebone black board for my demo.
> It seems that there is not GPIO driver for this platform.
> I wanted to know is there any documentation of GPIO driver for me to
> understand the other platforms driver and
Hi Parvaneh,
> I am trying to have my own seL4 demo on Sabre Lite board.
> I am using this command to create the image file:
> ../init-build.sh -DPLATFORM=sabre -DCROSS_COMPILER_PREFIX=arm-linux-
> gnueabi- -DCAMKES_APP=adder
>
> ...
>
> ELF-loader started on CPU: ARM Ltd. Cortex-A9 r2p10
>
Hi Parvaneh,
> By calling "gpio_init_pin(ALARM_PIN= 28, 0);" I am getting this
> error:
> Assertion failed: bank->data == v
> (PATH/projects/util_libs/libplatsupport/src/plat/imx6/gpio.c:
> imx6_gpio_write: 144)
> How can I fix this error? How should I specify the GPIO pins?
The assertion is
Hi Michael,
> Besides defining the hardware component and this connection in
> Camkes, is there anything else I must do? I will appreciate any
> guidance on this matter.
There shouldn't be anything else that you should need to do as long as
the connection and the hardware component is described
Hi Parvaneh,
> Hello all,
> I find your response to my question in Dvel Archive. I changed the parameter
> of gpio_new() that I am calling in my gpio_init_pin() (I changed it from 0 to
> 1 to have output direction).
> But I keep getting same error:
> imx6_gpio_init@gpio.c:96 Invalid GPIO
>
Hi yadong,
> static int alloc_free_io_port_range(vmm_io_port_list_t *io_list,
> ioport_range_t *io_range)
> {
> uint16_t free_port_addr = io_list->alloc_addr;
> if (free_port_addr + io_range->size < free_port_addr) {
> /* Possible overflow */
> return -1;
> }
>
Hi Travis,
For networking to work on the qemu-arm-virt platform, the networking device has
to be passthrough'd to the Linux guest.
We have an example of this in the sel4webserver project [1] which uses a Linux
guest VM to run a web server that serves static pages.
This file [2], describes the
Hi Tim,
Do you have a copy of the QEMU ARM emulator (qemu-system-arm)?
There are some scripts [1] in the kernel repository which uses the emulator to
generate a copy of the DTS and DTB of the platform.
Note that for the qemu-arm-virt platform, the minimum required version of QEMU
is 4.1.1.
Hi Chris,
> 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
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
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
Hi Ruslan,
There seems to be a race with the CMake configuration of the external libraries
that we haven't been able to fix yet.
If you run CMake again, i.e.:
$ cmake .
$ ninja
Then it should pick up the external libpicotcp project and build it.
Regards,
Damon
Hi Ben,
My guess is that there's something fishy going on with the bootinfo that is
passed into the capDL loader application which initialises the CAmkES system. I
don't have much information to go on, so I need to ask you to do a favour for
me.
Is it possible if you can re-run your
Hi Sachin,
> 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
>
Hi sever99,
> 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.
After creating a TCB with
Hi Nanfang,
> 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'
> ...
> CMake Warning (dev) in CMakeLists.txt:
> No project() command is
Hi Ben,
Sorry, it took so long to get back to you, I was quite busy and I had to do a
little research for your questions.
I'm not confident I'm correct in some of these answers as I mostly work above
the kernel.
Q: Why are there two separate memory regions defined here?
*and*
Q: Out of the
Hi Matt,
> 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
The build setup of the reference
Hi Nkem,
> 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:
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
Hi Chris,
> Thanks Damon for your help!
> I've added the required "simple" attribute to the assembly
> configuration:
> ...
> 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
Hi Nkem,
> 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
41 matches
Mail list logo
