l4-hackers

l4-hackers@os.inf.tu-dresden.de

2827 discussions

Doing simple I/O in clntsrv example
by Valentin Hauner 22 May '14

22 May '14

Hi! I'm having some trouble with doing simple I/O actions in the clntsrv example (/src/l4/pkg/examples/clntsrv). I want the client to enter minuend and subtrahend himself, so I've added the following code to client.cc: > printf("Please enter minuend and subtrahend: \n"); > l4_uint32_t val1, val2; > std::cin >> val1 >> val2; iostream is included at the beginning of the file. However, the linker has some serious problems: > ==> Linking ex_clntsrv-client > client.o: In function `main': > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::cin' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > client.o: In function `__static_initialization_and_destruction_0': > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::Init()' > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::~Init()' > make[1]: *** [ex_clntsrv-client] Error 1 > make: *** [/home/hnr/l4reb/pkg/examples/clntsrv/OBJ-x86_586-l4f] Error 2 I did not change the Makefile, so g++ is used for compiling (and not gcc). I've added > CXX_FLAGS = -lstdc++ but that doesn't help. I'm using update-alternatives to have different versions of g++ installed simultaneously. Currently, the link points to g++-4.7. But using g++-4.4 does not solve the problem either. Thanks in advance for support!

2 6

interfaces of scheduler Fiasco
by Bouchra Elouri 21 May '14

21 May '14

hello I'm currently reading the code of schudeler fiasco.oc to have an idea about the internal and external interfaces of the scheduler. Can you tell me what exactly are the codes that I have read so I can know the scheduler interfaces (ie with which it communicates) thank you

2 1

Porting Fiasco+L4re to DaVinci DA850 - Linux time wrong
by Peter Howard 21 May '14

21 May '14

I've now got L4Linux running on top of Fiasco+L4re on the DA850. However there appears to be something wrong with the time. Time seems to be passing at a rate of 10-1 (i.e. 1 elapsed second == 10 reported seconds) in Linux. If I change the default Hz rating the L4Linux config (from 100Hz) in either direction L4Linux either hangs or slows down dramatically. If I change the period in the timer driver (in the Fiasco bsp directory) things hang earlier. For the Fiasco BSP I'm using: * timer_tick-single-vector for timer_tick_IMPL, * clock_generic for clock_IMPL, * a da850 timer driver for timer_IMPL. Can someone enlighten me as to how it should work? Thanks -- Peter Howard <pjh(a)northern-ridge.com.au>

2 3

Can you check this patch file(imx6q-fec.patch) ?
by Taeung 20 May '14

20 May '14

Hello, l4 hackers :-) To secure Ethernet on L4 Linux, I've modified source code with yeongchann and we succeeded to obtain Ethernet. we've used 'l4re-snapshot-2014022818' and Freescale i.MX6 Quad SABRE SD board (ARMv7a) I don't know whether this patch can contribute l4 project. But can you check 'imx6q-fec.patch' ? Attached patch is 1. to change UART2 to UART1 for imx6q sabresd (learned by Ahmed Ammar) and 2. to fix compile error(fiasco and l4linux) , 3. to modify source related to FEC ethernet. To put it concretely... ===== About UART for imx6q sabresd ===== (learned by Ahmed Ammar) *1) mem_layout-arm-imx.cpp* (src/kernel/fiasco/src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp) * 2) uart-imx.cpp* (src/kernel/fiasco/src/kern/arm/bsp/imx/uart-imx.cpp) * 3) imx.cc* (src/l4/pkg/bootstrap/server/src/platform/imx.cc) ============================== ===== About compile error ===== *1) tb_entry_output.cc* (src/kernel/fiasco/src/kern/tb_entry_output.cc) *2) Kconfig* (src/l4linux/arch/l4/Kconfig) ======================= ** ===== For FEC ethernet ======* **1) mach_setup.c* (src/l4linux/arch/l4/kernel/arch-arm/mach_setup.c) * **2) fec.h* (src/l4linux/drivers/net/ethernet/freescale/fec.h) *3) fec_main.c* (src/l4linux/drivers/net/ethernet/freescale/fec_main.c) *4) fec_ptp.c* (src/l4linux/drivers/net/ethernet/freescale/fec_ptp.c) *5) Kconfig* (src/l4linux/drivers/net/ethernet/freescale/Kconfig) ====================== ===== For access HW on L4Linux ===== *1) imx6q.io* (src/l4/conf/examples/imx6q.io) *2) l4lx-imx6q.cfg* (src/l4/conf/examples/l4lx-imx6q.cfg) * **3) modules.list* (src/l4/conf/modules.list) =========================== I hope this is of some help to someone. - Taeung -

