- Devel - lists.sel4.systems

Tutorial app hello-camkes-mcs not working
by Nicholas VanderStel 24 Jun '17

24 Jun '17

I've been able to build and run the hello-camkes-mcs example app from the camkes-mcs-tutorials.xml manifest both on a SabreLite board and in QEMU. However, when I try to run the app with the budget and period values given in the solution file, the client tasks don't appear to be running as they should. See the output from running on the SabreLite here: https://pastebin.com/RM0aisyF After that point it seems to hang. I tried smaller budget & period values and have been able to get one client task running, but the second task doesn't appear to be running. Has anyone been able to run this example with different results? Thanks, Nick VanderStel

1 0

Help with libethdriver
by Fabrizio Bertocci 22 Jun '17

22 Jun '17

Hi all, I am facing an issue with our existing project (currently based on seL4 1.0). I am in the process of migrating our project to the latest version of seL4. After all the required changes I am facing a problem I need some help. In our code, we use libplatsupport for timer & serial I/O as well as the libethdriver in order to use the network interface of the IMX6 board. The problem appears that the IOMUX device registers are mapped twice. A first time from libplatsupport (and never released): -> sel4platsupport_new_io_ops() -> calls: mux_sys_init() -> calls the macro: MAP_IF_NULL(io_ops, IMX6_IOMUXC, _mux.iomuxc); This end up mapping the device region IMX6_IOMUXC: 0x20e0000 - 0x20e100 (size_bits=12). So far so good... but then they are mapped again from the ethernet driver: ethif_new_lwip_driver_no_malloc() -> call my initialization fn -> call ethif_imx6_init() -> call setup_iomux_enet() that end up mapping again the region @ IOMUXC_PADDR = 0x20e1000 This second time, the mapping function _utspace_split_alloc fails because apparently the region 0x20e000 has been already mapped (and is not in the regions available). If I comment out the call to mux_sys_init() in libsel4platsupport_new_io_ops() my ethernet driver successfully initialize (but clearly that's not the correct workaround). Any suggestions? Regards, Fabrizio Bertocci Real-Time Innovations, Inc. Sunnyvale, CA

2 1

Questions about TK1-SOM Memory Management
by Daniel Wang 22 Jun '17

22 Jun '17

Hi Adrian, Thank you very much for your explain. I might have some misunderstanding about the source code. First may I ask what the kernel window means? Does it means the virtual memory space kernel can access (through pptr_t)? I can see the dev_p_regs[] (kernel/src/plat/tk1/machine/hardware.c) has multiple parts: the first is the RAM part, VM_HOST_PA_START - VM_HOST_PA_START + VM_HOST_PA_SIZE (0xb0000000 — 0xf0000000), the rest are real device region from 0x01000000 - 0x7c000000 approximately. I guess my question is why put the second half as a “device” instead of putting it together in avail_p_regs[]? Is it somehow due to the support of virtualization? Here is the booting procedure according to my understanding, could you take a look and see if I got it right? 1. the code start at the ELF-loader main() (tools/elfloader/src/arch-arm/boot.c) which is loaded in physical memory 0x82000000 for TK1 (tools/elfloader/gen_boot_image.sh) 2. the boot code unpack the ELF and find the kernel image and the user-land image, the kernel is loaded at 0x80000000 the user land image is loaded at 0x80037000 approximately 3. MMU is enabled and a “boot" page directory is created that maps physical 0x80000000 to (0xe0000000 - 0xf0000000) 4. enter the kernel code _start, which setup up vector table and kernel stack; then init_kernel(); then try_init_kernel() calls map_kernel_window() I’m not sure why map_kernel_windows() remap the virtual address kernelBase (start from 0xe0000000) to physical address physBase (0x80000000) again or did I miss anything? Also I’m not sure what those armHSGlobalPGD[], armHSGlobalPD[] for, I assume it is for context switch? (deleted diagram due to size limit) Thanks -Dan

2 3

drivers in seL4
by 杰尔米 22 Jun '17

22 Jun '17

Hi all， I want to know more about the mechanism of device driver in seL4. How does seL4 support userspace drivers? if I want to write a driver(e.g. serial port) base on seL4, how to do that? can any one help? Best Regards! Jeremy

3 2

Questions about TK1-SOM Memory Management
by Daniel Wang 20 Jun '17

20 Jun '17

Hi all, I’m trying to get a better understand about the implementation details of seL4 for TK1-SOM. Most of the code are very clear, but I’m little confused on the available physical memory in TK1-SOM. I’m wondering why In the hardware.c file (/kernel/src/plat/tk1/machine/hardware.c), the avail_p_regs[] ={.start = 0x80000000, .end = 0xa7f00000 } instead of 0x80000000 - 0xffffffff? Thank you very much! -Dan

2 1

Linux binaries constructed by Buildroot cannot run on tk1 board
by li94575 20 Jun '17

20 Jun '17

Hi， I use Buildroot 2016.08.1 with the config "buildroot_tk1_initrd_defconfig" to compile linux-tegra(https://github.com/SEL4PROJ/linux-tegra/tree/sel4), everything goes well. But the linux binary cannot output any logs, camkes-arm-vm stops at “Starting VM”. Can anyone tells me where might be wrong? I have tried using cross-compiler arm-none-linux-gnueabi-(2014.05) to compile linux-tegra, and that linux binary can work.

2 4

seL4test with 4.0, 5.1 failed on Ubuntu
by Daniel Wang 16 Jun '17

16 Jun '17

Hi all, I’m testing the new versions of seL4 (,4.0, 5.0, 5.1, etc.) using the sel4test-manifest. I tried both Ubuntu 16 and Ubuntu 14. For 3.2 version both I32 and KZM_simulation built just fine. However for the higher version (4.0. 5.1, 5.2) only I32 built properly. KZM_simulation keep failing on both Ubuntu 14 and 16. Anyone has the similar issues? Thanks -Dan FYI: [apps/sel4test-tests] done. [KERNEL] [MKDIR] src/arch/arm/api [PBF_GEN] arch/object/structures.pbf [PBF_GEN] arch/api/shared_types.pbf [PBF_GEN] plat/machine/hardware.pbf [PBF_GEN] api/types.pbf [BF_GEN] arch/object/structures_gen.h [BF_GEN] arch/api/shared_types_gen.h [BF_GEN] plat/machine/hardware_gen.h [BF_GEN] api/types_gen.h [CPP] src/arch/arm/armv/armv6/machine_asm.s_pp [AS] src/arch/arm/armv/armv6/machine_asm.o [CPP] src/arch/arm/32/halt.s_pp [AS] src/arch/arm/32/halt.o [CPP] src/arch/arm/32/head.s_pp [AS] src/arch/arm/32/head.o [CPP] src/arch/arm/32/idle.s_pp [AS] src/arch/arm/32/idle.o [CPP] src/arch/arm/32/traps.s_pp [AS] src/arch/arm/32/traps.o [CPP] src/arch/arm/32/hyp_traps.s_pp [AS] src/arch/arm/32/hyp_traps.o [TOUCH] sources_list_updated [CPP_GEN] kernel_all.c [CPP] kernel_all.c_pp [CP] kernel_final.c [CC] kernel_final.s /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c: In function ‘doFlush’: /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1929:10: error: ‘ARMPDClean_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1929:10: note: each undeclared identifier is reported only once for each function it appears in /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1930:10: error: ‘ARMPageClean_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1933:10: error: ‘ARMPDInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1934:10: error: ‘ARMPageInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1937:10: error: ‘ARMPDCleanInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1938:10: error: ‘ARMPageCleanInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1941:10: error: ‘ARMPDUnify_Instruction’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:1942:10: error: ‘ARMPageUnify_Instruction’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c: In function ‘decodeARMPageDirectoryInvocation’: /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2217:10: error: ‘ARMPDClean_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2218:10: error: ‘ARMPDInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2219:10: error: ‘ARMPDCleanInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2220:10: error: ‘ARMPDUnify_Instruction’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c: In function ‘decodeARMPageTableInvocation’: /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2335:21: error: ‘ARMPageTableUnmap’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2344:41: error: ‘ARMPageTableMap’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c: In function ‘decodeARMFrameInvocation’: /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2440:10: error: ‘ARMPageMap’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2562:10: error: ‘ARMPageRemap’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2680:10: error: ‘ARMPageUnmap’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2699:10: error: ‘ARMPageClean_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2700:10: error: ‘ARMPageInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2701:10: error: ‘ARMPageCleanInvalidate_Data’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2702:10: error: ‘ARMPageUnify_Instruction’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2772:10: error: ‘ARMPageGetAddress’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c: In function ‘decodeARMMMUInvocation’: /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2818:45: error: ‘ARMASIDControlMakePool’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/src/arch/arm/32/kernel/vspace.c:2887:45: error: ‘ARMASIDPoolAssign’ undeclared (first use in this function) /home/daniel/Desktop/sel4test/kernel/Makefile:566: recipe for target 'kernel_final.s' failed make[1]: *** [kernel_final.s] Error 1 tools/common/project.mk:254: recipe for target 'kernel_elf' failed make: *** [kernel_elf] Error 2

2 2

seL4_Fault_t and friends seems to be missing in user libsel4
by Alexander Boettcher 15 Jun '17

15 Jun '17

Hello, if I compile and link seL4 5.2.0 ARCH=x86 PLAT=pc99 SEL4_ARCH=x86_64 make and I finally try to use the generated syscall/libsel4 headers, the compiler complains about missing seL4_Fault types and functions in libsel4/sel4_arch_include/x86_64/sel4/sel4_arch/faults.h like seL4_Fault_t seL4_Fault_tag seL4_Fault_VMFault_new and a lot more. These structs and functions seems to be generated only for the kernel side, e.g. in kernel_final.c they show up, but there are no traces of them on the user level side. Do I just miss a configuration option ? Thanks, -- Alexander Boettcher Genode Labs http://www.genode-labs.com - http://www.genode.org Genode Labs GmbH - Amtsgericht Dresden - HRB 28424 - Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 4

[Camkes] Is there any way to declare hierarchical header files and does CamKES support C++ boost preprocessor?
by Tran Cuong 14 Jun '17

14 Jun '17

Hello everybody, I'm conducting a C-project, in which the code is utilizing boost library to define several macros. This source code is running well in Linux and using only standard C library (I had tested this libraries individually by some mini-programs on CamKES). My project is organized as follows: - Top folder: + "components" folder contains my c code + "include" folder contains 1 .h file boost1.h and 1 folder test ++ sub-folder "test" contains 1 file boost2.h ++ content of boost1.h is just include "test/boost2.h" + "Makefile" is declared as below: TARGETS := $(notdir ${SOURCE_DIR}).cdl ADL := tst-macro.camkes Client_CFILES := \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/src/*.c)) \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/src/plat/${PLAT}/*.c)) \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/src/arch/${ARCH}/*.c)) Client_ASMFILES := \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/crt/arch-${ARCH}/crt0.S)) \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/src/*.S)) \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/src/arch/${ARCH}/*.S)) \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/src/plat/${PLAT}/*.S)) Client_HFILES := \ $(patsubst ${SOURCE_DIR}/%,%,$(wildcard ${SOURCE_DIR}/components/Client/include/*)) include ${PWD}/tools/camkes/camkes.mk - This above Makefile, I imitated from another application, and when I compiled the project, there are some errors related to directory of "test/boost2.h". I suspect that there is something wrong with Client_HFILES declaration, since maybe it is only valid for a list of .h files, not for hierarchical folders. - I really want to dive into CamKES, but I only have a little knowledge about this. My project is due so I hope to get some positive advice from you for 2 questions: + The right way to declare multi-level libraries as in my example. + Besides, does CamKES support boost preprocessing lib. Currently I'm using the toolchain arm-none-eabi- Thank all of you for the time and attention. Dinh-Cuong -- ------------------- TRAN Dinh Cuong (Mr) Email : cuongtd4(a)gmail.com

2 2

Trustworthy and mixed critical
by Jonathan C Day 14 Jun '17

14 Jun '17

Dear all, The first of these terms has an... interesting history. In a nutshell, it's not always used appropriately. Clearly that's not going to be the case with SEL4, but what exactly is meant? Mixed critical is another term that I'm cautious over. It's not completely clear to me if the mixing refers to relaxed constraints for utilisation reasons or something else. (Correct me if I'm mistaken, but I don't think SEL4 implements FLASK, which would be the obvious way to provide differing constraints, relaxed constraints within the trusted computing model. It's totally the wrong level.) I have absolutely no doubt SEL4 will retain all the provable integrity ever claimed (by anyone involved), but this experimental-proto-main branch confuses me on what fundamentally changes. Jonathan Day

2 1