Date   

[master][PATCH 00/22] Sync up with Dunfell

Denys Dmytriyenko
 

From: Denys Dmytriyenko <denys@...>

Keep master up to date with latest changes in Dunfell, adjust to the new
override syntax.

Denys Dmytriyenko (1):
powervr-drivers: teach modules_install to respect "usrmerge" distro
feature

Hari Nagalla (2):
ipc: ti-rpmsg-char: Update library to 0.3.1
ti-rtos-firmware: Update M4F binary for AM64x SoCs

Nick Saulnier (1):
pru-icss_git.bb: add AM64x, update to PSSP v6.0.0

Sinthu Raja (1):
conf: j7-evm: Replace eaik dtb with sk to KERNEL_DEVICETREE

Tom Rini (2):
conf/machine: k3: Enable grub-efi by default in wic images
conf: Add extlinux.conf support on some 32bit platforms

Vignesh Raghavedra (1):
prusw-fw-am65x-sr2: Add recipe for ICSSG Switch mode firmware for
AM65x SR2.0

Yogesh Siraswar (14):
linux-ti-staging: Update SRCREV to 5.10.65
linux-ti-staging-rt: Update SRCREV to 5.10.65
conf: omap-a15: fix the dtb file path for extlinux boot
conf: dra7xx-evm: ReIntroduce existent dtb* for 5.10
conf: am57xx-evm: ReIntroduce existent dtb* for 5.10
ti-linux-fw: Support common inc for all firmware
ti-linux-fw: AUTOREV support for ti-linux-fw
ti-sci-fw_git: Fix issue with using gp*.bin for TISCI firmware
linux-ti-staging: Bump linux version to latest
linux-ti-staging-rt: Bump linux rt version to latest
ti-linux-fw: Bump to 08.01.00.001 release
u-boot-ti-staging: Bump to 08.01.00.001 release
linux-ti-staging-rt: Bump to 08.01.00.001 release
linux-ti-staging: Bump to 08.01.00.001 release

conf/machine/am57xx-evm.conf | 6 +-
conf/machine/dra7xx-evm.conf | 8 +++
conf/machine/include/k3.inc | 6 +-
conf/machine/include/omap-a15.inc | 13 ++++-
conf/machine/include/ti33x.inc | 11 +++-
conf/machine/include/ti43x.inc | 11 +++-
conf/machine/j7-evm.conf | 2 +-
recipes-bsp/cadence-mhdp-fw/cadence-mhdp-fw_git.bb | 11 ++--
recipes-bsp/goodix-fw/goodix-fw_git.bb | 11 ++--
recipes-bsp/netcp-pa-fw/netcp-pa-fw_git.bb | 12 +---
recipes-bsp/netcp-sa-fw/netcp-sa-fw_git.bb | 12 +---
.../ti-img-rogue-driver_1.13.5776728.bb | 2 +-
.../powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb | 4 +-
recipes-bsp/pru/pru-icss_git.bb | 64 +++++++++++++++++++++-
recipes-bsp/prueth-fw/prueth-fw-am65x-sr2_git.bb | 11 +---
recipes-bsp/prueth-fw/prueth-fw-am65x_git.bb | 11 +---
recipes-bsp/prueth-fw/prueth-fw_5.6.15.bb | 10 +---
recipes-bsp/pruhsr-fw/pruhsr-fw_2.17.25.bb | 10 +---
recipes-bsp/pruprp-fw/pruprp-fw_2.17.25.bb | 10 +---
recipes-bsp/prusw-fw/prusw-fw-am65x-sr2_git.bb | 34 ++++++++++++
recipes-bsp/prusw-fw/prusw-fw_3.2.9.bb | 10 +---
recipes-bsp/qmss-pdsp-fw/qmss-pdsp-fw_git.bb | 11 ++--
recipes-bsp/serdes-fw/serdes-fw_git.bb | 10 ++--
recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 43 +++++++++++++++
recipes-bsp/ti-sci-fw/ti-sci-fw-source_git.bb | 2 +-
recipes-bsp/ti-sci-fw/ti-sci-fw.inc | 32 -----------
recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 7 ++-
recipes-bsp/u-boot/u-boot-ti-staging_2021.01.bb | 4 +-
recipes-kernel/linux/kernel-rdepends.inc | 2 +-
recipes-kernel/linux/linux-ti-staging-rt_5.10.bb | 4 +-
recipes-kernel/linux/linux-ti-staging_5.10.bb | 4 +-
recipes-ti/ipc/ti-rpmsg-char.inc | 6 +-
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 8 ++-
wic/sdimage-2part-efi.wks | 7 +++
34 files changed, 258 insertions(+), 151 deletions(-)
create mode 100644 recipes-bsp/prusw-fw/prusw-fw-am65x-sr2_git.bb
create mode 100644 recipes-bsp/ti-linux-fw/ti-linux-fw.inc
delete mode 100644 recipes-bsp/ti-sci-fw/ti-sci-fw.inc
create mode 100644 wic/sdimage-2part-efi.wks

