- l4-hackers - example.com Site

no such object found: rom/l4re backtrace
by 水镜 04 Mar '15

04 Mar '15

Hi, i have build the l4re,l4linux,fiasco for x86 successfully. when i boot try to boot l4linux, an error came out: FATAL exception in MOE: Exception: No such object found: rom/l4re: backtrace ... i use the vmware and ubuntu 14.04 to test the l4linux, here is the steps how i do my job: 1.create a directory 'l4linux' in /boot. 2.copy the bootstrap to '/boot/l4linux' from 'l4re_build/bin/x86_586' 3.copy all the file to '/boot/l4linux' in 'l4re_build/bin/x86_586/l4f' 4.copy the fiasco to '/boot/l4linux' from 'fiasco_build/bin' 5.copy the vmlinuz to '/boot/l4linux' form 'l4linux_build' 6.download the drops-rd.rd to '/boot/l4linux' 7.create the l4linux.cfg in '/boot/l4linux' 8.create the modules.list in '/boot/l4linux' the 'modules.list' is like this: entry L4Linux kernel fiasco -serial_esc roottask moe rom/l4linux.cfg module l4linux.cfg module l4re module ned module vmlinuz module drops-rd.rd the 'l4linux.cfg' is like this: L4.default_loader:start({}, "rom/vmlinuz mem=64M console=ttyLv0 l4x_rd=rom/drops-rd.rd root=1:0 ramdisk_size=4000 init=/bin/sh"); 9.modify the grub.cfg, add the following lines: menuentry 'L4Linux' { multiboot /boot/l4linux/bootstrap -modaddr 0x02000000 module /boot/l4linux/fiasco -serial_esc module /boot/l4linux/sigma0 module /boot/l4linux/moe rom/l4linux.cfg module /boot/l4linux/l4linux.cfg module /boot/l4linux/l4re module /boot/l4linux/ned module /boot/l4linux/vmlinuz } after this job is done. i reboot the system. the error came out. please give me some help to sovle the problem. thanks.

2 3

Blocking Read
by teclis High Elf 02 Mar '15

02 Mar '15

Hi, Would someone be able to point me to an example L4Re driver that does a blocking read? thanks,

2 1

Troubles testing UART3 on Exynos5
by Reinier Millo Sánchez 27 Feb '15

27 Feb '15

