| Message ID | 20250417033514.3429633-1-c-shilwant@ti.com |
|---|---|
| State | Superseded |
| Delegated to: | Ryan Eatmon |
| Headers | show |
| Series | [meta-ti,master/scarthgap] conf: machine: am62axx: Exclude tiboot3.bin for GP | expand |
On Thu, Apr 17, 2025 at 09:05:14AM +0530, Chirag Shilwant wrote: > * The GP variant of SK-AM62A-LP is no longer tested. * Is it still being built? * Also, what about other BSPs, e.g. 6.1? * What about derivative or customer platforms, besides SK-AM62A-LP? I.e. you are modifying the entire am62axx SoC family, which is supposed to be shared by multiple platforms in the AM62A SoC family. > Hence, don't include it under IMAGE_BOOT_FILES to ensure > tiboot3-am62ax-gp-evm.bin is not packaged inside /boot > partition of wic image > > Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> > --- > meta-ti-bsp/conf/machine/include/am62axx.inc | 3 --- > 1 file changed, 3 deletions(-) > > diff --git a/meta-ti-bsp/conf/machine/include/am62axx.inc b/meta-ti-bsp/conf/machine/include/am62axx.inc > index 98cea203..e5f827a9 100644 > --- a/meta-ti-bsp/conf/machine/include/am62axx.inc > +++ b/meta-ti-bsp/conf/machine/include/am62axx.inc > @@ -10,9 +10,6 @@ TFA_K3_SYSTEM_SUSPEND = "1" > # Default tiboot3.bin on AM62A is for HS-FS > IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-fs-evm.bin" > > -# Since default tiboot3.bin on AM62A is for HS-FS, add a version for GP > -IMAGE_BOOT_FILES += "tiboot3-am62ax-gp-evm.bin" > - > # Since default tiboot3.bin on AM62A is for HS-FS, add a version for HS-SE > IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-evm.bin" > > -- > 2.34.1
On 17/04/25 23:58, Denys Dmytriyenko wrote: > On Thu, Apr 17, 2025 at 09:05:14AM +0530, Chirag Shilwant wrote: >> * The GP variant of SK-AM62A-LP is no longer tested. > * Is it still being built? > > * Also, what about other BSPs, e.g. 6.1? The GP part was built during the device bring-up (~ 2years back) Apparently GP samples are limited to TI internal. Hence, the logic to deploy tiboot3 for it was added in meta-ti-bsp at that time to support internal development. Post device APL, all TI internal development is moved to HS-FS part. (Ideally, this logic of deploying tiboot3 for GP should have been removed at that time) From customer / 3rd party SOM pov, all receive HS-FS part by default from TI. So, they shouldn't be affected if meta-ti-bsp no longer deploys |tiboot3-am62ax-gp-evm.bin| > > * What about derivative or customer platforms, besides SK-AM62A-LP? I.e. you > are modifying the entire am62axx SoC family, which is supposed to be shared > by multiple platforms in the AM62A SoC family. In meta-ti-bsp, am62axx-evm (which represents SK-AM62A-LP) is the only machine which utilizes AM62A SoC. & for customer platforms...as mentioned above, ideally they shouldn't be affected as GP parts weren't shipped to them For reference, we can checkout prebuilt-images folder of phyCORE-AM62A [0] [0] : https://download.phytec.de/Software/Linux/BSP-Yocto-AM62Ax/BSP-Yocto-Ampliphy-AM62Ax-PD24.1.2/images/ampliphy/phyboard-lyra-am62axx-2/ -- Chirag > > >> Hence, don't include it under IMAGE_BOOT_FILES to ensure >> tiboot3-am62ax-gp-evm.bin is not packaged inside /boot >> partition of wic image >> >> Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> >> --- >> meta-ti-bsp/conf/machine/include/am62axx.inc | 3 --- >> 1 file changed, 3 deletions(-) >> >> diff --git a/meta-ti-bsp/conf/machine/include/am62axx.inc b/meta-ti-bsp/conf/machine/include/am62axx.inc >> index 98cea203..e5f827a9 100644 >> --- a/meta-ti-bsp/conf/machine/include/am62axx.inc >> +++ b/meta-ti-bsp/conf/machine/include/am62axx.inc >> @@ -10,9 +10,6 @@ TFA_K3_SYSTEM_SUSPEND = "1" >> # Default tiboot3.bin on AM62A is for HS-FS >> IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-fs-evm.bin" >> >> -# Since default tiboot3.bin on AM62A is for HS-FS, add a version for GP >> -IMAGE_BOOT_FILES += "tiboot3-am62ax-gp-evm.bin" >> - >> # Since default tiboot3.bin on AM62A is for HS-FS, add a version for HS-SE >> IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-evm.bin" >> >> -- >> 2.34.1
On Mon, Apr 21, 2025 at 12:07:28PM +0530, Chirag Shilwant wrote: > > On 17/04/25 23:58, Denys Dmytriyenko wrote: > >On Thu, Apr 17, 2025 at 09:05:14AM +0530, Chirag Shilwant wrote: > >>* The GP variant of SK-AM62A-LP is no longer tested. > >* Is it still being built? > > > >* Also, what about other BSPs, e.g. 6.1? > > > The GP part was built during the device bring-up (~ 2years back) > Apparently GP samples are limited to TI internal. Hence, the logic to > deploy tiboot3 for it was added in meta-ti-bsp at that time to support > internal development. > > Post device APL, all TI internal development is moved to HS-FS part. > (Ideally, this logic of deploying tiboot3 for GP should have been > removed at that time) > > From customer / 3rd party SOM pov, all receive HS-FS part by default > from TI. > So, they shouldn't be affected if meta-ti-bsp no longer deploys > |tiboot3-am62ax-gp-evm.bin| Chirag, Thanks for clarifying. Probably should rephrase the commit message with a brief explanation. Instead of: The GP variant of SK-AM62A-LP is no longer tested. Something like: The GP variant of AM62A SoC was only used internally for initial device bring-up and is not publicly available. > >* What about derivative or customer platforms, besides SK-AM62A-LP? I.e. you > >are modifying the entire am62axx SoC family, which is supposed to be shared > >by multiple platforms in the AM62A SoC family. > > > > In meta-ti-bsp, am62axx-evm (which represents SK-AM62A-LP) is the only > machine which utilizes AM62A SoC. > > & for customer platforms...as mentioned above, ideally they > shouldn't be affected > as GP parts weren't shipped to them > > For reference, we can checkout prebuilt-images folder of phyCORE-AM62A [0] > > [0] : https://download.phytec.de/Software/Linux/BSP-Yocto-AM62Ax/BSP-Yocto-Ampliphy-AM62Ax-PD24.1.2/images/ampliphy/phyboard-lyra-am62axx-2/ > > > -- > Chirag > > > > > > > > >>Hence, don't include it under IMAGE_BOOT_FILES to ensure > >>tiboot3-am62ax-gp-evm.bin is not packaged inside /boot > >>partition of wic image > >> > >>Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> > >>--- > >> meta-ti-bsp/conf/machine/include/am62axx.inc | 3 --- > >> 1 file changed, 3 deletions(-) > >> > >>diff --git a/meta-ti-bsp/conf/machine/include/am62axx.inc b/meta-ti-bsp/conf/machine/include/am62axx.inc > >>index 98cea203..e5f827a9 100644 > >>--- a/meta-ti-bsp/conf/machine/include/am62axx.inc > >>+++ b/meta-ti-bsp/conf/machine/include/am62axx.inc > >>@@ -10,9 +10,6 @@ TFA_K3_SYSTEM_SUSPEND = "1" > >> # Default tiboot3.bin on AM62A is for HS-FS > >> IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-fs-evm.bin" > >>-# Since default tiboot3.bin on AM62A is for HS-FS, add a version for GP > >>-IMAGE_BOOT_FILES += "tiboot3-am62ax-gp-evm.bin" > >>- > >> # Since default tiboot3.bin on AM62A is for HS-FS, add a version for HS-SE > >> IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-evm.bin" > >>-- > >>2.34.1 >
diff --git a/meta-ti-bsp/conf/machine/include/am62axx.inc b/meta-ti-bsp/conf/machine/include/am62axx.inc index 98cea203..e5f827a9 100644 --- a/meta-ti-bsp/conf/machine/include/am62axx.inc +++ b/meta-ti-bsp/conf/machine/include/am62axx.inc @@ -10,9 +10,6 @@ TFA_K3_SYSTEM_SUSPEND = "1" # Default tiboot3.bin on AM62A is for HS-FS IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-fs-evm.bin" -# Since default tiboot3.bin on AM62A is for HS-FS, add a version for GP -IMAGE_BOOT_FILES += "tiboot3-am62ax-gp-evm.bin" - # Since default tiboot3.bin on AM62A is for HS-FS, add a version for HS-SE IMAGE_BOOT_FILES += "tiboot3-am62ax-hs-evm.bin"
* The GP variant of SK-AM62A-LP is no longer tested. Hence, don't include it under IMAGE_BOOT_FILES to ensure tiboot3-am62ax-gp-evm.bin is not packaged inside /boot partition of wic image Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> --- meta-ti-bsp/conf/machine/include/am62axx.inc | 3 --- 1 file changed, 3 deletions(-)