ARM Juno ARM User manual

Juno ARM Development Platform
Version: 2.0
Getting Started Guide
Copyright © 2015 ARM. All rights reserved.
ARM DEN0928F

Juno ARM Development Platform
Getting Started Guide
Copyright © 2015 ARM. All rights reserved.
Release Information
Document History
Issue Date Confidentiality Change
A 02 July 2015 Non-Confidential First release
B 29 July 2015 Non-Confidential Second release
C 11 August 2015 Non-Confidential Third release
D 17 September 2015 Non-Confidential Fourth release
E 15 October 2015 Non-Confidential Fifth release
F 22 December 2015 Non-Confidential Sixth release
Non-Confidential Proprietary Notice
This document is protected by copyright and other related rights and the practice or implementation of the information contained in
this document may be protected by one or more patents or pending patent applications. No part of this document may be
reproduced in any form by any means without the express prior written permission of ARM. No license, express or implied, by
estoppel or otherwise to any intellectual property rights is granted by this document unless specifically stated.
Your access to the information in this document is conditional upon your acceptance that you will not use or permit others to use
the information for the purposes of determining whether implementations infringe any third party patents.
THIS DOCUMENT IS PROVIDED “AS IS”. ARM PROVIDES NO REPRESENTATIONS AND NO WARRANTIES,
EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, SATISFACTORY QUALITY, NON-INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE
WITH RESPECT TO THE DOCUMENT. For the avoidance of doubt, ARM makes no representation with respect to, and has
undertaken no analysis to identify or understand the scope and content of, third party patents, copyrights, trade secrets, or other
rights.
This document may include technical inaccuracies or typographical errors.
TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL ARM BE LIABLE FOR ANY DAMAGES,
INCLUDING WITHOUT LIMITATION ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE, OR
CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING
OUT OF ANY USE OF THIS DOCUMENT, EVEN IF ARM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
This document consists solely of commercial items. You shall be responsible for ensuring that any use, duplication or disclosure of
this document complies fully with any relevant export laws and regulations to assure that this document or any portion thereof is
not exported, directly or indirectly, in violation of such export laws. Use of the word “partner” in reference to ARM’s customers is
not intended to create or refer to any partnership relationship with any other company. ARM may make changes to this document at
any time and without notice.
If any of the provisions contained in these terms conflict with any of the provisions of any signed written agreement covering this
document with ARM, then the signed written agreement prevails over and supersedes the conflicting provisions of these terms.
This document may be translated into other languages for convenience, and you agree that if there is any conflict between the
English version of this document and any translation, the terms of the English version of the Agreement shall prevail.
Words and logos marked with ® or ™ are registered trademarks or trademarks of ARM Limited or its affiliates in the EU and/or
elsewhere. All rights reserved. Other brands and names mentioned in this document may be the trademarks of their respective
owners. Please follow ARM’s trademark usage guidelines at http://www.arm.com/about/trademark-usage-guidelines.php
Copyright © [2015], ARM Limited or its affiliates. All rights reserved.
ARM Limited. Company 02557590 registered in England.
Juno ARM Development Platform
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 2
Non-Confidential

110 Fulbourn Road, Cambridge, England CB1 9NJ.
LES-PRE-20349
Confidentiality Status
This document is Non-Confidential. The right to use, copy and disclose this document may be subject to license restrictions in
accordance with the terms of the agreement entered into by ARM and the party that ARM delivered this document to.
Unrestricted Access is an ARM internal classification.
Product Status
The information in this document is Final, that is for a developed product.
Web Address
http://www.arm.com
Conformance Notices
Federal Communications Commission Notice
This device is test equipment and consequently is exempt from part 15 of the FCC Rules under section 15.103 (c).
CE Declaration of Conformity
The system should be powered down when not in use.
It is recommended that ESD precautions be taken when handling Versatile™ Express boards.
The motherboard generates, uses, and can radiate radio frequency energy and may cause harmful interference to radio
communications. There is no guarantee that interference will not occur in a particular installation. If this equipment causes harmful
interference to radio or television reception, which can be determined by turning the equipment off or on, you are encouraged to try
to correct the interference by one or more of the following measures:
• Ensure attached cables do not lie across the target board
• Reorient the receiving antenna
• Increase the distance between the equipment and the receiver
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected
• Consult the dealer or an experienced radio/TV technician for help
Note
It is recommended that wherever possible shielded interface cables be used.
Juno ARM Development Platform
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 3
Non-Confidential

