diff options
| author | Ryan Harkin <ryan.harkin@linaro.org> | 2014-06-24 14:10:11 +0100 |
|---|---|---|
| committer | Ryan Harkin <ryan.harkin@linaro.org> | 2014-06-24 14:10:11 +0100 |
| commit | 03c5d2513cea8746afe01ccfdb9aba80871a313e (patch) | |
| tree | 96639598e53a8f81cc9c8bc8ac381be0ed39db1e /android/images | |
| parent | 6badd1c227fa0ef655dfe1f1ff1cbe9b80e4dfc9 (diff) | |
14.06: add Juice Juno notes as copy of Android Juno notes
Copy the Android Juno notes and update the embedded links.
Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
Diffstat (limited to 'android/images')
5 files changed, 1128 insertions, 0 deletions
diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_eula.txt b/android/images/armv8-juice-juno-lsk/HOWTO_eula.txt new file mode 100644 index 0000000..55e813f --- /dev/null +++ b/android/images/armv8-juice-juno-lsk/HOWTO_eula.txt @@ -0,0 +1,269 @@ +THIS END USER LICENCE AGREEMENT (“LICENCE”) IS A LEGAL AGREEMENT BETWEEN YOU (EITHER A SINGLE INDIVIDUAL, OR SINGLE LEGAL ENTITY) AND ARM LIMITED ("ARM") FOR THE USE OF THE DELIVERABLES ACCOMPANYING THIS LICENCE. ARM IS ONLY WILLING TO LICENSE THE DELIVERABLES TO YOU ON CONDITION THAT YOU ACCEPT ALL OF THE TERMS IN THIS LICENCE. BY CLICKING “I AGREE” OR BY INSTALLING OR OTHERWISE USING OR COPYING THE DELIVERABLES YOU INDICATE THAT YOU AGREE TO BE BOUND BY ALL THE TERMS OF THIS LICENCE. IF YOU DO NOT AGREE TO THE TERMS OF THIS LICENCE, ARM IS UNWILLING TO LICENSE THE DELIVERABLES TO YOU AND YOU MAY NOT INSTALL, USE OR COPY THE DELIVERABLES, BUT YOU SHOULD PROMPTLY RETURN THE DELIVERABLES TO YOUR SUPPLIER AND ASK FOR A REFUND OF ANY LICENCE FEE PAID. + + + +“ARM Versatile Express Development Board” means a hardware development board purchased directly from ARM or its authorised distributors. + + + +"Deliverables" means any software, firmware, boardfiles, data and documentation accompanying this Licence, any printed, electronic or online documentation supplied with it, and any updates, patches and modifications ARM may make available to you under the terms of this Licence, in all cases relating to the supporting deliverables for the ARM Versatile Express Development Board. + + + +“Separate Files” means the separate files identified in Part D of the Schedule. + + + +1. LICENCE GRANTS. + +(i) DELIVERABLES: ARM hereby grants to you, subject to the terms and conditions of this Licence, a non-exclusive, non-transferable licence solely for use on an ARM Versatile Express Development Board and only for the purposes of your internal development, testing and debugging of software applications that are designed to run solely on microprocessors manufactured under licence from ARM, to: + + + +(a) use and copy the Deliverables identified in Part A of the Schedule; + + + +(b) use, copy and modify the Deliverables identified in Part B and Part C of the Schedule; + + + +(c) distribute and sub-license to third parties the right to use, copy and modify the Deliverables identified in Part C(i) of the Schedule, or your derivatives thereof, as part of your own products (“Licensed Products”) provided you comply with the terms of Clause 1(ii); + + + +(d) permit either or both your customers and your authorised distributors to redistribute the Deliverables identified in Part C(i) of the Schedule, or your derivatives thereof, solely as part of Licensed Products developed by you or your permitted users (identified in clause 2 paragraph three below). + + + +Except as permitted by clause 1(i)(b) above, you shall not modify the Deliverables. Except as permitted by clauses 1(i)(c) and 1(i)(d) above, you shall not redistribute any of the Deliverables. + + + +(ii) FURTHER CONDITIONS APPLICABLE TO REDISTRIBUTION AND SUB-LICENSING: If you choose to redistribute the Deliverables identified in Part C(i) of the Schedule (“Example Code”) you agree: (a) to ensure that they are licensed for use only as part of Licensed Products and only on microprocessors manufactured or simulated under licence from ARM; (b) not to use ARM's or any of its licensors names, logos or trademarks to market the Licensed Products; (c) to include valid copyright notices on the Licensed Products, and preserve any copyright notices which are included with, or in, the Example Code; (d) to comply with all the other terms of this Licence; and (e) to ensure that any further redistribution is limited to redistribution by either or both your customers and your authorised distributors only as part of Licensed Products developed by you or your permitted users and only for use on microprocessors manufactured or simulated under licence from ARM and that your customers and authorised distributors comply with the terms of this clause 1(ii). + + + +2. RESTRICTIONS ON USE OF THE DELIVERABLES. + +COPYING: You shall not use or copy the Deliverables except as expressly authorised in this Licence. You may make one additional copy of the delivered Deliverables media or image for backup or archival purposes. + +PERMITTED USERS: The Deliverables shall be used only by your employees, or by your bona fide sub-contractors for whose acts and omissions you hereby agree to be responsible to ARM to the same extent as you are for any acts and omissions of your employees, and provided always that such sub-contractors; (i) work only onsite at your premises; (ii) comply with the terms of this Licence; (iii) are contractually obligated to use the Deliverables only for your benefit, and (iv) agree to assign all their work product and any rights they create therein in the supply of such work to you. Only the single individual, company or other legal entity to whom ARM is supplying this Licence may use the Deliverables. Except as provided in this clause, you shall not allow third parties (including but not limited to any subsidiary, parent or affiliated companies, or offsite contractors you may have) to use the Deliverables unless ARM specifically agrees otherwise with you on a case by case basis. + + + +NO REMOTE USE: The Deliverables shall only be used onsite at your premises and only for your benefit. + +MULTIPLE VERSIONS: The media on which the Deliverables resides may contain more than one version of the Deliverables, each of which is compatible with a different operating system (such as Microsoft Windows XP Professional and Red Hat Linux). + + + +ACADEMIC OR EDUCATIONAL USERS ONLY: If you or your employer or institution paid academic or educational pricing for the Deliverables, or the Deliverables are identified as an academic or educational version (together “Academic Software”), then notwithstanding anything else in this Licence, YOU AGREE TO USE THE ACADEMIC SOFTWARE ONLY FOR ACADEMIC, NON-COMMERCIAL PURPOSES, AND ARM DOES NOT GRANT YOU ANY RIGHTS TO DISTRIBUTE OR SUB-LICENSE ANY APPLICATIONS DEVELOPED USING THE ACADEMIC SOFTWARE UNDER THIS LICENCE. + + + +REVERSE ENGINEERING: Except to the extent that such activity is permitted by applicable law you shall not reverse engineer, decompile or disassemble any of the Deliverables. If the Deliverables were provided to you in Europe you shall not reverse engineer, decompile or disassemble any of the Deliverables for the purposes of error correction. + + + +BENCHMARKING: This licence does not prevent you from using the Deliverables for internal benchmarking purposes. However, you shall treat any and all benchmarking data, and any other results of your use or testing of the Deliverables which are indicative of performance, efficacy, reliability or quality, as confidential information and you shall not disclose such information to any third party without the express written permission of ARM. + + + +RESTRICTIONS ON TRANSFER OF LICENSED RIGHTS: The rights granted to you under this Licence may not be assigned, sublicensed or otherwise transferred by you to any third party without the prior written consent of ARM. An assignment shall be deemed to include, without limitation; (i) any transaction or series of transactions whereby a third party acquires, directly or indirectly, the power to control the management and policies of you, whether through the acquisition of voting securities, by contract or otherwise; or (ii) the sale of more than fifty percent (50%) of the your assets whether in a single transaction or series of transactions. You shall not rent or lease the Deliverables. You shall not share the Deliverables with contractors (except as identified in the ‘PERMITTED USERS' clause above) or other third parties. + + + +COPYRIGHT AND RESERVATION OF RIGHTS: The Deliverables are owned by ARM or its licensors and are protected by copyright and other intellectual property laws and international treaties. The Deliverables are licensed not sold. You acquire no rights to the Deliverables other than as expressly provided by this Licence. You shall not remove from the Deliverables any copyright notice or other notice and shall ensure that any such notice is reproduced in any copies of the whole or any part of the Deliverables made by you or your permitted users. + + + +3. SUPPORT AND MAINTENANCE. + +If you purchased the Deliverables directly from ARM, and you are not receiving them as an update or upgrade or as Academic Software (defined in Clause 2), you are entitled to reasonable support and maintenance for the Deliverables for the period of one (1) year from the date of purchase. The support will be provided on any version of the Deliverables which, at the date of your support request, are either; (a) the current version made generally available by ARM; or (b) the previous version made generally available by ARM at some time during the previous ninety (90) days. + + + +Support will be provided by telephone, email or other written format designated by ARM, prioritised at ARM's discretion, and may not be used as a substitute for training or as additional resource for your programming projects. Maintenance will be provided in the form of upgrades, updates and patch releases to the Deliverables as and when they are made generally available from ARM. + + + +ARM's obligation under this Clause 3 is limited to the provision of support and maintenance to you and ARM is under no obligation to provide any support and maintenance to any third parties under this Licence. If you purchase support and maintenance for additional years it will be provided pursuant to this Clause 3 and will be subject to the terms and conditions of this Licence. + + + +If; (i) you obtained the Deliverables from an ARM authorised reseller or other third party; (ii) Deliverables were provided free of charge or for evaluation; or (iii) it is Academic Software, you are not entitled to any support for the Deliverables from ARM, but ARM may, at its sole discretion provide limited support to you. The vendor of the Deliverables may or may not offer support to you for the Deliverables. Please refer to the Technical Support area of http://www.arm.com for contact details for ARM's support service and (if applicable) other authorised support channels. ARM shall be under no obligation to provide support in respect of any modifications (where permitted) to the Deliverables. + + + +4. CONFIDENTIALITY. + +You acknowledge that the Deliverables and any benchmarking data and related information mentioned in Clause 2 contains trade secrets and confidential material, and you agree to maintain all such information in confidence and apply security measures no less stringent than the measures which you apply to protect your own like information, but not less than a reasonable degree of care, to prevent their unauthorised disclosure and use. Subject to any restrictions imposed by applicable law, the period of confidentiality shall be indefinite. You agree that you shall not use any such information other than in normal use of the Deliverables under the licences granted in this Licence. + + + +Notwithstanding the foregoing you may disclose the Deliverables identified in Part C(i) of the Schedule to third parties solely in exercise of the licence rights contained in Clause 1(i)(c) of this Licence. + + + +5. LIMITED WARRANTIES. + +For the period of ninety (90) days from the date of receipt by you of the Deliverables, ARM warrants to you that (i) the media on which the Deliverables are provided shall be free from defects in materials and workmanship under normal use; and (ii) the Deliverables will perform substantially in accordance with the accompanying documentation (if any). ARM's total liability and your exclusive remedy for breach of these limited warranties shall be limited to ARM, at ARM's option; (a) replacing the defective Deliverables; or (b) using reasonable efforts to correct material, documented, reproducible defects in the Deliverables and delivering such corrected Deliverables to you. Any replacement Deliverables will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is the longer. + + + +EXCEPT AS PROVIDED ABOVE, YOU AGREE THAT THE DELIVERABLES ARE LICENSED “AS IS”, AND THAT ARM EXPRESSLY DISCLAIMS ALL REPRESENTATIONS, WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS, IMPLIED OR STATUTORY, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF NON- INFRINGEMENT, SATISFACTORY QUALITY, AND FITNESS FOR A PARTICULAR PURPOSE. + + + +YOU EXPRESSLY ASSUME ALL LIABILITIES AND RISKS, FOR USE OR OPERATION OF SOFTWARE APPLICATIONS, INCLUDING WITHOUT LIMITATION, APPLICATIONS DESIGNED OR INTENDED FOR MISSION CRITICAL APPLICATIONS, SUCH AS PACEMAKERS, WEAPONARY, AIRCRAFT NAVIGATION, FACTORY CONTROL SYSTEMS, ETC. SHOULD THE DELIVERABLES PROVE DEFECTIVE, YOU ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + + + +6. LIMITATION OF LIABILITY. + +TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL ARM BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING LOSS OF PROFITS) ARISING OUT OF THE USE OR INABILITY TO USE THE DELIVERABLES WHETHER BASED ON A CLAIM UNDER CONTRACT, TORT OR OTHER LEGAL THEORY, EVEN IF ARM WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + +ARM does not seek to limit or exclude liability for death or personal injury arising from ARM's negligence or ARM's fraud and because some jurisdictions do not permit the exclusion or limitation of liability for consequential or incidental damages the above limitation relating to liability for consequential damages may not apply to you. + + + +NOTWITHSTANDING ANYTHING TO THE CONTRARY CONTAINED IN THIS LICENCE, THE MAXIMUM LIABILITY OF ARM TO YOU IN AGGREGATE FOR ALL CLAIMS MADE AGAINST ARM IN CONTRACT TORT OR OTHERWISE UNDER OR IN CONNECTION WITH THE SUBJECT MATTER OF THIS LICENCE SHALL NOT EXCEED THE GREATER OF; (I) THE TOTAL OF SUMS PAID BY YOU TO ARM (IF ANY) FOR THIS LICENCE; AND (II) $10 USD. + +THE EXISTENCE OF MORE THAN ONE CLAIM WILL NOT ENLARGE OR EXTEND THE LIMIT. + + + +7. THIRD PARTY RIGHTS. + +The Separate Files are delivered subject to and your use is governed by their own separate licence agreements. This Licence does not apply to such Separate Files and they are not included in the term “Deliverables” under this Licence. You agree to comply with all terms and conditions imposed on you in respect of such Separate Files including those identified in the Schedule (“Third Party Terms”). + + + +ARM HEREBY DISCLAIMS ANY AND ALL WARRANTIES EXPRESS OR IMPLIED FROM ANY THIRD PARTIES REGARDING ANY SEPARATE FILES, ANY THIRD PARTY MATERIALS INCLUDED IN THE DELIVERABLES, ANY THIRD PARTY MATERIALS FROM WHICH THE DELIVERABLES ARE DERIVED (COLLECTIVELY “OTHER CODE”), AND THE USE OF ANY OR ALL THE OTHER CODE IN CONNECTION WITH THE DELIVERABLES, INCLUDING (WITHOUT LIMITATION) ANY WARRANTIES OF SATISFACTORY QUALITY OR FITNESS FOR A PARTICULAR PURPOSE. + + + +NO THIRD PARTY LICENSORS OF OTHER CODE SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND WHETHER MADE UNDER CONTRACT, TORT OR OTHER LEGAL THEORY, ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE OTHER CODE OR THE EXERCISE OF ANY RIGHTS GRANTED UNDER EITHER OR BOTH THIS LICENCE AND THE LEGAL TERMS APPLICABLE TO ANY SEPARATE FILES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + + + +8. GOVERNMENT END USERS. + +US Government Restrictions: Use, duplication, reproduction, release, modification, disclosure or transfer of the Deliverables is restricted in accordance with the terms of this Licence. + + + +9. TERM AND TERMINATION. + +This Licence shall remain in force until terminated by you or by ARM. Without prejudice to any of its other rights if you are in breach of any of the terms and conditions of this Licence then ARM may terminate this Licence immediately upon giving written notice to you. You may terminate this Licence at any time. Upon termination of this Licence by you or by ARM you shall stop using the Deliverables and confidential information and destroy all copies of the Deliverables and confidential information in your possession together with all documentation and related materials. Notwithstanding the foregoing, except where ARM has terminated this Licence for your breach, your rights to distribute the Example Code as part of Licensed Products developed prior to termination shall survive termination of this Licence, subject to the terms of this Licence. The provisions of Clauses 4, 6, 7, 8, 9 and 10 shall survive termination of this Licence. + + + +10. GENERAL. + +This Licence is governed by English Law. Except where ARM agrees otherwise in; (i) a written contract signed by you and ARM; or (ii) a written contract provided by ARM and accepted by you, this is the only agreement between you and ARM relating to the Deliverables and it may only be modified by written agreement between you and ARM. This Licence may not be modified by purchase orders, advertising or other representation by any person. If any clause or sentence in this Licence is held by a court of law to be illegal or unenforceable the remaining provisions of this Licence shall not be affected thereby. The failure by ARM to enforce any of the provisions of this Licence, unless waived in writing, shall not constitute a waiver of ARM's rights to enforce such provision or any other provision of this Licence in the future. + + + +The Deliverables provided under this Licence are subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. You agree to comply fully with all laws and regulations of the United States and other countries ("Export Laws") to assure that the Deliverables, are not (1) exported, directly or indirectly, in violation of Export Laws, either to any countries that are subject to U.S.A. export restrictions or to any end user who has been prohibited from participating in the U.S.A. export transactions by any federal agency of the U.S.A. government; or (2) intended to be used for any purpose prohibited by Export Laws, including, without limitation, nuclear, chemical, or biological weapons proliferation. + + + +To the extent that the provisions contained in this Licence conflict with any provisions of any other licence you have entered with ARM governing the Deliverables the provisions contained in this Licence shall prevail over and shall supersede any such conflicting provisions. + + + +SCHEDULE + +h5{margin-top:0cm;text-align:justify}. + +h5{margin-top:0cm;text-align:justify}. Part A + +*Hardware Binaries:* + +FPGA bitstream file for any or all of the Hardware Source identified below in this Part A + + + +*Software Binaries:* + +Motherboard configuration controller + +Daughterboard configuration controller + +Daughterboard Application note SelfTest + +SCP firmware + +Mali GPU Driver + +* * + +*Documentation:* + +Documentation, provided as PDF + + + +*Hardware Source:* + +Hardware netlists of the ARM CoreLink peripheral technology and components known as TLX-400, NIC-400, and PL330 + + + +*Header Files:* + +Provided as part of and with the Mali GPU Driver + + + +*Part B* + +*Wrapper:* + +Application Note wrapper file provided as hardware source files and netlists. + + + +*Part C: Example Code* + +(i) Platform specific libraries and source code. + +(ii) ARM source code of Application note SelfTest. + +* * + +*Part D: Separate Files* + + + +A. UEFI firmware, including drivers for third party components licensed to you under BSD 3-Clause. + + + +B. Linux kernel licensed to you under the GNU General Public License version 2.0 + + + +To the extent that ARM is obliged to do so, ARM hereby offers to supply the files which are subject to the GNU General Public Licence version 2 (identified above), in source code form, subject to the terms of the GNU General Public License version 2, upon request. This offer is valid for three (3) years from the date of your acceptance of this Licence. + + + +C. AP Trusted Firmware licensed to you under BSD 3-Clause. + + + +D. ARM Gator Profile driver and daemon licensed to you under the GNU General Public License version 2.0 + + + +To the extent that ARM is obliged to do so, ARM hereby offers to supply the files which are subject to the GNU General Public Licence version 2 (identified above), in source code form, subject to the terms of the GNU General Public License version 2, upon request. This offer is valid for three (3) years from the date of your acceptance of this Licence. + + + +/end + + + +ARM contract references: LES-PRE-20435 JUNO ARM DEVELOPMENT PLATFORM DELIVERABLES diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt b/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt new file mode 100644 index 0000000..705efcc --- /dev/null +++ b/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt @@ -0,0 +1,344 @@ +h2. License + +The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-5. + +h1. Accessing Source Code + +h2. Linaro Android Source Code + +Run the "linaro_android_build_cmds.sh":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/linaro_android_build_cmds.sh script, it will download the entire source code for both Android and the kernel and attempt to build it. + +The pinned and source manifests can be found here: + +* "Pinned Manifest":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/pinned-manifest.xml ("?":https://wiki.linaro.org/Platform/Android/ReproduceABuildExactly) +* "Source Manifest":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/source-manifest.xml + +h2. Kernel Source Code + +Obtain the exact *kernel source code* for this cycle by using the "linaro_kernel_build_cmds.sh":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/linaro_kernel_build_cmds.sh script to download the source and build it. You can get the kernel configuration from "here":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/kernel_config (listed above) + +h2. Compiling Linaro Android RootFS+Kernel + +The following simple steps download, install and compile a complete Linaro Android distribution + +* Download and install Ubuntu 12.04 64 bit or newer ("download":http://www.ubuntu.com) +* Install the following packages: + +bc. sudo apt-get install zip curl flex bison build-essential git-core gnupg gperf zlib1g-dev libx11-dev x11proto-core-dev \ +gcc-multilib g++-multilib libc6-dev-i386 ia32-libs lib32z-dev gcc-4.5 g++-4.5 cpp-4.5 gcc-4.5-multilib g++-4.5-multilib \ +uuid-dev openjdk-6-jdk ant lib32ncurses5-dev xsltproc + +* Download the Android building script for this release from "here":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/linaro_android_build_cmds.sh or from the list of artifacts listed above. + +* Run the script + +bc. chmod a+x linaro_android_build_cmds.sh +./linaro_android_build_cmds.sh + +h3. Installing Android on your board + +* Insert a USB drive and note the assigned @'/dev/sdX'@ or @'/dev/mmcblk0'@ + +bc. dmesg | less + +Look for a line that looks like the following at the end of the log + +@[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 <sdc5 sdc6 >@ + +Or, if your machine uses '/dev/mmcblkX', you may see a line line this: + +@[10770.938042] mmcblk0: p1 p2 p3 p4 < p5 p6 >@ + +*WARNING:* In the next step, make sure you use /dev/"whatever you see above". *You can erase your hard drive* with the wrong parameter. + +* Create media + +bc. cd android/out/target/product/ +sudo linaro-android-media-create --mmc /dev/sdX --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 + +* Insert the USB drive into your board and reboot it + +p. You must configure UEFI exach time you create a new disk image. + +h2. Compiling and installing your Kernel + +h3. Prerequisites + +* Download and install Ubuntu 12.04 64 bit or newer ("download":http://www.ubuntu.com) +* Install the following packages by typing: + +bc. sudo apt-get install build-essential git curl + +* toolchain + +bc. mkdir -p ~/bin +cd ~/bin +wget http://releases.linaro.org/13.11/components/toolchain/binaries/gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz +tar xf gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz +PATH=$PATH:~/bin/gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux/bin + +* Create a working subdirectory +* Download the auto build script for this release from the list of artifacts above (the kernel configuration will be automatically downloaded). +* Run the build script + +bc. chmod a+x linaro_kernel_build_cmds.sh +./linaro_kernel_build_cmds.sh + +h1. Installing your kernel + +This section is common for both Android and OpenEmbedded + +* Create the Device Tree blob if you don’t have one in your Linaro image (note, the A9 Core Tile boots using an ATAGS kernel): + +bc. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dtbs + +* Insert the USB drive containing the Linaro disk image +* Copy the kernel onto the memory card + +bc. cp arch/arm64/boot/Image /media/boot/ +cp arch/arm64/boot/dts/juno.dtb /media/boot + +* Eject the USB drive @eject /media/boot@ + +* Insert the USB drive into the board and power it on + + + + +h1. Building Firmware From Source + +h2. Prerequisites + +The following tools and environment are required: + + +* Ubuntu desktop OS and the following packages. ARM have only tested with Ubuntu 12.04.02 (64-bit). +** `git` package to obtain source code +** `ia32-libs` package +** `build-essential` and `uuid-dev` packages for building the UEFI and Firmware Image Package (FIP) tool + +* Baremetal GNU GCC tools. Can be downloaded from Linaro +** "http://releases.linaro.org/13.11/components/toolchain/binaries/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz":http://releases.linaro.org/13.11/components/toolchain/binaries/gcc-linaro-aarch64-none-elf-4.8-2013.11_linux.tar.xz + +* The instructions on this page below assume that the environment variable $JUNO_ROOT_DIR has been initialised to a working directory. + +bc. $ export JUNO_ROOT_DIR=<path-to-working-dir>/<name-of-working-dir> + + + +h1. Building the components + +h2. SCP Firmware + +The SCP Firmware is only available as a pre-built binary. + + + +h2. AP Trusted Firmware + +The AP trusted firmware consists of the following images: + +|<b>Filename</b>|<b>Image Type</b>|<b>Image Name</b>| +|bl1.bin|BL1|AP Trusted ROM image| +|bl2.bin|BL2|AP Trusted Firmware| +|bl31.bin|BL3-1|EL3 runtime| +|bl32.bin|BL3-2|Test Secure Payload| + +The bl2.bin, bl31.bin and bl32.bin images are inputs to the process of creating a Firmware Image Package. + +h3. Obtaining sources + +Clone the ARM Trusted Firmware repository from GitHub: + +bc. $ cd $JUNO_ROOT_DIR +$ git clone "$":https://github.com/ARM-software/arm-trusted-firmware.git +$ cd arm-trusted-firmware +$ git checkout v0.3-Juno-0.3 + +h3. Configuration + +Set the compiler path + +bc. $ export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf- + +h3. Building + +1. Change to the trusted firmware directory: + +bc. $ cd $JUNO_ROOT_DIR/arm-trusted-firmware + +2. Build the different firmware images: + +bc. $ make PLAT=juno all + +By default this produces a release version of the build. To produce a debug version instead and make the build more verbose use: + +bc. $ make PLAT=juno DEBUG=1 V=1 all + +The build process creates products in a `build` directory tree, building the objects for each boot loader stage in separate sub-directories. The following boot loader binary files are created: + + `build/juno/<build-type>/bl1.bin` + + `build/juno/<build-type>/bl2.bin` + + `build/juno/<build-type>/bl31.bin` + + `build/juno/<build-type>/bl32.bin` + + + +... where `<build-type>` is either `debug` or `release`. + + + +To clean the AP Trusted Firmware source tree (warning, this will remove the binaries too): + +bc. $ make realclean + + + +h2. UEFI + +UEFI is a single bl33.bin image that is an input to the process of creating a Firmware Image Package. + +h3. Obtaining sources + +Clone the Juno UEFI Github repository: + +bc. $ cd $JUNO_ROOT_DIR +$ git clone https://github.com/ARM-software/edk2.git -b juno +$ cd edk2 +$ git checkout v0.3 + + + +h3. Configuration + +1. Define the AArch64 GCC toolchain: + +bc. $ export GCC48_AARCH64_PREFIX=<path-to-aarch64-gcc>/bin/aarch64-none-elf- + +2. Configure Tianocore environment: + +bc. $ cd $JUNO_ROOT_DIR/edk2 +$ . edksetup.sh +$ make -C BaseTools + +h3. Building + +1. Change to the EDK2 directory: + +bc. $ cd $JUNO_ROOT_DIR/edk2 + +2. To build DEBUG version of UEFI firmware: + +bc. $ make -f ArmPlatformPkg/ArmJunoPkg/Makefile + +The build produces the binary $JUNO_ROOT_DIR/edk2/Build/ArmJuno/DEBUG_GCC48/FV/BL32_AP_UEFI.fd that should be used as 'bl33.bin' when generating the Firmware Image Package binary. + +To build RELEASE version of UEFI firmware: + +bc. $ make -f ArmPlatformPkg/ArmJunoPkg/Makefile EDK2_BUILD=RELEASE + +Use the release binary $JUNO_ROOT_DIR/edk2>/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd as bl33.bin when generating the Firmware Image Package binary. + +To clean EDK2 source tree: + +bc. $ make -f ArmPlatformPkg/ArmJunoPkg/Makefile clean + + + +h2. Packaging the binaries + +ARM Trusted Firmware uses the Firmware Image Package (FIP) binary blob to load images into the system, so that the firmware can avoid managing lots of smaller images. The FIP will contain: + + BL2 and BL3-1 boot loader images + + Test Secure Payload (BL3-2 image) + + UEFI firmware (BL3-3 image) + + SCP firmware (BL3-0 image) + +Note: BL1 image is NOT part of the FIP. + + +h3. Building a FIP binary + +The steps to create a FIP are as follows: + +1. Build the 'fip_create' tool. + +bc. $ cd $JUNO_ROOT_DIR/arm-trusted-firmware +$ make fiptool + +2. Define the FIP environment. Specifically, include the FIP tool in the path. + +bc. $ export PATH=$JUNO_ROOT_DIR/arm-trusted-firmware/tools/fip_create:$PATH + +3. Gather the binary files (the following example is for release builds only). + +bc. $ cd $JUNO_ROOT_DIR +$ mkdir fip +$ cd fip +$ cp <path to prebuilt binary>/bl30.bin . +$ cp $JUNO_ROOT_DIR/arm-trusted-firmware/build/juno/release/bl2.bin . +$ cp $JUNO_ROOT_DIR/arm-trusted-firmware/build/juno/release/bl31.bin . +$ cp $JUNO_ROOT_DIR/edk2/Build/ArmJuno/RELEASE_GCC48/FV/BL32_AP_UEFI.fd bl33.bin + + + +4. Create the FIP file: + +bc. $ fip_create --dump \ + --bl2 bl2.bin \ + --bl30 bl30.bin \ + --bl31 bl31.bin \ + --bl33 bl33.bin \ + fip.bin + + + +The previous command will display the FIP layout: + + + +bc. Firmware Image Package ToC: +--------------------------- +- Trusted Boot Firmware BL2: offset=0xD8, size=0x5268 +- SCP Firmware BL3-0: offset=0x5340, size=0x9C64 +- EL3 Runtime Firmware BL3-1: offset=0xEFA4, size=0x82A0 +- Non-Trusted Firmware BL3-3: offset=0x17244, size=0xF0000 +--------------------------- + +bc. Creating "fip.bin" + + + +5. Optional: the `fip_create` tool can be used in the exact same way to update individual images inside an existing FIP file. For example, to update the SCP Firmware BL3-0 image: + +bc. $ fip_create --dump --bl30 new_bl30.bin fip.bin + +The previous command will again display the FIP layout: + + + +bc. Firmware Image Package ToC: +--------------------------- +- Trusted Boot Firmware BL2: offset=0xD8, size=0x5268 +- SCP Firmware BL3-0: offset=0x5340, size=0x9C64 +file: 'new_bl30.bin' +- EL3 Runtime Firmware BL3-1: offset=0xEFA4, size=0x82A0 +- Non-Trusted Firmware BL3-3: offset=0x17244, size=0xF0000 +--------------------------- + +bc. Updating "fip.bin" + + + +For more details and options about the `fip_create` tool: + +bc. $ fip_create --help + + + diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt b/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt new file mode 100644 index 0000000..b489db4 --- /dev/null +++ b/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt @@ -0,0 +1,194 @@ +h2. License + +The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-5. + +h2. Juno ports + + + +h3. Back panel + +!Linaro_Release_Notes_v2_files/image001.png! + +h3. Front panel + +!Linaro_Release_Notes_v2_files/image002.png! + +h3. UARTs + +There are 4 UARTs on the Juno board: + +|<b>UART</b> +|<b>Location</b> +|<b>Used by</b> +|<b>Baud</b> +|<b>Data bits</b>| +|SoC UART0 +|"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, top slot. +|The motherboard, UEFI and the Linux kernel. +|115200 +|8 +| +|SoC UART1 +|"back panel":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel, bottom slot. +|SCP firmware +|115200 +|8 +| +|FPGA UART0 +|Corresponds to the J55 header on the board. Please contact ARM for more information about this type of header. +|AP Trusted Firmware +|115200 +|8 +| +|FPGA UART1 +|Corresponds to the J56 header on the board. Please contact ARM for more information about this type of header +|Unused at the moment +|- +|- +| + +h2. Quick Start + +If you have just unpacked a new Juno board and would like to get it booting straight away, you may wish to skip ahead to the “Set up and boot the Juno board” section. <make this a link> + + + +h4. Juno software stack overview + +There are several pieces of software that make up the complete Juno software stack, and a description of each one follows below. + +h4. Juno MCC Microcontroller Firmware + +The MCC is a microcontroller on the motherboard that takes care of early setup before the SCP or applications processors are powered on. The MCC is also responsible for managing firmware upgrades. + +h4. System Control Processor (SCP) Firmware + +The Juno System Control Processor (SCP) is an on-chip Cortex-M3 that provides low level power management and system control for the Juno platform. + +h4. Application Processor (AP) Trusted Firmware + +The Juno AP Trusted Firmware provides low-level Trusted World support for the Juno platform. + +h4. Unified Extensible Firmware Interface (UEFI) + +The Juno UEFI implementation provides Linux loader support for the Juno platform. It is based on the open source EFI Development Kit 2 (EDK2) implementation from the Tianocore sourceforge project. + +h4. Linux Kernel + +The Linaro Stable Kernel (LSK) for Juno. + +h4. Linux filesystem + +An Openembedded filesystem from Linaro can be mounted via USB (recommended) or NFS over Ethernet. + +h4. Android kernel and AOSP + +The LSK image contains Android patches and has a unified defconfig, so the same kernel binary will work with a Linux filesystem or an AOSP filesystem (available from Linaro). + + + +h3. Software preloaded on new Juno boards + +New Juno boards arrive preloaded with MCC firmware, SCP firmware, AP trusted firmware, UEFI, and a Linux kernel. The Juno board does not contain a Linux filesystem or Android AOSP filesystem anywhere in onboard storage. + +*Please note* that early batches of Juno boards contained an SCP firmware image that limits the CPU clock to 50 MHz. ARM strongly recommends that you immediately upgrade to the latest "firmware image":http://community.arm.com/docs/DOC-8396#jive_content_id_Juno_Board_Recovery_Image hosted on this website. <link should point to firmware tab> + +When the power is first turned on, it should boot straight through to Linux. UEFI offers a 10 second window during which you can interrupt the boot sequence by pressing a key on the serial terminal, otherwise the Linux kernel will be launched. In order to reach the Linux shell you must attach a Linux "filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem via USB. If no filesystem is attached then Linux will boot as far as it can and then announce that it is waiting for a filesystem to be attached. + +New Juno boards do not contain any Android software pre-installed. + + + +h3. Set up and boot the Juno board + +You are strongly recommended to update to the latest firmware before doing anything productive with your Juno board. + +The steps to set up and boot the board are: + +# Connect a serial terminal to the "UART0":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board connector ("settings":http://community.arm.com/docs/DOC-8396#jive_content_id_Setting_up_the_board). <UART0 link should point to the back panel picture, settings link should point to the UART table below it> +# Connect the 12 volt power, then press the red "ON/OFF button":http://community.arm.com/docs/DOC-8393#jive_content_id_Back_panel on the back panel. <link should point to the back panel picture> + +h3. Getting Juno to boot to the Linux shell + +If you have just received a new board and powered it on for the first time, you will not reach the Linux shell. Juno will boot Linux to the point where it looks for a filesystem, and when it can't find one it will sit and wait for one to be attached. To boot all the way to the Linux shell you will need to "attach a root filesystem":http://community.arm.com/docs/DOC-8396#jive_content_id_Deploying_a_root_filesystem. <the link should point to the relevant section in the “Binary Image Installation” tab> + +h3. Setting the Real Time Clock (required for Android) + +The example below demonstrates how to set the clock on the board: + +bc. ARM V2M-Juno Boot loader v1.0.0 +HBI0262 build 596 + +bc. ARM V2M_Juno Firmware v1.1.7 +Build Date: May 27 2014 + +bc. Time : 11:52:35 +Date : 09:07:2060 + +bc. Cmd> debug + +bc. Debug> date +09/07/2060 + +bc. Change Date? Y\N >y +D:>23 +M:>6 +Y:>2014 + +bc. Debug> time +15 : 51 : 58 + +bc. Change Time? Y\N >y +s:>0 +m:>08 +h:>14 + +bc. Debug> + + +h3. Enabling Texture Compression Formats + +The Mali GPU in Juno is able to use a variety of texture compression formats, many of which are subject to license from third parties. It is the responsibility of the end user to obtain a license for each texture that will be used on Juno. Once such licenses are obtained, the textures can be enabled by the following procedure: + +1. Connect a serial terminal to the top 9-pin UART0 connector on the rear panel (115200 baud, 8, n, 1). + +2. Connect a USB cable between the USB-B connector on the rear panel and a USB port of your host computer. + +3. Connect the 12 volt power supply to the board. + +The serial terminal will show the command prompt Cmd> + +4. At the Cmd> prompt on the serial terminal, issue the command usb_on + +bc. Cmd> usb_on + +The configuration flash memory should now be visible on the host computer as a mass storage device. + +5. Open the file SITE1/HBI0262B/board.txt for editing. + +6. Consult the “Mali-T600 Series GPU Configuration and Sign-off Guide” to determine the correct value that should be programmed into the GPU texture format register to enable only the registers that you have licensed for use with Juno. For example, to enable all texture compression formats, the value should be 0xFFFFFFFF. + +7. In the [SCC REGISTERS] section, below the “TOTALSCCS” line, insert the following line: + +SCC: 0x05C <value from step 6 above> ;Optional comment to explain which texture you have enabled + +8. Update the TOTALSCCS count (increment it by one) so that it now reflects the total number of SCC registers that are programmed. + +9. Press the red ON/OFF button on the rear panel of the board and wait for reprogramming to complete. + +The board will load the default configuration and boot up. + +h3. Additional documentation + +For further details, please see the following documents. + +· Juno SoC Reference Manual + +· V2M Juno Reference Manual + +· SCPI protocol description + + + + diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_install.txt b/android/images/armv8-juice-juno-lsk/HOWTO_install.txt new file mode 100644 index 0000000..bb84abd --- /dev/null +++ b/android/images/armv8-juice-juno-lsk/HOWTO_install.txt @@ -0,0 +1,160 @@ +h2. License + +The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-5. + +h2. Installation + +Linaro Android releases are made up of the following components. + +| *.img.bz2 | pre-built Android disk image | +| kernel | kernel binary | +| bl1.bin | ARM Trused Firmware BL1 binary | +| fip.bin | ARM Trused Firmware Firmware Image Package (FIP) binary | +| juno.dtb | Device Tree Binary | +| ramdisk.img | Ramdisk image | +| linaro_android_build_cmds.sh | Build script for the complete Android release | +| linaro_kernel_build_cmds.sh | Build script for the Linux kernel | + +Other files such as *manifest*, *.txt and *.html provide information such as package contents or MD5SUMs about the files they share a common filename with. + +Linaro provides two methods for installing Linaro binary builds: + +# Using a pre-built image, which you can download +# Assembling your own image using provided components + +h2. Pre-Installation Steps + +Before any installation begins, it is important that you ensure your board has the latest firmware installed. Please see "Juno Board Recovery Image and MCC firmware update" below for the latest updates and installation instructions. The 14.06 release has been tested with Firmware version 0.7.1, but we always recommend that users install the latest version available. + +h2. Using pre-built image + +h3. Prerequisites + +* Ubuntu 12.04 64 bit or newer on your desktop PC, which you can download from "www.ubuntu.com":http://www.ubuntu.com +* 4GB USB drive or larger +* Latest firmware installed onto the board. Please see "Firmware Update tab":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-4 +* This release pre-built image (vexpress.img.bz2), which you can downloaded from the above list of artifacts or just click "here":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/vexpress.img.bz2 + +h3. Installation Steps + +* Unzip the downloaded pre-built image +* Insert USB drive into your PC and note the assigned @'/dev/sdX'@ + +bc. dmesg +DRIVE=/dev/sdX # USB drive found from dmesg above +bzcat vexpress.img.bz2 | sudo dd bs=64k of=$DRIVE + +When the image is created, skip down to the section "Booting the image". + +*Note:* Windows users may use the "Image Writer for Windows":https://launchpad.net/win32-image-writer/+download + +<hr> + +h2. Building a custom image using pre-built components. + +Sometimes, you may wish to build your own custom image for your board. Perhaps you wish to use a more recent snapshot of the "hardware pack":https://wiki.linaro.org/HardwarePacks or take the latest Android build. Whatever the reason, you will want to use the "Linaro Image Tools":https://wiki.linaro.org/Linaro-Image-Tools to create a custom image. + +Using components to generate the image will yield the same functionality found in the pre-built image of the same release. + +h3. Prerequisites + +* Ubuntu 12.04 64 bit or newer on your desktop PC, which you can download from "www.ubuntu.com":http://www.ubuntu.com +* Download Artifacts from above or use the following command in your terminal + +bc. wget http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/boot.tar.bz2 +wget http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/system.tar.bz2 +wget http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/userdata.tar.bz2 + +* Get "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools. There are multiple ways you can get the latest Linaro Image Tools: + +** Method 1: Install them from the Linaro Image Tools "PPA":https://launchpad.net/~linaro-maintainers/+archive/tools + +bc. sudo add-apt-repository ppa:linaro-maintainers/tools +sudo apt-get update +sudo apt-get install linaro-image-tools + +** Method 2: Building from source + +bc. wget http://releases.linaro.org/14.06/components/platform/linaro-image-tools/linaro-image-tools-2014.06.tar.gz + +* Insert the USB drive and note the assigned @'/dev/sdX'@ or @'/dev/mmcblk0'@ + +bc. dmesg | less + +Look for a line that looks like the following at the end of the log + +@[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 <sdc5 sdc6 >@ + +Or, if your machine uses @'/dev/mmcblkX'@, you may see a line line this: + +@[10770.938042] mmcblk0: p1 p2 p3 p4 < p5 p6 >@ + +*WARNING:* In the next step, make sure you use @/dev/"whatever you see above"@. *You can erase your hard drive* with the wrong parameter. + +* Create media + +bc. linaro-android-media-create --mmc /dev/sdX --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 + +h2. Booting the image + +After the media create tool has finished executing, remove the USB drive from your PC and insert it into the board. + +Before you can boot the image you will need to install the latest firmware on the board. The instructions below provide information on how to do this. See the "UEFI wiki":https://wiki.linaro.org/ARM/UEFI#Configure_UEFI for more information on how to configure UEFI to boot disk images. + +h2. DS-5 Configuration Files for Juno + +As an optional step, you may wish to install DS-5 configuration files that will allow you to debug Juno. The procedure is as follows: + +1. Extract the DS-5 config files anywhere on your host PC. + +2. Start DS-5 and select "Preferences" from the "Window" menu. + +3. In the window that opens, expand the "DS-5" heading and select "Configuration Database" + +4. In the dialogue that opens, fill in: + +a. Name, which can be any string you like e.g. "Juno". + +b. Location, which must be the directory that you extracted the DS-5 config files to. Note this is not the "boards" directory, but the parent directory that now contains "boards". + +5. Click Ok to close the dialogue + +6. Back in the "Configuration Database" screen, click on "Rebuild database" then click Ok. + + + +h2. Juno Board Recovery Image and MCC firmware update + +This section describes how to reset all firmware images to their factory default state. This procedure is also the only way that you can install updates to the MCC firmware. + +The configuration of the Juno Development Platform board is determined by a set of files stored on a flash memory device on the board. The flash memory can be accessed via a USB-B socket on the rear panel of the board. When connected to a host computer, the flash memory will appear as a USB mass storage device with a FAT16 filesystem. The files in this filesystem are edited to control the configuration of the board. + +The configuration of the Juno Development Platform board can be returned to factory default by extracting the board recovery image onto the flash memory device, replacing any files already in the flash memory. + +To update the MCC firmware only, the procedure is just the same except that the MCC firmware update bundle will contain only a subset of the files contained in the full recovery image. + +To carry out a system recovery or update the MCC firmware, follow these steps: + +1. Connect a serial terminal to the top 9-pin UART0 connector on the rear panel (115200 baud, 8, n, 1). + +2. Connect a USB cable between the USB-B connector on the rear panel and a USB port of your host computer. + +3. Connect the 12 volt power supply to the board. + +The serial terminal will show the command prompt Cmd> + +4. At the Cmd> prompt on the serial terminal, issue the command usb_on + +bc. Cmd> usb_on + +The configuration flash memory should now be visible on the host computer as a mass storage device. + +5. Save to the host PC any of the existing files in the configuration flash memory that you wish to retain for future use. + +6. If you wish to update the MCC firmware only then skip to step 7. Otherwise, for a full system recovery, format the configuration flash memory (FAT16). + +7. Extract the board recovery image to the root directory of the configuration flash memory, preserving the directory structure. + +8. Press the red ON/OFF button on the rear panel of the board and wait for reprogramming to complete. + +The board will load the default configuration and boot up. diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt b/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt new file mode 100644 index 0000000..9b19b1b --- /dev/null +++ b/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt @@ -0,0 +1,161 @@ +h2. License + +The use of Juno software is subject to the terms of the Juno "End User License Agreement":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-5. + + +h2. About Juno + +Juno is the first 64-bit development platform from ARM, featuring a dual Cortex-A57 "big" cluster, a quad Cortex-A53 "little" cluster, and a Mali T624 GPU cluster with four shader cores. + +This board is lead-free (it does not contain Pb). + + + +h2. About the Linaro Stable Kernel (LSK) + +The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the linux stable kernel tree. The LSK focuses on quality and stability and is therefore a great foundation for product development. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes. + +LSK releases appear monthly. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-3 tab). + + +h2. About the Linaro Android Release for ARMv8 + +The Linaro Android release is based on Android AOSP master snapshot dated June 1st 2014, the release uses Linaro Linux LSK version 3.10 and is integrated with ARM Mali drivers for 3D graphics acceleration, the sources are built using Linaro GCC version 4.9. + +The Android AOSP software provided in this release is thoroughly tested for CTS version 4.4, the CTS results are shared with members, the BIONIC component is validated with Android BIONIC tests, Android Monkey tests were run for stress testing, OpenGL 3D graphics rendering is validated manually to check for any UI artifacts, multi-lib (both 64bit and 32bit applications) were validated using examples provided in Android NDK. + +The Linaro Android releases for Juno appear monthly. Sources are also made available so you can build your own images (see the "Building from Source tab":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-5). + + + +h2. Support + +Please send any support enquiries to "juno-support@arm.com":mailto:juno-support@arm.com?subject=Juno%20support%20request + + + +h2. Functionality in this release + +The current release supports the following: + +* Full cold boot support to Linux shell or Android homescreen +* Multicore support in Linux, all six CPUs enabled. +* Experimental big.LITTLE MP support. The code is functional but has not been tuned and there are no performance guarantees. +* Full USB driver support in Linux, for access to mass storage and input devices. +* There is no GPU support for Linux in this release. +* GPU support in Android, functional but *not performant*. The performance issues will be addressed in the next release. +* HDLCD is fully supported, but is not performant on Android. This will be addressed in the next release. +* Thermal protection is enabled. If the SoC reaches 85C it will shut down. Linux will receive a warning at 75C. +* Stable operating points are enabled for nominal (Cortex-A57 800MHz, Cortex-A53 700MHz, Mali T624 600MHz) and overdrive (Cortex-A57 1100MHz, Cortex-A53 850MHz). +* DVFS is supported in the SCP firmware and the Linux CPUFreq driver. +* The Linux CPUIdle driver is included, but is disabled by default. The latency table has not been tuned and when CPUIdle is enabled, performance suffers accordingly. This will be addressed in the next release. +* Android patches and defconfig have been merged to unify the Linux and Android kernels. +* There is no PCIe support in this release. + +h3. Functionality listed by software component + +h4. SCP Firmware + +* System configuration +* DDR initialization +* Basic power state management +* SCPI commands (Ready, Set/Get Clocks, Set/Get CPU power states) +* Thermal protection (shutdown at 85C) +* DVFS support + +h4. AP Trusted Firmware + +* Send the SCP firmware to SCP +* Initialize the Trusted World before transitioning into Normal World. +* Service CPU hotplug requests coming from Normal World + +h4. UEFI + +* Booting an Operating System from NOR Flash or USB mass storage +* Support for Ethernet and PXE boot + +h4. Linux Kernel + +* Enable Juno Compute Subsystem comprised of a dual A57 core cluster and a quad A53 core cluster. +* Enable a limited set of peripherals present on the Juno development board: on-chip USB, non-secure UART, HDMI output, keyboard and mouse functionality over PS/2 connector, Ethernet support via on-board SMSC ethernet chip. +* Experimental big.LITTLE support +* Unified kernel and kernel config for Android and Linux. + +h3. Limitations listed by software component + +h4. SCP Firmware + +* A number of SCPI commands are not yet implemented or are incomplete. + +h4. AP Trusted Firmware + +* Does not support changing the primary core using SCC General Purpose Register 1. +* Does not support bringing up secondary cores using PSCI CPU_ON when they have been enabled at boot time by SCP using SCC General Purpose Register 1. +* Does not support Secure-EL1 Payload (i.e. BL3-2) +* Does not support CPU suspend + +h4. UEFI + +* No PCI Express support included +* No display controller support +* No USB OHCI support. Only EHCI is supported + +h4. Linux Kernel + +* No PCI Express support included +* No support for MALI graphics other than in Android releases +* big.LITTLE support is experimental and there are no guarantees of performance. This support is disabled by default and must be "enabled":http://community.arm.com/docs/DOC-8664#biglittleenable before it can be used. + + + + +h2. Android AOSP Patch Summary + +The following list of patches developed by ARM and Linaro engineering teams were applied to Android AOSP dated June 1st 2014 to get Android booting to UI on ARMv8 Juno development platform. These patches can be found on Linaro's Android Git repositories. Few of these patches have been submitted to AOSP and being tracked for acceptance. + +* "build boot files and generate tarballs":https://android.git.linaro.org/gitweb/platform/build.git/commit/6a33bdf27388be96ed49b7eea4ee3f1ca90700e8 +* "set default runtime and zygote property in device config files":https://android.git.linaro.org/gitweb/platform/build.git/commit/2f9ad5ea5eb6ce50d17a600f1df3403bb1e7c60d +* "Increase timeouts":https://android.git.linaro.org/gitweb/platform/frameworks/base.git/commit/4776a5761247eca5750f52757d85bb060570b126 +* "Fix resolution issues for Juno.":https://android.git.linaro.org/gitweb/platform/frameworks/native.git/commit/ffa8b0c201615095f6783bc763b0bab9dbea9e33 +* "AArch64: force SurfaceFlinger to use last egl config":https://android.git.linaro.org/gitweb/platform/frameworks/native.git/commit/bba5860061cb0119ec8d08da766a3c58b51f9fe4 +* "Don't use memset to clear the framebuffer on arm64":https://android.git.linaro.org/gitweb/platform/hardware/libhardware.git/commit/d3080813c4284cd9a700bdc86bf3ee7807b8ceb4 +* "Increase timeouts for slow platforms":https://android.git.linaro.org/gitweb/platform/libcore.git/commit/c2ae1bd6b1879071a4ca0f0b3507f695759ebab9 +* "Don't write to the tty in init to avoid the cursor":https://android.git.linaro.org/gitweb/platform/system/core.git/commit/3e1977b8f719cc4e652902d7cd2331893d74ac6d +* "Quick and dirty utility to sync the system clock on Juno":https://android.git.linaro.org/gitweb/platform/system/core.git/commit/60d4dfae50a65980b34f28639b468aa8bddea271 +* "bionic libc test: make it can be compiled for 64 bit":https://android.git.linaro.org/gitweb/platform/system/extras.git/commit/fcfff0a2c6e95e9e8e0643b4a4e495be60b1189c + + + +h2. Known Issues + +h3. Issues on OpenEmbedded images + +* "ARM-133":https://cards.linaro.org/browse/ARM-133 2nd USB Mass storage device fails +* "ARM-134":https://cards.linaro.org/browse/ARM-134 nfs v4 hangs when creating symlinks +* "Bug 48":https://bugs.linaro.org/show_bug.cgi?id=48 password authentication over SSH doesn't work +* "LP:1192942":https://bugs.launchpad.net/linaro-oe/+bug/1192942 Invalid ps busybox option '-a' when starting or stopping cups +* "LP:1196907":https://bugs.launchpad.net/linaro-oe/+bug/1196907 HTTP downloads get cut short in Foundation model +* "LP:1212126":https://bugs.launchpad.net/linaro-oe/+bug/1212126 perf self test does not execute on Linaro openembedded lamp image +* "LP:1212115":https://bugs.launchpad.net/linaro-oe/+bug/1212115 phpmysql test fail on Linaro openembedded Lamp image on Lava +* "LP:1081162":https://bugs.launchpad.net/linaro-oe/+bug/1081162 No arm64 support in klibc +* "LP:1235239":https://bugs.launchpad.net/linaro-oe/+bug/1235239 level 1 translation fault when extracting bzipped tarball + +h3. Issues on all Android images + +* "ARM-135":https://cards.linaro.org/browse/ARM-135 Juno: Android fails to boot when board has a date in the future +* "Bug 54":https://bugs.linaro.org/show_bug.cgi?id=54 DNS loopup doesn't work +* "Bug 45":https://bugs.linaro.org/show_bug.cgi?id=45 CTS errors - Unable to resolve host "loca" : No address associated with hostname + +h3. Issues on Android for ARMv8 images + +* "Bug 51":https://bugs.linaro.org/show_bug.cgi?id=51 Two tests from command-bionic_libc_tests fail on LAVA +* "Bug 23":https://bugs.linaro.org/show_bug.cgi?id=23 backtrace_test reports failures on 64/64 build +* "Bug 11":https://bugs.linaro.org/show_bug.cgi?id=11 Browser crashes on Juno in 14.06 RC +* "Bug 10":https://bugs.linaro.org/show_bug.cgi?id=10 settings crashed when running monkey + +h3. Issues on Juice images + +* "Bug 22":https://bugs.linaro.org/show_bug.cgi?id=22 Caffeinemark crashes +* "Bug 21":https://bugs.linaro.org/show_bug.cgi?id=21 browser crash when closing a tab +* "Bug 12":https://bugs.linaro.org/show_bug.cgi?id=12 Intermittent HDMI failures on 14.06 RC + |