--
2.7.4


[master][PATCH 04/22] linux-ti-staging-rt: Update SRCREV to 5.10.65

Denys Dmytriyenko
 

From: Yogesh Siraswar <yogeshs@...>

Update SRCREV to 5.10.65

Signed-off-by: Yogesh Siraswar <yogeshs@...>
Signed-off-by: Denys Dmytriyenko <denys@...>
---
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 7148c71..ae3904c 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 = "c0d9886f48dda1788995c4e0d6a7286d177df2f1"
-PV = "5.10.59+git${SRCPV}"
+SRCREV = "890b86772cff397e32c66ea6528fe8702d7e44a5"
+PV = "5.10.65+git${SRCPV}"
--
2.7.4


[master][PATCH 01/22] conf/machine: k3: Enable grub-efi by default in wic images

Denys Dmytriyenko
 

From: Tom Rini <tom.rini@...>

All of our platforms here support running EFI binaries. We can have wic
generate a simple grub.cfg file for us that will find the root partition
via PARTUUID and utilize the device tree that is already discoverable
via the EFI configuration tables. Assuming the EFI loader is U-Boot,
this device tree can be replaced at run-time by the normal mechanism of
loading in to memory and passing that address as an argument to bootefi.

Signed-off-by: Tom Rini <trini@...>
Reviewed-by: Denys Dmytriyenko <denys@...>
Signed-off-by: Yogesh Siraswar <yogeshs@...>
Signed-off-by: Denys Dmytriyenko <denys@...>
---
conf/machine/include/k3.inc | 6 +++++-
wic/sdimage-2part-efi.wks | 7 +++++++
2 files changed, 12 insertions(+), 1 deletion(-)
create mode 100644 wic/sdimage-2part-efi.wks

diff --git a/conf/machine/include/k3.inc b/conf/machine/include/k3.inc
index 20ab7a9..a39ddd2 100644
--- a/conf/machine/include/k3.inc
+++ b/conf/machine/include/k3.inc
@@ -44,8 +44,12 @@ IMAGE_BOOT_FILES_LEGACY = "${SPL_BINARY} u-boot.${UBOOT_SUFFIX} tiboot3.bin sysf
IMAGE_BOOT_FILES_MULTI_CERT = "${SPL_BINARY} u-boot.${UBOOT_SUFFIX} tiboot3.bin"

IMAGE_BOOT_FILES ?= "${IMAGE_BOOT_FILES_LEGACY}"
+IMAGE_EFI_BOOT_FILES ?= "${IMAGE_BOOT_FILES}"

-WKS_FILE ?= "sdimage-2part.wks"
+EFI_PROVIDER ?= "grub-efi"
+MACHINE_FEATURES += "efi"
+
+WKS_FILE ?= "sdimage-2part-efi.wks"
do_image_wic[depends] += "virtual/bootloader:do_deploy"
do_image_wic[mcdepends] += "mc::k3r5:virtual/bootloader:do_deploy mc::k3r5:ti-sci-fw:do_deploy"
do_image_tar[mcdepends] += "mc::k3r5:virtual/bootloader:do_deploy mc::k3r5:ti-sci-fw:do_deploy"
diff --git a/wic/sdimage-2part-efi.wks b/wic/sdimage-2part-efi.wks
new file mode 100644
index 0000000..ffb8d24
--- /dev/null
+++ b/wic/sdimage-2part-efi.wks
@@ -0,0 +1,7 @@
+# short-description: Create SD card image with 2 partitions and EFI support
+# long-description: Creates a partitioned SD card image for TI platforms that
+# supports EFI. Boot files are located in the first vfat partition with extra
+# reserved space. We cannot use a GPT here.
+bootloader --append="rootfstype=ext4 ro"
+part /boot --source bootimg-efi --sourceparams="loader=grub-efi" --fstype=vfat --label boot --active --align 1024 --use-uuid --fixed-size 128M
+part / --source rootfs --fstype=ext4 --label root --align 1024 --use-uuid
--
2.7.4


[dunfell][PATCH v3] ti-rtos-firmware: Update M4F binary for AM64x SoCs

Yogesh Siraswar
 

From: Hari Nagalla <hnagalla@...>

AM64x SoCs have a Cortex-M4F core in MCU domain. This core is used a
standalone device for safety applications. For non safety applications,
the device is exposed as a remote processor with Linux rpmsg framework.

Signed-off-by: Hari Nagalla <hnagalla@...>
Signed-off-by: Yogesh Siraswar <yogeshs@...>
---

Changes from v2:
1) Added missing install m4 binary for am64x

recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 ++++++
1 file changed, 6 insertions(+)

diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index d8ac2ee0..ea69ad89 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -62,6 +62,7 @@ do_install_prepend_am64xx() {
mv am64-main-r5f0_1-fw ipc_echo_baremetal_test_mcu1_1_release_strip.xer5f; \
mv am64-main-r5f1_0-fw ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f; \
mv am64-main-r5f1_1-fw ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f; \
+ mv am64-mcu-m4f0_0-fw ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f; \
)
}

@@ -111,6 +112,7 @@ do_install_am64xx() {
install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu1_1_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
+ install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
}

# Set up names for the firmwares
@@ -124,6 +126,7 @@ ALTERNATIVE_${PN}_am64xx = "\
am64-main-r5f0_1-fw \
am64-main-r5f1_0-fw \
am64-main-r5f1_1-fw \
+ am64-mcu-m4f0_0-fw \
"

ALTERNATIVE_${PN}_j7 = "\
@@ -154,6 +157,7 @@ TARGET_MAIN_R5FSS0_0_am64xx = "am64-main-r5f0_0-fw"
TARGET_MAIN_R5FSS0_1_am64xx = "am64-main-r5f0_1-fw"
TARGET_MAIN_R5FSS1_0_am64xx = "am64-main-r5f1_0-fw"
TARGET_MAIN_R5FSS1_1_am64xx = "am64-main-r5f1_1-fw"
+TARGET_MCU_M4FSS0_0_am64xx = "am64-mcu-m4f0_0-fw"

TARGET_MCU_R5FSS0_0_j7 = "j7-mcu-r5f0_0-fw"
TARGET_MCU_R5FSS0_1_j7 = "j7-mcu-r5f0_1-fw"
@@ -177,6 +181,7 @@ ALTERNATIVE_LINK_NAME[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_M
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}"
@@ -202,6 +207,7 @@ ALTERNATIVE_TARGET[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_e
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"
--
2.17.1


[master/dunfell PATCH v2] ti-rtos-firmware: Update M4F binary for AM64x SoCs

Hari Nagalla
 

AM64x SoCs have a Cortex-M4F core in MCU domain. This core is used a
standalone device for safety applications. For non safety applications,
the device is exposed as a remote processor with Linux rpmsg framework.

Signed-off-by: Hari Nagalla <hnagalla@...>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 5 +++++
1 file changed, 5 insertions(+)

diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 43de1ec2..db630ecc 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -62,6 +62,7 @@ do_install_prepend_am64xx() {
mv am64-main-r5f0_1-fw ipc_echo_baremetal_test_mcu1_1_release_strip.xer5f; \
mv am64-main-r5f1_0-fw ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f; \
mv am64-main-r5f1_1-fw ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f; \
+ mv am64-mcu-m4f0_0-fw ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f; \
)
}

@@ -124,6 +125,7 @@ ALTERNATIVE_${PN}_am64xx = "\
am64-main-r5f0_1-fw \
am64-main-r5f1_0-fw \
am64-main-r5f1_1-fw \
+ am64-mcu-m4f0_0-fw \
"

ALTERNATIVE_${PN}_j7 = "\
@@ -154,6 +156,7 @@ TARGET_MAIN_R5FSS0_0_am64xx = "am64-main-r5f0_0-fw"
TARGET_MAIN_R5FSS0_1_am64xx = "am64-main-r5f0_1-fw"
TARGET_MAIN_R5FSS1_0_am64xx = "am64-main-r5f1_0-fw"
TARGET_MAIN_R5FSS1_1_am64xx = "am64-main-r5f1_1-fw"
+TARGET_MCU_M4FSS0_0_am64xx = "am64-mcu-m4f0_0-fw"

TARGET_MCU_R5FSS0_0_j7 = "j7-mcu-r5f0_0-fw"
TARGET_MCU_R5FSS0_1_j7 = "j7-mcu-r5f0_1-fw"
@@ -177,6 +180,7 @@ ALTERNATIVE_LINK_NAME[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_M
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}"
@@ -202,6 +206,7 @@ ALTERNATIVE_TARGET[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_e
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"
--
2.17.1


Re: [master/dunfell PATCH v1] ti-rtos-firmware: Update M4F binary for AM64x SoCs

Suman Anna
 

Hi Hari,

On 10/26/21 8:00 PM, Hari Nagalla via lists.yoctoproject.org wrote:
AM46x SoCs have a Cortex-M4F core in MCU domain. This core is used a
%s/AM46x/AM64x/

Also, no need to add v1 for the first versions, you only need it on subsequent
revisions.


standalone device for safety applications. For non safety applications,
the device is exposed as a remote processor with Linux rpmsg framework.

Signed-off-by: Hari Nagalla <hnagalla@...>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 5 +++++
1 file changed, 5 insertions(+)

diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 43de1ec2..adc218f1 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -62,6 +62,7 @@ do_install_prepend_am64xx() {
mv am64-main-r5f0_1-fw ipc_echo_baremetal_test_mcu1_1_release_strip.xer5f; \
mv am64-main-r5f1_0-fw ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f; \
mv am64-main-r5f1_1-fw ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f; \
+ mv am64-mcu-m4f0_0-fw ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f; \
)
}

@@ -124,6 +125,7 @@ ALTERNATIVE_${PN}_am64xx = "\
am64-main-r5f0_1-fw \
am64-main-r5f1_0-fw \
am64-main-r5f1_1-fw \
+ am64-mcu-m4f0_0-fw \
"

ALTERNATIVE_${PN}_j7 = "\
@@ -154,6 +156,7 @@ TARGET_MAIN_R5FSS0_0_am64xx = "am64-main-r5f0_0-fw"
TARGET_MAIN_R5FSS0_1_am64xx = "am64-main-r5f0_1-fw"
TARGET_MAIN_R5FSS1_0_am64xx = "am64-main-r5f1_0-fw"
TARGET_MAIN_R5FSS1_1_am64xx = "am64-main-r5f1_1-fw"
+TARGET_MCU_R4FSS0_0_am64xx = "am64-mcu-m4f0_0-fw"
%s/R4FSS0/M4FSS0/


TARGET_MCU_R5FSS0_0_j7 = "j7-mcu-r5f0_0-fw"
TARGET_MCU_R5FSS0_1_j7 = "j7-mcu-r5f0_1-fw"
@@ -177,6 +180,7 @@ ALTERNATIVE_LINK_NAME[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_M
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}"
ou have the variable name correct here. Makes me wonder if this patch is even
tested.

regards
Suman


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}"
@@ -202,6 +206,7 @@ ALTERNATIVE_TARGET[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_e
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"





[master/dunfell PATCH v1] ti-rtos-firmware: Update M4F binary for AM64x SoCs

Hari Nagalla
 

AM46x SoCs have a Cortex-M4F core in MCU domain. This core is used a
standalone device for safety applications. For non safety applications,
the device is exposed as a remote processor with Linux rpmsg framework.

Signed-off-by: Hari Nagalla <hnagalla@...>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 5 +++++
1 file changed, 5 insertions(+)

diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 43de1ec2..adc218f1 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -62,6 +62,7 @@ do_install_prepend_am64xx() {
mv am64-main-r5f0_1-fw ipc_echo_baremetal_test_mcu1_1_release_strip.xer5f; \
mv am64-main-r5f1_0-fw ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f; \
mv am64-main-r5f1_1-fw ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f; \
+ mv am64-mcu-m4f0_0-fw ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f; \
)
}

@@ -124,6 +125,7 @@ ALTERNATIVE_${PN}_am64xx = "\
am64-main-r5f0_1-fw \
am64-main-r5f1_0-fw \
am64-main-r5f1_1-fw \
+ am64-mcu-m4f0_0-fw \
"

ALTERNATIVE_${PN}_j7 = "\
@@ -154,6 +156,7 @@ TARGET_MAIN_R5FSS0_0_am64xx = "am64-main-r5f0_0-fw"
TARGET_MAIN_R5FSS0_1_am64xx = "am64-main-r5f0_1-fw"
TARGET_MAIN_R5FSS1_0_am64xx = "am64-main-r5f1_0-fw"
TARGET_MAIN_R5FSS1_1_am64xx = "am64-main-r5f1_1-fw"
+TARGET_MCU_R4FSS0_0_am64xx = "am64-mcu-m4f0_0-fw"

TARGET_MCU_R5FSS0_0_j7 = "j7-mcu-r5f0_0-fw"
TARGET_MCU_R5FSS0_1_j7 = "j7-mcu-r5f0_1-fw"
@@ -177,6 +180,7 @@ ALTERNATIVE_LINK_NAME[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_M
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}"
@@ -202,6 +206,7 @@ ALTERNATIVE_TARGET[am64-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_e
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"
--
2.17.1


Re: [dunfell][PATCH 0/4] Core-sdk 08.01.00.001 release

Denys Dmytriyenko
 

On Mon, Oct 25, 2021 at 09:31:36PM +0000, Yogesh Siraswar via lists.yoctoproject.org wrote:
Updated the version for core-sdk 08.01.00.001 release
For the entire series:

Reviewed-by: Denys Dmytriyenko <denys@...>


Yogesh Siraswar (4):
ti-linux-fw: Bump to 08.01.00.001 release
u-boot-ti-staging: Bump to 08.01.00.001 release
linux-ti-staging-rt: Bump to 08.01.00.001 release
linux-ti-staging: Bump to 08.01.00.001 release

recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 10 +++++-----
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, 9 insertions(+), 9 deletions(-)

--
2.17.1
--
Regards,
Denys Dmytriyenko <denis@...>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964


[dunfell][PATCH 2/4] u-boot-ti-staging: Bump to 08.01.00.001 release

Yogesh Siraswar
 

Updated the u-boot version for 08.01.00.001

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---
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 53a95f20..db8dc9d6 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 = "r11"
+PR = "r12"

BRANCH = "ti-u-boot-2021.01"

-SRCREV = "53e79d0e89f975eeb874366dd9a92f68b3a599d1"
+SRCREV = "316948e851b21f1f79e78fdd364a754cf9817038"
--
2.17.1


[dunfell][PATCH 3/4] linux-ti-staging-rt: Bump to 08.01.00.001 release

Yogesh Siraswar
 

Updated the linux-rt version for 08.01.00.001

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---
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 8a1f3812..166f40da 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 = "6f4d81d846c7c548ccc05498c4ad824f31dd6fc0"
+SRCREV = "b9f28fcb222bc4508077366b05ad5d44984087b0"
PV = "5.10.65+git${SRCPV}"
--
2.17.1


[dunfell][PATCH 4/4] linux-ti-staging: Bump to 08.01.00.001 release

Yogesh Siraswar
 

Updated the linux version for 08.01.00.001

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---
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 4b34756d..d620b022 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 = "85ac70d78c4ec6889dec24685ec4cea3bb4d5a59"
+SRCREV = "f22103162c771ddd47372b579682445e6dc8dd0e"
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 1/4] ti-linux-fw: Bump to 08.01.00.001 release

Yogesh Siraswar
 

Updated the firmware version for 08.01.00.001

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---
recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/recipes-bsp/ti-linux-fw/ti-linux-fw.inc b/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
index 80177f06..56a16e80 100644
--- a/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
+++ b/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
@@ -3,25 +3,25 @@ SUMMARY = "TI SCI firmware (SYSFW)"
LICENSE = "TI-TFL"
LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=b5aebf0668bdf95621259288c4a46d76"

-PV = "2021.05"
+PV = "2021.09"
INC_PR = "r1"

# Firmware versions
-CORESDK_RTOS_VERSION = "08.00.00.32"
+CORESDK_RTOS_VERSION = "08.01.00.01"
SERDES_FW_VERSION = "3.3.0.2c"
NETCP_SA_FW_VERSION = "1.0.0"
NETCP_PA_FW_VERSION = "3.0.2.3"
QMSS_PDSP_FW_VERSION = "1.0.0.9"
PRUETH_FW_AM65X_VERSION = "08.00.00.20"
-PRUETH_FW_AM65X_SR2_VERSION = "02.02.09.03"
+PRUETH_FW_AM65X_SR2_VERSION = "02.02.09.06"
GOODIX_FW_VERSION = "1.0.0.0"
CADENCE_MHDP_FW_VERSION = "1.2.17"

-TI_LINUX_FW_SRCREV ?= "793309716bce2e443f798dd5c5f0d8dd310970c0"
+TI_LINUX_FW_SRCREV ?= "10bcf8564c6e9277e7f402fb02cf941956d0d3eb"
SRCREV = "${TI_LINUX_FW_SRCREV}"

BRANCH ?= "ti-linux-firmware"
-SRCREV_imggen = "b65ae80847f5a0d1885ed6e4de4d9d635544053c"
+SRCREV_imggen = "e182c3114f11eea3ec7ebb88cb1ef563a78d4eda"
SRCREV_FORMAT = "imggen"

SRC_URI = " \
--
2.17.1


[dunfell][PATCH 0/4] Core-sdk 08.01.00.001 release

Yogesh Siraswar
 

Updated the version for core-sdk 08.01.00.001 release

Yogesh Siraswar (4):
ti-linux-fw: Bump to 08.01.00.001 release
u-boot-ti-staging: Bump to 08.01.00.001 release
linux-ti-staging-rt: Bump to 08.01.00.001 release
linux-ti-staging: Bump to 08.01.00.001 release

recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 10 +++++-----
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, 9 insertions(+), 9 deletions(-)

--
2.17.1


Re: [dunfell][PATCH v2] ti-sci-fw_git: Fix issue with using gp*.bin for TISCI firmware

Yogesh Siraswar
 

On 10/21/2021 3:52 PM, Denys Dmytriyenko wrote:
On Thu, Oct 21, 2021 at 07:04:41AM +0000, Yogesh Siraswar via lists.yoctoproject.org wrote:
With ti-sysfs also hosting *gp-cert.bin for am64x hs-fs breaks gp.
This patch removes * to directly reference the TISCI firmware

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---

Change from v1:
Previous version caused issue with the HS platforms.
Added conditional statement for HS device.

recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
index ca56e1de..a1a7446b 100644
--- a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
+++ b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
@@ -27,8 +27,9 @@ SYSFW_PREFIX_j7-hs-evm-k3r5 = "ti-fs-firmware"
SYSFW_SUFFIX ?= "unknown"
SYSFW_BASE = "${SYSFW_PREFIX}-${SYSFW_SOC}-${SYSFW_SUFFIX}"
+SYSFW_BASE_append = "${@['','*']['${SYSFW_SUFFIX}' == 'hs']}"
This kind of makes sense, but I'm afraid it could negatively affect
SYSFW_HS_PATH and SYSFW_HS_INNER_CERT_PATH having * and passed to the
Makefile:
EXTRA_OEMAKE_HS = " \
HS=1 SYSFW_HS_PATH="${S}/ti-sysfw/${SYSFW_BASE}-enc.bin" SYSFW_HS_INNER_CERT_PATH="${S}/ti-sysfw/${SYSFW_BASE}-cert.bin" \
"
This is similar to what we had for GP device :). Yes, its not idle but need more time to think this through. So will merge this for now since the builds are passing for both GP and HS..


-SYSFW_TISCI = "${S}/ti-sysfw/${SYSFW_BASE}*.bin"
+SYSFW_TISCI = "${S}/ti-sysfw/${SYSFW_BASE}.bin"
SYSFW_BINARY = "sysfw-${SYSFW_SOC}-${SYSFW_CONFIG}.itb"
SYSFW_VBINARY = "sysfw-${PV}-${SYSFW_SOC}-${SYSFW_CONFIG}.itb"
--
2.17.1


Re: [dunfell/master][PATCH] conf: j7-evm: Replace eaik dtb with sk to KERNEL_DEVICETREE

Denys Dmytriyenko
 

On Wed, Oct 20, 2021 at 07:52:21PM -0500, praneeth via lists.yoctoproject.org wrote:


On 10/20/2021 12:42 PM, Sinthu Raja M wrote:
Denys,

On Tue, Oct 19, 2021 at 10:45 PM Denys Dmytriyenko <denis@...> wrote:

On Tue, Oct 19, 2021 at 01:52:21PM +0530, Sinthu Raja wrote:
From: Sinthu Raja <sinthu.raja@...>

The board name for J721E EdgeAI Kit (EAIK) is changed to J721E SK [1],
so replace the eaik dtb with sk dtb file

[1] https://www.ti.com/tool/SK-TDA4VM

Signed-off-by: Sinthu Raja <sinthu.raja@...>
---
conf/machine/j7-evm.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/j7-evm.conf b/conf/machine/j7-evm.conf
index 7cde9f4d..1f47f00c 100644
--- a/conf/machine/j7-evm.conf
+++ b/conf/machine/j7-evm.conf
@@ -13,7 +13,7 @@ KERNEL_DEVICETREE = " \
ti/k3-j721e-common-proc-board.dtb \
ti/k3-j721e-proc-board-tps65917.dtb \
ti/k3-j721e-common-proc-board-infotainment.dtbo \
- ti/k3-j721e-eaik.dtb \
+ ti/k3-j721e-sk.dtb \
Was there a corresponding kernel change with the file rename?
Yes, The kernel changes are there in the review state and will get merged today.
merged now :
https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?h=ti-linux-5.10.y&id=2654df7db9e8f024be9ac4e769cdb454a61907e0
And kernel recipe should also have been updated first before changing
KERNEL_DEVICETREE - I see Yogesh is taking care of that:
https://lists.yoctoproject.org/g/meta-ti/message/14082



Regards,
Sinthu Raja.

"

UBOOT_MACHINE = "j721e_evm_a72_config"
--
2.31.1
--
Regards,
Denys Dmytriyenko <denis@...>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964


Re: [dunfell][PATCH v2] ti-sci-fw_git: Fix issue with using gp*.bin for TISCI firmware

Denys Dmytriyenko
 

On Thu, Oct 21, 2021 at 07:04:41AM +0000, Yogesh Siraswar via lists.yoctoproject.org wrote:
With ti-sysfs also hosting *gp-cert.bin for am64x hs-fs breaks gp.
This patch removes * to directly reference the TISCI firmware

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---

Change from v1:
Previous version caused issue with the HS platforms.
Added conditional statement for HS device.

recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
index ca56e1de..a1a7446b 100644
--- a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
+++ b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
@@ -27,8 +27,9 @@ SYSFW_PREFIX_j7-hs-evm-k3r5 = "ti-fs-firmware"
SYSFW_SUFFIX ?= "unknown"

SYSFW_BASE = "${SYSFW_PREFIX}-${SYSFW_SOC}-${SYSFW_SUFFIX}"
+SYSFW_BASE_append = "${@['','*']['${SYSFW_SUFFIX}' == 'hs']}"
This kind of makes sense, but I'm afraid it could negatively affect
SYSFW_HS_PATH and SYSFW_HS_INNER_CERT_PATH having * and passed to the
Makefile:

EXTRA_OEMAKE_HS = " \
HS=1 SYSFW_HS_PATH="${S}/ti-sysfw/${SYSFW_BASE}-enc.bin" SYSFW_HS_INNER_CERT_PATH="${S}/ti-sysfw/${SYSFW_BASE}-cert.bin" \
"


-SYSFW_TISCI = "${S}/ti-sysfw/${SYSFW_BASE}*.bin"
+SYSFW_TISCI = "${S}/ti-sysfw/${SYSFW_BASE}.bin"

SYSFW_BINARY = "sysfw-${SYSFW_SOC}-${SYSFW_CONFIG}.itb"
SYSFW_VBINARY = "sysfw-${PV}-${SYSFW_SOC}-${SYSFW_CONFIG}.itb"
--
2.17.1
--
Regards,
Denys Dmytriyenko <denis@...>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964


Re: Dunfell, populate_sdk, how to build development image?

Denys Dmytriyenko
 

On Thu, Oct 21, 2021 at 02:53:23PM -0400, John wrote:
On Thu, Oct 21, 2021 at 1:34 PM John via lists.yoctoproject.org
<r10kindsofpeople=gmail.com@...> wrote:

I've got a booting image for the AM335x under dunfell and so went on to
what I thought would be the easy step of building the cross-development
image using -c populate_sdk. It completes, but when I try to install it,
it locks up at the 'cannot access /opt/poky/environment-setup-*' stage, and
it seems to be missing some other significant pieces, at least most of the
x86_64-arago-linux folder.

Any suggestions on how to move forward?

Or was my first mistake 'dunfell', and if so, suggestions on how far back
to step? I got the impression that the TI SDK 07.03.00.005 was using
dunfell.
Sorry, I seem to have hit on the right search parameters shortly after
hitting 'send'.
See
https://www.openembedded.org/pipermail/openembedded-core/2015-July/106931.html

In arago-image.inc, I believe:
TOOLCHAIN_HOST_TASK += "nativesdk-buildtools-perl-dummy"
should be
TOOLCHAIN_HOST_TASK_append += "nativesdk-buildtools-perl-dummy"

I haven't built anything with the resulting SDK yet, but the install
completed.
John,

Thank you for your report!

It appears your email should have been sent to meta-arago mailing list
instead. As meta-ti is just a BSP layer for TI platforms, it is not specific
to TI SDK, since it does not define any distro policies, SDKs or even any
rootfs images. Hence there's no arago-image.inc file. Any distro could
utilize meta-ti, define own images and create SDKs with -c populate_sdk
w/o problems.

As of meta-arago, it uses a different approach for creating SDKs by defining
meta-toolchain recipes due to the way it uses toolchains and supports both
external and internal toolchain variants. But that's a topic for a different
mailing list...

--
Regards,
Denys Dmytriyenko <denis@...>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964


Re: Dunfell, populate_sdk, how to build development image?

John
 

On Thu, Oct 21, 2021 at 1:34 PM John via lists.yoctoproject.org <r10kindsofpeople=gmail.com@...> wrote:
I've got a booting image for the AM335x under dunfell and so went on to what I thought would be the easy step of building the cross-development image using -c populate_sdk.  It completes, but when I try to install it, it locks up at the 'cannot access /opt/poky/environment-setup-*' stage, and it seems to be missing some other significant pieces, at least most of the x86_64-arago-linux folder.  

Any suggestions on how to move forward?  

Or was my first mistake 'dunfell', and if so, suggestions on how far back to step?  I got the impression that the TI SDK 07.03.00.005 was using dunfell.  

John

Sorry, I seem to have hit on the right search parameters shortly after hitting 'send'.  

In arago-image.inc, I believe:
TOOLCHAIN_HOST_TASK += "nativesdk-buildtools-perl-dummy"
should be
TOOLCHAIN_HOST_TASK_append +=  "nativesdk-buildtools-perl-dummy"

I haven't built anything with the resulting SDK yet, but the install completed. 

John


[dunfell][PATCH 2/2] linux-ti-staging-rt: Bump linux rt version to latest

Yogesh Siraswar
 

To merge j7 dtb name change patch need to bump the linux and linux rt
before the point release

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---
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 a5fd6957..8a1f3812 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 = "890b86772cff397e32c66ea6528fe8702d7e44a5"
+SRCREV = "6f4d81d846c7c548ccc05498c4ad824f31dd6fc0"
PV = "5.10.65+git${SRCPV}"
--
2.17.1


[dunfell][PATCH 1/2] linux-ti-staging: Bump linux version to latest

Yogesh Siraswar
 

To merge the dtb file name change patch in meta-ti for j7 need to bump
linux version

Signed-off-by: Yogesh Siraswar <yogeshs@...>
---
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 aecac1b6..4b34756d 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 = "1d48ab8a3d3b58f74c02223a797dd80964310b3b"
+SRCREV = "85ac70d78c4ec6889dec24685ec4cea3bb4d5a59"
PV = "5.10.65+git${SRCPV}"

# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
--
2.17.1

861 - 880 of 14961