February 2015 - l4-hackers - example.com Site

Ram size of the arm images
by cem akpolat 13 Feb '15

13 Feb '15

Hi, As you know there are many configuration file for arm boards under l4re/mk/platforms folder. When we open one of them, vexpress, it contains the following information: PLATFORM_NAME = "ARM Versatile Express" PLATFORM_ARCH = arm PLATFORM_RAM_BASE = 0x60000000 PLATFORM_RAM_SIZE_MB = 256 The interesting part here is the size of the RAM, because you cannot give same size of the RAM when you compile the l4 lua configuration. In case you give l4linux raises "memory cannot reach out of the ..." error. what is the exact reason of that? is there any specific point where the ram size of arm boards are static defined? Thanks in advance, Cem Akpolat

2 1

Problem with socket program on l4linux
by Gayathri Nagarajan 13 Feb '15

13 Feb '15

I have copied my binaries compiled statically to ramdisk for executing on l4linux. When I execute, //server side /tmp # ./server1 Socket created bind done Waiting for incoming connections.... //client side /tmp # ./client1 connect failed. Error: Network is unreachable But I have enabled the network support and drivers in L4Linux configuartion. Where will the .config file be located, so as to reconfirm if I have enabled correctly? I couldn't find it in l4linux build directory. Also, I executed packet sniffer on l4linux, which showed /tmp # ./simplesniffer eth0 Opening device eth0 ERROR: eth0: No such device exists (SIOCGIFHWADDR:No such device) Thank you L4 community

2 1

Running l4android on cubieboard2
by cem akpolat 12 Feb '15

12 Feb '15

Dear all, Couple of months ago, I was trying to run l4 on the samsung nexus s, but then I decided to switch to Cubieboard2 due to the simple configurations and costs stemming from the JTAG/UART interfaces which are quite expensive(around 1000 Euro). What I did: + the fiasco is compiled for All-sunxi and cubieboard + l4re is compiled for cubieboard2. + the uImage is generated through the following command make uimage -C ~/l4android/src/l4/ E=L4LinuxARM O=~l4android/src/build/l4/ + boot.scr file for uboot is created in which the compiled kernel image is given as kernel as belowe ------------ setenv kernel_addr_r 0x46000000 # 8M setenv fdt_addr 0x49000000 # 2M setenv fdt_high 0xffffffff # Load fdt in place instead of relocating fatload mmc 0 0x43000000 /script.bin fatload mmc 0 ${kernel_addr_r} /uImage setenv bootargs "console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=EDID:1280x1024p60 rw root=/dev/mmcblk0p2 rootwait" fatload mmc 0 ${fdt_addr} /sun7i-a20-cubieboard2.dtb bootm ${kernel_addr_r} - ${fdt_addr} --------------------- #End of the setup # What I am seeing on the console outputs ------------------- ## Booting kernel from Legacy Image at 46000000 ... Image Name: L4 Image #32 Created: 2015-01-12 10:46:51 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 10268672 Bytes = 9.8 MiB Load Address: 41000000 Entry Point: 41000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 49000000 Booting using the fdt blob at 0x49000000 Loading Kernel Image ... OK Using Device Tree in place at 49000000, end 4900873e Using machid 0x10bb from environment Starting kernel ... L4 Bootstrapper Build: #32 Mo 12. Jan 11:46:50 CET 2015, 4.7.3 Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (40000000 - 7fffffff) RAM: 0000000040000000 - 000000007fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 14 modules behind 41100000 moving module 02 { 41999000-419ca623 } -> { 41a89000-41aba623 } [202276] moving module 01 { 4198f000-4199833b } -> { 41a7f000-41a8833b } [37692] moving module 00 { 4193c000-4198e42b } -> { 41a2c000-41a7e42b } [336940] moving module 13 { 4163c000-4193bfff } -> { 4172c000-41a2bfff } [3145728] moving module 12 { 4128a000-4163b477 } -> { 4137a000-4172b477 } [3871864] moving module 11 { 41289000-412890e4 } -> { 41379000-413790e4 } [229] moving module 10 { 411f1000-41288c43 } -> { 412e1000-41378c43 } [621636] moving module 09 { 411cf000-411f0623 } -> { 412bf000-412e0623 } [136740] moving module 08 { 41080000-411ce453 } -> { 41170000-412be453 } [1369172] moving module 07 { 4107f000-4107f588 } -> { 4116f000-4116f588 } [1417] moving module 06 { 4107e000-4107e03b } -> { 4116e000-4116e03b } [60] moving module 05 { 4107d000-4107d425 } -> { 4116d000-4116d425 } [1062] moving module 04 { 4102a000-4107cc03 } -> { 4111a000-4116cc03 } [338948] moving module 03 { 41010000-41029457 } -> { 41100000-41119457 } [103512] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x40002000 Regions of list 'regions' [ 40000000, 400001cf] { 1d0} Root mbi_rt [ 40001000, 40001bbf] { bc0} Kern fiasco [ 40002000, 4005efff] { 5d000} Kern fiasco [ 40090000, 400968fb] { 68fc} Sigma0 sigma0 [ 40098000, 4009e177] { 6178} Sigma0 sigma0 [ 40140000, 4016e6a3] { 2e6a4} Root moe [ 40170000, 40186f13] { 16f14} Root moe [ 41000000, 4100f5ff] { f600} Boot bootstrap [ 41100000, 41a2bfff] { 92c000} Root Module API Version: (87) experimental Sigma0 config ip:40090100 sp:00000000 Roottask config ip:40140260 sp:00000000 Starting kernel fiasco at 40001388 Non-HYP kernel detected but running in HYP mode, switching back. ------------------------ What exactly Fiasco tries to tell me with this message "Non-HYP kernel detected but running in HYP mode, switching back.". Thanks, Cem Akpolat