Hi I'm testing Fiasco.OC+L4re on YSE5250 (Exynos 5250) Board. I have compiled and tested some examples. I'm testing a GPS Driver for the board. The GPS is conected over UART3 at 9600 baudrate, first I'm testing UART3 port comunicating the UART1 serial output with UART3. I'm following as example the serial-drv package on L4re. I have adapted the source code to my uart driver >>> gps_drv.cc #include <l4/drivers/uart_s3c2410.h> #include <l4/io/io.h> #include <l4/re/env> #include <l4/re/error_helper> #include <l4/re/namespace> #include <l4/re/util/cap_alloc> #include <l4/re/util/object_registry> #include <l4/re/util/icu_svr> #include <l4/re/util/vcon_svr> #include <l4/sys/irq> #include <l4/util/util.h> #include <cstdlib> #include <cstdio> #define IRQ_NUM 86 #define UART_BASE 0x12C30000 static L4::Cap<void> srv_rcv_cap; class Loop_hooks : public L4::Ipc_svr::Ignore_errors, public L4::Ipc_svr::Default_timeout, public L4::Ipc_svr::Compound_reply { public: void setup_wait(L4::Ipc::Istream &istr, bool) { istr.reset(); istr << L4::Ipc::Small_buf(srv_rcv_cap.cap(), L4_RCV_ITEM_LOCAL_ID); l4_utcb_br_u(istr.utcb())->bdr = 0; } }; using L4Re::Env; using L4Re::Util::Registry_server; static Registry_server<Loop_hooks> server(l4_utcb(), Env::env()->main_thread(), Env::env()->factory()); using L4Re::Util::Vcon_svr; using L4Re::Util::Icu_cap_array_svr; class GPS_server : public Vcon_svr<GPS_server>, public Icu_cap_array_svr<GPS_server>, public L4::Server_object { public: GPS_server(); virtual ~GPS_server() throw() {} bool running() const { return _running; } int vcon_write(const char *buffer, unsigned size); unsigned vcon_read(char *buffer, unsigned size); L4::Cap<void> rcv_cap() { return srv_rcv_cap; } int handle_irq(); bool init(); int dispatch(l4_umword_t obj, L4::Ipc::Iostream &ios); private: bool _running; L4::Uart *_uart; L4::Cap<L4::Irq> _uart_irq; Icu_cap_array_svr<GPS_server>::Irq _irq; }; GPS_server::GPS_server() : Icu_cap_array_svr<GPS_server>(1, &_irq), _running(false), _uart(0), _uart_irq(L4_INVALID_CAP), _irq() { if (init()) _running = true; } int GPS_server::vcon_write(const char *buffer, unsigned size) { _uart->write(buffer, size); return -L4_EOK; } unsigned GPS_server::vcon_read(char *buffer, unsigned size) { unsigned i = 0; while (_uart->char_avail() && size) { int c = _uart->get_char(false); if (c >= 0) { buffer[i++] = (char)c; size--; } else break; } // if there still some data available send this info to the client if (_uart->char_avail()) i++; else _uart_irq->unmask(); return i; } int GPS_server::handle_irq() { if (_irq.cap().is_valid()) _irq.cap()->trigger(); return L4_EOK; } bool GPS_server::init() { l4_addr_t virt_base = 0; // Mapeando memoria de registros del UART if (l4io_request_iomem((l4_addr_t)UART_BASE, 0x1000, L4IO_MEM_NONCACHED, &virt_base)) { printf("gps-drv: request io-memory from l4io failed.\n"); return false; } printf("gps-drv: virtual base at:%lx\n", virt_base); // Inicializando memoria de los registros del UART L4::Io_register_block_mmio *regs = new L4::Io_register_block_mmio(virt_base); // Inicializando UART _uart = new (malloc(sizeof(L4::Uart_s5pv210))) L4::Uart_s5pv210; _uart->startup(regs); /** * FIX - Ajustando el BaudRate del UART * Valores calculados experimentalmente a través del UART1 * SCLK_UART = 100 MHz * TODO - Hacer el ajuste del BaudRate en el propio UART */ regs->write<unsigned int>(0x28,0x28a); regs->write<unsigned int>(0x2C,0x0); _uart_irq = L4Re::Util::cap_alloc.alloc<L4::Irq>(); if (!_uart_irq.is_valid()) { printf("gps-drv: Alloc capability for uart-irq failed.\n"); return false; } if (l4io_request_irq(IRQ_NUM, _uart_irq.cap())) { printf("gps-drv: request uart-irq from l4io failed\n"); return false; } /* setting IRQ type to L4_IRQ_F_POS_EDGE seems to be wrong place */ if (l4_error(_uart_irq->attach((l4_umword_t)static_cast<L4::Server_object *>(this), L4Re::Env::env()->main_thread()))) { printf("gps-drv: attach to uart-irq failed.\n"); return false; } if ((l4_ipc_error(_uart_irq->unmask(), l4_utcb()))) { printf("gps-drv: unmask uart-irq failed.\n"); return false; } _uart->enable_rx_irq(true); srv_rcv_cap = L4Re::Util::cap_alloc.alloc<void>(); if (!srv_rcv_cap.is_valid()) { printf("serial-drv: Alloc capability for rcv-cap failed.\\n"); return false; } return true; } int GPS_server::dispatch(l4_umword_t obj, L4::Ipc::Iostream &ios) { l4_msgtag_t tag; ios >> tag; switch (tag.label()) { case L4_PROTO_IRQ: if (!L4Re::Util::Icu_svr<GPS_server>::dispatch(obj, ios)) return handle_irq(); case L4_PROTO_LOG: return L4Re::Util::Vcon_svr<GPS_server>::dispatch(obj, ios); default: return -L4_EBADPROTO; } } int main() { char buffer[100]; int tmp; static GPS_server gps_srv; // Register calculation server if (!server.registry()->register_obj(&gps_srv, "gps_srv").is_valid()) { printf("Could not register GPS service, is there a 'gps_srv' in the caps table?\n"); return 1; } if (!gps_srv.running()) { printf("Failed to initialize serial driver; Aborting.\n"); return 1; } gps_srv.vcon_write("Hola Mundo\n",11); while(1){ tmp = gps_srv.vcon_read(buffer,11); if(tmp>0) printf("Readed data: %s\n",buffer); } // Wait for client requests server.loop(); return 0; } I have created my run config file >>> gps-drv.cfg require("L4"); -- Shortcuts local ld = L4.default_loader; local vbus_uart03 = ld:new_channel(); local platform_ctl = ld:new_channel(); local gps_srv = ld:new_channel(); -- Start the IO Server ld:start( { caps = { sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; platform_ctl = platform_ctl:svr(); uart03 = vbus_uart03:svr(); }, log = { "IO Server", "green" }, l4re_dbg = L4.Dbg.Warn, }, "rom/io rom/yse5250.devs rom/yse5250.io"); -- Start the GPS Driver Server conected to UART3 ld:start( { caps = { gps_srv = gps_srv:svr(); vbus = vbus_uart03; }, log = {"GPS Driver","blue"} }, "rom/gps_drv"); And have created the yse5250.devs and yse5250.io to put the UART3 on a virtual BUS >>> yse5250.devs local Hw = Io.Hw local Res = Io.Res Io.hw_add_devices { UART3 = Hw.Device { hid = "UART3"; Res.irq(86); Res.mmio(0x12C30000, 0x12C3ffff); } } >>> yse5250.io Io.add_vbusses { -- Create a virtual bus for a client and give access to UART3 uart03 = Io.Vi.System_bus(function () dev = wrap(Io.system_bus():match("UART3")); end); } On modules.list have added an entry for my example entry GPS-Driver kernel fiasco -serial_esc roottask moe rom/gps-drv.cfg module l4re module ned module gps-drv.cfg module gps_drv module io module yse5250.devs module yse5250.io After that i have compiled and uploaded the example to the board. At runtime, i got the "Hola Mundo" over UART3 but when I write in the UART3 I never read the written information. Something is wrong with my code? -- Lic. Reinier Millo Sánchez Centro de Estudios de Informática Universidad Central "Marta Abreu" de Las Villas "antes de discutir ... respira; antes de hablar ... escucha; antes de escribir ... piensa; antes de herir ... siente; antes de rendirte ... intenta; antes de morir ... vive"

