August 2023 - U-Boot

[PATCH] spl: remove duplicate SPL_MD5 option
by Oleksandr Suvorov 03 Aug '23

03 Aug '23

There is another SPL_MD5 option defined in lib/Kconfig. Renaming SPL_MD5_SUPPORT introduced duplicate option with different description. As for now FIT and hash algorithm options are not related to each others, removing a duplicate option seems OK. Fixes: 4b00fd1a84c ("Kconfig: Rename SPL_MD5_SUPPORT to SPL_MD5") Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov(a)foundries.io> --- common/spl/Kconfig | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/common/spl/Kconfig b/common/spl/Kconfig index bee231b583a..c66d70e2a99 100644 --- a/common/spl/Kconfig +++ b/common/spl/Kconfig @@ -561,18 +561,6 @@ config SPL_CRC32 for detected accidental image corruption. For secure applications you should consider SHA1 or SHA256. -config SPL_MD5 - bool "Support MD5" - depends on SPL_FIT - help - Enable this to support MD5 in FIT images within SPL. An MD5 - checksum is a 128-bit hash value used to check that the image - contents have not been corrupted. Note that MD5 is not considered - secure as it is possible (with a brute-force attack) to adjust the - image while still retaining the same MD5 hash value. For secure - applications where images may be changed maliciously, you should - consider SHA256 or SHA384. - config SPL_FIT_IMAGE_TINY bool "Remove functionality from SPL FIT loading to reduce size" depends on SPL_FIT -- 2.40.1

1 0

[PATCH] sunxi: MAINTAINERS: drop myself
by FUKAUMI Naoki 03 Aug '23

03 Aug '23

I no longer maintain them. Signed-off-by: FUKAUMI Naoki <naobsd(a)gmail.com> --- board/sunxi/MAINTAINERS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/board/sunxi/MAINTAINERS b/board/sunxi/MAINTAINERS index 98bbd2dd25..d89a25db7c 100644 --- a/board/sunxi/MAINTAINERS +++ b/board/sunxi/MAINTAINERS @@ -82,8 +82,8 @@ S: Maintained F: configs/A20-Olimex-SOM-EVB_defconfig A20-OLINUXINO-LIME BOARD -M: FUKAUMI Naoki <naobsd(a)gmail.com> -S: Maintained +M: +S: F: configs/A20-OLinuXino-Lime_defconfig A20-OLINUXINO-LIME2 BOARD @@ -379,8 +379,8 @@ S: Maintained F: configs/nanopi_a64_defconfig NINTENDO NES CLASSIC EDITION BOARD -M: FUKAUMI Naoki <naobsd(a)gmail.com> -S: Maintained +M: +S: F: configs/Nintendo_NES_Classic_Edition_defconfig OCEANIC 5205 5INMFD BOARD -- 2.39.2

4 5

[PATCH 0/2] treewide: rework linker symbol declarations and references
by Shiji Yang 03 Aug '23

03 Aug '23

2 1

[PATCH v3 0/4] arm: dts: k3-am64: Sync DT with Linux
by Roger Quadros 03 Aug '23

03 Aug '23

Hi, This series syncs AM64 DT files from Linux v6.5-rc1. Tested on AM642-EVM GP SR1.0 and AM642-SK-EVM HS-FS SR2.0. Couldn't verify Linux boot on AM642-SK-EVM so would appreciate if someone can give a Tested-by for that. Thanks! cheers, -roger Changelog: v3: - include board DT file in -r5 DT file. - move including -u-boot.dtsi file at the top of -r5 DT file. - drop duplicate nodes - document why we need to delete clock/power properties from main_timer0 v2: - Sync with v6.5-rc1 - Rebase on latest uboot/master - CPSW node cleanup - Timer node cleanup Roger Quadros (4): board: ti: am64x: Recognize AM64-HSEVM doc: board: ti: am64: Add boot flow diagram Revert "ARM: dts: k3-am642-sk-u-boot: add PMIC node" arm: dts: k3-am64: Sync DT with Linux v6.5-rc1 arch/arm/dts/k3-am64-main.dtsi | 171 ++++++++- arch/arm/dts/k3-am64-mcu.dtsi | 53 ++- arch/arm/dts/k3-am64-thermal.dtsi | 33 ++ arch/arm/dts/k3-am64.dtsi | 22 +- arch/arm/dts/k3-am642-evm-u-boot.dtsi | 67 ++-- arch/arm/dts/k3-am642-evm.dts | 173 +++++++-- arch/arm/dts/k3-am642-r5-evm.dts | 202 +--------- arch/arm/dts/k3-am642-r5-sk.dts | 209 +---------- arch/arm/dts/k3-am642-sk-u-boot.dtsi | 120 ++---- arch/arm/dts/k3-am642-sk.dts | 166 ++++++--- arch/arm/dts/k3-am642.dtsi | 1 + board/ti/am64x/evm.c | 3 +- doc/board/ti/img/boot_diagram_am64.svg | 496 +++++++++++++++++++++++++ 13 files changed, 1111 insertions(+), 605 deletions(-) create mode 100644 arch/arm/dts/k3-am64-thermal.dtsi create mode 100644 doc/board/ti/img/boot_diagram_am64.svg -- 2.34.1

