linaro-dev March 2014

linaro-dev@lists.linaro.org

32 participants
20 discussions

Call for testing QEMU aarch64-linux-user emulation

by Alex Bennée

Hi, After a solid few months of work the QEMU master branch [1] has now reached instruction feature parity with the suse-1.6 [6] tree that a lot of people have been using to build various aarch64 binaries. In addition to the SUSE work we have fixed numerous edge cases and finished off classes of instructions. All instructions have been verified with Peter's RISU random instruction testing tool. I have also built and run many packages as well as built gcc and passed most of the aarch64 specific tests. I've tested against the following aarch64 rootfs: * SUSE [2] * Debian [3] * Ubuntu Saucy [4] In my tree the remaining insns that the GCC aarch64 tests need to implement are: FRECPE FRECPX CLS (2 misc variant) CLZ (2 misc variant) FSQRT FRINTZ FCVTZS Which I'm currently working though now. However for most build tasks I expect the instructions in master [1] will be enough. If you want the latest instructions working their way to mainline you are free to use my tree [5] which currently has: * Additional NEON/SIMD instructions * sendmsg syscall * Improved helper scripts for setting up binfmt_misc * The ability to set QEMU_LOG_FILENAME to /path/to/something-%d.log - this is useful when tests are failing N-levels deep as %d is replaced with the pid Feedback I'm interested in ========================== * Any instruction failure (please include the log line with the unsupported message) * Any aarch64 specific failures (i.e. not generic QEMU threading flakeiness). If you need to catch me in real time I'm available on #qemu (stsquad) and #linaro-virtualization (ajb-linaro). Many thanks to the SUSE guys for getting the aarch64 train rolling. I hope your happy with the final result ;-) Cheers, -- Alex Bennée QEMU/KVM Hacker for Linaro [1] git://git.qemu.org/qemu.git master [2] http://download.opensuse.org/ports/aarch64/distribution/13.1/appliances/ope… [3] http://people.debian.org/~wookey/bootstrap/rootfs/debian-unstable-arm64.tar… [4] http://people.debian.org/~wookey/bootstrap/rootfs/saucy-arm64.tar.gz [5] https://github.com/stsquad/qemu/tree/ajb-a64-working [6] https://github.com/susematz/qemu/tree/aarch64-1.6

12 years

linux kernel flush_cache_all behaviour on a Big.LITTLE system

by karim.allah.ahmed＠gmail.com

Hello, I have two questions: 1- I was wondering what should be the expected semantics of "flush_cache_all" on a Big.LITTLE architecture. I can see that the implementation of this function under linux kernel is doing the following: a- Read the value of LoC ( level of coherency ) b- Flush each level of cache to that LoC value using DCCISW co-processor register. My expectation would be that if this is executed on one of the processors of the Big cluster it should flush all L1 and L2 caches on this cluster and then signal the CCI interconnect of the cache cleaning operation and then the CCI interconnect would propagate this signal downstream to the LITTLE cluster. This will mean that at the end all cache will be flushed. Is that the proper semantics of this operation ? or it's only going to affect this CPU and no other CPUs in the cluster ( and consequently no other CPUs on the other cluster ). And if that's the case, does this mean that I've to do the cache flushing per_cpu ? 2- and Is there a difference in semantics between flushing each cache till I reach the Level of coherency ( using DCCISW register ) and flushing the first cache only to the point of coherency ( using DCCIMVAC register ) ? Thanks. -- Karim Allah Ahmed.

12 years

Fwd: Issue while booting up VE board

by Tom Gall

