u-boot.git/tools/binman, branch v2024.07

binman: Fix typo in mkimage etype description

2024-05-03T18:22:59Z

Fix a typo, no functional change. Signed-off-by: Marek Vasut Reviewed-by: Quentin Schulz

binman: Add nxp_imx8mimage etype

2024-04-28T15:10:13Z

Add new binman etype derived from mkimage etype which generates configuration input file for mkimage -T imx8mimage, and runs the mkimage on input data. The mkimage -T imx8mimage is used to generate combined image with SPL and DDR PHY blobs which is bootable on i.MX8M. The configuration file generated here is equivalent of imx8mimage.cfg, which is the file passed to '$ mkimage -T imx8mimage -n imx8mimage.cfg ...' . The settings generated into the imx8mimage.cfg file are configured via supported binman DT properties, nxp,boot-from, nxp,loader-address, nxp,rom-version. Signed-off-by: Marek Vasut

tools: binman: ti_board_cfg: improve error message

2024-04-11T21:51:33Z

When there is a lint error the user gets the following cryptic message: binman: Node '/path/to/some/node': Yamllint error: 18: comments This isn't very helpful. Improve the message to tell the user that the number is actually a line number and also tell the user in which file they have to look. Signed-off-by: Michael Walle Reviewed-by: Neha Malcom Francis

binman: ti-secure: Enable debug extension for combined boot

2024-04-11T21:51:11Z

To debug using jtag, ROM needs to unlock jtag debugging on HS devices and it does that looking at this debug extension. Add the debug extension and enable it by default. Link: https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/security/sec_cert_format.html?highlight=debug#sysfw-debug-ext Signed-off-by: Manorit Chawdhry Reviewed-by: Neha Malcom Francis

tools: binman: ti_board_cfg: Check for linting problems

2024-01-18T22:50:27Z

Use yamllint for checking whether YAML configuration files are adhering to default yamllint rules. Signed-off-by: Neha Malcom Francis Suggested-by: Nishanth Menon

Merge patch series "ATF and OP-TEE Firewalling for K3 devices."

2024-01-04T21:53:49Z

Manorit Chawdhry says: K3 devices have firewalls that are used to prevent illegal accesses to memory regions that are deemed secure. The series prevents the illegal accesses to ATF and OP-TEE regions that are present in different K3 devices. AM62X, AM62AX and AM64X are currently in hold due to some firewall configurations that our System Controller (TIFS) needs to handle. The devices that are not configured with the firewalling nodes will not be affected and can continue to work fine until the firewall nodes are added so will be a non-blocking merge. Test Logs: https://gist.github.com/manorit2001/4cead2fb3a19eb5d19005b3f54682627 CICD Run: https://github.com/u-boot/u-boot/pull/442

binman: ftest: Add test for ti-secure firewall node

2024-01-04T21:48:00Z

Add test for TI firewalling node in ti-secure. Reviewed-by: Simon Glass Signed-off-by: Manorit Chawdhry

binman: ti-secure: Add support for firewalling entities

2024-01-04T21:48:00Z

We can now firewall entities while loading them through our secure entity TIFS, the required information should be present in the certificate that is being parsed by TIFS. The following commit adds the support to enable the certificates to be generated if the firewall configurations are present in the binman dtsi nodes. Reviewed-by: Simon Glass Signed-off-by: Manorit Chawdhry

binman: used-before-assignment in ftest.py

2023-12-31T14:21:02Z

Pytest 7.4.3 complains if a variable is used in a finally clause without having been initialized before the try clause. Signed-off-by: Heinrich Schuchardt Reviewed-by: Simon Glass

binman: elf: Using variable 'old_val' before assignment

2023-12-13T23:39:06Z

old_val can only be assumed initialized in the finally block if it is assigned a value before the try statement. Signed-off-by: Heinrich Schuchardt Reviewed-by: Simon Glass