Contents
Juno ARM Development Platform Getting Started
Guide
Preface
About this book ...................................................... ...................................................... 7
Feedback ...................................................................................................................... 9
Chapter 1 Introduction
1.1 About the Juno ADP ................................................................................................ 1-11
1.2 Ports and I/O ..................................................... ..................................................... 1-12
1.3 Use of Ethernet ports ............................................... ............................................... 1-13
1.4 UART configuration ................................................ ................................................ 1-14
1.5 Monitor compatibility ................................................................................................ 1-15
Chapter 2 Configuration
2.1 Connecting to a host computer ................................................................................ 2-17
2.2 SD card filesystem layout ........................................................................................ 2-18
2.3 Flash memory programming .................................................................................... 2-19
2.4 Erasing the flash memory ........................................................................................ 2-21
2.5 Board recovery procedure ........................................... ........................................... 2-22
2.6 Juno SoC configuration ............................................. ............................................. 2-23
2.7 Linux filesystems .................................................. .................................................. 2-24
Chapter 3 Firmware
3.1 Firmware components .............................................. .............................................. 3-26
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 4
Non-Confidential

3.2 System Control Processor (SCP) firmware .............................. .............................. 3-27
3.3 Application Processor (AP) firmware ................................... ................................... 3-28
Appendix A Revisions
A.1 Revisions ................................................... ................................................... Appx-A-30
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 5
Non-Confidential

Preface
This preface introduces the Juno ARM Development Platform Getting Started Guide.
It contains the following:
•About this book on page 7.
•Feedback on page 9.
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 6
Non-Confidential

About this book
This book describes the Juno ARM® Development Platform (ADP). The Juno ADP is an ARM Versatile™
Express V2M-Juno motherboard containing a Juno ADP SoC and reference software.
Using this book
This book is organized into the following chapters:
Chapter 1 Introduction
This chapter introduces the Juno ARM Development Platform (ADP).
Chapter 2 Configuration
This chapter describes the configuration of the V2M-Juno motherboard.
Chapter 3 Firmware
This chapter describes the firmware that the Juno ADP supports.
Appendix A Revisions
This appendix describes the technical changes between released issues of this book.
Glossary
The ARM Glossary is a list of terms used in ARM documentation, together with definitions for those
terms. The ARM Glossary does not contain terms that are industry standard unless the ARM meaning
differs from the generally accepted meaning.
See the ARM Glossary for more information.
Typographic conventions
italic
Introduces special terminology, denotes cross-references, and citations.
bold
Highlights interface elements, such as menu names. Denotes signal names. Also used for terms
in descriptive lists, where appropriate.
monospace
Denotes text that you can enter at the keyboard, such as commands, file and program names,
and source code.
monospace
Denotes a permitted abbreviation for a command or option. You can enter the underlined text
instead of the full command or option name.
monospace italic
Denotes arguments to monospace text where the argument is to be replaced by a specific value.
monospace bold
Denotes language keywords when used outside example code.
<and>
Encloses replaceable terms for assembler syntax where they appear in code or code fragments.
For example:
MRC p15, 0, <Rd>, <CRn>, <CRm>, <Opcode_2>
SMALL CAPITALS
Used in body text for a few terms that have specific technical meanings, that are defined in the
ARM glossary. For example, IMPLEMENTATION DEFINED, IMPLEMENTATION SPECIFIC, UNKNOWN, and
UNPREDICTABLE.
Additional reading
See http://infocenter.arm.com, for access to ARM documentation.
Preface
About this book
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 7
Non-Confidential

