Package k3-am62a7-sk-e3-max-opp.dtbo for AM62D2-EVM to configure C7x DSP
to run at its maximum supported frequency of 1GHz.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Recently, a few commits were merged beyond the 4.9.0 tag in optee_os. These
commits refactor some code in SA2UL, and add firewall configurations for RNG in
AM62L. Therefore, to integrate these changes in the SDK, update the optee_os
SHA.
Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updates trusted-firmware-a to a commit with the LPM patches and removes
them from yocto.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Our initial testing is nearing completion and 6.18 is ready to be our
default kernel along with 2026.01 uboot.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When loading an initramfs, the kernel no longer provides functionality
for mounting the rootfs. nfs-utils-mount is the minimal required
packages to provide the needed tooling for the kernel to mount the
rootfs over nfs when using an initramfs.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Using the new UBOOT_CONFIG flow, enable a mode where additional uboot
configurations can be built along side the main config. In this case,
turning on USBDFU for a board for testing purposes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Change the branch for am62l to ti-tfa-2.14y and change the TFA_PLATFORM
for am62l.
License-Udpate: am62l branch is now in line with master, so the md5sum
changed to match.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New recipes for GPU DDK 25.3. Update BSP configuration file to
package driver, which now supports kernel 6.18.
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update ti-rpmsg-char library to 0.6.11
It brings the below fixes:
dd4783422bf lib: Do not update local endpoint
f26e4a30ca7 example: benchmark: move latencies array to data section.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rather than using ?= to default the value of IMAGE_BOOT_FILES, instead
use += to add the files we want to the probably empty value.
We ran into an issue where the recent ti-core-initramfs changes used +=
and overrode the ?= in k3.inc, resulting in no boot files being packaged
in the wic boot partition. This addresses the issue by ensuring that we
never have a situation where the required files are not in the final
list.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update optee_os, optee_client, optee_examples and optee_test to the
newer 4.9.0 tag.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add TI_CORE_INITRAMFS_EXTRA_INSTALL variable that another layer can use to
install additional packages/changes into the initramfs. Setting this
variable will also turn on the initramfs even if the platform does not
have kernel modules to include.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Clean up the logic of the new ti-core-initramfs to reduce the impact on
downstream layers.
- Flip the logic in the machine .conf files to track the list of
required kernel modules for that platform, but if the variable is set
to "" then the ti-core-initramfs will not be created.
- Redo the logic of when we require creation/usage of the initramfs to
just platforms that need it (ie that set TI_CORE_INITRAMFS_KERNEL_MODULES).
- Add a big switch to disable the initramfs entirely. In that case, the
user is on their own to make sure that the kernel has everything it
needs to boot either via config fragments to turn on the needed
modules, or by using the TI_CORE_INITRAMFS_KERNEL_MODULES
variable to populate their own initramfs.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Pull additional standard VIRTUAL_RUNTIME components to respect Distro
configuration (e.g. systemd/udev, etc.)
This only requires adjusting the size to 128MB.
Signed-off-by: Denys Dmytriyenko (TI) <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
TAD5212 now uses a dedicated driver instead of the PCM6240 driver,
making the firmware files no longer needed. So remove the recipe and
corresponding changes.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When the feature was sent to upstream, it was requested to change the
command line option for specifying the key. Adapt to that change and
ensure it still works as is for bsp-ti-6_12.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Provide framework for how to sign the uboot files with different keys
so that customers can see how it is done. We have provided an ECDSA
key and follow on patches will show how to point to it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
meta-arm updated optee to 4.9.0 and added logic manage the
tag=xx;nobranch=1 vs branch=master in the SRC_URI for all of the optee
recipes except for optee-ftpm. Set the new variable to the same logic
as the other optee recipes to fix an unpack error.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It looks like the ti-linux-6.18.y was force pushed. As we are still in
the process of getting the LTA up and running, we need to update the
SHA.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Using the new UBOOT_CONFIG flow, enable a mode where additional uboot
configurations can be built along side the main config. In this case,
turning on USBDFU for a board for testing purposes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Using the new UBOOT_CONFIG flow, enable a mode where additional uboot
configurations can be built along side the main config. In this case,
turning on USBDFU for a board for testing purposes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since the extras stuff should "theoretically" apply to all u-boot
versions, move the include out of each recipe and into the central
include file.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Port the kernel module for gc320 driver to build on linux kernel 6.18.
The overall version of the driver remains the same.
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-vxe-vxd-driver recipe is not building with the 6.18 kernel.
Once a new version that addresses this is available we can turn this
back on.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
V4L2 API has been updated to remove the flags parameter from
v4l2_m2m_buf_copy_metadata in the 6.19 stable kernel release. Driver has
been updated to reflect these changes. Update SRCREV to pull these
changes.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rather than using shorthand variables for the guard, move to a longer
more explicit naming. This is mostly a cosmetic change, but we might
make a rule for it in the future so that we can check for it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
With the 6.18 we are moving to using an initramfs to provide non-default
modules for booting. So add that override to the machines that need it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It looks like we were modelling this initramfs off of the wrong example
from poky. This setup produces a much smaller initramfs.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Cleanup a few incorrect issues with the current file naming under the
config looping code.
1) Since binman is creating the tiboot3 files and signing them, when we
are trying to create the named version of the files, we do not want
to link against the spl/uboot-spl.bin file. We need to figure out
what the tiboot3.bin is pointing at and make this named version point
at the same thing.
2) When deploying the tiboot3 files, if we are deploying something that
is a link, then we should point the deployed link to the same named
target. This should help with figuring out what all of the links
actually point to from the build dir instead of running into .bin
file that has lost the audit trail.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
2025-10-24 10:52:17 -05:00
137 changed files with 738 additions and 571 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.
