March 2014 - l4-hackers - example.com Site

Can use other root file system instead of ramdisk(ramdisk-arm.rd) ?
by Taeung 25 Mar '14

25 Mar '14

Hello , L4 hackers !!:-) Would you mind if I ask you other questions ? I've done booting "L4 linux + L4/Fiasco" on Freescale imx6q_sabre_sd. I'm using ramdisk of which name is 'ramdisk-arm.rd'. I've got the file from URL (os.inf.tu-dresden.de/download/ramdisk-arm.rd). But it is not enough to install and run X-window. There is not enough package. I really want to use 'apt-get' on L4 Linux. 1. Can is what I want possible on L4 linux ? 2. Can use other root file system instead of ramdisk(ramdisk-arm.rd) ? 3. Whatever packages which is put in a ramdisk, is it no matter ? If I put ubuntu packages in a ramdisk, is it fine? - Taeung -

2 1

Is wrong my kernel command line, on this situation ? (Booting L4 linux)
by Taeung 24 Mar '14

24 Mar '14

Hello, every l4-hacker. I've succeeded booting "Hello world + L4/Fiasco" on Freescale i.MX6q_sabre_sd because big help of Admed, Tim, Matthias. And then, I'm trying to boot "L4 Linux + L4/Fiasco" on my board. I've configured for L4 linux build. Such as.. |System type -> ARM system type (L4 Linux) Build type (Use ARMv7) | And then, I've successfully build it. I've did "make uimage E='L4Linux ARM' ..." ,so I've got uimage. And I try to boot it ,using 'uImage' and 'u-boot.bin'. But I did not boot it on my board. It was stoped at "l4linux | panic: going to sleep forever, bye" ==================== ... (eclipsis) Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 Minicom2.6.2RAMDISK: 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: 112K (022ea000 - 02306000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 CPU: 0 PID: 1 Comm: sh Not tainted 3.13.0-l4-svn46 #1 [<0200b6ec>] (unwind_backtrace+0x0/0xf8) from [<02005308>] (show_stack+0x10/0x14) [<02005308>] (show_stack+0x10/0x14) from [<0222a17c>] (panic+0x78/0x1c0) [<0222a17c>] (panic+0x78/0x1c0) from [<02017d28>] (do_exit+0x724/0x7cc) [<02017d28>] (do_exit+0x724/0x7cc) from [<02017ea0>] (do_group_exit+0x40/0xa0) [<02017ea0>] (do_group_exit+0x40/0xa0) from [<02021754>] (get_signal_to_deliver+0x1a4/0x474) [<02021754>] (get_signal_to_deliver+0x1a4/0x474) from [<02006738>] (do_signal+0x78/0x3d4) [<02006738>] (do_signal+0x78/0x3d4) from [<02006b08>] (do_work_pending+0x74/0xcc) [<02006b08>] (do_work_pending+0x74/0xcc) from [<02009cf4>] (l4x_vcpu_entry_c+0x18ec/0x1e3c) [<02009cf4>] (l4x_vcpu_entry_c+0x18ec/0x1e3c) from [<00094e9c>] (0x94e9c) panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye ==================== I guess that the problem is somthing about ramdisk(root file system) and kernel command line might be wrong. Referentially I've used ramdisk file(ramdisk-arm.rd) and my kernel command line "setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk1p1 rootwait rw video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'". How do you think about that? Is wrong my kernel command line,on this situation ? - Taeung -

2 1

Re: l4linux
by Taeung 24 Mar '14

24 Mar '14

Hello, Tim I'm glad. Tim Your help save me !!! Thank you very much !!!! :-) I've succeed booting "L4 Linux + L4/Fiasco" on my board(Freescale i.MX6 Quad SABRE SD). After I readjustmy thread for booting, I will write document for booting it on my board. The document might help L4/Fiasco beginner or not, I'll share the document for their. Thank you again !! - Taeung - On 03/24/2014 07:33 PM, Tim Komarov wrote: > Hello, TaeWoong! > I've returned after the weekend. So, my congratulations! I guess that yo don't need my environment anymore :-) > > I suppose that your configuration of L4Linux is wrong. > > Try to build L4Linux like that (arm_defconfig, not your manual configuration): > > $mkdir builddir > > $ make O=pathtobuilddir L4ARCH=arm CROSS_COMPILER=arm-linux- arm_defconfig > > Change path to l4re-tree: > $ make O=pathtobuilddir L4ARCH=arm CROSS_COMPILER=arm-linux- menuconfig > > Build: > $ make O=pathtobuilddir L4ARCH=arm CROSS_COMPILER=arm-linux- -j5 > > It may help you!

1 0

Can you tell me function name that means 'Entry Point: 0x11000000' ?
by Taeung 24 Mar '14

24 Mar '14

Hello, l4 hacker. I'm trying to boot "Hello world / L4/ Fiasco" on Freescale i.MX6 Quad SABRE SD board(Cortex-A9, ARMv7). I'm using 'u-boot' and 'uImage'. So, i build uimage by "make uimage E=hello ~...". And i've try to booting it on Freescale i.MX6q_sabre_sd board. But i did not it because stoped at "Starting kernel ..." !! MMC read: dev # 2, block # 2048, count 8192 ... 8192 blocks read: OK ## Booting kernel from Legacy Image at 10800000 ... Image Name: L4 Image #2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 868352 Bytes = 848 kB Load Address: 11000000 Entry Point: 11000000 Loading Kernel Image ... OK OK Starting kernel ... uimage's file name is "bootstrap_hello.uimage". "bootstrap_hello.uimage" has information such as "bootstrap_hello.uimage: u-boot legacy uImage, L4 Image #2, Linux/ARM, OS Kernel Image (Not compressed), 868352 bytes, Thu Mar 20 13:14:42 2014, Load Address: 0x11000000, Entry Point: 0x11000000, Header CRC: 0xBEA251F3, Data CRC: 0xA0217B7D" I have a question. Can you tell me function name that means 'Entry Point: 0x11000000' ?

3 5

Fwd: Can you tell me function name that means 'Entry Point: 0x11000000' ?
by TaeWoong Song 23 Mar '14

23 Mar '14

Begin forwarded message: > From: Taeung <treeze.taeung(a)gmail.com> > Subject: Re: Can you tell me function name that means 'Entry Point: 0x11000000' ? > Date: March 23, 2014 12:07:38 PM GMT+09:00 > To: Matthias Lange <matthias.lange(a)kernkonzept.com> > > Thank you , Matthias :-) > > Fortunately , Ahmed in L4 hackers give me a patch about UART on Freescale imx6q sabre_sd. > > But i question , again. > > I have known that entry point mean the address of the execution of the image. > But i really want to know that.. > > What is concreate function name mapping the address in L4 re source code ? > > - Taeung - > > On 03/22/2014 07:02 AM, Matthias Lange wrote: >> Hi, >> >>> On 21 Mar 2014, at 11:33, Taeung <treeze.taeung(a)gmail.com> wrote: >>> >>> Hello, l4 hacker. >>> >>> >>> I'm trying to boot "Hello world / L4/ Fiasco" on Freescale i.MX6 Quad SABRE SD board(Cortex-A9, ARMv7). >>> >>> I'm using 'u-boot' and 'uImage'. >>> So, i build uimage by "make uimage E=hello ~...". >>> And i've try to booting it on Freescale i.MX6q_sabre_sd board. >>> But i did not it because stoped at "Starting kernel ..." !! >> Probably you selected the wrong UART, so the system is not printing something on the serial line. Make sure you have the right UART driver for your platform and make sure you have selected the right one. Usually there are more than one UARTs and only one is connected to you serial line. You can also check Linux to see which UART it uses. >> >>> MMC read: dev # 2, block # 2048, count 8192 ... 8192 blocks read: OK >>> ## Booting kernel from Legacy Image at 10800000 ... >>> Image Name: L4 Image #2 >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 868352 Bytes = 848 kB >>> Load Address: 11000000 >>> Entry Point: 11000000 >>> Loading Kernel Image ... OK >>> OK >>> >>> Starting kernel ... >>> >>> >>> uimage's file name is "bootstrap_hello.uimage". >>> "bootstrap_hello.uimage" has information such as >>> "bootstrap_hello.uimage: u-boot legacy uImage, L4 Image #2, Linux/ARM, OS Kernel Image (Not compressed), 868352 bytes, >>> Thu Mar 20 13:14:42 2014, Load Address: 0x11000000, Entry Point: 0x11000000, Header CRC: 0xBEA251F3, Data CRC: 0xA0217B7D" >>> >>> I have a question. >>> >>> Can you tell me function name that means 'Entry Point: 0x11000000' ? >> In the uimage format the entry point is defined as the address where uboot should start, as the name implies, the execution of the image. >> >> >> Matthias. >

