Update to latest ti-master commit which includes support for
BeagleBadge.
Signed-off-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for the BeagleBadge which is an AM62L
based device that requires new build configuration
for U-Boot and TF-A sources.
Signed-off-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A recent change in meta-arm installs all of files into a
trusted-firmware-a directory. We need that added to the paths for the
PACKAGECONFIG settings so that u-boot can compile.
Take this opportunity to also break all of the firmware paths into
separate variables in case we need to override one of them in the future.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The name of the u-boot defconfig changed when it was upstreamed into
2026.01, and the name of the dtb changed to k3-am6254atl-sk.dtb in the
kernel.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add entries for ti-6_18 for the upcoming LTS development effort. This
includes:
kernel: 6.18
u-boot: 2026.01
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As am57xx.inc is now the only user of omap-a15.inc, merge the content of
omap-a15.inc into am57xx.inc and remove omap-a15.inc. As we no longer have
this common include, also remove "omap-a15" and use "am57xx" in its place.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As AM57xx already defined both "dra7xx" and "am57xx" as SOC_FAMILY the
AM57xx was effectively a superset MACHINE. Although not all features of
AM57xx are needed for DRA7xx, make DRA7xx-EVM use the AM57xx definition.
This allows us to still support DRA7xx as the only differences that
impact device function are the selection of U-Boot defconfig, DTBs, and
OPTEE, all handled by the MACHINE conf file which is left unchanged.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This is no longer used anywhere, drop it out.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This is no longer used anywhere, drop it out.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These were used back when each board had to select the correct tiboot3.bin
to become the default for that board's image. Two things have changed since
then, first we deploy all options for tiboot3.bin generated by U-Boot. And
second, U-Boot's binman tool now symlinks the most appropriate version of
this file for us for the selected U-Boot defconfig file.
These are no longer needed so drop them.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As R5 only builds one working image (tiboot3.bin), define this as the
"UBOOT_BINARY", even though it was technically build using the SPL build
pass in U-Boot. This allows some simplification and removes deploying of
a dummy file (u-boot-spl.bin) which is not a usable boot file. It was only
deployed as UBOOT_BINARY is not optional and so something needed to be set
here.
BeagleBone-AI64 already did something similar to this so the overrides
in that MACHINE conf can now be removed.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These were set to the defaults we would expect from OMAP class U-Boot,
but as all board families set these including the OMAP class MACHINEs
we can remove these defaults. This helps in the cases that we do not
want to define one of these, such as SPL_BINARY in the case of OMAP-L138
which does not use SPL.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Every MACHINE build deploys a tiboot3.bin file for all three K3 security
types (GP, HS-FS, HS-SE). These extra MACHINE configs existed to select
a different default. As U-Boot now selects a default for us this logic
does not need to exist here. Instead if one wants to use a non-default
security type for an EVM then can simply rename the tiboot3.bin file in
the boot partition. Testing automation already handles this and Sitara-
family devices have dropped the dedicated MACHINE configs, do the same
for Jacinto-family devices.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add TPS6594 core and regulator driver modules in the initramfs image so
that the SD card can be probed for am62axx as it is dependent on regulator
to get the SD card probing and eventually boot from it.
Signed-off-by: Moteen Shah <m-shah@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adds the required TF-A and OP-TEE patches to enable LPM support on
J7200, J784s4, J742s2.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We have added a new PV check to the check_repo script that checks to
make sure that PV is set either in the filename or via the PV variable
in the recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We have some projects mirrored to GitHub currently. It makes sense to
add a MIRRORS entry for git.ti.com sources to fall back on in the event
git.ti.com is unreachable.
Placing this in the main BSP layer configuration file should be all that
is required for this and any other layers that depend this core layer to
fall back to GitHub.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New recipes for GPU DDK 25.2. Update BSP configuration files with new
preferred recipe versions.
For the driver recipe, specifically unset the CC variable due to yocto
appending CROSS_COMPILE and CC, resulting in a warning for the
do_compile task:
make[1]: aarch64-oe-linux-aarch64-oe-linux-gcc: No such file or directory
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The recent SRCREV bump to ti-rpmsg-char makes this patch not apply.
Update the patch to match the new changes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update rpmsg library to 0.6.10
It brings the following fixes from ti-rpmsg-char repo:
d4cf638 src: fix bug in file_read_string()
3e72722 src: add api to fetch kernel allocated remote proc id
5061690 benchmark: update max runs = 1 trillion, max latency = 9sec
4aa2a84 examples: clean up tabs, delay metering
07660dd example: add rpmsg_char_benchmark
b40845f Replace read bytes from 256 --> 496
b2e9e2f Update max message size to 496
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently, the overlay mentioned in KERNEL_DEVICETREE_PREFIX in case
of j722s is "k3-am625-sk-mcspi-loopback" which is incorrect as it has
been renamed recently. Change the overlay to "k3-am62x-sk-mcspi-loopback"
in order to carry out SPI loopback tests successfully.
Fixes: 3b2097d727 ("conf: machine: j722s: Change overlay in KERNEL_DEVICETREE_PREFIX")
Signed-off-by: Anurag Dutta <a-dutta@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Package eHRPWM overlay for am62dxx-evm by reusing the existing overlay
for am62a7-sk.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since cifs-utils is available in meta-openembedded, not OE-Core, it
cannot be added to this packagegroup unconditionally, as meta-ti-bsp
doesn't depend on meta-oe, only recommends it.
As it breaks yocto-check-layer now, move cifs-utils addition to
dynamic-layers to be added conditionally on meta-oe presence.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are seeing errors when building against linux-next where we run into
the INITRAMFS_MAXSIZE check. Lower the overhead factor a little to give
us a little more room.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Replace MIT license with TI-TFL to align with TI release policy
and product requirements. Legal approval: SRAS00013045
Update scarthgap srcrev and disable 2dfft example from lib build.
License-Update: Replace MIT to TI-TFL license
Signed-off-by: Vishnu Singh <v-singh1@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Major Updates since 1.7.0.120:
- Added WPA1 support
- Addressed many stability issues in WiFi and BLE
- Enabled thermal protection for operation up to 105C
SHA1 checksum:
c364c4d89802bcac769ee6eebc08ae1c4ef5a205 cc33xx_2nd_loader.bin
b39bfac65e0300e81dfcfee7301e07b4289df448 cc33xx-conf.bin
821fa40f608e350baa9e4cdfea6719bf469c5220 cc33xx_fw.bin
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
MCSPI overlay can be used for all am62* SK boards as well as
am62p SK, so include the overlay for am62p and am62 LP SK builds
since it is not included in the default configuration.
Signed-off-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upgrade U-boot to 2025.10.
PocketBeagle2 defconfigs and branch got slight name change.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New features added require another increase to max_leb_cnt
Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Package overlays which are common for AM62 family of devices for
am62dxx-evm by adding prefix string in KERNEL_DEVICETREE_PREFIX.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
am62dxx previously reused am62axx DM, but now that a dedicated DM is
available, migrate to device-specific DM.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
TI_INITRAMFS_KERNEL_MODULES gets set only for TI platfroms and ends up
being undefined otherwise, which breaks parsing in yocto-check-layer
and/or in multi-BSP setups. Ensure the variable is defined in the
packagegroup, if not already set by the machine configuration.
Remove the previous default assignment since we put it in the wrong
location.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Trigger build for initramfs image and package it in the boot partition
of all TI SoC's whenever an image recipe is built with upstream
kernel(mainline or mainline-next).
Signed-off-by: Moteen Shah <m-shah@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add initrd path to grub.cfg config so that it picks up
the initramfs image from the boot partition and includes
it in the boot process.
Signed-off-by: Moteen Shah <m-shah@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Introduce a new minimal initramfs image which will be used
for all K3 devices in the boot flow. The image will package
boot essential and other modules which will be modprobed by
initramfs-udev once the inbuilt drivers gets probed.
Signed-off-by: Moteen Shah <m-shah@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a new variable in ti-soc.inc which would be populated by individual
platforms with the required modules which would later be packaged inside
the initramfs image.
Signed-off-by: Moteen Shah <m-shah@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe builds and runs fine on both DRA7x and AM57x machines.
The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x
machines also set themselves as DRA7x family devices. The issue is then
we cannot then differentiate between packages that are actually DRA7x-
only and those that just use that family to mean both machine types. To
fix this when we mean both are allowed use "omap-a15" as done here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe builds and runs fine on both DRA7x and AM57x machines.
The COMPATIBLE_MACHINE is set to just DRA7x, but this was okay as AM57x
machines also set themselves as DRA7x family devices. The issue is then
we cannot then differentiate between packages that are actually DRA7x-
only and those that just use that family to mean both machine types. To
fix this when we mean both are allowed use "omap-a15" as done here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe is already only compatible with the DRA7xx machine, so
no need to set PLATFORM based on the only possibility. This then
allows us to directly set the compile flags for the same. And now
that the package does not change based on the machine, remove the
PACKAGE_ARCH line.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe is already only compatible with the DRA7xx machine, so
no need to set PLATFORM based on the only possibility. This then
allows us to directly set the compile flags for the same. And now
that the package does not change based on the machine, remove the
PACKAGE_ARCH line.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was only ever used as part of the DSP firmware for OpenCL dispatch.
That is all gone now, so remove this leftover dependency.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
vpe-tests is obsolete, it was replaced with "testvpe" as part of
glsdk-example-apps about 10 years ago in meta-arago, so long ago even
its replacement has been obsoleted and removed. Yet, this unbuildable
recipe still lives on here in meta-ti. Send it out to sea.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As of u-boot 2025.10, the fit image requires a value for the default
configuration. The change [1] introduced the FIT_CONF_DEFAULT_DTB code
to the legacy fitimage class, but failed to set values for the legacy
platforms. This led to us putting default = "" in the .its file, which
is now an error.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
AM64x supports PRP. Add pruprp-fw to AM64xx so that this can be packaged
for AM64xx
Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot bb.org-v6.12, Mainline, Next, and all future releases will have
am67a_beagley_ai_r5_defconfig. Only the three listed versions in this
patch need to use the old defconfig. Set the default so that we do not
need to set this for future versions.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
An upcoming patch series will optionally add in a second repository that
will optionally be needed as part of the builds. To facilitate that, we
need to name the uboot checkout so that the SRCREV can be tracked correctly
in the recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The TI_EXTRAS infrastructure needs a little tweaking to support turning
on multiple extra options at the same time.
1) Since TI_EXTRAS can be a space separated list and not a single fixed
value, we need to change how we detect when to include the TI_EXTRA
values.
2) The tie-jailhouse overrides were being a little too heavy handed.
All of the variables that are changed for any given extra feature needs
to use the proper variable override. This was most important for the
COMPATIBLE_MACHINE settings.
3) Move the ti-extras out of specific machine configs and into the
ti-soc so that all machines can use the extras.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that display controller aliases are not set using PACKAGECONFIG,
instead of using PREFERRED_PROVIDER to add either "sgx" or "pvr" to
PACKAGECONFIG, followed by reading it back out, simply use
PREFERRED_PROVIDER directly.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update mesa-pvr which includes a default set of display controller
aliases for the supported display controllers. This means we do not
have to manually set the alias for each device here in the integration
layer. Remove that here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The DRIVER and matching UMLIBS must always match, no need to define a
version number for both. Keep this simple and remove the extra defines.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Setting or removing the gpu MACHINE_FEATURE does not actually change
if the GPU driver is built or not. That is done based on the setting
of the BSP_{SGX,ROGUE}_{DRIVER,UMLIBS}_{PROVIDER,VERSION} vars. These
are default empty for BSP versions without supported GPU drivers, which
will correctly cause a fallback to SW rendering when the GPU driver is
not available.
As the "gpu" MACHINE_FEATURE now has no uses, remove it from all the
machine config include files.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update optee_client, optee_examples, optee_os and optee_test to the
newer 4.7.0 tag from the previous 4.6.0 one.
Further: meta-arm applies 0003-optee-enable-clang-support patch to
optee_os. However, in a recent upstream commit [0], the line to which
the patch applies was removed. Therefore the patch is no longer
required. As a result, tell optee_os.bbappend file to remove it.
[0] 3d5c2dd8b5
Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are missing the optee-ftpm package verson override along with our
other optee-* overrides. This resulted in a build error when meta-arm
moved to 4.7.0 while we are still sitting on 4.6.0. The 4.7.0
optee-ftpm is using some new header info that the 4.6.0
optee-os-tadevkit is not providing.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The BL32_BASE address is properly set in TF-A to jump to OP-TEE's
entrypoint for the am62lxx SoC family, so we can safily drop this.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch introduces udev rules to ensure consistent device naming for
VPU decoders, encoders, and the JPEG encoder. These rules are essential
for enabling hardware-accelerated video decoding in Chromium using the
V4L2 Stateful decoder.
The following udev rules are added:
- Map vpu and vpu0 to /dev/video-dec0 and /dev/video-enc0.
- Map vpu1 to /dev/video-dec1 and /dev/video-enc1.
- Map the JPEG encoder to /dev/jpeg-enc0.
These changes ensure proper operation of the VPU and JPEG encoder,
especially when other video devices are connected, avoiding mismatches.
Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com>
Reviewed-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Newer silicon revision of the AM62L family are capable of reliably
booting with OP-TEE integrated in the bootflow with all bootmedia.
However to support as many DDR densities as possible we cannot use the
default 0x9e78000 location as with other K3 devices.
So add OP-TEE back into the default build but modify the BL32 base
address for TF-A so it will jump to the correct location.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The latest tag in ipcdev project is 3.52.00.01. Update SRCREV to the
latest tag.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The messageq IPC firmware example for AM57xx SoCs is available in
ti-linux-firmware repository. Add a recipe to package the prebuilt
messageq firmware into the rootfs.
Additionally, make sure the firmware for IPU1 rproc is copied into boot
partition by updating the dependency in omap-a15 machine conf to the
above recipe. This is needed for Early Boot use cases and gets rid of
dependency on meta-ti-extras layer.
There is no need to deploy the vayu IPC firmware anymore. Remove
the deploy task from ti-ipc-rtos recipe.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe to build the Application Host (for A15 core) to demonstrate
IPC with remote processors through messageq firmware. Also package this
in the /usr/bin directory for testing IPC. This recipe only builds the
app_host, and the firmwares are available in ti-linux-firmware
repository.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot generates all the valid versions of tiboot3.bin and sysfw.itb
based on the given defconfig. The defaults are also picked based on
the board's binman files. No need to duplicate this logic here,
simply deploy what U-Boot generates.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
V4L2 has updated fh_add/delete to take another parameter in linux-next.
The update has been made in out-of-tree module to fix build failure.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Improve KERNEL_DEVICETREE lists for all Beagle platforms:
* Expand the list with more overlays and related DTBs
* Since in many cases the lists are slightly different between
6.6 and 6.12 kernels, explicitly provide both separate lists
* PocketBeagle2 is only supported by 6.12, so one list for now
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the INSIDE-Secure LICENSE and update the PKA recipe to use this
license.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe to install the PKA firmware in root filesystem needed by
sa2_ul driver for PKA operations across all K3 platforms.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Seems having hyphens in the revision tag causes issues with
RPM packaging. Remove this hyphen.
Reported-by: Daniel Schultz <D.Schultz@phytec.de>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
If you are not building a TI machine then KERNEL_BASE_CLASS is not
defined and you get a parse error. Move the default setting out of
ti-soc.inc and into ti-kernel.inc.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
2025-08-01 11:46:52 -05:00
179 changed files with 1636 additions and 862 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.