ARM® publications
This book contains information that is specific to this product. See the following documents for
other relevant information:
•Juno ARM® Development Platform (ADP) SoC Technical Reference Manual (ARM DDI
0515).
•Juno ARM® Development Platform SoC Technical Overview (ARM DTO 0038).
•ARM® Compute Subsystem SCP Message Handling Interface (ARM DUI 0922).
•Power State Coordination Interface (PSCI) System Software on ARM® Systems (ARM DEN
0022).
•Trusted Board Boot Requirements CLIENT (TTBR-CLIENT) System Software on ARM
(ARM DEN 0006C-1).
•ARM® Compute Subsystem SCP Message Interface Protocols (ARM DUI 0922).
•ARM® Versatile™ Express Juno r2 Development Platform (V2M-Juno r2) Technical Reference
Manual (100114).
•ARM® Versatile™ Express Juno r1 Development Platform (V2M-Juno r1) Technical Reference
Manual (100122).
•ARM® Versatile™ Express Juno Development Platform (V2M-Juno) Technical Reference
Manual (100113).
•ARM Technical Support Knowledge Articles.
•Support and Maintenance.
Preface
About this book
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 8
Non-Confidential

Feedback
Feedback on this product
If you have any comments or suggestions about this product, contact your supplier and give:
• The product name.
• The product revision or version.
• An explanation with as much information as you can provide. Include symptoms and diagnostic
procedures if appropriate.
Feedback on content
If you have comments on content then send an e-mail to [email protected]. Give:
• The title Juno ARM Development Platform Getting Started Guide.
• The number ARM DEN0928F.
• If applicable, the page number(s) to which your comments refer.
• A concise explanation of your comments.
ARM also welcomes general suggestions for additions and improvements.
Note
ARM tests the PDF only in Adobe Acrobat and Acrobat Reader, and cannot guarantee the quality of the
represented document when used with any other PDF reader.
Preface
Feedback
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 9
Non-Confidential

Chapter 1
Introduction
This chapter introduces the Juno ARM Development Platform (ADP).
It contains the following sections:
•1.1 About the Juno ADP on page 1-11.
•1.2 Ports and I/O on page 1-12.
•1.3 Use of Ethernet ports on page 1-13.
•1.4 UART configuration on page 1-14.
•1.5 Monitor compatibility on page 1-15.
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 1-10
Non-Confidential

1.1 About the Juno ADP
The Juno ADP is a 64-bit software development platform consisting of an ARM Versatile Express V2M-
Juno motherboard containing a Juno ADP SoC and reference software.
The ADP is based around an ARMv8-A Compute Subsystem (CSS) and provides:
•Juno r0 and r1
Dual core Cortex®-A57 MPCore processors (big cluster).
Juno r2
Dual core Cortex-A72 MPCore processors (big cluster).
• Quad core Cortex-A53 MPCore processors (LITTLE cluster).
• A Mali™-T624 series GPU with four shader cores for 3D Graphics acceleration and GPU compute.
• A Cortex M3-based System Control Processor (SCP) which offloads power control and thermal
management.
• 8GB of DDR3-1600 memory (dual channel, striped).
• An architecture that is aligned with Level 1 of the Server Base System Architecture.
• ARM big.LITTLE MP support. On Juno r1 only, the LITTLE cluster is limited to the lowest DVFS
Operating Performance Point (OPP) due to hardware limitations.
Note
The big.LITTLE MP scheduler is not optimized.
The following hardware features are available only on Juno r1 and later:
•Peripheral Component Interconnect Express (PCIe) Gen 2.0 support.
Reference firmware and other software images are available for the Juno ADP from Linaro.
Note
The use of Juno software is subject to the terms of the Juno End-User License Agreement.
External interfaces include:
• Support for LogicTile Express boards that you can use to extend the Juno ADP.
• USB 2.0 and a custom SoC to Field Programmable Gate Array (FPGA) prototyping extension
interface.
The V2M-Juno motherboard is available from ARM. For information, see www.arm.com/juno.
Note
The V2M-Juno motherboard is lead-free. The ARM Connected Community pages also provide
additional information for users of the Juno ADP, including FAQs and instructions on using the Linaro
software deliverables. For more information, see https://community.arm.com/groups/arm-development-
platforms.
1 Introduction
1.1 About the Juno ADP
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 1-11
Non-Confidential

