Lines Matching +full:sub +full:- +full:nodes
1 U-Boot new uImage source file format (bindings definition)
8 ---------------
15 replace direct passing of 'struct bd_info' which was used to boot pre-FDT
18 However, U-Boot needs to support both techniques to provide backward
21 blob. Kernel image, FDT blob and possibly ramdisk image - all must be placed
24 Additionally, old uImage format has been extended to support multi sub-images
34 --------------------------------
40 (3) increases code reuse as it is already part of the U-Boot source tree.
45 uImage internals. Bindings are defined from U-Boot perspective, i.e. describe
46 final form of the uImage at the moment when it reaches U-Boot. User
48 hashes) will need to be filled in automatically by the U-Boot mkimage tool.
53 FIT - Flattened uImage Tree
58 .its - image tree source
59 .itb - flattened image tree blob
65 help of standard U-Boot mkimage tool which in turn uses dtc (device tree
73 eldk-4.2-ramdisk --------------> tqm5200.itb --------------> bootm
78 - create .its file, automatically filled-in properties are omitted
79 - call mkimage tool on a .its file
80 - mkimage calls dtc to create .itb image and assures that
82 - .itb (new uImage) is uploaded onto the target and used therein
87 To identify FIT sub-nodes representing images, hashes, configurations (which
88 are defined in the following sections), the "unit name" of the given sub-node
94 -----------------------
98 / o image-tree
99 |- description = "image description"
100 |- timestamp = <12399321>
101 |- #address-cells = <1>
105 | o image-1 {...}
106 | o image-2 {...}
110 |- default = "conf-1"
112 o conf-1 {...}
113 o conf-2 {...}
118 - description : Textual description of the uImage
121 - timestamp : Last image modification time being counted in seconds since
122 1970-01-01 00:00:00 - to be automatically calculated by mkimage tool.
125 - #address-cells : Number of 32bit cells required to represent entry and
126 load addresses supplied within sub-image nodes. May be omitted when no
130 - images : This node contains a set of sub-nodes, each of them representing
131 single component sub-image (like kernel, ramdisk, etc.). At least one
132 sub-image is required.
135 - configurations : Contains a set of available configuration nodes and
140 -----------------
142 This node is a container node for component sub-image nodes. Each sub-node of
145 o image-1
146 |- description = "component sub-image description"
147 |- data = /incbin/("path/to/data/file.bin")
148 |- type = "sub-image type name"
149 |- arch = "ARCH name"
150 |- os = "OS name"
151 |- compression = "compression name"
152 |- load = <00000000>
153 |- entry = <00000000>
155 o hash-1 {...}
156 o hash-2 {...}
160 - description : Textual description of the component sub-image
161 - type : Name of component sub-image type, supported types are:
164 - data : Path to the external file which contains this node's binary data.
165 - compression : Compression used by included data. Supported compressions
168 uncompressed by U-Boot (e.g. compressed ramdisk), this should also be set
172 - os : OS name, mandatory for types "kernel" and "ramdisk". Valid OS names
176 - arch : Architecture name, mandatory for types: "standalone", "kernel",
181 - entry : entry point address, address size is determined by
182 '#address-cells' property of the root node. Mandatory for for types:
184 - load : load address, address size is determined by '#address-cells'
187 Optional nodes:
188 - hash-1 : Each hash sub-node represents separate hash or checksum
192 5) Hash nodes
193 -------------
195 o hash-1
196 |- algo = "hash or checksum algorithm name"
197 |- value = [hash or checksum value]
200 - algo : Algorithm name, supported are "crc32", "md5" and "sha1".
201 - value : Actual checksum or hash value, correspondingly 4, 16 or 20 bytes
206 -------------------------
215 |- default = "default configuration sub-node unit name"
217 o config-1 {...}
218 o config-2 {...}
223 - default : Selects one of the configuration sub-nodes as a default
226 Mandatory nodes:
227 - configuration-sub-node-unit-name : At least one of the configuration
228 sub-nodes is required.
231 7) Configuration nodes
232 ----------------------
236 o config-1
237 |- description = "configuration description"
238 |- kernel = "kernel sub-node unit name"
239 |- ramdisk = "ramdisk sub-node unit name"
240 |- fdt = "fdt sub-node unit-name" [, "fdt overlay sub-node unit-name", ...]
241 |- fpga = "fpga sub-node unit-name"
242 |- loadables = "loadables sub-node unit-name"
246 - description : Textual configuration description.
247 - kernel : Unit name of the corresponding kernel image (image sub-node of a
251 - ramdisk : Unit name of the corresponding ramdisk image (component image
253 - fdt : Unit name of the corresponding fdt blob (component image node of a
254 "fdt type"). Additional fdt overlay nodes can be supplied which signify
257 - setup : Unit name of the corresponding setup binary (used for booting
259 - fpga : Unit name of the corresponding fpga bitstream blob
261 - loadables : Unit name containing a list of additional binaries to be
262 loaded at their given locations. "loadables" is a comma-separated list
263 of strings. U-Boot will load each binary at its given start-address and
264 may optionaly invoke additional post-processing steps on this binary based
270 Older, 2.4 kernel and 2.6 non-FDT kernel do not use FDT blob, in such cases
276 ----------------
286 - data-offset : offset of the data in a separate image store. The image
288 aligned to a 4-byte boundary.
289 - data-size : size of the data in bytes
291 The 'data-offset' property can be substituted with 'data-position', which
293 booting U-Boot proper before performing relocation. Pass '-p [offset]' to
294 mkimage to enable 'data-position'.
296 Normal kernel FIT image has data embedded within FIT structure. U-Boot image
297 for SPL boot has external data. Existence of 'data-offset' can be used to
301 -----------