1. Meta-Ti
  2. Messages

Expanded

Topics Messages
   Date   
Re: [dunfell][PATCH] conf: machine: am64xx-hs-evm: Fix naming of u-boot.img

Denys Dmytriyenko
 

On Mon, Feb 21, 2022 at 01:43:31PM +0530, Aparna M via lists.yoctoproject.org wrote:
All the HS platforms generate the u-boot binary as u-boot.img_HS
but the bootloader expects the binary to be named as u-boot.img

Due to this mismatch, script cannot find the required image to
be added in the WIC image. Fix this by overwriting the
UBOOT_IMAGE variable via conf file.
Can you please clarify which script cannot find the image? Thanks!
Also, how does it work for am65xx HS, j721e HS, j7200 HS? Why only am64xx HS?


Signed-off-by: Nikhil Devshatwar <nikhil.nd@...>

Signed-off-by: Aparna M <a-m1@...>
---
conf/machine/am64xx-hs-evm.conf | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/conf/machine/am64xx-hs-evm.conf b/conf/machine/am64xx-hs-evm.conf
index 44e81463..781b8318 100644
--- a/conf/machine/am64xx-hs-evm.conf
+++ b/conf/machine/am64xx-hs-evm.conf
@@ -17,6 +17,7 @@ UBOOT_DTBO_OFFSET = "0x00010000"
SPL_BINARY = "tispl.bin_HS"
SPL_BINARYNAME = "tispl.bin"
UBOOT_BINARY = "u-boot.img_HS"
-IMAGE_BOOT_FILES = "${UBOOT_BINARY}"
+UBOOT_IMAGE = "u-boot.img"
+IMAGE_BOOT_FILES = "${UBOOT_IMAGE}"

TI_SECURE_DEV_PKG = "${TI_SECURE_DEV_PKG_K3}"
--
2.17.1
[dunfell][PATCH] conf: machine: am64xx-hs-evm: Fix naming of u-boot.img

Aparna M
 

All the HS platforms generate the u-boot binary as u-boot.img_HS
but the bootloader expects the binary to be named as u-boot.img

Due to this mismatch, script cannot find the required image to
be added in the WIC image. Fix this by overwriting the
UBOOT_IMAGE variable via conf file.

Signed-off-by: Nikhil Devshatwar <nikhil.nd@...>

Signed-off-by: Aparna M <a-m1@...>
---
conf/machine/am64xx-hs-evm.conf | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/conf/machine/am64xx-hs-evm.conf b/conf/machine/am64xx-hs-evm.conf
index 44e81463..781b8318 100644
--- a/conf/machine/am64xx-hs-evm.conf
+++ b/conf/machine/am64xx-hs-evm.conf
@@ -17,6 +17,7 @@ UBOOT_DTBO_OFFSET = "0x00010000"
SPL_BINARY = "tispl.bin_HS"
SPL_BINARYNAME = "tispl.bin"
UBOOT_BINARY = "u-boot.img_HS"
-IMAGE_BOOT_FILES = "${UBOOT_BINARY}"
+UBOOT_IMAGE = "u-boot.img"
+IMAGE_BOOT_FILES = "${UBOOT_IMAGE}"

TI_SECURE_DEV_PKG = "${TI_SECURE_DEV_PKG_K3}"
--
2.17.1
[dunfell][PATCH 4/4] u-boot-ti-staging: Bump to 08.02.00.003 release

Ryan Eatmon
 

Updated the u-boot version for 08.02.00.003

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb b/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb
index 16bb1521..701b802a 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb
@@ -2,8 +2,8 @@ require u-boot-ti.inc

LIC_FILES_CHKSUM = "file://Licenses/README;md5=5a7450c57ffe5ae63fd732446b988025"

-PR = "r18"
+PR = "r19"

BRANCH = "ti-u-boot-2021.01"

-SRCREV = "ebc8dca63dd961aaf5f5f626a19c6f6bfd7428f0"
+SRCREV = "bd58b61277a189ee49e0d6e9fd03d52996685d98"
--
2.17.1
[dunfell][PATCH 0/4] Update to 08.02.00.003

