diff mbox series

[v12,16/16] package/ti-k3: switch ti_am6{2, 4}x_sk_defconfig to HS-FS by default

Message ID 20240407103512.1112712-17-romain.naour@smile.fr
State Accepted
Headers show
Series Add support for AM62x-SK HS-FS devices | expand

Commit Message

Romain Naour April 7, 2024, 10:35 a.m. UTC 
From Andreas Dannenberg (TI K3 architect) [1]:

  "HS-FS should be the default for all TI AM6x devices. This is our
  "production silicon" and what's used for (almost) all projects,
  especially new projects. This being said having support for GP device
  variants still is desirable for existing boards/projects, such as the
  current BeaglePlay boards (amongst earlier version of TI starter kit
  EVMs for AM6x)."

See further details on e2e Forum [2]:

  "Unfortunately with this transition any existing GP device based AM62x
  (and AM64x) boards will no longer boot with MMC/SD card images generated"

For such existing GP device based AM62x (and AM64x) boards, users have
to provide the tiboot3.bin name using BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN.

[1] https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1210443/faq-am625-generating-sitara-am62x-am62ax-am64x-gp-device-bootable-mmc-sd-card-images-using-sdk-v8-6-and-yocto
[2] http://lists.busybox.net/pipermail/buildroot/2024-February/685821.html

Signed-off-by: Romain Naour <romain.naour@smile.fr>
---
 configs/ti_am62x_sk_defconfig | 1 -
 configs/ti_am64x_sk_defconfig | 1 -
 2 files changed, 2 deletions(-)

Comments

Arnout Vandecappelle April 8, 2024, 1:46 p.m. UTC | #1 
On 07/04/2024 12:35, Romain Naour wrote:
>  From Andreas Dannenberg (TI K3 architect) [1]:
> 
>    "HS-FS should be the default for all TI AM6x devices. This is our
>    "production silicon" and what's used for (almost) all projects,
>    especially new projects. This being said having support for GP device
>    variants still is desirable for existing boards/projects, such as the
>    current BeaglePlay boards (amongst earlier version of TI starter kit
>    EVMs for AM6x)."

  Andreas, BeaglePlay would anyway be a separate defconfig (it has another 
device tree), no? I think it's more relevant to have a BeaglePlay defconfig than 
to have a ti_am62x_sk GP defconfig.

> 
> See further details on e2e Forum [2]:
> 
>    "Unfortunately with this transition any existing GP device based AM62x
>    (and AM64x) boards will no longer boot with MMC/SD card images generated"
> 
> For such existing GP device based AM62x (and AM64x) boards, users have
> to provide the tiboot3.bin name using BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN.

  Please add this information to board/ti/am6{2,4}x-sk/readme.txt


> [1] https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1210443/faq-am625-generating-sitara-am62x-am62ax-am64x-gp-device-bootable-mmc-sd-card-images-using-sdk-v8-6-and-yocto
> [2] http://lists.busybox.net/pipermail/buildroot/2024-February/685821.html

  You swapped those two references (the first quote above comes from [2]).


  Regards,
  Arnout

> 
> Signed-off-by: Romain Naour <romain.naour@smile.fr>
> ---
>   configs/ti_am62x_sk_defconfig | 1 -
>   configs/ti_am64x_sk_defconfig | 1 -
>   2 files changed, 2 deletions(-)
> 
> diff --git a/configs/ti_am62x_sk_defconfig b/configs/ti_am62x_sk_defconfig
> index fa2c008d4c..5c7b97b3b0 100644
> --- a/configs/ti_am62x_sk_defconfig
> +++ b/configs/ti_am62x_sk_defconfig
> @@ -29,7 +29,6 @@ BR2_TARGET_TI_K3_R5_LOADER=y
>   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y
>   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.01"
>   BR2_TARGET_TI_K3_R5_LOADER_BOARD_DEFCONFIG="am62x_evm_r5"
> -BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN="tiboot3-am62x-gp-evm.bin"
>   BR2_TARGET_UBOOT=y
>   BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>   BR2_TARGET_UBOOT_CUSTOM_VERSION=y
> diff --git a/configs/ti_am64x_sk_defconfig b/configs/ti_am64x_sk_defconfig
> index f7c6d16b35..28e97f94e2 100644
> --- a/configs/ti_am64x_sk_defconfig
> +++ b/configs/ti_am64x_sk_defconfig
> @@ -29,7 +29,6 @@ BR2_TARGET_TI_K3_R5_LOADER=y
>   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y
>   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.01"
>   BR2_TARGET_TI_K3_R5_LOADER_BOARD_DEFCONFIG="am64x_evm_r5"
> -BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN="tiboot3-am64x-gp-evm.bin"
>   BR2_TARGET_UBOOT=y
>   BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
>   BR2_TARGET_UBOOT_CUSTOM_VERSION=y
Andreas Dannenberg April 9, 2024, 9:35 p.m. UTC | #2 
Hi Arnout, All,