1 0

Fwd: Re: cannot find -lld-l4
by ba_f 18 May '14

18 May '14

Hello Hackers, Am 2014-05-14 11:23, schrieb Matthias Lange: >> /opt/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/bin/arm-linux-gnueabihf-ld: cannot find -lld-l4 >> make[3]: *** [myProg] Fehler 1 > > Have you successfully build the 'ldso' package? libld-l4.so is provided > by > this package. > > Matthias. Yes, the lib seems to be there: obj/l4/arm-ca/lib/arm_armv7a/l4f/libld-l4.so obj/l4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/libld-l4.so obj/l4/arm-ca/config/have/ldso.h obj/l4/arm-ca/pc/ldso.pc obj/l4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/.ldso.s.o.d objl4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/ldso.s.o I also checked the 2> output from the snapshot build process, which shows a lot of Warnings, but no Error. Am 2014-05-15 01:04, schrieb Adam Lackorzynski: > Are you trying to build a program using shared libraries? Mind to share > your Makefile? Actually, i try to include libssl.a which Ivan Loskutov ported to L4re. http://os.inf.tu-dresden.de/pipermail/l4-hackers/2012/005141.html >> BTW before that missing lib error, i get a lot of "multiple definition >> of...". > > Could you show some examples of those errors please? > > Adam ./tpm_integrity.o: In function `TPM_Extend': /home/ba_f/vTPM/server/src/tpm_integrity.c:39: multiple definition of `tpm_log' ./tpm_cmd_handler.o:/home/ba_f/vTPM/server/src/tpm_marshalling.h:102: first defined here ./tpm_startup.o: In function `TPM_Startup': /home/ba_f/vTPM/server/src/tpm_startup.c:43: multiple definition of `tpm_read_from_storage' ./tpm_cmd_handler.o:/home/ba_f/vTPM/server/src/tpm_marshalling.h:103: first defined here But these warning/error must come from the build-process, because the code has already been compiled for ARM linux without any Warnings. l4re-snapshot-2014022818 Greets, ba_f

2 1

Doing simple I/O in clntsrv example
by Valentin Hauner 17 May '14

17 May '14

3 2

how to get current cpu id
by Yuxin Ren 15 May '14

15 May '14

How can I get the id of cpu(core) the current thread is running on? Thank you

3 3

OKL4 vs L4::Pistachio
by Taylor Bioniks 15 May '14

15 May '14

How does OKL4 compare with L4::Pistachio as far as speed, security, responsiveness? L4::Pistachio uses kickstart to load it, the core kernel is contained in kernel, and the physical memory manager is stored in sigma0, I'm not even sure if it has a virtual memory manager. Does OKL4 have a built in memory manager, and does it handle virtual memory? Thank you.

3 3

Question about dataspace
by Yuxin Ren 15 May '14

15 May '14

I cannot understand dataspace very well. I have some questions about it. Each time I want to alloc a piece of memory, I must create a dataspace first? I look at the example code of memory allocation. I found after create adataspace, we call L4Re::Env::env<http://l4re.org/doc/classL4Re_1_1Env.html#aa1181d6256037deda5b5f83c2006ba60>()->mem_alloc()->alloc() to alloca memory via dataspace. Can I call this function multiple times on the same dataspace instance without free? If so, what is its effect? In addtion we use attach to map the dataspace. Can I attach the same dataspace multiple times without free? In this case, does it mean that the same physical memory is mapped into different virtual address?

2 5

