diff options
38 files changed, 0 insertions, 6286 deletions
diff --git a/android/images/armv8-android-fvp-lsk/HOWTO_getsourceandbuild.txt b/android/images/armv8-android-fvp-lsk/HOWTO_getsourceandbuild.txt deleted file mode 100644 index 6d9a6e4..0000000 --- a/android/images/armv8-android-fvp-lsk/HOWTO_getsourceandbuild.txt +++ /dev/null @@ -1,28 +0,0 @@ -h2. How to download and build Android sources - -Recommended method to do a linaro android build is to use linaro android build script(linaro_android_build_cmds.sh). You can download this script from the Downloads section of the build page. Use this script to do a complete ARMv8 Android build for FVP models from scratch. If you prefer to do it manuaaly then follow the "Get the source" and "Build" instructions below. - -h3. Get the source -<pre> - $ sudo add-apt-repository ppa:linaro-maintainers/tools - $ sudo apt-get update - $ sudo apt-get install gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc openjdk-7-jdk openjdk-7-jre vim-common python-parted python-yaml wget uuid-dev - $ curl "https://android.git.linaro.org/gitweb?p=tools/repo.git;a=blob_plain;f=repo;hb=refs/heads/stable" > repo - $ chmod +x repo - $ ./repo init -u git://android.git.linaro.org/platform/manifest.git -b linaro-android-14.06-release -m armv8-android-fvp-lsk.xml - $ ./repo sync # this may take some time -</pre> - -h3. Build -<pre> - $ export CPUS=`grep -c processor /proc/cpuinfo` - $ export TARGET_PRODUCT=vexpress - $ export TARGET_BUILD_VARIANT=eng - $ export USE_LINARO_TOOLCHAIN=true - $ . build/envsetup.sh - $ make -j${CPUS} boottarball systemtarball userdatatarball -</pre> - -h2. Running the build on FVP models - -Follow "Binary Image Installation" tab for instructions. diff --git a/android/images/armv8-android-fvp-lsk/HOWTO_install.txt b/android/images/armv8-android-fvp-lsk/HOWTO_install.txt deleted file mode 100644 index b886ad7..0000000 --- a/android/images/armv8-android-fvp-lsk/HOWTO_install.txt +++ /dev/null @@ -1,104 +0,0 @@ -h2. Prerequisites - -You'll need latest ARM FVP Base models and a license to use the models. Follow the instructions at http://www.arm.com/products/tools/models/fast-models/foundation-model.php - -h2. Get artifacts - -Scroll down and click on 'Downloads' - -Click on each link to download: -* boot.tar.bz2 -* system.tar.bz2 -* userdata.tar.bz2 - -h2. Get linaro image tools - -Run these commands to get all the dependencies for linaro-image-tools and the tip of linaro-image-tools - -<pre> - $ sudo add-apt-repository ppa:linaro-maintainers/tools - $ sudo apt-get update - $ sudo apt-get install linaro-image-tools -</pre> -You can also use the tip of linaro-image-tools from http://git.linaro.org/infrastructure/linaro-image-tools.git - -h2. Create mmc image for the ARM FVP Base AEMv8 models - -Run linaro image tools - -pre. $ linaro-android-media-create --image_file mmc.bin --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2 - -If you're using tip of linaro image tools - -pre. $ ./linaro-image-tools/linaro-android-media-create --image_file mmc.bin --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2 - -h2. Running the models (verified on FVP Base model build 5602) - -<pre> - $ tar -jxvf boot.tar.bz2 - $ cd boot/ - $ /path/to/FVP_Base_AEMv8A-AEMv8A/models/Linux64_GCC-4.1/FVP_Base_AEMv8A-AEMv8A \ - -C pctl.startup=0.0.0.0 \ - -C bp.secure_memory=0 \ - -C cluster0.NUM_CORES=4 \ - -C cluster1.NUM_CORES=4 \ - -C cache_state_modelled=0 \ - -C bp.pl011_uart0.untimed_fifos=1 \ - -C bp.secureflashloader.fname=bl1.bin \ - -C bp.flashloader0.fname=fvp_fip.bin \ - -C bp.virtioblockdevice.image_path=../mmc.bin -</pre> - -h3. Set UEFI configuration, update kernel/ramdisk path and bootargs - -Stop the UEFI boot process and configure it for FVP models: - -<pre> -$ telnet 127.0.0.1 -debug 5000 -e ^z -Telnet escape character is 'b'. -Telnet escape character is '^Z'. -Trying 127.0.0.1... -setsockopt (SO_DEBUG): Permission denied -Connected to 127.0.0.1. -Escape character is '^Z'. - 7 seconds -[1] Linaro disk image on virtio -[2] Shell -[3] Boot Manager -Start: 3 -[1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 2 -[1] Linaro disk image on virtio -Update entry: 1 -File path of the EFI Application or the kernel: kernel -Has FDT support? [y/n] y -Add an initrd: [y/n] y -File path of the initrd: ramdisk.img -Arguments to pass to the binary: console=ttyAMA0 earlyprintk=pl011,0x1c090000 amba-clcd.mode=VGA -Description for this new Entry: Linaro disk image on virtio -[1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 5 -[1] Linaro disk image on virtio -[2] Shell -[3] Boot Manager -Start: 1 - PEI 1122 ms - DXE 259 ms - BDS 8 ms -Total Time = 1390 ms - -[ 0.000000] Initializing cgroup subsys cpu -[ 0.000000] Linux version 3.10.40-04438-g6a78140 (pundiramit@flying-dutchman) (gcc version 4.9 20140514 (prerelease) (GCC) ) #1 SMP Mon Jun 2 14:50:25 IST 2014 -</pre> - -h3. Black screen - -The boot screen has been disabled to speed up booting. This means you may not see anything on the CLCD terminal for a while depending on the performance of the machine the model is running on. For example a first boot on a 2 GHz machine with 32 GB of RAM took 20 minutes. Subsequent boots should take approximately half the time to boot. diff --git a/android/images/armv8-android-fvp-lsk/HOWTO_prebuilt.txt b/android/images/armv8-android-fvp-lsk/HOWTO_prebuilt.txt deleted file mode 100644 index f699a3e..0000000 --- a/android/images/armv8-android-fvp-lsk/HOWTO_prebuilt.txt +++ /dev/null @@ -1,69 +0,0 @@ -Instructions for https://android-build.linaro.org/builds/~linaro-android/<BUILD_NAME>/ - -= Get artifacts = - - Scroll down to the 'Downloads' section - - Click on each link to download: - boot.tar.bz2 - system.tar.bz2 - userdata.tar.bz2 - -= Get linaro image tools = - - Run these commands to get all the dependencies for linaro-image-tools and the tip of linaro-image-tools - - $ sudo add-apt-repository ppa:linaro-maintainers/tools - $ sudo apt-get update - $ sudo apt-get install linaro-image-tools - - If you're using a released build (with a -release or from releases.linaro.org), skip this step. - If you're using a "tip" build do not skip the step and do the following: - - $ sudo apt-get install bzr - $ bzr branch lp:linaro-image-tools - -= Create media (SD card) = - - Disable automount (instructions provided for Gnome) - - $ TMP1=$(dconf read /org/gnome/desktop/media-handling/automount) - $ TMP2=$(dconf read /org/gnome/desktop/media-handling/automount-open) - $ dconf write /org/gnome/desktop/media-handling/automount false - $ dconf write /org/gnome/desktop/media-handling/automount-open false - - Insert an SD card - - Run 'dmesg' - - $ dmesg - - Look for a line that looks like the following at the end of the log - - [288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 > - - WARNING: In the next step, make sure you use /dev/"whatever you see above". - You can erase your hard drive with the wrong parameter. - - Run linaro image tools - - $ linaro-android-media-create --mmc /dev/sdc --dev <BOARD> --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - - If you're using tip of linaro image tools - - $ ./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc --dev <BOARD> --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - - To find <BOARD> run linaro-android-media-create with a -h and read the help. - - Restore automount - - $ dconf write /org/gnome/desktop/media-handling/automount $TMP1 - $ dconf write /org/gnome/desktop/media-handling/automount-open $TMP2 - - Remove the SD card from the device writer and plug it into the board. - -= Check console output = - - Plug in an USB-to-serial converter and run minicom - - $ minicom -D /dev/ttyUSB0 -w -C minicom.txt diff --git a/android/images/armv8-android-fvp-lsk/HOWTO_releasenotes_armv8-android-fvp-lsk.txt b/android/images/armv8-android-fvp-lsk/HOWTO_releasenotes_armv8-android-fvp-lsk.txt deleted file mode 100644 index 2b8c8a9..0000000 --- a/android/images/armv8-android-fvp-lsk/HOWTO_releasenotes_armv8-android-fvp-lsk.txt +++ /dev/null @@ -1,54 +0,0 @@ - -h2. About the Linaro Android Release for FVP (Multi-arch 64-bit) - -The Linaro Android release for FVP is based on a snapshot of the Android AOSP master taken on the 1st June. The build contains multi-arch support allowing full use of the 64-bit ARMv8-A architecture and supports both 64-bit and 32-bit applications. Java-only applications will run as 64-bit in the supplied configuration with no modification. The release uses Linaro Stable Kernel version 3.10 and runs on FVP Base AEMv8 model 0.8 build 5202 and later. The sources are built using Linaro GCC version 4.9. - -The ARMv8-A reference software stack combined with the Juno ARM Development Platform (ADP) provides the ARM ecosystem with a foundation to accelerate Android availability on 64-bit silicon. The availability of this port is the culmination of a broad architecture enablement program carried out by Linaro, ARM and the ARM partnership. ARM partners will now have access to an AOSP file system with support for both 64-bit and 32-bit apps, together with a broad range of supporting material including the ARMv8-A FVP models, open source toolchain from Linaro and supporting documentation. - -For those with access to the FVPs, this release can be used to examine the internals of the Android Open Source Project in a running system. Application developers, particularly those working in Java, will also be able to use develop some applications via the recently announced Android 'L' preview SDK. - -It should be noted that this is an early software preview and not all 3rd party applications will run correctly at this time. Performance is limited due to the ART runtime running in interpreted mode, more recent versions of the AOSP tree have now enabled this and future monthly builds will feature much better performance, along with wider compatibility as the baseport and AOSP matures. Next month's build in particular will improve as the ART backend compiler is enabled along with some recent optimizations. - -The Android AOSP software provided in this release is functionally tested with CTS version 4.4 and the CTS results are shared with members. The BIONIC component is validated with Android BIONIC tests. Android Monkey tests were run for stress testing. Multi-arch support has been validated using examples provided in Android NDK. Detailed CTS results are made available to members seperately through the Juice mailing list. - -The Linaro Android releases for FVP 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-android-fvp-lsk/#tabs-2). - -A build for the Juno ARM Development Platform is available "here":http://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk - -p. Android AOSP Patches - 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 Fast Models. 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. Where To Find More Information - -More information on Linaro can be found on our "website.":http://www.linaro.org/ - -h2. Feedback and Support - -Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. - -** Linaro Android Development "mailing list":http://lists.linaro.org/mailman/listinfo/linaro-android -** Linaro Android IRC channel on irc.freenode.net at @#linaro-android@ - -* Bug reports should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to "Linaro Android project":http://bugs.launchpad.net/linaro-android/+filebug. -* Questions? "ask Linaro":http://ask.linaro.org/. -* Interested in commercial support? inquire at "Linaro support":mailto:support@linaro.org - -h2. Fixed in this release - -* NONE - -h2. Known issues - -* CTS failures are observed for few packages. Detailed CTS report is available to members for reference. diff --git a/android/images/armv8-android-juno-lsk/HOWTO_eula.txt b/android/images/armv8-android-juno-lsk/HOWTO_eula.txt deleted file mode 100644 index d8e300e..0000000 --- a/android/images/armv8-android-juno-lsk/HOWTO_eula.txt +++ /dev/null @@ -1,267 +0,0 @@ -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. - - - -"Juno ARM Development Platform" 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 Juno ARM Development Platform. - - - -"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 a Juno ARM Development Platform 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 - -*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. ARM 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-android-juno-lsk/HOWTO_getsourceandbuild.txt b/android/images/armv8-android-juno-lsk/HOWTO_getsourceandbuild.txt deleted file mode 100644 index 5b2d012..0000000 --- a/android/images/armv8-android-juno-lsk/HOWTO_getsourceandbuild.txt +++ /dev/null @@ -1,294 +0,0 @@ -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-android-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-android-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-android-juno-lsk/pinned-manifest.xml ("?":https://wiki.linaro.org/Platform/Android/ReproduceABuildExactly) -* "Source Manifest":http://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/source-manifest.xml - -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 update -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-7-jdk ant lib32ncurses5-dev xsltproc -sudo update-alternatives --config java -sudo update-alternatives --config javac -sudo update-alternatives --config javadoc - -* Accept the EULA and download the Mali graphics (vendor.tar.bz2) libraries from "here":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/vendor.tar.bz2 -* Download the Android building script for this release from "here":http://releases.linaro.org/14.06/android/images/armv8-android-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 -o $PWD/vendor.tar.bz2 -t - -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/juno -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. - - -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> - - -h2. SCP Firmware - -The SCP Firmware is only available as a pre-built binary. - - - -h2. ARM Trusted Firmware - -The ARM trusted firmware consists of the following images: - -|<b>Filename</b>|<b>Image Type</b>|<b>Image Name</b>| -|bl1.bin|BL1|ARM Trusted ROM image| -|bl2.bin|BL2|ARM Trusted Firmware| -|bl31.bin|BL3-1|EL3 runtime| -|bl32.bin (optional)|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.4-Juno-0.5 - -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 - -To build the optional bl3-2 Test Secure Payload component, use the following commands instead (the 'make realclean' is important): - -bc. $ make realclean -$ make PLAT=juno SPD=tspd all - -By default the preceding commands produce 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@ (if the 'SPD=tspd' flag is used) - -... where @<build-type>@ is either `debug` or `release`. - -To clean the ARM 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 v1.0-rc0 - - - -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/BL33_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/BL33_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 - optional) -* 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. Download the "firmware image artefacts":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=juno-firmware-beta-0.7.5.zip and extract to a working directory (hereafter referred to as @"<path to prebuilt binary>"@). - -4. 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/arm-trusted-firmware/build/juno/release/bl32.bin . -$ cp $JUNO_ROOT_DIR/edk2/Build/ArmJuno/RELEASE_GCC48/FV/BL33_AP_UEFI.fd bl33.bin - -If you wish to use the pre-built ARM trusted firmware and UEFI EDK2 images instead of building them from source, then the last four lines of the above block can independently be replaced with the following: - -bc. $ cp <path to prebuilt binary>/bl2.bin . -$ cp <path to prebuilt binary>/bl31.bin . -$ cp <path to prebuilt binary>/bl32.bin . -$ cp <path to prebuilt binary>/bl33.bin . - - -5. Create the FIP file: - -bc. $ fip_create --dump \ - --bl2 bl2.bin \ - --bl30 bl30.bin \ - --bl31 bl31.bin \ - --bl32 bl32.bin \ (if the optional bl32 image is present) - --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 ---------------------------- -Creating "fip.bin"; - -6. 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 ---------------------------- -Updating "fip.bin" - -For more details and options about the `fip_create` tool: - -bc. $ fip_create --help - - -h2. Installing the binaries - -Please refer to the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/#tabs-2. diff --git a/android/images/armv8-android-juno-lsk/HOWTO_gettingstarted.txt b/android/images/armv8-android-juno-lsk/HOWTO_gettingstarted.txt deleted file mode 100644 index ce97eb5..0000000 --- a/android/images/armv8-android-juno-lsk/HOWTO_gettingstarted.txt +++ /dev/null @@ -1,206 +0,0 @@ -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-android-juno-lsk/#tabs-5. - -h2. Juno ports - - - -h3. Back panel - -<img src="https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/RearPanel.png"> - -h3. Front panel - -<img src="https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/FrontPanel.png"> - -h3(#uarts). UARTs - -There are 4 UARTs on the Juno board: - -| *UART* | *Location* | *Used by* | *Baud* | *Data bits* | *Stop bits* | *Parity | -|SoC UART0 |"back panel":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/RearPanel.png |The motherboard, UEFI and the Linux kernel. |115200 |8 |1 |None | -|SoC UART1 |"back panel":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/RearPanel.png |SCP firmware |115200 |8 |1 |None | -|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 |1 |None | -|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":#setup section. - - - -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 hosted on this website by following the instructions in the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/#tabs-2. - -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":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/#tabs-2 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(#setup). 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":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/RearPanel.png connector ("settings":#uarts). -# Connect the 12 volt power, then press the red "ON/OFF button":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/RearPanel.png on the back panel. - -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":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/#tabs-2. - -h3. Setting the Real Time Clock (required for Android) - -New Juno boards do not have the correct time programmed into the real time clock. Some software (notably Android) will not operate correctly until a sensible time is programmed. To set the time, start a terminal session with "UART0":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/RearPanel.png connector ("settings":#uarts). Ensure there is power to the board, but the SoC must be powered off (if it is not, then press the black "Hardware Reset" button). - -Execute the following: - -bc. ARM V2M-Juno Boot loader v1.0.0 -HBI0262 build 596 -ARM V2M_Juno Firmware v1.1.7 -Build Date: May 27 2014 -Time : 11:52:35 -Date : 09:07:2060 -Cmd> debug -Debug> date -09/07/2060 -Change Date? Y\N >y -D:>23 -M:>6 -Y:>2014 -Debug> time -15 : 51 : 58 -Change Time? Y\N >y -s:>0 -m:>08 -h:>14 -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 Configuration Port 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 table 1 below 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. - To reset to factory settings, the value to program should be 0x00FE001E. - -7. In the [SCC REGISTERS] section, below the "TOTALSCCS" line, insert the following line: - -bc. 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. - -<br><br> - -h4. Table 1. Bit mappings for the CONFIG_TEX_COMPRESSED_FORMAT_ENABLE register. - - *Please ensure you have obtained the appropriate license(s) before enabling these texture compression formats* - -|Bit|Texture compression format| Direct X 9| DirectX 10| DirectX 11| OpenGL ES 1.1| OpenGL ES 2.0| OpenGL ES 3.0| OpenGL 2.0 - 2.1| OpenGL 3.0 - 3.1| OpenGL 3.2 - 4.1| OpenGL 4.2| -|0 | Invalid format | | | | | | | | | | | -|1 | ETC2 | | | | x<sup>[a]</sup> | x<sup>[a]</sup> | x | | | | | -|2 | EAC, 1 component | | | | | | x | | | | | -|3 | ETC2 + EAC | | | | | | x | | | | | -|4 | EAC, 2 components | | | | | | x | | | | | -|5 | Reserved | | | | | | | | | | | -|6 | NXR | | | | | | | | | | | -|7 | BC1_UNORM (DXT1) | x | x | x | x<sup>[b]</sup> | x<sup>[b]</sup> | x<sup>[b]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|8 | BC2_UNORM (DXT3) | x | x | x | | x<sup>[c]</sup> | x<sup>[c]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|9 | BC3_UNORM (DXT5) | x | x | x | | x<sup>[d]</sup> | x<sup>[d]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|10 | BC4_UNORM (RGTC1_UNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|11 | BC4_SNORM (RGTC1_SNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|12 | BC5_UNORM (RGTC2_UNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|13 | BC5_SNORM (RGTC2_SNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|14 | BC6H_UF16 | | | x | | | | | | x<sup>[h]</sup> | x | -|15 | BC6H_SF16 | | | x | | | | | | x<sup>[h]</sup> | x | -|16 | BC7_UNORM | | | x | | | | | | x<sup>[h]</sup> | x | -|17 | EAC_SNORM, 1 component | | | | | | x | | | | | -|18 | EAC_SNORM, 2 components | | | | | | x | | | | | -|19 | ETC2 + punch-through alpha | | | | | | x | | | | | -|20 | ASTC 3D LDR | | | | | | | | | | | -|21 | ASTC 3D HDR | | | | | | | | | | | -|22 | ASTC 2D LDR | | | | x<sup>[e]</sup> | x<sup>[e]</sup> | x<sup>[e]</sup> | | | | | -|23 | ASTC 2D HDR | | | | | | | | | | | -|24 - 31 | Reserved | | | | | | | | | | | - -<p></p> - -Key - [a] Enable for GL_OES_compressed_ETC1_RGB8_texture - [b] Enable for GL_EXT_texture_compression_dxt1 - [c] Enable for GL_ANGLE_texture_compression_dxt3 - [d] Enable for GL_ANGLE_texture_compression_dxt5 - [e] Enable for GL_KHR_texture_compression_astc_ldr - [f] Enable for GL_EXT_texture_compression_s3tc - [g] Enable for GL_EXT_texture_compression_rgtc - [h] Enable for GL_ARB_texture_compression_bptc - - - -h3. Additional documentation - -For further details, please see the following documents. - -* "Juno SoC Reference Manual":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DDI0515A3b_juno_arm_development_platform_soc_trm.pdf -* "V2M Juno Reference Manual":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DDI0524A4b_v2m_juno_reference_manual.pdf -* "SCPI protocol description":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=scpi-doc-v0.2.1.zip diff --git a/android/images/armv8-android-juno-lsk/HOWTO_install.txt b/android/images/armv8-android-juno-lsk/HOWTO_install.txt deleted file mode 100644 index 230bdaa..0000000 --- a/android/images/armv8-android-juno-lsk/HOWTO_install.txt +++ /dev/null @@ -1,374 +0,0 @@ -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-android-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 | -| board_recovery_image_0.7.5.zip | Juno board firmware recovery image | - -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":#firmware installed. Please see "Juno Board Recovery Image and MCC firmware update":#firmware below for the latest updates and installation instructions. The 14.06 release has been formally QA tested with Firmware version 0.7.1 and sanity tested with Firmware version 0.7.5, 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 ("www.ubuntu.com":http://www.ubuntu.com) -* 4GB USB drive or larger -* Latest firmware installed onto the board. Please see "Juno Board Recovery Image and MCC firmware update":#firmware section below -* This release pre-built image, which you can download from the above list of artifacts - -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 - -* Unmount all partitions on the drive -** If you do not unmount all of the USB drive's partitions, you run the risk that the image will not be created successfully. -* Write the image to the drive - -bc. bunzip2 juno.img.bz2 -sudo dd if=juno.img of=$DRIVE - -After you have created the disk image and before you remove the USB drive from your system, you should make sure you wait for all writes to the USB drive to complete. - -The following commands may help with this: - -bc. $ sync -$ sudo eject $DRIVE - -You should also ensure that you have written the image to the USB drive correctly. To do this, after running the eject command, physically remove the USB drive from the system and re-connect the USB drive again. You must unmount all partitions on the USB drive at this point. Note, due to disconnecting and reconnecting the drive, the device path /dev/sdX may have changed. You should check the @dmesg@ output again to ensure that you know the correct path of your USB drive. - -Once you are ready, run the following commands: - -bc. $ sudo cmp /dev/sdX juno.img -$ sync -$ sudo eject /dev/sdX - -When you are confident that the image was created successfully, 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 -* 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'@ - -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 >@ - -*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 - -After you have created the disk image and before you remove the USB drive from your system, you should make sure you wait for all writes to the USB drive to complete. - -The following commands may help with this: - -bc. $ sync -$ sudo eject /dev/sdX - -Where /dev/sdX is the device node for the USB drive as discovered in the instructions above. - - -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":#firmware provide information on how to do this. - -Once you have the latest firmware installed, you will need to configure UEFI to boot the kernel from the "boot" partition of the USB stick. See the steps directly below for instructions on how to configure UEFI. - - -h2. UEFI Configuration - -The example below shows how a test system was configured. Please note: some of the menu option numbers may be different on your board. In particular, the menu option used to choose the boot partition may change number over a reboot. In the example below, the partition named "boot" was option 4. Please be careful that you choose the correct option that corresponds to the menu options you see on your board. - -Also take care that the USB partitions are showing in the menu before selecting a menu option. There is a known bug in UEFI where the partitions on USB drives does not show the first time the menu is displayed. To overcome this, as shown in the example below, the user should enter the menu option @"[1] Add Boot Device Entry"@, by pressing @1@ followed by the enter key. Then, when the list display and the USB partitions are missing, please press the @ESC@ key once. This will exit out of the current menu prompt and leave you back at the Boot Menu again. At this point, please press 1 again to re-enter the menu option @"[1] Add Boot Device Entry"@ and continue by selecting the partition named "boot" on the USB drive. - -UEFI outputs to UART0 on the board. UART0 uses 115200 baud with 8 bits and no stop bit. Please see the "UARTs" section on the "Getting Started tab":https://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/#tabs-4 for more details on the UART configuration of the board. - - -h3. Example UEFI Configuration - -When booting your system, after a short time, you be presented by a boot countdown from 10, thus: - -bc. The default boot selection will start in 10 seconds - -When you see this prompt, please press the enter key to interrupt the countdown. You will then be presented with a menu, thus: - -bc. [1] Linux from NOR Flash -[2] Shell -[3] Boot Manager -Start: - -Depending on the configuration of your board, the menu option called "Boot Manager" may not be option 3. In this example, we can see that the Boot Menu is indeed option "3", so we choose it by pressing the "3" key and pressing enter. You will then be presented with a boot menu, thus: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: - -The first thing we need to do is to delete all of the existing Boot Device Entries. Deleting a Boot Device Entry is achieved by pressing the 3 key and pressing enter: - -bc. [1] Linux from NOR Flash -Delete entry: - -In our example, using the default config from the first time you boot the board, there is only 1 Boot Device Entry: "Linux from NOR Flash". You must delete this entry by pressing the 1 key and pressing enter. After this, you will be returned to the Boot Menu where you should continue by deleting *all* Boot Device Entries that are configured. - -Once you have done this, you should continue by creating a new Boot Device Entry by selecting option 1 from from the Boot Menu. After selecting the menu option by pressing the 1 key folllowed by enter, you will see a list of available Boot Devices, thus: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 1 -[1] Firmware Volume (0 MB) -[2] Firmware Volume (0 MB) -[3] NOR Flash (63 MB) -[4] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[5] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[6] PXE on MAC Address: 00:02:F7:00:57:DD -[7] TFTP on MAC Address: 00:02:F7:00:57:DD -Select the Boot Device: - -As you will see in the example above, there is no partition named "boot" available to the user. At this point, the user must press the @ESC@ key to exit the "Select the Boot Device" option and return to the Boot Menu. From the Boot Menu, please select option 1 again. The example below shows how this looked on our test system, your results may differ: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 1 -[1] Firmware Volume (4068 MB) -[2] Firmware Volume (4068 MB) -[3] NOR Flash (63 MB) -[4] boot (131 MB) -[5] sdcard (13585 MB) -[6] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[7] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[8] PXE on MAC Address: 00:02:F7:00:57:DD -[9] TFTP on MAC Address: 00:02:F7:00:57:DD -Select the Boot Device: - -As you will see, the menu option @"boot"@ has now appeared, allowing us to select the partition named "boot" on the USB drive. In the example above, the partition named "boot" is option 4. Your system may show a different option for the partition named boot on your USB drive. Please examine the menu and choose the appropriate option. - -Once you have choosen the Boot Device, you will be prompted for the configuration of that Boot Device. - -The first quesion will ask for the file path of the kernel, thus: - -bc. File path of the EFI Application or the kernel: - -When configuring a system to boot Android, you enter the file path of the kernel as "kernel" without the quotes and followed by the enter key, for this is the filename of the kernel in the boot partition on the USB drive. - -Next you will be prompted if the kernel has Flattened Device Tree support: - -bc. Has FDT support? [y/n] - -The answer is yes, so please press the "y" key followed by enter. Next you will be asked if you wish to configure an "initrd" for your system: - -bc. Add an initrd: [y/n] - -The answer is yes, so please press the "y" key followed by enter. Next you will be asked for the file path of the initrd on your USB drive: - -bc. File path of the initrd: - -The file is called "ramdisk.img", so please type "ramdisk.img" without the quotes, followed by the enter key. - -After this you will be asked to supply the arguments required to boot the kernel: - -bc. Arguments to pass to the binary: - -Please note, copy and paste does not work well over the serial terminal. The user is advised to type the commandline arguments by hand, character at a time, followed by the enter key. The commandline used is shown below: - -bc. console=ttyAMA0,115200 earlyprintk=pl011,0x7ff80000 root=/dev/ram0 verbose debug - -Finally, after entering the commandline, the final question is simply asking for a title that will appear in the Boot Menu: - -bc. Description for this new Entry: - -You may enter a simple string of alphanumberic characters use to represent the name of this Boot Device. On our example system, we chose to type the string "Linux on USB", without the quotes, followed by pressing the enter key. - -After entering the description string, you will then be returned to the boot menu: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu - -It may take a long time, perhaps over a minute for UEFI to save the Boot Device Entry. - -After you have configured the Boot Device Entry, next you must configure the Flattened Device Tree (FDT) path. You do this by selecting the option "Update FDT path" by pressing the 4 key and pressing enter. As with the Add Boot Device Entry option, next you will be presented with a list of Boot Devices that can host the FDT file. On our test system, the list looked like this: - -bc. [1] Firmware Volume (4068 MB) -[2] Firmware Volume (4068 MB) -[3] NOR Flash (63 MB) -[4] boot (131 MB) -[5] sdcard (13585 MB) -[6] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[7] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[8] PXE on MAC Address: 00:02:F7:00:57:DD -[9] TFTP on MAC Address: 00:02:F7:00:57:DD - -Choose the option that corresponds to the partition named "boot" on your system. In the example above, this is option 4. Enter the option number and press the enter key. You will then be prompted for the file path for the FDT file: - -bc. File path of the FDT blob: - -At this prompt, type the filename "juno.dtb" and press the enter key. The system may take some time to save the configuration. After which, you will be returned to the Boot Menu: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu - -At this point, we have completed our configuration and we can return to the main menu by selecting option 5 "Return to main menu". To select option 5, press the 5 key and press enter. - -Once you are back at the main menu, you will see that the selection of Boot Devices has now changed. On our test system, the selection looked like this: - -bc. [1] Linux on USB -[2] Shell -[3] Boot Manager -Start: - -Where option 1, "Linux on USB" was the Boot Device Entry that we created by following the instructions above. - -You should now choose this option to boot from your USB drive. When booting, you will see output similar to this: - -bc. [1] Linux on USB -[2] Shell -[3] Boot Manager -Start: 1 - PEI 217 ms - DXE 48 ms - BDS 3086 ms -Total Time = 3352 ms -[ 0.000000] Initializing cgroup subsys cpu -[ 0.000000] Linux version 3.10.40-04499-g1866f48 (jenkins-build@ip-10-62-41-78) (gcc version 4.9.1 20140529 (prerelease) (Linaro GCC 4.9-2014.06) ) #1 SMP Tue Jun 17 02:28:46 UTC 2014 -[ 0.000000] CPU: AArch64 Processor [410fd030] revision 0 -[ 0.000000] Machine: Juno - -One important part of the output is the Linux version, shown above as 3.10.40-04499-g1866f48. It is critical that you ensure you are booting Linux version 3.10.40-04499-g1866f48. If you are not, it may be that you have mis-cofigured your system and you should revise your configuration by repeating the steps above. - -note: it is normal for the BDS to show a excessively long time to load the images. This is a known intermittent bug. It did not take such a long time to load. - - -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":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DS-5_config.zip 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(#firmware). Firmware update - -This section describes how to update the firmware on the Juno board. - -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 Juno board recovery image onto the flash memory device, replacing any files already in the flash memory. - -To install firmware images that you have built yourself, the procedure is the same except that you will overwrite the contents of the /SOFTWARE/ directory with your own images. - -To update the MCC firmware only, the procedure is the same except that the MCC firmware update bundle will contain only a subset of the files contained in the full recovery image. - -<br> - -To carry out a system recovery, update the MCC firmware, or install your own custom firmware images, 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 one or more of the firmware components then skip to step 7. Otherwise, for a full system recovery, format the configuration flash memory (FAT16). - -7. Extract the board recovery image ("board_recovery_image_0.7.5.zip":http://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/board_recovery_image_0.7.5.zip) to the root directory of the configuration flash memory, preserving the directory structure. - -8. If you are performing a system recovery or installing an update from ARM then skip to step 9. Otherwise if you wish to install firmware images that you have "built yourself":http://releases.linaro.org/14.06/android/images/armv8-android-juno-lsk/#tabs-3 then delete the bl1.bin and fip.bin from the /SOFTWARE/ directory in the configuration flash memory, and copy your own bl1.bin and fip.bin images into that directory to replace them. - -9. Safely eject the mass storage device, giving it time to write the files to the internal storage. - -10. 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. - -h2. Attaching ADB - -ADB on Juno is supported over ethernet. Follow the instructions on "https://wiki.linaro.org/Platform/Android/SetupAdbOverTcp":https://wiki.linaro.org/Platform/Android/SetupAdbOverTcp to connect adb over the network. diff --git a/android/images/armv8-android-juno-lsk/HOWTO_releasenotes.txt b/android/images/armv8-android-juno-lsk/HOWTO_releasenotes.txt deleted file mode 100644 index 6b835b0..0000000 --- a/android/images/armv8-android-juno-lsk/HOWTO_releasenotes.txt +++ /dev/null @@ -1,149 +0,0 @@ - -h2. About the Linaro Android Release for Juno (Multi-arch 64-bit) - -The Linaro Android release is based on a snapshot of the Android AOSP master taken on the 1st June. The build contains multi-arch support allowing full use of the 64-bit ARMv8-A architecture and supports both 64-bit and 32-bit applications. Java-only applications will run as 64-bit in the supplied configuration with no modification. The release uses Linaro Stable Kernel 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 ARMv8-A reference software stack combined with the Juno ARM Development Platform (ADP) provides the ARM ecosystem with a foundation to accelerate Android availability on 64-bit silicon. The availability of this port is the culmination of a broad architecture enablement program carried out by Linaro, ARM and the ARM partnership. ARM partners will now have access to an AOSP file system with support for both 64-bit and 32-bit apps, together with a broad range of supporting material including the ARMv8-A FVP models, open source toolchain from Linaro and supporting documentation. - -For those with access to Juno, this release can be used to examine the internals of the Android Open Source Project in a running system. Application developers, particularly those working in Java, will also be able to use develop applications via the recently announced Android 'L' preview SDK. - -It should be noted that this is an early software preview and not all 3rd party applications will run correctly at this time. Performance is limited due to the ART runtime running in interpreted mode, more recent versions of the AOSP tree have now enabled this and future monthly builds will feature much better performance, along with wider compatibility as the baseport and AOSP matures. Next month's build in particular will improve as the ART backend compiler is enabled along with some recent optimizations. - -The Android AOSP software provided in this release is functionally tested with CTS version 4.4 and the CTS results are shared with members. The BIONIC component is validated with Android BIONIC tests. Android Monkey tests were run for stress testing. Multi-arch support has been 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-android-juno-lsk/#tabs-3). - -h2. About the Juno ARM Development Platform - -The Juno ARM Development Platform (ADP) is a software development platform for ARMv8-A. It includes: -* The Juno Versatile Express board -* ARMv8-A reference software ports available through Linaro -* Optional LogicTile Express FPGA board to extend the Juno system - this adds a large FPGA to Juno that can be used for driver development or prototyping. - -The Juno hardware delivers to software developers an open, vendor neutral ARMv8-A development platform with: -* Cortex® A57 and A53 MPCore™ for ARMv8-A big.LITTLE -* Mali™-T624 for 3D Graphics Acceleration and GP-GPU compute -* A SoC architecture aligned with Level 1 (Server) Base System Architecture - -The Juno ADP is available from ARM, please visit "www.arm.com/juno":http://www.arm.com/juno in early July for more details. - -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-android-juno-lsk/#tabs-3 tab). - -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-android-juno-lsk/#tabs-5. - -h2. Support - -Please send any ARM support enquiries to "juno-support@arm.com":mailto:juno-support@arm.com?subject=Juno%20support%20request. Engineers at Linaro Members can receive support for Juno by sending support requests to "support@linaro.org":mailto:support@linaro.org?subject=Juno%20support%20request or visiting "http://support.linaro.org":http://support.linaro.org. - -h2. Functionality Listed by Software Component - -h3. AOSP Filesystem - -* Snapshot of the AOSP Master at 1st of June 2014 -* ART Runtime enabled as default and booting in 64-bit primary mode -* GPU support. The driver itself is believed performant but issues with HDLCD driver impact on-screen performance -* HDLCD is fully supported, but is currently only single-buffered leading to visual artefacts - -h3. Linux Kernel - -* Support for the ARM Juno Development Platform -* 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 is provided via on-board SMSC ethernet chip. -* Full USB driver support in Linux, for access to mass storage and input devices. -* big.LITTLE MP support for all 6 cores. -* Unified kernel and kernel config for Android and Linux. -* DVFS stable operating points are enabled for nominal and overdrive - -h3. UEFI - -* Booting an Operating System from NOR Flash or USB mass storage -* Support for Ethernet and PXE boot -* Version: v1.0-rc0 - -h3. ARM Trusted Firmware - -* The ARM Trusted Firmware provides an open source framework enabling easy integration of secure OS and run-time services to ARMv8-A platforms -* Loads the System Control Processor(SCP) firmware into the SCP -* Initializes the Trusted World before transitioning into Normal World. -* Services CPU hotplug requests coming from Normal World -* Provides a standard Power State Coordintion Interface (PSCI) implementation -* Version: v0.4-Juno-0.5-rc1 - -h3. SCP Firmware - -* System configuration -* DDR initialization -* Basic power state management for frequency and C-states -* SCPI commands (Ready, Set/Get Clocks, Set/Get CPU power states) -* Thermal protection (shutdown at 85C, Linux will receive a warning at 75C) -* DVFS support -* Version: 1.0.0-rc3 - -h2. Known Limitations Listed by Software Component - -h3. AOSP Filesystem - -* The ART code at the time of branching from master did not have compilation or optmization enabled. As a result performance will be limited for Java code as it runs in the ART interpreter rather than being compiled at install time -* The Juno baseport integration with AOSP is at an early stage and not all applications using the NDK will work at this time. - * Lack of audio support may cause apps using audio to hang - * Webkit support is not working in 64-bit primary mode, apps using that functionality may not work. -* HDLCD issues include a lack of double buffering meaning tearing can be seen -* HDLCD compatibility with monitors is variable at this time -* OpenCL support is not present at this time and will be enabled in a future release - -h3. Linux Kernel - -* The big.LITTLE support is functional but has not yet been tuned for efficiency and performance. - -h3. UEFI - -* No display controller support -* No USB OHCI support. Only EHCI is supported - -h3. ARM 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. - -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 the ARMv8-A Juno development platform. These patches can be found on Linaro's Android Git repositories. Some of these patches have been submitted to AOSP and are 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 - -The following known issues are present in this release. Please contact "support@linaro.org":mailto:support@linaro.org?subject=Juno%20support%20request if you wish to know more information about these issues or have access problems when attempting to view them. - -| *Bug ID* | *Bug title* | *Bug summary* | -|"ARM-135":https://cards.linaro.org/browse/ARM-135 |Juno: Android fails to boot when board has a date in the future |When the board default date is set beyond 19.01.2038 Android fails to boot. This is most likely a bug in generic Android code. As a workaround, the date on the board needs to be set to something before 2038 cut off date. | -|"Bug 54":https://bugs.linaro.org/show_bug.cgi?id=54 |DNS lookup doesn't work |DNS lookup is broken on 64/64 and Juice builds. Setting additional 'dns' entries with setprop doesn't help. On the other hand networking works well when using IP addresses. | -|"Bug 45":https://bugs.linaro.org/show_bug.cgi?id=45 |CTS errors - Unable to resolve host "loca" : No address associated with hostname |A few CTS tests fails due to resons related to networking. Some of the failures are covered by Bug 54. This bug covers "Unable to resolve host "loca" : No address associated with hostname" | -|"Bug 12":https://bugs.linaro.org/show_bug.cgi?id=12 |Intermittent HDMI failures on 14.06 RC |There is a problem with HDMI sync. The board works with some monitors and doesn't work with other. The monitors known to work are: ASUS VS247 H-P, Samsung S22A300H, HP LP2475w | -|"Bug 51":https://bugs.linaro.org/show_bug.cgi?id=51 |Test test_getaddrinfo from bionic libc test suite fails on Juno build - LAVA |Problem similar to Bug 54. Happens in bionic unit tests | -|"Bug 23":https://bugs.linaro.org/show_bug.cgi?id=23 |backtrace_test reports failures on 64/64 build |There are failures in libbacktrace unit tests. They only happen on 64bit root filesystem | -|"Bug 11":https://bugs.linaro.org/show_bug.cgi?id=11 |Browser crashes on Juno in 14.06 RC |Due to missing webviewchromium browser crashes at startup. | -|"Bug 10":https://bugs.linaro.org/show_bug.cgi?id=10 |settings crashed when running monkey |Settings app crashes when invoking settings related to TTS (android.speech.tts.TextToSpeechService) | -|ARM JSW-749 Linux [Juno-Beta-rc3] | Performance is degraded with idle enabled | With cpuidle enabled android 64 bit fs shows performance degradation | -|ARM JSW-748 Linux [Juno-Beta-rc1] | Periodic black screen flash | Screen blanking is seen at a regular frequency of one in 10 sec | -|ARM JSW-746 | USB Drive failure at maximum OPP | With the overdrive operating point enabled, some USB hard drives don't work (causes kernel panic) | -|ARM JSW-743 | HDMI monitor incompatibilities | HDMI video out fails to display Android home screen on one out of 4 monitor types tried | -|ARM JSW-742 | No HDMI | HDMI video out does not work on both the ports | -|ARM JSW-741 |UEFI - missing boot options | UEFI bootmanager fails to list TFTP and PXE boot options if a live network cable not connected | -|ARM JSW-727 |'Trace' does not work in UEFI | While configuring DS-5 to trace UEFI execution, an error was returned when connecting DS-5 to the debugger | -|ARM JSW-711 |Reset failure | Reset fails if button is pressed during NOR flash write| diff --git a/android/images/armv8-juice-fvp-lsk/HOWTO_getsourceandbuild.txt b/android/images/armv8-juice-fvp-lsk/HOWTO_getsourceandbuild.txt deleted file mode 100644 index 54ef0f0..0000000 --- a/android/images/armv8-juice-fvp-lsk/HOWTO_getsourceandbuild.txt +++ /dev/null @@ -1,182 +0,0 @@ -Instructions for "https://android-build.linaro.org/builds/~linaro-android-restricted/armv8-juice-lsk-14.06-release/":https://android-build.linaro.org/builds/~linaro-android-restricted/armv8-juice-lsk-14.06-release/ - -h2. Prerequisites - -To clone the sources you must be able to ssh to git.linaro.org and be part of the big-little-switcher-private group. Contact "Philip Colmer" <philip.colmer@linaro.org> for access requests. - -h2. How to download and build Android sources - -Recommended method to do a linaro android build is to use linaro android build script(linaro_android_build_cmds.sh). You can download this script from the Downloads section of the build page. Use this script to do a complete ARMv8 Android build for FVP models from scratch. If you prefer to do it manuaaly then follow the "Get the source" and "Build" instructions below. - -h3. Get the source -<pre> - $ sudo add-apt-repository ppa:linaro-maintainers/tools - $ sudo apt-get update - $ sudo apt-get install gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z1-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc openjdk-7-jdk openjdk-7-jre vim-common python-parted python-yaml wget uuid-dev - $ curl "https://android.git.linaro.org/gitweb?p=tools/repo.git;a=blob_plain;f=repo;hb=refs/heads/stable" > repo - $ chmod +x repo - $ ./repo init -u ssh://$USER@linaro-private.git.linaro.org/srv/linaro-private.git.linaro.org/android/manifest.git -b linaro-android-14.06-release -m armv8-juice-lsk.xml - $ sed -i "s/linaro-big-little-switcher-bot/$USER/" .repo/manifest.xml - $ ./repo sync # this may take some time -</pre> - -h3. Build -<pre> - $ export CPUS=`grep -c processor /proc/cpuinfo` - $ export TARGET_PRODUCT=juice - $ export TARGET_BUILD_VARIANT=eng - $ . build/envsetup.sh - $ make -j${CPUS} boottarball systemtarball userdatatarball -</pre> - -h2. Get linaro image tools - -Run these commands to get all the dependencies for linaro-image-tools -<pre> - $ sudo add-apt-repository ppa:linaro-maintainers/tools - $ sudo apt-get update - $ sudo apt-get install linaro-image-tools -</pre> -You can also use the tip of linaro-image-tools from http://git.linaro.org/infrastructure/linaro-image-tools.git - -h2. How to run Juice images on FVP models - -h3. Create mmc image to be used on ARM FVP Base AEMv8 models - -Run linaro image tools - -pre. $ linaro-android-media-create --image_file mmc.img --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2 - -If you're using tip of linaro image tools - -pre. $ ./linaro-image-tools/linaro-android-media-create --image_file mmc.img --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2 - -h3. Extract the preboot files - -pre. tar -jxvf boot.tar.bz2 - -h3. Setup the runtime environment - -<pre> - $ export ARMLMD_LICENSE_FILE="8224@localhost" - $ ssh -L 8224:localhost:8224 -L 18224:localhost:18224 -N $USER@flexlm.linaro.org -</pre> - -h3. Running the models (verified on FVP Base model build 5602) - -<pre> - $ cd boot - $ /path/to/FVP_Base_AEMv8A-AEMv8A/models/Linux64_GCC-4.1/FVP_Base_AEMv8A-AEMv8A \ - -C pctl.startup=0.0.0.0 \ - -C bp.secure_memory=0 \ - -C cluster0.NUM_CORES=1 \ - -C cluster1.NUM_CORES=1 \ - -C cache_state_modelled=0 \ - -C bp.pl011_uart0.untimed_fifos=1 \ - -C bp.secureflashloader.fname=fvp_bl1.bin \ - -C bp.flashloader0.fname=fvp_fip.bin \ - -C bp.virtioblockdevice.image_path=../mmc.img -</pre> - -h3. Console redirection - -To redirect the console open a terminal and run - -pre. telnet 127.0.0.1 5000 - -h3. Set UEFI configuration, update kernel/ramdisk path and bootargs - -Stop the UEFI boot process and configure it for FVP models: - -<pre> -$ telnet 127.0.0.1 -debug 5000 -e ^z -Telnet escape character is 'b'. -Telnet escape character is '^Z'. -Trying 127.0.0.1... -setsockopt (SO_DEBUG): Permission denied -Connected to 127.0.0.1. -Escape character is '^Z'. - 7 seconds -[1] Linaro disk image on virtio -[2] Shell -[3] Boot Manager -Start: 3 -[1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 2 -[1] Linaro disk image on virtio -Update entry: 1 -File path of the EFI Application or the kernel: kernel -Has FDT support? [y/n] y -Add an initrd: [y/n] y -File path of the initrd: ramdisk.img -Arguments to pass to the binary: console=ttyAMA0 earlyprintk=pl011,0x1c090000 amba-clcd.mode=VGA -Description for this new Entry: Linaro disk image on virtio -[1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 5 -[1] Linaro disk image on virtio -[2] Shell -[3] Boot Manager -Start: 1 - PEI 1122 ms - DXE 259 ms - BDS 8 ms -Total Time = 1390 ms - -[ 0.000000] Initializing cgroup subsys cpu -[ 0.000000] Linux version 3.10.40-04438-g6a78140 (pundiramit@flying-dutchman) (gcc version 4.9 20140514 (prerelease) (GCC) ) #1 SMP Mon Jun 2 14:50:25 IST 2014 -</pre> - -h3. Black screen - -The boot screen has been disabled to speed up booting. This means you may not see anything on the CLCD terminal for a while depending on the performance of the machine the model is running on. For example a first boot on a 2 GHz machine with 32 GB of RAM took 20 minutes. Subsequent boots should take approximately half the time to boot. - -h3. Attach ADB - -ADB on FVP Base models are supported over network. Follow the instructions here https://wiki.linaro.org/Internal/Projects/Juice/SetupNetworkingOnModelsUsingBridges to setup networking and use adb. - -h2. How to run Juice images on Juno - -h3. Plug in the USB stick and flash Juice images on that USB device - -Run 'dmesg' and find out correct USB /dev node. - -pre. $ dmesg - -Look for a line that looks like the following at the end of the log - -pre. [288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 > - -WARNING: In the next step, make sure you use /dev/"whatever you see above". - You can erase your hard drive with the wrong parameter. - -Run linaro image tools - -pre. $ linaro-android-media-create --mmc /dev/sdX --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - -If you're using tip of linaro image tools - -pre. $ ./linaro-image-tools/linaro-android-media-create --mmc /dev/sdX --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - -Now unplug the USB stick and connect it to Juno and boot from it. - -h3. Configure Juno boot time UEFI configuration - -Copy Preboot firmwares (bl1.bin and fip.bin) from boot.tar.bz2 to <firmware_partition>/SOFTWARE/. Stop at UEFI prompt and change few parameters shown below - -<pre> -Select USB device's boot partition to boot from while "Selecting the boot device". -Change kernel in UEFI to "kernel" in the boot partition -Change ramdisk in UEFI to "ramdisk.img" in the boot partition -Change bootargs to "console=ttyAMA0,115200 earlyprintk=pl011,0x7ff80000" -</pre> -Note: There is a bug in UEFI where you won't see USB disk partitions while selecting the boot device. You have to press ESCAPE at "Select the boot device" menu item and then continue. - -It should get your Juno board up and running. diff --git a/android/images/armv8-juice-fvp-lsk/HOWTO_install.txt b/android/images/armv8-juice-fvp-lsk/HOWTO_install.txt deleted file mode 100644 index d964838..0000000 --- a/android/images/armv8-juice-fvp-lsk/HOWTO_install.txt +++ /dev/null @@ -1,135 +0,0 @@ -Instructions for "https://android-build.linaro.org/builds/~linaro-android-restricted/armv8-juice-lsk/":https://android-build.linaro.org/builds/~linaro-android-restricted/armv8-juice-lsk/ - -h2. Prerequisites - -h3. Get artifacts - -To get the build artifacts you must be part of the linaro-android-restricted launchpad group. Contact "Philip Colmer" <philip.colmer@linaro.org> for access requests. - -h3. Run the build - -You'll need the latest ARM FVP Base models and a license to use the models. Follow the instructions at https://collaborate.linaro.org/display/ITS/FlexLM+and+Fast+Models for the same. - -h2. Get artifacts - -Scroll down and click on 'Downloads' - -Click on each link to download: -* boot.tar.bz2 -* system.tar.bz2 -* userdata.tar.bz2 - -h2. Get linaro image tools - -Run these commands to get all the dependencies for linaro-image-tools and the tip of linaro-image-tools - -<pre> - $ sudo add-apt-repository ppa:linaro-maintainers/tools - $ sudo apt-get update - $ sudo apt-get install linaro-image-tools -</pre> - -You can also use the tip of linaro-image-tools from http://git.linaro.org/infrastructure/linaro-image-tools.git - -h2. How to run Juice images on FVP models - -h3. Create mmc image to be used on ARM FVP Base AEMv8 models - -Run linaro image tools - -pre. $ linaro-android-media-create --image_file mmc.img --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2 - -If you're using tip of linaro image tools - -pre. $ ./linaro-image-tools/linaro-android-media-create --image_file mmc.img --image_size 2000M --dev vexpress --system system.tar.bz2 --userdata userdata.tar.bz2 --boot boot.tar.bz2 - -h3. Extract the preboot files - -pre. tar -jxvf boot.tar.bz2 - -h3. Setup the runtime environment - -<pre> - $ export ARMLMD_LICENSE_FILE="8224@localhost" - $ ssh -L 8224:localhost:8224 -L 18224:localhost:18224 -N $USER@flexlm.linaro.org -</pre> - -h3. Running the models (verified on FVP Base model build 5602) - -<pre> - $ cd boot - $ /path/to/FVP_Base_AEMv8A-AEMv8A/models/Linux64_GCC-4.1/FVP_Base_AEMv8A-AEMv8A \ - -C pctl.startup=0.0.0.0 \ - -C bp.secure_memory=0 \ - -C cluster0.NUM_CORES=1 \ - -C cluster1.NUM_CORES=1 \ - -C cache_state_modelled=0 \ - -C bp.pl011_uart0.untimed_fifos=1 \ - -C bp.secureflashloader.fname=fvp_bl1.bin \ - -C bp.flashloader0.fname=fvp_fip.bin \ - -C bp.virtioblockdevice.image_path=mmc.img -</pre> - -h3. Console redirection - -To redirect the console open a terminal and run - -pre. telnet 127.0.0.1 5000 - -h3. Set UEFI configuration, update kernel/ramdisk path and bootargs - -Stop the UEFI boot process and configure it for FVP models: - -<pre> -$ telnet 127.0.0.1 -debug 5000 -e ^z -Telnet escape character is 'b'. -Telnet escape character is '^Z'. -Trying 127.0.0.1... -setsockopt (SO_DEBUG): Permission denied -Connected to 127.0.0.1. -Escape character is '^Z'. - 7 seconds -[1] Linaro disk image on virtio -[2] Shell -[3] Boot Manager -Start: 3 -[1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 2 -[1] Linaro disk image on virtio -Update entry: 1 -File path of the EFI Application or the kernel: kernel -Has FDT support? [y/n] y -Add an initrd: [y/n] y -File path of the initrd: ramdisk.img -Arguments to pass to the binary: console=ttyAMA0 earlyprintk=pl011,0x1c090000 amba-clcd.mode=VGA -Description for this new Entry: Linaro disk image on virtio -[1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 5 -[1] Linaro disk image on virtio -[2] Shell -[3] Boot Manager -Start: 1 - PEI 1122 ms - DXE 259 ms - BDS 8 ms -Total Time = 1390 ms - -[ 0.000000] Initializing cgroup subsys cpu -[ 0.000000] Linux version 3.10.40-04438-g6a78140 (pundiramit@flying-dutchman) (gcc version 4.9 20140514 (prerelease) (GCC) ) #1 SMP Mon Jun 2 14:50:25 IST 2014 -</pre> - -h3. Black screen - -The boot screen has been disabled to speed up booting. This means you may not see anything on the CLCD terminal for a while depending on the performance of the machine the model is running on. For example a first boot on a 2 GHz machine with 32 GB of RAM took 20 minutes. Subsequent boots should take approximately half the time to boot. - -h3. Attaching ADB - -ADB on FVP Base models is supported over the network. Follow the instructions here https://wiki.linaro.org/Internal/Projects/Juice/SetupNetworkingOnModelsUsingBridges to setup networking and use adb. diff --git a/android/images/armv8-juice-fvp-lsk/HOWTO_prebuilt.txt b/android/images/armv8-juice-fvp-lsk/HOWTO_prebuilt.txt deleted file mode 100644 index f699a3e..0000000 --- a/android/images/armv8-juice-fvp-lsk/HOWTO_prebuilt.txt +++ /dev/null @@ -1,69 +0,0 @@ -Instructions for https://android-build.linaro.org/builds/~linaro-android/<BUILD_NAME>/ - -= Get artifacts = - - Scroll down to the 'Downloads' section - - Click on each link to download: - boot.tar.bz2 - system.tar.bz2 - userdata.tar.bz2 - -= Get linaro image tools = - - Run these commands to get all the dependencies for linaro-image-tools and the tip of linaro-image-tools - - $ sudo add-apt-repository ppa:linaro-maintainers/tools - $ sudo apt-get update - $ sudo apt-get install linaro-image-tools - - If you're using a released build (with a -release or from releases.linaro.org), skip this step. - If you're using a "tip" build do not skip the step and do the following: - - $ sudo apt-get install bzr - $ bzr branch lp:linaro-image-tools - -= Create media (SD card) = - - Disable automount (instructions provided for Gnome) - - $ TMP1=$(dconf read /org/gnome/desktop/media-handling/automount) - $ TMP2=$(dconf read /org/gnome/desktop/media-handling/automount-open) - $ dconf write /org/gnome/desktop/media-handling/automount false - $ dconf write /org/gnome/desktop/media-handling/automount-open false - - Insert an SD card - - Run 'dmesg' - - $ dmesg - - Look for a line that looks like the following at the end of the log - - [288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 > - - WARNING: In the next step, make sure you use /dev/"whatever you see above". - You can erase your hard drive with the wrong parameter. - - Run linaro image tools - - $ linaro-android-media-create --mmc /dev/sdc --dev <BOARD> --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - - If you're using tip of linaro image tools - - $ ./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc --dev <BOARD> --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - - To find <BOARD> run linaro-android-media-create with a -h and read the help. - - Restore automount - - $ dconf write /org/gnome/desktop/media-handling/automount $TMP1 - $ dconf write /org/gnome/desktop/media-handling/automount-open $TMP2 - - Remove the SD card from the device writer and plug it into the board. - -= Check console output = - - Plug in an USB-to-serial converter and run minicom - - $ minicom -D /dev/ttyUSB0 -w -C minicom.txt diff --git a/android/images/armv8-juice-fvp-lsk/HOWTO_releasenotes_armv8-juice-fvp-lsk.txt b/android/images/armv8-juice-fvp-lsk/HOWTO_releasenotes_armv8-juice-fvp-lsk.txt deleted file mode 100644 index 2000338..0000000 --- a/android/images/armv8-juice-fvp-lsk/HOWTO_releasenotes_armv8-juice-fvp-lsk.txt +++ /dev/null @@ -1,49 +0,0 @@ -p. Linaro releases monthly binary Android images and associated sources for the AArch64 models. - -p. This is the Linaro Android release for ARMv8 FVP Base Models. The objective of this release is to build and boot Android as 32 bit rootfs and continue building and running Linux as 64bit. The release is based on Android AOSP June 1st 2014 snapshot, Linux Stable Kernel 3.10 (LSK) from Linaro and boots on the new FVP Base AEMv8 model 0.8 build 5202 using UEFI EDK II as boot loader. The sources are also made available so you can build your own images. The Android sources are compiled for 32bit rootfs with Linaro GCC 4.9 toolchain. - -p. The lastest available CTS package version 4.4 is compiled for 32bit Android user space and have tried running maximum number of tests possible. Few tests fail due to model limitation. Detailed CTS results is made available to members seperately through the juice mailing list. - -h2. About the ARMv8 Android Release - -p. This release is port of Android to the AArch64 architecture for Fast Models, there is a similar release for Juno (ARM's ARMv8 Hardware platform). - -p. The main purpose of this release is to provide our members a pre-integrated and validated Android software distribution based on LSK, Android AOSP master (32bit user space) and built with latest GCC 4.9 for Fast Models to go to production faster with existing set of applications and limited certification hurdles. - -p. Android AOSP Patches - 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 Fast Models. These patches can be found on Linaro's Android Git repositories. NOTE: Few of these patches are not applicable to run Android in 32bit user space, they are specific to Juno hardware and 64bit user space. - -* "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. Where To Find More Information - -More information on Linaro can be found on our "website.":http://www.linaro.org/ - -h2. Feedback and Support - -Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. - -** Linaro Android Development "mailing list":http://lists.linaro.org/mailman/listinfo/linaro-android -** Linaro Android IRC channel on irc.freenode.net at @#linaro-android@ - -* Bug reports should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to "Linaro Android project":http://bugs.launchpad.net/linaro-android/+filebug. -* Questions? "ask Linaro":http://ask.linaro.org/. -* Interested in commercial support? inquire at "Linaro support":mailto:support@linaro.org - -h2. Fixed in this release - -* NONE - -h2. Known issues - -* CTS failures are observed for few packages. Detailed CTS report is available to members for reference. diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_eula.txt b/android/images/armv8-juice-juno-lsk/HOWTO_eula.txt deleted file mode 100644 index d8e300e..0000000 --- a/android/images/armv8-juice-juno-lsk/HOWTO_eula.txt +++ /dev/null @@ -1,267 +0,0 @@ -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. - - - -"Juno ARM Development Platform" 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 Juno ARM Development Platform. - - - -"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 a Juno ARM Development Platform 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 - -*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. ARM 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 deleted file mode 100644 index f4158f8..0000000 --- a/android/images/armv8-juice-juno-lsk/HOWTO_getsourceandbuild.txt +++ /dev/null @@ -1,293 +0,0 @@ -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. 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 update -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-7-jdk ant lib32ncurses5-dev xsltproc -sudo update-alternatives --config java -sudo update-alternatives --config javac -sudo update-alternatives --config javadoc - -* 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 -t - -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/juice -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. - - -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> - - -h2. SCP Firmware - -The SCP Firmware is only available as a pre-built binary. - - - -h2. ARM Trusted Firmware - -The ARM trusted firmware consists of the following images: - -|<b>Filename</b>|<b>Image Type</b>|<b>Image Name</b>| -|bl1.bin|BL1|ARM Trusted ROM image| -|bl2.bin|BL2|ARM Trusted Firmware| -|bl31.bin|BL3-1|EL3 runtime| -|bl32.bin (optional)|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.4-Juno-0.5 - -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 - -To build the optional bl3-2 Test Secure Payload component, use the following commands instead (the 'make realclean' is important): - -bc. $ make realclean -$ make PLAT=juno SPD=tspd all - -By default the preceding commands produce 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@ (if the 'SPD=tspd' flag is used) - -... where @<build-type>@ is either `debug` or `release`. - -To clean the ARM 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 v1.0-rc0 - - - -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/BL33_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/BL33_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 - optional) -* 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. Download the "firmware image artefacts":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=juno-firmware-beta-0.7.5.zip and extract to a working directory (hereafter referred to as @"<path to prebuilt binary>"@). - -4. 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/arm-trusted-firmware/build/juno/release/bl32.bin . -$ cp $JUNO_ROOT_DIR/edk2/Build/ArmJuno/RELEASE_GCC48/FV/BL33_AP_UEFI.fd bl33.bin - -If you wish to use the pre-built ARM trusted firmware and UEFI EDK2 images instead of building them from source, then the last four lines of the above block can independently be replaced with the following: - -bc. $ cp <path to prebuilt binary>/bl2.bin . -$ cp <path to prebuilt binary>/bl31.bin . -$ cp <path to prebuilt binary>/bl32.bin . -$ cp <path to prebuilt binary>/bl33.bin . - - -5. Create the FIP file: - -bc. $ fip_create --dump \ - --bl2 bl2.bin \ - --bl30 bl30.bin \ - --bl31 bl31.bin \ - --bl32 bl32.bin \ (if the optional bl32 image is present) - --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 ---------------------------- -Creating "fip.bin"; - -6. 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 ---------------------------- -Updating "fip.bin" - -For more details and options about the `fip_create` tool: - -bc. $ fip_create --help - - -h2. Installing the binaries - -Please refer to the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-2. diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt b/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt deleted file mode 100644 index dd9e790..0000000 --- a/android/images/armv8-juice-juno-lsk/HOWTO_gettingstarted.txt +++ /dev/null @@ -1,206 +0,0 @@ -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 - -<img src="https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/RearPanel.png"> - -h3. Front panel - -<img src="https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/FrontPanel.png"> - -h3(#uarts). UARTs - -There are 4 UARTs on the Juno board: - -| *UART* | *Location* | *Used by* | *Baud* | *Data bits* | *Stop bits* | *Parity | -|SoC UART0 |"back panel":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/RearPanel.png |The motherboard, UEFI and the Linux kernel. |115200 |8 |1 |None | -|SoC UART1 |"back panel":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/RearPanel.png |SCP firmware |115200 |8 |1 |None | -|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 |1 |None | -|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":#setup section. - - - -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 hosted on this website by following the instructions in the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-2. - -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":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-2 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(#setup). 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":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/RearPanel.png connector ("settings":#uarts). -# Connect the 12 volt power, then press the red "ON/OFF button":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/RearPanel.png on the back panel. - -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":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-2. - -h3. Setting the Real Time Clock (required for Android) - -New Juno boards do not have the correct time programmed into the real time clock. Some software (notably Android) will not operate correctly until a sensible time is programmed. To set the time, start a terminal session with "UART0":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/RearPanel.png connector ("settings":#uarts). Ensure there is power to the board, but the SoC must be powered off (if it is not, then press the black "Hardware Reset" button). - -Execute the following: - -bc. ARM V2M-Juno Boot loader v1.0.0 -HBI0262 build 596 -ARM V2M_Juno Firmware v1.1.7 -Build Date: May 27 2014 -Time : 11:52:35 -Date : 09:07:2060 -Cmd> debug -Debug> date -09/07/2060 -Change Date? Y\N >y -D:>23 -M:>6 -Y:>2014 -Debug> time -15 : 51 : 58 -Change Time? Y\N >y -s:>0 -m:>08 -h:>14 -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 Configuration Port 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 table 1 below 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. - To reset to factory settings, the value to program should be 0x00FE001E. - -7. In the [SCC REGISTERS] section, below the "TOTALSCCS" line, insert the following line: - -bc. 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. - -<br><br> - -h4. Table 1. Bit mappings for the CONFIG_TEX_COMPRESSED_FORMAT_ENABLE register. - - *Please ensure you have obtained the appropriate license(s) before enabling these texture compression formats* - -|Bit|Texture compression format| Direct X 9| DirectX 10| DirectX 11| OpenGL ES 1.1| OpenGL ES 2.0| OpenGL ES 3.0| OpenGL 2.0 - 2.1| OpenGL 3.0 - 3.1| OpenGL 3.2 - 4.1| OpenGL 4.2| -|0 | Invalid format | | | | | | | | | | | -|1 | ETC2 | | | | x<sup>[a]</sup> | x<sup>[a]</sup> | x | | | | | -|2 | EAC, 1 component | | | | | | x | | | | | -|3 | ETC2 + EAC | | | | | | x | | | | | -|4 | EAC, 2 components | | | | | | x | | | | | -|5 | Reserved | | | | | | | | | | | -|6 | NXR | | | | | | | | | | | -|7 | BC1_UNORM (DXT1) | x | x | x | x<sup>[b]</sup> | x<sup>[b]</sup> | x<sup>[b]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|8 | BC2_UNORM (DXT3) | x | x | x | | x<sup>[c]</sup> | x<sup>[c]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|9 | BC3_UNORM (DXT5) | x | x | x | | x<sup>[d]</sup> | x<sup>[d]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|10 | BC4_UNORM (RGTC1_UNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|11 | BC4_SNORM (RGTC1_SNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|12 | BC5_UNORM (RGTC2_UNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|13 | BC5_SNORM (RGTC2_SNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|14 | BC6H_UF16 | | | x | | | | | | x<sup>[h]</sup> | x | -|15 | BC6H_SF16 | | | x | | | | | | x<sup>[h]</sup> | x | -|16 | BC7_UNORM | | | x | | | | | | x<sup>[h]</sup> | x | -|17 | EAC_SNORM, 1 component | | | | | | x | | | | | -|18 | EAC_SNORM, 2 components | | | | | | x | | | | | -|19 | ETC2 + punch-through alpha | | | | | | x | | | | | -|20 | ASTC 3D LDR | | | | | | | | | | | -|21 | ASTC 3D HDR | | | | | | | | | | | -|22 | ASTC 2D LDR | | | | x<sup>[e]</sup> | x<sup>[e]</sup> | x<sup>[e]</sup> | | | | | -|23 | ASTC 2D HDR | | | | | | | | | | | -|24 - 31 | Reserved | | | | | | | | | | | - -<p></p> - -Key - [a] Enable for GL_OES_compressed_ETC1_RGB8_texture - [b] Enable for GL_EXT_texture_compression_dxt1 - [c] Enable for GL_ANGLE_texture_compression_dxt3 - [d] Enable for GL_ANGLE_texture_compression_dxt5 - [e] Enable for GL_KHR_texture_compression_astc_ldr - [f] Enable for GL_EXT_texture_compression_s3tc - [g] Enable for GL_EXT_texture_compression_rgtc - [h] Enable for GL_ARB_texture_compression_bptc - - - -h3. Additional documentation - -For further details, please see the following documents. - -* "Juno SoC Reference Manual":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DDI0515A3b_juno_arm_development_platform_soc_trm.pdf -* "V2M Juno Reference Manual":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DDI0524A4b_v2m_juno_reference_manual.pdf -* "SCPI protocol description":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=scpi-doc-v0.2.1.zip diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_install.txt b/android/images/armv8-juice-juno-lsk/HOWTO_install.txt deleted file mode 100644 index 28c82ef..0000000 --- a/android/images/armv8-juice-juno-lsk/HOWTO_install.txt +++ /dev/null @@ -1,374 +0,0 @@ -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 | -| board_recovery_image_0.7.5.zip | Juno board firmware recovery image | - -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":#firmware installed. Please see "Juno Board Recovery Image and MCC firmware update":#firmware below for the latest updates and installation instructions. The 14.06 release has been formally QA tested with Firmware version 0.7.1 and sanity tested with Firmware version 0.7.5, 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 ("www.ubuntu.com":http://www.ubuntu.com) -* 4GB USB drive or larger -* Latest firmware installed onto the board. Please see "Juno Board Recovery Image and MCC firmware update":#firmware section below -* This release pre-built image, which you can download from the above list of artifacts - -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 - -* Unmount all partitions on the drive -** If you do not unmount all of the USB drive's partitions, you run the risk that the image will not be created successfully. -* Write the image to the drive - -bc. bunzip2 juno.img.bz2 -sudo dd if=juno.img of=$DRIVE - -After you have created the disk image and before you remove the USB drive from your system, you should make sure you wait for all writes to the USB drive to complete. - -The following commands may help with this: - -bc. $ sync -$ sudo eject $DRIVE - -You should also ensure that you have written the image to the USB drive correctly. To do this, after running the eject command, physically remove the USB drive from the system and re-connect the USB drive again. You must unmount all partitions on the USB drive at this point. Note, due to disconnecting and reconnecting the drive, the device path /dev/sdX may have changed. You should check the @dmesg@ output again to ensure that you know the correct path of your USB drive. - -Once you are ready, run the following commands: - -bc. $ sudo cmp /dev/sdX juno.img -$ sync -$ sudo eject /dev/sdX - -When you are confident that the image was created successfully, 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 -* 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'@ - -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 >@ - -*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 - -After you have created the disk image and before you remove the USB drive from your system, you should make sure you wait for all writes to the USB drive to complete. - -The following commands may help with this: - -bc. $ sync -$ sudo eject /dev/sdX - -Where /dev/sdX is the device node for the USB drive as discovered in the instructions above. - - -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":#firmware provide information on how to do this. - -Once you have the latest firmware installed, you will need to configure UEFI to boot the kernel from the "boot" partition of the USB stick. See the steps directly below for instructions on how to configure UEFI. - - -h2. UEFI Configuration - -The example below shows how a test system was configured. Please note: some of the menu option numbers may be different on your board. In particular, the menu option used to choose the boot partition may change number over a reboot. In the example below, the partition named "boot" was option 4. Please be careful that you choose the correct option that corresponds to the menu options you see on your board. - -Also take care that the USB partitions are showing in the menu before selecting a menu option. There is a known bug in UEFI where the partitions on USB drives does not show the first time the menu is displayed. To overcome this, as shown in the example below, the user should enter the menu option @"[1] Add Boot Device Entry"@, by pressing @1@ followed by the enter key. Then, when the list display and the USB partitions are missing, please press the @ESC@ key once. This will exit out of the current menu prompt and leave you back at the Boot Menu again. At this point, please press 1 again to re-enter the menu option @"[1] Add Boot Device Entry"@ and continue by selecting the partition named "boot" on the USB drive. - -UEFI outputs to UART0 on the board. UART0 uses 115200 baud with 8 bits and no stop bit. Please see the "UARTs" section on the "Getting Started tab":https://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-4 for more details on the UART configuration of the board. - - -h3. Example UEFI Configuration - -When booting your system, after a short time, you be presented by a boot countdown from 10, thus: - -bc. The default boot selection will start in 10 seconds - -When you see this prompt, please press the enter key to interrupt the countdown. You will then be presented with a menu, thus: - -bc. [1] Linux from NOR Flash -[2] Shell -[3] Boot Manager -Start: - -Depending on the configuration of your board, the menu option called "Boot Manager" may not be option 3. In this example, we can see that the Boot Menu is indeed option "3", so we choose it by pressing the "3" key and pressing enter. You will then be presented with a boot menu, thus: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: - -The first thing we need to do is to delete all of the existing Boot Device Entries. Deleting a Boot Device Entry is achieved by pressing the 3 key and pressing enter: - -bc. [1] Linux from NOR Flash -Delete entry: - -In our example, using the default config from the first time you boot the board, there is only 1 Boot Device Entry: "Linux from NOR Flash". You must delete this entry by pressing the 1 key and pressing enter. After this, you will be returned to the Boot Menu where you should continue by deleting *all* Boot Device Entries that are configured. - -Once you have done this, you should continue by creating a new Boot Device Entry by selecting option 1 from from the Boot Menu. After selecting the menu option by pressing the 1 key folllowed by enter, you will see a list of available Boot Devices, thus: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 1 -[1] Firmware Volume (0 MB) -[2] Firmware Volume (0 MB) -[3] NOR Flash (63 MB) -[4] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[5] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[6] PXE on MAC Address: 00:02:F7:00:57:DD -[7] TFTP on MAC Address: 00:02:F7:00:57:DD -Select the Boot Device: - -As you will see in the example above, there is no partition named "boot" available to the user. At this point, the user must press the @ESC@ key to exit the "Select the Boot Device" option and return to the Boot Menu. From the Boot Menu, please select option 1 again. The example below shows how this looked on our test system, your results may differ: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 1 -[1] Firmware Volume (4068 MB) -[2] Firmware Volume (4068 MB) -[3] NOR Flash (63 MB) -[4] boot (131 MB) -[5] sdcard (13585 MB) -[6] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[7] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[8] PXE on MAC Address: 00:02:F7:00:57:DD -[9] TFTP on MAC Address: 00:02:F7:00:57:DD -Select the Boot Device: - -As you will see, the menu option @"boot"@ has now appeared, allowing us to select the partition named "boot" on the USB drive. In the example above, the partition named "boot" is option 4. Your system may show a different option for the partition named boot on your USB drive. Please examine the menu and choose the appropriate option. - -Once you have choosen the Boot Device, you will be prompted for the configuration of that Boot Device. - -The first quesion will ask for the file path of the kernel, thus: - -bc. File path of the EFI Application or the kernel: - -When configuring a system to boot Android, you enter the file path of the kernel as "kernel" without the quotes and followed by the enter key, for this is the filename of the kernel in the boot partition on the USB drive. - -Next you will be prompted if the kernel has Flattened Device Tree support: - -bc. Has FDT support? [y/n] - -The answer is yes, so please press the "y" key followed by enter. Next you will be asked if you wish to configure an "initrd" for your system: - -bc. Add an initrd: [y/n] - -The answer is yes, so please press the "y" key followed by enter. Next you will be asked for the file path of the initrd on your USB drive: - -bc. File path of the initrd: - -The file is called "ramdisk.img", so please type "ramdisk.img" without the quotes, followed by the enter key. - -After this you will be asked to supply the arguments required to boot the kernel: - -bc. Arguments to pass to the binary: - -Please note, copy and paste does not work well over the serial terminal. The user is advised to type the commandline arguments by hand, character at a time, followed by the enter key. The commandline used is shown below: - -bc. console=ttyAMA0,115200 earlyprintk=pl011,0x7ff80000 root=/dev/ram0 verbose debug - -Finally, after entering the commandline, the final question is simply asking for a title that will appear in the Boot Menu: - -bc. Description for this new Entry: - -You may enter a simple string of alphanumberic characters use to represent the name of this Boot Device. On our example system, we chose to type the string "Linux on USB", without the quotes, followed by pressing the enter key. - -After entering the description string, you will then be returned to the boot menu: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu - -It may take a long time, perhaps over a minute for UEFI to save the Boot Device Entry. - -After you have configured the Boot Device Entry, next you must configure the Flattened Device Tree (FDT) path. You do this by selecting the option "Update FDT path" by pressing the 4 key and pressing enter. As with the Add Boot Device Entry option, next you will be presented with a list of Boot Devices that can host the FDT file. On our test system, the list looked like this: - -bc. [1] Firmware Volume (4068 MB) -[2] Firmware Volume (4068 MB) -[3] NOR Flash (63 MB) -[4] boot (131 MB) -[5] sdcard (13585 MB) -[6] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[7] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[8] PXE on MAC Address: 00:02:F7:00:57:DD -[9] TFTP on MAC Address: 00:02:F7:00:57:DD - -Choose the option that corresponds to the partition named "boot" on your system. In the example above, this is option 4. Enter the option number and press the enter key. You will then be prompted for the file path for the FDT file: - -bc. File path of the FDT blob: - -At this prompt, type the filename "juno.dtb" and press the enter key. The system may take some time to save the configuration. After which, you will be returned to the Boot Menu: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu - -At this point, we have completed our configuration and we can return to the main menu by selecting option 5 "Return to main menu". To select option 5, press the 5 key and press enter. - -Once you are back at the main menu, you will see that the selection of Boot Devices has now changed. On our test system, the selection looked like this: - -bc. [1] Linux on USB -[2] Shell -[3] Boot Manager -Start: - -Where option 1, "Linux on USB" was the Boot Device Entry that we created by following the instructions above. - -You should now choose this option to boot from your USB drive. When booting, you will see output similar to this: - -bc. [1] Linux on USB -[2] Shell -[3] Boot Manager -Start: 1 - PEI 217 ms - DXE 48 ms - BDS 3086 ms -Total Time = 3352 ms -[ 0.000000] Initializing cgroup subsys cpu -[ 0.000000] Linux version 3.10.40-04499-g1866f48 (jenkins-build@ip-10-62-41-78) (gcc version 4.9.1 20140529 (prerelease) (Linaro GCC 4.9-2014.06) ) #1 SMP Tue Jun 17 02:28:46 UTC 2014 -[ 0.000000] CPU: AArch64 Processor [410fd030] revision 0 -[ 0.000000] Machine: Juno - -One important part of the output is the Linux version, shown above as 3.10.40-04499-g1866f48. It is critical that you ensure you are booting Linux version 3.10.40-04499-g1866f48. If you are not, it may be that you have mis-cofigured your system and you should revise your configuration by repeating the steps above. - -note: it is normal for the BDS to show a excessively long time to load the images. This is a known intermittent bug. It did not take such a long time to load. - - -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":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DS-5_config.zip 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(#firmware). Firmware update - -This section describes how to update the firmware on the Juno board. - -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 Juno board recovery image onto the flash memory device, replacing any files already in the flash memory. - -To install firmware images that you have built yourself, the procedure is the same except that you will overwrite the contents of the /SOFTWARE/ directory with your own images. - -To update the MCC firmware only, the procedure is the same except that the MCC firmware update bundle will contain only a subset of the files contained in the full recovery image. - -<br> - -To carry out a system recovery, update the MCC firmware, or install your own custom firmware images, 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 one or more of the firmware components then skip to step 7. Otherwise, for a full system recovery, format the configuration flash memory (FAT16). - -7. Extract the board recovery image ("board_recovery_image_0.7.5.zip":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/board_recovery_image_0.7.5.zip) to the root directory of the configuration flash memory, preserving the directory structure. - -8. If you are performing a system recovery or installing an update from ARM then skip to step 9. Otherwise if you wish to install firmware images that you have "built yourself":http://releases.linaro.org/14.06/android/images/armv8-juice-juno-lsk/#tabs-3 then delete the bl1.bin and fip.bin from the /SOFTWARE/ directory in the configuration flash memory, and copy your own bl1.bin and fip.bin images into that directory to replace them. - -9. Safely eject the mass storage device, giving it time to write the files to the internal storage. - -10. 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. - -h2. Attaching ADB - -ADB on Juno is supported over ethernet. Follow the instructions on "https://wiki.linaro.org/Platform/Android/SetupAdbOverTcp":https://wiki.linaro.org/Platform/Android/SetupAdbOverTcp to connect adb over the network. diff --git a/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt b/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt deleted file mode 100644 index 0853ae2..0000000 --- a/android/images/armv8-juice-juno-lsk/HOWTO_releasenotes.txt +++ /dev/null @@ -1,142 +0,0 @@ - -h2. About the Linaro Android Release for Juno (32-bit only) - -The Linaro Android release is based on a snapshot of the Android AOSP master taken on the 1st June. The build demonstrates the native 32-bit support found in the ARMv8-A architecture. The release uses Linaro Stable Kernel 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 with CTS version 4.4 and the CTS results are shared with members. The BIONIC component is validated with Android BIONIC tests. Android Monkey tests were run for stress testing. - -*NOTE:* The default setting from AOSP Build Variant "Engineering" is not performant for applications with ART. For better performance follow the instructions below: - -* The default build scripts (linaro_android_build_cmds.sh) included in this release, builds the Android sources for “TARGET_BUILD_VARIANT=eng”, this in turn sets the compiler-filter option in dalvik.vm.dex2oat-flags to “interpret-only” mode (refer build/core/main.mk). - -* If the user is interested in performance of apps we suggest re-building the sources for “user” mode instead of “eng” mode. To do this, in the script file linaro_android_build_cmds.sh, please modify the line number 153 by replacing “eng” with “user” and then run the script. - - -The Linaro Android releases for Juno (32-bit) appear monthly. Sources are also made available so you can build your own images (see the Building from Source tab). - -h2. About the Juno ARM Development Platform - -The Juno ARM Development Platform (ADP) is a software development platform for ARMv8-A. It includes: -* The Juno Versatile Express board -* ARMv8-A reference software ports available through Linaro -* Optional LogicTile Express FPGA board to extend the Juno system - this adds a large FPGA to Juno that can be used for driver development or prototyping. - -The Juno hardware delivers to software developers an open, vendor neutral ARMv8-A development platform with: -* Cortex® A57 and A53 MPCore™ for ARMv8-A big.LITTLE -* Mali™-T624 for 3D Graphics Acceleration and GP-GPU compute -* A SoC architecture aligned with Level 1 (Server) Base System Architecture - -The Juno ADP is available from ARM, please visit "www.arm.com/juno":http://www.arm.com/juno in early July for more details. - -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. 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. Support - -Please send any ARM support enquiries to "juno-support@arm.com":mailto:juno-support@arm.com?subject=Juno%20support%20request. Engineers at Linaro Members can receive support for Juno by sending support requests to "support@linaro.org":mailto:support@linaro.org?subject=Juno%20support%20request or visiting "http://support.linaro.org":http://support.linaro.org. - -h2. Functionality Listed by Software Component - -h3. AOSP Filesystem - -* Snapshot of the AOSP Master at 1st of June 2014 -* ART Runtime enabled as default and booting in 64-bit primary mode -* GPU support. The driver itself is believed performant but issues with HDLCD driver impact on-screen performance -* HDLCD is fully supported, but is currently only single-buffered leading to visual artefacts - -h3. Linux Kernel - -* Support for the ARM Juno Development Platform -* 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 is provided via on-board SMSC ethernet chip. -* Full USB driver support in Linux, for access to mass storage and input devices. -* big.LITTLE MP support for all 6 cores. -* Unified kernel and kernel config for Android and Linux. -* DVFS stable operating points are enabled for nominal and overdrive - -h3. UEFI - -* Booting an Operating System from NOR Flash or USB mass storage -* Support for Ethernet and PXE boot -* Version: v1.0-rc0 - -h3. ARM Trusted Firmware - -* The ARM Trusted Firmware provides an open source framework enabling easy integration of secure OS and run-time services to ARMv8-A platforms -* Loads the System Control Processor(SCP) firmware into the SCP -* Initializes the Trusted World before transitioning into Normal World. -* Services CPU hotplug requests coming from Normal World -* Provides a standard Power State Coordintion Interface (PSCI) implementation -* Version: v0.4-Juno-0.5-rc1 - -h3. SCP Firmware - -* System configuration -* DDR initialization -* Basic power state management for frequency and C-states -* SCPI commands (Ready, Set/Get Clocks, Set/Get CPU power states) -* Thermal protection (shutdown at 85C, Linux will receive a warning at 75C) -* DVFS support -* Version: 1.0.0-rc3 - -h2. Known Limitations Listed by Software Component - -h3. AOSP Filesystem - -* This build has been configured with interpreter support and optimizations have been incorrectly disabled. Java performance as a result is poor. -* HDLCD issues include a lack of double buffering meaning tearing can be seen -* HDLCD compatibility with monitors is variable at this time -* OpenCL support is not present at this time and will be enabled in a future release - -h3. Linux Kernel - -* The big.LITTLE support is functional but has not yet been tuned for efficiency and performance. - -h3. UEFI - -* No display controller support -* No USB OHCI support. Only EHCI is supported - -h3. ARM 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. - -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 the ARMv8-A Juno development platform. These patches can be found on Linaro's Android Git repositories. Some of these patches have been submitted to AOSP and are 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 -* "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 - -h2. Known Issues - -The following known issues are present in this release. Please contact "support@linaro.org":mailto:support@linaro.org?subject=Juno%20support%20request if you wish to know more information about these issues or have access problems when attempting to view them. - -| *Bug ID* | *Bug title* | *Bug summary* | -|"ARM-135":https://cards.linaro.org/browse/ARM-135 |Juno: Android fails to boot when board has a date in the future |When the board default date is set beyond 19.01.2038 Android fails to boot. This is most likely a bug in generic Android code. As a workaround, the date on the board needs to be set to something before 2038 cut off date. | -|"Bug 54":https://bugs.linaro.org/show_bug.cgi?id=54 |DNS lookup doesn't work |DNS lookup is broken on 64/64 and Juice builds. Setting additional 'dns' entries with setprop doesn't help. On the other hand networking works well when using IP addresses. | -|"Bug 45":https://bugs.linaro.org/show_bug.cgi?id=45 |CTS errors - Unable to resolve host "loca" : No address associated with hostname |A few CTS tests fails due to resons related to networking. Some of the failures are covered by Bug 54. This bug covers "Unable to resolve host "loca" : No address associated with hostname" | -|"Bug 12":https://bugs.linaro.org/show_bug.cgi?id=12 |Intermittent HDMI failures on 14.06 RC |There is a problem with HDMI sync. The board works with some monitors and doesn't work with other. The monitors known to work are: ASUS VS247 H-P, Samsung S22A300H, HP LP2475w | -|"Bug 22":https://bugs.linaro.org/show_bug.cgi?id=22 |Caffeinemark crashes |Caffeinemark benchmarking app crashes. Happens once in 5 runs. | -|"Bug 21":https://bugs.linaro.org/show_bug.cgi?id=21 |browser crash when closing a tab |Browser crashes when trying to close an opened tab. The crash repeats in subsequent Browser launches. | -|ARM JSW-749 Linux [Juno-Beta-rc3] | Performance is degraded with idle enabled | With cpuidle enabled android 64 bit fs shows performance degradation | -|ARM JSW-748 Linux [Juno-Beta-rc1] | Periodic black screen flash | Screen blanking is seen at a regular frequency of one in 10 sec | -|ARM JSW-746 | USB Drive failure at maximum OPP | With the overdrive operating point enabled, some USB hard drives don't work (causes kernel panic) | -|ARM JSW-743 | HDMI monitor incompatibilities | HDMI video out fails to display Android home screen on one out of 4 monitor types tried | -|ARM JSW-742 | No HDMI | HDMI video out does not work on both the ports | -|ARM JSW-741 |UEFI - missing boot options | UEFI bootmanager fails to list TFTP and PXE boot options if a live network cable not connected | -|ARM JSW-727 |'Trace' does not work in UEFI | While configuring DS-5 to trace UEFI execution, an error was returned when connecting DS-5 to the debugger | -|ARM JSW-711 |Reset failure | Reset fails if button is pressed during NOR flash write | diff --git a/android/vexpress-lsk/HOWTO_flashfirmware.txt b/android/vexpress-lsk/HOWTO_flashfirmware.txt deleted file mode 100644 index acb9369..0000000 --- a/android/vexpress-lsk/HOWTO_flashfirmware.txt +++ /dev/null @@ -1,169 +0,0 @@ -Ensure that you update your Versatile Express board firmware to the latest version. To update your VE board firmware, please follow the instructions below: - -* Clone the Linaro Versatile Express Firmware repository -* Connect and mount your Versatile Express motherboard USB mass storage device to your PC -* Remove all of the existing files from the USB mass storage device -* Copy the Linaro Firmware to the board - -For example: - -bc. git clone git://git.linaro.org/arm/vexpress-firmware.git -rm -rf /media/VEMSD/* -cp -R vexpress-firmware/* /media/VEMSD - -Once you have finished copying the firmware over: - -* Safely unmount the Versatile Express motherboard -* Reboot the Versatile Express board -* At the ARM Boot Loader "Cmd> " prompt, type the following commands: - -bc. Cmd> flash -Cmd> eraseall -Cmd> exit -Cmd> reboot - -* You may need to configure UEFI to boot from the image that you've created. See the "UEFI page":https://wiki.linaro.org/ARM/UEFI#Configure_UEFI on the Linaro Wiki for more details on configuring UEFI. -* You may want to set /media/VEMSD/config.txt AUTORUN to TRUE to be make the CoreTile boot from power on. -* For TC2, you should set the DIP swich closest to the black reset button down so that the Boot Monitor runs the boot script on power on. -* "Versatile Express version 5.2":https://silver.arm.com/browse/VE052 contains the original firmware and documentation for the Versatile Express platform -* Please contact "support@arm.com":mailto:support@arm.com for any issues related their firmware -* Please "contact Linaro":http://www.linaro.org/engineering/getting-started/discuss for any issues related to booting this release on the Versatile Express platform. - -<br> - -h2. Using TC2 as an A7-only or A15-only board - -h3. Configure the Firmware - -It is possible to configure a TC2 development board as an A7 or A15 only board. To do this, the developer should modify the /SITE1/HBI0249A/board.txt file on the Versatile Express firmware drive, usually mounted at /media/VEMSD. - -The relevant register is CFGREG6 on pages 78-81 of the following TRM: -"http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503e/DDI0503E_v2p_ca15_a7_tc2_trm.pdf":http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503e/DDI0503E_v2p_ca15_a7_tc2_trm.pdf - -You should add the following setting in board.txt: - -bc. SCC: 0x018 0x1FFFFFFF ; CFGRW6 - Reset register default (both clusters active) - - - or - - -bc. SCC: 0x018 0x00001FFF ; CFGRW6 - A15-only config - - - or - - -bc. SCC: 0x018 0x1FFFF000 ; CFGRW6 - A7-only config - -Remember to update TOTALSCCS, eg, if it was 32 and you've added one register, it becomes 33: - -bc. TOTALSCCS: 33 ;Total Number of SCC registers - -h3. Configure the Device Tree - -Once the hardware is booting as an A7 or A15 only board, next you need to remove the unused CPU nodes from the device tree. - -In the kernel source tree, edit arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts and remove the unused CPUs from this section: - -bc. cpus { - #address-cells = <1>; - #size-cells = <0>; - -bc. cpu2: cpu@2 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x100>; - cluster = <&cluster1>; - core = <&core2>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu3: cpu@3 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x101>; - cluster = <&cluster1>; - core = <&core3>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu4: cpu@4 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x102>; - cluster = <&cluster1>; - core = <&core4>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu0: cpu@0 { - device_type = "cpu"; - compatible = "arm,cortex-a15"; - reg = <0>; - cluster = <&cluster0>; - core = <&core0>; - clock-frequency = <1000000000>; - cci-control-port = <&cci_control1>; - }; - -bc. cpu1: cpu@1 { - device_type = "cpu"; - compatible = "arm,cortex-a15"; - reg = <1>; - cluster = <&cluster0>; - core = <&core1>; - clock-frequency = <1000000000>; - cci-control-port = <&cci_control1>; - }; - }; - -Next, you need to remove the GIC entries that are associated with the removed CPUs, eg: - -bc. gic: interrupt-controller@2c001000 { - compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic"; - #interrupt-cells = <3>; - #address-cells = <0>; - interrupt-controller; - reg = <0 0x2c001000 0 0x1000>, - <0 0x2c002000 0 0x1000>, - <0 0x2c004000 0 0x2000>, - <0 0x2c006000 0 0x2000>; - interrupts = <1 9 0xf04>; - -bc. gic-cpuif@0 { - compatible = "arm,gic-cpuif"; - cpuif-id = <0>; - cpu = <&cpu0>; - }; - -bc. gic-cpuif@1 { - compatible = "arm,gic-cpuif"; - cpuif-id = <1>; - cpu = <&cpu1>; - }; - -bc. gic-cpuif@2 { - compatible = "arm,gic-cpuif"; - cpuif-id = <2>; - cpu = <&cpu2>; - }; - -bc. gic-cpuif@3 { - compatible = "arm,gic-cpuif"; - cpuif-id = <3>; - cpu = <&cpu3>; - }; - -bc. gic-cpuif@4 { - compatible = "arm,gic-cpuif"; - cpuif-id = <4>; - cpu = <&cpu4>; - }; - }; - - -Finally, you need to re-compile the DTS file and copy it to the SD card used to boot the system, eg: - -bc. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs -cp arch/arm/boot/dts/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb - diff --git a/android/vexpress-lsk/HOWTO_getsourceandbuild.txt b/android/vexpress-lsk/HOWTO_getsourceandbuild.txt deleted file mode 100644 index 5b58921..0000000 --- a/android/vexpress-lsk/HOWTO_getsourceandbuild.txt +++ /dev/null @@ -1,107 +0,0 @@ -h1. Accessing Source Code - -h2. Linaro Android JB Source Code - -Run the "linaro_android_build_cmds.sh":http://releases.linaro.org/14.06/android/vexpress-lsk/linaro_android_build_cmds.sh, it will download the entire source code for both Android JB 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/vexpress-lsk/pinned-manifest.xml ("?":https://wiki.linaro.org/Platform/Android/ReproduceABuildExactly) -* "Source Manifest":http://releases.linaro.org/14.06/android/vexpress-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/vexpress-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/vexpress-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 update -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 \ -uboot-mkimage uuid-dev openjdk-7-jdk ant lib32ncurses5-dev xsltproc -sudo update-alternatives --config java -sudo update-alternatives --config javac -sudo update-alternatives --config javadoc - -* Download the Android building script for this release from "here":http://releases.linaro.org/14.06/android/vexpress-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 JB on your board - -* Insert SD card 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 SD card into your Versatile Express board and reboot it - -p. If UEFI is already configured to boot a Linaro Android image, it will boot from the SD card. If not, follow the instructions in the section: "Configure UEFI":https://wiki.linaro.org/ARM/UEFI#Configure_UEFI found on the Linaro wiki. - -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 gcc-arm-linux-gnueabi curl git libncurses5-dev - -* 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 - -*Note:* When you run menuconfig, make sure you go to @System Type -> Versatile Express@ platform type and make sure that both options are enabled. - -bc. [*] Versatile Express Cortex-A9x4 tile -[*] Device Tree support for Versatile Express platforms - -This will mean that the same kernel will run on A5, A9, TC2 and various fast models. - -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=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs - -* Insert the SD card containing the Linaro disk image -* Copy the kernel onto the memory card - -bc. cp arch/arm/boot/uImage /media/boot/ - -* Copy the device tree blob -** For A9 CoreTile: no device tree blob is needed -** For A5 CoreTile: @cp arch/arm/boot/vexpress-v2p-ca5s.dtb /media/boot/v2p-ca5s.dtb@ -** For A15 CoreTile (TC1): @cp arch/arm/boot/vexpress-v2p-ca15-tc1.dtb /media/boot/v2p-ca15-tc1.dtb@ -** For A15_A7 CoreTile: (TC2): @cp arch/arm/boot/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb@ - -* Eject the memory card @eject /media/boot@ - -* Insert the memory card into the Versatile Express board and power it on diff --git a/android/vexpress-lsk/HOWTO_install.txt b/android/vexpress-lsk/HOWTO_install.txt deleted file mode 100644 index 6e1e18a..0000000 --- a/android/vexpress-lsk/HOWTO_install.txt +++ /dev/null @@ -1,128 +0,0 @@ -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 Versatile Express board has the latest firmware and boot loader installed. Please check the "Firmware Update" tab on this page for the latest updates and installation instructions. - -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 SD card or larger -* Latest firmware installed onto the Versatile Express. Please see "Firmware Update" tab -* 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/vexpress-lsk/vexpress.img.bz2 - -h3. Installation Steps - -* Unzip the downloaded pre-built image -* Insert SD card into your PC and note the assigned @'/dev/sdX'@ - -bc. dmesg -SDCARD=/dev/sdX # sdcard found from dmesg above -bzcat vexpress.img.bz2 | sudo dd bs=64k of=$SDCARD - -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 a Versatile Express. 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/vexpress-lsk/boot.tar.bz2 -wget http://releases.linaro.org/14.06/android/vexpress-lsk/system.tar.bz2 -wget http://releases.linaro.org/14.06/android/vexpress-lsk/userdata.tar.bz2 - -* Download "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools which can be obtained in two ways: - -** 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.02/components/platform/linaro-image-tools/linaro-image-tools-2014.02.tar.gz - -* Insert SD card 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 SD card from your PC and insert it into the Versatile Express board. - -Before you can boot the image you will need to install the UEFI boot loader into NOR flash and update the Versatile MMC card configuration files. The instructions on the Firmware Update tab provide information on how to do this and how to configure UEFI to specify the SD card as a boot device. - -h2. Advanced Setup for Benchmarking - -Advanced users of Versatile Express may wish to perform benchmarking tests on the board. - -Booting with the root filesystem on a USB mass storage device is more efficient both in terms of electrical power and processing speed. Unfortunately, UEFI does not support booting the kernel from USB. In order to achieve this, we recommend that you install the kernel onto SD card and the root filesystem to USB mass storage. - -The instructions below will create two identical images: one on SD card and one on USB mass storage. The user is able to choose which device the kernel uses for the root filesystem by adding a command line parameter. By default, the android kernel will expect the root filesystem to be read from the SD card. Adding the parameter "androidboot.hardware=arm-versatileexpress-usb" to the command line will over-ride this behaviour and instruct the kernel to read the root filesystem from USB. - -Before following these instructions, ensure that you have both an SD card and a USB mass storage device of at least 4GB inserted into your Linux machine. - -h3. Using a pre-built image - -Follow the instructions above for creating an image on an SD card. Then repeat the instructions using the device path for your USB device. For example: - -bc. dmesg -SDCARD=/dev/sdX # sdcard found from dmesg above -USBMS=/dev/sdY # USB device found from dmesg above -bzcat vexpress.img.bz2 | sudo dd bs=64k of=$SDCARD -bzcat vexpress.img.bz2 | sudo dd bs=64k of=$USBMS - -h3. Using linaro-android-media-create - -First the user should run linaro-android-media-create as described above. Then run it again with a USB mass storage device. This will create two release images: one on the SD card and the other on the USB device. - -For example: - -bc. dmesg -SDCARD=/dev/sdX # sdcard found from dmesg above -USBMS=/dev/sdY # USB device found from dmesg above -linaro-android-media-create --mmc $SDCARD --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 -linaro-android-media-create --mmc $USBMS --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - -h3. Booting your system with the advanced setup - -Insert the SD card into the card slot on the Versatile Express board and insert the USB device into one of the USB device slots on the board. The USB slots are located below the ethernet port on the rear panel. - -Boot the board using the standard UEFI firmware setup as described in the Firmware Update tab. - -When UEFI starts, you will need to interrupt the boot countdown and edit the configuration to add the following text to the end of the kernel commandline: - -bc. androidboot.hardware=arm-versatileexpress-usb - -Instructions for updating the UEFI configuration can be found on the "UEFI wiki":https://wiki.linaro.org/ARM/UEFI#Updating_your_UEFI_Configuration - diff --git a/android/vexpress-lsk/HOWTO_releasenotes.txt b/android/vexpress-lsk/HOWTO_releasenotes.txt deleted file mode 100644 index 463e45e..0000000 --- a/android/vexpress-lsk/HOWTO_releasenotes.txt +++ /dev/null @@ -1,191 +0,0 @@ -h1. Linaro Stable Kernel (LSK) 14.06 Release for Versatile Express (Android) - -p. The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the linux stable kernel tree. It is produced to satisfy the requirements of Linaro members. The LSK focuses on quality and stability and is therefore a great basis for member products. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes. - -p. Linaro releases monthly binary images for the ARM "Versatile Express":http://www.arm.com/products/tools/development-boards/versatile-express/index.php including support for Cortex-A9, Cortex-A5, TC2 (big.LITTLE) CoreTiles and Fast Models. - -p. For support matters related to ARM hardware or firmware images downloaded from ARM sites, please contact "ARM support":mailto:support@arm.com - -p. This release includes Linaro Android Jelly Bean for both Versatile Express and Fast Models. The images are able to boot A5, A9 and TC2 using UEFI. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.06/android/vexpress-lsk/#tabs-3 tab). - -h2. About the TC2 Engineering Build - -This release is based on the Linux v3.10.44 kernel. As a consequence, almost all of the patches in the ARM Landing Team tree have been rebased and refactored to account for the latest upstream content. - -The TC2 CoreTile is the first example of a big.LITTLE system shipped by ARM and serves as a platform for development and test of big.LITTLE software. TC2 contains a tri-core Cortex-A7 cluster and a dual-core Cortex-A15 cluster linked using the CCI-400 coherent interconnect. - -The release contains the big.LITTLE MP patchset developed by ARM. This patchset is hosted by Linaro and can be found in the linked "git repository":https://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=shortlog;h=refs/heads/big-LITTLE-MP-latest. These patches have been developed and rigorously tested in order to enable the ARM Versatile Express V2P-CA15_A7 CoreTile (TC2) to run in full MP mode. This functionality has been optimised for energy and performance bringing it close to the Cortex-A7 (LITTLE) in energy consumption with near Cortex-A15 (big) performance. The patchset also includes optimizations that provide a considerable performance uplift across a wide range of benchmarks. The functionality introduced by this patchset is stable and ready for use on other platforms. Note that at present this LSK release is the reference point for big.LITTLE MP functionality. - -The patches in the big.LITTLE MP patchset are generic and applicable to big.LITTLE systems with minimal porting effort. To ease porting, the patches are also available as an isolated package located "here":https://wiki.linaro.org/ARM/VersatileExpress?action=AttachFile&do=get&target=big-LITTLE-MP-scheduler-patchset-14.06-lsk.tar.bz2. This package may be used directly by partners interested in porting the big.LITTLE MP scheduler functionality to their custom platform. Please contact "ARM support":mailto:support-sw@arm.com?subject=Query%20about%20ARM%20big.LITTLE%20MP%20patchset%20package in case of any queries related to this package. - -Also provided is optional configurable kernel support for an implementation of ARM's Power State Co-ordination Interface (PSCI). This support is disabled by default. To use PSCI support you will require secure firmware that is currently available to ARM licensees upon request to ARM. Please contact "ARM support":mailto:support-sw@arm.com?subject=Access%20to%20PSCI to get access to the firmware code. - -The 'small task packing feature' continues to be enabled by default in the kernel configuration. (See the documentation for this feature located at 'Documentation/arm/small_task_packing.txt’ within the kernel sources for more information on this feature). - -Please note that this release does not introduce any new functionality. - -h3. Scheduler modifications to support big.LITTLE - -The following patches make up the big.LITTLE MP patchset. - -| "sched: implement usage tracking":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0841c6ae0b53d43e4634cf4a1f88407b93c15399 | | -| "sched: entity load-tracking load_avg_ratio":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=be6ef1d56e70bfdfd79174d7d23a4b12d5b911ee | | -| "sched: Task placement for heterogeneous systems based on task load-tracking":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=798e82cab1a39f4d75796be024c4d7b08bc062e8 | | -| "sched: Forced task migration on heterogeneous systems":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2dd22b22c95851445c189c3d4708c027aa19cf5f | | -| "sched: Introduce priority-based task migration filter":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=943106d9437fcced79c4e48ed794410e5f750b4c | | -| "ARM: Add HMP scheduling support for ARM architecture":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d278bb1c4d5191e0d9b9911337e3b31a100a7f9f | | -| "ARM: sched: Use device-tree to provide fast/slow CPU list for HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=dc68bd92107d8990f4608d8f42744770fe203f7f | | -ehis release introduces further optimizations for the existing 'idle pull task migration' feature. These optimizations -| "ARM: sched: Setup SCHED_HMP domains":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=1baaccf456ece33b8fa02f8cdf3977d6a95b393c | | -| "sched: Add ftrace events for entity load-tracking":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=b9d3d5612899de4f8372ecfbc4c8f4ba5aa170ec | | -| "sched: Add HMP task migration ftrace event":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0d811e649ad31994e8f06b6b18101f249b34e912 | | -| "sched: SCHED_HMP multi-domain task migration control":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=76525733b4f4e0fdcc188dfe23941024ae626979 | | -| "sched: Enable HMP priority filter by default":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=1b8ae251638844173bd04a4c9e543581f3d92fbd | | -| "ARM: sched: Avoid empty 'slow' HMP domain":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=362036513b1dff299b2035d5b928a203742b98d7 | | -| "sched: Only down migrate low priority tasks if allowed by affinity mask":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=eeebbf595c8dcd6392537c4d13b8cda78001f4e5 | | -| "sched: fix arch_get_fast_and_slow_cpus to get logical cpumask correctly":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=a9f9bca843e44144670c660638274363f34b9847 | | -| "sched: Do not ignore grouped tasks during HMP forced migration.":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d2c920023cbc456414f8e07ff253a89be535b41b | | -| "sched: Ignore offline CPUs in HMP migration & load stats":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=b64cc6f7e54b97536dbecc05d193b31b27feecf1 | | -| "ARM: Change load tracking scale using sysfs":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0e48eed05c47aa2e00b772a519b36286e466621e | | -| "ARM: Experimental Frequency-Invariant Load Scaling Patch":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=71b5dbd6d527d5de8aaef7e1f8658df95caf28aa | | -| "ARM: Fix build breakage when big.LITTLE.conf is not used.":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=ae570aeb1d40d531a498e53e2a815a52996f0749 | | -| "sched: Basic global balancing support for HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=cf71912f481c7b6fc39e9b2021e8f9c058116c26 | | -| "sched: cfs.nr_running does not contain the intended metric":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7e6446630039fcbabb9582ebefdcbc30de32c0e2 | | -| "Revert sched: Enable HMP priority filter by default":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7362251d8a422dcba5c56408b92fc2b6ad03b10c | | -| "HMP: Use unweighted load for hmp migration decisions":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=ede58a69a32b187899e6cccbbd299a04d3f50b71 | | -| "HMP: Select least-loaded CPU when performing HMP Migrations":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=08d7db89a214a138516419a85e17272b09180abd | | -| "HMP: Avoid multiple calls to hmp_domain_min_load in fast path":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=3f3b210703f80fe60dbfa13c25b30d4effbf9f4b | | -| "HMP: Force new non-kernel tasks onto big CPUs until load stabilises":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=954978dd2cff81cc15745b9e581a1709e238f8ef | | -| "sched: Restrict nohz balance kicks to stay in the HMP domain":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=6eada0087366d8aec6bc38348a68f721f538cc5c | | -| "HMP: experimental: Force all rt tasks to start on little domain":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=4ab2679351e9566a6b0822f2d841a902758ba066 | | -| "HMP: select 'best' task for migration rather than 'current'":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=ee52487aaf659ef630ce3371de0e59944253581b | | -| "sched: HMP fix traversing the rb-tree from the curr pointer":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=aaba2453951b3743d003be228102e1da63c75326 | | -| "sched: track per-rq 'last migration time'":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=5fad81c7739db3a1fc6380dcc3d7902666ed5ee8 | | -| "HMP: Modify the runqueue stats to add a new child stat":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=b98cd6acc86f2c3bc10902476836746727b73ba9 | | -| "HMP: Explicitly implement all-load-is-max-load policy for HMP targets":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=6b695bd8a4e2c86cc466010517c0260dc3653742 | | -| "sched: HMP change nr_running offload metric":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=1f435579ea80d4639061435d8337df5a2c92e530 | | -| "HMP: Implement idle pull for HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=db20b7088c6d7f7920dace95c7fc8d9955650214 | | -| "HMP: Access runqueue task clocks directly.":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=de66e01565848d0236ca9e7e9e2f6ecd5c27a021 | | -| "HMP: Update migration timer when we fork-migrate":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=18e3c3d2cc1346cb7cc2e3fd777b2c6f4fbb6135 | | -| "sched: HMP: Change default HMP thresholds":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d73babce9a77f8143136fe0d7b6c1ae44b5652dc | | -| "sched: HMP: Additional trace points for debugging HMP":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7b8e0b3f2af55b1ffb5c10be1daa59d8dc21d140 | | -| "arm: ipi raise/start/end tracing":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2353c1f8009c14e89b323b18ae246c485fc034e4 | | -| "smp: smp_cross_call function pointer tracing":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=5ecaba3d9f4ab514fe8d383534e24b306f116896 | | -| "sched: HMP: fix potential logical errors":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2e14ecb254a3eaa2993b5dd04014f41e1d6188ce | | -| "hmp: Remove potential for task_struct access race":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=cd5c2cc93d3dc581a19c62442f40895500d2a34c | | -| "HMP: Implement task packing for small tasks in HMP":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d8063e7015122eb3f6173acf496171def8941734 | | -| "HMP: Avoid using the cpu stopper to stop runnable tasks":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2a68d1e9125582bedeac4ea34fb9901ab1f7de11 | | -| "sched: hmp: add read-only hmp domain sysfs file":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0b877c2baac65994016c6812804d1b30e89c18ed | | -| "Documentation: HMP: Small Task Packing explanation":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=f5be72980bc321f3491377861835c343cc27af0d | | -| "sched: hmp: Fix build breakage when not using CONFIG_SCHED_HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7cf6a7300bb9a88f543061270419427395ab4d2f | | -| "sched: reset blocked load decay_count during synchronization":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/f720a920e88f1ec79db8c9f0031f61c610e40b02 | | -| "sched: update runqueue clock before migrations away":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/7896b1e659db571556436b99ebb2e475e54a24f5 | | -| "sched: hmp: Make idle balance behaviour normal when packing disabled":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/257e5075a1433513bb354f202adcd2dea8a8dc08 | | -| "sched: hmp: Change TC2 packing config to disabled default if present":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/ba8ed8301f5bca4a44c80e2173c66391b76898df | | -| "config: Make packing present on TC2":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/5e0791511a938eaf28d9071b411ffa71a79ef8ed | | -| "sched: hmp: Fix potential task_struct memory leak":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/b2fafaba35f490947b78e8d0d4f4264a137e64cd | | -| "HMP: Restrict irq_default_affinity to hmp_slow_cpu_mask":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/1d462599bee9a2f5f3988aafa43feda602d5e188 | | -| "HMP: Fix rt task allowed cpu mask restriction code on 1x1 system":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/b30814c74c184bbb231e24d6c857699af338468b | | -| "hmp: sched: Clean up hmp_up_threshold checks into a utility fn":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/765aae2 | | -| "sched: hmp: unify active migration code":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/0baa581 | | -| "hmp: Use idle pull to perform forced up-migrations":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/aae7721 | | -| "hmp: dont attempt to pull tasks if affinity doesn't allow it":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/5a570cf | | -| "Revert hmp: dont attempt to pull tasks if affinity doesn't allow it":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/8503bfd | | -| "Revert hmp: Use idle pull to perform forced up-migrations":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/7e1f7d3 | | -| "Revert sched: hmp: unify active migration code":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/11971ff | | -| "Revert hmp: sched: Clean up hmp_up_threshold checks into a utility fn":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/db3dba6 | | -| "sched: hmp: Change small task packing defaults for all platforms":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/1ade57e | | -| "hmp: sched: Clean up hmp_up_threshold checks into a utility fn":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/84efcd0 | | -| "sched: hmp: unify active migration code":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/0168997 | | -| "hmp: Use idle pull to perform forced up-migrations":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/940407d | | -| "hmp: dont attempt to pull tasks if affinity doesn't allow it":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/d1df056 | | - -h3. Platform Support. - -In addition to the big.LITTLE MP work the TC2 platform support includes: -** TC2: reset CPUs spuriously woken up on cluster power up -** vexpress: add shim layer for psci backend on TC2 -** vexpress: allow native pm ops backends to probe for psci suppport -** psci: add cmdline option to enable use of psci -** psci: add probe function to discover presence of a psci implementation -** psci: convert psci '-EALREADYON' error code to linux '-EAGAIN' -** vexpress: add psci support in TC2 device tree -** psci: add constants to specify affinity levels -** TC2: replace hard coded cluster and cpu values with constants -** TC2: use generic accessors to extract cpu and cluster ids -** CPUidle & CPUfreq support -** hwmon driver allowing, amongst other things, TC2's power, current and energy measurements to be read through standard sysfs interfaces -** Common clocks implementation -** Regulator driver -** Drivers for previously hard-coded configuration interfaces -** Support self-hosted debugging through idle -** In addition to the CPU PMUs the perf framework supports the CCI-400 PMUs -** A patch from Thomas Gliexner which supports a IRQ affinity mask being specified in the command line. This can be used to reduce unnecessary IRQ wakeups on Cortex-A15. For instructions see the irqaffinity entry in Documentation/kernel-parameters.txt -** arm-multi_pmu_v2 - enables the use of multiple PMU types or sources, for example profiling across both Cortex-A15 and Cortex-A7 clusters and getting results for CCI. - -h2. Where To Find More Information - -More information on Linaro can be found on our "website.":http://www.linaro.org/ - -h2. Feedback and Support - -Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. - -** Linaro Android Development "mailing list":http://lists.linaro.org/mailman/listinfo/linaro-android -** Linaro Android IRC channel on irc.freenode.net at @#linaro-android@ - -* Landing Team bug reports should be filed in "JIRA":http://cards.linaro.org/browse/ARM#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel by clicking on the "Create issue" button on the top menu bar. -** You will need to login to your JIRA account. If you do not have an account or are having problems, email its@linaro.org for help. -* More general bug reports should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to "Linaro project":http://bugs.launchpad.net/linaro/+filebug. -* Questions? "ask Linaro":http://ask.linaro.org/. -* Interested in commercial support? inquire at "Linaro support":mailto:support@linaro.org - -h2. Resolved in this release - -* "ARM-46":http://cards.linaro.org/browse/ARM-46 Booting using UEFI with bootmon from VE CD 5.2 fails -* "ARM-53":http://cards.linaro.org/browse/ARM-53 Watchdog timeout booting Android on single core fastmodels -* "ARM-58":http://cards.linaro.org/browse/ARM-58 LP:1231468 - HTML5 video playback failed, using Chromium but works with Firefox, on ARM Versatile Express ALIP image -* "ARM-60":http://cards.linaro.org/browse/ARM-60 LP:1254750 - Browser crashes regularly on vexpress with KitKat - -h2. Known Issues - -h3. General Issues - -* "ARM-16":http://cards.linaro.org/browse/ARM-16 LP:1097309 - serial console doesn't received characters on TC2 -* "ARM-24":http://cards.linaro.org/browse/ARM-24 LP:1172350 - Audio playback under Android JellyBean stops sporadically on TC2 with release 13.03 -* "ARM-50":http://cards.linaro.org/browse/ARM-50 LP:1217893 - perf shows zero for cycle and instruction counts on TC2 -* "ARM-57":http://cards.linaro.org/browse/ARM-57 LP:1243194 - power top doesn't show any stats -* "ARM-61":http://cards.linaro.org/browse/ARM-61 LP:1254738 - Serial console doesn't work reliably on vexpress with KitKat -* "ARM-77":http://cards.linaro.org/browse/ARM-77 LP:1260320 - long running gator and DS-5 streaming capture reported kernel crash dump -* "ARM-132":https://cards.linaro.org/browse/ARM-132 14.05 LSK pre-release validation shows degradation in BBench scores -* "ARM-137":https://cards.linaro.org/browse/ARM-137 HMP Patch 77 missing from 14.06 release - -h3. Known Issues due to lack of video acceleration - -* "ARM-59":http://cards.linaro.org/browse/ARM-59 LP:987155 - vexpress: Angrybirds display severely truncated -* "LP: #987172":http://launchpad.net/bugs/987172 vexpress: YouTube video playback fails - -h3. Known Issues due to generic Android features - -* "ARM-51":http://cards.linaro.org/browse/ARM-51 Gallery app crashes on start on vexpress Android 4.3 -* "ARM-101":https://cards.linaro.org/browse/ARM-101 LP: 1229185 - Panic in ip6tables during Android boot - -h3. Additional information - -NOTE: When using the interactive governor with Android, take care to use the following values for governor specific tunables. These values have been selected after careful analysis on this LSK version and result in optimal power-performance on TC2. In future LSK releases, additional system initialisation logic will use these values as defaults. - -Interactive settings for the Cortex-A7 cluster: - -'above_hispeed_delay': 20000 -'go_hispeed_load': 85 -'hispeed_freq': 800000 -'min_sample_time': 80000 -'timer_rate': 20000 - -Interactive settings for the Cortex-A15 cluster: - -'above_hispeed_delay': 20000 -'go_hispeed_load': 85 -'hispeed_freq': 1000000 -'min_sample_time': 80000 -'timer_rate': 20000 diff --git a/android/vexpress-lsk/HOWTO_rtsm.txt b/android/vexpress-lsk/HOWTO_rtsm.txt deleted file mode 100644 index 31ed027..0000000 --- a/android/vexpress-lsk/HOWTO_rtsm.txt +++ /dev/null @@ -1,79 +0,0 @@ -This release was boot tested on FVP A15x4 and A15x4-A7x4 models. No rigorous testing was carried out. This build is expected to run on other models. No UEFI binary exists for A15-A7 models; in this case, the A15 binary can be used, but the A7 CPUs will not be available - -h2. Prerequisites - -* Install the model(s) you wish to run. You must have a valid license and the environment set up to run models -* Install "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools - -h3. Install Linaro Image Tools - -Linaro Image Tools contain scripts that allow you to combine multiple components into a single Android image. The components are: - -* boot.tar.bz2 - contains the kernel and boot loaders -* system.tar.bz2 - contains the entire system files and general OS -* userdata.tar.bz2 - contains sample data and tests - -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: Build from source - -bc. wget http://releases.linaro.org/14.02/components/platform/linaro-image-tools/linaro-image-tools-2014.02.tar.gz - -h2. Create a 2GB image file - -Fast Models will only deal with file systems up to 2GB in size, however the Linaro pre-built image for Android requires a 4GB filesystem. Therefore, we will build our own image using the pre-built artifacts (displayed above) - -The following command downloads all the Android OS components necessary to make up a complete Android image. - -bc. wget http://releases.linaro.org/14.06/android/vexpress-lsk/boot.tar.bz2 -wget http://releases.linaro.org/14.06/android/vexpress-lsk/system.tar.bz2 -wget http://releases.linaro.org/14.06/android/vexpress-lsk/userdata.tar.bz2 - -Using the @linaro-android-media-create@, which is part of the @linaro-image-tools@, you can combine all the components into a single image. - -bc. linaro-android-media-create --image-file linaro.img --image-size 2000M --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 -tar jxvf boot.tar.bz2 - -h2. Run Fast Models with UEFI - -The instructions for running UEFI on the various models are very similar. The two differences are the UEFI binary and the model used. Follow the model specific instruction below, then proceed to the generic instructions in the section "Run the model with UEFI". Make sure that the model binary is on your path, or alter the MODEL variable definition to include the path to the binary. - -h3. Run A9x4 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A9_MPx4 -UEFI=boot/rtsm/uefi_rtsm_ve-ca9x4.bin - -h3. Run A15x1 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A15x1 -UEFI=boot/rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run A15x2 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A15x2 -UEFI=boot/rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run A15x4 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A15x4 -UEFI=boot/rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run the model with UEFI - -bc. touch uefi-vars.fd # create the file if it doesn't already exist - -bc. $MODEL \ --C motherboard.flashloader0.fname=$UEFI \ --C motherboard.flashloader1.fname=uefi-vars.fd \ --C motherboard.flashloader1.fnameWrite=uefi-vars.fd \ --C motherboard.mmc.p_mmc_file=linaro.img \ --C motherboard.pl011_uart0.unbuffered_output=true \ --C motherboard.smsc_91c111.enabled=1 \ --C motherboard.hostbridge.userNetworking=1 - diff --git a/android/vexpress/HOWTO_flashfirmware.txt b/android/vexpress/HOWTO_flashfirmware.txt deleted file mode 100644 index acb9369..0000000 --- a/android/vexpress/HOWTO_flashfirmware.txt +++ /dev/null @@ -1,169 +0,0 @@ -Ensure that you update your Versatile Express board firmware to the latest version. To update your VE board firmware, please follow the instructions below: - -* Clone the Linaro Versatile Express Firmware repository -* Connect and mount your Versatile Express motherboard USB mass storage device to your PC -* Remove all of the existing files from the USB mass storage device -* Copy the Linaro Firmware to the board - -For example: - -bc. git clone git://git.linaro.org/arm/vexpress-firmware.git -rm -rf /media/VEMSD/* -cp -R vexpress-firmware/* /media/VEMSD - -Once you have finished copying the firmware over: - -* Safely unmount the Versatile Express motherboard -* Reboot the Versatile Express board -* At the ARM Boot Loader "Cmd> " prompt, type the following commands: - -bc. Cmd> flash -Cmd> eraseall -Cmd> exit -Cmd> reboot - -* You may need to configure UEFI to boot from the image that you've created. See the "UEFI page":https://wiki.linaro.org/ARM/UEFI#Configure_UEFI on the Linaro Wiki for more details on configuring UEFI. -* You may want to set /media/VEMSD/config.txt AUTORUN to TRUE to be make the CoreTile boot from power on. -* For TC2, you should set the DIP swich closest to the black reset button down so that the Boot Monitor runs the boot script on power on. -* "Versatile Express version 5.2":https://silver.arm.com/browse/VE052 contains the original firmware and documentation for the Versatile Express platform -* Please contact "support@arm.com":mailto:support@arm.com for any issues related their firmware -* Please "contact Linaro":http://www.linaro.org/engineering/getting-started/discuss for any issues related to booting this release on the Versatile Express platform. - -<br> - -h2. Using TC2 as an A7-only or A15-only board - -h3. Configure the Firmware - -It is possible to configure a TC2 development board as an A7 or A15 only board. To do this, the developer should modify the /SITE1/HBI0249A/board.txt file on the Versatile Express firmware drive, usually mounted at /media/VEMSD. - -The relevant register is CFGREG6 on pages 78-81 of the following TRM: -"http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503e/DDI0503E_v2p_ca15_a7_tc2_trm.pdf":http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503e/DDI0503E_v2p_ca15_a7_tc2_trm.pdf - -You should add the following setting in board.txt: - -bc. SCC: 0x018 0x1FFFFFFF ; CFGRW6 - Reset register default (both clusters active) - - - or - - -bc. SCC: 0x018 0x00001FFF ; CFGRW6 - A15-only config - - - or - - -bc. SCC: 0x018 0x1FFFF000 ; CFGRW6 - A7-only config - -Remember to update TOTALSCCS, eg, if it was 32 and you've added one register, it becomes 33: - -bc. TOTALSCCS: 33 ;Total Number of SCC registers - -h3. Configure the Device Tree - -Once the hardware is booting as an A7 or A15 only board, next you need to remove the unused CPU nodes from the device tree. - -In the kernel source tree, edit arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts and remove the unused CPUs from this section: - -bc. cpus { - #address-cells = <1>; - #size-cells = <0>; - -bc. cpu2: cpu@2 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x100>; - cluster = <&cluster1>; - core = <&core2>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu3: cpu@3 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x101>; - cluster = <&cluster1>; - core = <&core3>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu4: cpu@4 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x102>; - cluster = <&cluster1>; - core = <&core4>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu0: cpu@0 { - device_type = "cpu"; - compatible = "arm,cortex-a15"; - reg = <0>; - cluster = <&cluster0>; - core = <&core0>; - clock-frequency = <1000000000>; - cci-control-port = <&cci_control1>; - }; - -bc. cpu1: cpu@1 { - device_type = "cpu"; - compatible = "arm,cortex-a15"; - reg = <1>; - cluster = <&cluster0>; - core = <&core1>; - clock-frequency = <1000000000>; - cci-control-port = <&cci_control1>; - }; - }; - -Next, you need to remove the GIC entries that are associated with the removed CPUs, eg: - -bc. gic: interrupt-controller@2c001000 { - compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic"; - #interrupt-cells = <3>; - #address-cells = <0>; - interrupt-controller; - reg = <0 0x2c001000 0 0x1000>, - <0 0x2c002000 0 0x1000>, - <0 0x2c004000 0 0x2000>, - <0 0x2c006000 0 0x2000>; - interrupts = <1 9 0xf04>; - -bc. gic-cpuif@0 { - compatible = "arm,gic-cpuif"; - cpuif-id = <0>; - cpu = <&cpu0>; - }; - -bc. gic-cpuif@1 { - compatible = "arm,gic-cpuif"; - cpuif-id = <1>; - cpu = <&cpu1>; - }; - -bc. gic-cpuif@2 { - compatible = "arm,gic-cpuif"; - cpuif-id = <2>; - cpu = <&cpu2>; - }; - -bc. gic-cpuif@3 { - compatible = "arm,gic-cpuif"; - cpuif-id = <3>; - cpu = <&cpu3>; - }; - -bc. gic-cpuif@4 { - compatible = "arm,gic-cpuif"; - cpuif-id = <4>; - cpu = <&cpu4>; - }; - }; - - -Finally, you need to re-compile the DTS file and copy it to the SD card used to boot the system, eg: - -bc. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs -cp arch/arm/boot/dts/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb - diff --git a/android/vexpress/HOWTO_getsourceandbuild.txt b/android/vexpress/HOWTO_getsourceandbuild.txt deleted file mode 100644 index d730a58..0000000 --- a/android/vexpress/HOWTO_getsourceandbuild.txt +++ /dev/null @@ -1,107 +0,0 @@ -h1. Accessing Source Code - -h2. Linaro Android JB Source Code - -Run the "linaro_android_build_cmds.sh":http://releases.linaro.org/latest/android/vexpress/linaro_android_build_cmds.sh, it will download the entire source code for both Android JB and the kernel and attempt to build it. - -The pinned and source manifests can be found here: - -* "Pinned Manifest":http://releases.linaro.org/latest/android/vexpress/pinned-manifest.xml ("?":https://wiki.linaro.org/Platform/Android/ReproduceABuildExactly) -* "Source Manifest":http://releases.linaro.org/latest/android/vexpress/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/latest/android/vexpress/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/latest/android/vexpress/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 update -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 \ -uboot-mkimage uuid-dev openjdk-7-jdk ant lib32ncurses5-dev xsltproc -sudo update-alternatives --config java -sudo update-alternatives --config javac -sudo update-alternatives --config javadoc - -* Download the Android building script for this release from "here":http://releases.linaro.org/latest/android/vexpress/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 JB on your board - -* Insert SD card 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 SD card into your Versatile Express board and reboot it - -p. If UEFI is already configured to boot a Linaro Android image, it will boot from the SD card. If not, follow the instructions in the section: "Configure UEFI":https://wiki.linaro.org/ARM/UEFI#Configure_UEFI found on the Linaro wiki. - -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 gcc-arm-linux-gnueabi curl git libncurses5-dev - -* 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 - -*Note:* When you run menuconfig, make sure you go to @System Type -> Versatile Express@ platform type and make sure that both options are enabled. - -bc. [*] Versatile Express Cortex-A9x4 tile -[*] Device Tree support for Versatile Express platforms - -This will mean that the same kernel will run on A5, A9, TC2 and various fast models. - -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=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs - -* Insert the SD card containing the Linaro disk image -* Copy the kernel onto the memory card - -bc. cp arch/arm/boot/uImage /media/boot/ - -* Copy the device tree blob -** For A9 CoreTile: no device tree blob is needed -** For A5 CoreTile: @cp arch/arm/boot/vexpress-v2p-ca5s.dtb /media/boot/v2p-ca5s.dtb@ -** For A15 CoreTile (TC1): @cp arch/arm/boot/vexpress-v2p-ca15-tc1.dtb /media/boot/v2p-ca15-tc1.dtb@ -** For A15_A7 CoreTile: (TC2): @cp arch/arm/boot/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb@ - -* Eject the memory card @eject /media/boot@ - -* Insert the memory card into the Versatile Express board and power it on diff --git a/android/vexpress/HOWTO_install.txt b/android/vexpress/HOWTO_install.txt deleted file mode 100644 index 4ba2556..0000000 --- a/android/vexpress/HOWTO_install.txt +++ /dev/null @@ -1,128 +0,0 @@ -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 Versatile Express board has the latest firmware and boot loader installed. Please check the "Firmware Update" tab on this page for the latest updates and installation instructions. - -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 SD card or larger -* Latest firmware installed onto the Versatile Express. Please see "Firmware Update" tab -* 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/latest/android/vexpress/vexpress.img.bz2 - -h3. Installation Steps - -* Unzip the downloaded pre-built image -* Insert SD card into your PC and note the assigned @'/dev/sdX'@ - -bc. dmesg -SDCARD=/dev/sdX # sdcard found from dmesg above -bzcat vexpress.img.bz2 | sudo dd bs=64k of=$SDCARD - -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 a Versatile Express. 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/latest/android/vexpress/boot.tar.bz2 -wget http://releases.linaro.org/latest/android/vexpress/system.tar.bz2 -wget http://releases.linaro.org/latest/android/vexpress/userdata.tar.bz2 - -* Download "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools which can be obtained in two ways: - -** 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/latest/components/platform/linaro-image-tools/linaro-image-tools-${YYYY}.${MM}.tar.gz - -* Insert SD card 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 SD card from your PC and insert it into the Versatile Express board. - -Before you can boot the image you will need to install the UEFI boot loader into NOR flash and update the Versatile MMC card configuration files. The instructions on the Firmware Update tab provide information on how to do this and how to configure UEFI to specify the SD card as a boot device. - -h2. Advanced Setup for Benchmarking - -Advanced users of Versatile Express may wish to perform benchmarking tests on the board. - -Booting with the root filesystem on a USB mass storage device is more efficient both in terms of electrical power and processing speed. Unfortunately, UEFI does not support booting the kernel from USB. In order to achieve this, we recommend that you install the kernel onto SD card and the root filesystem to USB mass storage. - -The instructions below will create two identical images: one on SD card and one on USB mass storage. The user is able to choose which device the kernel uses for the root filesystem by adding a command line parameter. By default, the android kernel will expect the root filesystem to be read from the SD card. Adding the parameter "androidboot.hardware=arm-versatileexpress-usb" to the command line will over-ride this behaviour and instruct the kernel to read the root filesystem from USB. - -Before following these instructions, ensure that you have both an SD card and a USB mass storage device of at least 4GB inserted into your Linux machine. - -h3. Using a pre-built image - -Follow the instructions above for creating an image on an SD card. Then repeat the instructions using the device path for your USB device. For example: - -bc. dmesg -SDCARD=/dev/sdX # sdcard found from dmesg above -USBMS=/dev/sdY # USB device found from dmesg above -bzcat vexpress.img.bz2 | sudo dd bs=64k of=$SDCARD -bzcat vexpress.img.bz2 | sudo dd bs=64k of=$USBMS - -h3. Using linaro-android-media-create - -First the user should run linaro-android-media-create as described above. Then run it again with a USB mass storage device. This will create two release images: one on the SD card and the other on the USB device. - -For example: - -bc. dmesg -SDCARD=/dev/sdX # sdcard found from dmesg above -USBMS=/dev/sdY # USB device found from dmesg above -linaro-android-media-create --mmc $SDCARD --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 -linaro-android-media-create --mmc $USBMS --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 - -h3. Booting your system with the advanced setup - -Insert the SD card into the card slot on the Versatile Express board and insert the USB device into one of the USB device slots on the board. The USB slots are located below the ethernet port on the rear panel. - -Boot the board using the standard UEFI firmware setup as described in the Firmware Update tab. - -When UEFI starts, you will need to interrupt the boot countdown and edit the configuration to add the following text to the end of the kernel commandline: - -bc. androidboot.hardware=arm-versatileexpress-usb - -Instructions for updating the UEFI configuration can be found on the "UEFI wiki":https://wiki.linaro.org/ARM/UEFI#Updating_your_UEFI_Configuration - diff --git a/android/vexpress/HOWTO_releasenotes.txt b/android/vexpress/HOWTO_releasenotes.txt deleted file mode 100644 index ae512ea..0000000 --- a/android/vexpress/HOWTO_releasenotes.txt +++ /dev/null @@ -1,44 +0,0 @@ -h1. Linux-Linaro Release for Versatile Express (Android) - -p. This release is produced, validated and released by Linaro and is based on the linux-linaro-tracking kernel tree. - -p. Linaro releases monthly binary images for the ARM "Versatile Express":http://www.arm.com/products/tools/development-boards/versatile-express/index.php including support for Cortex-A9, Cortex-A5, TC2 (big.LITTLE) CoreTiles and Fast Models. - -p. For support matters related to ARM hardware or firmware images downloaded from ARM sites, please contact "ARM support":mailto:support@arm.com - -p. This release includes Linaro Android Jelly Bean for both Versatile Express and Fast Models. The images are able to boot A5, A9 and TC2 using UEFI. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/latest/android/vexpress/#tabs-3 tab). - -More information on Linaro can be found on our "website.":http://www.linaro.org/ - -h2. Feedback and Support - -Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. - -** Linaro Android Development "mailing list":http://lists.linaro.org/mailman/listinfo/linaro-android -** Linaro Android IRC channel on irc.freenode.net at @#linaro-android@ - -* Landing Team bug reports should be filed in "JIRA":http://cards.linaro.org/browse/ARM#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel by clicking on the "Create issue" button on the top menu bar. -** You will need to login to your JIRA account. If you do not have an account or are having problems, email its@linaro.org for help. -* More general bug reports should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to "Linaro project":http://bugs.launchpad.net/linaro/+filebug. -* Questions? "ask Linaro":http://ask.linaro.org/. -* Interested in commercial support? inquire at "Linaro support":mailto:support@linaro.org - -h3. Additional information - -NOTE: When using the interactive governor with Android, take care to use the following values for governor specific tunables. These values have been selected after careful analysis on this LSK version and result in optimal power-performance on TC2. In future LSK releases, additional system initialisation logic will use these values as defaults. - -Interactive settings for the Cortex-A7 cluster: - -'above_hispeed_delay': 20000 -'go_hispeed_load': 85 -'hispeed_freq': 800000 -'min_sample_time': 80000 -'timer_rate': 20000 - -Interactive settings for the Cortex-A15 cluster: - -'above_hispeed_delay': 20000 -'go_hispeed_load': 85 -'hispeed_freq': 1000000 -'min_sample_time': 80000 -'timer_rate': 20000 diff --git a/android/vexpress/HOWTO_rtsm.txt b/android/vexpress/HOWTO_rtsm.txt deleted file mode 100644 index 581b3e4..0000000 --- a/android/vexpress/HOWTO_rtsm.txt +++ /dev/null @@ -1,81 +0,0 @@ -This release has been boot tested on FVP_VE A15x4 and A9MPx4. Reaching a login prompt is the only test carried out. This build is expected to run on other models. No UEFI binary exists for dual cluster A15x{1|4}-A7x{1|4} models; in this case the A15 binary can be used, but the A7 CPUs will be held in reset. - -h2. Prerequisites - -* Install the model(s) you wish to run. You must have a valid license and the environment set up to run models -* Install "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools - -h3. Install Linaro Image Tools - -Linaro Image Tools contain scripts that allow you to combine multiple components into a single Android image. The components are: - -* boot.tar.bz2 - contains the kernel and boot loaders -* system.tar.bz2 - contains the entire system files and general OS -* userdata.tar.bz2 - contains sample data and tests - -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: Build from source - -bc. wget http://releases.linaro.org/latest/components/platform/linaro-image-tools/linaro-image-tools-${YYYY}.${MM}.tar.gz - -h2. Create a 2GB image file - -Fast Models will only deal with file systems up to 2GB in size, however the Linaro pre-built image for Android requires a 4GB filesystem. Therefore, we will build our own image using the pre-built artifacts (displayed above) - -The following command downloads all the Android OS components necessary to make up a complete Android image. - -bc. wget http://releases.linaro.org/latest/android/vexpress/boot.tar.bz2 -wget http://releases.linaro.org/latest/android/vexpress/system.tar.bz2 -wget http://releases.linaro.org/latest/android/vexpress/userdata.tar.bz2 - -Using the @linaro-android-media-create@, which is part of the @linaro-image-tools@, you can combine all the components into a single image. - -bc. linaro-android-media-create --image-file linaro.img --image-size 2000M --dev vexpress --boot boot.tar.bz2 --system system.tar.bz2 --userdata userdata.tar.bz2 -tar jxvf boot.tar.bz2 - -h2. Run Fast Models with UEFI - -The instructions for running UEFI on the various models are very similar. The two differences are the UEFI binary and the model used. Follow the model specific instruction below, then proceed to the generic instructions in the section "Run the model with UEFI". - -h3. Run A9x4 model with UEFI - -bc. MODEL=/usr/local/DS-5/bin/FVP_VE_Cortex-A9_MPx4 -UEFI=boot/rtsm/uefi_rtsm_ve-ca9x4.bin - -h3. Run A15x1 model with UEFI - -bc. MODEL=$HOME/ARM/models/Linux64_GCC-4.1/FVP_VE_Cortex-A15x1 -UEFI=boot/rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run A15x2 model with UEFI - -bc. MODEL=$HOME/ARM/models/Linux64_GCC-4.1/FVP_VE_Cortex-A15x2 -UEFI=boot/rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run A15x4 model with UEFI - -bc. MODEL=$HOME/ARM/models/Linux64_GCC-4.1/FVP_VE_Cortex-A15x4 -UEFI=boot/rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run the model with UEFI - -bc. MMC=linaro.img -UEFI_VARS=$HOME/uefi-vars.fd -touch $UEFI_VARS # create the file if it doesn't already exist - -bc. $MODEL \ --C motherboard.flashloader0.fname=$UEFI \ --C motherboard.flashloader1.fname=$UEFI_VARS \ --C motherboard.flashloader1.fnameWrite=$UEFI_VARS \ --C motherboard.mmc.p_mmc_file=$MMC \ --C motherboard.pl011_uart0.unbuffered_output=true \ --C motherboard.smsc_91c111.enabled=1 \ --C motherboard.hostbridge.userNetworking=1 - diff --git a/openembedded/juno-lsk/EULA.txt b/openembedded/juno-lsk/EULA.txt deleted file mode 100644 index d8e300e..0000000 --- a/openembedded/juno-lsk/EULA.txt +++ /dev/null @@ -1,267 +0,0 @@ -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. - - - -"Juno ARM Development Platform" 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 Juno ARM Development Platform. - - - -"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 a Juno ARM Development Platform 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 - -*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. ARM 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/openembedded/juno-lsk/GETTINGSTARTED.textile b/openembedded/juno-lsk/GETTINGSTARTED.textile deleted file mode 100644 index 67a56d0..0000000 --- a/openembedded/juno-lsk/GETTINGSTARTED.textile +++ /dev/null @@ -1,206 +0,0 @@ -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/openembedded/juno-lsk/#tabs-5. - -h2. Juno ports - - - -h3. Back panel - -<img src="https://releases.linaro.org/14.06/openembedded/juno-lsk/RearPanel.png"> - -h3. Front panel - -<img src="https://releases.linaro.org/14.06/openembedded/juno-lsk/FrontPanel.png"> - -h3(#uarts). UARTs - -There are 4 UARTs on the Juno board: - -| *UART* | *Location* | *Used by* | *Baud* | *Data bits* | *Stop bits* | *Parity | -|SoC UART0 |"back panel":https://releases.linaro.org/14.06/openembedded/juno-lsk/RearPanel.png |The motherboard, UEFI and the Linux kernel. |115200 |8 |1 |None | -|SoC UART1 |"back panel":https://releases.linaro.org/14.06/openembedded/juno-lsk/RearPanel.png |SCP firmware |115200 |8 |1 |None | -|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 |1 |None | -|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":#setup section. - - - -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 hosted on this website by following the instructions in the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-2. - -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":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-2 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(#setup). 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":https://releases.linaro.org/14.06/openembedded/juno-lsk/RearPanel.png connector ("settings":#uarts). -# Connect the 12 volt power, then press the red "ON/OFF button":https://releases.linaro.org/14.06/openembedded/juno-lsk/RearPanel.png on the back panel. - -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":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-2. - -h3. Setting the Real Time Clock (required for Android) - -New Juno boards do not have the correct time programmed into the real time clock. Some software (notably Android) will not operate correctly until a sensible time is programmed. To set the time, start a terminal session with "UART0":https://releases.linaro.org/14.06/openembedded/juno-lsk/RearPanel.png connector ("settings":#uarts). Ensure there is power to the board, but the SoC must be powered off (if it is not, then press the black "Hardware Reset" button). - -Execute the following: - -bc. ARM V2M-Juno Boot loader v1.0.0 -HBI0262 build 596 -ARM V2M_Juno Firmware v1.1.7 -Build Date: May 27 2014 -Time : 11:52:35 -Date : 09:07:2060 -Cmd> debug -Debug> date -09/07/2060 -Change Date? Y\N >y -D:>23 -M:>6 -Y:>2014 -Debug> time -15 : 51 : 58 -Change Time? Y\N >y -s:>0 -m:>08 -h:>14 -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 Configuration Port 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 table 1 below 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. - To reset to factory settings, the value to program should be 0x00FE001E. - -7. In the [SCC REGISTERS] section, below the "TOTALSCCS" line, insert the following line: - -bc. 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. - -<br><br> - -h4. Table 1. Bit mappings for the CONFIG_TEX_COMPRESSED_FORMAT_ENABLE register. - - *Please ensure you have obtained the appropriate license(s) before enabling these texture compression formats* - -|Bit|Texture compression format| Direct X 9| DirectX 10| DirectX 11| OpenGL ES 1.1| OpenGL ES 2.0| OpenGL ES 3.0| OpenGL 2.0 - 2.1| OpenGL 3.0 - 3.1| OpenGL 3.2 - 4.1| OpenGL 4.2| -|0 | Invalid format | | | | | | | | | | | -|1 | ETC2 | | | | x<sup>[a]</sup> | x<sup>[a]</sup> | x | | | | | -|2 | EAC, 1 component | | | | | | x | | | | | -|3 | ETC2 + EAC | | | | | | x | | | | | -|4 | EAC, 2 components | | | | | | x | | | | | -|5 | Reserved | | | | | | | | | | | -|6 | NXR | | | | | | | | | | | -|7 | BC1_UNORM (DXT1) | x | x | x | x<sup>[b]</sup> | x<sup>[b]</sup> | x<sup>[b]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|8 | BC2_UNORM (DXT3) | x | x | x | | x<sup>[c]</sup> | x<sup>[c]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|9 | BC3_UNORM (DXT5) | x | x | x | | x<sup>[d]</sup> | x<sup>[d]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | x<sup>[f]</sup> | -|10 | BC4_UNORM (RGTC1_UNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|11 | BC4_SNORM (RGTC1_SNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|12 | BC5_UNORM (RGTC2_UNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|13 | BC5_SNORM (RGTC2_SNORM) | | x | x | | | | x<sup>[g]</sup> | x | x | x | -|14 | BC6H_UF16 | | | x | | | | | | x<sup>[h]</sup> | x | -|15 | BC6H_SF16 | | | x | | | | | | x<sup>[h]</sup> | x | -|16 | BC7_UNORM | | | x | | | | | | x<sup>[h]</sup> | x | -|17 | EAC_SNORM, 1 component | | | | | | x | | | | | -|18 | EAC_SNORM, 2 components | | | | | | x | | | | | -|19 | ETC2 + punch-through alpha | | | | | | x | | | | | -|20 | ASTC 3D LDR | | | | | | | | | | | -|21 | ASTC 3D HDR | | | | | | | | | | | -|22 | ASTC 2D LDR | | | | x<sup>[e]</sup> | x<sup>[e]</sup> | x<sup>[e]</sup> | | | | | -|23 | ASTC 2D HDR | | | | | | | | | | | -|24 - 31 | Reserved | | | | | | | | | | | - -<p></p> - -Key - [a] Enable for GL_OES_compressed_ETC1_RGB8_texture - [b] Enable for GL_EXT_texture_compression_dxt1 - [c] Enable for GL_ANGLE_texture_compression_dxt3 - [d] Enable for GL_ANGLE_texture_compression_dxt5 - [e] Enable for GL_KHR_texture_compression_astc_ldr - [f] Enable for GL_EXT_texture_compression_s3tc - [g] Enable for GL_EXT_texture_compression_rgtc - [h] Enable for GL_ARB_texture_compression_bptc - - - -h3. Additional documentation - -For further details, please see the following documents. - -* "Juno SoC Reference Manual":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DDI0515A3b_juno_arm_development_platform_soc_trm.pdf -* "V2M Juno Reference Manual":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DDI0524A4b_v2m_juno_reference_manual.pdf -* "SCPI protocol description":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=scpi-doc-v0.2.1.zip diff --git a/openembedded/juno-lsk/HACKING.textile b/openembedded/juno-lsk/HACKING.textile deleted file mode 100644 index e5d60c0..0000000 --- a/openembedded/juno-lsk/HACKING.textile +++ /dev/null @@ -1,282 +0,0 @@ -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/openembedded/juno-lsk/#tabs-5. - -h2. Building the Linaro Kernel - -h3. Prerequisites - -* Ubuntu 12.04 64 bit system. You can download Ubuntu from ubuntu.com -* git - -bc. sudo apt-get install build-essential git - -* 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 - -h3. Get the Linaro Kernel Source - -bc. git clone https://git.linaro.org/landing-teams/working/arm/kernel-release.git -cd kernel -git checkout lsk-3.10-armlt-juno-20140616 - -h3. Create a kernel config - -Do not use the arm64 defconfig, instead, build a config from the config fragments that Linaro provides: - -bc. ARCH=arm64 scripts/kconfig/merge_config.sh \ -linaro/configs/linaro-base.conf \ -linaro/configs/distribution.conf \ -linaro/configs/vexpress64.conf \ - -Note: the config fragments are part of the git repository and the source tarball. - -h3. Build the kernel - -To build the kernel Image and juno.dtb files, use the following command: - -bc. make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- Image dtbs - -h3. Install your kernel - -Copy the kernel Image and the juno.dtb files to the BOOT partition on the USB drive created in the "Binary Installation tab":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-2. - -bc. cp arch/arm64/boot/Image /media/BOOT/Image -cp arch/arm64/boot/dts/juno.dtb /media/BOOT/juno/juno.dtb - - -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> - - -h2. SCP Firmware - -The SCP Firmware is only available as a pre-built binary. - - - -h2. ARM Trusted Firmware - -The ARM trusted firmware consists of the following images: - -|<b>Filename</b>|<b>Image Type</b>|<b>Image Name</b>| -|bl1.bin|BL1|ARM Trusted ROM image| -|bl2.bin|BL2|ARM Trusted Firmware| -|bl31.bin|BL3-1|EL3 runtime| -|bl32.bin (optional)|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.4-Juno-0.5 - -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 - -To build the optional bl3-2 Test Secure Payload component, use the following commands instead (the 'make realclean' is important): - -bc. $ make realclean -$ make PLAT=juno SPD=tspd all - -By default the preceding commands produce 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@ (if the 'SPD=tspd' flag is used) - -... where @<build-type>@ is either `debug` or `release`. - -To clean the ARM 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 v1.0-rc0 - - - -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/BL33_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/BL33_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 - optional) -* 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. Download the "firmware image artefacts":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=juno-firmware-beta-0.7.5.zip and extract to a working directory (hereafter referred to as @"<path to prebuilt binary>"@). - -4. 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/arm-trusted-firmware/build/juno/release/bl32.bin . -$ cp $JUNO_ROOT_DIR/edk2/Build/ArmJuno/RELEASE_GCC48/FV/BL33_AP_UEFI.fd bl33.bin - -If you wish to use the pre-built ARM trusted firmware and UEFI EDK2 images instead of building them from source, then the last four lines of the above block can independently be replaced with the following: - -bc. $ cp <path to prebuilt binary>/bl2.bin . -$ cp <path to prebuilt binary>/bl31.bin . -$ cp <path to prebuilt binary>/bl32.bin . -$ cp <path to prebuilt binary>/bl33.bin . - - -5. Create the FIP file: - -bc. $ fip_create --dump \ - --bl2 bl2.bin \ - --bl30 bl30.bin \ - --bl31 bl31.bin \ - --bl32 bl32.bin \ (if the optional bl32 image is present) - --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 ---------------------------- -Creating "fip.bin"; - -6. 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 ---------------------------- -Updating "fip.bin" - -For more details and options about the `fip_create` tool: - -bc. $ fip_create --help - - -h2. Installing the binaries - -Please refer to the section titled "Firmware update" on the "Binary Image Installation tab":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-2. diff --git a/openembedded/juno-lsk/INSTALL.textile b/openembedded/juno-lsk/INSTALL.textile deleted file mode 100644 index bef8631..0000000 --- a/openembedded/juno-lsk/INSTALL.textile +++ /dev/null @@ -1,371 +0,0 @@ -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/openembedded/juno-lsk/#tabs-5. - -h2. Installation - -Linaro OpenEmbedded releases are made up of the following components. - -| *.img.gz | pre-built images for minimal and LAMP root filesystems | -| hwpack_*.tar.gz | hardware pack | -| linaro-image-*.rootfs.tar.gz | a choice of Root file system (RootFS) images | -| Image | kernel used by UEFI | -| juno_bl1.bin | ARM Trused Firmware BL1 binary | -| juno_fip.bin | ARM Trused Firmware Firmware Image Package (FIP) binary | -| juno.dtb | Device Tree Binary | -| board_recovery_image_0.7.5.zip | Juno board firmware recovery image | - -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 OpenEmbedded images are made up of two components. The "Hardware Pack":https://wiki.linaro.org/HardwarePacks, which contains the kernel, boot loader and/or Device Tree blob and a Root file system (RootFS) of your choice to generate an image. - -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":#firmware installed. Please see "Juno Board Recovery Image and MCC firmware update":#firmware below for the latest updates and installation instructions. The 14.06 release has been formally QA tested with Firmware version 0.7.1 and sanity tested with Firmware version 0.7.5, 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 ("www.ubuntu.com":http://www.ubuntu.com) -* 4GB USB drive or larger -* Latest firmware installed onto the board. Please see "Juno Board Recovery Image and MCC firmware update":#firmware section below -* This release pre-built image, which you can download from the above list of artifacts - -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 - -* Unmount all partitions on the drive -** If you do not unmount all of the USB drive's partitions, you run the risk that the image will not be created successfully. -* Write the image to the drive - -bc. gunzip *minimal*.img.gz -sudo dd if=*minimal*.img of=$DRIVE - -Replace @*minimal*.img.gz@ with the full filename of the prebuilt image you are attempting to write to the disk. - -After you have created the disk image and before you remove the USB drive from your system, you should make sure you wait for all writes to the USB drive to complete. - -The following commands may help with this: - -bc. $ sync -$ sudo eject $DRIVE - -You should also ensure that you have written the image to the USB drive correctly. To do this, after running the eject command, physically remove the USB drive from the system and re-connect the USB drive again. You must unmount all partitions on the USB drive at this point. Note, due to disconnecting and reconnecting the drive, the device path /dev/sdX may have changed. You should check the @dmesg@ output again to ensure that you know the correct path of your USB drive. - -Once you are ready, run the following commands: - -bc. $ sudo cmp /dev/sdX *minimal*.img -$ sync -$ sudo eject /dev/sdX - -Replace @*minimal*.img.gz@ with the full filename of the prebuilt image you are attempting to write to the disk. - -When you are confident that the image was created successfully, 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 -* 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'@ - -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 >@ - -*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. sudo linaro-media-create --mmc /dev/sdX --dev juno --hwpack <hwpack filename> --binary <rootfs filename> - -After you have created the disk image and before you remove the USB drive from your system, you should make sure you wait for all writes to the USB drive to complete. - -The following commands may help with this: - -bc. $ sync -$ sudo eject /dev/sdX - -Where /dev/sdX is the device node for the USB drive as discovered in the instructions above. - - -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":#firmware provide information on how to do this. - -Once you have the latest firmware installed, you will need to configure UEFI to boot the kernel from the "boot" partition of the USB stick. See the steps directly below for instructions on how to configure UEFI. - - -h2. UEFI Configuration - -The example below shows how a test system was configured. Please note: some of the menu option numbers may be different on your board. In particular, the menu option used to choose the boot partition may change number over a reboot. In the example below, the partition named "boot" was option 4. Please be careful that you choose the correct option that corresponds to the menu options you see on your board. - -Also take care that the USB partitions are showing in the menu before selecting a menu option. There is a known bug in UEFI where the partitions on USB drives does not show the first time the menu is displayed. To overcome this, as shown in the example below, the user should enter the menu option @"[1] Add Boot Device Entry"@, by pressing @1@ followed by the enter key. Then, when the list display and the USB partitions are missing, please press the @ESC@ key once. This will exit out of the current menu prompt and leave you back at the Boot Menu again. At this point, please press 1 again to re-enter the menu option @"[1] Add Boot Device Entry"@ and continue by selecting the partition named "boot" on the USB drive. - -UEFI outputs to UART0 on the board. UART0 uses 115200 baud with 8 bits and no stop bit. Please see the "UARTs" section on the "Getting Started tab":https://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-4 for more details on the UART configuration of the board. - - -h3. Example UEFI Configuration - -When booting your system, after a short time, you be presented by a boot countdown from 10, thus: - -bc. The default boot selection will start in 10 seconds - -When you see this prompt, please press the enter key to interrupt the countdown. You will then be presented with a menu, thus: - -bc. [1] Linux from NOR Flash -[2] Shell -[3] Boot Manager -Start: - -Depending on the configuration of your board, the menu option called "Boot Manager" may not be option 3. In this example, we can see that the Boot Menu is indeed option "3", so we choose it by pressing the "3" key and pressing enter. You will then be presented with a boot menu, thus: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: - -The first thing we need to do is to delete all of the existing Boot Device Entries. Deleting a Boot Device Entry is achieved by pressing the 3 key and pressing enter: - -bc. [1] Linux from NOR Flash -Delete entry: - -In our example, using the default config from the first time you boot the board, there is only 1 Boot Device Entry: "Linux from NOR Flash". You must delete this entry by pressing the 1 key and pressing enter. After this, you will be returned to the Boot Menu where you should continue by deleting *all* Boot Device Entries that are configured. - -Once you have done this, you should continue by creating a new Boot Device Entry by selecting option 1 from from the Boot Menu. After selecting the menu option by pressing the 1 key folllowed by enter, you will see a list of available Boot Devices, thus: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 1 -[1] Firmware Volume (0 MB) -[2] Firmware Volume (0 MB) -[3] NOR Flash (63 MB) -[4] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[5] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[6] PXE on MAC Address: 00:02:F7:00:57:DD -[7] TFTP on MAC Address: 00:02:F7:00:57:DD -Select the Boot Device: - -As you will see in the example above, there is no partition named "boot" available to the user. At this point, the user must press the @ESC@ key to exit the "Select the Boot Device" option and return to the Boot Menu. From the Boot Menu, please select option 1 again. The example below shows how this looked on our test system, your results may differ: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu -Choice: 1 -[1] Firmware Volume (4068 MB) -[2] Firmware Volume (4068 MB) -[3] NOR Flash (63 MB) -[4] boot (67 MB) -[5] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[6] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[7] PXE on MAC Address: 00:02:F7:00:57:DD -[8] TFTP on MAC Address: 00:02:F7:00:57:DD -Select the Boot Device: - -As you will see, the menu option @"boot"@ has now appeared, allowing us to select the partition named "boot" on the USB drive. In the example above, the partition named "boot" is option 4. Your system may show a different option for the partition named boot on your USB drive. Please examine the menu and choose the appropriate option. - -Once you have choosen the Boot Device, you will be prompted for the configuration of that Boot Device. - -The first quesion will ask for the file path of the kernel, thus: - -bc. File path of the EFI Application or the kernel: - -When configuring a system to boot OpenEmbedded, you enter the file path of the kernel as "Image" without the quotes and followed by the enter key, for this is the filename of the kernel in the boot partition on the USB drive. - -Next you will be prompted if the kernel has Flattened Device Tree support: - -bc. Has FDT support? [y/n] - -The answer is yes, so please press the "y" key followed by enter. Next you will be asked if you wish to configure an "initrd" for your system: - -bc. Add an initrd: [y/n] - -The answer is no, so please press the "n" key followed by enter. - -After this you will be asked to supply the arguments required to boot the kernel: - -bc. Arguments to pass to the binary: - -Please note, copy and paste does not work well over the serial terminal. The user is advised to type the commandline arguments by hand, character at a time, followed by the enter key. The commandline used is shown below: - -bc. console=ttyAMA0,115200 rootwait root=/dev/sda2 - -Finally, after entering the commandline, the final question is simply asking for a title that will appear in the Boot Menu: - -bc. Description for this new Entry: - -You may enter a simple string of alphanumberic characters use to represent the name of this Boot Device. On our example system, we chose to type the string "Linux on USB", without the quotes, followed by pressing the enter key. - -After entering the description string, you will then be returned to the boot menu: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu - -It may take a long time, perhaps over a minute for UEFI to save the Boot Device Entry. - -After you have configured the Boot Device Entry, next you must configure the Flattened Device Tree (FDT) path. You do this by selecting the option "Update FDT path" by pressing the 4 key and pressing enter. As with the Add Boot Device Entry option, next you will be presented with a list of Boot Devices that can host the FDT file. On our test system, the list looked like this: - -bc. [1] Firmware Volume (4068 MB) -[2] Firmware Volume (4068 MB) -[3] NOR Flash (63 MB) -[4] boot (67 MB) -[5] VenHw(E7223039-5836-41E1-B542-D7EC736C5E59) -[6] VenHw(02118005-9DA7-443A-92D5-781F022AEDBB) -[7] PXE on MAC Address: 00:02:F7:00:57:DD -[8] TFTP on MAC Address: 00:02:F7:00:57:DD - -Choose the option that corresponds to the partition named "boot" on your system. In the example above, this is option 4. Enter the option number and press the enter key. You will then be prompted for the file path for the FDT file: - -bc. File path of the FDT blob: - -At this prompt, type the filename "juno\juno.dtb" and press the enter key. Please note, the string contains a Windows style backslash, not a Unix style forward slash. The system may take some time to save the configuration. After which, you will be returned to the Boot Menu: - -bc. [1] Add Boot Device Entry -[2] Update Boot Device Entry -[3] Remove Boot Device Entry -[4] Update FDT path -[5] Return to main menu - -At this point, we have completed our configuration and we can return to the main menu by selecting option 5 "Return to main menu". To select option 5, press the 5 key and press enter. - -Once you are back at the main menu, you will see that the selection of Boot Devices has now changed. On our test system, the selection looked like this: - -bc. [1] Linux on USB -[2] Shell -[3] Boot Manager -Start: - -Where option 1, "Linux on USB" was the Boot Device Entry that we created by following the instructions above. - -You should now choose this option to boot from your USB drive. When booting, you will see output similar to this: - -bc. [1] Linux on USB -[2] Shell -[3] Boot Manager -Start: 1 - PEI 217 ms - DXE 48 ms - BDS 368934797873 ms - BDS 3650 ms -Total Time = 368934801789 ms -[ 0.000000] Initializing cgroup subsys cpu -[ 0.000000] Linux version 3.10.40.0-1-linaro-lt-vexpress64 (buildslave@x86-64-07) (gcc version 4.8.3 20140401 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2014.04 - Linaro GCC 4.8-2014.04) ) #1ubuntu1~ci+140623185422 SMP Mon Jun 23 18:55:05 UTC 2014 -[ 0.000000] CPU: AArch64 Processor [410fd030] revision 0 -[ 0.000000] Machine: Juno - -One important part of the output is the Linux version, shown above as 3.10.40.0-1-linaro-lt-vexpress64. It is critical that you ensure you are booting Linux version 3.10.40.0-1-linaro-lt-vexpress64. If you are not, it may be that you have mis-cofigured your system and you should revise your configuration by repeating the steps above. - -note: it is normal for the BDS to show a excessively long time to load the images. This is a known intermittent bug. It did not take such a long time to load. - - -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":https://wiki.linaro.org/ARM/Juno?action=AttachFile&do=get&target=DS-5_config.zip 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(#firmware). Firmware update - -This section describes how to update the firmware on the Juno board. - -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 Juno board recovery image onto the flash memory device, replacing any files already in the flash memory. - -To install firmware images that you have built yourself, the procedure is the same except that you will overwrite the contents of the /SOFTWARE/ directory with your own images. - -To update the MCC firmware only, the procedure is the same except that the MCC firmware update bundle will contain only a subset of the files contained in the full recovery image. - -<br> - -To carry out a system recovery, update the MCC firmware, or install your own custom firmware images, 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 one or more of the firmware components then skip to step 7. Otherwise, for a full system recovery, format the configuration flash memory (FAT16). - -7. Extract the board recovery image ("board_recovery_image_0.7.5.zip":http://releases.linaro.org/14.06/openembedded/juno-lsk/board_recovery_image_0.7.5.zip) to the root directory of the configuration flash memory, preserving the directory structure. - -8. If you are performing a system recovery or installing an update from ARM then skip to step 9. Otherwise if you wish to install firmware images that you have "built yourself":http://releases.linaro.org/14.06/openembedded/juno-lsk/#tabs-3 then delete the bl1.bin and fip.bin from the /SOFTWARE/ directory in the configuration flash memory, and copy your own bl1.bin and fip.bin images into that directory to replace them. - -9. Safely eject the mass storage device, giving it time to write the files to the internal storage. - -10. 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/openembedded/juno-lsk/README.textile b/openembedded/juno-lsk/README.textile deleted file mode 100644 index 2f6055a..0000000 --- a/openembedded/juno-lsk/README.textile +++ /dev/null @@ -1,101 +0,0 @@ - -h2. About the Linaro OpenEmbedded Release for ARMv8-A - -"OpenEmbedded":http://www.openembedded.org/wiki/Main_Page is a software framework used for creating Linux distributions aimed for, but not restricted to, embedded devices. The port offered here has been built using Linaro GCC version 4.8. - -h2. About the Juno ARM Development Platform - -The Juno ARM Development Platform (ADP) is a software development platform for ARMv8-A. It includes: -* The Juno Versatile Express board -* ARMv8-A reference software ports available through Linaro -* Optional LogicTile Express FPGA board to extend the Juno system - this adds a large FPGA to Juno that can be used for driver development or prototyping. - -The Juno hardware delivers to software developers an open, vendor neutral ARMv8-A development platform with: -* Cortex® A57 and A53 MPCore™ for ARMv8-A big.LITTLE -* Mali™-T624 for 3D Graphics Acceleration and GP-GPU compute -* A SoC architecture aligned with Level 1 (Server) Base System Architecture - -The Juno ADP is available from ARM, please visit "www.arm.com/juno":http://www.arm.com/juno in early July for more details. - -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/openembedded/juno-lsk/#tabs-3 tab). - -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/openembedded/juno-lsk/#tabs-5. - - -h2. Support - -Please send any ARM support enquiries to "juno-support@arm.com":mailto:juno-support@arm.com?subject=Juno%20support%20request. Engineers at Linaro Members can receive support for Juno by sending support requests to "support@linaro.org":mailto:support@linaro.org?subject=Juno%20support%20request or visiting "http://support.linaro.org":http://support.linaro.org. - -h2. Functionality Listed by Software Component - -h3. Linux Kernel - -* Support for the ARM Juno Development Platform -* 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 is provided via on-board SMSC ethernet chip. -* Full USB driver support in Linux, for access to mass storage and input devices. -* big.LITTLE MP support for all 6 cores. -* DVFS stable operating points are enabled for nominal and overdrive - -h3. UEFI - -* Booting an Operating System from NOR Flash or USB mass storage -* Support for Ethernet and PXE boot -* Version: v1.0-rc0 - -h3. ARM Trusted Firmware - -* The ARM Trusted Firmware provides an open source framework enabling easy integration of secure OS and run-time services to ARMv8-A platforms -* Loads the System Control Processor(SCP) firmware into the SCP -* Initializes the Trusted World before transitioning into Normal World. -* Services CPU hotplug requests coming from Normal World -* Provides a standard Power State Coordintion Interface (PSCI) implementation -* Version: v0.4-Juno-0.5-rc1 - -h3. SCP Firmware - -* System configuration -* DDR initialization -* Basic power state management for frequency and C-states -* SCPI commands (Ready, Set/Get Clocks, Set/Get CPU power states) -* Thermal protection (shutdown at 85C, Linux will receive a warning at 75C) -* DVFS support -* Version: 1.0.0-rc3 - -h2. Known Limitations Listed by Software Component - -h3. Linux Kernel - -* The big.LITTLE support is functional but has not yet been tuned for efficiency and performance. - -h3. UEFI - -* No display controller support -* No USB OHCI support. Only EHCI is supported - -h3. ARM 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. - -h2. Known Issues - -The following known issues are present in this release. Please contact "support@linaro.org":mailto:support@linaro.org?subject=Juno%20support%20request if you wish to know more information about these issues or have access problems when attempting to view them. - -| *Bug ID* | *Bug title* | *Bug summary* | -|"ARM-133":https://cards.linaro.org/browse/ARM-133 |2nd USB Mass storage device fails |When attempting to use a second USB storage device on Juno, both sda and sdb will go r/o and then fail to read from the device. | -|"ARM-134":https://cards.linaro.org/browse/ARM-134 |nfs v4 hangs when creating symlinks |nfs v4 hangs when creating symlinks | -|"Bug 48":https://bugs.linaro.org/show_bug.cgi?id=48 |password authentication over SSH doesn't work |<i>please see public bug for details</i> | -|ARM JSW-749 Linux [Juno-Beta-rc3] | Performance is degraded with idle enabled | With cpuidle enabled android 64 bit fs shows performance degradation | -|ARM JSW-746 | USB Drive failure at maximum OPP | With the overdrive operating point enabled, some USB hard drives don't work (causes kernel panic) | -|ARM JSW-727 |'Trace' does not work in UEFI | While configuring DS-5 to trace UEFI execution, an error was returned when connecting DS-5 to the debugger | -|ARM JSW-711 |Reset failure | Reset fails if button is pressed during NOR flash write| -|"LP:1212126":https://bugs.launchpad.net/linaro-oe/+bug/1212126 |perf self test does not execute on Linaro openembedded lamp image |<i>please see public bug for details</i> | -|"LP:1212115":https://bugs.launchpad.net/linaro-oe/+bug/1212115i |phpmysql test fail on Linaro openembedded Lamp image on Lava |<i>please see public bug for details</i> | -|"LP:1235239":https://bugs.launchpad.net/linaro-oe/+bug/1235239 |level 1 translation fault when extracting bzipped tarball |<i>please see public bug for details</i> | - diff --git a/openembedded/vexpress-lsk/FASTMODELS.textile b/openembedded/vexpress-lsk/FASTMODELS.textile deleted file mode 100644 index addfcdb..0000000 --- a/openembedded/vexpress-lsk/FASTMODELS.textile +++ /dev/null @@ -1,86 +0,0 @@ -This release has been boot tested on FVP_VE A15x4 and A9MPx4. Reaching a login prompt is the only test carried out. This build is expected to run on other models. No UEFI binary exists for dual cluster A15x{1|4}-A7x{1|4} models; in this case the A15 binary can be used, but the A7 CPUs will be held in reset. - -h2. Prerequisites - -* Install the model(s) you wish to run. You must have a valid license and the environment set up to run models -* Install "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools -* Install kpartx which you can get by issuing the following command in your terminal - -bc. sudo apt-get install kpartx - -Linaro OpemEmbedded images are made up of two components. The "Hardware Pack":https://wiki.linaro.org/HardwarePacks, which contains the kernel, boot loader and/or Device Tree blob and a Root file system (RootFS) of your choice to generate an image. - -h3. Install 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.02/components/platform/linaro-image-tools/linaro-image-tools-2014.02.tar.gz - -h2. Create a 2GB image file - -Fast Models will only deal with file systems up to 2GB in size, however the pre-built image may be larger. In this case, you can build your own image using the pre-built artifacts as listed below. - -Using the following command, you will download the RootFS, the hardware pack. - -bc. wget http://releases.linaro.org/14.06/openembedded/vexpress-lsk/hwpack_linaro-lsk-vexpress_20140621-667_armhf_supported.tar.gz -wget http://releases.linaro.org/14.06/openembedded/vexpress-lsk/linaro-image-alip-genericarmv7a-20140612-267.rootfs.tar.gz - -Now you need to create the image using the following commands. - -bc. linaro-media-create --image-file linaro.img --image-size 2000M --dev vexpress --hwpack hwpack_linaro-lsk-vexpress_20140621-667_armhf_supported.tar.gz --binary linaro-image-alip-genericarmv7a-20140612-267.rootfs.tar.gz - -bc. sudo kpartx -a linaro.img -mkdir boot -sudo mount /dev/mapper/loop0p1 boot -cp boot/uImage . -cp -ar boot/rtsm rtsm -sudo umount boot -sudo kpartx -d linaro.img - -note: unless you use kpartx to delete the loop mappings as above, even if you update linaro.img and re-mount it, it will not refresh and you will end up using the old image. - -h2. Run Fast Models with UEFI - -The instructions for running UEFI on the various models are very similar. The two differences are the UEFI binary and the model used. Follow the model specific instruction below, then proceed to the generic instructions in the section "Run the model with UEFI". Make sure that the model binary is on your path, or alter the MODEL variable definition to include the path to the binary. - -h3. Run A9x4 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A9_MPx4 -UEFI=rtsm/uefi_rtsm_ve-ca9x4.bin - -h3. Run A15x1 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A15x1 -UEFI=rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run A15x2 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A15x2 -UEFI=rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run A15x4 model with UEFI - -bc. MODEL=FVP_VE_Cortex-A15x4 -UEFI=rtsm/uefi_rtsm_ve-ca15.bin - -h3. Run the model with UEFI - -bc. touch uefi-vars.fd # create the file if it doesn't already exist - -bc. $MODEL \ --C motherboard.flashloader0.fname=$UEFI \ --C motherboard.flashloader1.fname=uefi-vars.fd \ --C motherboard.flashloader1.fnameWrite=uefi-vars.fd \ --C motherboard.mmc.p_mmc_file=linaro.img \ --C motherboard.pl011_uart0.unbuffered_output=true \ --C motherboard.smsc_91c111.enabled=1 \ --C motherboard.hostbridge.userNetworking=1 - diff --git a/openembedded/vexpress-lsk/FIRMWARE.textile b/openembedded/vexpress-lsk/FIRMWARE.textile deleted file mode 100644 index acb9369..0000000 --- a/openembedded/vexpress-lsk/FIRMWARE.textile +++ /dev/null @@ -1,169 +0,0 @@ -Ensure that you update your Versatile Express board firmware to the latest version. To update your VE board firmware, please follow the instructions below: - -* Clone the Linaro Versatile Express Firmware repository -* Connect and mount your Versatile Express motherboard USB mass storage device to your PC -* Remove all of the existing files from the USB mass storage device -* Copy the Linaro Firmware to the board - -For example: - -bc. git clone git://git.linaro.org/arm/vexpress-firmware.git -rm -rf /media/VEMSD/* -cp -R vexpress-firmware/* /media/VEMSD - -Once you have finished copying the firmware over: - -* Safely unmount the Versatile Express motherboard -* Reboot the Versatile Express board -* At the ARM Boot Loader "Cmd> " prompt, type the following commands: - -bc. Cmd> flash -Cmd> eraseall -Cmd> exit -Cmd> reboot - -* You may need to configure UEFI to boot from the image that you've created. See the "UEFI page":https://wiki.linaro.org/ARM/UEFI#Configure_UEFI on the Linaro Wiki for more details on configuring UEFI. -* You may want to set /media/VEMSD/config.txt AUTORUN to TRUE to be make the CoreTile boot from power on. -* For TC2, you should set the DIP swich closest to the black reset button down so that the Boot Monitor runs the boot script on power on. -* "Versatile Express version 5.2":https://silver.arm.com/browse/VE052 contains the original firmware and documentation for the Versatile Express platform -* Please contact "support@arm.com":mailto:support@arm.com for any issues related their firmware -* Please "contact Linaro":http://www.linaro.org/engineering/getting-started/discuss for any issues related to booting this release on the Versatile Express platform. - -<br> - -h2. Using TC2 as an A7-only or A15-only board - -h3. Configure the Firmware - -It is possible to configure a TC2 development board as an A7 or A15 only board. To do this, the developer should modify the /SITE1/HBI0249A/board.txt file on the Versatile Express firmware drive, usually mounted at /media/VEMSD. - -The relevant register is CFGREG6 on pages 78-81 of the following TRM: -"http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503e/DDI0503E_v2p_ca15_a7_tc2_trm.pdf":http://infocenter.arm.com/help/topic/com.arm.doc.ddi0503e/DDI0503E_v2p_ca15_a7_tc2_trm.pdf - -You should add the following setting in board.txt: - -bc. SCC: 0x018 0x1FFFFFFF ; CFGRW6 - Reset register default (both clusters active) - - - or - - -bc. SCC: 0x018 0x00001FFF ; CFGRW6 - A15-only config - - - or - - -bc. SCC: 0x018 0x1FFFF000 ; CFGRW6 - A7-only config - -Remember to update TOTALSCCS, eg, if it was 32 and you've added one register, it becomes 33: - -bc. TOTALSCCS: 33 ;Total Number of SCC registers - -h3. Configure the Device Tree - -Once the hardware is booting as an A7 or A15 only board, next you need to remove the unused CPU nodes from the device tree. - -In the kernel source tree, edit arch/arm/boot/dts/vexpress-v2p-ca15_a7.dts and remove the unused CPUs from this section: - -bc. cpus { - #address-cells = <1>; - #size-cells = <0>; - -bc. cpu2: cpu@2 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x100>; - cluster = <&cluster1>; - core = <&core2>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu3: cpu@3 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x101>; - cluster = <&cluster1>; - core = <&core3>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu4: cpu@4 { - device_type = "cpu"; - compatible = "arm,cortex-a7"; - reg = <0x102>; - cluster = <&cluster1>; - core = <&core4>; - clock-frequency = <800000000>; - cci-control-port = <&cci_control2>; - }; - -bc. cpu0: cpu@0 { - device_type = "cpu"; - compatible = "arm,cortex-a15"; - reg = <0>; - cluster = <&cluster0>; - core = <&core0>; - clock-frequency = <1000000000>; - cci-control-port = <&cci_control1>; - }; - -bc. cpu1: cpu@1 { - device_type = "cpu"; - compatible = "arm,cortex-a15"; - reg = <1>; - cluster = <&cluster0>; - core = <&core1>; - clock-frequency = <1000000000>; - cci-control-port = <&cci_control1>; - }; - }; - -Next, you need to remove the GIC entries that are associated with the removed CPUs, eg: - -bc. gic: interrupt-controller@2c001000 { - compatible = "arm,cortex-a15-gic", "arm,cortex-a9-gic"; - #interrupt-cells = <3>; - #address-cells = <0>; - interrupt-controller; - reg = <0 0x2c001000 0 0x1000>, - <0 0x2c002000 0 0x1000>, - <0 0x2c004000 0 0x2000>, - <0 0x2c006000 0 0x2000>; - interrupts = <1 9 0xf04>; - -bc. gic-cpuif@0 { - compatible = "arm,gic-cpuif"; - cpuif-id = <0>; - cpu = <&cpu0>; - }; - -bc. gic-cpuif@1 { - compatible = "arm,gic-cpuif"; - cpuif-id = <1>; - cpu = <&cpu1>; - }; - -bc. gic-cpuif@2 { - compatible = "arm,gic-cpuif"; - cpuif-id = <2>; - cpu = <&cpu2>; - }; - -bc. gic-cpuif@3 { - compatible = "arm,gic-cpuif"; - cpuif-id = <3>; - cpu = <&cpu3>; - }; - -bc. gic-cpuif@4 { - compatible = "arm,gic-cpuif"; - cpuif-id = <4>; - cpu = <&cpu4>; - }; - }; - - -Finally, you need to re-compile the DTS file and copy it to the SD card used to boot the system, eg: - -bc. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs -cp arch/arm/boot/dts/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb - diff --git a/openembedded/vexpress-lsk/HACKING.textile b/openembedded/vexpress-lsk/HACKING.textile deleted file mode 100644 index fd3e813..0000000 --- a/openembedded/vexpress-lsk/HACKING.textile +++ /dev/null @@ -1,63 +0,0 @@ -OpenEmbedded images are comprised of a Hardware Pack ("HWPack":https://wiki.linaro.org/HardwarePacks) and a root file system. The hardware pack contains the kernel, boot loader and Device Tree blobs (if applicable). There is no need to rebuild the RootFS since it is comprised of a large number of debian packages. Instead, the best approach is to use an image, which you can create as outlined in the "Binary Image Installation" tab then replace the kernel with your compiled one. This is common practice that many engineers deploy when wanting a standard Linux image to use for testing and development purposes. - -The following instructions will walk you through how to obtain the kernel source, build it, and add it to a pre-existing image. - -h2. Prerequisites - -* Ubuntu 12.04 64 bit system. You can download Ubuntu from "ubuntu.com":http://www.ubuntu.com -* git and toolchain. You can get those by typing the following command in your terminal - -bc. sudo apt-get install build-essential git gcc-arm-linux-gnueabi - -h2. Get the source - -You can use GIT to obtain the kernel source code for this release: - -bc. git clone git://git.linaro.org/kernel/linux-linaro-stable.git -cd linux-linaro-stable -git checkout lsk-vexpress-14.06 - -h3. Create a kernel config - -Do not use the defconfig for Versatile Express, instead, build a config from the config fragments that Linaro provides: - -bc. ARCH=arm scripts/kconfig/merge_config.sh \ -linaro/configs/linaro-base.conf \ -linaro/configs/distribution.conf \ -linaro/configs/vexpress.conf - -Note: the config fragments are part of the git repository and the source tarball. - -h3. Build the kernel - -To build the kernel uImage, use the following command: - -bc. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- LOADADDR=0x60008000 uImage - -h2. Install 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 so there is no need for a device tree blob): - -bc. make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- dtbs - -* Insert the SD card containing the Linaro disk image into your PC SD card reader - -* Copy the kernel onto the memory card using - -bc. cp arch/arm/boot/uImage /media/boot/ - -* Copy the device tree blob -** For A9 CoreTile: no device tree blob is needed -** For A5 CoreTile: @cp arch/arm/boot/dts/vexpress-v2p-ca5s.dtb /media/boot/v2p-ca5s.dtb@ -** For A15 CoreTile (TC1): @cp arch/arm/boot/dts/vexpress-v2p-ca15-tc1.dtb /media/boot/v2p-ca15-tc1.dtb@ -** For A15_A7 CoreTile (TC2): @cp arch/arm/boot/dts/vexpress-v2p-ca15_a7.dtb /media/boot/v2p-ca15-tc2.dtb@ - -* Eject the memory card from your PC by using the following command - -bc. eject /media/boot - -* Insert the memory card into the Versatile Express board and power it on - -* You should boot your image using your own compiled kernel diff --git a/openembedded/vexpress-lsk/INSTALL.textile b/openembedded/vexpress-lsk/INSTALL.textile deleted file mode 100644 index 9be7300..0000000 --- a/openembedded/vexpress-lsk/INSTALL.textile +++ /dev/null @@ -1,86 +0,0 @@ -Linaro OpenEmbedded images are made up of two components. The "Hardware Pack":https://wiki.linaro.org/HardwarePacks, which contains the kernel, boot loader and/or Device Tree blob and a Root file system (RootFS) of your choice to generate an image. - -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 Versatile Express board has the latest firmware and boot loader installed. Please check the "Firmware Update" tab on this page for the latest updates and installation instructions. - -h2. Using pre-built image - -h3. Prerequisites - -* Ubuntu 12.04 64 bit or newer on your desktop PC ("www.ubuntu.com":http://www.ubuntu.com) -* 4GB SD card or larger -* Latest firmware installed onto the Versatile Express. Please see "Firmware Update" tab -* Download the pre-built image for this release -bc. wget http://releases.linaro.org/14.06/openembedded/vexpress-lsk/lsk-vexpress-openembedded_alip-armv7a-gcc-4.8_20140621-667.img.gz - -h3. Installation Steps - -* Unzip the downloaded pre-built image -* Insert SD card into your PC and note the assigned @'/dev/sdX'@ - -bc. dmesg -SDCARD=/dev/sdX # sdcard found from dmesg above -zcat http://releases.linaro.org/14.06/openembedded/vexpress-lsk/lsk-vexpress-openembedded_alip-armv7a-gcc-4.8_20140621-667.img.gz | sudo dd bs=64k of=$SDCARD - -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 a Versatile Express. 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 ("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/openembedded/vexpress-lsk/hwpack_linaro-lsk-vexpress_20140621-667_armhf_supported.tar.gz -wget http://releases.linaro.org/14.06/openembedded/vexpress-lsk/linaro-image-alip-genericarmv7a-20140612-267.rootfs.tar.gz - -* 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.03/components/platform/linaro-image-tools/linaro-image-tools-2014.03.tar.gz - -* Insert SD card 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. sudo linaro-media-create --mmc /dev/sdX --dev vexpress --hwpack hwpack_linaro-lsk-vexpress_20140621-667_armhf_supported.tar.gz --binary linaro-image-alip-genericarmv7a-20140612-267.rootfs.tar.gz - -h2. Booting the image - -After the media create tool has finished executing, remove the SD card from your PC and insert it into the Versatile Express board. - -Before you can boot the image you will need to install the UEFI boot loader into NOR flash and update the Versatile Express motherboard's configuration files. The instructions on the Firmware Update tab provide information on how to do this and how to configure UEFI to specify the SD card as a boot device. - diff --git a/openembedded/vexpress-lsk/README.textile b/openembedded/vexpress-lsk/README.textile deleted file mode 100644 index 711db75..0000000 --- a/openembedded/vexpress-lsk/README.textile +++ /dev/null @@ -1,190 +0,0 @@ -h1. Linaro Stable Kernel (LSK) 14.06 Release for Versatile Express (OpenEmbedded) - -p. The Linaro Stable Kernel (LSK) is produced, validated and released by Linaro and is based on the linux stable kernel tree. It is produced to satisfy the requirements of Linaro members. The LSK focuses on quality and stability and is therefore a great basis for member products. It also includes backports of commonly desired features, provided they meet the quality requirements, and also any bug fixes. - -p. Linaro releases monthly binary images for the ARM "Versatile Express":http://www.arm.com/products/tools/development-boards/versatile-express/index.php including support for Cortex-A9, Cortex-A5, TC2 (big.LITTLE) CoreTiles and Fast Models. - -p. For support matters related to ARM hardware or firmware images downloaded from ARM sites, please contact "ARM support":mailto:support@arm.com - -p. This release includes Linaro OpenEmbedded for both Versatile Express and Fast Models. The images are able to boot A5, A9 and TC2 using UEFI. Sources are also made available so you can build your own images (see the "'Building from Source'":https://releases.linaro.org/14.06/openembedded/vexpress-lsk/#tabs-3 tab). - -h2. About the TC2 Engineering Build - -This release is based on the Linux v3.10.44 kernel. As a consequence, almost all of the patches in the ARM Landing Team tree have been rebased and refactored to account for the latest upstream content. - -The TC2 CoreTile is the first example of a big.LITTLE system shipped by ARM and serves as a platform for development and test of big.LITTLE software. TC2 contains a tri-core Cortex-A7 cluster and a dual-core Cortex-A15 cluster linked using the CCI-400 coherent interconnect. - -The release contains the big.LITTLE MP patchset developed by ARM. This patchset is hosted by Linaro and can be found in the linked "git repository":https://git.linaro.org/gitweb?p=arm/big.LITTLE/mp.git;a=shortlog;h=refs/heads/big-LITTLE-MP-latest. These patches have been developed and rigorously tested in order to enable the ARM Versatile Express V2P-CA15_A7 CoreTile (TC2) to run in full MP mode. This functionality has been optimised for energy and performance bringing it close to the Cortex-A7 (LITTLE) in energy consumption with near Cortex-A15 (big) performance. The patchset also includes optimizations that provide a considerable performance uplift across a wide range of benchmarks. The functionality introduced by this patchset is stable and ready for use on other platforms. Note that at present this LSK release is the reference point for big.LITTLE MP functionality. - -The patches in the big.LITTLE MP patchset are generic and applicable to big.LITTLE systems with minimal porting effort. To ease porting, the patches are also available as an isolated package located "here":https://wiki.linaro.org/ARM/VersatileExpress?action=AttachFile&do=get&target=big-LITTLE-MP-scheduler-patchset-14.06-lsk.tar.bz2. This package may be used directly by partners interested in porting the big.LITTLE MP scheduler functionality to their custom platform. Please contact "ARM support":mailto:support-sw@arm.com?subject=Query%20about%20ARM%20big.LITTLE%20MP%20patchset%20package in case of any queries related to this package. - -Also provided is optional configurable kernel support for an implementation of ARM's Power State Co-ordination Interface (PSCI). This support is disabled by default. To use PSCI support you will require secure firmware that is currently available to ARM licensees upon request to ARM. Please contact "ARM support":mailto:support-sw@arm.com?subject=Access%20to%20PSCI to get access to the firmware code. - -The 'small task packing feature' continues to be enabled by default in the kernel configuration. (See the documentation for this feature located at 'Documentation/arm/small_task_packing.txt’ within the kernel sources for more information on this feature). - -This release introduces further optimizations for the existing 'idle pull task migration' feature. These optimizations promote forward progress of tasks even if the target processor is currently idle. In addition, the release also contains some cleanups - see the patches marked 'New in this release' in the list below for details. - -h3. Scheduler modifications to support big.LITTLE - -The following patches make up the big.LITTLE MP patchset. - -| "sched: implement usage tracking":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0841c6ae0b53d43e4634cf4a1f88407b93c15399 | | -| "sched: entity load-tracking load_avg_ratio":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=be6ef1d56e70bfdfd79174d7d23a4b12d5b911ee | | -| "sched: Task placement for heterogeneous systems based on task load-tracking":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=798e82cab1a39f4d75796be024c4d7b08bc062e8 | | -| "sched: Forced task migration on heterogeneous systems":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2dd22b22c95851445c189c3d4708c027aa19cf5f | | -| "sched: Introduce priority-based task migration filter":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=943106d9437fcced79c4e48ed794410e5f750b4c | | -| "ARM: Add HMP scheduling support for ARM architecture":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d278bb1c4d5191e0d9b9911337e3b31a100a7f9f | | -| "ARM: sched: Use device-tree to provide fast/slow CPU list for HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=dc68bd92107d8990f4608d8f42744770fe203f7f | | -| "ARM: sched: Setup SCHED_HMP domains":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=1baaccf456ece33b8fa02f8cdf3977d6a95b393c | | -| "sched: Add ftrace events for entity load-tracking":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=b9d3d5612899de4f8372ecfbc4c8f4ba5aa170ec | | -| "sched: Add HMP task migration ftrace event":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0d811e649ad31994e8f06b6b18101f249b34e912 | | -| "sched: SCHED_HMP multi-domain task migration control":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=76525733b4f4e0fdcc188dfe23941024ae626979 | | -| "sched: Enable HMP priority filter by default":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=1b8ae251638844173bd04a4c9e543581f3d92fbd | | -| "ARM: sched: Avoid empty 'slow' HMP domain":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=362036513b1dff299b2035d5b928a203742b98d7 | | -| "sched: Only down migrate low priority tasks if allowed by affinity mask":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=eeebbf595c8dcd6392537c4d13b8cda78001f4e5 | | -| "sched: fix arch_get_fast_and_slow_cpus to get logical cpumask correctly":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=a9f9bca843e44144670c660638274363f34b9847 | | -| "sched: Do not ignore grouped tasks during HMP forced migration.":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d2c920023cbc456414f8e07ff253a89be535b41b | | -| "sched: Ignore offline CPUs in HMP migration & load stats":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=b64cc6f7e54b97536dbecc05d193b31b27feecf1 | | -| "ARM: Change load tracking scale using sysfs":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0e48eed05c47aa2e00b772a519b36286e466621e | | -| "ARM: Experimental Frequency-Invariant Load Scaling Patch":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=71b5dbd6d527d5de8aaef7e1f8658df95caf28aa | | -| "ARM: Fix build breakage when big.LITTLE.conf is not used.":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=ae570aeb1d40d531a498e53e2a815a52996f0749 | | -| "sched: Basic global balancing support for HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=cf71912f481c7b6fc39e9b2021e8f9c058116c26 | | -| "sched: cfs.nr_running does not contain the intended metric":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7e6446630039fcbabb9582ebefdcbc30de32c0e2 | | -| "Revert sched: Enable HMP priority filter by default":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7362251d8a422dcba5c56408b92fc2b6ad03b10c | | -| "HMP: Use unweighted load for hmp migration decisions":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=ede58a69a32b187899e6cccbbd299a04d3f50b71 | | -| "HMP: Select least-loaded CPU when performing HMP Migrations":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=08d7db89a214a138516419a85e17272b09180abd | | -| "HMP: Avoid multiple calls to hmp_domain_min_load in fast path":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=3f3b210703f80fe60dbfa13c25b30d4effbf9f4b | | -| "HMP: Force new non-kernel tasks onto big CPUs until load stabilises":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=954978dd2cff81cc15745b9e581a1709e238f8ef | | -| "sched: Restrict nohz balance kicks to stay in the HMP domain":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=6eada0087366d8aec6bc38348a68f721f538cc5c | | -| "HMP: experimental: Force all rt tasks to start on little domain":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=4ab2679351e9566a6b0822f2d841a902758ba066 | | -| "HMP: select 'best' task for migration rather than 'current'":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=ee52487aaf659ef630ce3371de0e59944253581b | | -| "sched: HMP fix traversing the rb-tree from the curr pointer":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=aaba2453951b3743d003be228102e1da63c75326 | | -| "sched: track per-rq 'last migration time'":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=5fad81c7739db3a1fc6380dcc3d7902666ed5ee8 | | -| "HMP: Modify the runqueue stats to add a new child stat":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=b98cd6acc86f2c3bc10902476836746727b73ba9 | | -| "HMP: Explicitly implement all-load-is-max-load policy for HMP targets":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=6b695bd8a4e2c86cc466010517c0260dc3653742 | | -| "sched: HMP change nr_running offload metric":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=1f435579ea80d4639061435d8337df5a2c92e530 | | -| "HMP: Implement idle pull for HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=db20b7088c6d7f7920dace95c7fc8d9955650214 | | -| "HMP: Access runqueue task clocks directly.":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=de66e01565848d0236ca9e7e9e2f6ecd5c27a021 | | -| "HMP: Update migration timer when we fork-migrate":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=18e3c3d2cc1346cb7cc2e3fd777b2c6f4fbb6135 | | -| "sched: HMP: Change default HMP thresholds":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d73babce9a77f8143136fe0d7b6c1ae44b5652dc | | -| "sched: HMP: Additional trace points for debugging HMP":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7b8e0b3f2af55b1ffb5c10be1daa59d8dc21d140 | | -| "arm: ipi raise/start/end tracing":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2353c1f8009c14e89b323b18ae246c485fc034e4 | | -| "smp: smp_cross_call function pointer tracing":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=5ecaba3d9f4ab514fe8d383534e24b306f116896 | | -| "sched: HMP: fix potential logical errors":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2e14ecb254a3eaa2993b5dd04014f41e1d6188ce | | -| "hmp: Remove potential for task_struct access race":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=cd5c2cc93d3dc581a19c62442f40895500d2a34c | | -| "HMP: Implement task packing for small tasks in HMP":http://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=d8063e7015122eb3f6173acf496171def8941734 | | -| "HMP: Avoid using the cpu stopper to stop runnable tasks":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=2a68d1e9125582bedeac4ea34fb9901ab1f7de11 | | -| "sched: hmp: add read-only hmp domain sysfs file":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=0b877c2baac65994016c6812804d1b30e89c18ed | | -| "Documentation: HMP: Small Task Packing explanation":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=f5be72980bc321f3491377861835c343cc27af0d | | -| "sched: hmp: Fix build breakage when not using CONFIG_SCHED_HMP":https://git.linaro.org/gitweb?p=kernel/linux-linaro-stable.git;a=commit;h=7cf6a7300bb9a88f543061270419427395ab4d2f | | -| "sched: reset blocked load decay_count during synchronization":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/f720a920e88f1ec79db8c9f0031f61c610e40b02 | | -| "sched: update runqueue clock before migrations away":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/7896b1e659db571556436b99ebb2e475e54a24f5 | | -| "sched: hmp: Make idle balance behaviour normal when packing disabled":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/257e5075a1433513bb354f202adcd2dea8a8dc08 | | -| "sched: hmp: Change TC2 packing config to disabled default if present":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/ba8ed8301f5bca4a44c80e2173c66391b76898df | | -| "config: Make packing present on TC2":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/5e0791511a938eaf28d9071b411ffa71a79ef8ed | | -| "sched: hmp: Fix potential task_struct memory leak":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/b2fafaba35f490947b78e8d0d4f4264a137e64cd | | -| "HMP: Restrict irq_default_affinity to hmp_slow_cpu_mask":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/1d462599bee9a2f5f3988aafa43feda602d5e188 | | -| "HMP: Fix rt task allowed cpu mask restriction code on 1x1 system":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/b30814c74c184bbb231e24d6c857699af338468b | | -| "hmp: sched: Clean up hmp_up_threshold checks into a utility fn":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/765aae2 | | -| "sched: hmp: unify active migration code":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/0baa581 | | -| "hmp: Use idle pull to perform forced up-migrations":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/aae7721 | | -| "hmp: dont attempt to pull tasks if affinity doesn't allow it":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/5a570cf | | -| "Revert hmp: dont attempt to pull tasks if affinity doesn't allow it":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/8503bfd | | -| "Revert hmp: Use idle pull to perform forced up-migrations":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/7e1f7d3 | | -| "Revert sched: hmp: unify active migration code":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/11971ff | | -| "Revert hmp: sched: Clean up hmp_up_threshold checks into a utility fn":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/db3dba6 | | -| "sched: hmp: Change small task packing defaults for all platforms":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/1ade57e | | -| "hmp: sched: Clean up hmp_up_threshold checks into a utility fn":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/84efcd0 | | -| "sched: hmp: unify active migration code":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/0168997 | | -| "hmp: Use idle pull to perform forced up-migrations":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/940407d | | -| "hmp: dont attempt to pull tasks if affinity doesn't allow it":https://git.linaro.org/kernel/linux-linaro-stable.git/commit/d1df056 | | - -h3. Platform Support. - -In addition to the big.LITTLE MP work the TC2 platform support includes: -** TC2: reset CPUs spuriously woken up on cluster power up -** vexpress: add shim layer for psci backend on TC2 -** vexpress: allow native pm ops backends to probe for psci suppport -** psci: add cmdline option to enable use of psci -** psci: add probe function to discover presence of a psci implementation -** psci: convert psci '-EALREADYON' error code to linux '-EAGAIN' -** vexpress: add psci support in TC2 device tree -** psci: add constants to specify affinity levels -** TC2: replace hard coded cluster and cpu values with constants -** TC2: use generic accessors to extract cpu and cluster ids -** CPUidle & CPUfreq support -** hwmon driver allowing, amongst other things, TC2's power, current and energy measurements to be read through standard sysfs interfaces -** Common clocks implementation -** Regulator driver -** Drivers for previously hard-coded configuration interfaces -** Support self-hosted debugging through idle -** In addition to the CPU PMUs the perf framework supports the CCI-400 PMUs -** A patch from Thomas Gliexner which supports a IRQ affinity mask being specified in the command line. This can be used to reduce unnecessary IRQ wakeups on Cortex-A15. For instructions see the irqaffinity entry in Documentation/kernel-parameters.txt -** arm-multi_pmu_v2 - enables the use of multiple PMU types or sources, for example profiling across both Cortex-A15 and Cortex-A7 clusters and getting results for CCI. - -h2. Where To Find More Information - -More information on Linaro can be found on our "website.":http://www.linaro.org/ - -h2. Feedback and Support - -Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. - -** Linaro Development "mailing list":http://lists.linaro.org/mailman/listinfo/linaro-dev -** Linaro IRC channel on irc.freenode.net at @#linaro@ - -* Landing Team bug reports should be filed in "JIRA":http://cards.linaro.org/browse/ARM#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel by clicking on the "Create issue" button on the top menu bar. -** You will need to login to your JIRA account. If you do not have an account or are having problems, email its@linaro.org for help. -* More general bug reports should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to "Linaro project":http://bugs.launchpad.net/linaro/+filebug. -* Questions? "ask Linaro":http://ask.linaro.org/. -* Interested in commercial support? inquire at "Linaro support":mailto:support@linaro.org - -h2. Resolved in this release - -* "ARM-46":http://cards.linaro.org/browse/ARM-46 Booting using UEFI with bootmon from VE CD 5.2 fails -* "ARM-53":http://cards.linaro.org/browse/ARM-53 Watchdog timeout booting Android on single core fastmodels -* "ARM-58":http://cards.linaro.org/browse/ARM-58 LP:1231468 - HTML5 video playback failed, using Chromium but works with Firefox, on ARM Versatile Express ALIP image -* "ARM-60":http://cards.linaro.org/browse/ARM-60 LP:1254750 - Browser crashes regularly on vexpress with KitKat - -h2. Known Issues - -h3. General Issues - -* "ARM-16":http://cards.linaro.org/browse/ARM-16 LP:1097309 - serial console doesn't received characters on TC2 -* "ARM-24":http://cards.linaro.org/browse/ARM-24 LP:1172350 - Audio playback under Android JellyBean stops sporadically on TC2 with release 13.03 -* "ARM-50":http://cards.linaro.org/browse/ARM-50 LP:1217893 - perf shows zero for cycle and instruction counts on TC2 -* "ARM-57":http://cards.linaro.org/browse/ARM-57 LP:1243194 - power top doesn't show any stats -* "ARM-61":http://cards.linaro.org/browse/ARM-61 LP:1254738 - Serial console doesn't work reliably on vexpress with KitKat -* "ARM-77":http://cards.linaro.org/browse/ARM-77 LP:1260320 - long running gator and DS-5 streaming capture reported kernel crash dump -* "ARM-132":https://cards.linaro.org/browse/ARM-132 14.05 LSK pre-release validation shows degradation in BBench scores -* "ARM-137":https://cards.linaro.org/browse/ARM-137 HMP Patch 77 missing from 14.06 release - -h3. Known Issues due to lack of video acceleration - -* "ARM-59":http://cards.linaro.org/browse/ARM-59 LP:987155 - vexpress: Angrybirds display severely truncated -* "LP: #987172":http://launchpad.net/bugs/987172 vexpress: YouTube video playback fails - -h3. Known Issues due to generic Android features - -* "ARM-51":http://cards.linaro.org/browse/ARM-51 Gallery app crashes on start on vexpress Android 4.3 -* "ARM-101":https://cards.linaro.org/browse/ARM-101 LP: 1229185 - Panic in ip6tables during Android boot - -h3. Additional information - -NOTE: When using the interactive governor with Android, take care to use the following values for governor specific tunables. These values have been selected after careful analysis on this LSK version and result in optimal power-performance on TC2. In future LSK releases, additional system initialisation logic will use these values as defaults. - -Interactive settings for the Cortex-A7 cluster: - -'above_hispeed_delay': 20000 -'go_hispeed_load': 85 -'hispeed_freq': 800000 -'min_sample_time': 80000 -'timer_rate': 20000 - -Interactive settings for the Cortex-A15 cluster: - -'above_hispeed_delay': 20000 -'go_hispeed_load': 85 -'hispeed_freq': 1000000 -'min_sample_time': 80000 -'timer_rate': 20000 |