Ryan Eatmon
 

Update u-boot, integrated lts kernel and firmware to 08.02.00.003 tag.

Ryan Eatmon (4):
ti-linux-fw: Bump to 08.02.00.003 release
linux-ti-staging: Bump to 08.02.00.003 release
linux-ti-staging-rt: Bump to 08.02.00.003 release
u-boot-ti-staging: Bump to 08.02.00.003 release

recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +-
recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb | 4 ++--
recipes-kernel/linux/linux-ti-staging-rt_5.10.bb | 4 ++--
recipes-kernel/linux/linux-ti-staging_5.10.bb | 4 ++--
4 files changed, 7 insertions(+), 7 deletions(-)

--
2.17.1
[dunfell][PATCH 2/4] linux-ti-staging: Bump to 08.02.00.003 release

Ryan Eatmon
 

Updated the linux version for 08.02.00.003

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-kernel/linux/linux-ti-staging_5.10.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-ti-staging_5.10.bb b/recipes-kernel/linux/linux-ti-staging_5.10.bb
index c74c0a10..cd7d9519 100644
--- a/recipes-kernel/linux/linux-ti-staging_5.10.bb
+++ b/recipes-kernel/linux/linux-ti-staging_5.10.bb
@@ -23,8 +23,8 @@ S = "${WORKDIR}/git"

BRANCH = "ti-linux-5.10.y"

-SRCREV = "46573628be468b58272d7c41b582603b06e0414a"
-PV = "5.10.65+git${SRCPV}"
+SRCREV = "4a12bec7d3f438ce9407e4ba9b2ec883729558a5"
+PV = "5.10.100+git${SRCPV}"

# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
MACHINE_KERNEL_PR_append = "b"
--
2.17.1
[dunfell][PATCH 3/4] linux-ti-staging-rt: Bump to 08.02.00.003 release

Ryan Eatmon
 

Updated the linux rt version for 08.02.00.003

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-kernel/linux/linux-ti-staging-rt_5.10.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb b/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
index aa49acdc..1d43ea95 100644
--- a/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
+++ b/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
@@ -6,5 +6,5 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-5.10:"

BRANCH = "ti-rt-linux-5.10.y"

-SRCREV = "1f6e95d4b12d73bd1728286f3ccc938df7b77954"
-PV = "5.10.65+git${SRCPV}"
+SRCREV = "b975aee14750c395bf5251ba4042cb0be1afa206"
+PV = "5.10.100+git${SRCPV}"
--
2.17.1
[dunfell][PATCH 1/4] ti-linux-fw: Bump to 08.02.00.003 release

Ryan Eatmon
 

Updated the ti-linux-fw version for 08.02.00.003

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/ti-linux-fw/ti-linux-fw.inc b/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
index 7b28f153..fced78fd 100644
--- a/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
+++ b/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
@@ -24,7 +24,7 @@ SRCREV = "${TI_LINUX_FW_SRCREV}"

BRANCH ?= "ti-linux-firmware"

-K3_IMAGE_GEN_SRCREV ?= "a0063e855414fd1609b5f63e2d765a49c8c513fe"
+K3_IMAGE_GEN_SRCREV ?= "f1db75bdc506287a9d04b0afbbb3d853a0948179"
SRCREV_imggen = "${K3_IMAGE_GEN_SRCREV}"
SRCREV_FORMAT = "imggen"

--
2.17.1
Re: [PATCH] ti-rtos-firmware: use nonarch_base_libdir for deployment

Awais Belal
 

Hi Denys,

Thanks, ti-rtos-firmware is just one of many other places where this needs to
be fixed.
Since this is for master, I'll take it into my new WIP master tree and extend
it to other FW recipes...
Yeah, I was thinking of doing the same in steps depending on the response I'd get here but I guess you can pick this up now :)

BR,
Awais
Re: [RESEND 1/2] beaglebone: make kernel machine-specific package

Vivien Didelot
 

Hi Denys,