3 13

Please pull u-boot-dm
by Simon Glass 03 Aug '23

03 Aug '23

Hi Tom, https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/17186 https://dev.azure.com/simon0972/u-boot/_build/results?buildId=44&view=resul… The following changes since commit 7755b2200777f72dca87dd169138e95f011bbcb9: Merge tag 'x86-pull-20230801' of https://source.denx.de/u-boot/custodians/u-boot-x86 (2023-08-01 11:57:55 -0400) are available in the Git repository at: git://git.denx.de/u-boot-dm.git tags/dm-pull-2aug23 for you to fetch changes up to 288ae53cb73605500b7fc01e5919753c878466be: binman: Add a temporary hack for duplicate phandles (2023-08-02 12:05:57 -0600) ---------------------------------------------------------------- binman fixes for options, etc. binman template fixes / tweaks ---------------------------------------------------------------- Heinrich Schuchardt (2): boot: fix bootdev_list() cmd/bootdev: print readable status code Jonas Karlman (7): binman: Update tee-os missing blob help text binman: Update missing optional external blob warning text binman: Report missing external blobs using error level binman: Override CheckOptional in fit entry binman: Fix blank line usage for invalid images warning text binman: Show filename in missing blob help message Makefile: Show binman missing blob message Lukas Funke (1): binman: elf: Check for ELF_TOOLS availability and remove extra semicolon Simon Glass (7): binman: Produce a template-file after processing dtoc: Make properties dirty when purging them dtoc: Add some debugging when copying nodes fdt: Allow copying phandles into templates binman: Remove templates after use binman: Support templates containing phandles binman: Add a temporary hack for duplicate phandles Makefile | 8 +++++++- boot/bootdev-uclass.c | 2 +- cmd/bootdev.c | 2 +- tools/binman/binman.rst | 26 +++++++++++++++++++++++- tools/binman/cmdline.py | 2 ++ tools/binman/control.py | 71 +++++++++++++++++++++++++++++++++++++++++++++++++++--------------- tools/binman/elf.py | 10 ++++++---- tools/binman/elf_test.py | 16 +++++++++++++-- tools/binman/etype/fit.py | 7 +++++++ tools/binman/ftest.py | 54 +++++++++++++++++++++++++++++++++++++++++++++++++- tools/binman/missing-blob-help | 2 +- tools/binman/test/264_tee_os_opt_fit.dts | 1 + tools/binman/test/291_template_phandle.dts | 51 +++++++++++++++++++++++++++++++++++++++++++++++ tools/binman/test/292_template_phandle_dup.dts | 65 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ tools/dtoc/fdt.py | 40 +++++++++++++++++++++++++++---------- tools/dtoc/test/dtoc_test_copy.dts | 6 ++++-- tools/dtoc/test_fdt.py | 40 +++++++++++++++++++++++++++++-------- 17 files changed, 355 insertions(+), 48 deletions(-) create mode 100644 tools/binman/test/291_template_phandle.dts create mode 100644 tools/binman/test/292_template_phandle_dup.dts Regards, Simon

2 1

[RFC 0/3] firmware: scmi: add sanity checks for protocols
by AKASHI Takahiro 03 Aug '23

03 Aug '23

