<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-ti.git, branch 11.01.05</title>
<subtitle>Mirror of git.yoctoproject.org/meta-ti.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-ti.git/atom?h=11.01.05</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-ti.git/atom?h=11.01.05'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/'/>
<updated>2025-07-02T00:53:14+00:00</updated>
<entry>
<title>CI/CD Auto-Merger: cicd.scarthgap.202507011953</title>
<updated>2025-07-02T00:53:14+00:00</updated>
<author>
<name>LCPD Automation Script</name>
<email>lcpdbld@list.ti.com</email>
</author>
<published>2025-07-02T00:53:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=59354be6c2362b9f7d0a3cd2c017f2f3c6ab7f2e'/>
<id>urn:sha1:59354be6c2362b9f7d0a3cd2c017f2f3c6ab7f2e</id>
<content type='text'>
Updated the value(s) for:
  ti-linux-fw: TI_LINUX_FW_SRCREV
  u-boot-ti-staging_2025.01: SRCREV
  k3conf: SRCREV
  linux-ti-staging_6.12: PV,SRCREV

Changelogs:
  ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&amp;q=1190654141a9604e21307555882d77eaaf8c5fac..33bec0e2ea9a25362c0c8243b2f1ed392dbc5b02
  u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&amp;q=5350f13b66393212475a15c4e107add1d38267d3..d2a72467939e169210bcd8e57de4b3e6ce2ef149
  k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&amp;q=ea9938bf9cafd9c0cb05ef060a713ab4ac72270f..e6abc1b87f1d5bc4c2ab5f1ebfbf5a70e437dcb4
  linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&amp;q=9167ea3511ca6ac1536b3114d92791b3de7422a3..e3e551586dfad357550da433969d6d9f458e06ce

Signed-off-by: LCPD Automation Script &lt;lcpdbld@list.ti.com&gt;
</content>
</entry>
<entry>
<title>trusted-firmware-a: Move back to tfa upstream except for am62lxx</title>
<updated>2025-07-01T18:48:35+00:00</updated>
<author>
<name>Ryan Eatmon</name>
<email>reatmon@ti.com</email>
</author>
<published>2025-07-01T18:30:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=f3f1b805a7689d27177b0148a25e9ddddf850dbc'/>
<id>urn:sha1:f3f1b805a7689d27177b0148a25e9ddddf850dbc</id>
<content type='text'>
This moves all of the platforms back to the main TFA repository, but
still points to the TI fork for the am62lxx platform while we continue
to work on upstreaming the needed patches.

With the the split into two repositories on two branches we need to also
split the LIC_FILES_CHECKSUM into two since the license.rst file is
slightly different between the two branches.  The upstream master
version is newer than the current am62l version.

Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>Revert "conf: machine: k3: disable all fit signing for uboot"</title>
<updated>2025-07-01T18:38:12+00:00</updated>
<author>
<name>Manorit Chawdhry</name>
<email>m-chawdhry@ti.com</email>
</author>
<published>2025-06-27T05:26:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=c3d9acf613232d7267fbcd97227361c3160f6e86'/>
<id>urn:sha1:c3d9acf613232d7267fbcd97227361c3160f6e86</id>
<content type='text'>
FIT signing was disabled in the past as it was interfering with multi
DTB usecase in binman, and it was thought that the binman signing being
done is equivalent to UBOOT_SIGN_ENABLE.

Though looking at the sources, UBOOT_SIGN_ENABLE is actually used to
sign the kernel FIT Image instead and the name UBOOT actually specifies
that it's used in tandom with U-boot. During the signing process, mkimage
from U-boot is used to pack the kernel FIT Image and along with that,
one DTB from U-boot is also passed to the mkimage command. The DTB that
gets passed gets the key embedded in it that is used to verify the
kernel FIT image at runtime.

Now this signed DTB is packed in U-boot by triggering a rebuild with
EXT_DTB argument in the U-boot build process. However, this failed as
there was a U-boot bug which was not looking at the packed sources
properly with the multi DTB usecase.

Now that a U-boot fix is available [0], revert that commit which
disabled the FIT signing.

This reverts commit 9656b79cb557a46d2611b67e7e51702f6da05594.

[0]: https://lore.kernel.org/all/20250626-b4-upstream-fix-icssg-fit-v1-1-95eff1c853a4@ti.com/

Signed-off-by: Manorit Chawdhry &lt;m-chawdhry@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-bsp: recipes-security: optee: Update OP-TEE components to 4.6.0</title>
<updated>2025-06-27T15:11:15+00:00</updated>
<author>
<name>Manorit Chawdhry</name>
<email>m-chawdhry@ti.com</email>
</author>
<published>2025-06-27T10:28:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=3e5f828f915327a2e8e5c8954058ff048d639db6'/>
<id>urn:sha1:3e5f828f915327a2e8e5c8954058ff048d639db6</id>
<content type='text'>
Updates optee_os, optee_test, optee_client, optee_examples to 4.6.0

Signed-off-by: Manorit Chawdhry &lt;m-chawdhry@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: move UBOOT_*ADDRESS to top level ti-soc</title>
<updated>2025-06-27T15:05:48+00:00</updated>
<author>
<name>Anshul Dalal</name>
<email>anshuld@ti.com</email>
</author>
<published>2025-06-27T06:04:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=8832e32cc7cb43dae45d3c318f8dc9d103827e94'/>
<id>urn:sha1:8832e32cc7cb43dae45d3c318f8dc9d103827e94</id>
<content type='text'>
Since all k3 and legacy platforms share common load addresses for kernel
and initrd in the fitImage, move them to top level ti-soc.inc.

