l4-hackers July 2017

l4-hackers@os.inf.tu-dresden.de

9 participants
10 discussions

Porting Fiasco + L4Re to Raspberry Pi 2
by Antoine DEBUT 26 Nov '17

26 Nov '17

Hello l4-hackers, I am currently working on porting the Fiasco.OC micro kernel onto the Raspberry pi 2. Therefore, I am struggling with memory mapping, and I encounter the following error when launching the default 'hello' entry: L4 Bootstrapper Build: #2 Tue Feb 23 11:57:19 CET 2016, 4.8.3 20140303 (prerelease) Scanning up to 1024 MB RAM, starting at offset 32MB Memory size is 1024MB (00000000 - 3fffffff) RAM: 0000000000000000 - 000000003fffffff: 1048576kB Total RAM: 1024MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 5 modules behind 1100000 moving module 02 { 10db000-110c4d7 } -> { 11cc000-11fd4d7 } [201944] moving module 01 { 10c9000-10da373 } -> { 11ba000-11cb373 } [70516] moving module 00 { 1043000-10c889f } -> { 1134000-11b989f } [546976] moving module 04 { 1029000-10425af } -> { 111a000-11335af } [103856] moving module 03 { 100f000-102849b } -> { 1100000-111949b } [103580] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x2000 Regions of list 'regions' [ 1000, 1aff] { b00} Kern fiasco [ 2000, 92fff] { 91000} Kern fiasco [ 93000, 930eb] { ec} Root mbi_rt [ c0000, c9c33] { 9c34} Sigma0 sigma0 [ d0000, d6177] { 6178} Sigma0 sigma0 [ 140000, 16905b] { 2905c} Root moe [ 170000, 17b58b] { b58c} Root moe [ 1000000, 100e4ff] { e500} Boot bootstrap [ 1100000, 1133fff] { 34000} Root Module API Version: (87) experimental Sigma0 config ip:000c0100 sp:00000000 Roottask config ip:00140250 sp:00000000 Starting kernel fiasco at 000012b8 Non-HYP kernel detected but running in HYP mode, switching back. Hello from Startup::stage2 Assertion failed at /home/adebut/Documents/snapshotTest/l4re-snapshot-2015123115/src/kernel/fiasco/src/kern/buddy_alloc.cpp:101: (unsigned long)block >= _base Press any key to reboot. I am currently working on the latest snapshot (2015123115), with U-Boot as a bootloader, and testing on a real board (Raspberry Pi 2 model B V1.1). The entry built is the standard 'hello', and I use the ramdisk-arm.rd given in the snapshot. I did add a custom Bsp for the board, mainly based on the first Raspberry Pi except for the Base Address, that is 0x3F000000 instead of the first Pi's 0x20000000. I highly think that it is an address configuration problem, because it first happened when I did expand the RAM size to 1024MB. With further investigation, I found out that it was the kernel memory allocation that causes this error, and suspect an incorrect MMU mapping. This suspicion comes from the fact that the assertion takes the address _base (0xf0400000) and the currently allocated block (0xee100000). I did not modify any parameter in the kern/arm/mem_layout-arm.cpp file on the Fiasco directory, which provides the default ARM addressing. Maybe that's where my error comes from ? How can I correctly configure my memory mapping, besides what I already configure in the Bsp (given in attachment) ? Also, it is the first time that I am assigned for porting a system, do you have some hints, like important steps to follow ? I am pretty sure it is a newbie error, but I cannot figure it out for now :( Thanks in advance for your time, -- Antoine Debut EPITA 2016 - GISTRE

3 7

L4Linux network and SD Access
by Daniel (Xiaolong) Wang 19 Aug '17

19 Aug '17

