when i plug sdcard into the board , i got the following errors :
U-Boot SPL 2013.01.-rc1-00003-g43ee87a (Jul 22 2013 - 05:47:23)
OMAP4460 ES1.1
SDRAM: identified size not same as expected size identified: 0 expected:
40000000
OMAP SD/MMC: -1901534549
spl: mmc init failed: err - -19
### ERROR ### Please RESET the board ###
I did exactly as this link says.
http://releases.linaro.org/13.07/android/panda/#tabs-2
I guess the error caused by the following step:
linaro-android-media-create --mmc /dev/sdc --dev panda --boot
boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2
however,I do not know how to solve it ,can you give me some
suggestions? thank you in advance!
Hi,
We are trying to build android Kitkat (for our own platform) using
linaro android toolchain version
4.7.4 from 13.12 release. We are observing following while compiling
some shared libraries:
~arm-linux-androideabi-4.7/bin/../libexec/gcc/arm-linux-androideabi/4.7.4/real-ld:
warning: shared library text segment is not shareable
~arm-linux-androideabi-4.7/bin/../libexec/gcc/arm-linux-androideabi/4.7.4/real-ld:
error: treating warnings as errors
We tried to suppress thisn warning by setting LDFLAGS but the
tool-chain does not seem to identify this flag:
LOCAL_LDFLAGS := --no-warn-shared-textrel
We need some help to fix this, so posting on both android and
tool-chain mailing lists.
Thanks,
Sandeepa
Hello,
Based on previous discussion, some simplifications and clarifications
were done to Android publishing process:
1. When first (usually only) group of files is published, it must
include BUILD-INFO.txt which gives permissions for all files which will
be published as artifacts.
2. If there's 2nd group of files to publish (the only case we have is
to publish lava-job-info metadata file), it must NOT include
BUILD-INFO.txt, and ACLs for it must be set in the main BUILD-INFO.txt
file (step 1).
3. BUILD-INFO.txt is not rewritten or altered in nay way. Again, it
must include complete and final ACLs for all artifact files in a build.
linaro-license-protection app as running on snapshots.linaro.org will
use verbatim content of BUILD-INFO.txt as provided by the build authors
to control access to the files.
Hope this clarifies access control setup greatly and resolves cases
where we couldn't control some access aspects of private builds.
Now, looking at "open" builds BUILD-INFO overlays,
(https://snapshots.linaro.org/android/binaries/open/) I see that
https://snapshots.linaro.org/android/binaries/open/20131212/build-info.tar.…
has complicated file pattern comparing to previous incarnation,
https://snapshots.linaro.org/android/binaries/open/20131008/build-info.tar.…
which has just:
-------
Files-Pattern: *
License-Type: open
-------
I'm not sure which prompted to prepare 20131212/build-info.tar.bz2 ,
but if it was done as a workaround to previous publishing problems, I'd
suggest to switch back to 20131008/build-info.tar.bz2 .
Please let us (me, Milo) know if spot any issues with ACL with new
publishing settings, or need help with ACLs for private builds.
Thanks,
Paul
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
Hi,
I need to run Linaro on Nexus 10 (manta, Exynos 5250). I've downloaded http://releases.linaro.org/13.11/android/galaxynexus/, but during the build I saw a mentioning of 'maguro', which is definitely not a 'manta' model: TI OMAP4460 platform, etc.
What is about Linaro for Nexus 10? Is there any code?
Thanks
Andrei.
