u-boot.git/doc/board/ti, branch next

tools: fit: sign all config image references

2026-08-25T23:12:40Z

Target-side configuration verification builds the signed-region list from every image-reference property in the selected configuration. Host-side signing still uses either the signature node sign-images property or the legacy kernel/fdt/script default list. This lets mkimage generate configuration signatures which U-Boot cannot verify when the configuration references other image types, such as firmware, loadables or ramdisk entries. It also lets the host and target disagree when sign-images names only a subset of the configuration images. Build the host-side signing list from the configuration properties in the same way as target-side verification. Use one shared property classifier so the host and target cannot drift apart again. This makes signed configurations cover the root node, the configuration node, every referenced image node, and its hash, cipher and dm-verity subnodes, regardless of image type. Warn when a legacy sign-images property is present, since it no longer limits the signed image list. Require every referenced image to have at least one hash subnode. Add sandbox coverage proving that a firmware reference omitted from sign-images is still recorded in hashed-nodes and verified. Update the signed-configuration documentation to describe the same rule and the hash-subnode requirement. Fixes: 2092322b31cc ("boot: Add fit_config_get_hash_list() to build signed node list") Signed-off-by: James Hilliard Reviewed-by: Simon Glass

doc: ti: k3: Fix pseudo DTS syntax

2026-08-22T21:58:05Z

The code block does not use valid DTS syntax, but rather a pseudo DTS syntax. Sphinx complains about this, so fix the syntax. " doc/board/ti/k3.rst:467: WARNING: Lexing literal_block '/dts-v1/;...};' as "dts" resulted in an error at token: 'i'. Retrying in relaxed mode. [misc.highlighting_failure] " Signed-off-by: Marek Vasut

Merge patch series "Enable Ethernet boot on SK-AM62A-LP"

2026-07-28T18:30:50Z

Chintan Vankar says: This series enables Ethernet boot on SK-AM62A-LP. The series is based on commit 'a18265f1ccb7' of origin/next branch of U-Boot repo. Link: https://lore.kernel.org/r/20260716080553.2664147-1-c-vankar@ti.com

doc: board: ti: am62ax_sk: Add document for Ethernet boot on AM62x SoC.

2026-07-28T17:58:36Z

Document the procedure to enable Ethernet Boot on SK-AM62A-LP. Tested-by: Anshul Dalal Signed-off-by: Chintan Vankar

doc: Switch from setenv to env set

2026-07-27T16:50:27Z

The "env" command is the recommended environment management command, its "set" subcommand is the equivalent replacement for legacy "setenv" command. Update the documentation to use the contemporary "env set" command instead of legacy "setenv" command. Note that the "setenv" command is unlikely to be removed from U-Boot in the near future due to it being integral part of the command line ABI. Implemented using: $ sed -i 's@\@env set@g' $(git grep -li '\' doc/) README Signed-off-by: Marek Vasut

global: Switch from source.denx.de to git.u-boot-project.org

2026-07-20T17:13:21Z

As part of moving our git forge to a new location, update all references in tree to point to git.u-boot-project.org now. Signed-off-by: Tom Rini

Merge patch series "ti: j7: Update to v0.12.0 of DDR config tool"

2026-06-09T16:26:36Z

Neha Malcom Francis says: Update all DDR configuration DTSIs to the latest auto-generated output of the Sysconfig Tool (DDR Configuration for TDA4x, DRA8x, AM67x, AM68x, AM69x (0.12.00.0000)) [0] The auto-generated files must not be modified, but effort will be taken to change the tool output to adhere to the latest checkpatch.pl rules. J722S and J721E will also be updated in a subsequent series. All the changes have been kernel boot tested and memtester has passed (same as v1, as no functional changes made). [0] https://dev.ti.com/sysconfig/#/start Link: https://lore.kernel.org/r/20251103071035.674604-1-n-francis@ti.com

doc: ti: k3: Add section for DDR configuration

2026-06-09T16:26:21Z

Add a concise section for DDR configuration pointing to the public tool that can be used to generate the configuration DTSI. Signed-off-by: Neha Malcom Francis Reviewed-by: Romain Naour

doc: board: ti: k3: Add fTPM support documentation

2026-05-01T08:30:32Z

Add fTPM support documentation including an overview, configuration steps for RPMB provisioning, OP-TEE TA build instructions, and verification procedure. Signed-off-by: Shiva Tripathi

doc: board: ti: j784s4_evm: Automate BAR address lookup for PCIe Boot

2026-04-17T06:16:03Z

When the J784S4-EVM is configured for PCIe Boot, the Bootloaders are to be written to the address specified by particular BARs. The existing documentation hard-codes the address corresponding to the BAR under the assumption that the Root-Complex transferring the Bootloaders is also a J784S4-EVM. The Root-Complex assigns addresses to the BARs depending on the currently available set of free system addresses. Since the free system addresses vary with the Root-Complex being used, instead of hard-coding the BARs, automate the process of identifying the appropriate BAR in the form of a command to be run by the user on the Root-Complex. Signed-off-by: Siddharth Vadapalli