Anyone with a VE board ever encounter something like this? ---------- Forwarded message ---------- From: Bibhuti Panigrahi <bibhuti.panigrahi(a)linaro.org> Date: Tue, Mar 11, 2014 at 5:14 AM Subject: Issue while booting up VE board To: Tom Gall <tom.gall(a)linaro.org> Hi Tom, I am finding below issues while booting the Versatile Express board. The board boots and u-boot prompt comes but after that it gets powered down because of exceeding power limit (seems to be some PMIC issue). Please find the detailed log below: Cmd> ARM V2M Boot loader v1.1.2 HBI0190 build 2199 ARM V2M Firmware v3.1.1 Build Date: Aug 20 2012 Date: Wed 13 Sep 2006 Time: 05:38:05 Cmd> Powering up system... Daughterboard fitted to site 1. Switching on ATXPSU... ATX3V3: ON VIOset: 1.8V WARNING: PSU 1V0 : 0.79V (21% error) ERROR: PSU 1V0 outside limit, switching off... Powering down, switching on UART0 bypass. Powering down... Disabling debug USB. Switching off ATX PSU. Board powered down, use REBOOT to restart Cmd> Please let me know if you have any pointer to this. Regards, Bibhuti -- Regards, Tom "Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com

12 years

[GSOC 2014] Interested in working on "Run lightweight IP stack on top of Open Data Plane"

by Shonali Balakrishna

Hi all, I am Shonali Balakrishna from Bangalore, India. I am going to be starting graduate school(MSc.) at TU Delft this fall and wish to participate in Google Summer of Code 2014 as a part of Linaro. I am an Electronics and Telecommunications engineering graduate(2008-2012) from PESIT, Bangalore and I'm currently working in Oracle India, on automation/scripting for refresh(cloning) and network related tasks in their Cloud Division. I am proficient in programming/scripting in C, C++ Java and Perl. I am also proficient in Linux networking and systems programming and have sound knowledge of TCP/IP(have completed CCNA certification as well). Most importantly, I enjoy learning and am always willing to learning something new. I am interested in working on the project - "Run lightweight IP stack on top of Open Data Plane" and intend to apply for this project through GSOC 2014. I have been familiarizing myself with the Open Data Plane project and source code. I am working on a project proposal for the same and would like to run it by you for feedback when I'm done. I would be extremely grateful for any pointers or links to resources you could provide me with, that would help me with this project. Thank you for your time. Best Regards, -- Shonali Balakrishna

12 years

qemu crash

by Daniel Lipsitt

I sent the below to the list before I was a subscriber and I don't think it made it through. ----- I don't know if I'm having a problem with QEMU or the linaro system image I'm using or something else, so I'm posting it here. Let me know if there's a more appropriate place. I'm experiencing the following crash: $ qemu-system-arm -machine beagle -nographic -sd linaro-saucy-nano-20140126.img qemu: fatal: Trying to execute code outside RAM or ROM at 0x402f0400 R00=40014044 R01=402f0400 R02=00000000 R03=00000000 R04=00000000 R05=00000000 R06=00000000 R07=00000000 R08=00000000 R09=00000000 R10=00000000 R11=00000000 R12=00000000 R13=4020fcb0 R14=00000000 R15=402f0400 PSR=400001df -Z-- A sys32 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 s32=00000000 s33=00000000 d16=0000000000000000 s34=00000000 s35=00000000 d17=0000000000000000 s36=00000000 s37=00000000 d18=0000000000000000 s38=00000000 s39=00000000 d19=0000000000000000 s40=00000000 s41=00000000 d20=0000000000000000 s42=00000000 s43=00000000 d21=0000000000000000 s44=00000000 s45=00000000 d22=0000000000000000 s46=00000000 s47=00000000 d23=0000000000000000 s48=00000000 s49=00000000 d24=0000000000000000 s50=00000000 s51=00000000 d25=0000000000000000 s52=00000000 s53=00000000 d26=0000000000000000 s54=00000000 s55=00000000 d27=0000000000000000 s56=00000000 s57=00000000 d28=0000000000000000 s58=00000000 s59=00000000 d29=0000000000000000 s60=00000000 s61=00000000 d30=0000000000000000 s62=00000000 s63=00000000 d31=0000000000000000 FPSCR: 00000000 Aborted (core dumped) Here's how I created the image: linaro-media-create --dev beagle \ --hwpack hwpack_linaro-beaglebone_20140203-602_armhf_supported.tar.gz \ --binary linaro-saucy-nano-20140126-627.tar.gz \ --image-file linaro-saucy-nano-20140126.img I get the same error on the following OS/qemu combos: Ubuntu Trusty $ qemu-system-arm --version QEMU emulator version 1.7.0 (Debian 1.7.0+dfsg-3ubuntu1), Copyright (c) 2003-2008 Fabrice Bellard Ubuntu Saucy $ qemu --version QEMU emulator version 1.5.0 (Debian 1.5.0+dfsg-3ubuntu5.2), Copyright (c) 2003-2008 Fabrice Bellard MacOS 10.8.5 QEMU emulator version 1.7.0 (qemu-linaro 2014.01), Copyright (c) 2003-2008 Fabrice Bellard I get a similar error at a different address with this highbank image: http://releases.linaro.org/14.01/ubuntu/highbank/highbank-saucy_server_2014… $ qemu-system-arm -machine highbank -nographic -sd highbank-saucy_server_20140126-596.img qemu: fatal: Trying to execute code outside RAM or ROM at 0x08000000 I am able to boot this oneiric image: http://releases.linaro.org/images/12.03/oneiric/nano/beagle-nano.img.gz Can somebody supply me with a working qemu beaglebone command line? What does LAVA use? Thanks, Dan

