u-boot.git/tools, branch v2019.07-rc3

Merge tag 'u-boot-stm32-20190523' of https://github.com/pchotard/u-boot

2019-05-24T12:13:27Z

- Add various STM32MP1 fixes for serial, env, clk, board, i2c ... - Add STM32MP1 DDR driver update: These update introduce the DDR interactive mode described in: https://wiki.st.com/stm32mpu/index.php/U-Boot_SPL:_DDR_interactive_mode This mode is used by the CubeMX: DDR tuning tool. https://wiki.st.com/stm32mpu/index.php/STM32CubeMX The DDR interactive mode is NOT activated by default because it increase the SPL size and slow down the boot time (200ms wait added).

mkimage: change stm32image header to manage binary information

2019-05-23T09:36:47Z

To get more information from STM32 Header about the generated binary, we will add a new byte with the following field: replace padding byte 255 with 0x00 for "U-Boot" Signed-off-by: Patrick Delaunay

buildman: Deal more nicely with invalid build-status file

2019-05-21T23:33:23Z

The 'done' files created by buildman may end up being empty if buildman runs out of disk space while writing them. At present buildman dies with an exception when using -s to check the build status. Fix this. Seriesl-cc: trini Signed-off-by: Simon Glass

tools: use read-only mmap in fit_check_sign

2019-05-18T16:32:02Z

Add an option to open files in read-only mode in mmap_fdt so that fit_check_sign can be used to inspect files on read-only filesystems. For example, this is useful when a key is shipped in a read-only rootfs or squashfs. Signed-off-by: Luca Boccassi

arm: k3: config.mk: Use k3_gen_x509_cert.sh to generate boot images

2019-05-10T00:22:05Z

Instead of overlading makefile, use the k3_gen_x509_cert.sh script to generate boot images. Signed-off-by: Lokesh Vutla

tools: k3_get_x509 cert: Add a script to generate x509 certificate for K3 devices

2019-05-10T00:22:04Z

TI's K3 boot architecture mandates a x509 certificate for every boot image. While signing the image K3 ROM allows for two types of keys based on which the boot image gets loaded in different ways: - Degenerate RSA keys: This generates a signature which is equal to the digest. When ROM sees this, it does a DMA for copying the images, which significantly improves the boot time. - Any other key: Does a memcpy to load the image. This is introduced as a fallback for DMA copy. Add a script for generating boot images with the above options. Default generates image using rsa degenerate key in order to improve boot time. Signed-off-by: Lokesh Vutla Signed-off-by: Dave Gerlach Signed-off-by: Andreas Dannenberg

Make FIT support really optional

2019-05-09T23:52:55Z

Due to some mistakes in the source code, it was not possible to really turn FIT support off. This commit fixes the problem by means of the following changes: - Enclose "bootm_host_load_image" and "bootm_host_load_images" between checks for CONFIG_FIT_SIGNATURE, in common/bootm.c. - Enclose the declaration of "bootm_host_load_images" between checks for CONFIG_FIT_SIGNATURE, in common/bootm.h. - Condition the compilation and linking of fit_common.o fit_image.o image-host.o common/image-fit.o to CONFIG_FIT=y, in tools/Makefile. Signed-off-by: Carlos Santos [fabio: adapt for 2016.07] Signed-off-by: Fabio Estevam [Ricardo: fix conditional compilation and linking of the files mentioned above for 2016.07] Signed-off-by: Ricardo Martincoski [Jörg: adapt for 2019.01] Signed-off-by: Jörg Krause [Retrieved from: https://git.buildroot.net/buildroot/tree/package/uboot-tools/0003-Make-FIT-support-really-optional.patch] Signed-off-by: Fabrice Fontaine

binman: Allow sections to have an offset

2019-05-08T04:44:07Z

At present sections are always placed automatically. Even if an 'offset' property is provided it is ignored. Update the logic to support an offset for sections. Signed-off-by: Simon Glass Reviewed-by: Bin Meng

binman: Add a missing comment in Entry_vblock

2019-05-08T04:44:07Z

An important property is missing. Update the entry comment to include this. Signed-off-by: Simon Glass Reviewed-by: Bin Meng

binman: Don't show image-skip message by default

2019-05-08T04:44:07Z

This message is not very important since it is simply indicating that the user's instructions are being followed. Only show it when the verbosity level is above the default. Also drop the unnecessary extra newline on this message, which causes two line breaks. Signed-off-by: Simon Glass Reviewed-by: Bin Meng