3 15

Re: Problem Launching L4Linux
by Piwe li 12 Feb '15

12 Feb '15

Hi, Thank you for your answer Adam. Nothing happens when I press ESC. I also tried to send ESC with the QEMU monitor using "sendkey esc" which has also no effect. Same thing with the Hello World. I really don't know what could cause this problem but I think it may have something to do with capabilities (just a guess). I have to say that my QEMU works fine, I tested it with another Linux. My .dtb is good too. Do you have any ideas or suggestions ? I was also wondering about the "libio: Warning: Query of 'vbus' failed!" during the boot of L4Linux. I don't think it is a problem (due to the fact that I'm not using any IPC) but I'm not sure. Thank you for all the help, Louis. ----------------------------------------------------------------- > I am actually trying to launch L4Linux on Fiasco.OC+L4RE on Xilinx Zynq > using QEMU but I get an error at the end of the boot of L4Linux : > > */bin/sh: can't access tty; job control turned off* This is a standard message when launching the shell with init=/bin/sh, it's not L4Linux specific. > */ #* > > > > Even if I have a shell prompt I can?t type anything, that?s why I am > sending this email. Does pressing ESC get you into Fiasco's jdb? Otherwise the configs do not show me anything obvious wrong right now. > I am aware that my problem is very similar to this one > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2013/005920.html but I > tried every solution you suggested. > > > > I am working under *Ubuntu 64bits 14.04* and I am compiling with > *arm-linux-gnueabi-gcc > 4.7.3*. > > To emulate the *Xilinx Zynq*, I?m using *QEMU emulator version 2.0.50* > configured this way : > > *./configure --target-list="arm-softmmu,microblazeel-softmmu" --enable-fdt > --disable-kvm* > > To launch QEMU, here is my command line : > > *qemu-system-arm -M arm-generic-fdt -dtb ~/Documents/zynq-zc706.dtb -kernel > ~/Documents/gitL4/l4-hypervisor/build/l4/images/bootstrap.elf -serial > mon:stdio* > > Zynq is ARM so I?m using this ramdisk : > http://os.inf.tu-dresden.de/download/ramdisk-arm.rd >

3 5

Problem with executing a binary on l4linux
by Harini Balachandran 11 Feb '15

11 Feb '15

We mounted the ramdisk and copied the binary to l4linux ramdisk but while executing on l4linux, /# cd tmp /tmp#./hello /bin/sh: ./hello : not found How do I execute my binary? Regards, Harini

2 1

testing tools
by Waldo Paz Rodriguez 11 Feb '15

11 Feb '15

hello l4hackers, I need to know which types of testing and tools are available for testing devices drivers, system call performance, scheduling and any modification made on the system. best regards, waldo

2 1

Running the FERRET Examples
by Karl Steger 10 Feb '15

10 Feb '15

Hi L4 hackers, I'm trying to run the scalar demo from the FERRET package. Although the server loop from "l4/pkg/ferret/server/re/sensordir.cc" starts, no scalar sensor is registered in "l4/pkg/ferret/examples/demo/scalar_demo/main.c" as the program execution pauses at this line: ret = ferret_create(srv, 10, 1, 0, FERRET_SCALAR, 0, "0:100:%", s1, &malloc); which leads to an l4_ipc_call to the sensor directory. Could you please tell me if there is a problem with my configuration file below or provide a working configuration file? >require("L4"); > >local ld = L4.default_loader; >local ferret = ld:new_channel(); >local sensordir = ld:new_channel(); > >ld:start( >{ caps = { ferret=ferret:svr(), sensordir=sensordir:svr() } >}, >"rom/ferret_sensor_dir"); > >ld:start( >{ caps = { ferret=ferret, sensordir=sensordir }, > log = { "f_scalar_demo", "green" } >}, >"rom/fer_scalar_demo"); Thanks and regards, Karl

2 1

Getting dataspace of a tmpfs-file blocks forever
by Stark, Josef 10 Feb '15

10 Feb '15

Hey, when I have created and filled a file in tmpfs, reading normally (-> read() ) from it works fine. However, I cannot get the associated dataspace. The call would just block forever. Here is an example code snippet: ========================== const char* filename="/tmp/test"; mount("/", "tmp", "tmpfs", 0, 0); int fd=open(filename,O_WRONLY|O_CREAT); write(fd,"Hello",6); close(fd); fd=open(filename,O_RDONLY); char buf[15]; read(fd,buf,15); printf("file content: %s\n",buf); cxx::Ref_ptr<L4Re::Vfs::File> fp = L4Re::Vfs::vfs_ops->get_file(fd); printf("Got file!\n"); L4::Cap<L4Re::Dataspace> ds = fp->data_space(); printf("Got Dataspace!"); long int size = ds->size(); printf("Dataspace size: %li\n",size); printf("Done.\n"); close(fd); ============================ It would just output file content: Hello Got file! but nothing more, which tells me that reading normally from the file works, but the fp->data_space() call blocks. If I tried the same with an existing file in /rom/, it works just fine (except for the writing part, obviously). How can I make this work? Thanks, Josef

2 1

Profiling/Runtime Monitoring in Fiasco.OC and L4Re
by "Patrick Stäblein" 10 Feb '15

10 Feb '15

2 1

How to Install L4Re
by Jerry L 10 Feb '15

10 Feb '15

Hi all, I want to install L4Re in my zedboard. Who can give me some information about how to do it. I searched online and did not find any useful information about it. Thank you very much. best, Jian

2 1