- l4-hackers - example.com Site

Custom ramdisk
by Tim Komarov 31 Mar '14

31 Mar '14

Hello, L4 hackers! I use Pandaboard for my practising with Fiasco.OC and L4Linux. 1) I got a problem with booting L4Linux with my own ramdisk. When I use 18 mb ramdisk, I got the following error: reading image.elf 24691072 bytes read ## Starting application at 0x81000000 ... ... ,,,[Everything is usual] ,,, NET: Registered protocol family 17 List of all partitions: No filesystem could mount root, tried: ext3 ext2 ext4 cramfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.0-l4 #1 [<0200c624>] (unwind_backtrace+0x0/0xec) from [<020054c0>] (show_stack+0x10/0x14) [<020054c0>] (show_stack+0x10/0x14) from [<0222e63c>] (panic+0x7c/0x1b8) [<0222e63c>] (panic+0x7c/0x1b8) from [<022f2c40>] (mount_block_root+0x25c/0x29c) [<022f2c40>] (mount_block_root+0x25c/0x29c) from [<022f2f44>] (prepare_namespace+0x160/0) [<022f2f44>] (prepare_namespace+0x160/0x1b4) from [<022f2894>] (kernel_init_freeable+0x1) [<022f2894>] (kernel_init_freeable+0x174/0x1b8) from [<0222ccf0>] (kernel_init+0x8/0x118) [<0222ccf0>] (kernel_init+0x8/0x118) from [<020077d4>] (ret_from_fork+0x14/0x20) [<020077d4>] (ret_from_fork+0x14/0x20) from [<00000000>] ( (null)) panic: going to sleep forever, bye To make ramdisk I simply create a file, write 18 Mb of zeroes to it (with dd), create in that file ext2 partition and copy there files from ramdisk-arm.rd So, what should I do to get a proper working ramdisk? 2) Even more. If I create 20 mb ramdisk, I got this: reading image.elf 26788224 bytes read ## Starting application at 0x00000000 ... Than the booting hangs. Why so? Looking forward for your help, guys! Best wishes, Tim

2 3

I share attached this guide with you.
by Taeung 28 Mar '14

28 Mar '14

Hello, l4 hackers :-) !! I've promised a guide Document to you. It is "L4 / Fiasco porting guide on Freescale i.MX6 Quad SABRE SD(ARMv7)". I have had help from L4 Hackers. So, I was able to do booting "L4 Linux + L4/Fiasco.OC" on this board. I'm particularly grateful to /Tim Komarov /and /Ademd Ammar/ , /Adam Lackorzynski/, /Matthias Lange/. I don't know how much this document will help some beginner. I've thought that the guide Document might help them. But I share this document because I have had a big help from them. It is small but I am delighted to be able to contribute this open source community. :-) If it's contents is wrong , let me know your feedback. - Taeung -

3 2

hello/l4/fiasco.oc for realview pbxa9
by Alexis Fajardo Moya 27 Mar '14

27 Mar '14

