u-boot.git/tools/mkimage.c, branch v2020.07

tools: mkimage: use /* fallthrough */ as needed

2020-05-15T18:47:35+00:00

GCC recognizes /* fallthrough */ if -Wimplicit-fallthrough=3 is enabled.
Let's use it consistently.

Signed-off-by: Heinrich Schuchardt

mkimage: fit_image: Add option to make fit header align

2020-04-24T14:10:01+00:00

The image is usually stored in block device like emmc, SD card, make the
offset of image data aligned to block(512 byte) can avoid data copy
during boot process.
eg. SPL boot from FIT image with external data:
- SPL read the first block of FIT image, and then parse the header;
- SPL read image data separately;
- The first image offset is the base_offset which is the header size;
- The second image offset is just after the first image;
- If the offset of imge does not aligned, SPL will do memcpy;
The header size is a ramdon number, which is very possible not aligned, so
add '-B size'to specify the align size in hex for better performance.

example usage:
  ./tools/mkimage -E -f u-boot.its -B 0x200 u-boot.itb

Signed-off-by: Kever Yang 
Reviewed-by: Punit Agrawal 
Reviewed-by: Tom Rini

tools: mkimage: use common ALIGN to do the size align

2020-04-24T14:10:00+00:00

The ALIGN() is now available at imagetool.h, migrate to use it.

Signed-off-by: Kever Yang 
Reviewed-by: Punit Agrawal 
Reviewed-by: Tom Rini

rockchip: mkimage: support packing optional second level boot-loader

2019-12-27T07:17:07+00:00

Support packing optional second level boot-loader:

$ ./tools/mkimage -n rk3399 -T rksd -d \
  rk3399_ddr_800MHz_v1.24.bin:rk3399_miniloader_v1.19.bin out -v
Adding Image rk3399_ddr_800MHz_v1.24.bin
Size 116492(pad to 116736)
Adding Image rk3399_miniloader_v1.19.bin
Size 88060(pad to 88064)
Image Type:   Rockchip RK33 (SD/MMC) boot image
Init Data Size: 116736 bytes
Boot Data Size: 88064 bytes

Mainly parse init file and boot file from datafile option, copy them to
the image with 2KB alignment.

Signed-off-by: Jeffy Chen 
Reviewed-by: Kever Yang

lib: rsa: add support to other openssl engine types than pkcs11

2019-07-18T15:31:23+00:00

There are multiple other openssl engines used by HSMs that can be used to
sign FIT images instead of forcing users to use pkcs11 type of service.

Relax engine selection so that other openssl engines can be specified and
use generic key id definition formula.

Signed-off-by: Vesa Jääskeläinen 
Cc: Tom Rini

fdt: Fix mkimage list to try every header type

2019-04-12T02:10:50+00:00

Signed-off-by: Jordan Hand 
Tested-by: Vagrant Cascadian 
Tested-by: Alex Kiernan

fdt: Fix FIT header verification in mkimage and conduct same checks as bootm

2019-03-08T16:31:44+00:00

FIT header verification in mkimage was treating a return code as a boolean,
which meant that failures in validating the fit were seen as successes.

Additionally, mkimage was checking all formats to find a header which
passes validation, rather than using the image type specified to
mkimage.

checkpatch.pl checks for lines ending with '(' and alignment matching
open parentheses are ignored to keep with existing coding style.

Signed-off-by: Jordan Hand

tools: add i.MX8M image support

2019-01-01T13:12:18+00:00

i.MX8M bootable image type is like i.MX6/7, but there is signed HDMI
firmware image in front of A53 bootable image, which is also has an IVT
header.

Here we also include fit image to generate a bootable image.

Signed-off-by: Peng Fan 
Signed-off-by: Stefano Babic

tools: add i.MX8/8X image support

2018-10-22T11:01:27+00:00

i.MX8/8X bootable image type is container type.
The bootable image, containers a container set which supports two
container. The 1st container is for SECO firmware, the 2nd container
needs to include scfw, m4_0/1 image, ACore images per your requirement.

Signed-off-by: Peng Fan

tools: mkimage: Ensure munmap unmaps the same length that was mapped

2018-09-11T01:19:32+00:00

The set_header call in kwbimage.c adds a checksum to the end of the
image in addition to setting up the header. It 'helpfully' updates the
st_size to match the fact that the file is now longer. However, mkimage
uses this length in the munmap call. This can lead to unmapping an extra
page, of perhaps required data. When this happens, a SEGV can occur.

To prevent this from happening, the munmap call now uses the same length
that was passed to mmap. This could also have been fixed by not changing
the length in kwbimage.c, however changing it in the main file means
that other plugins will also not fall for the same trap.

Signed-off-by: Mark Tomlinson 
Signed-off-by: Chris Packham 
[cp: resolve checkpatch complaints]
Tested-by: Chris Packham