NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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] http://lists.busybox.net/pipermail/buildroot/2024-February/685821.html
[2] 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

Reviewed-by: Arnout Vandecappelle <arnout@mind.be>
Signed-off-by: Romain Naour <romain.naour@smile.fr>
This commit is contained in:
Romain Naour 2024-03-04 00:03:55 +01:00
parent e5d8cd5173
commit 700ba1df1e
4 changed files with 32 additions and 2 deletions

16
board/ti/am62x-sk/readme.txt
View File

@ -17,6 +17,22 @@ Optional: modify the configuration:
$ make menuconfig
IMPORTANT: make sure to use the tiboot3 firmware that match with the TI
K3 SoC boot ROM (tiboot3-am62x-{gp/hs-fs/hs}-*.bin) used on the board.
HS-FS should be the default for all TI AM6x devices but earlier version
of TI starter kit EVMs for AM6x was produced with a GP device.
See further details on e2e Forum [1] :
"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 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
Build:
$ make

16
board/ti/am64x-sk/readme.txt
View File

@ -17,6 +17,22 @@ Optional: modify the configuration:
$ make menuconfig
IMPORTANT: make sure to use the tiboot3 firmware that match with the TI
K3 SoC boot ROM (tiboot3-am64x-{gp/hs-fs/hs}-*.bin) used on the board.
HS-FS should be the default for all TI AM6x devices but earlier version
of TI starter kit EVMs for AM6x was produced with a GP device.
See further details on e2e Forum [1] :
"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 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
Build:
$ make

1
configs/ti_am62x_sk_defconfig
View File

@ -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

1
configs/ti_am64x_sk_defconfig
View File

@ -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