Porting Fiasco+L4re to DaVinci DA850 - prefetch abort in sigma0
by Peter Howard 14 May '14

14 May '14

Dear all, I'm trying to port Fiasco to the DA850. I'm basing this on the 2014022818 snapshot. I've gotten to the point where I've modified the configuration for both fiasco and l4re, added the BSP and bootstrap platform files, and added the extra drivers I need to get started. I can build an image to load on the machine and it boots through the kernel fine. Then it tries to run sigma0 and gets a prefetch abort: EXCEPTION: prefetch abort pfa=c0090100, error=0033000d R[0]: c0002000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 R[8]: 00000000 00000000 00000000 00000000 00000000 c1013de4 04080124 c0090100 (note, I'm including the full boot output at the end of the email) The address, c0090100, is correct as the entry point for sigma0. Now, if I'm reading the FSR right, that's indicating a permission error on the section. But nothing I've added/changed has anything to do with the MMU/mapping. As far as I can see, that's all straight armv5 code, with nothing special to the board (which uses an arm926ejs core). So any idea why sigma0 would be getting mappings with the wrong permission? ------ Full output from boot: U-Boot > bootm 0xc0700000 ## Booting kernel from Legacy Image at c0700000 ... Image Name: L4 Image #2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 860160 Bytes = 840 KiB Load Address: c1000000 Entry Point: c1000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... L4 Bootstrapper Build: #2 Tue May 13 14:38:28 EST 2014, 4.7.3 Scanning up to 32 MB RAM Memory size is 32MB (c0000000 - c1ffffff) RAM: 00000000c0000000 - 00000000c1ffffff: 32768kB Total RAM: 32MB mod04: c10b8000-c10d1574: hello mod03: c109e000-c10b7454: l4re mod02: c106c000-c109d620: moe mod01: c1062000-c106b338: sigma0 mod00: c1015000-c1061380: fiasco Moving up to 5 modules behind c1100000 moving module 00 { c1015000-c106137f } -> { c11bd000-c120937f } [312192] moving module 01 { c1062000-c106b337 } -> { c120a000-c1213337 } [37688] moving module 02 { c106c000-c109d61f } -> { c1214000-c124561f } [202272] moving module 03 { c109e000-c10b7453 } -> { c1100000-c1119453 } [103508] moving module 04 { c10b8000-c10d1573 } -> { c111a000-c1133573 } [103796] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe --init=rom/hello Relocated mbi to [0xc100e000-0xc100e0e2] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0xc0002000 Regions of list 'regions' [ c0001000, c0001a3f] { a40} Kern fiasco [ c0002000, c005afff] { 59000} Kern fiasco [ c0090000, c00965bb] { 65bc} Sigma0 sigma0 [ c0098000, c009e17b] { 617c} Sigma0 sigma0 [ c0140000, c016cb87] { 2cb88} Root moe [ c0170000, c0186f0f] { 16f10} Root moe [ c1000000, c10143f3] { 143f4} Boot bootstrap [ c100a000, c100a0a6] { a7} Boot mbi [ c100e000, c100e1df] { 1e0} Root Multiboot info [ c1014048, c101409f] { 58} Boot mbi [ c1100000, c1133573] { 33574} Root Module API Version: (87) experimental Sigma0 config ip:c0090100 sp:c1013de4 Roottask config ip:c0140260 sp:00000000 Starting kernel fiasco at c0001208 Hello from Startup::stage2 Cache config: ON Timer::Timer() SERIAL ESC: allocated IRQ 61 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rUnversioned directory compiled with gcc 4.7.3 for Davinci DA850 [] Build: #1 Tue May 13 14:33:35 EST 2014 Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 EXCEPTION: prefetch abort pfa=c0090100, error=0033000d R[0]: c0002000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 R[8]: 00000000 00000000 00000000 00000000 00000000 c1013de4 04080124 c0090100 KERNEL: Warning: Sigma0 raised an exception --> HALT Panic: ... Return reboots, "k" enters L4 kernel debugger... -- Peter Howard <pjh(a)northern-ridge.com.au>

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers