- l4-hackers - example.com Site

make error
by Shabnam Engineer 31 Aug '15

31 Aug '15

Hi l4-hackers,I want to build fiasco.OC for my rpi , but in "make" command I have faced this error : ******************************************make: arm-linux-g++: Command not found /bin/sh: 1: arm-linux-g++: not found /bin/sh: 1: arm-linux-g++: not found make: arm-linux-g++: Command not found make srcdir=/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/src objbase=/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/mybuild -f /home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/src/Makefile.sub1 make[1]: arm-linux-g++: Command not found make[1]: Entering directory `/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/mybuild' /bin/sh: 1: arm-linux-g++: not found /bin/sh: 1: arm-linux-g++: not found make[1]: arm-linux-g++: Command not found Checking compiler config... unchanged. /bin/sh: 1: arm-linux-ld: not found No known ld emulation found make[1]: *** [.Host-config] Error 1 make[1]: Leaving directory `/home/shabnam/Desktop/fiasco1/l4re-core-2014092821/src/kernel/fiasco/mybuild' make: *** [create-sources] Error 2 ******************************************************************************************and also in /bin/sh route we have the arm-linux-g++ file , and I attach the screenshots of this route .I don't know what to do .thank you for considering my question . regards, shabnam

2 3

Question about JDB in Fiasco
by yang.wei9＠zte.com.cn 30 Aug '15

30 Aug '15