Hi all, I want to give L4Linux access to SD card, and ethernet driver. Initially I thought by run L4Linux kernel on top of L4re, drivers built with L4Linux kernel can just work. After trying and reading the email archive, seems like I need to configure the corresponding capability in cfg. I’m very new to L4re environment is there any tutorials or references that can help me understand it better? (I’m currently reading the manual, my development board is a beagle bone black) Also I’m trying to build a L4Linux with MMC driver. My configuration is based on default arm_defconfig. I enabled * Make Linux be a Server * Bus driver for L4vbus * L4shm based network driver * MMC/SD/SDIO card support -> HW reset support for eMMC, MMC block device driver, Use bounce buffer for simple hosts, SDIO UART/GPS class support, Secure Digital Host Controller Interface Support, SDHCI platform and OF driver helper, MediaTek SD/MMC Card Interface support * DOS/FAT/NT Filesystem -> MSDOS fs support, VFAT fs support however, when it build the following errors show did I do something wrong? LD drivers/i2c/busses/built-in.o LD drivers/i2c/muxes/built-in.o LD drivers/i2c/built-in.o LD drivers/idle/built-in.o CC drivers/input/input.o CC drivers/input/input-compat.o CC drivers/input/input-mt.o CC drivers/input/ff-core.o LD drivers/input/input-core.o CC drivers/input/mousedev.o CC drivers/input/evdev.o LD drivers/input/built-in.o LD drivers/iommu/built-in.o CC drivers/irqchip/irqchip.o LD drivers/irqchip/built-in.o LD drivers/leds/built-in.o LD drivers/lguest/built-in.o LD drivers/macintosh/built-in.o LD drivers/media/common/b2c2/built-in.o LD drivers/media/common/saa7146/built-in.o LD drivers/media/common/siano/built-in.o LD drivers/media/common/v4l2-tpg/built-in.o LD drivers/media/common/built-in.o LD drivers/media/firewire/built-in.o LD drivers/media/i2c/soc_camera/built-in.o LD drivers/media/i2c/built-in.o LD drivers/media/mmc/siano/built-in.o LD drivers/media/mmc/built-in.o LD drivers/media/pci/b2c2/built-in.o LD drivers/media/pci/ddbridge/built-in.o LD drivers/media/pci/dm1105/built-in.o LD drivers/media/pci/mantis/built-in.o LD drivers/media/pci/netup_unidvb/built-in.o LD drivers/media/pci/ngene/built-in.o LD drivers/media/pci/pluto2/built-in.o LD drivers/media/pci/pt1/built-in.o LD drivers/media/pci/pt3/built-in.o LD drivers/media/pci/saa7146/built-in.o LD drivers/media/pci/smipcie/built-in.o LD drivers/media/pci/ttpci/built-in.o LD drivers/media/pci/built-in.o LD drivers/media/platform/omap/built-in.o LD drivers/media/platform/built-in.o LD drivers/media/rc/keymaps/built-in.o LD drivers/media/rc/built-in.o LD drivers/media/tuners/built-in.o LD drivers/media/usb/b2c2/built-in.o LD drivers/media/usb/dvb-usb/built-in.o LD drivers/media/usb/dvb-usb-v2/built-in.o LD drivers/media/usb/s2255/built-in.o LD drivers/media/usb/siano/built-in.o LD drivers/media/usb/stkwebcam/built-in.o LD drivers/media/usb/ttusb-budget/built-in.o LD drivers/media/usb/ttusb-dec/built-in.o LD drivers/media/usb/zr364xx/built-in.o LD drivers/media/usb/built-in.o LD drivers/media/built-in.o LD drivers/mfd/built-in.o LD drivers/misc/cb710/built-in.o LD drivers/misc/eeprom/built-in.o LD drivers/misc/lis3lv02d/built-in.o LD drivers/misc/mic/bus/built-in.o LD drivers/misc/mic/built-in.o LD drivers/misc/ti-st/built-in.o LD drivers/misc/built-in.o CC drivers/mmc/card/block.o CC drivers/mmc/card/queue.o LD drivers/mmc/card/mmc_block.o CC drivers/mmc/card/sdio_uart.o LD drivers/mmc/card/built-in.o CC drivers/mmc/core/core.o CC drivers/mmc/core/bus.o CC drivers/mmc/core/host.o CC drivers/mmc/core/mmc.o CC drivers/mmc/core/mmc_ops.o CC drivers/mmc/core/sd.o CC drivers/mmc/core/sd_ops.o CC drivers/mmc/core/sdio.o CC drivers/mmc/core/sdio_ops.o CC drivers/mmc/core/sdio_bus.o CC drivers/mmc/core/sdio_cis.o CC drivers/mmc/core/sdio_io.o CC drivers/mmc/core/sdio_irq.o CC drivers/mmc/core/quirks.o CC drivers/mmc/core/slot-gpio.o CC drivers/mmc/core/pwrseq.o CC drivers/mmc/core/debugfs.o LD drivers/mmc/core/mmc_core.o CC drivers/mmc/core/pwrseq_simple.o CC drivers/mmc/core/pwrseq_emmc.o LD drivers/mmc/core/built-in.o CC drivers/mmc/host/sdhci.o CC drivers/mmc/host/mtk-sd.o CC drivers/mmc/host/sdhci-pltfm.o CC drivers/mmc/host/sdhci-of-arasan.o CC drivers/mmc/host/sdhci-of-at91.o LD drivers/mmc/host/built-in.o LD drivers/mmc/built-in.o CC drivers/net/Space.o CC drivers/net/loopback.o CC drivers/net/l4shmnet.o LD drivers/net/built-in.o LD drivers/nfc/built-in.o LD drivers/nvme/host/built-in.o LD drivers/nvme/built-in.o CC drivers/of/base.o CC drivers/of/device.o CC drivers/of/platform.o CC drivers/of/fdt.o CC drivers/of/fdt_address.o CC drivers/of/address.o CC drivers/of/irq.o CC drivers/of/of_reserved_mem.o LD drivers/of/built-in.o LD drivers/platform/built-in.o LD drivers/power/built-in.o LD drivers/pwm/built-in.o CC drivers/rtc/rtc-lib.o LD drivers/rtc/built-in.o LD drivers/soc/bcm/built-in.o LD drivers/soc/fsl/built-in.o LD drivers/soc/built-in.o CC drivers/tty/tty_io.o CC drivers/tty/n_tty.o CC drivers/tty/tty_ioctl.o CC drivers/tty/tty_ldisc.o CC drivers/tty/tty_buffer.o CC drivers/tty/tty_port.o CC drivers/tty/tty_mutex.o CC drivers/tty/tty_ldsem.o CC drivers/tty/pty.o CC drivers/tty/sysrq.o LD drivers/tty/ipwireless/built-in.o CC drivers/tty/serial/serial_core.o CC drivers/tty/serial/l4ser.o CC drivers/tty/serial/l4ser_shm.o LD drivers/tty/serial/built-in.o CC drivers/tty/vt/vt_ioctl.o CC drivers/tty/vt/vc_screen.o CC drivers/tty/vt/selection.o CC drivers/tty/vt/keyboard.o CC drivers/tty/vt/consolemap.o CC drivers/tty/vt/consolemap_deftbl.o CC drivers/tty/vt/vt.o CC drivers/tty/vt/defkeymap.o LD drivers/tty/vt/built-in.o LD drivers/tty/built-in.o LD drivers/video/backlight/built-in.o CC drivers/video/console/dummycon.o CC drivers/video/console/fbcon.o CC drivers/video/console/bitblit.o CC drivers/video/console/softcursor.o LD drivers/video/console/built-in.o CC drivers/video/fbdev/core/fb_cmdline.o CC drivers/video/fbdev/core/fb_notify.o CC drivers/video/fbdev/core/fbmem.o CC drivers/video/fbdev/core/fbmon.o CC drivers/video/fbdev/core/fbcmap.o CC drivers/video/fbdev/core/fbsysfs.o CC drivers/video/fbdev/core/modedb.o CC drivers/video/fbdev/core/fbcvt.o LD drivers/video/fbdev/core/fb.o LD drivers/video/fbdev/core/built-in.o LD drivers/video/fbdev/omap2/omapfb/displays/built-in.o LD drivers/video/fbdev/omap2/omapfb/dss/built-in.o LD drivers/video/fbdev/omap2/omapfb/built-in.o LD drivers/video/fbdev/omap2/built-in.o LD drivers/video/fbdev/built-in.o CC drivers/video/logo/logo.o LOGO drivers/video/logo/logo_linux_mono.c CC drivers/video/logo/logo_linux_mono.o LOGO drivers/video/logo/logo_linux_vga16.c CC drivers/video/logo/logo_linux_vga16.o LOGO drivers/video/logo/logo_linux_clut224.c CC drivers/video/logo/logo_linux_clut224.o LD drivers/video/logo/built-in.o LOGO drivers/video/logo/logo_superh_mono.c LOGO drivers/video/logo/clut_vga16.c LOGO drivers/video/logo/logo_blackfin_vga16.c LOGO drivers/video/logo/logo_superh_vga16.c LOGO drivers/video/logo/logo_blackfin_clut224.c LOGO drivers/video/logo/logo_dec_clut224.c LOGO drivers/video/logo/logo_m32r_clut224.c LOGO drivers/video/logo/logo_mac_clut224.c LOGO drivers/video/logo/logo_parisc_clut224.c LOGO drivers/video/logo/logo_sgi_clut224.c LOGO drivers/video/logo/logo_spe_clut224.c LOGO drivers/video/logo/logo_sun_clut224.c LOGO drivers/video/logo/logo_superh_clut224.c LD drivers/video/built-in.o LD drivers/built-in.o LD sound/built-in.o LD firmware/built-in.o CC arch/l4/drivers/vbus/l4vbus.o LD arch/l4/drivers/vbus/built-in.o CC arch/l4/drivers/events.o LD arch/l4/drivers/built-in.o CC net/socket.o LD net/802/built-in.o CC net/core/sock.o CC net/core/request_sock.o CC net/core/skbuff.o CC net/core/datagram.o CC net/core/stream.o CC net/core/scm.o CC net/core/gen_stats.o CC net/core/gen_estimator.o CC net/core/net_namespace.o CC net/core/secure_seq.o CC net/core/flow_dissector.o CC net/core/sysctl_net_core.o CC net/core/dev.o CC net/core/ethtool.o CC net/core/dev_addr_lists.o CC net/core/dst.o CC net/core/netevent.o CC net/core/neighbour.o CC net/core/rtnetlink.o CC net/core/utils.o CC net/core/link_watch.o CC net/core/filter.o CC net/core/sock_diag.o CC net/core/dev_ioctl.o CC net/core/tso.o CC net/core/sock_reuseport.o CC net/core/flow.o CC net/core/net-sysfs.o CC net/core/net-procfs.o LD net/core/built-in.o CC net/ethernet/eth.o LD net/ethernet/built-in.o CC net/ipv4/route.o CC net/ipv4/inetpeer.o CC net/ipv4/protocol.o CC net/ipv4/ip_input.o CC net/ipv4/ip_fragment.o CC net/ipv4/ip_forward.o CC net/ipv4/ip_options.o CC net/ipv4/ip_output.o CC net/ipv4/ip_sockglue.o CC net/ipv4/inet_hashtables.o CC net/ipv4/inet_timewait_sock.o CC net/ipv4/inet_connection_sock.o CC net/ipv4/tcp.o CC net/ipv4/tcp_input.o CC net/ipv4/tcp_output.o CC net/ipv4/tcp_timer.o CC net/ipv4/tcp_ipv4.o CC net/ipv4/tcp_minisocks.o CC net/ipv4/tcp_cong.o CC net/ipv4/tcp_metrics.o CC net/ipv4/tcp_fastopen.o CC net/ipv4/tcp_recovery.o CC net/ipv4/tcp_offload.o CC net/ipv4/datagram.o CC net/ipv4/raw.o CC net/ipv4/udp.o CC net/ipv4/udplite.o CC net/ipv4/udp_offload.o CC net/ipv4/arp.o CC net/ipv4/icmp.o CC net/ipv4/devinet.o CC net/ipv4/af_inet.o CC net/ipv4/igmp.o CC net/ipv4/fib_frontend.o CC net/ipv4/fib_semantics.o CC net/ipv4/fib_trie.o CC net/ipv4/inet_fragment.o CC net/ipv4/ping.o CC net/ipv4/ip_tunnel_core.o CC net/ipv4/gre_offload.o CC net/ipv4/sysctl_net_ipv4.o CC net/ipv4/proc.o CC net/ipv4/xfrm4_mode_beet.o CC net/ipv4/xfrm4_mode_transport.o CC net/ipv4/xfrm4_mode_tunnel.o CC net/ipv4/ipconfig.o CC net/ipv4/inet_diag.o CC net/ipv4/tcp_diag.o CC net/ipv4/tcp_cubic.o CC net/ipv4/xfrm4_policy.o CC net/ipv4/xfrm4_state.o CC net/ipv4/xfrm4_input.o CC net/ipv4/xfrm4_output.o CC net/ipv4/xfrm4_protocol.o LD net/ipv4/built-in.o CC net/ipv6/addrconf_core.o CC net/ipv6/exthdrs_core.o CC net/ipv6/ip6_checksum.o CC net/ipv6/ip6_icmp.o CC net/ipv6/output_core.o CC net/ipv6/protocol.o CC net/ipv6/ip6_offload.o CC net/ipv6/tcpv6_offload.o CC net/ipv6/exthdrs_offload.o LD net/ipv6/built-in.o CC net/netlink/af_netlink.o CC net/netlink/genetlink.o LD net/netlink/built-in.o CC net/packet/af_packet.o LD net/packet/built-in.o CC net/sched/sch_generic.o CC net/sched/sch_mq.o LD net/sched/built-in.o CC net/unix/af_unix.o CC net/unix/garbage.o CC net/unix/sysctl_net_unix.o LD net/unix/unix.o LD net/unix/built-in.o CC net/xfrm/xfrm_policy.o CC net/xfrm/xfrm_state.o CC net/xfrm/xfrm_hash.o CC net/xfrm/xfrm_input.o CC net/xfrm/xfrm_output.o CC net/xfrm/xfrm_sysctl.o CC net/xfrm/xfrm_replay.o LD net/xfrm/built-in.o CC net/sysctl_net.o LD net/built-in.o CC lib/lockref.o CC lib/bcd.o CC lib/div64.o CC lib/sort.o CC lib/parser.o CC lib/halfmd4.o CC lib/debug_locks.o CC lib/random32.o CC lib/bust_spinlocks.o CC lib/kasprintf.o CC lib/bitmap.o CC lib/scatterlist.o CC lib/gcd.o CC lib/lcm.o CC lib/list_sort.o CC lib/uuid.o CC lib/flex_array.o CC lib/iov_iter.o CC lib/clz_ctz.o CC lib/bsearch.o CC lib/find_bit.o CC lib/llist.o CC lib/memweight.o CC lib/kfifo.o CC lib/percpu-refcount.o CC lib/percpu_ida.o CC lib/rhashtable.o CC lib/reciprocal_div.o CC lib/once.o CC lib/string_helpers.o CC lib/hexdump.o CC lib/kstrtox.o CC lib/pci_iomap.o CC lib/iomap_copy.o CC lib/devres.o CC lib/hweight.o CC lib/bitrev.o CC lib/crc16.o HOSTCC lib/gen_crc32table GEN lib/crc32table.h CC lib/crc32.o CC lib/genalloc.o CC lib/fonts/fonts.o CC lib/fonts/font_8x8.o CC lib/fonts/font_8x16.o LD lib/fonts/font.o LD lib/fonts/built-in.o CC lib/lz4/lz4_decompress.o LD lib/lz4/built-in.o CC lib/lzo/lzo1x_decompress_safe.o LD lib/lzo/lzo_decompress.o LD lib/lzo/built-in.o CC lib/xz/xz_dec_syms.o CC lib/xz/xz_dec_stream.o CC lib/xz/xz_dec_lzma2.o CC lib/xz/xz_dec_bcj.o LD lib/xz/xz_dec.o LD lib/xz/built-in.o CC lib/zlib_inflate/inffast.o CC lib/zlib_inflate/inflate.o CC lib/zlib_inflate/infutil.o CC lib/zlib_inflate/inftrees.o CC lib/zlib_inflate/inflate_syms.o LD lib/zlib_inflate/zlib_inflate.o LD lib/zlib_inflate/built-in.o CC lib/swiotlb.o CC lib/iommu-helper.o CC lib/iommu-common.o CC lib/syscall.o CC lib/nlattr.o CC lib/dynamic_queue_limits.o CC lib/net_utils.o LD lib/built-in.o CC lib/argv_split.o CC lib/bug.o CC lib/cmdline.o CC lib/ctype.o CC lib/dec_and_lock.o CC lib/decompress.o CC lib/decompress_bunzip2.o CC lib/decompress_inflate.o CC lib/decompress_unlz4.o CC lib/decompress_unlzma.o CC lib/decompress_unlzo.o CC lib/decompress_unxz.o CC lib/dma-noop.o CC lib/dump_stack.o CC lib/earlycpio.o CC lib/extable.o CC lib/fdt.o CC lib/fdt_empty_tree.o CC lib/fdt_ro.o CC lib/fdt_rw.o CC lib/fdt_strerror.o CC lib/fdt_sw.o CC lib/fdt_wip.o CC lib/flex_proportions.o CC lib/idr.o CC lib/int_sqrt.o CC lib/ioremap.o CC lib/irq_regs.o CC lib/is_single_threaded.o CC lib/klist.o CC lib/kobject.o CC lib/kobject_uevent.o CC lib/md5.o CC lib/nmi_backtrace.o CC lib/nodemask.o CC lib/plist.o CC lib/radix-tree.o CC lib/ratelimit.o CC lib/rbtree.o CC lib/seq_buf.o CC lib/sha1.o CC lib/show_mem.o CC lib/string.o CC lib/timerqueue.o CC lib/vsprintf.o AR lib/lib.a CC arch/l4/lib/arch-arm/../proc.o CC arch/l4/lib/arch-arm/../debugfs.o LD arch/l4/lib/arch-arm/built-in.o AS arch/l4/lib/arch-arm/../../../arm/lib/ashldi3.o AS arch/l4/lib/arch-arm/../../../arm/lib/ashrdi3.o AS arch/l4/lib/arch-arm/../../../arm/lib/backtrace.o AS arch/l4/lib/arch-arm/../../../arm/lib/bswapsdi2.o AS arch/l4/lib/arch-arm/../../../arm/lib/call_with_stack.o AS arch/l4/lib/arch-arm/../../../arm/lib/changebit.o AS arch/l4/lib/arch-arm/../../../arm/lib/clearbit.o AS arch/l4/lib/arch-arm/../../../arm/lib/copy_page.o AS arch/l4/lib/arch-arm/../../../arm/lib/csumipv6.o AS arch/l4/lib/arch-arm/../../../arm/lib/csumpartial.o AS arch/l4/lib/arch-arm/../../../arm/lib/csumpartialcopy.o AS arch/l4/lib/arch-arm/../../../arm/lib/delay-loop.o CC arch/l4/lib/arch-arm/../../../arm/lib/delay.o AS arch/l4/lib/arch-arm/../../../arm/lib/div64.o AS arch/l4/lib/arch-arm/../../../arm/lib/findbit.o AS arch/l4/lib/arch-arm/../../../arm/lib/io-readsb.o AS arch/l4/lib/arch-arm/../../../arm/lib/io-readsl.o AS arch/l4/lib/arch-arm/../../../arm/lib/io-readsw-armv4.o AS arch/l4/lib/arch-arm/../../../arm/lib/io-writesb.o AS arch/l4/lib/arch-arm/../../../arm/lib/io-writesl.o AS arch/l4/lib/arch-arm/../../../arm/lib/io-writesw-armv4.o AS arch/l4/lib/arch-arm/../../../arm/lib/lib1funcs.o AS arch/l4/lib/arch-arm/../../../arm/lib/lshrdi3.o AS arch/l4/lib/arch-arm/../../../arm/lib/memchr.o AS arch/l4/lib/arch-arm/../../../arm/lib/memcpy.o AS arch/l4/lib/arch-arm/../../../arm/lib/memmove.o AS arch/l4/lib/arch-arm/../../../arm/lib/memset.o AS arch/l4/lib/arch-arm/../../../arm/lib/memzero.o AS arch/l4/lib/arch-arm/../../../arm/lib/muldi3.o AS arch/l4/lib/arch-arm/../../../arm/lib/setbit.o AS arch/l4/lib/arch-arm/../../../arm/lib/strchr.o AS arch/l4/lib/arch-arm/../../../arm/lib/strrchr.o AS arch/l4/lib/arch-arm/../../../arm/lib/testchangebit.o AS arch/l4/lib/arch-arm/../../../arm/lib/testclearbit.o AS arch/l4/lib/arch-arm/../../../arm/lib/testsetbit.o AS arch/l4/lib/arch-arm/../../../arm/lib/ucmpdi2.o CC arch/l4/lib/arch-arm/../csumpartialcopyuser.o CC arch/l4/lib/arch-arm/../memcpy_user.o CC arch/l4/lib/arch-arm/../pte.o CC arch/l4/lib/arch-arm/../uaccess.o AR arch/l4/lib/arch-arm/lib.a LD arch/l4/l4lxlib/generic/built-in.o CC arch/l4/l4lxlib/generic/irq_gen.o CC arch/l4/l4lxlib/generic/legacy.o CC arch/l4/l4lxlib/generic/thread_gen.o AR arch/l4/l4lxlib/generic/lib.a LD arch/l4/l4lxlib/l4env/built-in.o CC arch/l4/l4lxlib/l4env/irq_vcpu.o CC arch/l4/l4lxlib/l4env/memory.o CC arch/l4/l4lxlib/l4env/misc.o CC arch/l4/l4lxlib/l4env/task.o CC arch/l4/l4lxlib/l4env/thread.o AR arch/l4/l4lxlib/l4env/lib.a LD virt/lib/built-in.o LD virt/built-in.o LINK vmlinux LD vmlinux.o MODPOST vmlinux.o GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o LD init/built-in.o drivers/built-in.o: In function `sdhci_at91_probe': /home/daniel/Desktop/l4re-snapshot/src/l4linux/build-arm/../drivers/mmc/host/sdhci-of-at91.c:212: undefined reference to `clk_set_rate' make[1]: *** [vmlinux] Error 1 make[1]: Leaving directory `/home/daniel/Desktop/l4re-snapshot/src/l4linux/build-arm' make: *** [sub-make] Error 2