Now that we have the Base protocol support, we will be able to add a couple of checks so that we will make sure that U-Boot scmi drivers work as expected. - check if SCMI server (firmware) supports the protocol - check if SCMI server implements an expected version of protocol Although adding these checks was one of my objectives in supporting the Base protocol, this patch series is marked as RFC for now because I have no confidence about what exact version the existing drivers are based on. (I temporarily assigned the version numbers in [1].) Test ==== The patch series was tested on the following platforms: * sandbox Prerequisite: ============= * This patch series is based on my previous patch of base protocol support[1] [1] https://lists.denx.de/pipermail/u-boot/2023-July/524811.html Change history: =============== RFC (Jul, 28, 2023) * initial release AKASHI Takahiro (3): firmware: scmi: add a check against availability of protocols firmware: scmi: add PROTOCOL_VERSION support for existing protocols on sandbox firmware: scmi: add a sanity check against protocol version drivers/clk/clk_scmi.c | 6 ++ drivers/firmware/scmi/sandbox-scmi_agent.c | 80 ++++++++++++++++++++++ drivers/firmware/scmi/scmi_agent-uclass.c | 41 ++++++++++- drivers/power/regulator/scmi_regulator.c | 6 ++ drivers/reset/reset-scmi.c | 14 +++- include/scmi_protocols.h | 6 ++ 6 files changed, 149 insertions(+), 4 deletions(-) -- 2.41.0

2 6

[PATCH v5 00/12] Integrate EFI capsule tasks into u-boot's build flow
by Sughosh Ganu 03 Aug '23

03 Aug '23

