diff options
| author | Simon Glass <sjg@chromium.org> | 2017-11-12 21:52:06 -0700 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2017-11-22 18:05:38 -0700 |
| commit | 9c0a8b1f44a18343acb48a7b6cf6ec724a7fac93 (patch) | |
| tree | b2df137550986c21aa9b86ecf556671fae95aa2d /tools | |
| parent | 511fd0b2bb60e640895e7c51f71db29ddeb42aa4 (diff) | |
binman: Add docs explaining how to enable binman for a board
The process is not obvious. Add a little section to explain how to move a
board to use binman.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/binman/README | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/tools/binman/README b/tools/binman/README index 63f9722642..4ef76c8f08 100644 --- a/tools/binman/README +++ b/tools/binman/README @@ -206,6 +206,27 @@ for its instructions in the 'binman' node. Binman has a few other options which you can see by running 'binman -h'. +Enabling binman for a board +--------------------------- + +At present binman is invoked from a rule in the main Makefile. Typically you +will have a rule like: + +ifneq ($(CONFIG_ARCH_<something>),) +u-boot-<your_suffix>.bin: <input_file_1> <input_file_2> checkbinman FORCE + $(call if_changed,binman) +endif + +This assumes that u-boot-<your_suffix>.bin is a target, and is the final file +that you need to produce. You can make it a target by adding it to ALL-y +either in the main Makefile or in a config.mk file in your arch subdirectory. + +Once binman is executed it will pick up its instructions from a device-tree +file, typically <soc>-u-boot.dtsi, where <soc> is your CONFIG_SYS_SOC value. +You can use other, more specific CONFIG options - see 'Automatic .dtsi +inclusion' below. + + Image description format ------------------------ |