On Mon, 14 Feb 2022 17:15:16 -0500 Denys Dmytriyenko <denis@...> wrote:
"make kernel machine-specific package" doesn't reflect the actual change, plus
kernel is already a machine-specific package - PACKAGE_ARCH = "${MACHINE_ARCH}"

Your original commit for beaglebone-yocto in meta-yocto-bsp is correct though.

I can take these patches into my new WIP master tree with this minor update.
Indeed using "machine-specific package" when I meant moving the kernel
artifacts into packagegroup-core-boot was confusing. Thanks for rewording!


Vivien
Re: [RESEND 1/2] beaglebone: make kernel machine-specific package

Denys Dmytriyenko
 

"make kernel machine-specific package" doesn't reflect the actual change, plus
kernel is already a machine-specific package - PACKAGE_ARCH = "${MACHINE_ARCH}"

Your original commit for beaglebone-yocto in meta-yocto-bsp is correct though.

I can take these patches into my new WIP master tree with this minor update.

On Sat, Jan 29, 2022 at 02:33:19PM -0500, Vivien Didelot wrote:
Require kernel image and device tree as machine-specific packages with
MACHINE_ESSENTIAL_EXTRA_RDEPENDS instead of appending IMAGE_INSTALL.

This binds the packages to the packagegroup-core-boot package group,
allowing one to skip their installation, e.g. for container trees.

This patch reflects commit d4cbe0e43393 [1] from meta-yocto-bsp
("beaglebone-yocto: move kernel and dtb to packagegroup-core-boot").

[1] https://git.yoctoproject.org/meta-yocto/commit/?id=d4cbe0e43393ec70e98caf006372b5311597d377

Signed-off-by: Vivien Didelot <vdidelot@...>
---
conf/machine/beaglebone.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index dcb14cc9..fe3127bb 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -13,7 +13,7 @@ MACHINE_GUI_CLASS = "bigscreen"

SERIAL_CONSOLES = "115200;ttyS0"

-IMAGE_INSTALL:append = " kernel-devicetree kernel-image-zimage"
+MACHINE_ESSENTIAL_EXTRA_RDEPENDS += "kernel-devicetree kernel-image-zimage"

# Refine the list of device targets for ti-pdk class recipes
TI_PDK_LIMIT_BOARDS = "bbbAM335x"
--
2.35.0
Re: [PATCH] ti-rtos-firmware: use nonarch_base_libdir for deployment

Denys Dmytriyenko
 

Thanks, ti-rtos-firmware is just one of many other places where this needs to
be fixed.

Since this is for master, I'll take it into my new WIP master tree and extend
it to other FW recipes...

On Wed, Feb 02, 2022 at 07:16:41PM +0500, Awais Belal wrote:
base_libdir is not configuration safe while firmware binaries
should always be deployed to /lib. In configurations where
base_libdir is not /lib the firmware gets deployed to wrong
paths.
This is fixed by using the nonarch_base_libdir which is
configuration agnostic.

Signed-off-by: Awais Belal <awais_belal@...>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 102 ++++++++++-----------
1 file changed, 51 insertions(+), 51 deletions(-)

diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index c0beb550..7d286b20 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -31,7 +31,7 @@ PR = "${INC_PR}.0"
# Secure Build
DEPENDS += "openssl-native"

-FILES:${PN} += "${base_libdir}"
+FILES:${PN} += "${nonarch_base_libdir}"

TI_SECURE_DEV_PKG ?= ""

@@ -41,9 +41,9 @@ RTOS_IPC_FW_DIR = "${S}/ti-ipc/${PLAT_SFX}"

# For back-ward compatability keeping legacy firmware folder name
# TODO: fix this in next version
-LEGACY_ETH_FW_DIR = "${D}${base_libdir}/firmware/ethfw/"
-LEGACY_IPC_FW_DIR = "${D}${base_libdir}/firmware/pdk-ipc/"
-LEGACY_DM_FW_DIR = "${D}${base_libdir}/firmware/pdk-ipc/"
+LEGACY_ETH_FW_DIR = "${D}${nonarch_base_libdir}/firmware/ethfw/"
+LEGACY_IPC_FW_DIR = "${D}${nonarch_base_libdir}/firmware/pdk-ipc/"
+LEGACY_DM_FW_DIR = "${D}${nonarch_base_libdir}/firmware/pdk-ipc/"