2 1

Re: Ethernet on l4linux
by taeung 27 Feb '15

27 Feb '15

On 02/26/2015 02:11 PM, Harini Balachandran wrote: > For getting ethernet on l4linux, what are the packages and network > elements I should copy to ramdisk? > As of now, my ramdisk has only the basic programs.I got this from l4re > snapshot ie ramdisk-x86.rd.I have copied my target application > program(compiled statically) alone to this ramdisk additionally. > I tired copying /proc,/sys and /etc from ubuntu but the size goes > beyond 1.5 GB.What are the essential packages for getting ethernet on > l4linux? > Thank you. > Files in /proc and /sys aren't general files. They are a virtual filesystem provided by Linux. sysfs is http://en.wikipedia.org/wiki/Sysfs procfs is http://en.wikipedia.org/wiki/Procfs So, it isn't needed that you copy them to ramdisk. But if procfs isn't mounted , you can manually mount procfs. For example $ mount -t proc proc proc/ $ mount -t sysfs sys sys/ And the ramdisk already has enough packages and files to connect network. Important thing is to successfully load ethernet driver on L4/L4linux environment. If you succeed in working ethernet driver, you can use commands 'ifup' and 'ifdown','ifconfig' to connect network. And you can check whether ethernet driver is loaded or not if you do 'dmesg | grep ethernet'. Thanks, Taeung > > Regards, > Harini

1 0

Ethernet on l4linux
by Gayathri Nagarajan 20 Feb '15

20 Feb '15

I am getting an ERROR : NETWORK IS UNREACHABLE, when i run socket program in l4linux. I am using 64-bit host, upon that - virtual machine which is 32-bit, upon that - ubuntu, upon that - fiasco+l4re+l4re+l4linux *//l4linux_socket.io <http://l4linux_socket.io> file* l4linux => new System_bus() { NIC => wrap(hw-root.NIC); } *//l4linux_socket.cfg* -- vim:set ft=lua: local lxname = "vmlinuz"; if L4.Info.arch() == "arm" then lxname = "vmlinuz.arm"; end loader = L4.default_loader; vbus_l4linux = loader:new_channel(); loader:start( { caps={ sigma0 = L4.cast(L4.Proto.Factory, L4.Env.sigma0):create(L4.Proto.Sigma0); icu = L4.Env.icu; l4linux = vbus_l4linux:svr(); }, },"rom/io -vv rom/l4linux_socket.io"); loader:start( { caps = { log = L4.Env.log:m("rws"), vbus = vbus_l4linux; }, l4re_dbg = L4.Dbg.Warn, log = { "l4linux", "yellow" }, }, "rom/" .. lxname .. " mem=64M console=ttyLv0 l4x_rd=rom/new_ramdisk root=0:0 ramdisk_size=8400 init=/bin/sh"); *//l4linux_socket.list* modaddr 0x01100000 entry l4linux_socket kernel fiasco -serial_esc roottask moe rom/l4linux_socket.cfg module l4re module ned module l4linux_socket.cfg module io module l4linux_socket.io module vmlinuz module new_ramdisk Please help us in resolving the error Thank you

