diff options
| author | Simon Glass <sjg@chromium.org> | 2018-09-14 04:57:31 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2018-09-29 11:49:35 -0600 |
| commit | e0e5df9310d3a0e1fc0eda86ff43fd3e782e61f1 (patch) | |
| tree | 7550a5bb58f99bcf8e0f3ac2fdd2db8a5bce4bbf /tools/binman/README | |
| parent | 9c888cca5e87e28e9addcffae9810fee481428a8 (diff) | |
binman: Support hashing entries
Sometimesi it us useful to be able to verify the content of entries with
a hash. Add an easy way to do this in binman. The hash information can be
retrieved from the device tree at run time.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/binman/README')
| -rw-r--r-- | tools/binman/README | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/tools/binman/README b/tools/binman/README index cf1a06d164..088f3a63d9 100644 --- a/tools/binman/README +++ b/tools/binman/README @@ -466,6 +466,28 @@ see README.entries. This is generated from the source code using: binman -E >tools/binman/README.entries +Hashing Entries +--------------- + +It is possible to ask binman to hash the contents of an entry and write that +value back to the device-tree node. For example: + + binman { + u-boot { + hash { + algo = "sha256"; + }; + }; + }; + +Here, a new 'value' property will be written to the 'hash' node containing +the hash of the 'u-boot' entry. Only SHA256 is supported at present. Whole +sections can be hased if desired, by adding the 'hash' node to the section. + +The has value can be chcked at runtime by hashing the data actually read and +comparing this has to the value in the device tree. + + Order of image creation ----------------------- |