12 years

Uboot Does NOT boot on Pandaboard-ES Rev B3

by 孙钰

Hi all, The uboot in the linaro-saucy-developer-20140222-647.tar.gz dose not boot on Pandaboard-ES Rev B3 because the Modification of Elpida DDR2 RAM Please upgrade to latest u-boot (2014.01), it works fan for my rev B3. Here follows the serial port messages: identified size not same as expected size identified: 0 expected:40000000 -- Best Regards！孙钰 Address:北航新主楼F703

12 years

Third Ubuntu Trusty test rebuild (all components, all architectures except powerpc)

by Matthias Klose

The third test rebuild of Trusty Tahr was started this week for all architectures except powerpc (all components). Results will appear at (currently this link doesn't yet exist) http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201403… The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20140307/ Additional build failures for packages in trusty-proposed (not yet in trusty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures for the final release. To prepare for the u-series, a second test rebuild using GCC 4.9 as the default is run in parallel in https://launchpad.net/ubuntu/+archive/test-rebuild-20140307-4.9/ The compiler used for this test rebuild can be found in the ubuntu-toolchain-r/test PPA. Matthias

12 years

Add support to qtcreator for aarch32 / aarch64

by Gregory H. Nietsky

Port QT Creator to ARM aarch32 / aarch64. Here is the changeset. https://codereview.qt-project.org/79828 Greg

12 years

Porting distro to aarch64

by Gregory H. Nietsky

Hi all im busy mopping up the last stragglers now that i have icedtea7/qt4/qt5/webkit working [sans JIT]. cross-compiling icedtea from x86_64 with help from binfmt_misc/qemu is not "fun" but doable if anyone wants the JDK as a "seed" im happy to publish it. with gcc lacking classpath for this arch its not possible to bootstrap JDK natively and icedtea without patching is not happy about it. for those intrested you welcome to checkout https://github.com/Distrotech/icedtea7-2.4 the patches and scripts are in .build-info dir. there is some additional patching required to get qt-5.2.1 too work with qt5.3 earmarked for aarch64 upstream im not too concerned with that. There is a open bug on qtbugs for qtcreator support for arm7hf as it currently is intel only but is a trivial patch i have posted a "clean" patch for arm32 but needs to be extended to aarch64. https://bugreports.qt-project.org/browse/QTCREATORBUG-8107. Kind regards greg.

12 years

Question regarding building a minimal kitkat arm build that can run apps?

by andrew mcelroy

Greetings, I apologize in advance if I've asked a question that's been asked ad infinity time on this list. I am attempting to build the smallest kitkat image that is capable of running a "hello world" activity/apk. I found the TINY_ANDROID option https://wiki.linaro.org/Platform/Android/UseTinyAndroid. However, it states that zygote, surfaceflinger, keystore, systemui, and installd are not built. How would I build TINY_ANDROID + those programs. SystemUI isn't a strict requirement. My target is arm-js ( a 32bit arm emulator). I don't care about i18n, networking, or anything else that isn't strictly required to run an Activity with a window, label, and possibly button. I am trying to optimize for file size. Thanks in advance. Respectfully, Andrew McElroy

12 years

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-dev March 2014