1.2 Ports and I/O
The following figure shows the front panel of the V2M-Juno motherboard.
Figure 1-1 V2M-Juno motherboard front panel
The front Ethernet port is enabled in hardware on all current versions of Juno. It is connected internally
over a Static Memory Bus (SMB). The USB ports exist only on Juno r0.
The following figure shows the rear panel of the V2M-Juno motherboard.
Figure 1-2 V2M-Juno motherboard rear panel
The rear Ethernet port is not enabled in hardware on Juno r0. On Juno r1 and later, it is enabled and
connected over the PCI Express bus.
1 Introduction
1.2 Ports and I/O
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 1-12
Non-Confidential

1.3 Use of Ethernet ports
This section describes the Ethernet ports on the rear panel of the V2M-Juno motherboard.
1.3.1 Boot support
If using Trivial File Transfer Protocol (TFTP) boot with Unified Extensible Firmware Interface (UEFI),
the front Ethernet port must be used.
U-Boot does not contain support for booting over an Ethernet connection.
1.3.2 Port numbering in Linux and Android with UEFI
UEFI is responsible for passing the MAC address of the primary Ethernet port to the kernel using its
command line. UEFI reads this address from the System Configuration and Control (SCC) registers.
Juno r0
The front Ethernet port is numbered eth0. The rear port is not enabled in hardware and therefore
the kernel does not allocate a number.
Juno r1 and later
Using the Linaro tracking kernel with the OpenEmbedded filesystem results in the rear Ethernet
port being numbered eth0. This kernel and filesystem combination does not support the front
Ethernet port without extra configuration.
The Linaro Stable Kernel (LSK) does not support the rear Ethernet port. The front Ethernet port
is therefore numbered eth0.
1.3.3 Port numbering in Linux and Android with U-boot
If U-Boot is used, you must use the ifconfig tool within Linux to set up an Ethernet port as follows:
ifconfig eth0 hw ether [MAC address]
1 Introduction
1.3 Use of Ethernet ports
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 1-13
Non-Confidential

1.4 UART configuration
There are 4 UARTs on the V2M-Juno motherboard. Two (SoC UART0 and SoC UART1) are on the rear
panel, while two are only exposed as headers.
SoC UART0
On the back panel.
Used by the boot firmware, for example the V2M-Juno motherboard, ARM Trusted Firmware,
and UEFI.
It also used by the Operating System, for example, the Linux kernel.
SoC UART1
On the back panel.
Used by the runtime firmware, for example, ARM Trusted Firmware or UEFI.
FGPA UART0
Corresponds to the J55 header on the V2M-Juno motherboard.
Contact ARM for further information about this type of header.
Used by the ARM Trusted Firmware.
FGPA UART1
Corresponds to the J56 header on the V2M-Juno motherboard.
Contact ARM for further information about this type of header.
Used by the SCP Firmware if it is built in debug mode.
1.4.1 Settings
For all UARTs, the settings are:
Baud rate 115200
Data bits 8
Parity bits None
Stop bits 1
Related concepts
1.2 Ports and I/O on page 1-12.
1 Introduction
1.4 UART configuration
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 1-14
Non-Confidential

