<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-ti.git/conf/multiconfig, branch 08.04.01.005</title>
<subtitle>Mirror of git.yoctoproject.org/meta-ti.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-ti.git/atom?h=08.04.01.005</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-ti.git/atom?h=08.04.01.005'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/'/>
<updated>2022-09-08T12:35:17+00:00</updated>
<entry>
<title>conf: machine: am64xx-evm: Switch to SR2.0 HS-FS build by default</title>
<updated>2022-09-08T12:35:17+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2022-09-07T16:03:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=0dcd35143270740233510bfe233e2dd3b0a450cb'/>
<id>urn:sha1:0dcd35143270740233510bfe233e2dd3b0a450cb</id>
<content type='text'>
AM64x devices will only be available as SR2.0 HS-FS. Set this as the
default type provided by the SDK. To allow SR2.0 HS-SE to continue to
boot, like we did with GP, we add an extra machine to build SR2.0 HS-SE
SYSFW. To use on SR2.0 HS-SE boards simply switch out the SYSFW image:

$ cd /mnt/sd-card/boot
$ mv tiboot3-am64x_sr2-hs-evm.bin tiboot3.bin

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: am64xx-evm: Make HS-SE the default</title>
<updated>2022-08-26T19:33:15+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2022-08-12T01:41:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=dbc88f2d652a08d3f0f9dbb24b7f693dec6f7f2a'/>
<id>urn:sha1:dbc88f2d652a08d3f0f9dbb24b7f693dec6f7f2a</id>
<content type='text'>
The HS-SE AM64xx machine can now be run on GP devices and built without
needing the TI_SECURE_DEV_PKG for the same. AM64xx will only be available
in the HS-FS type going forward. Make the HS-SE the default and remove
the original GP machine.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: am64xx-hs-evm: Add extra machine to build GP SYSFW</title>
<updated>2022-08-07T00:07:44+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2022-08-05T21:33:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=d4bfd5ec91881ee0dd71a6942d4bdc825a2e9426'/>
<id>urn:sha1:d4bfd5ec91881ee0dd71a6942d4bdc825a2e9426</id>
<content type='text'>
Use multiconfig to generate a GP SYSFW image. This allows the HS SDK
to be used on GP boards by simply switching out the SYSFW image:

$ cd /mnt/sd-card/boot
$ mv tiboot3-am64x-gp-evm.bin tiboot3.bin

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>j721e-sr1_1: Add j721e sr1.1 HS support</title>
<updated>2021-11-19T00:07:45+00:00</updated>
<author>
<name>Yogesh Siraswar</name>
<email>yogeshs@ti.com</email>
</author>
<published>2021-11-18T20:11:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=f438a091c319250eed33fe058706e93c9fbefd1c'/>
<id>urn:sha1:f438a091c319250eed33fe058706e93c9fbefd1c</id>
<content type='text'>
This patch adds support for J721e HS SR1.1
HS SR1.1 requires updated sysfw binary. Both SR1.0 and SR1.1 sysfw
binary will be generated. sysfw.itb will point to SR1.1

This patch requires J7 SR 1.1 support in K3 Image gen.

Signed-off-by: Yogesh Siraswar &lt;yogeshs@ti.com&gt;
Reviewed-by: Denys Dmytriyenko &lt;denys@konsulko.com&gt;
</content>
</entry>
<entry>
<title>conf, recipes-bsp: support building for K3 R5F cores via multiconfig</title>
<updated>2020-05-05T05:22:25+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@ti.com</email>
</author>
<published>2020-05-05T02:41:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=f814840465358a6b5429ad20165742ac6e6e6a29'/>
<id>urn:sha1:f814840465358a6b5429ad20165742ac6e6e6a29</id>
<content type='text'>
K3 Multicore SoC architecture defines different functional domains, each
containing specific processing cores and peripherals. Early boot is normally
handled by running bootloader and loading SYSFW on MCU Cortex-R5F core:
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am65x/README
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/j721e/README

This change adds support for building bootloader and SYSFW ITB image for
K3 Cortex-R5F cores via multiconfig.

Signed-off-by: Denys Dmytriyenko &lt;denys@ti.com&gt;
</content>
</entry>
</feed>
