For AM62L there is no GP and both HS sub-types are supported by the
same TIFS. This means we do not need multiple versions of tiboot3.bin.
So no need to deploy an additional version which is identical to the
default tiboot3.bin already deployed.
Signed-off-by: Andrew Davis <afd@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add configuration files for the new PocketBeagle2 platform.
U-boot support for this platform is still in its own branch.
Adjust U-boot bootcmd, since EFI boot doesn't seem to work.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upgrade BeagleY-AI platform to 6.12 BSP.
U-boot support for this platform is still in its own branch.
Also adjust U-boot bootcmd, as Distro Boot doesn't fully work yet.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
TI is starting to run an automated checker for all incoming patches to
the mailing list. One of the checks is to scan all of the files in the
repository looking for things that we have flagged as the "right way" of
doing recipes. This file contains a set of exceptions that the checking
script is finding but can be skipped due to manual review.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Usually :append is used to add items to a space separated list. In
those cases the first character of the appended string should be a
space to make sure that the append is correct.
In this case, the space was embedded in the string and not right after
the ". Simple fix is to move the space to the front to be consistent.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Every recipe should have a SUMMARY and that can only be 72 characters at
most. Some of these recipes had DESCRIPTIONS and not SUMMARY, some were
missing the SUMMARY, and some had slightly too long values for the SUMMARY.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The AM62D SoC is a high-performance Digital Signal Processing (DSP)
device with a quad-core Cortex-A53 cluster, dual Cortex-R5F cores, and
a Cx7 DSP core with Matrix Multiplication Accelerator (MMA). It features
a range of peripherals, including multichannel audio serial ports,
Ethernet, UARTs, SPI, I2C, USB, and more.
This SoC is part of K3-AM62x family, which includes the AM62A and AM62P
variants. While the AM62A and AM62D are largely similar, the AM62D is
specifically targeted for general-purpose DSP applications, whereas the
AM62A focuses on edge AI workloads. A key distinction is that the AM62D
does not include multimedia components such as the video encoder/decoder,
MJPEG encoder, Vision Processing Accelerator (VPAC) for image signal
processing, or the display subsystem. Additionally, the AM62D has a
different pin configuration compared to the AM62A, which impacts embedded
software development.
The EVM board is a low-cost, expandable platform designed for the AM62D2
SoC, having 4GB LPDDR4 RAM, Gigabit Ethernet expansion connectors, audio
jacks, USB ports, and more.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This OP-TEE fTPM is a TA from Microsoft containing the reference
implementation of the TPM 2.0 Specification. As K3 OP-TEE now has the
necessary features supported to run this fTPM, enable it here. This will
serve as an example of using OP-TEE on K3 as a TPM without needing an
external harware TPM.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This is an old code base and hasn't been updated in a very long
time. It now fails to compile with gcc-15 (C23 standard). Force
compilation with GNU/C11 standard instead.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This is an old code base and hasn't been updated in a very long
time. It now fails to compile with gcc-15 (C23 standard). Force
compilation with GNU/C11 standard instead.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* For AM62P display cluster usecase, we need to pick
"dss_display_share.wkup-r5f0_0.release.strip.out" from ti-linux-firmware [0]
Hence, pick the display cluster firmware only when DISPLAY_CLUSTER_ENABLE is set to 1.
* When DISPLAY_CLUSTER_ENABLE is not set to 1, fallback to pick the "ipc_echo_testb_mcu1_0_release_strip.xer5f"
DM firmware.
[0]: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/tree/ti-dm/am62pxx?h=11.00.12
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Firmware, like kernel modules, may be only relevant to a small subset of
hardware. Shipping all firmware for all hardware can waste space. For
this reason modules are split out into packages, and the same should
be done for firmware.
What we do currently is change the content of the package itself based
on what device we are building for. Having a package change content for
each machine means we cannot generate one image that supports multiple
machines, nor host a common machine agnostic package repo.
Instead we can generate different packages for the different firmwares
and only include the firmware packages needed for each machine.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Firmware here are not built, no need for C compiler nor std libs.
Add INHIBIT_DEFAULT_DEPS=1 and remove the same from all recipes
that include this file.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These other machines are not compatible with this recipe, no need to
setup definitions for these.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since OE bitbake commit 24772dd2ae6c ("parse/ConfHandler: Add warning for
deprecated whitespace usage"), the current build generates the following
warning (as example):
| WARNING: ...meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb:
| meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb:2
| has a lack of whitespace around the assignment:
| 'HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC"'
Fix all the warnings.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since OE bitbake commit 24772dd2ae6c ("parse/ConfHandler: Add warning for
deprecated whitespace usage"), the current build generates the following
warning (as example):
| WARNING: ...meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb:
| meta-ti/meta-ti-bsp/recipes-ti/ipc/ti-ipc_git.bb:2
| has a lack of whitespace around the assignment:
| 'HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC"'
Fix all the warnings.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In falcon mode, ATF jumps straight to the linux kernel which requires a
2MiB aligned load address. Hence this patch changes the ATF jump address
(PRELOADED_BL33_BASE) to a 2MiB aligned value 0x82000000 and the DTB
address (K3_HW_CONFIG_BASE) to 0x88000000.
These values are chosen to be consistent with the addresses used by
u-boot when booting in the normal flow.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Falcon boot requires tispl_falcon.bin to be on the same filesystem
partition as the fitImage.
This patch creates a new u-boot package called
'u-boot-ti-staging-falcon' that is included in IMAGE_INSTALL when
ti-falcon is enabled which allows us to deploy the required files to
rootfs.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ti-falcon.inc configures the following things for enabling falcon boot:
1. Change fitImage class to kernel-fitimage-legacyhs
2. Update kernel and dtb address for falcon boot
3. Disable kernel compression
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The am62x_r5_falcon.config fragment in u-boot enables falcon boot
support for R5 SPL, this patch enables the config fragment for am62a,
62p, 62x and 62lp evms based on ti-falcon distro override.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
All other firmware recipes are in recipes-bsp. There is nothing much
special about this set of firmware so move it to match.
This firmware is the pre-compiled "echo test" example for various
remote cores. The directory name is not very clear on that, so fix
that up too.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* The GP variant of AM62A SoC was only used internally
for initial device bring-up and is not publicly available.
Hence, drop it from IMAGE_BOOT_FILES to ensure
tiboot3-am62ax-gp-evm.bin is not packaged inside vfat boot
partition of wic image
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New features added under meta-tisdk [0] require another
increase to max_leb_cnt.
[0]: 3985a7caea
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* U-Boot reads the bootsplash image file from the vfat boot partition
& displays it during boot-up showcasing early splash screen support.
* There's no significance of having an additional do_install
as the logo file need not be added in the rootfs/image.
* Fixes 277f04df4c & 1fed958bfe
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
FIT_CONF_DEFAULT_DTB config specifies the default dtb file for the
FITimage when multiple ones are provided[1].
Legacyhs fitimage does not currently support this feature set which is
required for repurposing the same class for falcon boot.
This patch adds support for FIT_CONF_DEFAULT_DTB without affecting
existing platforms that rely on legacyhs fitImage.
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-FIT_CONF_DEFAULT_DTB
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe to deploy the HSM demo firmware to the DEPLOYDIR, to be
picked up by the tisdk-core-bundle for the prebuilt binaries directory.
This firmware is then further picked by U-Boot and packaged inside
tispl.bin FIT image for loading the HSM M4 core in applicable SoCs.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* New features added under meta-tisdk [0] require another
increase to max_leb_cnt.
* This patch fixes following errors observed with 11.00.09.04
tag on meta-tisdk,
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch adds prefix string for eqep overlay to
KERNEL_DEVICETREE_PREFIX.
Signed-off-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the srcrev to include a fix for events where the driver is
requested to show advanced information about file descriptors that are
associated with the device but are not currently associated with a
rendering task.
This should address the kernel fault in pvr_show_fdinfo associated with
fdinfo/lsof.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fix the package config params to make it obvious what combinations are
allowed. Also, rework the way we are inheriting init related classes so
that we don't accidentally do any additional postinstall steps. While
we're at it, don't execute anything for the compile or configure stage.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
FIT_CONF_DEFAULT_DTB config specifies the default dtb file for the FIT
image when multiple ones are provided[1].
Since the variable is not set in current machine configs, the default is
set to the first dtb read during FIT image creation which doesn't give
us direct control over the default configuration.
Therefore this patch adds default dtbs for am62 evms.
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-FIT_CONF_DEFAULT_DTB
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
To facilitate better testing we need to control all aspects of the
SRC_URI. Create TI_LINUX_FW_GIT_URI, TI_LINUX_FW_GIT_PROTOCOL, and
TI_LINUX_FW_GIT_BRANCH and build SRC_URI using them.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The user mode libraries needed recompiling with the scarthgap revision of gcc to
remove all the warnings about 32bit API usage during the linking stage, new
SRCREV includes this changes. Versions of the libraries remain the same.
Signed-off-by: Antonios Christidis <a-christidis@ti>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
MACHINE_FEATURE gc320, already gets set on omap-a15.inc. But ti-bsp.inc file,
removes the feature. So, remove that portion of functionality from ti-bsp, in
order to allow the building of gc320 in kernel 6.12.
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Changes made on the gc320 kernel mode driver in order to work with kernel
6.12. There is no other change in functionality with this update, and the
driver version remains the same.
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include a patch that changes the way
compiler_preferred_target is selected for a given toolchain. This now
checks specified SYS_CFLAGS to see if hardfloat is set explicitly and
will override the default target selection if necessary.
Signed-off-by: Randolph Sapp <rs@ti.com>
Tested-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The meta-arm layer, which is the provider of the base recipe for
optee-os, added [1] a separate optee-os-ta package for the embedded TAs
that are compiled as part of the OPTEE OS build process. However, the
TI overrides for optee-os include the embedded TAs inside the base
package, leaving the optee-os-ta package empty (and thus not
installable).
Align to the meta-arm behaviour and simply add a runtime dependency on
optee-os-ta for optee-os. While keeping backward compatibility, this
allows to install only the embedded TAs - reducing the required disk
space - on platforms on which the OPTEE OS is loaded from an external
boot image rather than being fetched from the root filesystem, like the
K3 SoCs.
[1] https://patchwork.yoctoproject.org/project/arm/patch/20230630112340.3314395-1-r.czerwinski@pengutronix.de/
Signed-off-by: Francesco Valla <francesco@valla.it>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Correct SRCREV for jailhouse which currently points to an unpublished
commit hash.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Out-of-tree module failing to build against linux-next as a result of
changes to platform driver remove function.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fix OS APM interactions when uninitialized. Because this driver uses
lazy initialization, if the GPU is never given a task it will not be
initialized. Even if the device is not fully initialized it is still
registered with the DRM subsystem and capable of receiving OS APM
signals.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Well, this is the evil vendor driver. Time to start acting like it.
Blacklist the upstream powervr module if this driver is present.
This patch also does away with the bin_package components. It was cool
and found some interesting bugs, but we might as well start leveraging
that Makefile more now that we're starting to get some more common
files between devices.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Module recipe is missing SUMMARY and a proper SRC_URI leading to
warnings during the build process.
Fixes: 296344c8 ("ti-bsp: ti-img-encode-decode: Add Recipe for Building VXE-VXD Out-of-Tree Module")
Reported-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new out of tree module ti-vxe-vxd-driver is only for the 6.12 kernel
and later. Since we support multiple BSPs we need to correctly wrap
this addition behind some additional logic that can make sure to not
include it for the 6.1 and 6.6 kernel builds where the module is still
in the tree.
Additionally, fix up the beaglebone-ai64 since it includes the j721e.inc
file and will need to clear this variable for its BSPs as well.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rather than using COMPATIBLE_HOST move to using COMPATIBLE_MACHINE to
limit the recipe to being TI specific. Also, this package is "k3"
specific so further limit it down to just those matching machines and
not all TI SOCs.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous commit incorrectly added the k3-j721s2-evm-ub954.dtbo to
the KERNEL_DEVICETREE and it was missed during a quick review.
The correct way to add dtbs is to add a prefix string to the
KERNEL_DEVICETREE_PREFIX variable so that all files that match the
string will be picked up. This allows for multiple kernels to be
swapped out that may have different DTBs in their respective trees and
not break a build.
The upstream testing on the kernel will automatically update the
KERNEL_DEVICETREE variable when the final kernel version is available.
That way the KERNEL_DEVICETREE always points to what is available in the
mainline.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous commit incorrectly added the k3-j721e-evm-ub954.dtbo to
the KERNEL_DEVICETREE and it was missed during a quick review.
The correct way to add dtbs is to add a prefix string to the
KERNEL_DEVICETREE_PREFIX variable so that all files that match the
string will be picked up. This allows for multiple kernels to be
swapped out that may have different DTBs in their respective trees and
not break a build.
The upstream testing on the kernel will automatically update the
KERNEL_DEVICETREE variable when the final kernel version is available.
That way the KERNEL_DEVICETREE always points to what is available in the
mainline.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
IMG codec drivers reside only on the J721e SoC. Ensure that the drivers
are being built when building SDK.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
During 10.0 LTS bringup, the decision was made that it would be the last LTS
that carried the IMG VXE and VXD driver in tree. Driver is now hosted on
git.ti.com. This recipe is responsible for pulling in the driver,
building it, and packaging it within the J721e SDK.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
All K3 SoCs utilize the binman packaging tools in U-Boot to package
and sign the different boot firmware components needed to boot the
various security variants of K3 platform. Disable UBOOT_SIGN_ENABLE
to simplify the build
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
DS90UB954-Q1EVM can be used to connect FPDLink-III based sensors to
TI EVMs. So pick the DS90UB954-Q1EVM overlay.
Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
DS90UB954-Q1EVM can be used to connect FPDLink-III based sensors to
TI EVMs. So pick the DS90UB954-Q1EVM overlay.
Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OPTEE support for the am62lxx is still in progress.
Therefore, temporarily set TFA_SPD to empty to avoid
using any SPD (Secure Payload Dispatcher) services.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The original .bbappend started with just a few customizations behind
a :k3 SoC override, but eventually grew in size. It got converted into
a .inc file, which is behind the same SoC override and hence it gets
included by .bbappend only for K3 platforms:
https://git.yoctoproject.org/meta-ti/commit/?id=389f9a8b726868768a8bed6cbe0b2a1f18c05410
It doesn't make sense to use the same :k3 override inside this .inc
file for every variable. Moreover, it makes it harder to change
those variables downstream for any derivative platform or even for
upstream testing.
This change drops redundant :k3 SoC overrides, w/o changing existing
behavior. It allows easier modifications of such customizations from
downstream layers or a local.conf, e.g. SRC_URI_TRUSTED_FIRMWARE_A
Note that SRC_URI is set exactly the same as in upstream base .inc
file, but version-specific recipes in meta-arm tend to add extra
patches directly to SRC_URI, which is undesirable here. Thus, reset
SRC_URI back to its default.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add am62lxx as compatible machine for ti-extras recipes and jailhouse
recipes. This is to to control the kernel and u-boot repos, branches.
So the am62lxx jailhouse build can be done by adding TI_EXTRAS=tie-jailhouse
in local.conf.
Update SRCREV and branch in ti-extras recipes for LTS migration.
Also update jailhouse recipe to build and package jailhouse, cell files,
device tree for inmate etc on am62lx image.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the bb_org-6.6 bsp provider to pick the correct version of
mesa-pvr. This probably should have be a part of the previous patch
switching ti bsp logic as well.
Fixes: 0be0a5f6 (ti-bsp: select the graphics 24.2 packages, 2025-01-22)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the source revision to allow this module to work on kernel 6.12.
Originally this was going to be a separate branch, but considering the
bsp selector logic, this makes just as much sense.
Also enable the sgx driver in the ti_6.12 bsp selector.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Relocate the patches for 22.3.5 to the mesa-pvr-22.3.5 subdirectory so
it's more clear what version of mesa they apply to.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
No reason to do this pre install now that my python function can
evaluate file paths. Also, this may have been causing issues with state
when attempting to switch between opencl enabled/disabled builds.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since this is new logic is in place, switch the k6.6 and k6.12 configs
to use these new libraries. Do not enable GFX on 6.12 just yet. Still
need some kernel patches on the SGX side.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The gfx library provided by rogue can support this never version of mesa
out of the box. Pull it in now that we have ported the SGX side of
things.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the package version for DDK 24.2, this includes a few fixups from
IMG and support for a newer version of mesa.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently, the overlay mentioned in KERNEL_DEVICETREE_PREFIX in case
of j722s is "k3-j7200-evm-mcspi-loopback" which is incorrect. Change
the overlay to "k3-am625-sk-mcspi-loopback.dtso" in order to carry
out SPI loopback tests successfully.
Fixes: 13b691a9bc ("conf: machine: j722s: Add overlay to
KERNEL_DEVICETREE_PREFIX")
Signed-off-by: Anurag Dutta <a-dutta@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We have a need for some platforms to add kernel options to the bootloader
during wic creation time. Create a new variable and add that to the
sdimage-2part-efi.wks.in file so that a machine can override it if
needed.
Add an override for am64 to point the kernel at console=ttyS2.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add logic to generate UBI filesystem images which can be used to directly
flash into the NAND’s file-system partition.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump up SRCREV of optee-os to ef1ebdc23034a804a72da2207f1a825ce96a1464
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the overlay "k3-j7200-evm-mcspi-loopback.dtso" to the j722s
configuration so that SPI loopback tests can be carried out
successfully.
Signed-off-by: Anurag Dutta <a-dutta@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ti-linux-kernel tree has several prune config fragments for ARM/ARM64/RT
configurations. Enable the prune config fragments here.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Acked-by: Andrew Davis <afd@ti.com>
All current K3 devices use either A53 or A72. Use the compile tune
configuration specific for these to allow the compiler to make
better optimizations.
Default tune here is weakly set to a lowest common denominator of
aarch64, as before, which is a recommended behavior for a BSP layer.
This allows for greater binary reuse (packages, sstate, etc.) across
different platforms of the same architecture in multi-BSP environments.
At the same time, since all the correct tunes are now configured for
K3 devices, one can elevate compiler optimization levels either from
local.conf or own Distro configuration on a per-SoC or per-device
basis, like so:
DEFAULTTUNE:k3 = "armv8a-crc"
DEFAULTTUNE:j721e = "cortexa72-cortexa53"
DEFAULTTUNE:beagleplay = "cortexa72-cortexa53"
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Rather than override the value for SPL_BINARY for all bsps, simply just
set the value to the correct value. This should be ok since all
beaglebone-ai64 variations should use tispl.bin_unsigned.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The defaults for UBOOT_MACHINE and SPL_BINARY are now aligned with the
mainline values and new ti-6_1 values for the previous defaults were
created to capture those. Also updated the meta-beagle beagleplay since
it inherits the beagleplay-ti settings.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt-arm compiler is a custom TI compiler. It does not
currently support reproducible builds and is provided via a
binary blob download that we cannot patch in the recipe to
address the issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update SRCREV to pick up patch that fixes some compile errors:
../git/memplugin_linux.c: In function 'memplugin_alloc':
../git/memplugin_linux.c:69:9: error: implicit declaration of function 'dsp_dce_buf_lock' [-Wimplicit-function-declaration]
69 | dsp_dce_buf_lock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~~~
../git/memplugin_linux.c:71:9: error: implicit declaration of function 'dce_buf_lock' [-Wimplicit-function-declaration]
71 | dce_buf_lock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~
../git/memplugin_linux.c: In function 'memplugin_free':
../git/memplugin_linux.c:91:17: error: implicit declaration of function 'dsp_dce_buf_unlock' [-Wimplicit-function-declaration]
91 | dsp_dce_buf_unlock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~~~~~
../git/memplugin_linux.c:93:17: error: implicit declaration of function 'dce_buf_unlock' [-Wimplicit-function-declaration]
93 | dce_buf_unlock(1, &(h->dma_buf_fd));
| ^~~~~~~~~~~~~~
../git/memplugin_linux.c:95:13: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration]
95 | close(h->dma_buf_fd);
| ^~~~~
| pclose
and
../git/libdce_linux.c: In function 'dce_deinit':
../git/libdce_linux.c:90:9: error: implicit declaration of function 'close'; did you mean 'pclose'? [-Wimplicit-function-declaration]
90 | close(OmapDrm_FD);
| ^~~~~
| pclose
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There were some errors related to ipk postinst. The issues were fixed
by going to the update-alternatives class instead of trying to create
the steps directly in the recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The script that sends the automated patch does not currently handle
updating the KERNEL_REPRODUCIBILITY_PATCHES variable with the changes in
the patches.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Like we do with GPU support, GC320 support is conditional on the
kernel we are building and so should be disabled here for kernels
on which it is not functional yet.
We can then remove these disabling lines as the driver is updated
for each supported kernel, instead of blanket disabling in the
distro layer as done currently.
Signed-off-by: Andrew Davis <afd@ti.com>
This might have been useful for building development packages with
the pre-built binaries for deployment elsewhere, but there are
better ways to do this and these are no longer consumed. Remove
this packaging step.
Signed-off-by: Andrew Davis <afd@ti.com>
This might have been useful for building development packages with
the pre-built binaries for deployment elsewhere, but there are
better ways to do this and these are no longer consumed. Remove
this packaging step.
Signed-off-by: Andrew Davis <afd@ti.com>
This was used when the kernel had a different configuration for
the testing kernel. This has not been the case since v5.10 so
drop the systest kernel package as it will be the same as the
normal kernel package now.
Signed-off-by: Andrew Davis <afd@ti.com>
We are moving to 6.12 to be our new LTS, so we are switching the default
BSP to that. You can still access the 6.6 kernel if you need to by using
the BSP system and setting TI_PREFERRED_BSP = "ti-6_6" in your
local.conf.
Current known issues:
- Hardware graphics is disabled until we get a patch that updates the
patches to work with the 6.12 kernel. Falling back to software
rendering.
- am62xxsip-evm and j742s2-evm are not supported in the 2025.01 u-boot
yet. They will fail to build until the u-boot recipe is updated to
point to a commit that fixes their support.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There was a fix for "buildpaths" QA error in master that got backported
to scarthgap, but out of 2 references to the new UNPACKDIR, one got
corrected, but the other one was left behind. Since scarthgap has no
notion of UNPACKDIR, replace it with corresponding WORKDIR.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Rogue graphics driver 24.1 currently fails to build against the kernel
that enables FORTIFY_SOURCE, such as bb.org. Disable this config for now,
until the driver is fixed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Most Beagle platforms are switching to 6.6 based Linux kernel and U-boot
2024.10. Add corresponding recipes and extend beagle-bsp with required
settings.
BeagleY-AI for now remains on 6.1 BSP with U-boot 2023.04.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Rename "bb_org" BSP recipes to include version in the recipe names.
This way we can support multiple versions.
Also remove 2 unused kernel patches that were needed for 5.10
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Move "bb_org" kernel and U-boot providers that use corresponding official
BeagleBoard.org trees into own meta-beagle layer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Extract "bb_org" BSP specific settings from beagleplay-ti in meta-ti-bsp and
move them to own beagleplay machine config in meta-beagle.
The differences between 2 configs are minimal, hence beagleplay in meta-beagle
inherits beagleplay-ti from meta-ti-bsp as a base and only adjusts what's
needed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
OE-Core master has switched from lz4c to lz4 host tool, but a corresponding
change only appears in kernel 6.13. Since bb.org kernels 6.1 and 6.6 enable
LZ4 compression by default, also add a legacy lz4c tool in the list.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
The new meta-beagle will host all supported Beagle platforms that
use TI SoCs and hence need to depend on meta-ti-bsp. The default
BSP for the platforms in this layer will use BeagleBoard.org
official trees for the Linux kernel and U-boot.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
BeaglePlay is officially supported by TI "ti-6_6" BSP and is part
of the TI-SDK releases. Switching BSP to BeagleBoard.org "bb_org"
settings for the same machine is possible within the same layer.
But having different machine configs for the same machine name in
multiple layers can be confusing and prone to errors. Hence rename
the config to indicate BeaglePlay with official TI support in order
to re-use the canonical name in a separate layer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Early Boot of remote processors is supported at the SPL stage of the
bootloader. Currently, SPL looks for the remoteproc firmwares in the
boot partition.
Therefore, add the rproc firmware to the boot partition of wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Early boot of remote processors from SPL stage of bootloader requires
the remoteproc firmware to be present in the boot partition. Deploy this
rproc IPC firmware so that it can be copied to the boot partitions of
the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
This package provides Linux-side components for TI IPC and depends on
virtual/kernel Linux kernel for the build, so it is not compatible with
non-Linux builds, such as k3r5 baremetal multiconfig. Hence adjust
COMPATIBLE_HOST accordingly.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Add a SECURITY file with hints for security researchers and other
parties who might report potential security vulnerabilities.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
This IPC example is no longer supported nor recommended for new designs.
The documentation is no not available either (was on Processors Wiki).
Remove this example.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel
6.6 and the same version of mesa rogue is using.
Enable SGX by default in the 6.6 BSP provider section logic.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to commit 58b25570c9ef91753b14c2103f45f4be9dddb696, which adds
the DM_MANAGED suspend feature.
58b25570c9
Also change the docs/license.rst checksum. The license file was
modified to include a reference to the pydevicetree project which uses
the Apache License 2.0.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The mesa.inc that we inherit from oe-core now has the required
parameters. This conditional append is no longer required.
This reverts commit dbc6afc46e.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
PREFERRED_VERSION matches against the PV in the recipe, not against the
file name. With the upcoming 6.12, the 6.1 kernel version string was a
little too loose. The "6.1%" could glob onto the 6.12 recipe. Take
this time to also clean up a couple of the other versions and narrow
them down.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add bsp-ti-6_12 overrides in A53 & R5 machine configuration
to ensure it picks the appropriate u-boot configs for beagleplay
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are planning on adding upstream u-boot testing against stable tagged
versions of u-boot and need a little more control over telling bitbake to
not point at a branch but point to a tag.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest u-boot release v2024.10.
Additionally, take this time to clean up the mainline recipe and
streamline it a bit.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Our upstream testing needs to point to both master and master-next and
we need two different recipes to track that. This recipe mirrors the
linux-ti-next recipe and points to the master-next branch for the latest
bleeding edge changes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It was suggested to move the reproducibility patches out of
ti-kernel.inc and into the respective recipes.
Taking this time to also rework all of the pieces that go into the SRC_URI
and create a standardization for how all of the kernel recipes are done.
Create KERNEL_GIT_URI, KERNEL_GIT_PROTOCOL, KERNEL_GIT_BRANCH,
KERNEL_DEFCONFIG, and KERNEL_REPRODUCIBILITY_PATCHES. The default for
the above new variables is to the git.ti.com repository and how we manage
the kernel settings. The other kernel recipes that do something other than
how TI does it can simply override the variables.
This change will make it easier to perform the upstream testing that we
do on a nightly basis. Additionally, it will simplify the auto generation
of the patches to move the mainline (stable kernel) recipes since the
required patches will be all done in the same recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Resolve some issues with J721E and compressed NPOT (Non-Power-Of-Two)
textures.
Also, add some additional allocation tracking in render process specific
tasks.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We got a bit more time to do a proper migration this time. A discovery
period to see what actually works and boy, it wasn't much.
This update resolves issues with:
- Macro redefinition
- Sparse NPOT texture allocations
- vec4 reductions
- Mesa image extensions
- Buffer allocations under weston
- Devices with both a RENDER and PRIMARY display node
- Underprivileged users being unable to allocate buffers
- Removed call to drm_map_legacy
- Replace deprecated kernel calls
- Fix some cache attributes for userspace allocations
- About 40 other various errors and warnings
This core was never fully GLES2 conformant. In fact, if you try to run
cts on any of the older releases you'll find yourself in a hardware
recovery loop pretty quickly. We've gotten it to about 94.2% conformance
with these patches.
There are still dragons here, but they are at least a little more
manageable.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We were missing controlling the versions for linux-ti-staging-rt and
linux-ti-staging-systest using the BSP framework. Since the
PREFERRED_VERSION is not tied to the virtual/kernel we need two
additional settings for those alternate kernel package names.
For BSPs that do not have the -rt and -systest recipes then the two
new variable settings should effectively be ignored and cause no issues.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There was a change to the return value for a function pointer in the
kernel v6.11. This patch adapts the module to the kernel change.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adding needed recipe for initial testing and development of the 2024.10
version of u-boot for the next LTS.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This will prevent a lot of noise on the build logs.
Currently we have some erros:
rm: cannot remove 'file'
No such file or directory
Like the following:
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5 /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5-2024.04+git-r0*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5-2024.04+git-r0*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0*'
| : No such file or directory
| + true
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The upcoming SRCREV change to the linux-ti 6.6 kernel version no longer
needs these two patches, and they are blocking the CICD promotion being
in place.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Last user was dspdce-fw which is removed. Remove this now unused
support library.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was an attempt to run the DCE server firmware on the DSP instead
of on the IPU M4 cores. Not widely used and not used at all anymore,
remove the firmware for this.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
CMEM has been deprecated for removal for some time now. All users should
have migrated to the Linux upstream DMA-BUF Heaps framework. Remove CMEM.
We have already removed the CMEM kernel module but left the CMEM userspace
recipe to prevent breaking meta-arago builds which had some leftover
packages that still had a dependency on it. Nothing we now build still
needs this now so drop it out also.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove openmp-rtos component as deprecated and not maintained.
This used to provide OpenMP DSP runtime components for legacy devices.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
openembedded-core commit f5cfb3e23603 ("mesa: set PV from the .inc
file and not via filenames") now sets PV in the mesa.inc file
explicitely to whatever version oe-core is using.
Override that setting to the actual version here to prevent the
following parse error and whatever else would go wrong afterwards.
| ERROR: .../mesa-pvr_23.2.1.bb: Unable to get checksum for mesa-pvr SRC_URI entry 0001-meson-Disable-cmake-dependency-detector-for-llvm.patch: file could not be found
| The following paths were searched:
| .../meta-ti-bsp/recipes-graphics/mesa/mesa-pvr-24.0.7/bsp-ti-6_1/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
| ...
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update our custom config fragment handling code to work with the new
UBOOT_CONFIG changes. To better align with naming, change the name of
UBOOT_CONFIG_FRAGMENTS to just UBOOT_FRAGMENTS. Also create a
UBOOT_FRAGMENTS_CONFIG that goes hand in hand with UBOOT_CONFIG so that
you can specify different fragments for each of the config types.
For example:
UBOOT_CONFIG = "a b"
UBOOT_CONFIG[a] = "config_a"
UBOOT_CONFIG[b] = "config_b"
UBOOT_FRAGMENTS_CONFIG[a] = ""
UBOOT_FRAGMENTS_CONFIG[b] = "fragment1"
The logic in the class will automatically populate UBOOT_FRAGMENTS from
UBDOOT_FRAGMENTS_CONFIG.
Additionally, change the value that UBOOT_FRAGMENTS can take to be a
comma separated list of fragments to apply.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
To reduce the number of required builds for testing purposes, create a
common unified am62xx machine target that can produce all of the files
for all of the variant platforms related to am62xx (sip and lp).
Additionally, continue to support building the specific target if
desired.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Deploy a shell script that can take the deployed images/bootloaders from
a build and swap out the bootloader files with alternate versions
produced from the UBOOT_CONFIG flow and from what the u-boot binman tool
creates.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The IMAGE_BOOT_FILES variable has been overloaded to include additional
files that should be included in the boot partition but are not boot
loaders themselves (images, etc...).
There is also a need to generate a report in the deploy directory for
the list of actual bootloader files that were constructed as part of the
build.
Solution, break the IMAGE_BOOT_FILES into two new variables
TI_BOOTLAODERS and TI_MULTICONFIGS and default IMAGE_BOOT_FILES to
TI_BOOTLOADERS. This way we can stick additional boot loaders into a
new variable and they will will end up in the IMAGE_BOOT_FILES list.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A recent change in oe-core [1] to refactor the uboot flow allows for a more
targeted refactoring of our override code as well.
[1] TBD
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
omapzoom has been down since a long time. Point the repository to the
mirror in git.ti.com
Reported-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A compile error has apperaed when building againt the v6.10 kernel.
git/debugss_module/debugss-mod/debugss_kmodule.c:1149:34: error: array type has incomplete element type 'struct of_device_id'
1149 | static const struct of_device_id dra7xx_debugss_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~
The easy fix is just to add an include for the header that defines the
missing struct.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The gdbc6x debugger might be able to be updated for the reproducible
build effort. While we continue to explore what is possible, we will
disable the check so that we can continue to maintain our code for
releases.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt6x compiler is a custom TI compiler for the TI C6000
Digital Signal Processor(DSP) platform. It does not currently
support reproducible builds and is provided via a binary blob
download that we cannot patch in the recipe to address the
issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt6x compiler is a custom TI compiler for the TI C6000
Digital Signal Processor(DSP) platform. It does not currently
support reproducible builds and is provided via a binary blob
download that we cannot patch in the recipe to address the
issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt6x compiler is a custom TI compiler for the TI C6000
Digital Signal Processor(DSP) platform. It does not currently
support reproducible builds and is provided via a binary blob
download that we cannot patch in the recipe to address the
issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Referring to the TI specific kernel header file via -I${UNPACKDIR}
causes a "buildpaths" QA error. Solution is to tell gcc to map the host
directory to a target directory using -fdebug-prefix-map
Suggested-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Installer log contains absolute paths and is not really needed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A newly enabled check in master is causing errors with this package:
ERROR: QA Issue: Architecture did not match (ARM, expected x86-64)
Adding arch to the INSANE_SKIP variable disables that check for this
recipe.
Suggested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Applying the patches to all kernels is not going to work. Each kernel
might need different patches to address reproducibility issues.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add ti-img-rogue-driver as the preferred provider and enable the gpu
driver in the image.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j742s2 has the same GPU as j784s4. Add j742s2 support to the recipes.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Testing shows that the SRC_URI += does not work for adding the new
patches. += takes place during parsing, we want :append instead to make
sure that no matter what SRC_URI is in the various kernel recipes, that
we we append the patches to the end.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to pick up some patches that adjust the way heaps are
sized. This solves issues seen when utilizing page sizes greater
than 4K.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adding this sanity check here preemptively. Since these libraries were
compiled with an older version of GCC than what is currently in use on
scarthgap and master they won't trip the sanity check just yet, but if
someone attempts to update them and uses a newer compiler (for some
reason) it will trigger the sanity checks again.
This also keeps the DDK 23.3 and 24.1 recipe diff to a minimum.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add ldflags to INSANE_SKIP for the libopencl-rogue-tools package. For
some reason I didn't catch this sooner, but this falls victim to the
same issues the parent package faced earlier this year.
Just enough options enabled that Yocto wants to do a ldflags check, but
the DDK will not be able to utilize all the build flags Yocto uses.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
- Update SRCREV for jailhouse which incorporates makefile changes for
scarthgap.
- To handle ${ARAGO_IMAGE_SUFFIX}, add * wherever JH_RAMFS_IMAGE is used in
do_install (install or copy) so to pick correct inmate image for RT build.
- Skip QA checks for usrmerge and buildpath. This is required to package
jailhouse in image.
- Update FILES:${PN}.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update u-boot/ti-extras.inc to 2024.04 version.
Update linux/ti-extras-rt.inc to 6.6 version.
Update linux/ti-extras.inc to version 6.6.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The config fragment "am62x_r5_usbdfu.config" is applicable to AM62x,
AM62x-SIP, AM62x-LP-EVM, AM62Ax and AM62Px devices and enables USB DFU boot
support at the R5 stage of boot.
Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
J721E SK, AM68 SK and AM69 SK have similar connectivity
for CSI2 RPi connector and the same overlays can be reused,
thus pick the J721E SK CSI2 IMX219, fusion overlay and
AM68 SK V3Link fusion overlay for AM69 SK also.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
J721E SK and AM68 SK have similar connectivity for CSI2 RPi
connector and the same overlays can be reused, thus pick the
J721E SK CSI2 IMX219 and fusion overlays for AM68 SK also.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
J784S4 and J721S2 EVM has similar connectivity for MIPI CSI2
connector and the same overlays can be reused, thus pick the
J721S2 CSI2 OV5640 and J721S2 EVM fusion overlays for J784S4.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Reset this back to the proper branches for kernel 6.1 since this recipe
is only being used in 6.6 bsp providers.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Download and install the cc33xx firmware and binaries
to be used with the cc33xx drivers.
FW Version: 1.7.0.120
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
cc33calibrator is a tool provided by TI to manually control the
radio frontend of the cc33xx device. This tool can also be used
for production line testing of the radio.
Documentation for this tool is provided within the following link:
https://www.ti.com/tool/CC33XX-SOFTWARE
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
cc33conf is a tool provided by TI to configure
cc33xx WLAN devices. It can be used to change
the RF parameters and other features of the target.
Documentation for this tool is provided within the following link:
https://www.ti.com/tool/CC33XX-SOFTWARE
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Share the most commonality between the recipes, except:
* SRC_URI torvalds vs. linux-next
* SRCREV and PV
* Device Tree list vs. DT prefix
* SUMMARY
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The use of external metadata file to control RTOS binary firmware
integration has been deprecated some time ago. Remove it now.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as next BSP does not support all combinations
of SR1.0, HS-FS and HS-SE variants.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
For our upstream testing flow we have the need to have a "next" BSP for
configuring various settings based on building the latest kernel/uboot.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations
of SR1.0, SR2.0, HS-FS and HS-SE variants.
Suggested-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update am62xxsip-evm machine configuration to support
TI kernel 6.1 & ti-u-boot-2023.04
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As of commit [1] there will be a separate defconfig to build u-boot for
j721e-evm and j721e-sk.
Hence, introduce new yocto machine configs for j721e-sk.
[1]: c9507f07a1
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
MACHINE_KERNEL_PR is a remnant of the early OE days and hasn't been
needed for quite some time. Let's finally remove it completely.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
BeaglePlay gains official support from latest TI lts-6.6 baseline, so set
it as the default. Other Beagle platforms will still use BB.org as default.
And these defaults can still be changed with TI_PREFERRED_BSP setting in a
distro config or by end user in the local.conf
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all Beagle platform configurations to support multiple BSPs.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This adds a facility to define multiple supported BSPs with their own
preferences for individual components, as well as lets machine configs
specify conditional configurations for different BSPs.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to pick up some new binaries for AM62P. The allocation
patch for Chromium was not included for this device previously.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In order to be able to switch between different kernel providers, as well
as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize
Device Tree lists as follows:
* Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org
recipe for now, to be used when building beagleboard.org baseline
* Update KERNEL_DEVICETREE in the machine configs to only list what already
exists in the upstream/mainline kernel
* Update KERNEL_DEVICETREE_PREFIX to match the list when building TI baseline
With this change it is now very easy to switch the kernel between providers
supported by meta-ti - linux-ti-mainline, linux-ti-staging and linux-bb.org
Please note that 6.6 LTS has moved to "vendored" device tree layout even for
32-bit platforms, while BB.org still uses 6.1 LTS and flat DT layout.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lift the common parts of the top level gitignore from oe-core and
meta-openembedded. This masks out temporary python files, intermediate
artifacts, and unclean patch leftovers (.orig, .rej, etc).
We're choosing to leave patches at the root of the project out of this
as maintainer preference.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As of commit [1] there will be a separate defconfig to build u-boot
for j721s2-evm and am68-sk.
Hence, introduce new yocto machine configs for am68-sk. This is done
through a new am68.inc file as the am68-sk platform does not support GP.
So j721s2-evm.inc is copied to am68.inc and updated accordingly.
[1]: a96be9b8c0
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to pick up rebuilt binaries. Upstream release notes:
Regenerate all binaries with a fix for exportable buffer allocations
that should improve Chromium compatibility.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms
* Update DTB/DTBO lists to include latest renames and additions
* Re-enable vendored DTB layout by default
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all of the optee components to the upstream 4.2.0 version.
While at it, remove the patches and fixups which are not needed anymore.
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that are past the inital stages of our LTS migration, we can remove
the DEFAULT_PREFERENCE settings that prevented these recipes from being
the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While we are working to finish our kernel migration 6.6, we are falling
aback to software rendering for platforms that do not currently have a
solution for GPU drivers (namely the boards that use SGX).
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New features added require another increase to max_leb_cnt.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
This branch does not currently contain SGX patches so it is also being
masked by the ltsprep branding to prevent regressing those devices
currently.
Please note that may run into sstate errors when switching to or away
from the ltsprep tag. Please issue a clean to mesa and
ti-img-rogue-umlibs if you get warnings from either package's
do_create_runtime_spdx step.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Locally overlay verbatim copies of mesa 22.3.5 patches from
oe-core/master, so we get whatever QoL patches from core relevant to the
current release.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Recipes for DDK 24.1, but lock them behind ltsprep tags because they
require device tree changes that do not work on the current default
kernel for this layer.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Reusing the j784s4.inc file presents problems as the am69-sk platform
does not support GP. So copy the j784s4.inc to am69.inc and update
accordingly.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently, the 6.1 kernel is the default. Removing the k3-am69-sk dtb
file only applies to the 6.6 kernel. Restoring this entry so that
current builds work until such time as the 6.1 kernel is removed from
the recipes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream driver expects Wave5 firmware to be named "wave521c_k3_codec_fw.bin".
Driver probe fails because this compatible isn't being found.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Separate FAT boot partition holds SPL, SYSFW and U-boot images, while
rootfs places kernel images and DTBs into /boot directory. So it is not
desirable to mount boot FAT partition into /boot directory of the rootfs
and shadow its original content - adjust corresponding entry in wic
templates.
While at it, remove unused ondisk parameter when using use-uuid, which
takes precedence and is more flexible.
Note: boot FAT partition will be automounted at /run/media/boot-mmcblk0p1/
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Jonathan Cormier <jcormier@criticallink.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new kernel directory stucture for the DTBs is causing problems when
assembing the image files. It produces errors like this:
output: install: cannot stat 'deploy-ti/images/XXXX-evm/omap/XXXX.dtb': No such file or directory
or
output: install: cannot stat 'deploy-ti/images/XXXX-evm/ti/omap/XXXX.dtb': No such file or directory
The issue comes from the UBOOT_EXTLINUX_BOOT_FILES list. am57 already
had a mechanism but it was missing the omap/ dir to remove, and am33 and
am43 were just takeing KERNEL_DEVICETREE directly. This patch fixes
both cases.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We missed that the KERNEL_DEVICETREE should have been updated for the
32bit platforms with the change in linux-ti-mainline to v6.6. The new
directory structure under arch/arm/boot/dts is in effect for that
version.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This upgrade contains the following changes:
* updated hostapd path in ap_start.sh
* ap_stop.sh removes wlan1 interface
* hostapd.conf updated to work seamlessly with hostapd 2.10
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It is useful to have U-boot initial environment deployed for future
reference or to initialize environment files as part of the build.
In multiconfig setup, such as TI K3 platforms, building U-boot
multiple times for Cortex-R5 and Cortex-A53 cores results in file
conflicts when deploying under the same name. To avoid that, those
initial-env files were removed at the end of the do_deploy task.
But it is better to only remove them for k3r5 multiconfig, since
that only builds SPL and saved env doesn't make much sense, but
preserve and deploy initial-env for the main machine multiconfig.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update SRCREV for jailhouse recipe which will add changes for Out of Box
demo and also a new application to test whether the linux inmate cell has
crashed or not.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Latest ti-u-boot will be supporting HSSE1.0 and HSFS1.0 versions of the
j7200 soc through the binman dts nodes. Add support in yocto to package
the created binaries in the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Latest ti-u-boot will be supporting HSSE2.0 and HSFS1.1 versions of the
j721e soc through the binman dts nodes. Add support in yocto to package
the created binaries in the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Our CICD script inadvertently added the SRCPV back into the recipes.
The script has been fixed, so removing the variable once again.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New features added require another increase to max_leb_cnt.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Set the KERNEL_DEVICETREE_PREFIX so that, when using the various TI
kernel recipes, the "correct" DTB files are pulled in depending on what
is available in that kernel source.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
am69 and am68 sk boards supports V3Link cameras interfaced via V3Link
camera fusion board. Refer to
commit b7a97b1b (conf: machine: am62axx: Pick overlays for V3Link cameras)
for details
Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Acked-by: Jai Luthra <j-luthra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j722s-evm supports capture from fpdlink cams via fpdlink fusion1 board
or V3Link camera fusion board. So package fpdlink camera overlays
Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Like the current TI-RTOS/MCU+ firmware, this is a prebuilt example
firmware for TI K3 remote cores. It is an alternative to the echo test
demo currently provided by "ti-rtos-firmware" recipe. In addition to
supporting rpmsg_client_sample just as the current firmware does, it
also provides:
* A serial console with shell on the MCU UART port
* A console over RPMSG at /dev/ttyRPMSG0
* Example usage of the MCU GPIO/I2C/SPI from this shell
* And many other Zephyr default enabled features..
It does all this using the Zephyr RTOS, a scalable real-time operating
system, optimized for resource constrained devices, and built with
security in mind. Zephyr is a Linux Foundation project. For more
info see here[0][1].
Zephyr firmware like this can also be built as part of the Yocto build
using meta-zephyr. Although this is a prebuilt currently, we intend
to build this from source to reduce meta-ti's dependence on firmware
blobs.
This currently works with the AM62 M4F. Support for additional SoCs
and cores is in progress.
[0] https://www.zephyrproject.org/
[1] https://docs.zephyrproject.org/latest/introduction/index.html
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We have a request to be able to override the beagle kernel set in
PREFERRED_PROVIDER_virtual/kernel, but it is being absolutely set and
not loosely set with ?=. Take this time to create a central include for
all beagle boards like we have for the k3.inc.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This firmware is named so that the correct firmware is chosen on each
machine. No need to split this package for each machine, combine them
into one non-machine-specific package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The firmware for different machines and versions are named differently so
there is no need to have machine specific packages for each of these
firmwares. Move all the PRU-Switch firmwares into single package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The firmware for different machines and versions are named differently so
there is no need to have machine specific packages for each of these
firmwares. Move all the PRU-HSR firmwares into single package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The firmware for different machines and versions are named differently so
there is no need to have machine specific packages for each of these
firmwares. Move all the PRU-ETH firmwares into single package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Most firmware does not run on the host and is therefor not architecture
specific, at least as far as the package manager is concerned. Although
the firmware might not be useful on some machines, the package itself
is not machine specific. Remove PACKAGE_ARCH.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update from 0.6.4 to 0.6.6.
This update brings the following fixes from ti-rpmsg-char repo.
55a6f40 remove ti.ipc4.ping-pong reference
8892e57 lib: fix data type build warnings
7c2ab48 lib: fix build warnings
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new V3Link camera fusion board [1] comes with a CSI to FPDLink
serializer board, which allows interfacing multiple 22-pin FFC
compatible sensors with SK-AM62A.
Currently overlays for interfacing IMX219 sensor with V3Link are built
as part of the TI linux kernel, so pick these in the BSP filesystem.
[1]: https://www.arducam.com/fpd-link-3-cameras/
Signed-off-by: Jai Luthra <j-luthra@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Stop using UBOOT_LOCALVERSION, and copy what is done in the kernel recipe. This
allows us to set the correct SHA into the version string even if AUTOREV is used
since SRCPV is no longer set in oe-core.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The use of KERNEL_LOCALVERSION for controlling the kernel version has
changed recently. Placing the value of KERNEL_LOCALVERSION in
.scmversion was causing it to duplicate the string in the final version.
Instead, drop KERNEL_LOCALVERSION to just identify that it comes from
TI, and that it is an RT kernel. Additionally, place the commit sha for
the kernel into the .scmversion file explicitly to be both backward and
forward compatible.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch moves the jailhouse recipe general variables to a
ti-jailhouse.inc file along with fetch and compile task.
Jailhouse repo also contains some demo applications which can
be packaged alone in filesytem and does not require packaging
jailhouse module, firmware and tool.
So add a new recipe jailhouse-inmate which can be used to only
package those demos. The existing jailhouse recipe will contain
variables and other dependencies needed for do_install task for
jailhouse module, tools, demos etc. The do_install of jailhouse
inmate recipe will only package demo applications.
This new recipe(jailhouse-inmate) will be added to a new image
in meta-arago. The new image will be used for jailhouse second
linux instance or cell.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update linux-bb.org to 6.1.69 for both 32 and 64 bit platforms
* Update u-boot-bb.org to the latest 2023.04 based on SDK 9.1 release
* Update DTB/DTBO lists to include latest renames and additions
Note: all changes are in a single commit for bisectability
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream now includes all DTB/DTBO files recursively, no need to extend
corresponding FILES list.
Revert "linux-bb.org: also package DT overlays in separate dir"
This reverts commit f22ea63f66.
Note: adjust SRC_URI cosmetically, so it now matches kirkstone
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The current master has the support for power off functionality, update
to that.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all OP-TEE components to 4.1 tag. OP-TEE examples are already in
4.1 tag.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Switch the branches to the new LTS names. These are still experimental,
hence the isolation from kirkstone.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The "upstream" is not maintained, but this is an easy patch to get this
working again. Still need to watch this for big breakages and rethink
supporting this recipe at that time.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add TI logo image as bootsplash image file for AM62P and install it in
boot directory from where u-boot can read from and display during
boot-up time.
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In preperation of LTS migration, switching from 2024.01 to 2024.04 for
u-boot as this is close to what will be the final version for LTS.
Default preference is still kept as low for this version since we are in
early migration phase.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Migrate to version 23.3.6512818, this includes the stability updates
released in 23.2 as well as some additional modifications to help with
userspace application support, namely Chromium.
We're also dropping the x11 window system extensions from the Vulkan
libraries for now. Ideally, both x11 and wayland extensions will be
provided by mesa's vulkan-wsi-layer in the future, but currently x11
isn't supported and this just added extra complexity to the package in
Yocto.
Signed-off-by: Randolph Sapp <rs@ti.com>
Tested-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to include some useful patches that:
- Fix the ROGUE segfault issue introduced by SGX (this was what
the old conditional logic was addressing)
- Fix destruction of event queue with proxies still attached
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
If Yocto even sees a "-dev" package in the PACKAGES string it will
automatically forward all dev-so links to that package. Remove that
entry from the PACKAGES string so we get the required links again.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for ti-extras for am62xx-lp to control the kernel and u-boot
repos, branches, and srcrevs via the TI_EXTRAS variable in the local.conf
file.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that 2024.01 is official, the logo that am62xx-evm installs is
available in all versions of the repo that we point to. Move all of
that code out of the .bb files and into the u-boot-ti.inc file.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include the following changes in UM and KM:
- Rebuild all releases with external memory wrap disabled due to
some incompatibility with certain Qt use cases.
- Add a watchdog change that prevents an occasional false
timeout when servicing long DM processes.
- Rely on snooping to perform certain cache operations and
results in decreased overhead for device -> cpu
communications.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A patch has been accepted in mainline u-boot that has binman calling
yamllint to verify the configs during compile. This means that the
yamllint must be available as a tool at the time.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add recipe for yamllint. There is an upcoming change in u-boot where
the binman tool is now configured to call yamllint to verify the configs
during compile time.
There was a previous patch a year ago from Trevor Woerner that never
made it into oe-core. This patch is a reworking of his patch but
pointing to a newer version.
We are waiting on this patch to be accepted in oe-core. Once it is
available on master we will remove this recipe to avoid conflict.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j722s is same GPU as am62p, need to add this into machine definition so
that Rogue driver gets included in the image.
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fetch from the latest commit which has J722S support now.
Signed-off-by: Apurva Nandan <a-nandan@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove config files from /usr/share/jailhouse as they are not required.
Package only the cell files for respective devices and not all k3 files.
Update FILES:PN to use wildcard.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
RPM does not accept '-' as a character in the PR/version and fails with:
| error: line 4: Illegal char '-' (0x2d) in: Release: sgxrgx-54fd9d7dea098b6f11c2a244b0c6763dc8c5690c.1
The correct approach is to reference SRCPV and not SRCREV and also add it
to PV and not PR. But PV is used in the branch to fetch the sources and
cannot be modified, so use SRCPV in PR w/o any illegal characters.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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 <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are preparing to migrate our uboot version to 2024.01. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this uboot in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
2023.04 uboot and make this the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are preparing to migrate our kernel version to 6.6. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this kernel in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
6.1 kernel and make this the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the BB.org kernel to the latest. Also update BeaglePlay device
tree list, as there were some renames and new additions.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit [1] created a common LPM wkup sources overlay and removes
k3-am62x-sk-mcu-gpio-wakeup.dtso for am62 device family.
k3-am62x-sk prefix picks this overlay for am62xx, am62axx and am62xxsip already.
This patch picks the necessary overlay for am62xx-lp-evm since it doesnt use
the same prefix as other am62 platforms.
[1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=4ba1886b886d
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update SRCREV for ti-jailhouse. All the patches which was being applied via yocto
have been moved to ti-jailhouse repo now. So remove the patches from SRC_URI and
files.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for ti-extras for am62pxx to control the kernel and u-boot
repos, branches, and srcrevs via the TI_EXTRAS variable in the local.conf
file.
Also add am62pxx as compatble machine in jailhouse recipe. So the am62pxx
jailhouse build can be done by adding TI_EXTRAS=tie-jailhouse in local.conf.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A bug was introduced while trying to unify the Mesa version that is used
on SGX GPU's and Rogue GPU's. It manifests itself as an immediate segfault
whenever you try and run something like glmark2-es2-wayland or
weston-simple-egl on certain Rogue based platforms (specifically am62x).
Use different srcrev for Rogue GPU and SGX GPU platforms. The SGX GPU platforms
will use the latest commit. Rogue GPU platforms will use the last good working
commit before SGX related changes were introduced.
This change will be reverted once the issue is rootcaused and a common solution
is found for both Rogue and SGX based GPU platforms.
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upgrade to v6.3.0 version.
This release adds resources for using AM243x & AM64x PRU cores with cores
running FreeRTOS:
* The RTOS Getting Started Labs
* Examples for using PRU GPIO and the broadside interface
* SORTE_G example (a custom networking interface)
Bug fixes:
* AM64x & AM65x header files, fix the names of extended sections to be in the
format of
ConstantsTableName_0x100
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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 <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit [1] renamed the MCU GPIO wakeup overlay as k3-am62x-sk-mcu-gpio-wakeup.dtbo
k3-am62x-sk prefix picks this overlay for am62xx, am62axx and am62xxsip already.
This patch picks the necessary overlay for am62xx-lp-evm since it doesnt use
the same prefix as other am62 platforms.
[1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=24bd6ce832cd
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was a temporary class to help with the v5.10 to v6.1 kernel
migration, now that we have completed that, remove this class.
Suggested-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We support Linux v6.1 as our official version for Kirkstone. The older
kernel version was kept around during the transition to the newer version,
but we are past that now. Remove this old version.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SRCREV is auto updated, but the PV still uses the old tag version,
update this to v0.3.
While here, we also now have a proper LICENSE file, use that.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit f5851386 ("conf: machine: am62*: Pick common overlays by prefix")
picks common HDMI and CSI overlays for am62 platform variants.
Adding capability to extend the same prefix for common overlays for applicable
am62 platforms in more generic way to include new mcan overlays added [1]
[1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=3b01c392627f
given the differences in SK-AM62-LP containing B2B HDMI Samtec connector,
just added the kernel prefix to pick common mcan overlay.
for am62pxx: It has 4 MCANs vs all other am62xx devices have 3 MCANs,
hence keeping this prefix seperate for am62pxx to pick right overlay.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Jai Luthra <j-luthra@ti.com>
Reviewed-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These are all useful for firmware recipes but some recipes did not have
them. For firmware including ti-linux-fw.inc let's add these all to
one spot and remove them from any recipe that did already have these.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These defines are specific to a SoC, not any specific board. Move these
to the SoC level for these boards to be consistent with boards already
doing this correctly.
J7200 didn't have these at all, add them while we are here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The common include ti-linux-fw.inc already includes setting this, no need
to set it in each recipe, remove that.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is no compilation in this simple firmware recipe, no need for
these lines, remove them.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These are common for all recipes that include ti-linux-fw.inc, add
it to this include file and remove from each recipe.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for ti-extras features for rt as it was added for non
rt kernel and u-boot earlier. It will also be accessible via the
TI_EXTRAS variable in the local.conf file.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Don't try to locate TI-TFL license within meta-ti-bsp relative to OE-Core
using COREBASE, as the directory structure of the layers is not guaranteed.
Instead, point to it relative to the recipe itself.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Minor rework of the TI include files used to override both SRCREV and
other settings in the optee recipes for TI SOC parts. The intent is to
make it more clear when we are changing SRCREVs versus changing other
items, and allow for sharing the SRCREV changes for optee-os-tadevkit
which should track the optee-os SRCREV.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the SRCREV to latest commit for both u-boot and linux
extras. Also update SRCREV for jailhouse branch for both psdk
linux and u-boot.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous allowance for overriding the value for the kernel is
incorrect. The kernel should not be changed from linux-dummy for the
k3r5 multiconfigs.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is a build error under master that is not present in kirkstone
related to .SECONDARY/.NOTINTERMEDIATE being set differently between the
ti-img-rogue-driver repo and the kernel. The long term solution to
allow this code to be built on both kirkstone/master is being
investigated. In the meantime, this patch gets things building on
master.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move to the 23.2 release branch and bump SRCREV accordingly. This branch
has the proper implementation of the cache coherency fix along with some
other checks that address some system stability issues on Jacinto
devices.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include some patches to better isolate SGX and PVR
components.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Instead of making kernel RDEPENDS on devicetree and different FW images with
lots of machine-override appends that are hard to modify downstream, use proper
MACHINE_ESSENTIAL_EXTRA_RDEPENDS and MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS vars
that are specifically designed for this purpose.
This also makes such dependencies generic and not tied to a particular kernel
recipe including kernel-rdepends.inc with the entire machine-specific list.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Acked-by: Andrew Davis <afd@ti.com>
Acked-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Set MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS per platform to list recommended
essential FW images to be added to rootfs by default.
Correct beagle-x15 to pull devicetrees and kernel image as well.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Majority of Beagle devices use ti-u-boot repo from u-boot-ti-staging directly.
But some latest devices may need to point to own tree with additional support
added that is not yet upstream, e.g. BeaglePlay.
Add the Beagle-specific recipe and point beagleplay to use it. Other devices
can switch to using it as well, if desired, but right now the code base is the
same for other Beagle devices.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update both 32-bit and 64-bit configs to use the latest 6.1 Linux kernel
from beagleboard.org repository, which is based on ti-linux-kernel repo
used in linux-ti-staging, but with extra Beagle-specific features on top.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update DTB/DTBO list to only upstreamed devicetrees and overlays. This
help with migration to kernel 6.1, which doesn't have BB.org specific
overlays.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update DTB/DTBO list to only upstreamed devicetrees and overlays. This
help with migration to kernel 6.1, which doesn't have BB.org specific
overlays.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since the introduction of TI_COMMON_DEPLOY, we've been seeing frequent
Pseudo errors [1] breaking image build during development, in particular
with partial rebuilds due to the externalsrc bbclass.
The relevant part of the error log seems to be the following:
ERROR: Task (/home/schifferm/Devel/src/ci-meta-tq-kirkstone/sources/meta
-tq/meta-dumpling/recipes-images/images/tq-image-generic-debug.bb:do
_rootfs) failed with exit code '1'
Pseudo log:
path mismatch [1 link]: ino 12215614 db '/home/schifferm/Devel/src/ci-me
ta-tq-kirkstone/build-mba64xx/deploy-ti/images/tqma64xxl-mbax4xxl/tq
-image-generic-debug-tqma64xxl-mbax4xxl-20231020091917.testdata.json
' req '/home/schifferm/Devel/src/ci-meta-tq-kirkstone/build-mba64xx/
tmp/work/tqma64xxl_mbax4xxl-tq-linux/tq-image-generic-debug/1.0-r0/r
ootfs/usr/share/stress-ng/example-jobs/device.job;65324e26'.
My understanding is that all deploy dirs should be ignored by Pseudo, as
openembedded-core/meta/bitbake.conf includes the whole of DEPLOY_DIR in
PSEUDO_IGNORE_PATHS. With the introduction of TI_COMMON_DEPLOY,
DEPLOY_DIR_IMAGE is not covered by that setting anymore, so we add it in
meta-ti to avoid the issue.
[1] https://wiki.yoctoproject.org/wiki/Pseudo_Abort
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
2023-10-11 15:28:15 -05:00
313 changed files with 4206 additions and 3127 deletions
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