DM_FIRMWARE = "ipc_echo_testb_mcu1_0_release_strip.xer5f"

@@ -208,60 +208,60 @@ TARGET_MCU_R5FSS0_1:j7200-hs-evm = "j7200-mcu-r5f0_1-fw"
TARGET_MAIN_R5FSS0_0:j7200-hs-evm = "j7200-main-r5f0_0-fw"
TARGET_MAIN_R5FSS0_1:j7200-hs-evm = "j7200-main-r5f0_1-fw"

-ALTERNATIVE_LINK_NAME[am65x-mcu-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
-ALTERNATIVE_LINK_NAME[am65x-mcu-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
-
-ALTERNATIVE_LINK_NAME[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
-ALTERNATIVE_LINK_NAME[am64-main-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_1}"
-ALTERNATIVE_LINK_NAME[am64-main-r5f1_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS1_0}"
-ALTERNATIVE_LINK_NAME[am64-main-r5f1_1-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS1_1}"
-ALTERNATIVE_LINK_NAME[am64-mcu-m4f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_M4FSS0_0}"
-
-ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
-ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
-ALTERNATIVE_LINK_NAME[j7-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
-ALTERNATIVE_LINK_NAME[j7-main-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_1}"
-ALTERNATIVE_LINK_NAME[j7-main-r5f1_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS1_0}"
-ALTERNATIVE_LINK_NAME[j7-main-r5f1_1-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS1_1}"
-ALTERNATIVE_LINK_NAME[j7-c66_0-fw] = "${base_libdir}/firmware/${TARGET_C66_0}"
-ALTERNATIVE_LINK_NAME[j7-c66_1-fw] = "${base_libdir}/firmware/${TARGET_C66_1}"
-ALTERNATIVE_LINK_NAME[j7-c71_0-fw] = "${base_libdir}/firmware/${TARGET_C7X}"
-
-ALTERNATIVE_LINK_NAME[j7200-mcu-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
-ALTERNATIVE_LINK_NAME[j7200-mcu-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
-ALTERNATIVE_LINK_NAME[j7200-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
-ALTERNATIVE_LINK_NAME[j7200-main-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_1}"
+ALTERNATIVE_LINK_NAME[am65x-mcu-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
+ALTERNATIVE_LINK_NAME[am65x-mcu-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
+
+ALTERNATIVE_LINK_NAME[am64-main-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
+ALTERNATIVE_LINK_NAME[am64-main-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS0_1}"
+ALTERNATIVE_LINK_NAME[am64-main-r5f1_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS1_0}"
+ALTERNATIVE_LINK_NAME[am64-main-r5f1_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS1_1}"
+ALTERNATIVE_LINK_NAME[am64-mcu-m4f0_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MCU_M4FSS0_0}"
+
+ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
+ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
+ALTERNATIVE_LINK_NAME[j7-main-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
+ALTERNATIVE_LINK_NAME[j7-main-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS0_1}"
+ALTERNATIVE_LINK_NAME[j7-main-r5f1_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS1_0}"
+ALTERNATIVE_LINK_NAME[j7-main-r5f1_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS1_1}"
+ALTERNATIVE_LINK_NAME[j7-c66_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_C66_0}"
+ALTERNATIVE_LINK_NAME[j7-c66_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_C66_1}"
+ALTERNATIVE_LINK_NAME[j7-c71_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_C7X}"
+
+ALTERNATIVE_LINK_NAME[j7200-mcu-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
+ALTERNATIVE_LINK_NAME[j7200-mcu-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
+ALTERNATIVE_LINK_NAME[j7200-main-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
+ALTERNATIVE_LINK_NAME[j7200-main-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/${TARGET_MAIN_R5FSS0_1}"

# Create the firmware alternatives

-ALTERNATIVE_TARGET[am65x-mcu-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_0_release_strip.xer5f"
-ALTERNATIVE_TARGET[am65x-mcu-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
-
-ALTERNATIVE_TARGET[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f"
-ALTERNATIVE_TARGET[am64-main-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu1_1_release_strip.xer5f"
-ALTERNATIVE_TARGET[am64-main-r5f1_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f"
-ALTERNATIVE_TARGET[am64-main-r5f1_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f"
-ALTERNATIVE_TARGET[am64-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f"
-
-ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
-ALTERNATIVE_TARGET[j7-mcu-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
-ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = "${base_libdir}/firmware/ethfw/app_remoteswitchcfg_server_strip.xer5f"
-ALTERNATIVE_TARGET[j7-main-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_1_release_strip.xer5f"
-ALTERNATIVE_TARGET[j7-main-r5f1_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu3_0_release_strip.xer5f"
-ALTERNATIVE_TARGET[j7-main-r5f1_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu3_1_release_strip.xer5f"
-ALTERNATIVE_TARGET[j7-c66_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c66xdsp_1_release_strip.xe66"
-ALTERNATIVE_TARGET[j7-c66_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c66xdsp_2_release_strip.xe66"
-ALTERNATIVE_TARGET[j7-c71_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c7x_1_release_strip.xe71"
-
-ALTERNATIVE_TARGET[j7200-mcu-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
-ALTERNATIVE_TARGET[j7200-mcu-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
-ALTERNATIVE_TARGET[j7200-main-r5f0_0-fw] = "${base_libdir}/firmware/ethfw/app_remoteswitchcfg_server_strip.xer5f"
-ALTERNATIVE_TARGET[j7200-main-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_1_release_strip.xer5f"
+ALTERNATIVE_TARGET[am65x-mcu-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[am65x-mcu-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
+
+ALTERNATIVE_TARGET[am64-main-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[am64-main-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu1_1_release_strip.xer5f"
+ALTERNATIVE_TARGET[am64-main-r5f1_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[am64-main-r5f1_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f"
+ALTERNATIVE_TARGET[am64-mcu-m4f0_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f"
+
+ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[j7-mcu-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
+ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/ethfw/app_remoteswitchcfg_server_strip.xer5f"
+ALTERNATIVE_TARGET[j7-main-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_1_release_strip.xer5f"
+ALTERNATIVE_TARGET[j7-main-r5f1_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu3_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[j7-main-r5f1_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu3_1_release_strip.xer5f"
+ALTERNATIVE_TARGET[j7-c66_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_c66xdsp_1_release_strip.xe66"
+ALTERNATIVE_TARGET[j7-c66_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_c66xdsp_2_release_strip.xe66"
+ALTERNATIVE_TARGET[j7-c71_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_c7x_1_release_strip.xe71"
+
+ALTERNATIVE_TARGET[j7200-mcu-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[j7200-mcu-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
+ALTERNATIVE_TARGET[j7200-main-r5f0_0-fw] = "${nonarch_base_libdir}/firmware/ethfw/app_remoteswitchcfg_server_strip.xer5f"
+ALTERNATIVE_TARGET[j7200-main-r5f0_1-fw] = "${nonarch_base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_1_release_strip.xer5f"

ALTERNATIVE_PRIORITY = "10"

# make sure that lib/firmware, and all its contents are part of the package
-FILES:${PN} += "${base_libdir}/firmware"
+FILES:${PN} += "${nonarch_base_libdir}/firmware"

# This is used to prevent the build system to_strip the executables
INHIBIT_PACKAGE_STRIP = "1"
--
2.17.1
Re: [PATCH] ti-rtos-firmware: use nonarch_base_libdir for deployment

Awais Belal
 

ping!

BR,
Awais
[dunfell][PATCH 4/4] ti-linux-fw: Bump to 08.02.00.002 release

Ryan Eatmon
 

Updated the ti-linux-fw version for 08.02.00.002

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/ti-linux-fw/ti-linux-fw.inc b/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
index 5954cbd8..7b28f153 100644
--- a/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
+++ b/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
@@ -24,7 +24,7 @@ SRCREV = "${TI_LINUX_FW_SRCREV}"

BRANCH ?= "ti-linux-firmware"

-K3_IMAGE_GEN_SRCREV ?= "892c86501ff745dfde4d535923ce686f45700da3"
+K3_IMAGE_GEN_SRCREV ?= "a0063e855414fd1609b5f63e2d765a49c8c513fe"
SRCREV_imggen = "${K3_IMAGE_GEN_SRCREV}"
SRCREV_FORMAT = "imggen"

--
2.17.1
[dunfell][PATCH 2/4] linux-ti-staging-rt: Bump to 08.02.00.002 release

Ryan Eatmon
 

Updated the linux rt version for 08.02.00.002

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-kernel/linux/linux-ti-staging-rt_5.10.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb b/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
index 7929b9cf..aa49acdc 100644
--- a/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
+++ b/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
@@ -6,5 +6,5 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-5.10:"

BRANCH = "ti-rt-linux-5.10.y"

-SRCREV = "d81474af4e33f8de2869d9b21a2389e06178c230"
+SRCREV = "1f6e95d4b12d73bd1728286f3ccc938df7b77954"
PV = "5.10.65+git${SRCPV}"
--
2.17.1
[dunfell][PATCH 0/4] Update to 08.02.00.002

Ryan Eatmon
 

Update u-boot, integrated lts kernel and firmware to 08.02.00.002 tag.

Ryan Eatmon (4):
linux-ti-staging: Bump to 08.02.00.002 release
linux-ti-staging-rt: Bump to 08.02.00.002 release
u-boot-ti-staging: Bump to 08.02.00.002 release
ti-linux-fw: Bump to 08.02.00.002 release

recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +-
recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb | 4 ++--
recipes-kernel/linux/linux-ti-staging-rt_5.10.bb | 2 +-
recipes-kernel/linux/linux-ti-staging_5.10.bb | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)

--
2.17.1
[dunfell][PATCH 1/4] linux-ti-staging: Bump to 08.02.00.002 release

Ryan Eatmon
 

Updated the linux version for 08.02.00.002

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-kernel/linux/linux-ti-staging_5.10.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-ti-staging_5.10.bb b/recipes-kernel/linux/linux-ti-staging_5.10.bb
index 51083382..c74c0a10 100644
--- a/recipes-kernel/linux/linux-ti-staging_5.10.bb
+++ b/recipes-kernel/linux/linux-ti-staging_5.10.bb
@@ -23,7 +23,7 @@ S = "${WORKDIR}/git"

BRANCH = "ti-linux-5.10.y"

-SRCREV = "a523aa26d870552a44c5f48b01c3c1ea3a48751a"
+SRCREV = "46573628be468b58272d7c41b582603b06e0414a"
PV = "5.10.65+git${SRCPV}"

# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
--
2.17.1
[dunfell][PATCH 3/4] u-boot-ti-staging: Bump to 08.02.00.002 release

Ryan Eatmon
 

Updated the u-boot version for 08.02.00.002

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb b/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb
index a7e21b7c..16bb1521 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb
@@ -2,8 +2,8 @@ require u-boot-ti.inc

LIC_FILES_CHKSUM = "file://Licenses/README;md5=5a7450c57ffe5ae63fd732446b988025"

-PR = "r17"
+PR = "r18"

BRANCH = "ti-u-boot-2021.01"

-SRCREV = "eadf5af36c6e0097a162f81308b64cc0b796b6b5"
+SRCREV = "ebc8dca63dd961aaf5f5f626a19c6f6bfd7428f0"
--
2.17.1
Re: [dunfell][PATCH 1/3] linux-ti-staging: Bump to 08.02.00.001 release

Ryan Eatmon
 

My auto script is not picking up that change. I'll fix that for future releases. Thanks for pointing it out.

On 2/10/2022 21:41, Denys Dmytriyenko wrote:
On Mon, Feb 07, 2022 at 09:39:48AM -0600, Ryan Eatmon via lists.yoctoproject.org wrote:
Updated the linux version for 08.02.00.001

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-kernel/linux/linux-ti-staging_5.10.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-ti-staging_5.10.bb b/recipes-kernel/linux/linux-ti-staging_5.10.bb
index 3f3d50af..51083382 100644
--- a/recipes-kernel/linux/linux-ti-staging_5.10.bb
+++ b/recipes-kernel/linux/linux-ti-staging_5.10.bb
@@ -23,7 +23,7 @@ S = "${WORKDIR}/git"
BRANCH = "ti-linux-5.10.y"
-SRCREV = "dcc6bedb2c2bdb509709e4ae08303206e95ce6c2"
+SRCREV = "a523aa26d870552a44c5f48b01c3c1ea3a48751a"
PV = "5.10.65+git${SRCPV}"
Why is it still versioned as 5.10.65? Quick glance at ti-linux-kernel shows
it's been updating with the latest stable on a regular basis and the latest
version now is 5.10.90, which is 25 minor releases ahead:
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/Makefile?h=ti-linux-5.10.y

# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
--
2.17.1
--
Ryan Eatmon
reatmon@...
Re: [dunfell][PATCH 1/3] linux-ti-staging: Bump to 08.02.00.001 release

Denys Dmytriyenko
 

On Mon, Feb 07, 2022 at 09:39:48AM -0600, Ryan Eatmon via lists.yoctoproject.org wrote:
Updated the linux version for 08.02.00.001

Signed-off-by: Ryan Eatmon <reatmon@...>
---
recipes-kernel/linux/linux-ti-staging_5.10.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-ti-staging_5.10.bb b/recipes-kernel/linux/linux-ti-staging_5.10.bb
index 3f3d50af..51083382 100644
--- a/recipes-kernel/linux/linux-ti-staging_5.10.bb
+++ b/recipes-kernel/linux/linux-ti-staging_5.10.bb
@@ -23,7 +23,7 @@ S = "${WORKDIR}/git"

BRANCH = "ti-linux-5.10.y"

-SRCREV = "dcc6bedb2c2bdb509709e4ae08303206e95ce6c2"
+SRCREV = "a523aa26d870552a44c5f48b01c3c1ea3a48751a"
PV = "5.10.65+git${SRCPV}"
Why is it still versioned as 5.10.65? Quick glance at ti-linux-kernel shows
it's been updating with the latest stable on a regular basis and the latest
version now is 5.10.90, which is 25 minor releases ahead:

https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/Makefile?h=ti-linux-5.10.y


# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
--
2.17.1
Re: [dunfell][PATCH] conf/machine/am57xx-evm: add overlay for OV10635 sensor

Denys Dmytriyenko
 

On Wed, Feb 09, 2022 at 11:56:25AM -0800, Kevin Hilman wrote:
The VIP camera capture driver recently ported to ti-linux-5.10.y adds
a DT overlay for the OV10635 camera sensor. Add this to
KERNEL_DEVICTREE so it's added to the artifacts.

Signed-off-by: Kevin Hilman <khilman@...>
Reviewed-by: Denys Dmytriyenko <denys@...>


---
Fixes: LCPD-24423

conf/machine/am57xx-evm.conf | 1 +
1 file changed, 1 insertion(+)

diff --git a/conf/machine/am57xx-evm.conf b/conf/machine/am57xx-evm.conf
index f977c5c62872..afcfbb4318ad 100644
--- a/conf/machine/am57xx-evm.conf
+++ b/conf/machine/am57xx-evm.conf
@@ -25,6 +25,7 @@ KERNEL_DEVICETREE = " \
ti/am572x-idk-touchscreen.dtbo \
ti/lcd-osd101t2587.dtbo \
ti/lcd-osd101t2045.dtbo \
+ ti/ov10635.dtbo \
"

KERNEL_DEVICETREE += "${@oe.utils.conditional('ENABLE_TI_UIO_DEVICES', '1', 'am574x-idk-pru-excl-uio.dtb am572x-idk-pru-excl-uio.dtb am571x-idk-pru-excl-uio.dtb', '', d)}"
--
2.34.0
2301 - 2320 of 16706