August 2021 - U-Boot

[PATCH] rpi: Conditionally add simple-framebuffer node
by Ivan T. Ivanov 15 Sep '21

15 Sep '21

It appears that RPi firmware has already added framebuffer node under /chosen, at least on RPi 2 versions. So check for this and don't add duplicate node. Signed-off-by: Ivan T. Ivanov <iivanov(a)suse.de> --- board/raspberrypi/rpi/rpi.c | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/board/raspberrypi/rpi/rpi.c b/board/raspberrypi/rpi/rpi.c index df52a4689f..372b26b6f2 100644 --- a/board/raspberrypi/rpi/rpi.c +++ b/board/raspberrypi/rpi/rpi.c @@ -497,12 +497,11 @@ void *board_fdt_blob_setup(void) int ft_board_setup(void *blob, struct bd_info *bd) { - /* - * For now, we simply always add the simplefb DT node. Later, we - * should be more intelligent, and e.g. only do this if no enabled DT - * node exists for the "real" graphics driver. - */ - lcd_dt_simplefb_add_node(blob); + int node; + + node = fdt_node_offset_by_compatible(blob, -1, "simple-framebuffer"); + if (node < 0) + lcd_dt_simplefb_add_node(blob); #ifdef CONFIG_EFI_LOADER /* Reserve the spin table */ -- 2.32.0

2 2

[PATCH v2 1/2] arm: dts: bcm283x: Add minimal smbios information
by matthias.bgg＠kernel.org 15 Sep '21

15 Sep '21