2 1

compile l4re for arm
by Waldo 21 Mar '14

21 Mar '14

Hi, i am running the hello world example for the arm realview (exynos4412), and i don't how create a elfimage to run the example, i compile the fiasco and l4re for arm, but the elfimage is not generated.

3 3

Google Summer of Code - DEADLINE IS TODAY!
by Crypto Stick 21 Mar '14

21 Mar '14

Hi! Crypto Stick is an open source secure USB device for data encryption and authentication. OpenCoin is an open source system for anonymous cash. We (both projects) are aiming to collaborate on building a L4-based server system which would act as an eCash issuer server. Now, we got accepted at the upcoming Google Summer of Code 2014, which means that Google will sponsor a student working on this project during the summer with $5500. If this sounds interesting for you, please get in touch with us! Also, please share the word with fellow students. THE APPLICATION DEADLINE IS TODAY 19:00 UTC! Sorry for this last minute announcement. More details are available at: https://www.assembla.com/spaces/cryptostick/wiki/Ideas Best regards, Jan

1 0

L4 Fiasco's scheduling in Multi-Core
by Ganis Zulfa Santoso 20 Mar '14

20 Mar '14

Hi l4-hackers, Suppose we have 2 cores (core 0 and core 1) and we have 2 tasks (task A and task B). And I assign all threads of task A to run in core 0 and all threads of task B to run in core 1. How L4 Fiasco's scheduler manages this? Will the tasks run together or they have to switch from one to another? >From what I understand, the tasks don't run together regardless which core they are located, is it correct? Thank you. Best regards, Ganis