Hi, Adam I have some questions about JDB in Fiasco. 1). Is there any latest manual about JDB? I can only find <Fiasco Kernel Debugger Manual>( http://os.inf.tu-dresden.de/fiasco/doc/jdb.pdf) which is written in 2008. This manual does not conform to the current fiasco version(l4re-snapshot-2014092821)。 2). Does JDB support bt(dump backtrace)? There are some descriptions about "bt" command in <Fiasco Kernel Debugger Manual>. But I can not find it in current version. Does older version fiasco support it? 3). How can I get the older version fiasco code？ Best Regards， Albin -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.

2 1

Re: l4-hackers Digest, Vol 148, Issue 3
by Raja Sekhar 23 Aug '15

23 Aug '15

Thanks for your kid reply. I've done changes according to you suggestions. But still getting same issue.... Thanks, Sekhar On Wed, Aug 5, 2015 at 3:30 PM, <l4-hackers-request(a)os.inf.tu-dresden.de> wrote: > Send l4-hackers mailing list submissions to > l4-hackers(a)os.inf.tu-dresden.de > > To subscribe or unsubscribe via the World Wide Web, visit > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > or, via email, send a message with subject or body 'help' to > l4-hackers-request(a)os.inf.tu-dresden.de > > You can reach the person managing the list at > l4-hackers-owner(a)os.inf.tu-dresden.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of l4-hackers digest..." > > > Today's Topics: > > 1. Re: L4Re: unhandled exception while building Fiasco.OC-L4Re > for ARM platform (Adam Lackorzynski) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 4 Aug 2015 21:35:09 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: L4Re: unhandled exception while building Fiasco.OC-L4Re > for ARM platform > Message-ID: <20150804193509.GB4565(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > On Mon Aug 03, 2015 at 12:33:05 +0530, Raja Sekhar wrote: > > I'm getting unhandled exception while running clntsrv example > > > > > > I've build Fiasco-L4Re system with the following specifications > > *Fiasco.OC:* > > Architecture (ARM processor family) > > Platform (ARM RealView Platform) > > Realview Platform (PBX) > > Start of RAM (physical address) (0x00000000) > > CPU (ARM Cortex-A9 CPU) > > *L4Re:* > > Target Architecture (ARM architecture) > > CPU variant (ARMv4 type CPU) > > Could you switch to ARMv7 here as this is the corresponding version for > a Cortex-A9. > > > Platform Selection (ARM Realview PBX) > > > > and *trying to run examples/clntsrv* by adding the following entry in > > module.list > > > > entry clntsrv > > bootstrap bootstrap -serial > > kernel fiasco -serial_esc > > roottask moe rom/clntsrv.cfg > > module clntsrv.cfg > > module l4re > > module ned > > module ex_clntsrv-server > > module ex_clntsrv-client > > > > Creating image: > > > > make elfimage E=clntsrv > > MODULE_SEARCH_PATH=`pwd`/../Fiasco.OC:`pwd`/source/pkg/examples/clntsrv > > > > Running image on QEMU: > > > > qemu-system-arm -M realview-pbx-a9 --kernel images/bootstrap_clntsrv > > -m 256M -serial /dev/pts/4 > > > > L4 Bootstrapper > > Build: #56 Thu Jul 30 23:21:33 IST 2015, 4.7.3 20130226 (prerelease) > > Scanning up to 256 MB RAM > > Memory size is 256MB (00000000 - 0fffffff) > > RAM: 0000000000000000 - 000000000fffffff: 262144kB > > Total RAM: 256MB > > mod07: 0113d000-011565bc: ex_clntsrv-client > > mod06: 01123000-0113c5c0: ex_clntsrv-server > > mod05: 010d0000-01122bf4: ned > > mod04: 010b6000-010cf49c: l4re > > mod03: 010b5000-010b52a6: clntsrv.cfg > > mod02: 01083000-010b4668: moe > > mod01: 01079000-01082380: sigma0 > > mod00: 01015000-01078770: fiasco > > Moving up to 8 modules behind 1100000 > > moving module 00 { 1015000-107876f } -> { 1242000-12a576f } [407408] > > moving module 01 { 1079000-108237f } -> { 12a6000-12af37f } [37760] > > moving module 02 { 1083000-10b4667 } -> { 12b0000-12e1667 } [202344] > > moving module 03 { 10b5000-10b52a5 } -> { 1157000-11572a5 } [678] > > moving module 04 { 10b6000-10cf49b } -> { 1158000-117149b } [103580] > > moving module 05 { 10d0000-1122bf3 } -> { 1172000-11c4bf3 } [338932] > > moving module 06 { 1123000-113c5bf } -> { 1100000-11195bf } [103872] > > moving module 07 { 113d000-11565bb } -> { 111a000-11335bb } [103868] > > moving module 03 { 1157000-11572a5 } -> { 1134000-11342a5 } [678] > > moving module 04 { 1158000-117149b } -> { 1135000-114e49b } [103580] > > moving module 05 { 1172000-11c4bf3 } -> { 114f000-11a1bf3 } [338932] > > Scanning fiasco -serial_esc > > Scanning sigma0 > > Scanning moe rom/clntsrv.cfg > > Relocated mbi to [0x100e000-0x100e140] > > Loading fiasco > > Loading sigma0 > > Loading moe > > find kernel info page... > > found kernel info page at 0x2000 > > Regions of list 'regions' > > [ 1000, 1abf] { ac0} Kern fiasco > > [ 2000, 72fff] { 71000} Kern fiasco > > [ 90000, 9643b] { 643c} Sigma0 sigma0 > > [ 98000, 9e17b] { 617c} Sigma0 sigma0 > > [ 140000, 16becb] { 2becc} Root moe > > [ 170000, 186f0f] { 16f10} Root moe > > [ 1000000, 10143f7] { 143f8} Boot bootstrap > > [ 100e000, 100e23d] { 23e} Root Multiboot info > > [ 1100000, 11a1bf3] { a1bf4} Root Module > > API Version: (87) experimental > > Sigma0 config ip:00090100 sp:01013de4 > > Roottask config ip:001401fc sp:00000000 > > Starting kernel fiasco at 000012b4 > > Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 > > Hello from Startup::stage2 > > Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) > > Number of IRQs available at this GIC: 96 > > Cache config: ON > > ID_PFR[01]: 00001031 00000001 ID_[DA]FR0: 00000000 00000000 > > ID_MMFR[04]: 00100103 20000000 01230000 00002111 > > L2: ID=410000c8 Type=1c100100 Aux=30520000 WMask=ff S=0 > > L2: Type L2C-310 Size = 128kB > > SERIAL ESC: allocated IRQ 44 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: rexported compiled with gcc 4.7.3 for Realview [] > > Build: #4 Tue Jul 28 22:46:31 IST 2015 > > > > Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) > > Allocate 2432 bytes (2KB) for CPU[4] local storage (offset=1187a18, > > 0xf11e8000-0xf11e8980) > > Number of CPUs: 1 > > Calibrating timer loop... done. > > SIGMA0: Hello! > > KIP @ 2000 > > allocated 4KB for maintenance structures > > SIGMA0: Dump of all resource maps > > RAM:------------------------ > > [0:0;fff] > > [0:73000;8ffff] > > [0:97000;97fff] > > [0:9f000;13ffff] > > [4:140000;16bfff] > > [0:16c000;16ffff] > > [4:170000;186fff] > > [0:187000;100dfff] > > [4:100e000;100efff] > > [0:100f000;10fffff] > > [4:1100000;11a1fff] > > [0:11a2000;effffff] > > IOMEM:---------------------- > > [0:10000000;ffffffff] > > MOE: Hello world > > MOE: found 244324 KByte free memory > > MOE: found RAM from 73000 to f000000 > > MOE: allocated 239 KByte for the page array @0x9f000 > > MOE: virtual user address space [0-bfffffff] > > MOE: rom name space cap -> [C:501000] > > BOOTFS: [1134000-11342a6] [C:503000] clntsrv.cfg > > BOOTFS: [1135000-114e49c] [C:504000] l4re > > BOOTFS: [114f000-11a1bf4] [C:505000] ned > > BOOTFS: [1100000-11195c0] [C:506000] ex_clntsrv-server > > BOOTFS: [111a000-11335bc] [C:507000] ex_clntsrv-client > > MOE: cmdline: moe rom/clntsrv.cfg > > MOE: Starting: rom/ned rom/clntsrv.cfg > > MOE: loading 'rom/ned' > > Ned says: Hi World! > > ****I am in luaK_prefix()**** > > L4Re: unhandled exception: pc=0x1021984 > > > > I have gone through the code flow for "ned" and I found that the > > exception is raising while loading ned.lua script, > > At certain point luaK_prefix() is trying to call codearith() but > > failed to call codearith(). > > both the function are located at l4re/pkg/lua/lib/contrib/src/lcode.c > > > > I'm able to get print statement which I placed before calling the > > codearith() in luaK_prefix(), > > But not printing the statement which I placed inside the codearith() > > > > Can you please get me out from this issue. > > Please check whether this persists after recompiling for ARMv7. > If not, I'd like to know which instruction/code is at 0x1021984. > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > l4-hackers mailing list > l4-hackers(a)os.inf.tu-dresden.de > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers > > > ------------------------------ > > End of l4-hackers Digest, Vol 148, Issue 3 > ****************************************** > -- *Thanks & Regards* Raja Sekhar Reddy. B

2 1

Re: Solution of the previous thread "Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD"
by Le Guan 17 Aug '15

17 Aug '15

Hello Adam, Thanks for your reply and I'm sorry for the ambiguity of my description. In fact, I have followed that thread and have solved many problems until the last step. ( http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007551.html) You guessed that it was the problem of the ramdisk, which I downloaded at http://os.inf.tu-dresden.de/download/ramdisk-arm.rd . After that, you and Mahdi no longer posted messages in this mailing list at this subject. So, I want to know how you address this problem. The output of the execution now appears like this: >* RAMDISK: ext2 filesystem found at block 0 *>* RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. *>* EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities *>* EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem *>* EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) *>* VFS: Mounted root (ext2 filesystem) readonly on device 1:0. *>* Freeing unused kernel memory: 116K (02312000 - 0232f000) *>* potentially unexpected fatal signal 4. *> >* CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 *>* task: 05c23ac0 ti: 05c26000 task.ti: 05c26000 *>* PC is at 0xc4c0 *>* LR is at 0x0 *>* pc : [<0000c4c0>] lr : [<00000000>] psr: 00000010 *>* sp : bfa42ef0 ip : 00000000 fp : 00000000 *>* r10: 00000000 r9 : 00000000 r8 : 00000000 *>* r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : 00000000 *>* r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000000 *>* vcpu: b3000c00 vcpu-state: 00000001 *>* Flags: nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user *>* CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 *>* [<02000>] (unwind_backtrace) from [<02005924>] (show_stack+0x10/0x14) *>* [<02005924>] (show_stack) from [<02028c50>] *>* (get_signal_to_deliver+0x240/0x4cc) *>* [<02028c50>] (get_signal_to_deliver) from [<02006fb4>] *>* (do_signal+0x118/0x464) *>* [<02006fb4>] (do_signal) from [<020073a0>] (do_work_pending+0xa0/0xe8) *>* [<020073a0>] (do_work_pending) from [<02008d50>] *>* (l4x_pre_iret_work.isra.31.part.32+0x60/0x104) *>* [<02008d50>] (l4x_pre_iret_work.isra.31.part.32) from [<02009e38>] *>* (l4x_vcpu_entry_c+0x274/0x1ddc) *>* [<02009e38>] (l4x_vcpu_entry_c) from [<00000000>] ( (null)) *>* Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 *> >* CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 *>* [<02000>] (unwind_backtrace) from [<02005924>] (show_stack+0x10/0x14) *>* [<02005924>] (show_stack) from [<022486c0>] (panic+0x8c/0x1dc) *>* [<022486c0>] (panic) from [<0201e0b0>] (complete_and_exit+0x0/0x1c) *>* [<0201e0b0>] (complete_and_exit) from [<00000001>] (0x1) *>* ---[ end Kernel panic - not syncing: Attempted to kill init! *>* exitcode=0x00000004 *> >* panic: going to sleep forever, bye *>* panic: going to sleep forever, bye* Thanks a lot for your help! Regards, Le Guan Date: Fri, 14 Aug 2015 00:00:09 +0200 > From: Adam Lackorzynski <adam(a)os.inf.tu-dresden.de> > To: l4-hackers(a)os.inf.tu-dresden.de > Subject: Re: Solution of the previous thread "Running L4Linux + Fiasco > on Freescale i.MX 6 Sabre SD" > Message-ID: <20150813220009.GA4552(a)os.inf.tu-dresden.de> > Content-Type: text/plain; charset=iso-8859-1 > > On Thu Aug 13, 2015 at 10:43:33 -0400, Le Guan wrote: > > Hi l4-hackers, > > > > Greetings! I encountered exactly the same problem as Mahdi's. His > original > > thread can be found at > > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007491.html. > > AS Mahdi and Adam communicated using private email later, I don't know if > > the problem has been solved. If it has been solved, can anybody give me > > some hint on it? > > When 'swp' is trapping then it's not enabled in the CPU. You can do so by > enabling it in Fiasco's config. > Alternative: Why is 'swp' used at all on an ARMv7 architecture as the > imx6? Did you compile L4Linux for ARMv7? > > > > Adam > -- > Adam adam(a)os.inf.tu-dresden.de > Lackorzynski http://os.inf.tu-dresden.de/~adam/ >

2 3

using math lua module
by AVK 16 Aug '15

16 Aug '15

Quick question, How can i use the math module in lua ? I see that it is there in the contrib folder of lua pkg so it should be built hopefully. Whenever i require("math") in lua, i get an error like Ned: ERROR: rom/json.lua:32: module 'math' not found: no field package.preload['math'] no file 'rom/math.lua' no file './math.so' no file '/usr/local/lib/lua/5.1/math.so' no file '/usr/local/lib/lua/5.1/loadall.so' -- --- Avinash Kundaliya avinash(a)avinash.com.np http://avinash.com.np

2 1

Solution of the previous thread "Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD"
by Le Guan 13 Aug '15

13 Aug '15

Hi l4-hackers, Greetings! I encountered exactly the same problem as Mahdi's. His original thread can be found at http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007491.html. AS Mahdi and Adam communicated using private email later, I don't know if the problem has been solved. If it has been solved, can anybody give me some hint on it? Many thanks! Regards, Le Guan

2 1

Re: porting linux driver in Fiasco.OC
by Shabnam Engineer 10 Aug '15

10 Aug '15

Hi thanks for your answersI want to implement Fiasco.OC on a board and test some RTOS beside other non realtime OS .. at first I want to be sure that if I need a driver for our special tests and the Fiasco.OC does not support that, Could I choose it from linux drivers and port it to Fiasco.OC microkernel?does someone do this work?thanks for your considering my question.regards, shabnam On Saturday, August 8, 2015 10:39 AM, Shabnam Engineer <shabnam.engineer72(a)yahoo.com> wrote: Hi thanks for your answerI want to implement Fiasco.OC on a board and test some RTOS beside other non realtime OS .. at first I want to be sure that if I need a driver for our special tests and the Fiasco.OC does not support that, Could I choose it from linux drivers and port it to Fiasco.OC microkernel?does someone do this work?thanks for your considering my question.regards, shabnam On Thursday, July 30, 2015 5:53 PM, Jorge Alberto Garcia <jorge.garcia.gonzalez(a)gmail.com> wrote: Hi!This is very interesting!, is there any resource about what needs to be done for a user space component handling hw ?Thanks! On Thu, Jul 30, 2015 at 1:51 AM, Matthias Lange <matthias.lange(a)kernkonzept.com> wrote: Hi, On 07/29/2015 12:29 PM, Shabnam Engineer wrote: > hi > I have a question about porting linux drivers in Fiasco.OC. > Can I port linux drivers into Fiasco.OC ? In a microkernel system device drivers are implemented as isolated user space components. No devices drivers, except from selected very low level devices like timer and interrupt controller, are implemented in the kernel. Matthias. -- Matthias Lange, matthias.lange(a)kernkonzept.com, +49 - 351 - 41 88 86 14 Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth _______________________________________________ l4-hackers mailing list l4-hackers(a)os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

3 3

L4Linux interface to convert physical address to machine address
by Olujide Adeola 05 Aug '15

05 Aug '15

Hi guys, Apologies if this question has already been answered elsewhere on this mailing list. We are porting our driver to L4Linux but having issues with the page_to_phys() Linux function, what's the L4Linux API to map a VM physical address to a machine address which can be programmed into the DMA registers of a peripheral device on the system bus. Note on terminology, (virtual address <-> physical address <-> machine address). Regards,Olujide

2 1

L4Re: unhandled exception while building Fiasco.OC-L4Re for ARM platform
by Raja Sekhar 04 Aug '15

04 Aug '15

Hello L4-Hackers, I'm getting unhandled exception while running clntsrv example I've build Fiasco-L4Re system with the following specifications *Fiasco.OC:* Architecture (ARM processor family) Platform (ARM RealView Platform) Realview Platform (PBX) Start of RAM (physical address) (0x00000000) CPU (ARM Cortex-A9 CPU) *L4Re:* Target Architecture (ARM architecture) CPU variant (ARMv4 type CPU) Platform Selection (ARM Realview PBX) and *trying to run examples/clntsrv* by adding the following entry in module.list entry clntsrv bootstrap bootstrap -serial kernel fiasco -serial_esc roottask moe rom/clntsrv.cfg module clntsrv.cfg module l4re module ned module ex_clntsrv-server module ex_clntsrv-client Creating image: make elfimage E=clntsrv MODULE_SEARCH_PATH=`pwd`/../Fiasco.OC:`pwd`/source/pkg/examples/clntsrv Running image on QEMU: qemu-system-arm -M realview-pbx-a9 --kernel images/bootstrap_clntsrv -m 256M -serial /dev/pts/4 L4 Bootstrapper Build: #56 Thu Jul 30 23:21:33 IST 2015, 4.7.3 20130226 (prerelease) Scanning up to 256 MB RAM Memory size is 256MB (00000000 - 0fffffff) RAM: 0000000000000000 - 000000000fffffff: 262144kB Total RAM: 256MB mod07: 0113d000-011565bc: ex_clntsrv-client mod06: 01123000-0113c5c0: ex_clntsrv-server mod05: 010d0000-01122bf4: ned mod04: 010b6000-010cf49c: l4re mod03: 010b5000-010b52a6: clntsrv.cfg mod02: 01083000-010b4668: moe mod01: 01079000-01082380: sigma0 mod00: 01015000-01078770: fiasco Moving up to 8 modules behind 1100000 moving module 00 { 1015000-107876f } -> { 1242000-12a576f } [407408] moving module 01 { 1079000-108237f } -> { 12a6000-12af37f } [37760] moving module 02 { 1083000-10b4667 } -> { 12b0000-12e1667 } [202344] moving module 03 { 10b5000-10b52a5 } -> { 1157000-11572a5 } [678] moving module 04 { 10b6000-10cf49b } -> { 1158000-117149b } [103580] moving module 05 { 10d0000-1122bf3 } -> { 1172000-11c4bf3 } [338932] moving module 06 { 1123000-113c5bf } -> { 1100000-11195bf } [103872] moving module 07 { 113d000-11565bb } -> { 111a000-11335bb } [103868] moving module 03 { 1157000-11572a5 } -> { 1134000-11342a5 } [678] moving module 04 { 1158000-117149b } -> { 1135000-114e49b } [103580] moving module 05 { 1172000-11c4bf3 } -> { 114f000-11a1bf3 } [338932] Scanning fiasco -serial_esc Scanning sigma0 Scanning moe rom/clntsrv.cfg Relocated mbi to [0x100e000-0x100e140] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 1abf] { ac0} Kern fiasco [ 2000, 72fff] { 71000} Kern fiasco [ 90000, 9643b] { 643c} Sigma0 sigma0 [ 98000, 9e17b] { 617c} Sigma0 sigma0 [ 140000, 16becb] { 2becc} Root moe [ 170000, 186f0f] { 16f10} Root moe [ 1000000, 10143f7] { 143f8} Boot bootstrap [ 100e000, 100e23d] { 23e} Root Multiboot info [ 1100000, 11a1bf3] { a1bf4} Root Module API Version: (87) experimental Sigma0 config ip:00090100 sp:01013de4 Roottask config ip:001401fc sp:00000000 Starting kernel fiasco at 000012b4 Realview System ID: Rev=0 HBI=178 Build=0 Arch=5 FPGA=00 Hello from Startup::stage2 Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) Number of IRQs available at this GIC: 96 Cache config: ON ID_PFR[01]: 00001031 00000001 ID_[DA]FR0: 00000000 00000000 ID_MMFR[04]: 00100103 20000000 01230000 00002111 L2: ID=410000c8 Type=1c100100 Aux=30520000 WMask=ff S=0 L2: Type L2C-310 Size = 128kB SERIAL ESC: allocated IRQ 44 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: rexported compiled with gcc 4.7.3 for Realview [] Build: #4 Tue Jul 28 22:46:31 IST 2015 Per_cpu_data_alloc: (orig: 0xf00605e8-0xf0060f68) Allocate 2432 bytes (2KB) for CPU[4] local storage (offset=1187a18, 0xf11e8000-0xf11e8980) Number of CPUs: 1 Calibrating timer loop... done. SIGMA0: Hello! KIP @ 2000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [0:0;fff] [0:73000;8ffff] [0:97000;97fff] [0:9f000;13ffff] [4:140000;16bfff] [0:16c000;16ffff] [4:170000;186fff] [0:187000;100dfff] [4:100e000;100efff] [0:100f000;10fffff] [4:1100000;11a1fff] [0:11a2000;effffff] IOMEM:---------------------- [0:10000000;ffffffff] MOE: Hello world MOE: found 244324 KByte free memory MOE: found RAM from 73000 to f000000 MOE: allocated 239 KByte for the page array @0x9f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [1134000-11342a6] [C:503000] clntsrv.cfg BOOTFS: [1135000-114e49c] [C:504000] l4re BOOTFS: [114f000-11a1bf4] [C:505000] ned BOOTFS: [1100000-11195c0] [C:506000] ex_clntsrv-server BOOTFS: [111a000-11335bc] [C:507000] ex_clntsrv-client MOE: cmdline: moe rom/clntsrv.cfg MOE: Starting: rom/ned rom/clntsrv.cfg MOE: loading 'rom/ned' Ned says: Hi World! ****I am in luaK_prefix()**** L4Re: unhandled exception: pc=0x1021984 I have gone through the code flow for "ned" and I found that the exception is raising while loading ned.lua script, At certain point luaK_prefix() is trying to call codearith() but failed to call codearith(). both the function are located at l4re/pkg/lua/lib/contrib/src/lcode.c I'm able to get print statement which I placed before calling the codearith() in luaK_prefix(), But not printing the statement which I placed inside the codearith() Can you please get me out from this issue. Thanks, Rajasekhar

2 1

issues in creating an elf binary
by AVK 31 Jul '15

31 Jul '15

Hello, I am trying to create an elf binary for the hello package (to start with) and when i run the `make elfimage` command, it fails with the following error make[3]: *** No rule to make target `mod.make.inc', needed by `bootstrap.ld'. Stop. While i am trying to look into the issue, maybe there is a quick fix for this, or someone has come across this issue already. Or maybe there is a better/easier way to create an elfimage. Regards, Avinash Kundaliya avinash(a)avinash.com.np http://avinash.com.np

2 3