[Buildroot] [PATCH 21/21] boot/ti-k3-image-gen: remove package

[Romain Naour]

Hi Andreas,

Le 19/02/2024 à 20:42, Andreas Dannenberg a écrit :
> 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.

I'm curently working on a j721e SoC based custom board bringup involving IPC
communication with one DSP (C66x).

While it was possible to build the DSP firmware within Yocto (dunfell), it
required to package the TI-PDK to provide headers and libraries for the DSP
project. We endup by building the DSP firmware outside of Yocto (it would be the
same with Buildroot).

If the SoC is available and can run Linux, the the rootfs can be build by Buildroot.

And what about the Beagleboard-AI64 (J721e) ?

https://beagleboard.org/ai-64

> 
> 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.

Patch welcome then :)

I don't have one but it would go hand in hand with my (old) beagleboard rev C2
(omap3530)!

Best regards,
Romain


> 
> 
> --
> 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 at buildroot.org
>>>> https://lists.buildroot.org/mailman/listinfo/buildroot
>>