No functional change is intended from this patch.

Signed-off-by: Anshul Dalal &lt;anshuld@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: k3: update fitImage load address</title>
<updated>2025-06-27T15:04:34+00:00</updated>
<author>
<name>Anshul Dalal</name>
<email>anshuld@ti.com</email>
</author>
<published>2025-06-27T06:04:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=8b920cab4098450f49a5c2c8e7eda1c9c8457726'/>
<id>urn:sha1:8b920cab4098450f49a5c2c8e7eda1c9c8457726</id>
<content type='text'>
In yocto, the UBOOT_ENTRYPOINT and UBOOT_*LOADADDRESS variables specify
the entry point and load addresses for the kernel image and the DTB when
creating the fitImage[1].

Currently the load address for the kernel is set to 0x81000000 and
0x83000000 for the DTB for all k3 platforms.

However the region 0x80080000 to 0x81880000 is reserved for OPTEE on
am62xxsip-evm, leading to boot failure[2] when using the fitImage.

This patch fixes the issue by changing the addresses to 0x82000000 for
kernel and 0x88000000 for the DTB. This also allows us to load kernel
images &gt; 32MiB in size when not using initrd while also making the
falcon and standard boot addresses consistent.

[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_ENTRYPOINT
[2]:
https://raw.githubusercontent.com/ArchUsr64/ti_boot_logs/HEAD/am62xxsip-evm/failures/fitImage_load_addr_issue.log

Signed-off-by: Anshul Dalal &lt;anshuld@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>CI/CD Auto-Merger: cicd.scarthgap.202506261626</title>
<updated>2025-06-26T21:27:18+00:00</updated>
<author>
<name>LCPD Automation Script</name>
<email>lcpdbld@list.ti.com</email>
</author>
<published>2025-06-26T21:27:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=2e1d6a979db913849d3a6a12bd82ce2878557b4d'/>
<id>urn:sha1:2e1d6a979db913849d3a6a12bd82ce2878557b4d</id>
<content type='text'>
Updated the value(s) for:
  ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION
  atf: SRCREV_tfa
  u-boot-ti-staging_2025.01: SRCREV
  linux-ti-staging_6.12: PV,SRCREV

Changelogs:
  ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&amp;q=e594deb508a322d5681888d48fbb153953b06ca9..1190654141a9604e21307555882d77eaaf8c5fac
  u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&amp;q=c99a1f082ba4970678c9cb5100d13a986e77817c..5350f13b66393212475a15c4e107add1d38267d3
  linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&amp;q=34d0b070130a8cd2cddd9260389ad974e8cb8468..9167ea3511ca6ac1536b3114d92791b3de7422a3

Signed-off-by: LCPD Automation Script &lt;lcpdbld@list.ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: am62xxsip: update kernel dtbs</title>
<updated>2025-06-26T14:05:46+00:00</updated>
<author>
<name>Anshul Dalal</name>
<email>anshuld@ti.com</email>
</author>
<published>2025-06-26T09:51:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=af9c3289ace214ad052a33488bc4cf808b1768ea'/>
<id>urn:sha1:af9c3289ace214ad052a33488bc4cf808b1768ea</id>
<content type='text'>
The new kernel dtb for am62x SiP have been merged to ti-linux-kernel as
of f9579207b081 ("arm64: dts: ti: Add support for AM6254xxl SiP SK") on
ti-linux-6.12.y-cicd. This patch modifies FIT_CONF_DEFAULT_DTB to pick
the new dtb instead.

Signed-off-by: Anshul Dalal &lt;anshuld@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-bsp: optee: add build flags for am62xxsip-evm</title>
<updated>2025-06-26T14:05:46+00:00</updated>
<author>
<name>Anshul Dalal</name>
<email>anshuld@ti.com</email>
</author>
<published>2025-06-26T09:51:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=266610c6f3b2c41fe6629ec24db11a709a8edba7'/>
<id>urn:sha1:266610c6f3b2c41fe6629ec24db11a709a8edba7</id>
<content type='text'>
CFG_TZDRAM_START in OPTEE defines it's load address and is used to
configure the page tables accordingly.

Due to 512MiB DDR limitation of am62x SiP, the memory map has been
modified with OP-TEE moved to bottom of DDR after atf to 0x80080000,
this requires modifications to the OPTEE's CFG_TZDRAM_START.

Signed-off-by: Anshul Dalal &lt;anshuld@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-bsp: tfa: add build flags for am62xxsip-evm</title>
<updated>2025-06-26T14:05:46+00:00</updated>
<author>
<name>Anshul Dalal</name>
<email>anshuld@ti.com</email>
</author>
<published>2025-06-26T09:51:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=1892ec68f72e40b720606fe8105f6bb4aa79b335'/>
<id>urn:sha1:1892ec68f72e40b720606fe8105f6bb4aa79b335</id>
<content type='text'>
Due to 512MiB DDR limitation of am62x SiP, the memory map has been
modified with OP-TEE moved to bottom of DDR after atf to 0x80080000,
this requires modifications to ATF's BL32_BASE. PRELOADED_BL33_BASE has
also been updated to 0x82000000 to reflect the updated SPL_TEXT_BASE
from u-boot.

Signed-off-by: Anshul Dalal &lt;anshuld@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
</feed>
