<1> Yes, All the FW are hosted on same repo processor-sdk/coresdk_rtos_releases. But its only hosting purpose, these FW are builds from PDK (all device except AM64x) and mcu-plus-sdk (AM64x alone) Similarly metadata.inc will be used to get the version/urls details for all devices except AM64x and mcusdk_metadata.inc is used for AM64x. Same metadata.inc for mcu-plus-sdk is a big risk as any PDK build of AM64x can override this.
<2> coresdk_rtos_releases has 2 branches - master & next. All metadata files and tags are applied on next and during RC period coreSDK team merge next to master. At the same time next-branch also carry the metadata files from daily build as well. During this merge they make sure only release builds of all devices on that tag/commit, as only release build points the FW url from external location. If any daily build of any device happens in between the tagging and as daily build has TI internal url for FW will spoil the purpose. AM65x, J7 & J7200 builds of PSDK should have happen one after another without any daily builds in between, this can be controlled as all these are built from same codebase of PDK. As AM64x builds from mcu-plus-sdk, a different codebase, code-freeze and RC timing rarely match. Rebuild of all devices and recipe updates will arises if builds from both repo doesn't happen at same time. Separate TI_RTOS_METADATA_SRCREV_am64xx is added to avoid this syncing of builds from two different repos. <3> I will correct the typo in the commit-comment -----Original Message----- From: Bajjuri, Praneeth Sent: Friday, March 26, 2021 3:04 AM To: Sivasankaran, Shiju <[email protected]>; [email protected] Subject: Re: [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware On 3/25/2021 1:30 AM, Shiju Sivasankaran wrote: > updated rtos firmware > am64xx: 07.03.00.13 > > rtos fw of am64x build and upload from mcu-plus-sdk repo. > rtos fw of am65x, j7 and j7200 build and upload from pdk repo. But all of the fws are coming from the same repo processor-sdk/coresdk_rtos_releases where metadata.inc is updated on master with right tag and public urls inside the metadata_*.inc isnt it ? > a separate TI_RTOS_METADATA_SRCREV_am64xx for pining am64x fw from > macu-plus-sdk typo s/macu? avoids syncing of builds from two different repos. TI_RTOS_METADATA_SRCREV is pointing to master branch commitsha where the given tag is present. I dont see why we have to seperate this macro for each device seperately. Add your signoff by. > --- > recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 +++--- > recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 1 + > 2 files changed, 4 insertions(+), 3 deletions(-) > > diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb > b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb > index e85948b2..fe020aa3 100644 > --- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb > +++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb > @@ -23,8 +23,8 @@ DEFAULT_RTOS_FAMILY = "jacinto" > DEFAULT_RTOS_VERSION = "07_03_00_21" > DEFAULT_RTOS_VERSION_DOT = "07.03.00.21" > > -DEFAULT_RTOS_VERSION_am64xx = "07_03_00_03" > -DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.03" > +DEFAULT_RTOS_VERSION_am64xx = "07_03_00_13" > +DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.13" > > DEFAULT_RTOS_VERSION_am65xx = "07_03_00_22" > DEFAULT_RTOS_VERSION_DOT_am65xx = "07.03.00.22" > @@ -51,7 +51,7 @@ DEFAULT_FIRMWARE_SHA256SUM = "unknown" > DEFAULT_FIRMWARE_SHA256SUM_j7 = > "fc7805ed3d6c1801efb2b85ac9af99a8657aa3a7a9327bc16a1163d566f11c2c" > DEFAULT_FIRMWARE_SHA256SUM_j7200-evm = > "71f282ba6768ad3b603a17d30851cc621986c88311c174960a50196bfc79f85c" > DEFAULT_FIRMWARE_SHA256SUM_am65xx = > "61e0be08bea8ab1055645bd96504a6a29c70318c5b277237dee9981cd94d7f79" > -DEFAULT_FIRMWARE_SHA256SUM_am64xx = > "bc2d3d603ad30006ea3fefa3e777c26c19b95ee6d6f5a630259009f2f5a4996b" > +DEFAULT_FIRMWARE_SHA256SUM_am64xx = > "0c43cea6ccaf45b3d7c48996f1c561e814a6e409a330da5d45877c82ce7a299a" > > # 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 83e0e901..f052c627 100644 > --- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb > +++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb > @@ -19,6 +19,7 @@ PLAT_SFX_am64xx = "/am64x" > TI_RTOS_METADATA_URI ?= > "git://git.ti.com/processor-sdk/coresdk_rtos_releases.git" > TI_RTOS_METADATA_PROTOCOL ?= "git" > TI_RTOS_METADATA_SRCREV ?= "3cda650c9e22eb4fd4eb5797ad998991a6124243" > +TI_RTOS_METADATA_SRCREV_am64xx ?= "051de801b539f4acc6e7630684f9993e34332dde" Why this? Why TI_RTOS_METADATA_SRCREV ?= "051de801b539f4acc6e7630684f9993e34332dde" willnot work for all devices? > TI_RTOS_METADATA_BRANCH ?= "master" > TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}" > TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc" >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13573): https://lists.yoctoproject.org/g/meta-ti/message/13573 Mute This Topic: https://lists.yoctoproject.org/mt/81596325/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
