From 9c0a8b1f44a18343acb48a7b6cf6ec724a7fac93 Mon Sep 17 00:00:00 2001 From: Simon Glass Date: Sun, 12 Nov 2017 21:52:06 -0700 Subject: [PATCH] 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 --- tools/binman/README | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/tools/binman/README b/tools/binman/README index 63f9722..4ef76c8 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_),) +u-boot-.bin: checkbinman FORCE + $(call if_changed,binman) +endif + +This assumes that u-boot-.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 -u-boot.dtsi, where is your CONFIG_SYS_SOC value. +You can use other, more specific CONFIG options - see 'Automatic .dtsi +inclusion' below. + + Image description format ------------------------ -- 2.7.4