September 2023 - U-Boot

sandbox trace errors in CI loop
by Michal Simek 11 Sep '23

11 Sep '23

Hi Simon and Tom, I am preparing pull request and I see that CI loop is reporting issue with sandbox trace and I have no idea what's going wrong here. This is the first problematic commit but have no clue what it has to do with trace. https://source.denx.de/u-boot/custodians/u-boot-microblaze/-/commit/8c5f80d… If you have an access you can take a look at my queue to see that only this job is failing. https://source.denx.de/u-boot/custodians/u-boot-microblaze/-/pipelines Thanks, Michal collected 1152 items / 1151 deselected / 1 selected test/py/tests/test_trace.py F [100%] =================================== FAILURES =================================== __________________________________ test_trace __________________________________ test/py/tests/test_trace.py:292: in test_trace check_function(cons, fname, proftool, map_fname, trace_dat) test/py/tests/test_trace.py:117: in check_function out = util.run_and_log(cons, ['sh', '-c', cmd]) test/py/u_boot_utils.py:181: in run_and_log output = runner.run(cmd, ignore_errors=ignore_errors, stdin=stdin, env=env) test/py/multiplexed_log.py:183: in run raise exception E ValueError: Exit code: 1 ---------------------------- Captured stdout setup ----------------------------- /u-boot trace: early enable at 00100000 sandbox_serial serial: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 => ----------------------------- Captured stdout call ----------------------------- => Call list dumped to 02000000, size 0xde3b30 => +/tmp/sandbox/tools/proftool -t /tmp/test_trace/trace -o /tmp/test_trace/trace.dat -m /tmp/sandbox/System.map dump-ftrace 9842 functions found in map file, start addr 3e000 call count: 1213676 +trace-cmd dump /tmp/test_trace/trace.dat Tracing meta data in file /tmp/test_trace/trace.dat: [Initial format] 6 [Version] 0 [Little endian] 4 [Bytes in a long] 4096 [Page size, bytes] [Header page, 205 bytes] [Header event, 205 bytes] [Ftrace format, 3 events] [Events format, 0 systems] [Kallsyms, 370293 bytes] [Trace printk, 0 bytes] [Saved command lines, 9 bytes] 1 [CPUs with tracing data] [6 options] [Flyrecord tracing data] [Tracing clock] [local] global counter uptime perf mono mono_raw boot x86-tsc +sh -c trace-cmd report /tmp/test_trace/trace.dat |grep -E '(initf_|initr_)' failed to init data Exit code: 1 =========================== short test summary info ============================ FAILED test/py/tests/test_trace.py::test_trace - ValueError: Exit code: 1 ====================== 1 failed, 1151 deselected in 3.32s ====================== -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP/Versal ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal/Versal NET SoCs TF-A maintainer - Xilinx ZynqMP/Versal/Versal NET SoCs

3 6

[PATCH] binman: doc: fix reference tag placement for Logging section
by Massimo Pegorer 10 Sep '23

10 Sep '23

Move BinmanLogging reference tag after section "Signing FIT container with private key in an image" and just before section "Logging". Fixes: 0f40e23fd22 ("binman: add documentation for binman sign option") Signed-off-by: Massimo Pegorer <massimo.pegorer+oss(a)gmail.com> --- Note that at the end of section "Replacing files in an image" and just before section "Signing FIT container with private key in an image" there is a line which seems a typo or an incomplete sentence: Repacking an image involves --- tools/binman/binman.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst index aeea33fddb..8945b19446 100644 --- a/tools/binman/binman.rst +++ b/tools/binman/binman.rst @@ -1482,7 +1482,6 @@ when it was created. Repacking an image involves -.. _`BinmanLogging`: Signing FIT container with private key in an image -------------------------------------------------- @@ -1501,6 +1500,7 @@ If you want to sign and replace FIT container in place:: which will sign FIT container with private key and replace it immediately inside your image. +.. _`BinmanLogging`: Logging ------- -- 2.34.1

3 3

[PATCH v1] doc: Update path to source_file_format.rst
by Joao Marcos Costa 10 Sep '23

10 Sep '23