5 19

I/O memory access and hardware page mappings
by Paul Boddie 26 Jul '17

26 Jul '17

Hello again, Having looked at the l4vbus_gpio functions and struggled with providing suitable devices, I decided to take the simpler approach and just ask for the I/O memory of the devices and access that directly. However, this didn't prove as straightforward as anticipated, either. The aim was to take the previously-mentioned device resources of the following form and to perform l4io_request_iomem (or l4io_request_resource_iomem) to get addresses of virtual regions corresponding to the different physical memory regions. PORTA = Hw.Device(function() Property.hid = "jz4780-gpio-PORTA"; Resource.regs = Res.mmio(0x10010000, 0x100100ff); ... end); PORTB = Hw.Device(function() Property.hid = "jz4780-gpio-PORTB"; Resource.regs = Res.mmio(0x10010100, 0x100101ff); ... end); ... PORTF = Hw.Device(function() Property.hid = "jz4780-gpio-PORTF"; Resource.regs = Res.mmio(0x10010500, 0x100105ff); ... end); It was indeed possible to obtain the resources involved with individual ports and also to obtain an address for each port region. However, accesses relative to these base addresses did not produce the expected results (LED output changes, switch input changes). (Looking at the virtual and physical regions in jdb suggested that the accesses were not being propagated, although I was also not successful in putting values into physical memory addresses and obtaining any of the expected results, either.) Now, I did wonder how such a small, 256-byte region mapping would actually work with my hardware. The JZ4780 does not support pages smaller than 4K when mapping memory, but I did notice that I do get an exception if trying to access beyond the end of the virtual region. (I found this out when considering that perhaps the virtual address might actually point to the base of the hardware page containing the region. So, I added a region offset to the base and tried to perform a memory access. Obviously, returning the hardware page address would be an unfortunate choice because it would oblige the API user to know about such things. Clearly, the API should return the address of the actual region, and maybe it does.) So, if this smaller-than-hardware page size is enforced, there must be a mechanism above the plain TLB mechanism that performs such enforcement. One interesting thing I noticed was that when requesting two different regions, the virtual addresses for the base of the regions were 4K apart, not 256 bytes apart. In any case, I was left wondering if any such mechanism might be preventing accesses from being correctly propagated. To simplify things a bit more, I then decided to just define the entire GPIO region in the device tree: GPIO = Hw.Device(function() Property.hid = "JZ4780 GPIO"; Resource.regs = Res.mmio(0x10010000, 0x100105ff); end); Requesting the memory for this device succeeds as before, but then performing accesses relative to the returned virtual address (with port F at vaddr + 0x500, for instance) also succeeds and produces the desired result, unlike before. So, what is this mechanism that handles accesses to regions that do not correspond to hardware pages (either in size or alignment)? Is there some kind of address-based trapping that redirects accesses to some kind of privately- allocated page that is then mapped to the hardware page concerned? Is it possible that this mechanism does not work on MIPS or on my specific device? I apologise if I should be answering my own questions by looking at the code or particular documentation resources. Paul

