linux/meta-ti.git/meta-ti-bsp/conf/multiconfig, branch master

k3r5: make the separate TMPDIR optional

2023-12-13T18:22:29+00:00

With the current implemetation is not possible to remove the '-k3r5' customization using overrides like below and the '-k3r5' always stay there. | TMPDIR:remove:k3r5 = "-k3r5" | or | TMPDIR:k3r5 = "${TOPDIR}/tmp" This patch allows to build the core-image-minimal in oe-core master/nanbield without any issue on a common TMPDIR folder just using the following: | TI_COMMON_DEPLOY = "${DEPLOY_DIR}" | TI_TMPDIR_APPEND = "" Signed-off-by: Jose Quaresma Signed-off-by: Ryan Eatmon

k3r5: ensure separate TMPDIR used for this multiconfig

2023-11-22T14:57:02+00:00

This k3r5 multiconfig builds baremetal components (and corresponding native, nativesdk and cross tools) and sets TCLIBC accordingly to "baremetal". The expectation is that those components and tools will use a separate TMPDIR to isolate from the main Linux build that uses "glibc" TCLIBC and to avoid potential conflicts. OE-Core "nodistro" default configuration already sets TCLIBCAPPEND facility to automatically add a suffix to TMPDIR, resulting in "tmp-baremetal" temp directory for this multiconfig and "tmp-glibc" for the main Linux one. Other distros like Arago follow this convention and even extend a bit (e.g. Arago also adds TCMODE suffix to TMPDIR for external toolchain support separation). But Poky (and derivative distros, like AGL or YoE) disable TCLIBCAPPEND and result in a combined TMPDIR, leading to potential conflicts, such as: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15273 And that's just the beginning, there were other conflicts observed later in the build, e.g. during nativesdk builds - that's why we also set a unique SDKPKGSUFFIX here. To force a separate TMPDIR for k3r5 multiconfig, we have to directly append a suffix to it. Multiple other options were tested in hopes of making it slightly cleaner, but they either didn't work or were dismissed. For example, trying to override TCLIBCAPPEND getting cleared by a distro would require using a machine/soc-override, which doesn't have enough scope (nativesdk) or forcing it with :forcevariable would also change the main Linux TMPDIR and affect existing CI flows. Also, using TCLIBC itself as a suffix to add to TMPDIR may result in getting it appended twice (tmp-baremetal-baremetal) when normal TCLIBCAPPEND facility is used. Hence the least invasive/confusing option is to always append "-k3r5" suffix to this multiconfig TMPDIR. That results in "tmp-k3r5" in Poky (leaving main TMPDIR as "tmp"), while OE-Core "nodistro" and Arago would end up with "tmp-baremetal-k3r5" (and "tmp-glibc" for the main). Also note, meta-ti-bsp layer.conf sets up images and sdks to be deployed into a common location outside of TMPDIRs, but TI_COMMON_DEPLOY variable that controls it is set weakly, allowing to be modified from a distro configuration or local.conf. It means that all images and sdks can be deployed into the main TMPDIR if one's CI flow expects tmp/deploy/ as the final destination, by using := for immediate variable expansion: TI_COMMON_DEPLOY := "${TMPDIR}/deploy" Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: switch k3r5 multiconfig to baremetal

2023-09-25T14:58:09+00:00

There are couple of k3r5 components that need to be built for the target and they are self-contained and don't use glibc. Moreover, when building a cross-compile toolchain for k3r5, there's no need to build glibc and all its dependencies. While build-time speed up is nice, the main benefit comes when packaging a nativesdk toolchain for distribution, reducing the number of packages and the resulting size of the toolchain installer. To avoid potential namespace conflict in package feeds between nativesdk binary packages of Linux glibc and k3r5 baremetal toolchains, adjust the package suffix accordingly. This also requires a rather impactful change in the deployment structure, which affects CIs and user experience. By default different TCLIBC builds (e.g. glibc and baremetal in this case) are built in separate TMPDIRs to avoid conflicts, especially on the nativesdk side. Also the default config has DEPLOY_DIR residing under corresponding TMPDIR. Of course, this can be changed by local.conf or .conf, which meta-ti-bsp has no control over. Unlike multiconfig-image-packager example that can access deployed artifacts across multiconfigs to package in an image, we use wic and its IMAGE_BOOT_FILES list to package a final image. Unfortunately, wic cannot access deployed artifacts across multiconfigs in separate TMPDIRs, as it uses DEPLOY_DIR_IMAGE to collect the artifacts. To overcome this, we need to set up a "common" deploy directory for images and sdks produced by multiconfigs, which is located outside of TMPDIRs, set by TI_COMMON_DEPLOY variable that can be changed or adjusted by distros as needed. Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: machine: Remove all leftover config files

2023-06-07T15:08:55+00:00

Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon

conf: machine: j721s2-evm: Add support for J721S2 HS-FS

2023-03-21T18:03:29+00:00

Add the basic J721S2 HS-FS configuration. - Add configurations to support both HS-FS and GP keeping GP as default. - Add ti-sci-firmware overrides for HS-FS. - Remove evm conf file inclusion in hs-evm conf. - Add j721s2 hs-evm specific config to hs-evm conf. Signed-off-by: Aniket Limaye Signed-off-by: Sinthu Raja Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

am62xx-evm: Add AM62x HS-FS evm configuration

2023-03-21T18:03:29+00:00

Lets add the basic AM62x HS-FS configuration - Add machine conf for AM62x HS-FS. - The wic images will boot on AM62x HS-FS devices by default. - The sysfw image for GP and HS-SE will be packaged in the wic image as tiboot3-am62x-gp-evm.bin and tiboot3-am62x-hs-evm.bin respectively. - Add ti-sci-firmware overrides. Signed-off-by: Chirag Shilwant Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

machine: Add AM62Q HS-SE evm configuration

2023-03-21T18:03:29+00:00

Lets add the basic AM62Q HS-SE configuration. - Add configurations. - Add ti-sci-firmware overrides. - Add u-boot overrides. - Add optee overrides. - Add ti-rtos-firmware overrides. Signed-off-by: Chirag Shilwant Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: machine: Rework do_image_wic dependencies

2023-01-24T18:51:24+00:00

The WIC image for K3 depends on the TI-SCI firmware, on AM65x and J721e also the bootloader. Make this clear by only depending on firmware in the base k3.inc file, then adding the bootloader dependency in AM65x and J721e specific includes. Remove unneeded overrides from the evm level files. Remove do_image_tar dependencies as the tar files do not include the bootloader nor TI-SCI firmware, only the boot partition of the WIC file needs these. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: machine: am64xx-evm: Switch to SR2.0 HS-FS build by default

2022-11-23T22:08:24+00:00

AM64x devices will only be available as SR2.0 HS-FS. Set this as the default type provided by the SDK. To allow SR2.0 HS-SE to continue to boot, like we did with GP, we add an extra machine to build SR2.0 HS-SE SYSFW. To use on SR2.0 HS-SE boards simply switch out the SYSFW image: $ cd /mnt/sd-card/boot $ mv tiboot3-am64x_sr2-hs-evm.bin tiboot3.bin Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon

conf: machine: am64xx-evm: Make HS-SE the default

2022-11-23T22:08:24+00:00

The HS-SE AM64xx machine can now be run on GP devices and built without needing the TI_SECURE_DEV_PKG for the same. AM64xx will only be available in the HS-FS type going forward. Make the HS-SE the default and remove the original GP machine. Signed-off-by: Andrew Davis Signed-off-by: Ryan Eatmon Signed-off-by: Denys Dmytriyenko Signed-off-by: Ryan Eatmon