mirror of
https://git.yoctoproject.org/meta-ti
synced 2026-04-20 19:53:43 +00:00
conf: machine: add AM69-SK machine configuration
As of commits [1] and [2] in ti-u-boot-2024.04 and upstream respectively
there is a separate defconfig to build u-boot for j784s4-evm and am69-sk
Hence, introduce new yocto machine configs for am69-sk. Also remove am69
devicetree builds from the j784s4-evm conf
[1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=8a46af7a39e6218e4de5c6195697af36201c778c
[2]: 740759d558
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This commit is contained in:
committed by
Ryan Eatmon
parent
3dd6b2f6cf
commit
dd2e3f5879
11
meta-ti-bsp/conf/machine/am69-sk-k3r5.conf
Normal file
11
meta-ti-bsp/conf/machine/am69-sk-k3r5.conf
Normal file
@@ -0,0 +1,11 @@
|
||||
#@TYPE: Machine
|
||||
#@NAME: AM69 SK (R5F)
|
||||
#@DESCRIPTION: Machine configuration for the TI AM69 SK (R5F core)
|
||||
|
||||
require conf/machine/include/k3r5.inc
|
||||
|
||||
SYSFW_SOC = "j784s4"
|
||||
SYSFW_CONFIG = "evm"
|
||||
SYSFW_SUFFIX = "hs-fs"
|
||||
|
||||
UBOOT_MACHINE = "am69_sk_r5_defconfig"
|
||||
20
meta-ti-bsp/conf/machine/am69-sk.conf
Normal file
20
meta-ti-bsp/conf/machine/am69-sk.conf
Normal file
@@ -0,0 +1,20 @@
|
||||
#@TYPE: Machine
|
||||
#@NAME: AM69 SK
|
||||
#@DESCRIPTION: Machine configuration for the TI AM69 SK
|
||||
|
||||
require conf/machine/include/j784s4.inc
|
||||
|
||||
TFA_K3_USART = "0x8"
|
||||
OPTEE_K3_USART = "0x8"
|
||||
|
||||
KERNEL_DEVICETREE_PREFIX = " \
|
||||
ti/k3-am69-sk \
|
||||
ti/k3-fpdlink \
|
||||
ti/k3-v3link \
|
||||
"
|
||||
|
||||
KERNEL_DEVICETREE = " \
|
||||
ti/k3-am69-sk.dtb \
|
||||
"
|
||||
|
||||
UBOOT_MACHINE = "am69_sk_a72_defconfig"
|
||||
@@ -11,7 +11,6 @@ KERNEL_DEVICETREE_PREFIX = " \
|
||||
ti/k3-j784s4 \
|
||||
ti/k3-fpdlink \
|
||||
ti/k3-j7200-evm-mcspi-loopback \
|
||||
ti/k3-am69-sk \
|
||||
ti/k3-v3link \
|
||||
"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user