2 2

uImage Load Address Issue
by Daniel (Xiaolong) Wang 23 Jul '17

23 Jul '17

Hi All, I’m testing L4re on a customized I.MX6 Solo-X-4 board. I found that the fiasco kernel (the simple hello world example built into an uimage) cannot be load by the U-boot. It shows “data abort". The reason I guess it is due to different loading address. The U-boot’s default $loadaddr is 0x80800000, but the uimage I build using the L4re buildsystem has: Load Address: 11000000 Entry Point: 11000000 ==> Installing bootstrap.uimage in image directory Image size(s) in bytes: bootstrap_hello-cfg.elf: 1470844 bootstrap.raw: 1437696 bootstrap.uimage: 1437760 Start address: 0x11000000 I used the RAM_BASE=0x8080000 option to change the starting address when I made the image (as shown below), the boot did not crash but the kernel hangs at “Starting kernel..." Load Address: 01000000 Entry Point: 01000000 ==> Installing bootstrap.uimage in image directory Image size(s) in bytes: bootstrap_hello-cfg.elf: 1470844 bootstrap.raw: 1437696 bootstrap.uimage: 1437760 Start address: 0x801000000 I think it is still related to the different load address. But I do not know how to fix it. I would really appreciate if someone can point me to a right direction. Thanks -Dan

