Bump the SRCREV to include the required changes to build for SGX now.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump ti-sgx-ddk-um and ti-sgx-ddk-km to the new branch for Kirkstone and
mesa independent builds. This also sets up SGX to use the latest mesa
revision rogue uses.
Changelog:
- IMG Support has officially ended. This repo will not be getting
regular updates after this unless things are really broken.
- The Mesa patches which were previously being relicensed internally
were opened and combined with the unofficial rogue efforts on
freedesktop.
- Toolchains were upgraded and multiple warnings and issues were
addressed. Hardware recoveries work now, but there are still some
longstanding issues with SGX that remain to be addressed if further
resources are set aside for that.
- We moved to an lws-generic build target to avoid rebuilding external
components. As such, these external components must be patched as
needed. Libdrm is an example of this and the required patches can be
found in meta-ti.
Known bugs:
- Buffer allocations under Weston may misbehave
- GLSL macro redefinitions will cause errors regardless of whether or
not they are identical
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Makes ti-ipc firmware as default for main-r5f0_0 firmware softlink
The ti-eth-fw binaries are tested at the SDK level and should be
made default only at that level
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The main-r5f0_0 softlinks should be pointing to the ethfw binaries
instead of the mcu-r5f0_0
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This reverts commit cd13cafd65.
Some devices need ti-fs-stub-* firmware for the uboot aarch64 build
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Revert ebcf15bf0f :
"recipes-bsp:ti-sci-fw: Add k3r5 as COMPATIBLE_MACHINE"
Extend recipe to k3 machines too, to provide ti-fs-stub-* firmware
for u-boot aarch64 build.
Update do_deploy() to allow multiconfig builds for k3 machines
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fixes the QA warnings about package contains reference to TMPDIR.
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently the do_compile step fails if we try to implement UBOOT_CONFIG
in an attempt to build U-Boot with multiple R5 defconfigs.
This commit adds a condition to handle linking the UBOOT_BINARY if
UBOOT_CONFIG is used in place of UBOOT_MACHINE.
Signed-off-by: Garrett Giordano <ggiordano@phytec.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous patch is incorrectly accepted and released. This patch
applies the logic that was discussed on the mailing list.
- Create a new variable grouping for SPL_HS_MLO
- Update the install/deploy code to reference the new variables.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The common u-boot-ti.inc file still uses the old license checksum
from 2021 U-boot. There were formatting changes in the license text
between 2021 and 2023 and version-specific recipes had the license
checksum updated to the new value. Since there are no 2021 recipes
remaining, the new license checksum can be set in the common .inc
file generically.
Note: U-boot license hasn't changed and the same checksum is simply
being moved from the recipes to the common .inc file.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Preserve the directory structure of the deployed dm firmware so that one
can directly specify the deploy directory for binman based u-boot build.
Additionally, this makes it easier to preserve the same structure inside
the prebuilt-images directory of the tisdk-core-bundle for the same reason.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Deploy the sysfw binaries to the DEPLOYDIR, to be picked up by the
tisdk-core-bundle... for the prebuilt binaries directory
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SPL binary built by u-boot for SD/MMC/eMMC media on HS platforms is
u-boot-spl_HS_MLO. Thanks to this fix, the binary is properly installed
and deployed.
Signed-off-by: Julien Panis <jpanis@baylibre.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe only provides the sysfw binaries compiled for the r5
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ti-sci-fw should be needed by the binman u-boot build only for the k3r5
machines and not for the k3 machines
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OP-TEE OS provides a handful of TAs itself. While these are often meant
to be built-in, when they are not we should deploy them as part of the
OP-TEE OS package so they can be loaded at runtime.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Only move directories which haven't already been moved.
This prevents a build error should a subsequent bitbake execution
rerun do_install where the sources to 'mv' no longer exist.
| mv: cannot stat 'ti-img-rogue-umlibs/23.1.6404501/git/targetfs/am62_linux/lws-generic/release/lib/firmware': No such file or directory
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
multi_v7_defconfig that is used for legacy platforms enables
SMP by default.
Platforms like am335x and am473x are single core platforms that
doesnt need this option to be enabled.
This config cannot go in multi_v7_defconfig as well,
since there will be systems like am57x/dra7x or other community platforms
which can have multiple arm cores.
Adding the provision to disable SMP configuration for applicable platforms like
am335x and am437x.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updates SRCREV, PV, and BRANCH for armv7a targets and fixes
failure to mount /boot when using poky with systemd. The
kernel selected supports VFAT without initramfs as noted
here - https://lists.yoctoproject.org/g/meta-ti/message/16913
Removes defconfig patch setting LZMA, as the new kernel
already defaults to LZ4.
Tested by running `bitbake core-image-base` with this patchset,
and then booting a pair of Beaglebone Black devices from the
resulting image. Prior to the change, systemd boots to a
maintenance mode having failed to mount /boot. After the change,
the system boots normally and /boot is mounted.
Suggested-by: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Anthony J. Martinez <anthony@ajmartinez.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Jacinto platforms use first R5 MCU core for DM firmware. When DM firmware was
split out into own recipe[1], ALTERNATIVE_TARGET entries got removed from
ti-rtos-firmware recipe, but corresponding ALTERNATIVE_LINK_NAME entries
remained, causing warnings. Clean up those now.
[1] https://git.yoctoproject.org/meta-ti/commit/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb?id=b21d29d94694ac49b97a1f4ba428c7d8cd6fb64a
Fixes these warnings:
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw or /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw: /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw == /usr/lib/firmware/j7-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw or /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw: /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw == /usr/lib/firmware/j7200-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Make sure shortname R5 SPL symlink is not the same as the main K3 SPL
one, as they will overlap/overwrite each other when deployed into a
common location. Latest code in master now checks for this and errors
out.
Also remove unused UBOOT_SPI_* variables.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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 <distro>.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 <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
LCPD Automation Script
Paresh Bhagat
Randolph Sapp
Ryan Eatmon
Aniket Limaye
Dan McGregor
Garrett Giordano
Denys Dmytriyenko
Kamlesh Gurudasani
Julien Panis
Andrew Davis
Max Krummenacher
Praneeth Bajjuri
Anthony J. Martinez
Hari Nagalla