Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dannenberg via buildroot <buildroot@buildroot.org>
To: Romain Naour <romain.naour@smile.fr>
Cc: Xuanhao Shi <X15000177@gmail.com>, Anand Gadiyar <gadiyar@ti.com>,
	Alexander Sverdlin <alexander.sverdlin@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 21/21] boot/ti-k3-image-gen: remove package
Date: Mon, 19 Feb 2024 13:42:07 -0600	[thread overview]
Message-ID: <20240219194207.pfonekdap7jagk3d@dasso> (raw)
In-Reply-To: <b3065644-f654-49fc-9560-31caa0beffbe@smile.fr>

Hi Romain,

On Fri, Feb 16, 2024 at 10:38:42PM +0100, Romain Naour wrote:
> Hello Andreas,
> 
> Le 16/02/2024 à 21:06, Andreas Dannenberg a écrit :
> > On Thu, Feb 15, 2024 at 11:20:50AM +0100, Alexander Sverdlin wrote:
> >> Hi Romain,
> >>
> >> On Tue, 2024-02-13 at 18:28 +0100, Romain Naour wrote:
> >>> -choice
> >>> -	prompt "Security type"
> >>> -	help
> >>> -	  The target SoC security type option for image gen.  Valid
> >>> -	  options are "gp" for General Purpose devices, "hs-fs" for
> >>> -	  High Security - Field Securable devices, or "hs" for High
> >>> -	  Security - Security Enforcing devices.  Note for all High
> >>> -	  Security device variants the TI_SECURE_DEV_PKG environmental
> >>> -	  variable must be defined at build time pointing to a valid
> >>> -	  core-secdev-k3 folder location, otherwise the build will
> >>> -	  fail, see
> >>> -	  https://git.ti.com/cgit/security-development-tools/core-secdev-k3
> >>> -
> >>> -config BR2_TARGET_TI_K3_IMAGE_GEN_SECTYPE_GP
> >>> -	bool "gp"
> >>> -
> >>> -config BR2_TARGET_TI_K3_IMAGE_GEN_SECTYPE_HS_FS
> >>> -	bool "hs-fs"
> >>> -
> >>> -config BR2_TARGET_TI_K3_IMAGE_GEN_SECTYPE_HS
> >>> -	bool "hs"
> >>> -
> >>> -endchoice
> >>
> >> another observation I made just now: previously BR2_TARGET_TI_K3_IMAGE_GEN_SECTYPE_GP=y
> >> was the default, which didn't boot on my HS-FS SoC.
> >>
> >> You patchset started out-of-the-box, which, I conclude, means, HS-FS is now the
> >> default for AM62x. I'm not sure if this is a problem, though.
> > 
> > HS-FS should be the default for all TI AM6x devices. This is our
> > "production silicon" and what's used for (almost) all projects,
> > especially new projects. This being said having support for GP device
> > variants still is desirable for existing boards/projects, such as the
> > current BeaglePlay boards (amongst earlier version of TI starter kit
> > EVMs for AM6x).
> 
> Thank you, I was not aware of this.
> 
> I found your post in the TI forum about the recent switch from GP to HS-FS
> device in Yocto [1].
> 
> Currently existing am64/am62 defconfigs are still targeting GP devices but we
> should add additional commits to do the switch to HS-FS.
> 
> What about other SoC of the K3 architecture?
> Is the DRA829/J721e device will also switch to HS-FS by default?

I needed to double-check with the team, since I'm only intimately
involved with AM62/AM64/AM65 type devices. All the others are managed by
a different group in TI.

So based on what I found out here's the full context accross TI's K3
platform of devices and their associated TI EVMs / Starter Kits:

* All "Sitara"-brand SoCs (AM62x, AM64, AM65x) are HS-FS first
* All "Jacinto"-brand industrial SoCs (AM68, AM69 and AM67) are also HS-FS first
* All new "Jacinto"-brand automotive/other SoCs (J7AEN onwards) are HS-FS first
* All existing "Jacinto"-brand SoCs (TDA4, J721E, J7200, J721S2 and J784S4) are GP by default

So while there are still boards out there with GP silicon (last bullet)
those are probably not the typical target platforms for Buildroot, being
very complex and high-end multi-core SoCs, mostly used in automotive
applications. The one exception here that has more weight in my oppinion
is the current BeaglePlay board (AM62x-based), those also have GP devices
on those boards.

All this being being said, I stand by my previous comment that HS-FS
should be the default. As for the BeaglePlay board (which is a very nice
community board) and potentially selected Jacinto-based boards this
could potentially be handled with a dedicated defconfig or some other
Kconfig magic to enable a seamless and easy out of box experience.


--
Andreas Dannenberg
Texas Instruments Inc