3 3

Obtaining and accessing device abstractions in L4Re
by Paul Boddie 22 Jul '17

22 Jul '17

Hello, I've been trying to write some drivers in L4Re, starting out with a GPIO driver for a currently-unsupported board, and I think I have mostly understood the concepts involved. Fortunately, there are already a couple of drivers to borrow ideas from... pkg/io/io/server/src/drivers/gpio/bcm2835.cc pkg/io/io/server/src/drivers/gpio/omap.cc And if I am not mistaken, such drivers can be accessed from other components by just doing something like this (testing for validity as we go): vbus = l4re_env_get_cap("vbus"); l4vbus_get_device_by_hid(vbus, 0, &gpio_handle, gpio_hid, 0, 0); l4vbus_gpio_set(vbus, gpio_handle, gpio_reg, value); It appears that if I just declare the device appropriately in my board's hw_devices.io file, I should be able to get a handle for it using code like the above. And all access can apparently be done via the l4vbus_gpio functions with this handle. (I was also wondering if it was possible to actually instantiate or obtain a device directly instead of obtaining a handle, for code written in C++, but the above is easily good enough at the moment.) But now I want to make another, non-GPIO, driver abstraction, instead of directly accessing the mapped memory regions concerned (which I see that some of the drivers do). It seems like I should be able to... * define a class for the abstraction inheriting from Hw::Device * declare the device in hw_devices.io using this class * provide various properties in the hw_devices.io declaration (for configuration purposes) * read the properties in the actual class implementation * access registers in memory just as the GPIO drivers do I think I can muddle through all this. But how should another component access methods provided by this driver? Do I have to implement functionality like that provided by the following files...? pkg/io/libvbus/lib/src/vbus_gpio.cc pkg/io/libvbus/include/vbus_gpio-ops.h pkg/io/io/server/src/virt/gpio/vgpio.cc Does any of this make any sense? :-) I'm just getting started here, but thanks are due in advance for any advice anyone may have! Paul