3 2

compiling L4RE for ARM
by Waldo 18 Mar '14

18 Mar '14

hello, i am a beginner in this topic, but you can tell me how i can compile L4re for ARM ?

2 1

I was not able to run "Hello world" on my board(imx6).
by taeung 18 Mar '14

18 Mar '14

Hello, L4 hackers. I have questions about booting "Hello world" on myboard. Please help me. I'm try to boot "Hello world + L4re + fiasco" on my board of which name is 'freescale i.MX6 Quad SABRE SD'(Cortex-A9,ARMv7). I built L4re and Fiasco. So, i got L4 build tree and fiasco image. Although i have built uimage file by "make uimage" and and i try to "make qemu", i was not able to run "hello world". (For reference,i have run original linux of which name is Linux/ARM, OS Kernel ,Linux-3.0.35-2508-g54750ff on my board(Freescale imx6q_sabre_sd)) <1. Result of the try booting on my board after "make uimage"> ======================================================================== MMC read: dev # 2, block # 2048, count 8192 ... 8192 blocks read: OK ## Booting kernel from Legacy Image at 10800000 ... Image Name: L4 Image #3 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1224704 Bytes = 1.2 MB Load Address: 11000000 Entry Point: 11000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... ======================================================================== <1-1. My Question > Why stop at "Starting kernel..." ? Is wrong my environment variables in u-boot ? (If it is the problem, how fix u-boot environment variables from '1-4'? ) Or, my toolchains(linaro gcc 4.6 (64bit) ) are a wrong choice ? <1-2. Fiasco : What i configured for myboard > ======================================================================== Target configuration ---> Architecture (ARM processor family) Platform (Freescale i.MX) Freescale i.MX (i.MX6) CPU (ARM Cortex-A9 CPU) [ ] Enable alignment check (NEW) [ ]Execution Model (Standard mode) [ ] Enable the deprecated 'swp' instruction (NEW) [*] Enable L2 Cache [ ] Enable FPU co-processor [ ] Enable CPU errata workarounds (NEW) Kernel options ---> [*] Enable multi processor support (4) Maximal supported number of CPUs (NEW) [*] Fine-grained CPU time Scheduler (Fixed priority scheduler) ======================================================================== <1-3. L4 re : What i configured for myboard> ======================================================================== Target Architecture 3. ARM architecture (BUILD_ARCH_arm) (NEW) CPU variant 9. ARMv7A type CPU (CPU_ARM_ARMV7A) (NEW) Platform Selection 7. Freescale i.MX6 (PLATFORM_TYPE_imx6) (NEW) Automatically determine internal gcc preprocessor names (INT_CPP_NAME_SWITCH) [Y/n] (NEW) Y Automatically determine internal ld names (INT_LD_NAME_SWITCH) [Y/n] (NEW) Y Strip binaries on install (BID_STRIP_PROGS) [N/y/?] (NEW) N GCC: Omit Frame-pointers (BID_GCC_OMIT_FP) [N/y/?] (NEW) N Build doc directories (BID_BUILD_DOC) [N/y/?] (NEW) N Enable RELEASE flag (RELEASE_MODE) [N/y/?] (NEW) N ======================================================================== <1-4. U-boot : what i set environment variable for my board> (u-boot-mx6q-sabresd.bin is supported from freescale home page.) ======================================================================== MX6Q SABRESD U-Boot > setenv loadaddr 0x10800000 MX6Q SABRESD U-Boot > setenv bootargs_base 'setenv bootargs console=ttymxc0,115200' MX6Q SABRESD U-Boot > setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk1p1 rootwait rw video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24' MX6Q SABRESD U-Boot > setenv bootcmd_mmc 'run bootargs_base bootargs_mmc;mmc dev 2;mmc read ${loadaddr} 0x800 0x2000;bootm' MX6Q SABRESD U-Boot > setenv bootcmd 'run bootcmd_mmc' MX6Q SABRESD U-Boot > saveenv Saving Environment to MMC... Writing to MMC(2)... done MX6Q SABRESD U-Boot > run bootcmd ======================================================================== <2. Result of the second try "make qemu"> ======================================================================== root@taeung-MS-7798:/path/to/obj2/tudos# make qemu E=hello-cfg MODULE_SEARCH_PATH=/path/to/obj2/fiasco/ make[1]: Entering directory `/home/taeung/Hello_test_l4/src/l4' ... Generating bootstrap.ld Building entry "hello-cfg". Merging image /path/to/obj2/fiasco//fiasco to mod00 [360kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/sigma0 to mod01 [351kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/moe to mod02 [2365kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/l4re to mod03 [1228kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/ned to mod04 [2387kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/hello.cfg to mod05 [1kB] Merging image /path/to/obj2/tudos/bin/arm_armv7a/l4f/hello to mod06 [896kB] ... Compiling exec.o ... Compiling module.o ... Compiling ARCH-arm/crt0.o ... Compiling region.o ... Compiling startup.o ... Compiling init_kip_v2.o ... Compiling init_kip_v4.o ... Compiling libc_support+.o ... Compiling patch.o ... Compiling koptions.o ... Compiling platform/imx.o ... Compiling loader_mbi.o ... Compiling ARCH-arm/reboot.o ==> Linking bootstrap.elf ==> Post-processing bootstrap.elf ==> "bootstrap.elf" built ==> Installing bootstrap.elf in image directory ==> Installing bootstrap_hello-cfg in image directory ==> Installing bootstrap_hello-cfg.elf in image directory Image size(s) in bytes: bootstrap_hello-cfg.elf: 1257856 Start address: 0x11000000 --> Build-Nr: 4 ==> Installing bootstrap.elf to local build-tree ==> Installing bootstrap_hello-cfg to local build-tree ==> Installing bootstrap_hello-cfg.elf to local build-tree QEmu-cmd: qemu-system-arm -kernel /path/to/obj2/tudos/images/bootstrap.elf qemu: fatal: Trying to execute code outside RAM or ROM at 0x11000000 R00=00000000 R01=00000000 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=00000000 R14=00000000 R15=11000000 PSR=400001d3 -Z-- A svc32 s00=00000000 s01=00000000 d00=0000000000000000 s02=00000000 s03=00000000 d01=0000000000000000 s04=00000000 s05=00000000 d02=0000000000000000 s06=00000000 s07=00000000 d03=0000000000000000 s08=00000000 s09=00000000 d04=0000000000000000 s10=00000000 s11=00000000 d05=0000000000000000 s12=00000000 s13=00000000 d06=0000000000000000 s14=00000000 s15=00000000 d07=0000000000000000 s16=00000000 s17=00000000 d08=0000000000000000 s18=00000000 s19=00000000 d09=0000000000000000 s20=00000000 s21=00000000 d10=0000000000000000 s22=00000000 s23=00000000 d11=0000000000000000 s24=00000000 s25=00000000 d12=0000000000000000 s26=00000000 s27=00000000 d13=0000000000000000 s28=00000000 s29=00000000 d14=0000000000000000 s30=00000000 s31=00000000 d15=0000000000000000 FPSCR: 00000000 bash: line 3: 5158 Aborted (core dumped) $qemu -kernel /path/to/obj2/tudos/images/bootstrap.elf make[1]: *** [qemu] Error 134 make[1]: Leaving directory `/home/taeung/Hello_test_l4/src/l4' make: *** [qemu] Error 2 ======================================================================== <2-1. My Question > Qemu support cpu such as cortex-A9 and ARMv7. But it not support mahine information for Freescale i.MX6 quad sabre sd. Because this is the reason, Can't boot "Helloworld + L4re+Fiasco" by qemu ? Or Is there other reason ? Thank you, if you help whatever. /Regards, Taeung Song | Student of Computer Engineering Hansung University./

1 0