From: Matthias Brugger <mbrugger(a)suse.com> At present SMBIOS tables are empty, which breaks some use-cases that rely on that. Add some minimal information to fulfill this. Signed-off-by: Matthias Brugger <mbrugger(a)suse.com> --- Changes in v2: - drop product from chassi - fix typo in commit message arch/arm/dts/bcm283x-u-boot.dtsi | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/arch/arm/dts/bcm283x-u-boot.dtsi b/arch/arm/dts/bcm283x-u-boot.dtsi index 68d03627f4..22c67c4218 100644 --- a/arch/arm/dts/bcm283x-u-boot.dtsi +++ b/arch/arm/dts/bcm283x-u-boot.dtsi @@ -6,6 +6,25 @@ * (C) Copyright 2016 Fabian Vogt <fvogt(a)suse.com> */ +/ { + smbios { + compatible = "u-boot,sysinfo-smbios"; + smbios { + system { + manufacturer = "raspberrypi"; + product = "rpi"; + }; + baseboard { + manufacturer = "raspberrypi"; + product = "rpi"; + }; + chassis { + manufacturer = "raspberrypi"; + }; + }; + }; +}; + &uart0 { skip-init; u-boot,dm-pre-reloc; -- 2.30.2

2 2

[PATCH] ARM: bcm283x: change the virtual address of the XHCI PCI device base
by Marek Szyprowski 15 Sep '21

15 Sep '21

Move the XHCI PCI device base up in the virtual address space. This fixes initialization failure observed with newer Raspberry Pi firmware, later than 63b1922311 ("firmware: arm_loader: Update armstubs with those from PR 117). It looks that chosing 0xff800000 as the XHCI PCI device base conflicts with the updated ARM/VideoCore firmware. This also requires to reduce the size of the mapped PCI device region from 8MiB to 4MiB to fit into 32bit address space. This is still enough for the XHCI PCI device. Signed-off-by: Marek Szyprowski <m.szyprowski(a)samsung.com> --- This fixes the issue observed on ARM 32bit after upgrading the RPi4 firmware files, described some time ago here: https://lists.denx.de/pipermail/u-boot/2021-February/442317.html --- arch/arm/mach-bcm283x/init.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-bcm283x/init.c b/arch/arm/mach-bcm283x/init.c index 49027ce0a2..9803499985 100644 --- a/arch/arm/mach-bcm283x/init.c +++ b/arch/arm/mach-bcm283x/init.c @@ -14,7 +14,7 @@ #include <asm/global_data.h> #define BCM2711_RPI4_PCIE_XHCI_MMIO_PHYS 0x600000000UL -#define BCM2711_RPI4_PCIE_XHCI_MMIO_SIZE 0x800000UL +#define BCM2711_RPI4_PCIE_XHCI_MMIO_SIZE 0x400000UL #ifdef CONFIG_ARM64 #include <asm/armv8/mmu.h> @@ -148,7 +148,7 @@ int mach_cpu_init(void) #ifdef CONFIG_ARMV7_LPAE #ifdef CONFIG_TARGET_RPI_4_32B -#define BCM2711_RPI4_PCIE_XHCI_MMIO_VIRT 0xff800000UL +#define BCM2711_RPI4_PCIE_XHCI_MMIO_VIRT 0xffc00000UL #include <addr_map.h> #include <asm/system.h> -- 2.17.1

5 4

[PATCH 1/1] lib/rsa: don't use NULL as key_id
by Heinrich Schuchardt 15 Sep '21

15 Sep '21

If keydir is not provided but name is we want to use name as key_id. But with the current coding name is only used on its own if it is NULL and keydir is provided which never occurs. Fixes: 824ee745fbca ("lib/rsa: Use the 'keyfile' argument from mkimage") Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- lib/rsa/rsa-sign.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/rsa/rsa-sign.c b/lib/rsa/rsa-sign.c index 085dc89bf7..0e0a890fd1 100644 --- a/lib/rsa/rsa-sign.c +++ b/lib/rsa/rsa-sign.c @@ -269,7 +269,7 @@ static int rsa_engine_get_priv_key(const char *keydir, const char *name, snprintf(key_id, sizeof(key_id), "%s%s", keydir, name); - else if (keydir) + else if (name) snprintf(key_id, sizeof(key_id), "%s", name); -- 2.30.2

3 2

[PATCH] image: rsa: Move padding_algos to linker lists
by Alexandru Gagniuc 15 Sep '21

15 Sep '21

We are not guaranteed to have the padding_pkcs_15_verify symbol since commit 92c960bc1d ("lib: rsa: Remove #ifdefs from rsa.h"), and commit 61416fe9df ("Kconfig: FIT_SIGNATURE should not select RSA_VERIFY") The padding_algos only make sense with RSA verification, which can now be disabled in lieu of ECDSA. In fact this will lead to build failures because of the missing symbol mentioned earlier. To resolve this, move the padding_algos to a linker list, with declarations moved to rsa_verify.c. This is consistent with commit 6909edb4ce ("image: rsa: Move verification algorithm to a linker list") One could argue that the added #ifdef USE_HOSTCC is ugly, and should be hidden within the U_BOOT_PADDING_ALGO() macro. However, this would be inconsistent with the "cryptos" list. This logic for was not previously explored: Without knowledge of the U_BOOT_PADDING_ALGO() macro, its use is similar to something being declared. However, should #ifndef USE_HOSTCC be part of the macro, it would not be obvious that it behaves differently on host code and target code. Having the #ifndef outside the macro makes this obvious. Also, the #ifdef is not always necessary. For example ecda-verify makes use of U_BOOT_CRYPTO_ALGO() without any accompanying #ifdefs. The fundamental issue is a lack of separation of host and target code in rsa_verify. Therefore, the declaration of a padding algo with the external #ifdef is more readable and consistent. Signed-off-by: Alexandru Gagniuc <mr.nuke.me(a)gmail.com> --- common/image-sig.c | 23 ++++++----------------- include/image.h | 4 ++++ lib/rsa/rsa-verify.c | 15 +++++++++++++++ 3 files changed, 25 insertions(+), 17 deletions(-) diff --git a/common/image-sig.c b/common/image-sig.c index fb0035524e..fa9407bb30 100644 --- a/common/image-sig.c +++ b/common/image-sig.c @@ -51,19 +51,6 @@ struct checksum_algo checksum_algos[] = { }; -struct padding_algo padding_algos[] = { - { - .name = "pkcs-1.5", - .verify = padding_pkcs_15_verify, - }, -#ifdef CONFIG_FIT_RSASSA_PSS - { - .name = "pss", - .verify = padding_pss_verify, - } -#endif /* CONFIG_FIT_RSASSA_PSS */ -}; - struct checksum_algo *image_get_checksum_algo(const char *full_name) { int i; @@ -129,14 +116,16 @@ struct crypto_algo *image_get_crypto_algo(const char *full_name) struct padding_algo *image_get_padding_algo(const char *name) { - int i; + struct padding_algo *padding, *end; if (!name) return NULL; - for (i = 0; i < ARRAY_SIZE(padding_algos); i++) { - if (!strcmp(padding_algos[i].name, name)) - return &padding_algos[i]; + padding = ll_entry_start(struct padding_algo, paddings); + end = ll_entry_end(struct padding_algo, paddings); + for (; padding < end; padding++) { + if (!strcmp(padding->name, name)) + return padding; } return NULL; diff --git a/include/image.h b/include/image.h index e20f0b69d5..ab0a6c2ef0 100644 --- a/include/image.h +++ b/include/image.h @@ -1334,6 +1334,10 @@ struct padding_algo { const uint8_t *hash, int hash_len); }; +/* Declare a new U-Boot padding algorithm handler */ +#define U_BOOT_PADDING_ALGO(__name) \ +ll_entry_declare(struct padding_algo, __name, paddings) + /** * image_get_checksum_algo() - Look up a checksum algorithm * diff --git a/lib/rsa/rsa-verify.c b/lib/rsa/rsa-verify.c index 3840764e42..ad6d33d043 100644 --- a/lib/rsa/rsa-verify.c +++ b/lib/rsa/rsa-verify.c @@ -95,6 +95,13 @@ int padding_pkcs_15_verify(struct image_sign_info *info, return 0; } +#ifndef USE_HOSTCC +U_BOOT_PADDING_ALGO(pkcs_15) = { + .name = "pkcs-1.5", + .verify = padding_pkcs_15_verify, +}; +#endif + #ifdef CONFIG_FIT_RSASSA_PSS static void u32_i2osp(uint32_t val, uint8_t *buf) { @@ -296,6 +303,14 @@ out: return ret; } + +#ifndef USE_HOSTCC +U_BOOT_PADDING_ALGO(pss) = { + .name = "pss", + .verify = padding_pss_verify, +}; +#endif + #endif #if CONFIG_IS_ENABLED(FIT_SIGNATURE) || CONFIG_IS_ENABLED(RSA_VERIFY_WITH_PKEY) -- 2.31.1

2 1

[PATCH v2 0/6] Call phy_config at port probe time for the Felix DSA driver
by Vladimir Oltean 14 Sep '21

14 Sep '21

Changes in v2: Rebased on top of the master branch (solves this conflict: https://patchwork.ozlabs.org/project/uboot/patch/20210629170839.2583797-4-o… with Tim Harvey's patch to make DSA masters promiscuous) This series makes the Felix DSA driver initialize all its connected PHYs regardless of whether those will be used for networking or not. This is in order to satisfy the expectations of some software in later boot stages. To make this work, it is necessary to introduce a new method in struct dsa_ops: .port_probe(). There is some further refactoring/cleanup along the way. Vladimir Oltean (6): net: dsa: felix: felix_init() can be static net: dsa: use "err" instead of "ret" in dsa_port_probe net: dsa: refactor the code to set the port MAC address into a dedicated function net: dsa: introduce a .port_probe() method in struct dsa_ops net: dsa: felix: call phy_config at .port_probe() time net: dsa: felix: propagate the error code from phy_startup() drivers/net/mscc_eswitch/felix_switch.c | 28 ++++++----- include/net/dsa.h | 5 +- net/dsa-uclass.c | 62 +++++++++++++++---------- 3 files changed, 59 insertions(+), 36 deletions(-) -- 2.25.1

2 12

[PATCH v2 00/32] pci: Drop all pre-driver model code
by Simon Glass 14 Sep '21

14 Sep '21

The hard work to actually enable DM_PCI everywhere was done recently. This series attempts to drop most of the code that it no-longer needed now that PCI has been converted to driver model. It also drops the UCP1020 board since it has various unique build issues. It doesn't even support driver model so it seems reasonable to just remove it. The DM_PCI option disappears and only PCI is left. We can drop about 50 ad-hoc CONFIGs also, but this series doesn't do that since it is probably best done when the CONFIGs are resynced. It does include a CONFIG resync patch which can be dropped if that is done separately. Changes in v2: - Update to mention DM_PCI instead - Fix tag to 'mips' from 'ppc' Simon Glass (32): pci: Drop old code from pci command ppc: Remove UCP1020 board pci: Drop old code from header file pci: Remove guard around compatibility functions pci: Drop DM_PCI check from fdtdec pci: Drop DM_PCI check from pci_common ppc: Drop CONFIG_SYS_PCI_SUBSYS_VENDORID pci: powerpc: Drop old code pci: freescale: Drop old code pci: dm: core: Drop DM_PCI check from devfdt_get_addr_pci() ppc: Drop DM_PCI from config files pci: acpi: Drop DM_PCI check from ahci pci: usb: Drop DM_PCI from ohci ppc: malta: Drop use of DM_PCI ppc: socrates: Drop use of DM_PCI pci: gt64120: Drop use of DM_PCI pci: msc01: Drop use of DM_PCI pci: imx: Drop use of DM_PCI pci: scsi: pci: Drop DM_PCI check from scsi pci: Drop DM_PCI check from bios_emul net: Drop DM_PCI check from designware driver pci: imx: Drop DM_PCI check from cpu driver pci: arm: mvebu: Drop DM_PCI check from pci: sata_sil: Drop DM_PCI checks distro_bootcmd: Drop DM_PCI check pci: Drop pci_init_board() pci: ppc: Drop ftpci100 driver ppc: Drop idt8t49n222a_serdes_clk driver ppc: Drop t4qds and b4860qds references pci: Drop PCI_INDIRECT_BRIDGE pci: Drop DM_PCI pci: Drop migration method .azure-pipelines.yml | 4 +- README | 3 - arch/Kconfig | 1 - arch/arm/Kconfig | 2 +- arch/arm/mach-imx/cpu.c | 4 - arch/arm/mach-imx/mx6/Kconfig | 2 +- arch/arm/mach-mvebu/arm64-common.c | 5 +- arch/mips/Kconfig | 2 +- arch/nds32/include/asm/arch-ag102/ag102.h | 2 - arch/powerpc/cpu/mpc83xx/pci.c | 160 ---- arch/powerpc/cpu/mpc85xx/Makefile | 1 - arch/powerpc/cpu/mpc85xx/pci.c | 191 ---- board/Arcturus/ucp1020/Kconfig | 28 +- board/Arcturus/ucp1020/MAINTAINERS | 7 - board/Arcturus/ucp1020/Makefile | 31 - board/Arcturus/ucp1020/README | 54 -- board/Arcturus/ucp1020/cmd_arc.c | 408 --------- board/Arcturus/ucp1020/ddr.c | 161 ---- board/Arcturus/ucp1020/law.c | 24 - board/Arcturus/ucp1020/spl.c | 127 --- board/Arcturus/ucp1020/spl_minimal.c | 67 -- board/Arcturus/ucp1020/tlb.c | 100 --- board/Arcturus/ucp1020/ucp1020.c | 372 -------- board/Arcturus/ucp1020/ucp1020.h | 45 - board/cavium/thunderx/thunderx.c | 7 - board/emulation/qemu-riscv/Kconfig | 1 - board/freescale/common/Makefile | 1 - board/freescale/common/cds_pci_ft.c | 59 -- .../common/idt8t49n222a_serdes_clk.c | 208 ----- .../common/idt8t49n222a_serdes_clk.h | 106 --- board/freescale/common/p_corenet/Makefile | 1 - board/freescale/common/p_corenet/pci.c | 25 - board/freescale/mpc8349emds/pci.c | 73 -- board/freescale/mpc837xerdb/Makefile | 1 - board/freescale/mpc837xerdb/pci.c | 109 --- board/freescale/mpc8548cds/mpc8548cds.c | 114 --- board/freescale/p1010rdb/p1010rdb.c | 11 - board/freescale/p1_p2_rdb_pc/p1_p2_rdb_pc.c | 11 - board/freescale/t102xrdb/Makefile | 1 - board/freescale/t102xrdb/pci.c | 25 - board/freescale/t104xrdb/Makefile | 1 - board/freescale/t104xrdb/pci.c | 25 - board/freescale/t208xqds/Makefile | 1 - board/freescale/t208xqds/pci.c | 25 - board/freescale/t208xrdb/Makefile | 1 - board/freescale/t208xrdb/pci.c | 25 - board/freescale/t4rdb/Makefile | 1 - board/freescale/t4rdb/pci.c | 25 - board/imgtec/malta/malta.c | 67 -- board/socionext/developerbox/Kconfig | 1 - board/socrates/socrates.c | 4 +- board/xes/common/fsl_8xxx_pci.c | 50 -- cmd/pci.c | 212 ----- common/Kconfig | 1 - configs/UCP1020_defconfig | 58 -- doc/board/freescale/b4860qds.rst | 453 ---------- doc/board/freescale/index.rst | 1 - doc/develop/driver-model/migration.rst | 9 - drivers/ata/ahci.c | 55 -- drivers/ata/sata_sil.c | 8 - drivers/ata/sata_sil.h | 4 - drivers/bios_emulator/atibios.c | 98 --- drivers/bios_emulator/bios.c | 39 - drivers/core/fdtaddr.c | 3 +- drivers/gpio/Kconfig | 2 +- drivers/i2c/Makefile | 2 +- drivers/net/Kconfig | 6 +- drivers/net/designware.c | 22 +- drivers/net/mscc_eswitch/Kconfig | 2 +- drivers/pci/Kconfig | 40 +- drivers/pci/Makefile | 2 - drivers/pci/pci_common.c | 4 +- drivers/pci/pci_ftpci100.c | 319 ------- drivers/pci/pci_gt64120.c | 64 -- drivers/pci/pci_indirect.c | 71 -- drivers/pci/pci_msc01.c | 64 -- drivers/pci/pcie_imx.c | 81 -- drivers/scsi/scsi.c | 6 - drivers/spi/Kconfig | 2 +- drivers/usb/host/ohci-hcd.c | 15 +- drivers/virtio/Kconfig | 2 +- include/ahci.h | 4 - include/bios_emul.h | 16 - include/config_distro_bootcmd.h | 5 - include/configs/MPC8349EMDS.h | 5 - include/configs/MPC8349EMDS_SDRAM.h | 5 - include/configs/MPC837XERDB.h | 3 - include/configs/MPC8540ADS.h | 2 - include/configs/MPC8548CDS.h | 16 - include/configs/MPC8560ADS.h | 2 - include/configs/P1010RDB.h | 28 - include/configs/P2041RDB.h | 17 - include/configs/T102xRDB.h | 17 - include/configs/T104xRDB.h | 20 - include/configs/T208xQDS.h | 20 - include/configs/T208xRDB.h | 20 - include/configs/T4240RDB.h | 21 - include/configs/UCP1020.h | 832 ------------------ include/configs/corenet_ds.h | 21 - include/configs/p1_p2_rdb_pc.h | 24 - include/configs/t4qds.h | 240 ----- include/init.h | 3 - include/pci.h | 76 +- lib/fdtdec.c | 10 +- scripts/config_whitelist.txt | 6 - test/dm/Makefile | 2 +- 106 files changed, 55 insertions(+), 5785 deletions(-) delete mode 100644 arch/powerpc/cpu/mpc85xx/pci.c delete mode 100644 board/Arcturus/ucp1020/MAINTAINERS delete mode 100644 board/Arcturus/ucp1020/Makefile delete mode 100644 board/Arcturus/ucp1020/README delete mode 100644 board/Arcturus/ucp1020/cmd_arc.c delete mode 100644 board/Arcturus/ucp1020/ddr.c delete mode 100644 board/Arcturus/ucp1020/law.c delete mode 100644 board/Arcturus/ucp1020/spl.c delete mode 100644 board/Arcturus/ucp1020/spl_minimal.c delete mode 100644 board/Arcturus/ucp1020/tlb.c delete mode 100644 board/Arcturus/ucp1020/ucp1020.c delete mode 100644 board/Arcturus/ucp1020/ucp1020.h delete mode 100644 board/freescale/common/idt8t49n222a_serdes_clk.c delete mode 100644 board/freescale/common/idt8t49n222a_serdes_clk.h delete mode 100644 board/freescale/common/p_corenet/pci.c delete mode 100644 board/freescale/mpc837xerdb/pci.c delete mode 100644 board/freescale/t102xrdb/pci.c delete mode 100644 board/freescale/t104xrdb/pci.c delete mode 100644 board/freescale/t208xqds/pci.c delete mode 100644 board/freescale/t208xrdb/pci.c delete mode 100644 board/freescale/t4rdb/pci.c delete mode 100644 configs/UCP1020_defconfig delete mode 100644 doc/board/freescale/b4860qds.rst delete mode 100644 drivers/pci/pci_ftpci100.c delete mode 100644 drivers/pci/pci_indirect.c delete mode 100644 include/configs/UCP1020.h delete mode 100644 include/configs/t4qds.h -- 2.32.0.554.ge1b32706d8-goog

3 72

[PATCH v7 0/5] Add SIMATIC IOT2050 board support
by Jan Kiszka 13 Sep '21

13 Sep '21

This is the baseline support for the SIMATIC IOT2050 devices. Changes in v7: - rebased - registered board doc with index Changes in v6: - rebased - converted board README to docs/board/siemens/iot2050.rst Changes in v5: - rebased - use DEFAULT_LINUX_BOOT_ENV from ti_armv7_common.h, rather than home-grown values - avoids misaligned kernel load address - no longer exposes issue around LMB reservations Changes in v4: - rebased - make rtd-wdt firmware a "loadable" inside U-Boot proper fit image, avoiding controversial embedding as object - improved mmc1 removal from boot_targets - fixed various build issues Changes in v3: - rebased - addressed several checkpatch warnings - a few #ifdef -> IS_ENABLED conversions - comment marker for SPDK identifier in .S file - trailing whitespaces - factored out rti_wdt_load_fw (less #ifdef) Changes in v2: - rebased - sync with upstream-accepted DT - add boot switch - include watchdog support Allows to boot mainline 5.10 kernels, but not the original BSP-derived kernel we currently ship as reference. This is due to the TI sysfw ABI breakages between 2.x and 3.x. We will soon provide a transitional kernel that allows booting both firmware ABIs - as long as full upstream kernel support is work in progress. Note that this baseline support lacks Ethernet drivers. We are working closely with TI to ensure that the to-be-upstreamed icssg-prueth driver will work both with new SR2.0 AM65x silicon as well as with SR1.0 which is used in the currently shipped IOT2050 devices. A staging tree for complete IOT2050 support can be found at [1]. Full image integration is available via [2]. Jan [1] https://github.com/siemens/u-boot/commits/jan/iot2050 [2] https://github.com/siemens/meta-iot2050 Jan Kiszka (5): arm: dts: Add IOT2050 device tree files board: siemens: Add support for SIMATIC IOT2050 devices arm64: dts: ti: k3-am65-mcu: Add RTI watchdog entry watchdog: rti_wdt: Add support for loading firmware iot2050: Enable watchdog support, but do not auto-start it arch/arm/dts/Makefile | 7 +- arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 121 ++++ .../dts/k3-am65-iot2050-common-u-boot.dtsi | 103 +++ arch/arm/dts/k3-am65-iot2050-common.dtsi | 655 ++++++++++++++++++ arch/arm/dts/k3-am65-iot2050-spl.dts | 16 + arch/arm/dts/k3-am65-mcu.dtsi | 9 + arch/arm/dts/k3-am6528-iot2050-basic.dts | 67 ++ arch/arm/dts/k3-am6548-iot2050-advanced.dts | 66 ++ arch/arm/mach-k3/Kconfig | 1 + board/siemens/iot2050/Kconfig | 32 + board/siemens/iot2050/MAINTAINERS | 9 + board/siemens/iot2050/Makefile | 10 + board/siemens/iot2050/board.c | 284 ++++++++ board/siemens/iot2050/config.mk | 8 + configs/iot2050_defconfig | 138 ++++ doc/board/index.rst | 1 + doc/board/siemens/index.rst | 9 + doc/board/siemens/iot2050.rst | 76 ++ drivers/watchdog/Kconfig | 20 + drivers/watchdog/rti_wdt.c | 88 +++ include/configs/iot2050.h | 62 ++ 21 files changed, 1781 insertions(+), 1 deletion(-) create mode 100644 arch/arm/dts/k3-am65-iot2050-boot-image.dtsi create mode 100644 arch/arm/dts/k3-am65-iot2050-common-u-boot.dtsi create mode 100644 arch/arm/dts/k3-am65-iot2050-common.dtsi create mode 100644 arch/arm/dts/k3-am65-iot2050-spl.dts create mode 100644 arch/arm/dts/k3-am6528-iot2050-basic.dts create mode 100644 arch/arm/dts/k3-am6548-iot2050-advanced.dts create mode 100644 board/siemens/iot2050/Kconfig create mode 100644 board/siemens/iot2050/MAINTAINERS create mode 100644 board/siemens/iot2050/Makefile create mode 100644 board/siemens/iot2050/board.c create mode 100644 board/siemens/iot2050/config.mk create mode 100644 configs/iot2050_defconfig create mode 100644 doc/board/siemens/index.rst create mode 100644 doc/board/siemens/iot2050.rst create mode 100644 include/configs/iot2050.h -- 2.31.1

3 15

Bug: qemu_arm64: Cannot access the second flash bank
by Robin Randhawa 13 Sep '21

13 Sep '21

Hi folks. [CC'ing some hopefully relevant folks]. As of: commit 0ba41ce1b7816c229cc19e0621148b98f990cb68 libfdt: return correct value if #size-cells property is not present .. accesses to the second flash bank on the qemu_arm64 virtual board appear broken. To demonstrate, consider that the physical memory map for the 2 flash banks is: Bank 1: 0x0000_0000 - 0x03FC_0000 Bank 2: 0x0400_0000 - 0x7FC0_0000 Now, consider the abbreviated output of the flinfo command pre and post the above commit: Pre: === => flinfo Bank # 1: CFI conformant flash (32 x 16) Size: 64 MB in 256 Sectors Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x0018 Erase timeout: 16384 ms, write timeout: 3 ms Buffer write timeout: 3 ms, buffer size: 2048 bytes Sector Start Addresses: 00000000 RO 00040000 RO 00080000 RO 000C0000 00100000 00140000 00180000 001C0000 00200000 00240000 . . 03E80000 03EC0000 03F00000 03F40000 03F80000 03FC0000 Bank # 2: CFI conformant flash (32 x 16) Size: 64 MB in 256 Sectors Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x0018 Erase timeout: 16384 ms, write timeout: 3 ms Buffer write timeout: 3 ms, buffer size: 2048 bytes Sector Start Addresses: 04000000 RO 04040000 04080000 040C0000 04100000 04140000 04180000 041C0000 04200000 04240000 . . 07E80000 07EC0000 07F00000 07F40000 07F80000 07FC0000 Post: ==== => flinfo Bank # 1: CFI conformant flash (32 x 16) Size: 64 MB in 256 Sectors Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x0018 Erase timeout: 16384 ms, write timeout: 3 ms Buffer write timeout: 3 ms, buffer size: 2048 bytes Sector Start Addresses: 00000000 RO 00040000 RO 00080000 RO 000C0000 00100000 00140000 00180000 001C0000 00200000 00240000 . . 03E80000 03EC0000 03F00000 03F40000 03F80000 03FC0000 Bank # 2: CFI conformant flash (32 x 16) Size: 64 MB in 256 Sectors Intel Extended command set, Manufacturer ID: 0x89, Device ID: 0x0018 Erase timeout: 16384 ms, write timeout: 3 ms Buffer write timeout: 3 ms, buffer size: 2048 bytes Sector Start Addresses: 400000000000000 400000000040000 400000000080000 4000000000C0000 400000000100000 400000000140000 400000000180000 4000000001C0000 400000000200000 400000000240000 . . 400000003E80000 400000003EC0000 400000003F00000 40 0000003F40000 400000003F80000 400000003FC0000 As a result, the second bank is unusable for environment stores (CONFIG_ENV_ADDR is 0x4000000): => saveenv Saving Environment to Flash... Error: start and/or end address not on sector boundary Error: start and/or end address not on sector boundary Failed (1) Rewinding the u-boot repo to before this commit fixes the problem. Manually (uncleanly) reverting the commit and it's dependent commits fixes the problem. Here are the HEAD commits from the relevant repos that I used for the data above: qemu: commit dd5b0f95490883cd8bc7d070db8de70d5c979cbc u-boot: commit 6cb87cbb1475f668689f95911d1521ee6ba7f55c Here is the qemu invocation I used: $ dd if=/dev/zero of=./flash0-with-uboot.img bs=1M count=64 && dd if=/path/to/u-boot.bin of=./flash0-with-uboot.img conv=notrunc $ qemu-system-aarch64 -M virt -cpu cortex-a53 -m 1024M -nographic -drive if=pflash,format=raw,index=0,file=flash0-with-uboot.img -drive if=pflash,format=raw,index=1,file=flash1.img I'm happy to help test any fixes if and as needed. Cheers, Robin

3 9

[PATCH] board: atmel: sama7g5ek: avoid rewriting of configured CONFIG_BOOTCOMMAND
by Eugen Hristev 13 Sep '21

13 Sep '21

Rewrite the CONFIG_BOOTCOMMAND only if it's not previously configured from defconfig file. This allows the user to select from defconfig/menuconfig the desired boot command. Adjust the current board defconfigs to reflect the default booting command for the specific ENV configuration. Signed-off-by: Eugen Hristev <eugen.hristev(a)microchip.com> --- configs/sama7g5ek_mmc1_defconfig | 2 ++ configs/sama7g5ek_mmc_defconfig | 2 ++ include/configs/sama7g5ek.h | 6 +++++- 3 files changed, 9 insertions(+), 1 deletion(-) diff --git a/configs/sama7g5ek_mmc1_defconfig b/configs/sama7g5ek_mmc1_defconfig index e076e07e11..a78adf0dd8 100644 --- a/configs/sama7g5ek_mmc1_defconfig +++ b/configs/sama7g5ek_mmc1_defconfig @@ -18,6 +18,8 @@ CONFIG_FIT=y CONFIG_SD_BOOT=y CONFIG_USE_BOOTARGS=y CONFIG_BOOTARGS="console=ttyS0,115200 root=/dev/mmcblk1p2 rw rootwait" +CONFIG_USE_BOOTCOMMAND=y +CONFIG_BOOTCOMMAND="fatload mmc 1:1 0x61000000 at91-sama7g5ek.dtb; fatload mmc 1:1 0x62000000 zImage; bootz 0x62000000 - 0x61000000" CONFIG_MISC_INIT_R=y CONFIG_HUSH_PARSER=y CONFIG_CMD_BOOTZ=y diff --git a/configs/sama7g5ek_mmc_defconfig b/configs/sama7g5ek_mmc_defconfig index 96549c23f8..de845178e6 100644 --- a/configs/sama7g5ek_mmc_defconfig +++ b/configs/sama7g5ek_mmc_defconfig @@ -18,6 +18,8 @@ CONFIG_FIT=y CONFIG_SD_BOOT=y CONFIG_USE_BOOTARGS=y CONFIG_BOOTARGS="console=ttyS0,115200 root=/dev/mmcblk0p2 rw rootwait" +CONFIG_USE_BOOTCOMMAND=y +CONFIG_BOOTCOMMAND="fatload mmc 0:1 0x61000000 at91-sama7g5ek.dtb; fatload mmc 0:1 0x62000000 zImage; bootz 0x62000000 - 0x61000000" CONFIG_MISC_INIT_R=y CONFIG_HUSH_PARSER=y CONFIG_CMD_BOOTZ=y diff --git a/include/configs/sama7g5ek.h b/include/configs/sama7g5ek.h index 96db82e9d4..07e14ff507 100644 --- a/include/configs/sama7g5ek.h +++ b/include/configs/sama7g5ek.h @@ -26,7 +26,7 @@ #define CONFIG_SYS_LOAD_ADDR 0x62000000 /* load address */ -#undef CONFIG_BOOTCOMMAND +#ifndef CONFIG_BOOTCOMMAND #ifdef CONFIG_SD_BOOT /* u-boot env in sd/mmc card */ @@ -34,6 +34,10 @@ #define CONFIG_BOOTCOMMAND "fatload mmc " CONFIG_ENV_FAT_DEVICE_AND_PART " 0x61000000 at91-sama7g5ek.dtb; " \ "fatload mmc " CONFIG_ENV_FAT_DEVICE_AND_PART " 0x62000000 zImage; " \ "bootz 0x62000000 - 0x61000000" +#else +#define CONFIG_BOOTCOMMAND "Place your bootcommand here" +#endif + #endif /* Size of malloc() pool */ -- 2.25.1

2 1