2 1

Re: Problem with Socket program in l4linux
by TaeWoong Song 18 Feb '15

18 Feb '15

> On Feb 18, 2015, at 1:58 PM, Harini Balachandran <harinisbcn(a)gmail.com> wrote: > > Sir, > > I referred the document you suggested. I have set up my environment like this > Base - windows 8 , 64- bit > upon this, virtual machine , then UBUNTU, then l4re+fiasco+l4linux > > Procr = intel core i5 , > x86 board What is your x86 board ? What is your ethernet tranceiver ? (I used ARM board which has Atheros AR8031 for gigabit ethernet ) > > The document you sent was with respect to ARM procr. > Can I use the same .io and .cfg files? Yes, whichever procr you use you should use .io and .cfg to enable ethernet driver and network device on L4Linux. But should change addresses in .io file like 'new-res Mmio(0x02188000 .. 0x0218BFFF);’. You can find mmio addresses in data sheet for your CPU. And refer to URL http://os.inf.tu-dresden.de/L4Re/doc/io.html <http://os.inf.tu-dresden.de/L4Re/doc/io.html> Also should change information of architecture such as ‘if L4.Info.arch() == "arm” then’ in .cfg file > If not, I dont know how to modify according to my set up. > Also how to modify the l4linux source code as it has been done for ARM in the document ie mach_setup.c > What is the ethernet driver you’ll use ? Where is source codes for the ethernet driver ? (I used ‘FEC ethernet driver’) If mach_setup.c hasn’t registering 'platform device’ for your ethernet driver, should add it to mach_setup.c source code. Thanks, Taeung > > Kindly help > > > Regards, > Harini > > On Mon, Feb 16, 2015 at 12:29 PM, taeung <treeze.taeung(a)gmail.com <mailto:treeze.taeung@gmail.com>> wrote: > > On 02/16/2015 03:19 PM, Harini Balachandran wrote: >> Hello sir, >> We saw your question related to networking being posted on l4re mailing list.We request you to assist us. >> >> I have copied my binaries of socket program 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 >> >> Please list us the network support drivers that are to be enabled in l4linux configuration.Is there any other changes that have to be made apart from enabling the networking support in l4linux? >> Thank You. >> > > 1. It is important that what is your boad and what is cpu on your board > 2. You should register a network device in IO server > 3. To access network device on L4 Linux, you need to configure ‘.io’ file > > 4. I don't know if this is of any help but I do hope so > The link has a document about porting and enabling ethernet on L4Linux. > http://developerpostit.blogspot.kr/search/label/l4%20device%20driver <http://developerpostit.blogspot.kr/search/label/l4%20device%20driver> > > Thanks, > Taeung > >> >> Regards, >> Harini > >

1 0

Re: Problem with Socket program in l4linux
by taeung 16 Feb '15

16 Feb '15

On 02/16/2015 03:19 PM, Harini Balachandran wrote: > Hello sir, > We saw your question related to networking being posted on l4re > mailing list.We request you to assist us. > I have copied my binaries of socket program 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 > > Please list us the network support drivers that are to be enabled in > l4linux configuration.Is there any other changes that have to be made > apart from enabling the networking support in l4linux? > Thank You. > 1. It is important that what is your boad and what is cpu on your board 2. You should register a network device in IO server 3. To access network device on L4 Linux, you need to configure ‘.io’ file 4. I don't know if this is of any help but I do hope so The link has a document about porting and enabling ethernet on L4Linux. http://developerpostit.blogspot.kr/search/label/l4%20device%20driver Thanks, Taeung > > Regards, > Harini

1 0

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