* [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
@ 2021-03-25 6:30 Shiju Sivasankaran
2021-03-25 21:34 ` praneeth
0 siblings, 1 reply; 8+ messages in thread
From: Shiju Sivasankaran @ 2021-03-25 6:30 UTC (permalink / raw)
To: meta-ti; +Cc: Praneeth Bajjuri, Shiju Sivasankaran
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.
a separate TI_RTOS_METADATA_SRCREV_am64xx for pining am64x fw
from macu-plus-sdk avoids syncing of builds from two different repos.
---
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"
TI_RTOS_METADATA_BRANCH ?= "master"
TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}"
TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc"
--
2.17.1
^ permalink raw reply related [flat|nested] 8+ messages in thread* Re: [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
2021-03-25 6:30 [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware Shiju Sivasankaran
@ 2021-03-25 21:34 ` praneeth
2021-03-26 3:49 ` Shiju Sivasankaran
0 siblings, 1 reply; 8+ messages in thread
From: praneeth @ 2021-03-25 21:34 UTC (permalink / raw)
To: Shiju Sivasankaran, meta-ti
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"
>
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
2021-03-25 21:34 ` praneeth
@ 2021-03-26 3:49 ` Shiju Sivasankaran
0 siblings, 0 replies; 8+ messages in thread
From: Shiju Sivasankaran @ 2021-03-26 3:49 UTC (permalink / raw)
To: Bajjuri, Praneeth, meta-ti@lists.yoctoproject.org
<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 <shiju@ti.com>; meta-ti@lists.yoctoproject.org
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"
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
@ 2021-03-26 7:17 Shiju Sivasankaran
0 siblings, 0 replies; 8+ messages in thread
From: Shiju Sivasankaran @ 2021-03-26 7:17 UTC (permalink / raw)
To: meta-ti; +Cc: Praneeth Bajjuri, Shiju Sivasankaran
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.
a separate TI_RTOS_METADATA_SRCREV_am64xx for pining am64x fw
from mcu-plus-sdk avoids syncing of builds from two different repos.
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
---
v2 - typo in the commit-message corrected
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.
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.
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"
TI_RTOS_METADATA_BRANCH ?= "master"
TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}"
TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc"
--
2.17.1
^ permalink raw reply related [flat|nested] 8+ messages in thread* [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
@ 2021-03-29 4:11 Shiju Sivasankaran
2021-03-29 4:41 ` praneeth
0 siblings, 1 reply; 8+ messages in thread
From: Shiju Sivasankaran @ 2021-03-29 4:11 UTC (permalink / raw)
To: meta-ti; +Cc: Praneeth Bajjuri, Shiju Sivasankaran
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.
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
---
v3 - The way this system was designed is to be used with nightly builds
where commit is AUTOREV-ed (from next branch) and should work the same with
master branch as well, hence TI_RTOS_METADATA_SRCREV_am64xx is removed
from previous patch
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 +++---
recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 2 +-
2 files changed, 4 insertions(+), 4 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..d7f22a1a 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
@@ -18,7 +18,7 @@ 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 ?= "3cda650c9e22eb4fd4eb5797ad998991a6124243"
+TI_RTOS_METADATA_SRCREV ?= "051de801b539f4acc6e7630684f9993e34332dde"
TI_RTOS_METADATA_BRANCH ?= "master"
TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}"
TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc"
--
2.17.1
^ permalink raw reply related [flat|nested] 8+ messages in thread* Re: [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
2021-03-29 4:11 Shiju Sivasankaran
@ 2021-03-29 4:41 ` praneeth
0 siblings, 0 replies; 8+ messages in thread
From: praneeth @ 2021-03-29 4:41 UTC (permalink / raw)
To: Shiju Sivasankaran, meta-ti
On 3/28/2021 11:11 PM, 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.
This patch is not doing anything on non AM64x device.
so this message about am65,j7* is redundant on what this patch is
actually trying to address.
>
> Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
> ---
>
> v3 - The way this system was designed is to be used with nightly builds
> where commit is AUTOREV-ed (from next branch) and should work the same with
> master branch as well, hence TI_RTOS_METADATA_SRCREV_am64xx is removed
> from previous patch
>
> recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 +++---
> recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 2 +-
> 2 files changed, 4 insertions(+), 4 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..d7f22a1a 100644
> --- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
> +++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
> @@ -18,7 +18,7 @@ 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 ?= "3cda650c9e22eb4fd4eb5797ad998991a6124243"
> +TI_RTOS_METADATA_SRCREV ?= "051de801b539f4acc6e7630684f9993e34332dde"
> TI_RTOS_METADATA_BRANCH ?= "master"
> TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}"
> TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc"
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
@ 2021-03-31 18:56 Shiju Sivasankaran
0 siblings, 0 replies; 8+ messages in thread
From: Shiju Sivasankaran @ 2021-03-31 18:56 UTC (permalink / raw)
To: meta-ti; +Cc: Praneeth Bajjuri, Shiju Sivasankaran
updated am64x rtos release mode firmware
am64xx: 07.03.00.18
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 +++---
recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 1820858f..176d0ad0 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_13"
-DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.13"
+DEFAULT_RTOS_VERSION_am64xx = "07_03_00_18"
+DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.18"
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 = "0c43cea6ccaf45b3d7c48996f1c561e814a6e409a330da5d45877c82ce7a299a"
+DEFAULT_FIRMWARE_SHA256SUM_am64xx = "1b44bccd20b767568e996e924a2ef18cabd1c3e16d3412629ff72d83b81b152f"
# 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 d7f22a1a..c07e932d 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
@@ -18,7 +18,7 @@ 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 ?= "051de801b539f4acc6e7630684f9993e34332dde"
+TI_RTOS_METADATA_SRCREV ?= "12a455643928b9fc22af4d85f2aac7894b80e6a5"
TI_RTOS_METADATA_BRANCH ?= "master"
TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}"
TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc"
--
2.17.1
^ permalink raw reply related [flat|nested] 8+ messages in thread* [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware
@ 2021-04-05 4:08 Shiju Sivasankaran
0 siblings, 0 replies; 8+ messages in thread
From: Shiju Sivasankaran @ 2021-04-05 4:08 UTC (permalink / raw)
To: meta-ti; +Cc: Praneeth Bajjuri, Shiju Sivasankaran
update am64x rtos firmware to keep pinmux and control MMRs
remain unlocked now since linux needs this to be unlock.
this fix the USB and performance degradation issues.
am64xx: 07.03.00.19
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 +++---
recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 84dae9a6..e095b7f5 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_26"
DEFAULT_RTOS_VERSION_DOT = "07.03.00.26"
-DEFAULT_RTOS_VERSION_am64xx = "07_03_00_18"
-DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.18"
+DEFAULT_RTOS_VERSION_am64xx = "07_03_00_19"
+DEFAULT_RTOS_VERSION_DOT_am64xx = "07.03.00.19"
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 = "d3fc9fbcfaf67ebd5a509e56ef30e9a54242c290baecfda15e7ff92c127738d0"
DEFAULT_FIRMWARE_SHA256SUM_j7200-evm = "674040e161cb4b87845fd527dea166a2dd25d0df9136aa6206d73a9240058c40"
DEFAULT_FIRMWARE_SHA256SUM_am65xx = "61e0be08bea8ab1055645bd96504a6a29c70318c5b277237dee9981cd94d7f79"
-DEFAULT_FIRMWARE_SHA256SUM_am64xx = "1b44bccd20b767568e996e924a2ef18cabd1c3e16d3412629ff72d83b81b152f"
+DEFAULT_FIRMWARE_SHA256SUM_am64xx = "5d1785cbdb91904a5ef3027378061041c59186c4198d7ebcfa660a1ff513d528"
# 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 c07e932d..9a1659dc 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
@@ -18,7 +18,7 @@ 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 ?= "12a455643928b9fc22af4d85f2aac7894b80e6a5"
+TI_RTOS_METADATA_SRCREV ?= "d45318854fcc9c664cb9c097afcc6ae08fa82876"
TI_RTOS_METADATA_BRANCH ?= "master"
TI_RTOS_METADATA_DIR ?= "${PLAT_SFX}"
TI_RTOS_METADATA_FILE ?= "${S}${TI_RTOS_METADATA_DIR}/metadata.inc"
--
2.17.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
end of thread, other threads:[~2021-04-05 4:09 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-03-25 6:30 [dunfell/master PATCH] ti-rtos: update metadata and version of am64x rtos firmware Shiju Sivasankaran
2021-03-25 21:34 ` praneeth
2021-03-26 3:49 ` Shiju Sivasankaran
-- strict thread matches above, loose matches on Subject: below --
2021-03-26 7:17 Shiju Sivasankaran
2021-03-29 4:11 Shiju Sivasankaran
2021-03-29 4:41 ` praneeth
2021-03-31 18:56 Shiju Sivasankaran
2021-04-05 4:08 Shiju Sivasankaran
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.