2 3

Booting L4Re on the CI20: Panic in sigma0
by Paul Boddie 21 Jul '17

21 Jul '17

Hello, I've been trying to get Fiasco.OC and L4Re booting on the MIPS Creator CI20, starting out by building the "hello" example. The first obstacle was actually seeing the serial output, where the board appears to be configured to output to UART4 in the bootstrap package, but booting from an SD card produced no output. Although I thought I had messed up the preparation of the image, or that U-Boot was being fussy about the image addresses and failing to execute the payload, switching to UART0 and rewiring my connection got me some output. For reference, changing the UART involves a couple of modifications to pkg/bootstrap/server/src/platform/ci20.cc as follows: - kuart.base_address = 0x10034000; // UART4 + kuart.base_address = 0x10030000; // UART0 - kuart.irqno = 34; + kuart.irqno = 51; // UART0: 32 + 19 But now I appear to experience a panic in sigma0 as it starts up, with the message... Warning: Sigma0 raised an exception --> HALT Here are the regions: Regions of list 'regions' [ 0, 1db] { 1dc} Kern fiasco [ 1000, 10eb] { ec} Root mbi_rt [ 10000, 9d09f] { 8d0a0} Kern fiasco [ 140000, 184773] { 44774} Root moe [ 190000, 197f3f] { 7f40} Root moe [ 200000, 20be17] { be18} Sigma0 sigma0 [ 210000, 2161bf] { 61c0} Sigma0 sigma0 [ 2d0000, 2e33df] { 133e0} Boot bootstrap [ 1100000, 1164fff] { 65000} Root Module And the registers look like this: 00[ 0]: 00000000 at[ 1]: 80022e50 v0[ 2]: 00000001 v1[ 3]: 80000000 a0[ 4]: 00010000 a1[ 5]: 002000e0 a2[ 6]: ffffffe7 a3[ 7]: 00000401 t0[ 8]: 00000000 t1[ 9]: 00000401 t2[10]: 00000413 t3[11]: 82152f38 t4[12]: 82152000 t5[13]: 801873bc t6[14]: fffffffe t7[15]: 801873bc s0[16]: 82152f60 s1[17]: 00000400 s2[18]: 00000001 s3[19]: 00000000 s4[20]: 80090000 s5[21]: 00000000 s6[22]: 00000fa0 s7[23]: 00000000 t8[24]: 8008519c t9[25]: 800a0000 k0[26]: ffffffff k1[27]: ffffffff gp[28]: 800b7f80 sp[29]: 00000000 fp[30]: 80185000 ra[31]: 80010000 HI: 00000000 LO: 000003a8 Status 00000413 Cause 00000010 EPC 002000ec The EPC indeed appears to reference sigma0, with the Cause indicating an erroneous data or instruction fetch operation. Looking at the disassembly of sigma0... 002000e0 <__start>: 2000e0: 3c1c0001 lui gp,0x1 2000e4: 279c7f80 addiu gp,gp,32640 2000e8: 0399e021 addu gp,gp,t9 2000ec: 8f9d8018 lw sp,-32744(gp) 2000f0: 8f99801c lw t9,-32740(gp) 2000f4: 27bdfff0 addiu sp,sp,-16 2000f8: 0320f809 jalr t9 2000fc: 00000000 nop ...it appears that the problem occurs when the global offset table is accessed. The global pointer gets computed as... 0x10000 + 32640 + 0x800a0000 = 0x800b7f80 ...with the load-relative operation accessing... 0x800b7f80 - 32744 = 0x800aff98 It is presumably this address that is illegal within the failing thread of execution. I've been looking at the debugger documentation... http://l4re.org/fiasco/doc/jdb.pdf ...but I'm not sure I'm doing the right things to see the state of the machine. Attempting to dump the memory at that address appears to indicate inaccessible memory, but I imagine that this region might not be mapped within whichever "task" is active. Does anyone have any suggestions about how I can troubleshoot this problem? Thanks in advance, Paul