This patchset aims to bring two capsule related tasks under the u-boot build flow. One is the embedding of the public key into the platform's dtb. The public key is in the form of an EFI Signature List(ESL) file and is used for capsule authentication. This is being achieved by adding the signature node containing the capsule public key in the architecture's u-boot.dtsi file. Currently, the u-boot.dtsi file has been added for the sandbox and arm architectures. The path to the ESL file is being provided through a Kconfig symbol(CONFIG_EFI_CAPSULE_ESL_FILE). Changes have also been made to the test flow so that the keys used for signing the capsule, and the ESL file, are generated prior to invoking the u-boot's build, which enables embedding the ESL file into the dtb as part of the u-boot build. The other task is related to generation of capsules. Support is being added to generate capsules by specifying the capsule parameters in a config file. Calling the mkeficapsule tool then results in generation of the corresponding capsule files. The capsules can be generated as part of u-boot build, and this is being achieved through binman, by adding a capsule entry type. The capsules can be generated either by specifying the capsule parameters in a config file, or through specifying them as properties under the capsule entry node. If using the config file, the path to the config file is to be specified through a Kconfig symbol(CONFIG_EFI_CAPSULE_CFG_FILE). Changes have also been made to the efi capsule update feature testing setup on the sandbox variants. Currently, the capsule files and the public key ESL file are generated after u-boot has been built. This logic has been changed so that the capsule input files along with the keys needed for capsule signing and authentication are generated prior to initiation of the u-boot build. The placement of all the files needed for generation of capsules, along with the generated capsule files is under the /tmp/capsules/ directory. Currently, the capsule update feature is tested on the sandbox and sandbox_flattree variants in CI. The capsule generation through config file is enabled for the sandbox variant, with the sandbox_flattree variant generating capsules through the command-line parameters. The document has been updated to reflect the above changes. Changes since V4: * Rebase on top of current HEAD. * Pass the single command target names directly to the function instead of putting them in a separate list. * Fix multi line comment format. * Drop additional blank line. * Remove the check for CONFIG_EFI_HAVE_CAPSULE_SUPPORT from arm's u-boot.dtsi. * Wrap the help text in the EFI_CAPSULE_ESL_FILE config at 72 chars. * New patch which moves the setting up of the files needed for testing the EFI capsule update feature to the Dockerfile. * Remove blank lines after function comments. * Fix a couple of typos. * Use single quotes for strings. * Put the GUIDs in variables with relevant names. * Declare certain values in local variables instead of member values. * Add comments for explaning the payload offsets in the capsule file. * Drop the test case for generating the capsule from the config file. * Define payload data for the capsule tests. * Add logic to find input and output files in capsule generation in the indir and outdir directories when absolute path is not passed. * Use a relative path for CONFIG_EFI_CAPSULE_CFG_FILE. * Remove logic to copy capsule config file to /tmp/capsules/ directory, as the capsule entry can handle relative paths. * Add a comment in the capsule config file for the image GUIDs being used. * Use lower case for image GUIDs. * Define macros for the image GUIDs being used for generating the capsules. * Use lower case for image GUIDs. Sughosh Ganu (12): binman: bintool: Build a tool from a list of commands nuvoton: npcm845-evb: Add a newline at the end of file capsule: authenticate: Add capsule public key in platform's dtb doc: capsule: Document the new mechanism to embed ESL file into dtb tools: mkeficapsule: Add support for parsing capsule params from config file Dockerfile: capsule: Setup the files needed for capsule update testing binman: capsule: Add support for generating capsules doc: Add documentation to highlight capsule generation related updates test: py: Setup capsule files for testing test: capsule: Remove public key embed logic from capsule update test sandbox: capsule: Add a config file for generating capsules sandbox: capsule: Generate capsule related files through binman arch/arm/dts/nuvoton-npcm845-evb.dts | 2 +- arch/arm/dts/u-boot.dtsi | 14 + arch/sandbox/dts/u-boot.dtsi | 288 ++++++++++++++ configs/sandbox_defconfig | 3 + configs/sandbox_flattree_defconfig | 1 + configs/sandbox_spl_defconfig | 1 + doc/develop/uefi/uefi.rst | 106 +++++- lib/efi_loader/Kconfig | 9 + lib/efi_loader/Makefile | 7 + test/py/conftest.py | 84 +++++ test/py/tests/test_efi_capsule/conftest.py | 164 +------- .../test_efi_capsule/sandbox_capsule_cfg.txt | 175 +++++++++ test/py/tests/test_efi_capsule/signature.dts | 10 - .../tests/test_efi_capsule/uboot_bin_env.its | 36 -- tools/Kconfig | 16 + tools/Makefile | 1 + tools/binman/bintool.py | 19 +- tools/binman/btool/mkeficapsule.py | 153 ++++++++ tools/binman/entries.rst | 42 +++ tools/binman/etype/capsule.py | 132 +++++++ tools/binman/ftest.py | 115 ++++++ tools/binman/test/307_capsule.dts | 19 + tools/binman/test/308_capsule_signed.dts | 21 ++ tools/binman/test/309_capsule_version.dts | 20 + tools/binman/test/310_capsule_missing_key.dts | 20 + .../binman/test/311_capsule_missing_index.dts | 18 + .../binman/test/312_capsule_missing_guid.dts | 17 + .../test/313_capsule_missing_payload.dts | 18 + tools/binman/test/314_capsule_missing.dts | 18 + tools/binman/test/files/capsule_cfg.txt | 6 + tools/docker/Dockerfile | 12 + tools/eficapsule.h | 115 ++++++ tools/mkeficapsule.c | 87 +++-- tools/mkeficapsule_parse.c | 352 ++++++++++++++++++ 34 files changed, 1845 insertions(+), 256 deletions(-) create mode 100644 arch/arm/dts/u-boot.dtsi create mode 100644 arch/sandbox/dts/u-boot.dtsi create mode 100644 test/py/tests/test_efi_capsule/sandbox_capsule_cfg.txt delete mode 100644 test/py/tests/test_efi_capsule/signature.dts delete mode 100644 test/py/tests/test_efi_capsule/uboot_bin_env.its create mode 100644 tools/binman/btool/mkeficapsule.py create mode 100644 tools/binman/etype/capsule.py create mode 100644 tools/binman/test/307_capsule.dts create mode 100644 tools/binman/test/308_capsule_signed.dts create mode 100644 tools/binman/test/309_capsule_version.dts create mode 100644 tools/binman/test/310_capsule_missing_key.dts create mode 100644 tools/binman/test/311_capsule_missing_index.dts create mode 100644 tools/binman/test/312_capsule_missing_guid.dts create mode 100644 tools/binman/test/313_capsule_missing_payload.dts create mode 100644 tools/binman/test/314_capsule_missing.dts create mode 100644 tools/binman/test/files/capsule_cfg.txt create mode 100644 tools/mkeficapsule_parse.c -- 2.34.1

5 44

U-Boot video output for rk3588
by Simon Glass 03 Aug '23

03 Aug '23

Hi, Does anyone know how to enable HDMI output on this device in U-Boot, e.g. on rock5b? Regards, Simon

4 4

[PATCH v2 0/9] x86: Improve bootstd support
by Simon Glass 03 Aug '23

03 Aug '23

