u-boot.git/tools, branch v2025.04

buildman: update PyYAML requirement

2025-04-07T13:34:49Z

On Ubuntu 25.04 installing the dependency pyyaml 6.0 fails with License classifiers are deprecated Update PyYAML to the current release. Signed-off-by: Heinrich Schuchardt

dumpimage: fix handling of StarFive SPL too long

2025-03-18T14:17:32Z

The header of the StarFive U-Boot SPL file u-boot-spl.normal.out has a field indicating the payload size. When copying U-Boot SPL from a partition the copied file might be too long. Currently in this situation a misleading error message 'Incorrect CRC32' is written. We must use the payload size and not the file size when calculating the CRC32. Write a warning if the file is too long indicating the correct size. This enables the user to truncate the file accordingly. Signed-off-by: Heinrich Schuchardt

qconfig: Correct unhashable-type error with --scan-source

2025-03-18T14:17:30Z

This gives an error with newer Python version, so fix it. Signed-off-by: Simon Glass

binman: Honour the skip-at-start property more faithfully

2025-03-04T14:22:11Z

A discussion on the mailing list about dealing with block offsets and binman symbols made me think that something is wrong with how Binman deals with the skip-at-start property. The feature was originally designed to handle x86 ROMs, which are mapped at the top of the address space. That seemed too specific, whereas skipping some space at the start seemed more generally useful. It has proved useful. For example, rockchip images start at block 64, so a skip-at-start of 0x8000 deals with this. But it doesn't actually work correctly, since the image_pos value does not give the actual position on the media. Fix this and update the documentation, moving it into the 'section' section. Signed-off-by: Simon Glass

binman: Rename Entry.end_4gb

2025-03-04T14:22:10Z

The property is named end_at_4gb so name the variable the same, to avoid confusion. Signed-off-by: Simon Glass

tools: use cryptographically safe RNG

2025-02-18T18:30:32Z

The PRNG implementing the random() function only has 2^31 states and therefore is unsafe to use for cryptography. Use arc4random() instead. Fixes: cc34f04efd63 ("tools: image-host.c: use random instead of rand") Addresses-Coverity-ID: 312953 Calling risky function Signed-off-by: Heinrich Schuchardt

tools: mkenvimage: List -V parameter in help text

2025-02-10T16:27:01Z

The -V version parameter is missing in the optional list of parameters in help text. Add it. Signed-off-by: Marek Vasut

lib: Allow crc16 code to be dropped

2025-02-03T22:00:42Z

This code is not necessarily needed in VPL, even if SPL uses it, so adjust the rules to allow it to be dropped. Do the same for the hash API. Signed-off-by: Simon Glass Reviewed-by: Tom Rini

tools: check result of lseek

2025-01-26T17:35:46Z

Return value of function 'lseek', called at pblimage.c:211, is not checked, but it is usually checked for this function. This trigger was found using the Svace static analyzer. Signed-off-by: Maks Mishin Reviewed-by: Tom Rini

buildman: Record an error if a toolchain is missing

2025-01-25T22:27:24Z

Buildman has always treated the lack of a toolchain as an infrastructure problem rather than a build failure. However the logic for this is not correct, since it does not write a 'done' file in this case. As a result, one of two things can happen. 1. If a previous build ran in the same (output) directory, the outcome of *that* build is recorded as the outcome of this one 2. Otherwise, no outcome is recorded Obviously this inconsistency is not ideal. While (2) is rare, it can be very confusing as the build sort-of fails but does not produce any summary output with 'buildman -s' Overall it seems better to attribute a toolchain issue to the boards that it affects. This results in clear failures which can be examined, no matter what happened in the .bm-work directory previously. So write a 'done' file for each build when a toolchain is missing. The end result of this patch is to make missing toolchains much more obvious. It should be things a bit easier for novice users. Signed-off-by: Simon Glass