Searched refs:fit_check_sign (Results 1 – 7 of 7) sorted by relevance
| /u-boot/test/py/tests/ |
| A D | test_vboot.py | 232 util.run_and_log(cons, [fit_check_sign, '-f', fit, '-k', dtb])
245 cons, [fit_check_sign, '-f', ffit, '-k', dtb],
256 cons, [fit_check_sign, '-f', efit, '-k', dtb],
268 cons, [fit_check_sign, '-f', efit, '-k', dtb],
302 cons, [fit_check_sign, '-f', fit, '-k', dtb],
372 fit_check_sign = cons.config.build_dir + '/tools/fit_check_sign'
|
| /u-boot/tools/ |
| A D | fdt_host.h | 30 int fit_check_sign(const void *fit, const void *key,
|
| A D | .gitignore | 11 /fit_check_sign
|
| A D | fit_check_sign.c | 86 ret = fit_check_sign(fit_blob, key_blob, config_name); in main()
|
| A D | Makefile | 56 hostprogs-$(CONFIG_FIT_SIGNATURE) += fit_info fit_check_sign
127 fit_check_sign-objs := $(dumpimage-mkimage-objs) fit_check_sign.o
|
| A D | image-host.c | 1110 int fit_check_sign(const void *fit, const void *key, in fit_check_sign() function
|
| /u-boot/doc/uImage.FIT/ |
| A D | beaglebone_vboot.txt | 245 You can also run fit_check_sign to check it:
247 $UOUT/tools/fit_check_sign -f image.fit -k am335x-boneblack-pubkey.dtb
304 in each image referenced by that configuration. So fit_check_sign goes on to
306 case fit_check_sign checks the hash and prints sha1+ meaning that the SHA1
322 fit_check_sign again. You should see something like:
420 $UOUT/tools/fit_check_sign -f image.fit -k am335x-boneblack-pubkey.dtb
440 $UOUT/tools/fit_check_sign -f image.fit -k am335x-boneblack-pubkey.dtb
|
Completed in 15 milliseconds