diff options
| author | Ryan Harkin <ryan.harkin@linaro.org> | 2014-07-08 12:42:47 +0100 |
|---|---|---|
| committer | Ryan Harkin <ryan.harkin@linaro.org> | 2014-07-08 14:32:35 +0100 |
| commit | 2a5e6392416dfcfb5c65e1e99074d1b88bbb501c (patch) | |
| tree | c22616838af95d0e8d5b881e015881f63fc1c6fd | |
| parent | 394c677195f1be548751319d0b1b07b81e2e08a5 (diff) | |
14.07: trim OE Juno release note
Signed-off-by: Ryan Harkin <ryan.harkin@linaro.org>
| -rw-r--r-- | openembedded/juno-lsk/GETTINGSTARTED.textile | 206 | ||||
| -rw-r--r-- | openembedded/juno-lsk/HACKING.textile | 249 | ||||
| -rw-r--r-- | openembedded/juno-lsk/INSTALL.textile | 362 | ||||
| -rw-r--r-- | openembedded/juno-lsk/README.textile | 99 |
4 files changed, 19 insertions, 897 deletions
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 index e5d60c0..4015f72 100644 --- a/openembedded/juno-lsk/HACKING.textile +++ b/openembedded/juno-lsk/HACKING.textile @@ -7,22 +7,12 @@ 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 +* "13.11 Linaro aarch64 Linux GNU 4.8 toolchain":http://releases.linaro.org/13.11/components/toolchain/binaries/gcc-linaro-aarch64-linux-gnu-4.8-2013.11_linux.tar.xz h3. Get the Linaro Kernel Source bc. git clone https://git.linaro.org/landing-teams/working/arm/kernel-release.git -cd kernel +cd kernel-release git checkout lsk-3.10-armlt-juno-20140616 h3. Create a kernel config @@ -45,238 +35,3 @@ 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 index bef8631..8a08fd8 100644 --- a/openembedded/juno-lsk/INSTALL.textile +++ b/openembedded/juno-lsk/INSTALL.textile @@ -4,368 +4,32 @@ The use of Juno software is subject to the terms of the Juno "End User License A 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 +h3. Pre-Installation Steps * Ubuntu 12.04 64 bit or newer on your desktop PC ("www.ubuntu.com":http://www.ubuntu.com) +* Before any installation begins, it is important that you ensure your board has the latest firmware installed +** See the Juno Firmware wiki for more details: +** "https://wiki.linaro.org/ARM/Juno/Firmware":https://wiki.linaro.org/ARM/Juno/Firmware * 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: +* Choose either to use a pre-built image or to build a custom image by following the steps below -bc. $ sync -$ sudo eject $DRIVE +h3. Using pre-built image -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. +* Unzip the downloaded pre-built image and write it to a USB drive +* Safely remove the USB drive and insert it into the board -Once you are ready, run the following commands: +h3. Building a custom image using pre-built components -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. - +* Get "Linaro image tools":https://wiki.linaro.org/Linaro-Image-Tools * 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. +h3. Post-installation steps +* Safely remove the USB drive and insert it into the board +* "Configure UEFI":https://wiki.linaro.org/ARM/UEFI for your new USB drive -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 index 2f6055a..b7fff18 100644 --- a/openembedded/juno-lsk/README.textile +++ b/openembedded/juno-lsk/README.textile @@ -1,101 +1,10 @@ +h2. Linaro OpenEmbedded Engineering Build for Juno -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 +h3. 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> | +h3. Known Issues +Known Issues are managed in "Bugzilla":https://bugs.linaro.org |