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>
This change is needed due to the SGX driver, any distro, not just Arago,
using a TI SoC with SGX will need this fix, so it should go in meta-ti.
Signed-off-by: Andrew Davis <afd@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Convert devicetree prefix matching functionality into a generic
class that can be used by the kernel and wic images. That way
dynamically generated KERNEL_DEVICETREE list will be the same
when populating /boot dir of rootfs and/or FAT boot partition
of a wic image.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Automatically generate non-vendored DTBs list in DEVICETREE_FILES from
vendored KERNEL_DEVICETREE list for all platforms to use.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move KERNEL_DTBVENDORED settings from the kernel to ti-soc.inc
in the config scope.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update to PSSP release v6.5.0. This release is compatible to linux
v6.12 and other fixes for RP message size.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Minor comment changes, fix versions listed for some items.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
This was used when the DT_VENDOR_PREFIX was different between supported
BSP versions. All supported now use the new prefix so drop this var.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Remove support for the v6.1 TI and Beagle BSPs. This was originally
split into meta-ti-bsp and meta-beagle changes, but there are some
hidden interdependencies that made that more painful than needed.
Remove v6.1 support from both BSP layers here.
This includes packages specific to those BSPs:
- TI and BB.org v6.1 Linux kernel
- TI and BB.org 2023.04 U-Boot
- Rogue GPU driver 23.3 and Mesa 22.3.5
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
A recent change in bitbake requires that all variable assignments have
whitespace between the variable, the operator and the value.
FOO = "1"
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>
The legacy HS platforms (am335x-hs-evm, am437x-hs-evm, and
am57xx-hs-evm) are not using the new fitImage flow, but the kernels all
include the kernel.bbclass which disallows the old fitImage flow.
Copy in the last version of the kernel.bbclass and name it
kernel_legacyhs.bbclass, and update the machine configs to defined a
variable to use as the KERNEL_BASE_CLASS to inherit.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
- The S change needs to skip the APPEND-2 check since S should never
have a space in a path.
- The UBOOT_VERSION bbappend does not need a guard since we are
modifying our own layer.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
FIT signing was disabled in the past as it was interfering with multi
DTB usecase in binman, and it was thought that the binman signing being
done is equivalent to UBOOT_SIGN_ENABLE.
Though looking at the sources, UBOOT_SIGN_ENABLE is actually used to
sign the kernel FIT Image instead and the name UBOOT actually specifies
that it's used in tandom with U-boot. During the signing process, mkimage
from U-boot is used to pack the kernel FIT Image and along with that,
one DTB from U-boot is also passed to the mkimage command. The DTB that
gets passed gets the key embedded in it that is used to verify the
kernel FIT image at runtime.
Now this signed DTB is packed in U-boot by triggering a rebuild with
EXT_DTB argument in the U-boot build process. However, this failed as
there was a U-boot bug which was not looking at the packed sources
properly with the multi DTB usecase.
Now that a U-boot fix is available [0], revert that commit which
disabled the FIT signing.
This reverts commit 9656b79cb5.
[0]: https://lore.kernel.org/all/20250626-b4-upstream-fix-icssg-fit-v1-1-95eff1c853a4@ti.com/
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In order to turn the fitImage signing back on, we need to inherit the
ti-secdev class to setup all of the needed signing variables.
Remove the inherit ti-secdev from the kernel recipes since the fitImage
signing is handled in the ti-kernel-fitimage recipe and not in the
kernel recipes anymore.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The CICD flow needs to control the value for BRANCH in order to have the
recipe updated with the next SRCREV, but point to the CICD/next branch
for initial build/test.
With this split in linux-ti-staging-rt we cannot just have an override
for BRANCH in the local.conf because it trumps the new BRANCH_ARM32
system.
This patch creates an additional "default" variable BRANCH_ARM64 (or not
arm32), which can be controlled separately by the CICD flow. Then BRANCH
simply is picking between the two and so can be controlled by overrides
in the recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since the kernel branches could theoretically drift apart, we need to
track the PV of the kernel on the RT branch for the ARM32 platforms as
well.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While all ARM64 devices use the same branch for RT and non-RT builds,
the ARM32 devices have a separate branch for RT Kernel which is
"ti-rt-linux-6.12.y-arm32". Update the BRANCH and SRCREV for ARM32
devices for RT builds.
Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The U-Boot config fragment used to enable falcon mode was renamed from
'am62x_r5_falcon.config' to the more generic 'k3_r5_falcon.config' when
adapting upstream patches to ti-u-boot[1].
Therefore this patch fixes the same in meta-ti.
[1]: 90d2e960b4c at ti-u-boot-2025.01-next
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove no longer used snapshots of the kernel and kernel-fitimage
classes that were used for the old FIT image processing.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rename old snapshot of the kernel-uboot.bbclass to indicate it is
still being used by the FIT processing for the legacy HS devices.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Switch all kernel recipes and K3 based platforms to use the new
FIT image wrapper functionality.
Update FIT default DTB entry to not contain vendor dubdir, as it
is now handled through a conf prefix.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OE-Core provides default FIT image wrapper, but we need to extend it
with support for the dynamic devicetree prefix matching. While at it,
also use the correct kernel version from PKGV. Both of these use the
shared kernel sources tree, hence ensure it's available before any
processing.
Since old behavior was putting vendor subdir as a sanitized prefix
for each DTB entry as "ti_", U-boot expects corresponding config
entries to also contain the same - update conf prefix accordingly.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Handle devicetree prefix matching inside the shared kernel sources
tree, instead of ${S}. From the kernel recipe perspective, ${S} is
just a symlink to the shared kernel sources. But since the new FIT
image wrapper is a separate recipe now, it has its own different
${S}. To enable FIT image wrapper to support devicetree prefix
matching, it also needs to access the same shared kernel sources.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Beagle machines define both static KERNEL_DEVICETREE list and dynamic
KERNEL_DEVICETREE_PREFIX matching. But BB.org kernel recipes only use
the static list, while TI kernel recipes use dynamic prefix matching
by default.
Since devicetree lists now need to be used outside of the kernel
build, specifically for the new FIT processing wrapper, explicitly
unset KERNEL_DEVICETREE_PREFIX to disable dynamic devicetree prefix
matching, when BB.org BSPs are selected.
This way both kernel build and FIT image wrapper will have the same
list of DTBs to handle, based on the BSP selection.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This hides issues like missing flags that will cause issues for folks who
build or re-build the kernel outside the Yocto environment. It is better
to find these issues and fix them at the source in the Linux makefile,
not mask issues here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This file uses both spaces and tabs in different functions which
needs fixed at some point. For now at least make sure they are
consistent within the same function.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Looks to be left over from long ago, now completely unneeded.
Remove it and fix some comments while here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As ti-librpmsg-dma depends on ti-rpmsg-char, which is only compatible
with K3 platforms, ti-librpmsg-dma should also have the same limitations.
This resolves yocto-check-layer failure:
ERROR: Nothing PROVIDES 'ti-rpmsg-char' (but .../ti-librpmsg-dma_1.0.bb DEPENDS on or otherwise requires it)
ti-rpmsg-char was skipped: incompatible with machine qemux86-64 (not in COMPATIBLE_MACHINE)
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The gitpkgv class we are using to set UBOOT_VERSION is located in
meta-openembedded. We do not want to depend on meta-openembedded to
keep meta-ti-bsp as light as possible, and the naming of UBOOT_VERSION
is not a requirement, just a nice to have. Dynamic layers allow us to
use the class if it is available in the build, but not require it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We were waiting on a patch [1] to make it to master. Now that it has, move
to point the SRCREV to the latest commit.
[1] b1bca91e93
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This moves all of the platforms back to the main TFA repository, but
still points to the TI fork for the am62lxx platform while we continue
to work on upstreaming the needed patches.
With the the split into two repositories on two branches we need to also
split the LIC_FILES_CHECKSUM into two since the license.rst file is
slightly different between the two branches. The upstream master
version is newer than the current am62l version.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since all k3 and legacy platforms share common load addresses for kernel
and initrd in the fitImage, move them to top level ti-soc.inc.
No functional change is intended from this patch.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In yocto, the UBOOT_ENTRYPOINT and UBOOT_*LOADADDRESS variables specify
the entry point and load addresses for the kernel image and the DTB when
creating the fitImage[1].
Currently the load address for the kernel is set to 0x81000000 and
0x83000000 for the DTB for all k3 platforms.
However the region 0x80080000 to 0x81880000 is reserved for OPTEE on
am62xxsip-evm, leading to boot failure[2] when using the fitImage.
This patch fixes the issue by changing the addresses to 0x82000000 for
kernel and 0x88000000 for the DTB. This also allows us to load kernel
images > 32MiB in size when not using initrd while also making the
falcon and standard boot addresses consistent.
[1]:
https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_ENTRYPOINT
[2]:
https://raw.githubusercontent.com/ArchUsr64/ti_boot_logs/HEAD/am62xxsip-evm/failures/fitImage_load_addr_issue.log
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new kernel dtb for am62x SiP have been merged to ti-linux-kernel as
of f9579207b081 ("arm64: dts: ti: Add support for AM6254xxl SiP SK") on
ti-linux-6.12.y-cicd. This patch modifies FIT_CONF_DEFAULT_DTB to pick
the new dtb instead.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
CFG_TZDRAM_START in OPTEE defines it's load address and is used to
configure the page tables accordingly.
Due to 512MiB DDR limitation of am62x SiP, the memory map has been
modified with OP-TEE moved to bottom of DDR after atf to 0x80080000,
this requires modifications to the OPTEE's CFG_TZDRAM_START.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Due to 512MiB DDR limitation of am62x SiP, the memory map has been
modified with OP-TEE moved to bottom of DDR after atf to 0x80080000,
this requires modifications to ATF's BL32_BASE. PRELOADED_BL33_BASE has
also been updated to 0x82000000 to reflect the updated SPL_TEXT_BASE
from u-boot.
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As of 35df864a0c26 ("configs: add defconfigs for am6254xxl") in
ti-u-boot, new SiP sepcific defconfigs have been added with updated
memory maps and OP-TEE load address. This requires changing the
UBOOT_MACHINE variables inside machine configs for am62xxsip-evm.
Note that AM6254xxl is the OPN for am62x SiP and expands as follows:
AM6254XXL
||||
|||+-- Feature Lookup (L indicates 512MiB of integrated LPDDR4)
||+--- Clock Speed
|+---- Silicon PG Revision
+----- Core configuration (4 indicates A53's in Quad core config)
Signed-off-by: Anshul Dalal <anshuld@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for packaging AM64x PRU firmwares separately
Previously, AM64x platforms used the same PRU firmware binaries as
AM65x (the "am65x-sr2-*" files). This patch updates the recipes to
package dedicated AM64x PRU firmware binaries, ensuring that AM64x
devices use the correct firmware files.
The following changes are made:
- Add AM64x-specific firmware binaries to the TARGET lists in the
prueth-fw, pruhsr-fw, pruprp-fw, and prusw-fw recipes.
- Update COMPATIBLE_MACHINE in pruprp-fw to include "am64xx".
- Add new PRU PRP firmware binaries for AM64x, as AM64x now supports
PRP mode.
Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add TAD5212 DAC firmware images for am62dxx-evm to support two DAC
configurations:
- tad5212_01.bin: Configures 1 DAC with stereo channel in i2s mode.
- tad5212_04.bin: Configures 4 DAC with each having stereo channel
support in i2s mode.
Signed-off-by: Vishnu Singh <v-singh1@ti.com>
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Reviewed-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Previously, AM62d build reused AM62a's IPC firmwares. Now that
dedicated AM62d IPC firmwares are being pushed to ti-linux-firmware
repo, package the new IPC firmwares for echo test.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When specifying multiple git repos in the SRC_URI and you want the
"secondary" repositories to appear within the directory structure of the
primary repository, then we need to make sure that the destsuffix is
correct. With the change to calculating the value of S to use
BB_GIT_DEFAULT_DESTSUFFIX, we need to make sure that the destsuffix is
based on that variable as well.
Also, update the paths for S to be within new source location.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
If a recipe is fetching an entire git repo and then just building a
single dir, then we need to update S to lock into the sub directory.
Easiest fix is to simply append the subdir to whatever the system wants
to set S to by default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX
is set to match S from bitbake.conf (which itself is set to match typical tarball
releases).
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is no need to have two assignments; also setting S from
UNPACKDIR (and not vice versa) is more logical as unpack
task comes first, and tasks that come after unpack use S to access
unpack results.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The kernel class operates a little differently. The kernel is
downloaded and then moved to the "global" shared location and a symlink
is created to point to that location. Since we cannot set S =
"${WORKDIR}/git" anymore, just choose a new name under UNPACKDIR. The
value for BB_GIT_DEFAULT_DESTSUFFIX is the subdir name that is used by
default when fetching git repositories, so just use that name.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We would like to know the git commit for the build by looking at the
filenames of u-boot files. Include the value for PKGV in the names of
the files instead of PV.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all layers with the new Yocto release, fixing the current build
error:
ERROR: Layer meta-ti-bsp is not compatible with the core layer which
only supports these series: whinlatter (layer is compatible with styhead
walnascar)
Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are seeing an error related to a check from oe-core wanting to make
sure that a package does not RDEPEND on a debug package.
ERROR: linux-bb.org-6.12.22+git-r0 do_package_qa: QA Issue: kernel-modules rdepends on kernel-module-g-dbgp-6.12.22-ti [debug-deps]
A bug has been filed:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15901
In the meantime, add debug-deps to the INSANE_SKIP list.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A recent set of changes on oe-core has dramatically revamped the
fitimage generation code. It is initially unclear how to fold those
change into our flow, so in the short term we will copy the previous
versions of the kernel bbclass files from a commit before [1] any
changes to the class files.
As soon as we figure it out, these files will be removed. This just
help unblock anyone trying to build on master including meta-ti-bsp.
[1] https://git.openembedded.org/openembedded-core/commit/?id=fdb0a51598156f99aa91f7495d7eada92a459e97
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Package k3-am62a7-sk-edgeai.dtso for am62dxx-evm image. This overlay is
required for audio analytics for am62dxx-evm.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
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>
Mark corresponding arrays with nonstring attribute to suppress the new
gcc-15 warning -Wunterminated-string-initialization that becomes an
error due to the global -Werror.
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>
* 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>
OE-core updated mesa to 25.0.2 [1]. The resulting mesa.inc file no
longer matches mesa recipes building older versions.
Copy the mesa.inc version from before the update renamed to
mesa-pvr.inc to work around the issue.
| ../git/meson.build:21:0: ERROR: Value "softpipe" for option "gallium-drivers" is not in allowed choices: "auto, kmsro, radeonsi, r300, r600, nouveau, freedreno, swrast, v3d, vc4, etnaviv, tegra, i915, svga, virgl, panfrost, iris, lima, zink, d3d12, asahi, crocus, pvr, sgx, all"
[1] https://git.openembedded.org/openembedded-core/commit/?id=f9eb0468e45ee5a6a3b3195ef5e78c328c4347c9
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
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>
meta-arm adds a patch that was sent and accepted upstream, remove
it since mta-ti pulls a more recent verstion.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.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>
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>
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>
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>
This reverts commit eeb68bcae3.
This patch was accepted to the ti-u-boot repo, so this patch is no
longer needed.
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>
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>
A recent patch to ti-u-boot 2025.01 introduces a compile error on
master for am64xx-evm. A patch has been sent to the mailing list
that fixes this, but it will take time before we will see that patch
available to us on master. So we need to carry the patch here.
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>
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 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>
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>
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 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>
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>
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>
As the patch that added these states, this is an ugly hack, the issues
involved are fixed and no longer relevant, remove this.
Signed-off-by: Andrew Davis <afd@ti.com>
We use the makefile shipped with the firmware to deploy the firmware
instead of just manually moving it in the install step. But the makefile
doesn't do the right thing, so we also modify the makefile. Skip all
this and just move the firmware ourselves.
Signed-off-by: Andrew Davis <afd@ti.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>
# Verify that the above loop found a initramfs, fail otherwise
[ -f ${B}/usr/${INITRAMFS_IMAGE_NAME}.cpio ] && echo "Finished copy of initramfs into ./usr" || die "Could not find any ${INITRAMFS_DEPLOY_DIR_IMAGE}/${INITRAMFS_IMAGE_NAME}.cpio{.gz|.lz4|.lzo|.lzma|.xz|.zst) for bundling; INITRAMFS_IMAGE_NAME might be wrong."
}
do_bundle_initramfs () {
if [ ! -z "${INITRAMFS_IMAGE}" -a x"${INITRAMFS_IMAGE_BUNDLE}" = x1 ]; then
echo "Creating a kernel image with a bundled initramfs..."
copy_initramfs
# Backing up kernel image relies on its type(regular file or symbolic link)
tmp_path=""
for imageType in ${KERNEL_IMAGETYPE_FOR_MAKE} ; do
# Must be ran no earlier than after do_kernel_checkout or else Makefile won't be in ${S}/Makefile
do_kernel_version_sanity_check() {
if [ "x${KERNEL_VERSION_SANITY_SKIP}" = "x1" ]; then
exit 0
fi
# The Makefile determines the kernel version shown at runtime
# Don't use KERNEL_VERSION because the headers it grabs the version from aren't generated until do_compile
VERSION=$(grep "^VERSION =" ${S}/Makefile | sed s/.*=\ *//)
PATCHLEVEL=$(grep "^PATCHLEVEL =" ${S}/Makefile | sed s/.*=\ *//)
SUBLEVEL=$(grep "^SUBLEVEL =" ${S}/Makefile | sed s/.*=\ *//)
EXTRAVERSION=$(grep "^EXTRAVERSION =" ${S}/Makefile | sed s/.*=\ *//)
# Build a string for regex and a plain version string
reg="^${VERSION}\.${PATCHLEVEL}"
vers="${VERSION}.${PATCHLEVEL}"
if [ -n "${SUBLEVEL}" ]; then
# Ignoring a SUBLEVEL of zero is fine
if [ "${SUBLEVEL}" = "0" ]; then
reg="${reg}(\.${SUBLEVEL})?"
else
reg="${reg}\.${SUBLEVEL}"
vers="${vers}.${SUBLEVEL}"
fi
fi
vers="${vers}${EXTRAVERSION}"
reg="${reg}${EXTRAVERSION}"
if [ -z `echo ${PV} | grep -E "${reg}"` ]; then
bbfatal "Package Version (${PV}) does not match of kernel being built (${vers}). Please update the PV variable to match the kernel source or set KERNEL_VERSION_SANITY_SKIP=\"1\" in your recipe."
fi
exit 0
}
addtask shared_workdir after do_compile before do_compile_kernelmodules
if bb.utils.vercmp_string(kernel_version, oldest_kernel) < 0:
bb.warn('%s: OLDEST_KERNEL is "%s" but the version of the kernel you are building is "%s" - therefore %s as built may not be compatible with this kernel. Either set OLDEST_KERNEL to an older version, or build a newer kernel.' % (d.getVar('PN'), oldest_kernel, kernel_version, tclibc))
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.