> 
> From the u-boot k3 documentation, it's not clear witch device type is used by
> default across all k3 SoC. By default I was expecting the GP type for all the k3
> family (I was wrong).
> 
> [1]
> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1210443/faq-am625-generating-sitara-am62x-am62ax-am64x-gp-device-bootable-mmc-sd-card-images-using-sdk-v8-6-and-yocto
> 
> [2]
> https://source.denx.de/u-boot/u-boot/-/blob/master/doc/board/ti/k3.rst?ref_type=heads&plain=1#L108
> 
> Best regards,
> Romain
> 
> > 
> > --
> > Andreas Dannenberg
> > Texas Instruments Inc
> > 
> > 
> >>
> >> -- 
> >> Alexander Sverdlin.
> >>
> >> _______________________________________________
> >> buildroot mailing list
> >> buildroot@buildroot.org
> >> https://lists.buildroot.org/mailman/listinfo/buildroot
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-19 19:42 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 17:27 [Buildroot] [PATCH 00/21] Add ti_j721e_sk_defconfig Romain Naour
2024-02-13 17:27 ` [Buildroot] [PATCH 01/21] DEVELOPERS: add Romain Naour for am574x_idk_defconfig Romain Naour
2024-02-13 17:27 ` [Buildroot] [PATCH 02/21] configs/ti_am62x_sk_defconfig: fix optee-os plateform Romain Naour
2024-02-13 18:45   ` Alexander Sverdlin
2024-02-13 17:27 ` [Buildroot] [PATCH 03/21] configs/ti_am64x_sk_defconfig: " Romain Naour
2024-02-13 18:56   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 04/21] package/python-attrs: add host variant Romain Naour
2024-02-13 17:28 ` [Buildroot] [PATCH 05/21] package/python-rpds-py: " Romain Naour
2024-02-13 17:28 ` [Buildroot] [PATCH 06/21] package/python-referencing: " Romain Naour
2024-02-13 17:28 ` [Buildroot] [PATCH 07/21] package/python-jsonschema-specifications: " Romain Naour
2024-02-13 17:28 ` [Buildroot] [PATCH 08/21] package/python-jsonschema: " Romain Naour
2024-02-13 17:28 ` [Buildroot] [PATCH 09/21] boot/uboot: add BR2_TARGET_UBOOT_USE_BINMAN option Romain Naour
2024-02-14 10:58   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 10/21] boot/ti-k3-r5-loader: add BR2_TARGET_TI_K3_R5_LOADER_USE_BINMAN option Romain Naour
2024-02-14 10:58   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 11/21] boot/ti-k3-r5-loader: install tiboot3.bin and sysfw.itb to BINARIES_DIR Romain Naour
2024-02-14 10:58   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 12/21] boot/ti-k3-boot-firmware: introduce BR2_TARGET_TI_K3_BOOT_FIRMWARE_SOC_{AM62AX, AM62X, AM64X, AM65X} Romain Naour
2024-02-14 11:20   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 13/21] boot/uboot: use DM firmware name defined by ti-k3-boot-firmware package Romain Naour
2024-02-14 11:29   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 14/21] boot/ti-k3-boot-firmware: add BR2_TARGET_TI_K3_BOOT_FIRMWARE_SOC_J721E Romain Naour
2024-02-13 20:23   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 15/21] boot/uboot: replace ti-k3-image-gen options by ti-k3-firmware options Romain Naour
2024-02-14 11:37   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 16/21] boot/uboot: enable TI K3 Device Manager (DM) for j721e Romain Naour
2024-02-14 10:58   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 17/21] boot/ti-k3-boot-firmware: bump to version 09.02.00.004 Romain Naour
2024-02-14 11:25   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 18/21] configs/ti_j721e_sk_defconfig: new defconfig Romain Naour
2024-02-14 12:06   ` Alexander Sverdlin
2024-02-16  1:19   ` Alexander Sverdlin
2024-02-16  1:44   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 19/21] configs/ti_am62x_sk_defconfig: update to uboot 2024.01 to use binman tool Romain Naour
2024-02-14 10:59   ` Alexander Sverdlin
2024-02-14 15:24     ` Romain Naour
2024-02-13 17:28 ` [Buildroot] [PATCH 20/21] configs/ti_am64x_sk_defconfig: " Romain Naour
2024-02-14 11:05   ` Alexander Sverdlin
2024-02-13 17:28 ` [Buildroot] [PATCH 21/21] boot/ti-k3-image-gen: remove package Romain Naour
2024-02-13 19:05   ` Alexander Sverdlin
2024-02-13 21:35     ` Romain Naour
2024-02-14 10:58   ` Alexander Sverdlin
2024-02-15 10:20   ` Alexander Sverdlin
2024-02-15 11:26     ` Romain Naour
2024-02-15 18:50       ` Alexander Sverdlin
2024-02-15 22:32         ` Romain Naour
2024-02-15 22:36           ` Alexander Sverdlin
2024-02-16 20:06     ` Andreas Dannenberg via buildroot
2024-02-16 21:38       ` Romain Naour
2024-02-19 19:42         ` Andreas Dannenberg via buildroot [this message]
2024-02-19 22:27           ` Romain Naour
2024-02-15 10:13 ` [Buildroot] [PATCH 00/21] Add ti_j721e_sk_defconfig Alexander Sverdlin
2024-02-15 11:23   ` Romain Naour
2024-02-15 21:14     ` Alexander Sverdlin
2024-02-15 22:13       ` Romain Naour
2024-02-15 22:22         ` Alexander Sverdlin
2024-02-16 20:13     ` Andreas Dannenberg via buildroot
2024-02-16 21:17       ` Romain Naour
2024-02-16 20:19 ` Andreas Dannenberg via buildroot
2024-02-16 21:52   ` Romain Naour
2024-02-16 22:20     ` Andreas Dannenberg via buildroot
2024-02-17  3:13       ` Alexander Sverdlin
2024-02-19 19:59         ` Andreas Dannenberg via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240219194207.pfonekdap7jagk3d@dasso \
    --to=buildroot@buildroot.org \
    --cc=X15000177@gmail.com \
    --cc=alexander.sverdlin@gmail.com \
    --cc=dannenberg@ti.com \
    --cc=gadiyar@ti.com \
    --cc=romain.naour@smile.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox