Praneeth To pick AM64x mcu-plus-sdk FW, we have pinned coresdk-rtos-releases repo to a latest commit - "e558080592d910783bf2f9ad46ed3b622f899155" There was one latest build happened for AM65x under coresdk-rtos-releases repo commit - "e558080592d910783bf2f9ad46ed3b622f899155"and hence the DEFAULT_FIRMWARE_SHA256SUM_am65xx got updated. For J7 and j7200-evm, no new release builds triggered by PDK and hence no changes in respective SHA256SUM
Regards, Shiju -----Original Message----- From: Bajjuri, Praneeth Sent: Saturday, March 13, 2021 8:11 AM To: Denys Dmytriyenko <[email protected]>; Sivasankaran, Shiju <[email protected]> Cc: [email protected] Subject: Re: [meta-ti] [dunfell/next v2 PATCH] ti-rtos: update to uisng fw from mcu-plus-sdk for AM64x On 3/12/2021 5:07 PM, Denys Dmytriyenko wrote: > On Thu, Mar 11, 2021 at 03:54:30PM +0530, Shiju Sivasankaran via > lists.yoctoproject.org wrote: >> update ti-rtos-metadata and ti-rtos-firmware recipes of meta-ti to >> pick AM64x rtos firmware from mcu-plus-sdk instead of PDK. >> >> Other devices such as AM65x, J7 continue to use fw from PDK. >> >> Built and tested both IPC echo test applications - "rpmsg_client_sample” >> & “rpmsg_char_simple”. Both tests passed for all remote R5F cores on >> AM64x EVM >> >> Signed-off-by: Shiju Sivasankaran <[email protected]> >> --- >> v2: rebased to dunfell-next >> DEFAULT_FIRMWARE_SHA256SUM_am65xx updated > > Why are you updating am65xx when you said only am64xx is being > switched from PDK to mcu-plus-sdk? > > Also, can you explain what is it and why it has to be the default for am64x? > Shouldn't CoreSDK Linux pick CoreSDK RTOS (i.e. PDK) components by default? > > Thanks. > > >> recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 14 +++++++++----- >> recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 3 ++- >> 2 files changed, 11 insertions(+), 6 deletions(-) >> >> diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb >> b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb >> index 507d0000..c70fc50d 100644 >> --- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb >> +++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb >> @@ -11,17 +11,20 @@ INHIBIT_DEFAULT_DEPS = "1" >> >> inherit deploy >> >> +DEFAULT_METADATA_FILE ?= "metadata.inc" >> +DEFAULT_METADATA_FILE_am64xx ?= "mcusdk_metadata.inc" >> + >> # First, let's try including metadata.inc that could be fetched and >> deployed >> # by ti-rtos-metadata earlier and provide new set of CORESDK_RTOS_* >> variables -include ${DEPLOY_DIR_IMAGE}/metadata.inc >> +include ${DEPLOY_DIR_IMAGE}/${DEFAULT_METADATA_FILE} >> >> # Set some defaults for when metadata.inc is not available >> DEFAULT_RTOS_FAMILY = "jacinto" >> DEFAULT_RTOS_VERSION = "07_03_00_16" >> DEFAULT_RTOS_VERSION_DOT = "07.03.00.16" >> >> -DEFAULT_RTOS_VERSION_am64xx = "07_03_01_06" >> -DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.01.06" >> +DEFAULT_RTOS_VERSION_am64xx = "07_03_00_03" >> +DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.03" >> >> DEFAULT_RTOS_SOC = "undefined" >> DEFAULT_RTOS_SOC_j7 = "j721e" >> @@ -36,6 +39,7 @@ DEFAULT_RTOS_WEBLINK_am65xx = >> "https://software-dl.ti.com/processor-sdk-rtos/esd >> DEFAULT_RTOS_WEBLINK_am64xx = >> "https://software-dl.ti.com/processor-sdk-rtos/esd/AM64X/firmware/${CORESDK_RTOS_VERSION}"; >> >> DEFAULT_FIRMWARE_FILE = >> "coresdk_rtos_${CORESDK_RTOS_SOC}_${CORESDK_RTOS_VERSION}_firmware.tar.xz" >> +DEFAULT_FIRMWARE_FILE_am64xx = >> "mcu_plus_sdk_${CORESDK_RTOS_SOC}_${CORESDK_RTOS_VERSION}_firmware.tar.xz" >> >> DEFAULT_FIRMWARE_URL = "file://empty" >> DEFAULT_FIRMWARE_URL_k3 = >> "${CORESDK_RTOS_WEBLINK}/${DEFAULT_FIRMWARE_FILE}" >> @@ -43,8 +47,8 @@ DEFAULT_FIRMWARE_URL_k3 = >> "${CORESDK_RTOS_WEBLINK}/${DEFAULT_FIRMWARE_FILE}" >> DEFAULT_FIRMWARE_SHA256SUM = "unknown" >> DEFAULT_FIRMWARE_SHA256SUM_j7 = >> "78f3ab929a0f3c6e2907538061de82e16d8aff7ffb2fac0c3c4d56df8abec3b0" >> DEFAULT_FIRMWARE_SHA256SUM_j7200-evm = >> "5bae696d35e206bbcd9b26ab6508af59a2c2d72f9b89aa1d3fc1aa808f7a8615" >> -DEFAULT_FIRMWARE_SHA256SUM_am65xx = >> "7bd854dbf96c25683d684ac731fde3edd7fb8a65f8727f7aae3802a2e9a9cab6" >> -DEFAULT_FIRMWARE_SHA256SUM_am64xx = >> "450bf23d659756695d62168fe06eebe4641522293d89692a9eea837426bac0f9" >> +DEFAULT_FIRMWARE_SHA256SUM_am65xx = >> "d3cffd472fdd17b000afcee806318344e6033ac271ab3a6fa9ca8f432e8420c9" Shiju, Fix this , AM65xx update doesnt make sense in this patch. >> +DEFAULT_FIRMWARE_SHA256SUM_am64xx = >> "bc2d3d603ad30006ea3fefa3e777c26c19b95ee6d6f5a630259009f2f5a4996b" >> >> # Use weak assignment for CORESDK_RTOS_* variables to use defaults if not >> yet set >> CORESDK_RTOS_FAMILY ?= "${DEFAULT_RTOS_FAMILY}" >> diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb >> b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb >> index 9bb0d3c5..466a22a8 100644 >> --- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb >> +++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb >> @@ -18,10 +18,11 @@ PLAT_SFX_am64xx = "/am64x" >> # Use weak assignment to set defaults to TI_RTOS_METADATA_* variables >> TI_RTOS_METADATA_URI ?= >> "git://git.ti.com/processor-sdk/coresdk_rtos_releases.git" >> TI_RTOS_METADATA_PROTOCOL ?= "git" >> -TI_RTOS_METADATA_SRCREV ?= "ba81dc5a9342fc35435920092a0df2cb2ab342ef" >> +TI_RTOS_METADATA_SRCREV ?= "e558080592d910783bf2f9ad46ed3b622f899155" >> TI_RTOS_METADATA_BRANCH ?= "master" >> TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}" >> TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc" >> +TI_RTOS_METADATA_FILE_am64xx ?= >> "${S}${TI_RTOS_METADATA_DIR}/mcusdk_metadata.inc" >> >> PV = "1.0.0+git${SRCPV}" >> >> -- >> 2.17.1 >> >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13529): https://lists.yoctoproject.org/g/meta-ti/message/13529 Mute This Topic: https://lists.yoctoproject.org/mt/81249389/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