1.5 Monitor compatibility
There are hardware limitations affecting HDMI support and issues might be encountered when using the
V2M-Juno motherboard with certain monitors.
• On some monitors, the native resolution is not always achieved, and the V2M-Juno motherboard
output degrades to 1024×768. On the next reboot, there is a chance that the native resolution might be
selected.
• For some display modes on some monitors, the display can periodically lose synchronization, causing
a brief picture loss each time this occurs. The ratio of display time to blanking time varies
significantly across monitors and modes.
• On some monitors, the V2M-Juno motherboard is unable to establish a working display mode.
The following table summarizes the results for monitors that ARM has tested.
Table 1-1 Monitor compatibility with the V2M-Juno motherboard
Manufacturer Model Native resolution Native resolution
achieved
Fallback to
1024x768 @
60Hz
achieved
No display
achieved
Success
rate
Blanking
occurs
Success
rate
Blanking
occurs
BenQ GL2460 1920×1080@60Hz 91% Yesa0% n/a 9%
BenQ GL2450 1920×1080@60Hz 100% Yesan/a n/a n/a
BenQ G2200WT 1680×1050@60Hz 100% No n/a n/a n/a
BenQ BL2201 1680×1050@60Hz 100% No n/a n/a n/a
Dell P1911 1440×900@60Hz 100% No n/a n/a n/a
HP L1940T 1280×1024@60Hz 100% No n/a n/a n/a
Iiyama ProLite E511S 1600×1200@60Hz 100% No n/a n/a n/a
LG LED 22M35 1920×1080@60Hz 100% Yesan/a n/a n/a
NEC EA274WMi 2560×[email protected] 100% Yesan/a n/a n/a
NEC LCD2070NX 1600×1200@60Hz 20% No n/a n/a n/a
Samsung SyncMaster
S22B370
1920×1080@60Hz 0% n/a 0% n/a
Samsung SyncMaster
SA850
2560×1440@60Hz 0% n/a 100%bNo n/a
aNo blanking occurs when invoking the kernel with a video command-line option that includes an R flag. For example:
video=HDMI-A-1:1920×1080R@60
bThe Samsung SyncMaster SA850 is available for purchase at the time of writing and works well when using 1024×768 or half of the native resolution, but only if
the following kernel command-line option is provided to force the resolution. ARM recommends adding this option to get the monitor to work:
video=HDMI-A-1:1280x720@60
(If you have a 3.10 based kernel, then replace HDMI-A-1 with DVI-D-1)
1 Introduction
1.5 Monitor compatibility
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 1-15
Non-Confidential

Chapter 2
Configuration
This chapter describes the configuration of the V2M-Juno motherboard.
It contains the following sections:
•2.1 Connecting to a host computer on page 2-17.
•2.2 SD card filesystem layout on page 2-18.
•2.3 Flash memory programming on page 2-19.
•2.4 Erasing the flash memory on page 2-21.
•2.5 Board recovery procedure on page 2-22.
•2.6 Juno SoC configuration on page 2-23.
•2.7 Linux filesystems on page 2-24.
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 2-16
Non-Confidential

2.1 Connecting to a host computer
A set of files that are stored on an SD card on the board determines the configuration of the V2M-Juno
motherboard. The SD card can be accessed using a USB-B socket on the rear panel of the board. When
connected to a host computer, the SD card appears as a USB mass storage device with a FAT16
filesystem. The files in the filesystem are edited to control the configuration of the V2M-Juno
motherboard.
Follow these steps:
1. Connect a serial terminal to the top 9-pin UART0 connector on the rear panel.
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 V2M-Juno motherboard.
The serial terminal shows the command prompt Cmd>.
Note
If the command prompt is not shown, ensure that both configuration switches are in the top position.
Also reset the V2M-Juno motherboard using the hardware reset button. The hardware reset button is
on the rear panel.
4. At the Cmd> prompt on the serial terminal, issue the command usb_on.
Cmd> usb_on
The configuration SD card is now visible on the host computer as a mass storage device.
2 Configuration
2.1 Connecting to a host computer
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 2-17
Non-Confidential

