u-boot/tools/binman/test/53_symbols.dts

/dts-v1/;

/ {
	#address-cells = <1>;
	#size-cells = <1>;

	binman {
		pad-byte = <0xff>;
		u-boot-spl {
		};

		u-boot {
			pos = <20>;
		};

		u-boot-spl2 {
			type = "u-boot-spl";
		};
	};
};
binman: Support accessing binman tables at run time Binman construct images consisting of multiple binary files. These files sometimes need to know (at run timme) where their peers are located. For example, SPL may want to know where U-Boot is located in the image, so that it can jump to U-Boot correctly on boot. In general the positions where the binaries end up after binman has finished packing them cannot be known at compile time. One reason for this is that binman does not know the size of the binaries until everything is compiled, linked and converted to binaries with objcopy. To make this work, we add a feature to binman which checks each binary for symbol names starting with '_binman'. These are then decoded to figure out which entry and property they refer to. Then binman writes the value of this symbol into the appropriate binary. With this, the symbol will have the correct value at run time. Macros are used to make this easier to use. As an example, this declares a symbol that will access the 'u-boot-spl' entry to find the 'pos' value (i.e. the position of SPL in the image): binman_sym_declare(unsigned long, u_boot_spl, pos); This converts to a symbol called '_binman_u_boot_spl_prop_pos' in any binary that includes it. Binman then updates the value in that binary, ensuring that it can be accessed at runtime with: ulong u_boot_pos = binman_sym(ulong, u_boot_spl, pos); This assigns the variable u_boot_pos to the position of SPL in the image. Signed-off-by: Simon Glass <sjg@chromium.org> 2017-11-14 01:55:01 +00:00			`/dts-v1/;`

			`/ {`
			`#address-cells = <1>;`
			`#size-cells = <1>;`

			`binman {`
			`pad-byte = <0xff>;`
			`u-boot-spl {`
			`};`

			`u-boot {`
			`pos = <20>;`
			`};`

			`u-boot-spl2 {`
			`type = "u-boot-spl";`
			`};`
			`};`
			`};`