3 12

Open a shell for a an individual task
by Hennebold, Christoph 08 Jul '17

08 Jul '17

Hello, I'am trying to write an interactive client/server system which consists of a client component that runs its own shell, and the corresponding server which provides various interfaces. I was wondering if it is possible to spawn a shell for the client during the initialization with Ned or if it is possible at all? (Besides running Ned in interactive mode) Best regards!

2 2

Re: Define Addr. Space of Task
by ba_f 08 Jul '17

08 Jul '17

Hello again, this topic is still open. So, how can I link a Task to a specific address space? > Hi Adam, > > >> Linking a program to a specific location is well possible. >> However, the extra memory region is not part of the normal RAM but an >> extra piece of memory? How is it accessed? And how big is it? >> >> Adam > > > Yes, the secure ram is separate from the ordinary DRAM. > But, access to it is address based via ARM AXI. > > My design has a trusted L4re-App. > And i want to link the trusted app alone to the secure ram. > I argue that ordinary DRAM is easy to read out for an attacker that has > local access to the platform. > The secure ram is less easy to read-out, so the trusted app would be > more secure. > > > > > Greets, > > ba_f Thank you, ba_f

2 1

L4Re IPC share memory that share file in one Linux filesystem and be visible to other Linuxes
by Joyce Peng(彭美僑) 07 Jul '17

07 Jul '17

Hi L4, I want to share a file in one Linux filesystem and be visible to other Linuxes that all run on top Fiasco.OC. It seems an IPC communication between L4re vm tasks. And access a file in Linux filesystem is a mechanism of kernel block device driver. But I only notice two char device drivers that use L4re library l4shmc in L4linux. It is l4ser_shm and l4shmnet. May you give some information about this work how to work. Thanks. Joyce.peng(彭美僑)

2 3

Unit testing guidelines or resource
by jrodriguez＠uns.edu.ar 05 Jul '17

05 Jul '17

Hi L4 team, I'm looking forward for information about existent or recommended methodology to perform systematic test on single fiasco component or L4Re service. From what I see, there is not other option than running on qemu or target host. What I would really like is to get sort of fiasco&L4Re mock to be able to run systematic unit test on user level app but on my PC (avoiding the emulator). Any recommendation on this regard? Thought about fiasco UX, but not sure if that feature is still maintained. And if I jump into the complex task of designing this mock, any recommendation about l4re service which is more "isolated" from microkernel to take it as initial use case for such development? Well that's all by now. Thanks in advance for any feedback Best Agustin

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers July 2017