This series provides some bootstd fixes so that IDE can be used reliably for booting a distro. It also includes some documentation on how to boot from coreboot in various scenarios, using QEMU. With this it is possible to boot Ubuntu 2023.04 from coreboot64, for example. Changes in v2: - Use log_warning() for the warning - Fix the function name in the header as well Simon Glass (9): fs: fat: Support reading from a larger block size usb: Return -ENOENT when no devices are found lib: Suppress E when writing error-string output bootstd: Rename bootdev_setup_sibling_blk() bootstd: Correct creating of bootdev sibling bootstd: Add some more debugging in the bootdev uclass x86: coreboot: Add IDE and SATA x86: coreboot: Enable standard boot x86: coreboot: Enable support for CBFS boot/bootdev-uclass.c | 17 +++-- common/usb_storage.c | 2 +- configs/coreboot64_defconfig | 16 ++--- configs/coreboot_defconfig | 11 ++++ doc/board/coreboot/coreboot.rst | 74 ++++++++++++++++++++-- doc/develop/bootstd.rst | 4 +- drivers/block/ide.c | 4 +- drivers/mmc/mmc-uclass.c | 2 +- drivers/nvme/nvme.c | 2 +- drivers/scsi/scsi.c | 2 +- drivers/usb/host/usb-uclass.c | 2 +- drivers/virtio/virtio-uclass.c | 2 +- fs/fat/Kconfig | 13 ++++ fs/fat/fat.c | 107 ++++++++++++++++++++++++++++---- fs/fat/fat_write.c | 8 ++- include/bootdev.h | 10 +-- include/usb.h | 9 ++- lib/vsprintf.c | 5 +- 18 files changed, 238 insertions(+), 52 deletions(-) -- 2.41.0.487.g6d72f3e995-goog

3 31

Data abort when starting DFU on SAMA5D2
by Alexis Lothoré 03 Aug '23

03 Aug '23

Hi, I am currently using an ATSAMA5D27-WLSOM1-EK1. This boards embeds an ATSAMA5D27-WLSOM1, which in turns holds an ATSAMA5D27 and a 8MB QSPI flash. I have been wanting to program u-boot in the QSPI flash thanks to DFU, since the board is able to boot from QSPI and is supported in uboot. To do so, I have executed the following steps: - check out recent uboot version (2023.07.02, but issed described below is observed on master too) - load sama5d27_wlsom1_ek_qspiflash_defconfig - tune the configuration to enable DFU: - CONFIG_CMD_DFU=y - CONFIG_DFU_SF=y - CONFIG_USB_GADGET_DOWNLOAD=y - build uboot, upload and run it onto external ram thanks to snagrecover ([1]). - running "bdinfo" shows that board is properly defined/recognized - "sf probe" properly detects the qspi flash chip - in u-boot console, configure dfu: - setenv dfu_alt_info uboot raw 0 0x80000 - start DFU: - dfu 0 sf 2:0 Unfortunately, this step systematically and immediately leads to a data abort with the following log: => dfu 0 sf 2:0 data abort pc : [<2fda9ee0>] lr : [<2fd8dc08>] reloc pc : [<26f3fee0>]lr : [<26f23c08>] sp : 2f963fe8 ip : 2f9829cc fp : 00000000 r10: 2fde1cd9 r9 : 2f969e80 r8 : 2fdfc304 r7 : 00000000 r6 : 00000000 r5 : 2fdf3034 r4 : 2f982948 r3 : 0a299cfc r2 : ffffffec r1 : 00000000 r0 : 00000000 Flags: nzCv IRQs off FIQs off Mode SVC_32 Code: e5843058 e5950004 e3a01000 e5903008 (e5933008) Resetting CPU ... resetting ... System reset not supported on this platform ### ERROR ### Please RESET the board ### A quick translation with addr2line shows that the data abort occurs in include/linux/usb/gagdet.h, in usb_ep_alloc_request, likely because of ep being NULL, which seems confirmed by adding some custom logs in both usb_ep_alloc_request and its caller (composite_bind). Before digging further, does anyone have successfully used DFU on SAMA5D2 boards (and if so, am I missing something in the configuration) ? Or does this data abort show that some support is still missing to make it work for SAMA5D2 ? Kind regards, Alexis [1] https://github.com/bootlin/snagboot -- Alexis Lothoré, Bootlin Embedded Linux and Kernel engineering https://bootlin.com

3 3