Hello, recently I tried to run hello program in top of l4/fiasco.oc for exynos 4412 platform, but qemu doest'n have any platform that support it (at least my installed version) none empty machine collie Collie PDA (SA-1110) nuri Samsung NURI board (Exynos4210) smdkc210 Samsung SMDKC210 board (Exynos4210) connex Gumstix Connex (PXA255) verdex Gumstix Verdex (PXA270) highbank Calxeda Highbank (ECX-1000) midway Calxeda Midway (ECX-2000) integratorcp ARM Integrator/CP (ARM926EJ-S) (default) kzm ARM KZM Emulation Baseboard (ARM1136) mainstone Mainstone II (PXA27x) musicpal Marvell 88w8618 / MusicPal (ARM926EJ-S) n800 Nokia N800 tablet aka. RX-34 (OMAP2420) n810 Nokia N810 tablet aka. RX-44 (OMAP2420) sx1 Siemens SX1 (OMAP310) V2 sx1-v1 Siemens SX1 (OMAP310) V1 cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310) realview-eb ARM RealView Emulation Baseboard (ARM926EJ-S) realview-eb-mpcore ARM RealView Emulation Baseboard (ARM11MPCore) realview-pb-a8 ARM RealView Platform Baseboard for Cortex-A8 realview-pbx-a9 ARM RealView Platform Baseboard Explore for Cortex-A9 akita Akita PDA (PXA270) spitz Spitz PDA (PXA270) borzoi Borzoi PDA (PXA270) terrier Terrier PDA (PXA270) lm3s811evb Stellaris LM3S811EVB lm3s6965evb Stellaris LM3S6965EVB tosa Tosa PDA (PXA255) versatilepb ARM Versatile/PB (ARM926EJ-S) versatileab ARM Versatile/AB (ARM926EJ-S) vexpress-a9 ARM Versatile Express for Cortex-A9 vexpress-a15 ARM Versatile Express for Cortex-A15 xilinx-zynq-a9 Xilinx Zynq Platform Baseboard for Cortex-A9 z2 Zipit Z2 (PXA27x) For that reason I try to test hello/l4/fiasco.oc in realview pbxa9 platform. I create build directories for l4 and fiasco, configure and compile them for realview pbxa9 platform. Then I execute the following command: ~/build/l4.realview$ make -j2 elfimage E=hello MODULE_SEARCH_PATH=~/build/foc.realview SYSTEM_TARGET=/usr/local/arm-2012.03/bin/arm-none-linux-gnueabi- and this was the result: make[1]: se ingresa al directorio «/home/afmoya/src/l4» =========== Updating RAM_BASE for platform rv_pbx to 0x70000000 ========= ... Regenerating RAM_BASE settings make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» ==> Linking sigma0 ==> "sigma0" built ==> Installing sigma0 to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/sigma0/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/sigma0/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: atención: el servidor de tareas no está disponible: se utilizará -j1. Añada `+' a la regla padre del make. make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ... Building Makefile.inc make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» ==> Linking moe ==> "moe" built ==> Installing moe to local build-tree make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/moe/server/src/OBJ-arm_armv7a-l4f» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/moe/server/src» make[2]: se ingresa al directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Building .general.d ... Building Makefile.inc Building entry "hello". Merging image /home/afmoya/build/foc.realview/fiasco to mod00 [344kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/sigma0 to mod01 [340kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/moe to mod02 [2396kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/l4re to mod03 [1227kB] Merging image /home/afmoya/build/l4.realview/bin/arm_armv7a/l4f/hello to mod04 [887kB] make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[3]: se ingresa al directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» ... Generating bootstrap.ld ... 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/rv.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.elf to local build-tree ==> Installing bootstrap_hello to local build-tree ==> Installing bootstrap_hello.elf to local build-tree ==> Installing bootstrap_hello in image directory ==> Installing bootstrap_hello.elf in image directory Image size(s) in bytes: bootstrap_hello.elf: 971420 Start address: 0x71000000 --> Build-Nr: 2 make[3]: se sale del directorio «/home/afmoya/build/l4.realview/pkg/bootstrap/server/src/OBJ-arm_armv7a» make[2]: se sale del directorio «/home/afmoya/src/l4/pkg/bootstrap/server/src» make[1]: se sale del directorio «/home/afmoya/src/l4» After that I execute: ~/build/l4.realview/images$ qemu-system-arm -M realview-pbx-a9 -kernel bootstrap_hello.elf -m 256 -serial mon:stdio -nographic this was the result of the execution: oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory oss: Could not initialize DAC oss: Failed to open `/dev/dsp' oss: Reason: No such file or directory audio: Failed to create voice `lm4549.out' L4 Bootstrapper Build: #2 mié mar 26 13:02:05 CDT 2014, 4.6.3 Scanning up to 256 MB RAM Memory size is 256MB (70000000 - 7fffffff) RAM: 0000000070000000 - 000000007fffffff: 262144kB Total RAM: 256MB mod04: 710cb000-710e4580: hello mod03: 710b1000-710ca460: l4re mod02: 71077000-710b062c: moe mod01: 7106d000-71076378: sigma0 mod00: 71017000-7106cedc: fiasco Moving up to 5 modules behind 71100000 moving module 00 { 71017000-7106cedb } -> { 711ce000-71223edb } [351964] moving module 03 { 710b1000-710ca45f } -> { 71100000-7111945f } [103520] moving module 04 { 710cb000-710e457f } -> { 71100000-7111957f } [103808] ...and that was all. No "Hello world". After that I kill the qemu process. What 's the problem with my procedure? Sorry for the huge amount of lines of my email. Best regards! Alexis.

2 6

Have you modified L4 Kernel command line ?
by Taeung 27 Mar '14

27 Mar '14

Hello, L4 hackers :-) May I ask you a question about L4 linux ? Have you modified ' l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 init=/bin/sh' in L4 kernel command ? I want to change it , as if the part of original linux's kernel command line is "root=/dev/mmcblk1p1 rootwait rw" Because I want to assign 'root' to '/dev/mmcblk1p1' or '/dev/mtdblock0' instead of 'rom/ramdisk-arm.rd'. To what I want is achieved, how to modify L4 linux kernel command line ?

2 1

Compiling L4Linux for Pandaboard ARM Error
by Erry Pradana Darajati 25 Mar '14

25 Mar '14

Hello L4 Hackers, i am doing a project that involve L4 and Pandaboard Rev.B1 So far, i am successful to boot Fiasco with L4Re in it. And now, i'm moving on to boot the L4Linux to Pandaboard I'm following the tuts from wiki tudos quickstart. But when i'm try to *make* the L4Linux, it gave me an error like this : =============================================== GEN /media/chiqiVstorage/l4resnap/src/l4linux/TArev2/Makefile CHK include/generated/uapi/linux/version.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig gcc: error: unrecognized argument in option '-mabi=aapcs-linux' gcc: note: valid arguments to '-mabi=' are: ms sysv CC scripts/mod/devicetable-offsets.s gcc: error: unrecognized command line option '-mno-thumb-interwork' make[3]: *** [scripts/mod/empty.o] Error 1 make[3]: *** Waiting for unfinished jobs.... gcc: error: unrecognized argument in option '-mabi=aapcs-linux' gcc: note: valid arguments to '-mabi=' are: ms sysv gcc: error: unrecognized command line option '-mno-thumb-interwork' make[3]: *** [scripts/mod/devicetable-offsets.s] Error 1 make[2]: *** [scripts/mod] Error 2 make[1]: *** [scripts] Error 2 make[1]: *** Waiting for unfinished jobs.... make: *** [sub-make] Error 2 ================================================================ Is this error caused by my GCC ? i am using GCC from the default repository of ubuntu 13.10 And also, when i'm try to *make mrproper *it gave me error : ERROR: Cannot determine L4 source directory Please properly set the path to your L4 build directory in the configuration menu. But i'm sure i set in the wrong path Is there any solution about my problems above, I am appreciating any help and answer Thank you L4 Hackers -- *Regards,* *Erry Pradana Darajati | Student of Computer Engineering* *Politeknik Elektronika Negeri Surabaya / EEPIS, Indonesia*

2 1

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