Binman does not support this properly at present. Add documentation about it including a work-around.
Signed-off-by: Simon Glass sjg@chromium.org ---
tools/binman/binman.rst | 50 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+)
diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst index f85d13b700a..7cfac724b84 100644 --- a/tools/binman/binman.rst +++ b/tools/binman/binman.rst @@ -858,6 +858,55 @@ allow-repack: image description to be stored in the FDT and fdtmap.
+Image dependencies +------------------ + +Binman does not currently support images that depend on each other. For example, +if one image creates `fred.bin` and then the next uses this `fred.bin` to +produce a final `image.bin`, then the behaviour is undefined. It may work, or it +may produce an error about `fred.bin` being missing, or it may use a version of +`fred.bin` from a previous run. + +Often this can be handled by incorporating the dependency into the second +image. For example, instead of:: + + binman { + multiple-images; + + fred { + u-boot { + }; + fill { + size = <0x100>; + }; + }; + + image { + blob { + filename = "fred.bin"; + }; + u-boot-spl { + }; + }; + +you can do this:: + + binman { + image { + fred { + type = "section"; + u-boot { + }; + fill { + size = <0x100>; + }; + }; + u-boot-spl { + }; + }; + + + Hashing Entries ---------------
@@ -1690,6 +1739,7 @@ Some ideas: Perhaps it should completely regenerate the flat tree? - Put faked files into a separate subdir and remove them on start-up, to avoid seeing them as 'real' files on a subsequent run +- Support images which depend on each other
-- Simon Glass sjg@chromium.org