2.2 SD card filesystem layout
If you are using the recovery images or following the Linaro software release instructions, you do not
need to change any of the firmware or configuration files.
The V2M-Juno motherboard firmware images, SoC software images, and settings are stored on an SD
card on the board. At boot time, the V2M-Juno motherboard firmware accesses the SD card and copies
certain images into internal flash memory.
The SD card is exposed to a host computer as a USB mass storage device with a FAT16 filesystem. A
brief description of the filesystem layout follows.
./
SITE1 - Motherboard firmware (BIOS, IOFPGA image, PMIC configuration)
SITE2 - Supporting files for LogicTile daughterboards
HBI0262B - Configuration files for Juno r0 only
HBI0262C - Configuration files for Juno r1 only
SOFTWARE - SoC software images (SCP Firmware, ARM Trusted Firmware,
UEFI, Linux, etc)
config.txt - Configuration file for the V2M-motherboard
HBI0262D - Configuration files for Juno r2 only
Figure 2-1 filesystem layout
Related concepts
1.2 Ports and I/O on page 1-12.
2 Configuration
2.2 SD card filesystem layout
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 2-18
Non-Confidential

2.3 Flash memory programming
This section describes flash memory programming.
Note
If you are using the recovery images or following the Linaro software release instructions, the firmware
or configuration files do not need to be changed.
For an image file to be programmed into the V2M-Juno motherboard flash memory, it must first be
placed onto the SD card filesystem. Each image must also have a corresponding entry in the SITE1/
HBI0262[B/C/D]/images.txt file. This file is used by the V2M-Juno motherboard firmware to
determine which images to program into flash memory at boot time.
Note
ARM recommends that all SoC software images to be loaded are placed in the SOFTWARE directory of the
SD card.
The following example illustrates the required format for the images.txt file. The number of entries
is likely to differ on a newly received V2M-Juno motherboard.
Example 2-1 Images.txt file format
TITLE: Versatile Express Images Configuration File
[IMAGES]
TOTALIMAGES: 2 ;Number of Images (Max: 32)
NOR0UPDATE: AUTO ;Image Update:NONE/AUTO/FORCE
NOR0ADDRESS: 0x00000000 ;Image Flash Address
NOR0FILE: \SOFTWARE\fip.bin ;Image File Name
NOR0LOAD: 00000000 ;Image Load Address
NOR0ENTRY: 00000000 ;Image Entry Point
NOR1UPDATE: AUTO ;Image Update:NONE/AUTO/FORCE
NOR1ADDRESS: 0x03EC0000 ;Image Flash Address
NOR1FILE: \SOFTWARE\bl1.bin ;Image File Name
NOR1LOAD: 00000000 ;Image Load Address
NOR1ENTRY: 00000000 ;Image Entry Point
The TOTALIMAGES value informs the V2M-Juno motherboard firmware of the number of images to be
programmed into the flash memory of the board. It must match the number of entries that follow it. If the
value is too low, that is, smaller than the number of images, some images are not programmed into the
flash memory. If it is too high, then the behavior of the V2M-Juno motherboard firmware is UNDEFINED.
Note
The numbering for images begins at zero. For example, NOR0UPDATE, NOR1UPDATE.
Each entry must have a consistent format that matches the examples that are given. The NOR[x] naming
prefix must increment with every new entry.
You can define a maximum of 32 entries, with NOR31 being the highest possible prefix name. Above this
value, the behavior of the motherboard firmware is UNDEFINED.
For each NOR[x] image, the following fields are required:
UPDATE
2 Configuration
2.3 Flash memory programming
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 2-19
Non-Confidential

None
The file is programmed into flash memory if it is not already present. On subsequent
boots the file in flash is not updated, even if it has changed on the SD card.
Auto
The V2M-Juno motherboard firmware determines if the file on the SD card is
consistent with the file in flash memory. If not, the flash memory is updated.
Force
The V2M-Juno motherboard firmware programs the flash memory with the contents of
the file on the SD card at every boot, regardless of whether it has changed or not.
ADDRESS
The base address within the flash memory that the image is programmed to. The address must
always be prefixed with 0x.
NAME
The path to, and name of, the file that is programmed. All paths must be specified from the root
of the SD card filesystem.
LOAD
Leave as zero unless required.
ENTRY
Leave as zero unless required.
2 Configuration
2.3 Flash memory programming
ARM DEN0928F Copyright © 2015 ARM. All rights reserved. 2-20
Non-Confidential