On 2020-03-29, Chris Dumont wrote:
- What led up to the situation?
read the manpage for mkimage and then used 'mkimage -T -h'
...
- What was the outcome of this action?
The output (ellipsized) $ mkimage -T -hInvalid image type, supported are: Unknown image type Unknown image type aisimage Davinci AIS image atmelimage ATMEL ROM-Boot Image filesystem Filesystem Image ...
It appears the recommendation from mkimage help output is to use "mkimage -T list" now.
It seems like this should be changed to "-T list" in the manpage.
There are several other options -A, -O and -C that also should probably be updated, but those options need an updated to the code as well, as they output the usage information in addition to listing the available Architecture/Os/Compression types:
$ mkimage -A list
Invalid architecture, supported are: Unknown architecture Unknown architecture Unknown architecture Unknown architecture alpha Alpha arc ARC arm ARM arm64 AArch64 ... x86_64 AMD x86_64 xtensa Xtensa
Error: Invalid architecture Usage: mkimage -l image -l ==> list image header information mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image -A ==> set architecture to 'arch' ... -i => input filename for ramdisk file Signing / verified boot not supported (CONFIG_FIT_SIGNATURE undefined) mkimage -V ==> print version information and exit Use '-T list' to see a list of available image types
Using "mkimage -T list" just displays the list of image types, from what I can tell, which seems more-or-less fine.
I haven't tested anything newer than 2020.04~rc2, so there may be newer fixes upstream...
live well, vagrant