Previously, the file extension was .txt, and it referenced the uImage.FIT directory, which no longer exists. This commit updates the path accordingly. Signed-off-by: Joao Marcos Costa <jmcosta944(a)gmail.com> --- doc/usage/fit/howto.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/usage/fit/howto.rst b/doc/usage/fit/howto.rst index c933703d1d..8b38cd534d 100644 --- a/doc/usage/fit/howto.rst +++ b/doc/usage/fit/howto.rst @@ -22,7 +22,7 @@ for its latest version. mkimage (together with dtc) takes as input an image source file, which describes the contents of the image and defines its various properties used during booting. By convention, image source file has the ".its" extension, also, the details of its format are given in -doc/uImage.FIT/source_file_format.txt. The actual data that is to be included in +doc/usage/fit/source_file_format.rst. The actual data that is to be included in the uImage (kernel, ramdisk, etc.) is specified in the image source file in the form of paths to appropriate data files. The outcome of the image creation process is a binary file (by convention with the ".itb" extension) that -- 2.41.0

3 2

[PATCH] tpm: Fix autostart for TPM1.2 devices
by Ilias Apalodimas 10 Sep '23

10 Sep '23

On commit e663b2ff4ba2("tpm: Add 'tpm autostart' shell command") an autostart function was added for both TPM1.2 and 2.0 devices. Instead of correctly wiring the autostart command for TPM1.2 devices that patch mistakenly added it on 'tpm init' Fixes: commit e663b2ff4ba2("tpm: Add 'tpm autostart' shell command") Signed-off-by: Ilias Apalodimas <ilias.apalodimas(a)linaro.org> --- cmd/tpm-v1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/tpm-v1.c b/cmd/tpm-v1.c index 3b95c950cc96..1b1efcd204d2 100644 --- a/cmd/tpm-v1.c +++ b/cmd/tpm-v1.c @@ -655,7 +655,7 @@ TPM_COMMAND_NO_ARG(tpm_physical_disable) static struct cmd_tbl tpm1_commands[] = { U_BOOT_CMD_MKENT(device, 0, 1, do_tpm_device, "", ""), U_BOOT_CMD_MKENT(info, 0, 1, do_tpm_info, "", ""), - U_BOOT_CMD_MKENT(init, 0, 1, do_tpm_autostart, "", ""), + U_BOOT_CMD_MKENT(autostart, 0, 1, do_tpm_autostart, "", ""), U_BOOT_CMD_MKENT(init, 0, 1, do_tpm_init, "", ""), U_BOOT_CMD_MKENT(startup, 0, 1, do_tpm_startup, "", ""), -- 2.37.2

3 2

[PATCH v1] CI: Add jsonschema python module
by Andrejs Cainikovs 10 Sep '23

10 Sep '23

Some TI boards utilizes `ti-board-config` via binman device tree node, which when built via binman, triggers schema validation for board specific yaml configuration files. This change adds jsonschema python module to CI Docker image, which allows these targets to be built by CI without errors. Signed-off-by: Andrejs Cainikovs <andrejs.cainikovs(a)toradex.com> --- tools/docker/Dockerfile | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/docker/Dockerfile b/tools/docker/Dockerfile index 3d2b64a355f..2f3121ffcf6 100644 --- a/tools/docker/Dockerfile +++ b/tools/docker/Dockerfile @@ -98,6 +98,7 @@ RUN apt-get update && apt-get install -y \ python2.7 \ python3 \ python3-dev \ + python3-jsonschema \ python3-pip \ python3-pyelftools \ python3-sphinx \ -- 2.34.1

3 4

[PULL] u-boot-sh/next_ufs
by Marek Vasut 10 Sep '23

10 Sep '23

The following changes since commit 515e0af77b25fba24ef6a3c72afee6ae3c739825: Merge branch '2023-09-06-assorted-CI-updates' into next (2023-09-06 18:47:18 -0400) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-sh.git next_ufs for you to fetch changes up to fad9d9b70113bda05b5339d0193adc4edd3ca0e9: ufs: ufs-renesas: Drop include common.h (2023-09-09 04:56:50 +0200) ---------------------------------------------------------------- Marek Vasut (4): clk: Add GPIO-controlled clock gate driver ufs: ufs-renesas: Add support for Renesas R-Car UFS controller ARM: renesas: Enable UFS on R8A779F0 S4 Spider ufs: ufs-renesas: Drop include common.h configs/r8a779f0_spider_defconfig | 11 + drivers/clk/Kconfig | 13 ++ drivers/clk/Makefile | 1 + drivers/clk/clk-gpio.c | 66 ++++++ drivers/ufs/Kconfig | 9 + drivers/ufs/Makefile | 1 + drivers/ufs/ufs-renesas.c | 412 ++++++++++++++++++++++++++++++++++++++ 7 files changed, 513 insertions(+) create mode 100644 drivers/clk/clk-gpio.c create mode 100644 drivers/ufs/ufs-renesas.c

2 1

Pull request doc-2023-10-rc5
by Heinrich Schuchardt 10 Sep '23

10 Sep '23

Dear Tom, The following changes since commit c0c08be5468cb26db597932bc69c4eda1129841d: Merge branch 'master' of https://gitlab.denx.de/u-boot/custodians/u-boot-usb (2023-09-05 14:44:10 -0400) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-efi.git tags/doc-2023-10-rc5 for you to fetch changes up to 7314ba2bf8452df68d07f251aa59440de58067b0: doc: board: ti: Move documentation from README to .rst (2023-09-09 06:12:47 +0200) Gitlab CI showed no issues: https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/17697 ---------------------------------------------------------------- Pull request doc-2023-10-rc5 Documentation: * move more TI board documentation to HTML * update TPM usage instructions for qemu-arm * update the EFI app documentation Other: * tpm: Fix autostart for TPM1.2 devices * spl: fix undefined return value in spl_blk_load_image ---------------------------------------------------------------- Heinrich Schuchardt (2): spl: undefined return value in spl_blk_load_image timer: document the unit of the timer rate Ilias Apalodimas (2): tpm: Fix autostart for TPM1.2 devices doc: qemu: switch swtpm instruction to 'tpm autostart' Joao Marcos Costa (1): doc: Update path to source_file_format.rst Neha Malcom Francis (1): doc: board: ti: Move documentation from README to .rst Simon Glass (1): doc: efi: Update for the 64-bit app board/ti/dra7xx/README | 26 --- board/ti/ks2_evm/README | 194 ---------------- cmd/tpm-v1.c | 2 +- common/spl/spl_blk_fs.c | 2 +- doc/README.ti-secure | 226 ------------------- doc/SPI/README.ti_qspi_am43x_test | 76 ------- doc/SPI/README.ti_qspi_dra_test | 47 ---- doc/SPI/README.ti_qspi_flash | 47 ---- doc/board/emulation/qemu-arm.rst | 2 +- doc/board/ti/am335x_evm.rst | 437 ++++++++++++++++++++++++++++--------- doc/board/ti/am43xx_evm.rst | 188 ++++++++++++++++ doc/board/ti/dra7xx_evm.rst | 139 ++++++++++++ doc/board/ti/index.rst | 3 + doc/board/ti/ks2_evm.rst | 306 ++++++++++++++++++++++++++ doc/develop/uefi/u-boot_on_efi.rst | 26 +-- doc/usage/fit/howto.rst | 4 +- include/timer.h | 6 +- 17 files changed, 984 insertions(+), 747 deletions(-) delete mode 100644 board/ti/dra7xx/README delete mode 100644 board/ti/ks2_evm/README delete mode 100644 doc/README.ti-secure delete mode 100644 doc/SPI/README.ti_qspi_am43x_test delete mode 100644 doc/SPI/README.ti_qspi_dra_test delete mode 100644 doc/SPI/README.ti_qspi_flash create mode 100644 doc/board/ti/am43xx_evm.rst create mode 100644 doc/board/ti/dra7xx_evm.rst create mode 100644 doc/board/ti/ks2_evm.rst

3 2

[PATCH] expo: Fix documentation reference
by Massimo Pegorer 10 Sep '23

10 Sep '23

Fix typo: doc/develop/expo.rst instead of doc/developer/expo.rst Signed-off-by: Massimo Pegorer <massimo.pegorer+oss(a)gmail.com> --- boot/expo_build.c | 6 +++--- include/expo.h | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/boot/expo_build.c b/boot/expo_build.c index 22f62eb54b..702bf49890 100644 --- a/boot/expo_build.c +++ b/boot/expo_build.c @@ -209,7 +209,7 @@ static void list_strings(struct build_info *info) /** * menu_build() - Build a menu and add it to a scene * - * See doc/developer/expo.rst for a description of the format + * See doc/develop/expo.rst for a description of the format * * @info: Build information * @node: Node containing the menu description @@ -282,7 +282,7 @@ static int menu_build(struct build_info *info, ofnode node, struct scene *scn) /** * menu_build() - Build an expo object and add it to a scene * - * See doc/developer/expo.rst for a description of the format + * See doc/develop/expo.rst for a description of the format * * @info: Build information * @node: Node containing the object description @@ -318,7 +318,7 @@ static int obj_build(struct build_info *info, ofnode node, struct scene *scn) /** * scene_build() - Build a scene and all its objects * - * See doc/developer/expo.rst for a description of the format + * See doc/develop/expo.rst for a description of the format * * @info: Build information * @node: Node containing the scene description diff --git a/include/expo.h b/include/expo.h index 0b1d944a16..e8f7d7d6ff 100644 --- a/include/expo.h +++ b/include/expo.h @@ -667,7 +667,7 @@ int expo_apply_theme(struct expo *exp, ofnode node); * * Build a complete expo from a description in the provided devicetree. * - * See doc/developer/expo.rst for a description of the format + * See doc/develop/expo.rst for a description of the format * * @root: Root node for expo description * @expp: Returns the new expo -- 2.34.1

2 1

[PATCH] doc: delete unused values kernel command line
by Jaewon Jung 09 Sep '23

09 Sep '23

Delete "boot=local", "noswap" unused values in kernel command line Signed-off-by: Jaewon Jung <jw.jung(a)navercorp.com> --- doc/board/google/chromebook_coral.rst | 4 ++-- doc/usage/cmd/bootflow.rst | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/board/google/chromebook_coral.rst b/doc/board/google/chromebook_coral.rst index 23e2db4556..1ee634c6c2 100644 --- a/doc/board/google/chromebook_coral.rst +++ b/doc/board/google/chromebook_coral.rst @@ -88,7 +88,7 @@ Here is the console output:: Net: No ethernet found. SF: Detected w25q128fw with page size 256 Bytes, erase size 4 KiB, total 16 MiB Hit any key to stop autoboot: 0 - cmdline=console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=PARTUUID=${uuid}/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none rw 1,0 3788800 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=3788800 alg=sha1 root_hexdigest=55052b629d3ac889f25a9583ea12cdcd3ea15ff8 salt=a2d4d9e574069f4fed5e3961b99054b7a4905414b60a25d89974a7334021165c" noinitrd vt.global_cursor_default=0 kern_guid=${uuid} add_efi_memmap boot=local noresume noswap i915.modeset=1 Kernel command line: "console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=PARTUUID=35c775e7-3735-d745-93e5-d9e0238f7ed0/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none rw 1,0 3788800 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=3788800 alg=sha1 root_hexdigest=55052b629d3ac889f25a9583ea12cdcd3ea15ff8 salt=a2d4d9e574069f4fed5e3961b99054b7a4905414b60a25d89974a7334021165c" noinitrd vt.global_cursor_default=0 kern_guid=35c775e7-3735-d745-93e5-d9e0238f7ed0 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic disablevmx=off " + cmdline=console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=PARTUUID=${uuid}/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none rw 1,0 3788800 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=3788800 alg=sha1 root_hexdigest=55052b629d3ac889f25a9583ea12cdcd3ea15ff8 salt=a2d4d9e574069f4fed5e3961b99054b7a4905414b60a25d89974a7334021165c" noinitrd vt.global_cursor_default=0 kern_guid=${uuid} add_efi_memmap noresume i915.modeset=1 Kernel command line: "console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=PARTUUID=35c775e7-3735-d745-93e5-d9e0238f7ed0/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none rw 1,0 3788800 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=3788800 alg=sha1 root_hexdigest=55052b629d3ac889f25a9583ea12cdcd3ea15ff8 salt=a2d4d9e574069f4fed5e3961b99054b7a4905414b60a25d89974a7334021165c" noinitrd vt.global_cursor_default=0 kern_guid=35c775e7-3735-d745-93e5-d9e0238f7ed0 add_efi_memmap noresume i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic disablevmx=off " Setup located at 00090000: ACPI RSDP addr : 7991f000 @@ -136,7 +136,7 @@ Here is the console output:: Ext loader ver : 0 Ext loader type : 0 Command line ptr : 99000 - console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=PARTUUID=35c775e7-3735-d745-93e5-d9e0238f7ed0/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none rw 1,0 3788800 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=3788800 alg=sha1 root_hexdigest=55052b629d3ac889f25a9583ea12cdcd3ea15ff8 salt=a2d4d9e574069f4fed5e3961b99054b7a4905414b60a25d89974a7334021165c" noinitrd vt.global_cursor_default=0 kern_guid=35c775e7-3735-d745-93e5-d9e0238f7ed0 add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic disablevmx=off + console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=PARTUUID=35c775e7-3735-d745-93e5-d9e0238f7ed0/PARTNROFF=1 rootwait rw dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=0 dm="1 vroot none rw 1,0 3788800 verity payload=ROOT_DEV hashtree=HASH_DEV hashstart=3788800 alg=sha1 root_hexdigest=55052b629d3ac889f25a9583ea12cdcd3ea15ff8 salt=a2d4d9e574069f4fed5e3961b99054b7a4905414b60a25d89974a7334021165c" noinitrd vt.global_cursor_default=0 kern_guid=35c775e7-3735-d745-93e5-d9e0238f7ed0 add_efi_memmap noresume i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic disablevmx=off Initrd addr max : 7fffffff Kernel alignment : 200000 Relocatable kernel : 1 diff --git a/doc/usage/cmd/bootflow.rst b/doc/usage/cmd/bootflow.rst index a8af1f8f60..65e3777cdc 100644 --- a/doc/usage/cmd/bootflow.rst +++ b/doc/usage/cmd/bootflow.rst @@ -495,8 +495,8 @@ the cmdline is word-wrapped here and some parts of the command line are elided:: root_hexdigest=78cc462cd45aecbcd49ca476587b4dee59aa1b00ba5ece58e2c29ec9acd914ab salt=8dec4dc80a75dd834a9b3175c674405e15b16a253fdfe05c79394ae5fd76f66a" noinitrd vt.global_cursor_default=0 - kern_guid=799c935b-ae62-d143-8493-816fa936eef7 add_efi_memmap boot=local - noresume noswap i915.modeset=1 ramoops.ecc=1 tpm_tis.force=0 + kern_guid=799c935b-ae62-d143-8493-816fa936eef7 add_efi_memmap + noresume i915.modeset=1 ramoops.ecc=1 tpm_tis.force=0 intel_pmc_core.warn_on_s0ix_failures=1 i915.enable_guc=3 i915.enable_dc=4 xdomain=0 swiotlb=65536 intel_iommu=on i915.enable_psr=1 usb-storage.quirks=13fe:6500:u -- 2.17.1

2 1

[PATCH 1/1] Watchdog: Support WDIOF_CARDRESET on TI AM65x platform
by huaqian.li＠siemens.com 09 Sep '23

09 Sep '23

From: Li Hua Qian <huaqian.li(a)siemens.com> To have the WDIOF_CARDRESET support for the TI AM65x platform watchdog, this patch reserves some memories, which indicate if the current boot due to a watchdog reset. Signed-off-by: Li Hua Qian <huaqian.li(a)siemens.com> --- Here is the Kernel Reviewed-by Submission: https://lore.kernel.org/all/20230718021007.1338761-1-huaqian.li@siemens.com/ arch/arm/dts/k3-am65-iot2050-common.dtsi | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/dts/k3-am65-iot2050-common.dtsi b/arch/arm/dts/k3-am65-iot2050-common.dtsi index 65da226847..b6135b849f 100644 --- a/arch/arm/dts/k3-am65-iot2050-common.dtsi +++ b/arch/arm/dts/k3-am65-iot2050-common.dtsi @@ -64,6 +64,12 @@ alignment = <0x1000>; no-map; }; + + /* To reserve the power-on(PON) reason for watchdog reset */ + wdt_reset_memory_region: wdt-memory@a2200000 { + reg = <0x00 0xa2200000 0x00 0x00001000>; + no-map; + }; }; leds { @@ -720,6 +726,11 @@ mboxes = <&mailbox0_cluster1 &mbox_mcu_r5fss0_core1>; }; +&mcu_rti1 { + memory-region = <&wdt_reset_memory_region>; + +}; + &icssg0_mdio { status = "disabled"; }; -- 2.34.1

2 1