summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorAlexey Ignatov <lexszero@gmail.com>2014-10-12 01:43:30 +0400
committerStefano Babic <sbabic@denx.de>2014-11-20 10:13:45 +0100
commit7a139959d0de14a7efd0fe12b49b18e939468525 (patch)
treead86eb961a688f443a44340dedb9862d39fbd87b /doc
parentf196044dfd64745a163773c6c746f9e149ace127 (diff)
downloadtalos-obmc-uboot-7a139959d0de14a7efd0fe12b49b18e939468525.tar.gz
talos-obmc-uboot-7a139959d0de14a7efd0fe12b49b18e939468525.zip
ARM: mxs: tools: Add support for boot progress display flag
mkimage -T mxs now support new flag in config file: DISPLAYPROGRESS - makes boot process print HTLLC characters for each BootROM instruction. Signed-off-by: Alexey Ignatov <lexszero@gmail.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.mxsimage13
1 files changed, 9 insertions, 4 deletions
diff --git a/doc/README.mxsimage b/doc/README.mxsimage
index 0d31cba1fb..c3975ee5e6 100644
--- a/doc/README.mxsimage
+++ b/doc/README.mxsimage
@@ -27,7 +27,7 @@ These semantics and rules will be outlined now.
- Each line of the configuration file contains exactly one instruction.
- Every numeric value must be encoded in hexadecimal and in format 0xabcdef12 .
- The configuration file is a concatenation of blocks called "sections" and
- optionally "DCD blocks" (see below).
+ optionally "DCD blocks" (see below), and optional flags lines.
- Each "section" is started by the "SECTION" instruction.
- The "SECTION" instruction has the following semantics:
@@ -139,9 +139,14 @@ These semantics and rules will be outlined now.
NOOP
- This instruction does nothing.
-- If the verbose output from the BootROM is enabled, the BootROM will produce a
- letter on the Debug UART for each instruction it started processing. Here is a
- mapping between the above instructions and the BootROM verbose output:
+ - An optional flags lines can be one of the following:
+
+ DISPLAYPROGRESS
+ - Enable boot progress output form the BootROM.
+
+- If the boot progress output from the BootROM is enabled, the BootROM will
+ produce a letter on the Debug UART for each instruction it started processing.
+ Here is a mapping between the above instructions and the BootROM output:
H -- SB Image header loaded
T -- TAG instruction
OpenPOWER on IntegriCloud