On Mon, Apr 08, 2024 at 03:46:54PM +0200, Arnout Vandecappelle wrote:
> 
> 
> On 07/04/2024 12:35, Romain Naour wrote:
> >  From Andreas Dannenberg (TI K3 architect) [1]:
> > 
> >    "HS-FS should be the default for all TI AM6x devices. This is our
> >    "production silicon" and what's used for (almost) all projects,
> >    especially new projects. This being said having support for GP device
> >    variants still is desirable for existing boards/projects, such as the
> >    current BeaglePlay boards (amongst earlier version of TI starter kit
> >    EVMs for AM6x)."
> 
>  Andreas, BeaglePlay would anyway be a separate defconfig (it has another
> device tree), no? I think it's more relevant to have a BeaglePlay defconfig
> than to have a ti_am62x_sk GP defconfig.

Yes BeaglePlay should have its own defconfig, and I think is actually a
really REALLY great target in the context and "spirit" of Buildroot. And
it _should_ really be the only board out there that uses AM62x GP.

Now that we have AM6x base support merged (thanks everybody!!) I can't
wait to see this support growing. I do have working AM6x graphics
patches that I'll spend some time cleaning up and posting soon.

--
Andreas Dannenberg
Texas Instruments Inc



> > 
> > See further details on e2e Forum [2]:
> > 
> >    "Unfortunately with this transition any existing GP device based AM62x
> >    (and AM64x) boards will no longer boot with MMC/SD card images generated"
> > 
> > For such existing GP device based AM62x (and AM64x) boards, users have
> > to provide the tiboot3.bin name using BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN.
> 
>  Please add this information to board/ti/am6{2,4}x-sk/readme.txt
> 
> 
> > [1] https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1210443/faq-am625-generating-sitara-am62x-am62ax-am64x-gp-device-bootable-mmc-sd-card-images-using-sdk-v8-6-and-yocto
> > [2] http://lists.busybox.net/pipermail/buildroot/2024-February/685821.html
> 
>  You swapped those two references (the first quote above comes from [2]).
> 
> 
>  Regards,
>  Arnout
> 
> > 
> > Signed-off-by: Romain Naour <romain.naour@smile.fr>
> > ---
> >   configs/ti_am62x_sk_defconfig | 1 -
> >   configs/ti_am64x_sk_defconfig | 1 -
> >   2 files changed, 2 deletions(-)
> > 
> > diff --git a/configs/ti_am62x_sk_defconfig b/configs/ti_am62x_sk_defconfig
> > index fa2c008d4c..5c7b97b3b0 100644
> > --- a/configs/ti_am62x_sk_defconfig
> > +++ b/configs/ti_am62x_sk_defconfig
> > @@ -29,7 +29,6 @@ BR2_TARGET_TI_K3_R5_LOADER=y
> >   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y
> >   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.01"
> >   BR2_TARGET_TI_K3_R5_LOADER_BOARD_DEFCONFIG="am62x_evm_r5"
> > -BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN="tiboot3-am62x-gp-evm.bin"
> >   BR2_TARGET_UBOOT=y
> >   BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> >   BR2_TARGET_UBOOT_CUSTOM_VERSION=y
> > diff --git a/configs/ti_am64x_sk_defconfig b/configs/ti_am64x_sk_defconfig
> > index f7c6d16b35..28e97f94e2 100644
> > --- a/configs/ti_am64x_sk_defconfig
> > +++ b/configs/ti_am64x_sk_defconfig
> > @@ -29,7 +29,6 @@ BR2_TARGET_TI_K3_R5_LOADER=y
> >   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y
> >   BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.01"
> >   BR2_TARGET_TI_K3_R5_LOADER_BOARD_DEFCONFIG="am64x_evm_r5"
> > -BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN="tiboot3-am64x-gp-evm.bin"
> >   BR2_TARGET_UBOOT=y
> >   BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> >   BR2_TARGET_UBOOT_CUSTOM_VERSION=y
diff mbox series

Patch

diff --git a/configs/ti_am62x_sk_defconfig b/configs/ti_am62x_sk_defconfig
index fa2c008d4c..5c7b97b3b0 100644
--- a/configs/ti_am62x_sk_defconfig
+++ b/configs/ti_am62x_sk_defconfig
@@ -29,7 +29,6 @@  BR2_TARGET_TI_K3_R5_LOADER=y
 BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y
 BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.01"
 BR2_TARGET_TI_K3_R5_LOADER_BOARD_DEFCONFIG="am62x_evm_r5"
-BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN="tiboot3-am62x-gp-evm.bin"
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_VERSION=y
diff --git a/configs/ti_am64x_sk_defconfig b/configs/ti_am64x_sk_defconfig
index f7c6d16b35..28e97f94e2 100644
--- a/configs/ti_am64x_sk_defconfig
+++ b/configs/ti_am64x_sk_defconfig
@@ -29,7 +29,6 @@  BR2_TARGET_TI_K3_R5_LOADER=y
 BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION=y
 BR2_TARGET_TI_K3_R5_LOADER_CUSTOM_VERSION_VALUE="2024.01"
 BR2_TARGET_TI_K3_R5_LOADER_BOARD_DEFCONFIG="am64x_evm_r5"
-BR2_TARGET_TI_K3_R5_LOADER_TIBOOT3_BIN="tiboot3-am64x-gp-evm.bin"
 BR2_TARGET_UBOOT=y
 BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
 BR2_TARGET_UBOOT_CUSTOM_VERSION=y