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>
This makes the final changes needed to bring falcon support to
am62xx-evm builds using a single bitbake call.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since we are going to be effectively duplicating most of the what k3r5
does for the k3r5-falcon builds, we need to have the same settings. But
we cannot just include the am62xx-evm-k3r5.conf as a starting point
since it sets somethings we do not want.
Solution is to pull all of the common settings out into an include files
and just include it in both flows.
This commit just does this for the existing k3r5 build so that the
upcoming k3r5-falcon change can use it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The two changes related to falcon for u-boot are building a tifalcon.bin
file in the a53 build, and applying a config fragment for the r5 builds.
To make sure we avoid releasing the same files as the non-falcon builds
we need to uniquely name all of the files produced by the r5 build, and
prune down the files for a53 builds.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since nothing in ti-dm-fw changes for the falcon flow, we do not want to
deploy the same files and trigger an error.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since nothing in optee changes for the falcon flow, we do not want to
deploy the same files and trigger an error.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We need to specify different memory locations for TFA and also uniquely
name the deployed files to avoid collision with the main versions of the
bootloaders.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We need to copy the same settings that the k3r5 overrides have so that
the k3r5-falcons build shave the same settings.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since the requirements for building with falcon support involve building
some of the same software packages with different options, we are trying
out doing this via Yocto multiconfigs. This will allow us to build
everything in one bitbake run rather than as different MACHINE= targets.
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>
Part of the testing for TI is to build alternative versions of uboot
that turn on/off certain features. The decision was made to host these
config fragments in the ti-upstream repository so that they are outside
of the tree, but centrally located for all version of u-boot to access.
This patch adds the logic to enable this feature by adding this to the
local.conf:
TI_EXTRAS += "tie-test-builds"
This makes use of the existing UBOOT_CONFIG flow for looping over uboot
and building it multiple times and naming the output files uniquely.
Additionally, we want to provide examples of 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 to point to it.
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>
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>
This package provides Linux-side components for TI IPC and depends on
virtual/kernel Linux kernel for the build, so it is not compatible with
non-Linux builds, such as k3r5 baremetal multiconfig. Hence adjust
COMPATIBLE_HOST accordingly.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
This IPC example is no longer supported nor recommended for new designs.
The documentation is no not available either (was on Processors Wiki).
Remove this example.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a SECURITY file with hints for security researchers and other
parties who might report potential security vulnerabilities.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel
6.6 and the same version of mesa rogue is using.
Enable SGX by default in the 6.6 BSP provider section logic.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to commit 58b25570c9ef91753b14c2103f45f4be9dddb696, which adds
the DM_MANAGED suspend feature.
58b25570c9
Also change the docs/license.rst checksum. The license file was
modified to include a reference to the pydevicetree project which uses
the Apache License 2.0.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The mesa.inc that we inherit from oe-core now has the required
parameters. This conditional append is no longer required.
This reverts commit dbc6afc46e.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
PREFERRED_VERSION matches against the PV in the recipe, not against the
file name. With the upcoming 6.12, the 6.1 kernel version string was a
little too loose. The "6.1%" could glob onto the 6.12 recipe. Take
this time to also clean up a couple of the other versions and narrow
them down.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add bsp-ti-6_12 overrides in A53 & R5 machine configuration
to ensure it picks the appropriate u-boot configs for beagleplay
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are planning on adding upstream u-boot testing against stable tagged
versions of u-boot and need a little more control over telling bitbake to
not point at a branch but point to a tag.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest u-boot release v2024.10.
Additionally, take this time to clean up the mainline recipe and
streamline it a bit.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Our upstream testing needs to point to both master and master-next and
we need two different recipes to track that. This recipe mirrors the
linux-ti-next recipe and points to the master-next branch for the latest
bleeding edge changes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It was suggested to move the reproducibility patches out of
ti-kernel.inc and into the respective recipes.
Taking this time to also rework all of the pieces that go into the SRC_URI
and create a standardization for how all of the kernel recipes are done.
Create KERNEL_GIT_URI, KERNEL_GIT_PROTOCOL, KERNEL_GIT_BRANCH,
KERNEL_DEFCONFIG, and KERNEL_REPRODUCIBILITY_PATCHES. The default for
the above new variables is to the git.ti.com repository and how we manage
the kernel settings. The other kernel recipes that do something other than
how TI does it can simply override the variables.
This change will make it easier to perform the upstream testing that we
do on a nightly basis. Additionally, it will simplify the auto generation
of the patches to move the mainline (stable kernel) recipes since the
required patches will be all done in the same recipe.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Resolve some issues with J721E and compressed NPOT (Non-Power-Of-Two)
textures.
Also, add some additional allocation tracking in render process specific
tasks.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We got a bit more time to do a proper migration this time. A discovery
period to see what actually works and boy, it wasn't much.
This update resolves issues with:
- Macro redefinition
- Sparse NPOT texture allocations
- vec4 reductions
- Mesa image extensions
- Buffer allocations under weston
- Devices with both a RENDER and PRIMARY display node
- Underprivileged users being unable to allocate buffers
- Removed call to drm_map_legacy
- Replace deprecated kernel calls
- Fix some cache attributes for userspace allocations
- About 40 other various errors and warnings
This core was never fully GLES2 conformant. In fact, if you try to run
cts on any of the older releases you'll find yourself in a hardware
recovery loop pretty quickly. We've gotten it to about 94.2% conformance
with these patches.
There are still dragons here, but they are at least a little more
manageable.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The next Yocto Project release is called walnascar and OE-Core master branch
is now marked accordingly. Add layer compatibility with walnascar.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We were missing controlling the versions for linux-ti-staging-rt and
linux-ti-staging-systest using the BSP framework. Since the
PREFERRED_VERSION is not tied to the virtual/kernel we need two
additional settings for those alternate kernel package names.
For BSPs that do not have the -rt and -systest recipes then the two
new variable settings should effectively be ignored and cause no issues.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There was a change to the return value for a function pointer in the
kernel v6.11. This patch adapts the module to the kernel change.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adding needed recipe for initial testing and development of the 2024.10
version of u-boot for the next LTS.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This will prevent a lot of noise on the build logs.
Currently we have some erros:
rm: cannot remove 'file'
No such file or directory
Like the following:
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5 /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5-2024.04+git-r0*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-initial-env-am64xx-evm-k3r5-2024.04+git-r0*'
| : No such file or directory
| + true
| + rm /lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0*
| rm: cannot remove '/lmp/build/tmp-lmp-k3r5/work/am64xx_evm_k3r5-lmp-eabi/u-boot-ti-staging/2024.04+git/deploy-u-boot-ti-staging/u-boot-ti-staging-initial-env-am64xx-evm-k3r5-2024.04+git-r0*'
| : No such file or directory
| + true
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The upcoming SRCREV change to the linux-ti 6.6 kernel version no longer
needs these two patches, and they are blocking the CICD promotion being
in place.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Last user was dspdce-fw which is removed. Remove this now unused
support library.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was an attempt to run the DCE server firmware on the DSP instead
of on the IPU M4 cores. Not widely used and not used at all anymore,
remove the firmware for this.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
CMEM has been deprecated for removal for some time now. All users should
have migrated to the Linux upstream DMA-BUF Heaps framework. Remove CMEM.
We have already removed the CMEM kernel module but left the CMEM userspace
recipe to prevent breaking meta-arago builds which had some leftover
packages that still had a dependency on it. Nothing we now build still
needs this now so drop it out also.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove openmp-rtos component as deprecated and not maintained.
This used to provide OpenMP DSP runtime components for legacy devices.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
openembedded-core commit f5cfb3e23603 ("mesa: set PV from the .inc
file and not via filenames") now sets PV in the mesa.inc file
explicitely to whatever version oe-core is using.
Override that setting to the actual version here to prevent the
following parse error and whatever else would go wrong afterwards.
| ERROR: .../mesa-pvr_23.2.1.bb: Unable to get checksum for mesa-pvr SRC_URI entry 0001-meson-Disable-cmake-dependency-detector-for-llvm.patch: file could not be found
| The following paths were searched:
| .../meta-ti-bsp/recipes-graphics/mesa/mesa-pvr-24.0.7/bsp-ti-6_1/0001-meson-Disable-cmake-dependency-detector-for-llvm.patch
| ...
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
omapzoom has been down since a long time. Point the repository to the
mirror in git.ti.com
Reported-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A compile error has apperaed when building againt the v6.10 kernel.
git/debugss_module/debugss-mod/debugss_kmodule.c:1149:34: error: array type has incomplete element type 'struct of_device_id'
1149 | static const struct of_device_id dra7xx_debugss_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~
The easy fix is just to add an include for the header that defines the
missing struct.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The gdbc6x debugger might be able to be updated for the reproducible
build effort. While we continue to explore what is possible, we will
disable the check so that we can continue to maintain our code for
releases.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt6x compiler is a custom TI compiler for the TI C6000
Digital Signal Processor(DSP) platform. It does not currently
support reproducible builds and is provided via a binary blob
download that we cannot patch in the recipe to address the
issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt6x compiler is a custom TI compiler for the TI C6000
Digital Signal Processor(DSP) platform. It does not currently
support reproducible builds and is provided via a binary blob
download that we cannot patch in the recipe to address the
issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-cgt6x compiler is a custom TI compiler for the TI C6000
Digital Signal Processor(DSP) platform. It does not currently
support reproducible builds and is provided via a binary blob
download that we cannot patch in the recipe to address the
issue.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add ti-img-rogue-driver as the preferred provider and enable the gpu
driver in the image.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j742s2 has the same GPU as j784s4. Add j742s2 support to the recipes.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Installer log contains absolute paths and is not really needed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fix warning that S does not exist, since it defaults to ${WORKDIR}/${BP}
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to pick up some patches that adjust the way heaps are
sized. This solves issues seen when utilizing page sizes greater
than 4K.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Applying the patches to all kernels is not going to work. Each kernel
might need different patches to address reproducibility issues.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Testing shows that the SRC_URI += does not work for adding the new
patches. += takes place during parsing, we want :append instead to make
sure that no matter what SRC_URI is in the various kernel recipes, that
we we append the patches to the end.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Referring to the TI specific kernel header file via -I${UNPACKDIR}
causes a "buildpaths" QA error. Solution is to tell gcc to map the host
directory to a target directory using -fdebug-prefix-map
Suggested-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adding this sanity check here preemptively. Since these libraries were
compiled with an older version of GCC than what is currently in use on
scarthgap and master they won't trip the sanity check just yet, but if
someone attempts to update them and uses a newer compiler (for some
reason) it will trigger the sanity checks again.
This also keeps the DDK 23.3 and 24.1 recipe diff to a minimum.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add ldflags to INSANE_SKIP for the libopencl-rogue-tools package. For
some reason I didn't catch this sooner, but this falls victim to the
same issues the parent package faced earlier this year.
Just enough options enabled that Yocto wants to do a ldflags check, but
the DDK will not be able to utilize all the build flags Yocto uses.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
- Update SRCREV for jailhouse which incorporates makefile changes for
scarthgap.
- To handle ${ARAGO_IMAGE_SUFFIX}, add * wherever JH_RAMFS_IMAGE is used in
do_install (install or copy) so to pick correct inmate image for RT build.
- Skip QA checks for usrmerge and buildpath. This is required to package
jailhouse in image.
- Update FILES:${PN}.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update u-boot/ti-extras.inc to 2024.04 version.
Update linux/ti-extras-rt.inc to 6.6 version.
Update linux/ti-extras.inc to version 6.6.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The config fragment "am62x_r5_usbdfu.config" is applicable to AM62x,
AM62x-SIP, AM62x-LP-EVM, AM62Ax and AM62Px devices and enables USB DFU boot
support at the R5 stage of boot.
Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
J721E SK, AM68 SK and AM69 SK have similar connectivity
for CSI2 RPi connector and the same overlays can be reused,
thus pick the J721E SK CSI2 IMX219, fusion overlay and
AM68 SK V3Link fusion overlay for AM69 SK also.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
J721E SK and AM68 SK have similar connectivity for CSI2 RPi
connector and the same overlays can be reused, thus pick the
J721E SK CSI2 IMX219 and fusion overlays for AM68 SK also.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
J784S4 and J721S2 EVM has similar connectivity for MIPI CSI2
connector and the same overlays can be reused, thus pick the
J721S2 CSI2 OV5640 and J721S2 EVM fusion overlays for J784S4.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Reset this back to the proper branches for kernel 6.1 since this recipe
is only being used in 6.6 bsp providers.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Download and install the cc33xx firmware and binaries
to be used with the cc33xx drivers.
FW Version: 1.7.0.120
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
cc33calibrator is a tool provided by TI to manually control the
radio frontend of the cc33xx device. This tool can also be used
for production line testing of the radio.
Documentation for this tool is provided within the following link:
https://www.ti.com/tool/CC33XX-SOFTWARE
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
cc33conf is a tool provided by TI to configure
cc33xx WLAN devices. It can be used to change
the RF parameters and other features of the target.
Documentation for this tool is provided within the following link:
https://www.ti.com/tool/CC33XX-SOFTWARE
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Share the most commonality between the recipes, except:
* SRC_URI torvalds vs. linux-next
* SRCREV and PV
* Device Tree list vs. DT prefix
* SUMMARY
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The use of external metadata file to control RTOS binary firmware
integration has been deprecated some time ago. Remove it now.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
For our upstream testing flow we have the need to have a "next" BSP for
configuring various settings based on building the latest kernel/uboot.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as next BSP does not support all combinations
of SR1.0, HS-FS and HS-SE variants.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations
of SR1.0, SR2.0, HS-FS and HS-SE variants.
Suggested-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update am62xxsip-evm machine configuration to support
TI kernel 6.1 & ti-u-boot-2023.04
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As of commit [1] there will be a separate defconfig to build u-boot for
j721e-evm and j721e-sk.
Hence, introduce new yocto machine configs for j721e-sk.
[1]: c9507f07a1
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
MACHINE_KERNEL_PR is a remnant of the early OE days and hasn't been
needed for quite some time. Let's finally remove it completely.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
BeaglePlay gains official support from latest TI lts-6.6 baseline, so set
it as the default. Other Beagle platforms will still use BB.org as default.
And these defaults can still be changed with TI_PREFERRED_BSP setting in a
distro config or by end user in the local.conf
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all Beagle platform configurations to support multiple BSPs.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations
of SR1.1, SR2.0, HS-FS and HS-SE variants.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This adds a facility to define multiple supported BSPs with their own
preferences for individual components, as well as lets machine configs
specify conditional configurations for different BSPs.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to pick up some new binaries for AM62P. The allocation
patch for Chromium was not included for this device previously.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In order to be able to switch between different kernel providers, as well
as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize
Device Tree lists as follows:
* Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org
recipe for now, to be used when building beagleboard.org baseline
* Update KERNEL_DEVICETREE in the machine configs to only list what already
exists in the upstream/mainline kernel
* Update KERNEL_DEVICETREE_PREFIX to match the list when building TI baseline
With this change it is now very easy to switch the kernel between providers
supported by meta-ti - linux-ti-mainline, linux-ti-staging and linux-bb.org
Please note that 6.6 LTS has moved to "vendored" device tree layout even for
32-bit platforms, while BB.org still uses 6.1 LTS and flat DT layout.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lift the common parts of the top level gitignore from oe-core and
meta-openembedded. This masks out temporary python files, intermediate
artifacts, and unclean patch leftovers (.orig, .rej, etc).
We're choosing to leave patches at the root of the project out of this
as maintainer preference.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As of commit [1] there will be a separate defconfig to build u-boot
for j721s2-evm and am68-sk.
Hence, introduce new yocto machine configs for am68-sk. This is done
through a new am68.inc file as the am68-sk platform does not support GP.
So j721s2-evm.inc is copied to am68.inc and updated accordingly.
[1]: a96be9b8c0
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A newly enabled check in master is causing errors with this package:
ERROR: QA Issue: Architecture did not match (ARM, expected x86-64)
Adding arch to the INSANE_SKIP variable disables that check for this
recipe.
Suggested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
One of the changes in gcc v14 is making implicit-function-declaration an
error. For some older software packages the easiest fix is to add
-fpermissive to the compile line.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to pick up rebuilt binaries. Upstream release notes:
Regenerate all binaries with a fix for exportable buffer allocations
that should improve Chromium compatibility.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms
* Update DTB/DTBO lists to include latest renames and additions
* Re-enable vendored DTB layout by default
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all of the optee components to the upstream 4.2.0 version.
While at it, remove the patches and fixups which are not needed anymore.
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that are past the inital stages of our LTS migration, we can remove
the DEFAULT_PREFERENCE settings that prevented these recipes from being
the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While we are working to finish our kernel migration 6.6, we are falling
aback to software rendering for platforms that do not currently have a
solution for GPU drivers (namely the boards that use SGX).
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This has been accepted to oe-core and is available in scarthgap and newer.
This reverts commit e9a56223ed.
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: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
This branch does not currently contain SGX patches so it is also being
masked by the ltsprep branding to prevent regressing those devices
currently.
Please note that may run into sstate errors when switching to or away
from the ltsprep tag. Please issue a clean to mesa and
ti-img-rogue-umlibs if you get warnings from either package's
do_create_runtime_spdx step.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Locally overlay verbatim copies of mesa 22.3.5 patches from
oe-core/master, so we get whatever QoL patches from core relevant to the
current release.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Recipes for DDK 24.1, but lock them behind ltsprep tags because they
require device tree changes that do not work on the current default
kernel for this layer.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Reusing the j784s4.inc file presents problems as the am69-sk platform
does not support GP. So copy the j784s4.inc to am69.inc and update
accordingly.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently, the 6.1 kernel is the default. Removing the k3-am69-sk dtb
file only applies to the 6.6 kernel. Restoring this entry so that
current builds work until such time as the 6.1 kernel is removed from
the recipes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream driver expects Wave5 firmware to be named "wave521c_k3_codec_fw.bin".
Driver probe fails because this compatible isn't being found.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Separate FAT boot partition holds SPL, SYSFW and U-boot images, while
rootfs places kernel images and DTBs into /boot directory. So it is not
desirable to mount boot FAT partition into /boot directory of the rootfs
and shadow its original content - adjust corresponding entry in wic
templates.
While at it, remove unused ondisk parameter when using use-uuid, which
takes precedence and is more flexible.
Note: boot FAT partition will be automounted at /run/media/boot-mmcblk0p1/
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Jonathan Cormier <jcormier@criticallink.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new kernel directory stucture for the DTBs is causing problems when
assembing the image files. It produces errors like this:
output: install: cannot stat 'deploy-ti/images/XXXX-evm/omap/XXXX.dtb': No such file or directory
or
output: install: cannot stat 'deploy-ti/images/XXXX-evm/ti/omap/XXXX.dtb': No such file or directory
The issue comes from the UBOOT_EXTLINUX_BOOT_FILES list. am57 already
had a mechanism but it was missing the omap/ dir to remove, and am33 and
am43 were just takeing KERNEL_DEVICETREE directly. This patch fixes
both cases.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We missed that the KERNEL_DEVICETREE should have been updated for the
32bit platforms with the change in linux-ti-mainline to v6.6. The new
directory structure under arch/arm/boot/dts is in effect for that
version.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This upgrade contains the following changes:
* updated hostapd path in ap_start.sh
* ap_stop.sh removes wlan1 interface
* hostapd.conf updated to work seamlessly with hostapd 2.10
Signed-off-by: Sabeeh Khan <sabeeh-khan@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It is useful to have U-boot initial environment deployed for future
reference or to initialize environment files as part of the build.
In multiconfig setup, such as TI K3 platforms, building U-boot
multiple times for Cortex-R5 and Cortex-A53 cores results in file
conflicts when deploying under the same name. To avoid that, those
initial-env files were removed at the end of the do_deploy task.
But it is better to only remove them for k3r5 multiconfig, since
that only builds SPL and saved env doesn't make much sense, but
preserve and deploy initial-env for the main machine multiconfig.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In an attempt to try and better support non-LTS branches, we need to do
a better job at not removing temporary patches too soon from master.
This TODO file should allow us to better schedule the time when the
patches can be safely removed.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add recipe for yamllint. There is an upcoming change in u-boot where
the binman tool is now configured to call yamllint to verify the configs
during compile time.
There was a previous patch a year ago from Trevor Woerner that never
made it into oe-core. This patch is a reworking of his patch but
pointing to a newer version.
We are waiting on this patch to be accepted in oe-core. Once it is
available on master we will remove this recipe to avoid conflict.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Our CICD script inadvertently added the SRCPV back into the recipes.
The script has been fixed, so removing the variable once again.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
New features added require another increase to max_leb_cnt.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Set the KERNEL_DEVICETREE_PREFIX so that, when using the various TI
kernel recipes, the "correct" DTB files are pulled in depending on what
is available in that kernel source.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
am69 and am68 sk boards supports V3Link cameras interfaced via V3Link
camera fusion board. Refer to
commit b7a97b1b (conf: machine: am62axx: Pick overlays for V3Link cameras)
for details
Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Acked-by: Jai Luthra <j-luthra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j722s-evm supports capture from fpdlink cams via fpdlink fusion1 board
or V3Link camera fusion board. So package fpdlink camera overlays
Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Like the current TI-RTOS/MCU+ firmware, this is a prebuilt example
firmware for TI K3 remote cores. It is an alternative to the echo test
demo currently provided by "ti-rtos-firmware" recipe. In addition to
supporting rpmsg_client_sample just as the current firmware does, it
also provides:
* A serial console with shell on the MCU UART port
* A console over RPMSG at /dev/ttyRPMSG0
* Example usage of the MCU GPIO/I2C/SPI from this shell
* And many other Zephyr default enabled features..
It does all this using the Zephyr RTOS, a scalable real-time operating
system, optimized for resource constrained devices, and built with
security in mind. Zephyr is a Linux Foundation project. For more
info see here[0][1].
Zephyr firmware like this can also be built as part of the Yocto build
using meta-zephyr. Although this is a prebuilt currently, we intend
to build this from source to reduce meta-ti's dependence on firmware
blobs.
This currently works with the AM62 M4F. Support for additional SoCs
and cores is in progress.
[0] https://www.zephyrproject.org/
[1] https://docs.zephyrproject.org/latest/introduction/index.html
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update SRCREV for jailhouse recipe which will add changes for Out of Box
demo and also a new application to test whether the linux inmate cell has
crashed or not.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Latest ti-u-boot will be supporting HSSE1.0 and HSFS1.0 versions of the
j7200 soc through the binman dts nodes. Add support in yocto to package
the created binaries in the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Latest ti-u-boot will be supporting HSSE2.0 and HSFS1.1 versions of the
j721e soc through the binman dts nodes. Add support in yocto to package
the created binaries in the wic images.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We have a request to be able to override the beagle kernel set in
PREFERRED_PROVIDER_virtual/kernel, but it is being absolutely set and
not loosely set with ?=. Take this time to create a central include for
all beagle boards like we have for the k3.inc.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This firmware is named so that the correct firmware is chosen on each
machine. No need to split this package for each machine, combine them
into one non-machine-specific package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The firmware for different machines and versions are named differently so
there is no need to have machine specific packages for each of these
firmwares. Move all the PRU-Switch firmwares into single package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The firmware for different machines and versions are named differently so
there is no need to have machine specific packages for each of these
firmwares. Move all the PRU-HSR firmwares into single package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The firmware for different machines and versions are named differently so
there is no need to have machine specific packages for each of these
firmwares. Move all the PRU-ETH firmwares into single package.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Most firmware does not run on the host and is therefor not architecture
specific, at least as far as the package manager is concerned. Although
the firmware might not be useful on some machines, the package itself
is not machine specific. Remove PACKAGE_ARCH.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update from 0.6.4 to 0.6.6.
This update brings the following fixes from ti-rpmsg-char repo.
55a6f40 remove ti.ipc4.ping-pong reference
8892e57 lib: fix data type build warnings
7c2ab48 lib: fix build warnings
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The new V3Link camera fusion board [1] comes with a CSI to FPDLink
serializer board, which allows interfacing multiple 22-pin FFC
compatible sensors with SK-AM62A.
Currently overlays for interfacing IMX219 sensor with V3Link are built
as part of the TI linux kernel, so pick these in the BSP filesystem.
[1]: https://www.arducam.com/fpd-link-3-cameras/
Signed-off-by: Jai Luthra <j-luthra@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Stop using UBOOT_LOCALVERSION, and copy what is done in the kernel recipe. This
allows us to set the correct SHA into the version string even if AUTOREV is used
since SRCPV is no longer set in oe-core.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The use of KERNEL_LOCALVERSION for controlling the kernel version has
changed recently. Placing the value of KERNEL_LOCALVERSION in
.scmversion was causing it to duplicate the string in the final version.
Instead, drop KERNEL_LOCALVERSION to just identify that it comes from
TI, and that it is an RT kernel. Additionally, place the commit sha for
the kernel into the .scmversion file explicitly to be both backward and
forward compatible.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch moves the jailhouse recipe general variables to a
ti-jailhouse.inc file along with fetch and compile task.
Jailhouse repo also contains some demo applications which can
be packaged alone in filesytem and does not require packaging
jailhouse module, firmware and tool.
So add a new recipe jailhouse-inmate which can be used to only
package those demos. The existing jailhouse recipe will contain
variables and other dependencies needed for do_install task for
jailhouse module, tools, demos etc. The do_install of jailhouse
inmate recipe will only package demo applications.
This new recipe(jailhouse-inmate) will be added to a new image
in meta-arago. The new image will be used for jailhouse second
linux instance or cell.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update linux-bb.org to 6.1.69 for both 32 and 64 bit platforms
* Update u-boot-bb.org to the latest 2023.04 based on SDK 9.1 release
* Update DTB/DTBO lists to include latest renames and additions
Note: all changes are in a single commit for bisectability
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream now includes all DTB/DTBO files recursively, no need to extend
corresponding FILES list.
Revert "linux-bb.org: also package DT overlays in separate dir"
This reverts commit f22ea63f66.
Note: adjust SRC_URI cosmetically, so it now matches kirkstone
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The current master has the support for power off functionality, update
to that.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update all OP-TEE components to 4.1 tag. OP-TEE examples are already in
4.1 tag.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Switch the branches to the new LTS names. These are still experimental,
hence the isolation from kirkstone.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The "upstream" is not maintained, but this is an easy patch to get this
working again. Still need to watch this for big breakages and rethink
supporting this recipe at that time.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add TI logo image as bootsplash image file for AM62P and install it in
boot directory from where u-boot can read from and display during
boot-up time.
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Acked-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In preperation of LTS migration, switching from 2024.01 to 2024.04 for
u-boot as this is close to what will be the final version for LTS.
Default preference is still kept as low for this version since we are in
early migration phase.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Migrate to version 23.3.6512818, this includes the stability updates
released in 23.2 as well as some additional modifications to help with
userspace application support, namely Chromium.
We're also dropping the x11 window system extensions from the Vulkan
libraries for now. Ideally, both x11 and wayland extensions will be
provided by mesa's vulkan-wsi-layer in the future, but currently x11
isn't supported and this just added extra complexity to the package in
Yocto.
Signed-off-by: Randolph Sapp <rs@ti.com>
Tested-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to include some useful patches that:
- Fix the ROGUE segfault issue introduced by SGX (this was what
the old conditional logic was addressing)
- Fix destruction of event queue with proxies still attached
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
If Yocto even sees a "-dev" package in the PACKAGES string it will
automatically forward all dev-so links to that package. Remove that
entry from the PACKAGES string so we get the required links again.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for ti-extras for am62xx-lp to control the kernel and u-boot
repos, branches, and srcrevs via the TI_EXTRAS variable in the local.conf
file.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that 2024.01 is official, the logo that am62xx-evm installs is
available in all versions of the repo that we point to. Move all of
that code out of the .bb files and into the u-boot-ti.inc file.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include the following changes in UM and KM:
- Rebuild all releases with external memory wrap disabled due to
some incompatibility with certain Qt use cases.
- Add a watchdog change that prevents an occasional false
timeout when servicing long DM processes.
- Rely on snooping to perform certain cache operations and
results in decreased overhead for device -> cpu
communications.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A patch has been accepted in mainline u-boot that has binman calling
yamllint to verify the configs during compile. This means that the
yamllint must be available as a tool at the time.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add recipe for yamllint. There is an upcoming change in u-boot where
the binman tool is now configured to call yamllint to verify the configs
during compile time.
There was a previous patch a year ago from Trevor Woerner that never
made it into oe-core. This patch is a reworking of his patch but
pointing to a newer version.
We are waiting on this patch to be accepted in oe-core. Once it is
available on master we will remove this recipe to avoid conflict.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
j722s is same GPU as am62p, need to add this into machine definition so
that Rogue driver gets included in the image.
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fetch from the latest commit which has J722S support now.
Signed-off-by: Apurva Nandan <a-nandan@ti.com>
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove config files from /usr/share/jailhouse as they are not required.
Package only the cell files for respective devices and not all k3 files.
Update FILES:PN to use wildcard.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
RPM does not accept '-' as a character in the PR/version and fails with:
| error: line 4: Illegal char '-' (0x2d) in: Release: sgxrgx-54fd9d7dea098b6f11c2a244b0c6763dc8c5690c.1
The correct approach is to reference SRCPV and not SRCREV and also add it
to PV and not PR. But PV is used in the branch to fetch the sources and
cannot be modified, so use SRCPV in PR w/o any illegal characters.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
With the current implemetation is not possible to remove the '-k3r5'
customization using overrides like below and the '-k3r5' always stay there.
| TMPDIR:remove:k3r5 = "-k3r5"
| or
| TMPDIR:k3r5 = "${TOPDIR}/tmp"
This patch allows to build the core-image-minimal in oe-core master/nanbield
without any issue on a common TMPDIR folder just using the following:
| TI_COMMON_DEPLOY = "${DEPLOY_DIR}"
| TI_TMPDIR_APPEND = ""
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are preparing to migrate our uboot version to 2024.01. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this uboot in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
2023.04 uboot and make this the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are preparing to migrate our kernel version to 6.6. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this kernel in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
6.1 kernel and make this the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the BB.org kernel to the latest. Also update BeaglePlay device
tree list, as there were some renames and new additions.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit [1] created a common LPM wkup sources overlay and removes
k3-am62x-sk-mcu-gpio-wakeup.dtso for am62 device family.
k3-am62x-sk prefix picks this overlay for am62xx, am62axx and am62xxsip already.
This patch picks the necessary overlay for am62xx-lp-evm since it doesnt use
the same prefix as other am62 platforms.
[1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=4ba1886b886d
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update SRCREV for ti-jailhouse. All the patches which was being applied via yocto
have been moved to ti-jailhouse repo now. So remove the patches from SRC_URI and
files.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for ti-extras for am62pxx to control the kernel and u-boot
repos, branches, and srcrevs via the TI_EXTRAS variable in the local.conf
file.
Also add am62pxx as compatble machine in jailhouse recipe. So the am62pxx
jailhouse build can be done by adding TI_EXTRAS=tie-jailhouse in local.conf.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A bug was introduced while trying to unify the Mesa version that is used
on SGX GPU's and Rogue GPU's. It manifests itself as an immediate segfault
whenever you try and run something like glmark2-es2-wayland or
weston-simple-egl on certain Rogue based platforms (specifically am62x).
Use different srcrev for Rogue GPU and SGX GPU platforms. The SGX GPU platforms
will use the latest commit. Rogue GPU platforms will use the last good working
commit before SGX related changes were introduced.
This change will be reverted once the issue is rootcaused and a common solution
is found for both Rogue and SGX based GPU platforms.
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upgrade to v6.3.0 version.
This release adds resources for using AM243x & AM64x PRU cores with cores
running FreeRTOS:
* The RTOS Getting Started Labs
* Examples for using PRU GPIO and the broadside interface
* SORTE_G example (a custom networking interface)
Bug fixes:
* AM64x & AM65x header files, fix the names of extended sections to be in the
format of
ConstantsTableName_0x100
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This k3r5 multiconfig builds baremetal components (and corresponding native,
nativesdk and cross tools) and sets TCLIBC accordingly to "baremetal". The
expectation is that those components and tools will use a separate TMPDIR
to isolate from the main Linux build that uses "glibc" TCLIBC and to avoid
potential conflicts.
OE-Core "nodistro" default configuration already sets TCLIBCAPPEND facility
to automatically add a suffix to TMPDIR, resulting in "tmp-baremetal" temp
directory for this multiconfig and "tmp-glibc" for the main Linux one. Other
distros like Arago follow this convention and even extend a bit (e.g. Arago
also adds TCMODE suffix to TMPDIR for external toolchain support separation).
But Poky (and derivative distros, like AGL or YoE) disable TCLIBCAPPEND and
result in a combined TMPDIR, leading to potential conflicts, such as:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15273
And that's just the beginning, there were other conflicts observed later in
the build, e.g. during nativesdk builds - that's why we also set a unique
SDKPKGSUFFIX here.
To force a separate TMPDIR for k3r5 multiconfig, we have to directly append
a suffix to it. Multiple other options were tested in hopes of making it
slightly cleaner, but they either didn't work or were dismissed. For example,
trying to override TCLIBCAPPEND getting cleared by a distro would require
using a machine/soc-override, which doesn't have enough scope (nativesdk)
or forcing it with :forcevariable would also change the main Linux TMPDIR
and affect existing CI flows. Also, using TCLIBC itself as a suffix to add
to TMPDIR may result in getting it appended twice (tmp-baremetal-baremetal)
when normal TCLIBCAPPEND facility is used. Hence the least invasive/confusing
option is to always append "-k3r5" suffix to this multiconfig TMPDIR. That
results in "tmp-k3r5" in Poky (leaving main TMPDIR as "tmp"), while OE-Core
"nodistro" and Arago would end up with "tmp-baremetal-k3r5" (and "tmp-glibc"
for the main).
Also note, meta-ti-bsp layer.conf sets up images and sdks to be deployed
into a common location outside of TMPDIRs, but TI_COMMON_DEPLOY variable
that controls it is set weakly, allowing to be modified from a distro
configuration or local.conf. It means that all images and sdks can be
deployed into the main TMPDIR if one's CI flow expects tmp/deploy/ as
the final destination, by using := for immediate variable expansion:
TI_COMMON_DEPLOY := "${TMPDIR}/deploy"
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit [1] renamed the MCU GPIO wakeup overlay as k3-am62x-sk-mcu-gpio-wakeup.dtbo
k3-am62x-sk prefix picks this overlay for am62xx, am62axx and am62xxsip already.
This patch picks the necessary overlay for am62xx-lp-evm since it doesnt use
the same prefix as other am62 platforms.
[1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=24bd6ce832cd
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was a temporary class to help with the v5.10 to v6.1 kernel
migration, now that we have completed that, remove this class.
Suggested-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We support Linux v6.1 as our official version for Kirkstone. The older
kernel version was kept around during the transition to the newer version,
but we are past that now. Remove this old version.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SRCREV is auto updated, but the PV still uses the old tag version,
update this to v0.3.
While here, we also now have a proper LICENSE file, use that.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit f5851386 ("conf: machine: am62*: Pick common overlays by prefix")
picks common HDMI and CSI overlays for am62 platform variants.
Adding capability to extend the same prefix for common overlays for applicable
am62 platforms in more generic way to include new mcan overlays added [1]
[1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/?&id=3b01c392627f
given the differences in SK-AM62-LP containing B2B HDMI Samtec connector,
just added the kernel prefix to pick common mcan overlay.
for am62pxx: It has 4 MCANs vs all other am62xx devices have 3 MCANs,
hence keeping this prefix seperate for am62pxx to pick right overlay.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Jai Luthra <j-luthra@ti.com>
Reviewed-by: Judith Mendez <jm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These are all useful for firmware recipes but some recipes did not have
them. For firmware including ti-linux-fw.inc let's add these all to
one spot and remove them from any recipe that did already have these.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These defines are specific to a SoC, not any specific board. Move these
to the SoC level for these boards to be consistent with boards already
doing this correctly.
J7200 didn't have these at all, add them while we are here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The common include ti-linux-fw.inc already includes setting this, no need
to set it in each recipe, remove that.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is no compilation in this simple firmware recipe, no need for
these lines, remove them.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These are common for all recipes that include ti-linux-fw.inc, add
it to this include file and remove from each recipe.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add support for ti-extras features for rt as it was added for non
rt kernel and u-boot earlier. It will also be accessible via the
TI_EXTRAS variable in the local.conf file.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Don't try to locate TI-TFL license within meta-ti-bsp relative to OE-Core
using COREBASE, as the directory structure of the layers is not guaranteed.
Instead, point to it relative to the recipe itself.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Minor rework of the TI include files used to override both SRCREV and
other settings in the optee recipes for TI SOC parts. The intent is to
make it more clear when we are changing SRCREVs versus changing other
items, and allow for sharing the SRCREV changes for optee-os-tadevkit
which should track the optee-os SRCREV.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the SRCREV to latest commit for both u-boot and linux
extras. Also update SRCREV for jailhouse branch for both psdk
linux and u-boot.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous allowance for overriding the value for the kernel is
incorrect. The kernel should not be changed from linux-dummy for the
k3r5 multiconfigs.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is a build error under master that is not present in kirkstone
related to .SECONDARY/.NOTINTERMEDIATE being set differently between the
ti-img-rogue-driver repo and the kernel. The long term solution to
allow this code to be built on both kirkstone/master is being
investigated. In the meantime, this patch gets things building on
master.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move to the 23.2 release branch and bump SRCREV accordingly. This branch
has the proper implementation of the cache coherency fix along with some
other checks that address some system stability issues on Jacinto
devices.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump SRCREV to include some patches to better isolate SGX and PVR
components.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Instead of making kernel RDEPENDS on devicetree and different FW images with
lots of machine-override appends that are hard to modify downstream, use proper
MACHINE_ESSENTIAL_EXTRA_RDEPENDS and MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS vars
that are specifically designed for this purpose.
This also makes such dependencies generic and not tied to a particular kernel
recipe including kernel-rdepends.inc with the entire machine-specific list.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Acked-by: Andrew Davis <afd@ti.com>
Acked-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Set MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS per platform to list recommended
essential FW images to be added to rootfs by default.
Correct beagle-x15 to pull devicetrees and kernel image as well.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Majority of Beagle devices use ti-u-boot repo from u-boot-ti-staging directly.
But some latest devices may need to point to own tree with additional support
added that is not yet upstream, e.g. BeaglePlay.
Add the Beagle-specific recipe and point beagleplay to use it. Other devices
can switch to using it as well, if desired, but right now the code base is the
same for other Beagle devices.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update both 32-bit and 64-bit configs to use the latest 6.1 Linux kernel
from beagleboard.org repository, which is based on ti-linux-kernel repo
used in linux-ti-staging, but with extra Beagle-specific features on top.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update DTB/DTBO list to only upstreamed devicetrees and overlays. This
help with migration to kernel 6.1, which doesn't have BB.org specific
overlays.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update DTB/DTBO list to only upstreamed devicetrees and overlays. This
help with migration to kernel 6.1, which doesn't have BB.org specific
overlays.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since the introduction of TI_COMMON_DEPLOY, we've been seeing frequent
Pseudo errors [1] breaking image build during development, in particular
with partial rebuilds due to the externalsrc bbclass.
The relevant part of the error log seems to be the following:
ERROR: Task (/home/schifferm/Devel/src/ci-meta-tq-kirkstone/sources/meta
-tq/meta-dumpling/recipes-images/images/tq-image-generic-debug.bb:do
_rootfs) failed with exit code '1'
Pseudo log:
path mismatch [1 link]: ino 12215614 db '/home/schifferm/Devel/src/ci-me
ta-tq-kirkstone/build-mba64xx/deploy-ti/images/tqma64xxl-mbax4xxl/tq
-image-generic-debug-tqma64xxl-mbax4xxl-20231020091917.testdata.json
' req '/home/schifferm/Devel/src/ci-meta-tq-kirkstone/build-mba64xx/
tmp/work/tqma64xxl_mbax4xxl-tq-linux/tq-image-generic-debug/1.0-r0/r
ootfs/usr/share/stress-ng/example-jobs/device.job;65324e26'.
My understanding is that all deploy dirs should be ignored by Pseudo, as
openembedded-core/meta/bitbake.conf includes the whole of DEPLOY_DIR in
PSEUDO_IGNORE_PATHS. With the introduction of TI_COMMON_DEPLOY,
DEPLOY_DIR_IMAGE is not covered by that setting anymore, so we add it in
meta-ti to avoid the issue.
[1] https://wiki.yoctoproject.org/wiki/Pseudo_Abort
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV to include the required changes to build for SGX now.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump ti-sgx-ddk-um and ti-sgx-ddk-km to the new branch for Kirkstone and
mesa independent builds. This also sets up SGX to use the latest mesa
revision rogue uses.
Changelog:
- IMG Support has officially ended. This repo will not be getting
regular updates after this unless things are really broken.
- The Mesa patches which were previously being relicensed internally
were opened and combined with the unofficial rogue efforts on
freedesktop.
- Toolchains were upgraded and multiple warnings and issues were
addressed. Hardware recoveries work now, but there are still some
longstanding issues with SGX that remain to be addressed if further
resources are set aside for that.
- We moved to an lws-generic build target to avoid rebuilding external
components. As such, these external components must be patched as
needed. Libdrm is an example of this and the required patches can be
found in meta-ti.
Known bugs:
- Buffer allocations under Weston may misbehave
- GLSL macro redefinitions will cause errors regardless of whether or
not they are identical
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Makes ti-ipc firmware as default for main-r5f0_0 firmware softlink
The ti-eth-fw binaries are tested at the SDK level and should be
made default only at that level
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The main-r5f0_0 softlinks should be pointing to the ethfw binaries
instead of the mcu-r5f0_0
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This reverts commit cd13cafd65.
Some devices need ti-fs-stub-* firmware for the uboot aarch64 build
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Revert ebcf15bf0f :
"recipes-bsp:ti-sci-fw: Add k3r5 as COMPATIBLE_MACHINE"
Extend recipe to k3 machines too, to provide ti-fs-stub-* firmware
for u-boot aarch64 build.
Update do_deploy() to allow multiconfig builds for k3 machines
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fixes the QA warnings about package contains reference to TMPDIR.
Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently the do_compile step fails if we try to implement UBOOT_CONFIG
in an attempt to build U-Boot with multiple R5 defconfigs.
This commit adds a condition to handle linking the UBOOT_BINARY if
UBOOT_CONFIG is used in place of UBOOT_MACHINE.
Signed-off-by: Garrett Giordano <ggiordano@phytec.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The previous patch is incorrectly accepted and released. This patch
applies the logic that was discussed on the mailing list.
- Create a new variable grouping for SPL_HS_MLO
- Update the install/deploy code to reference the new variables.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The common u-boot-ti.inc file still uses the old license checksum
from 2021 U-boot. There were formatting changes in the license text
between 2021 and 2023 and version-specific recipes had the license
checksum updated to the new value. Since there are no 2021 recipes
remaining, the new license checksum can be set in the common .inc
file generically.
Note: U-boot license hasn't changed and the same checksum is simply
being moved from the recipes to the common .inc file.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Preserve the directory structure of the deployed dm firmware so that one
can directly specify the deploy directory for binman based u-boot build.
Additionally, this makes it easier to preserve the same structure inside
the prebuilt-images directory of the tisdk-core-bundle for the same reason.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Deploy the sysfw binaries to the DEPLOYDIR, to be picked up by the
tisdk-core-bundle... for the prebuilt binaries directory
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SPL binary built by u-boot for SD/MMC/eMMC media on HS platforms is
u-boot-spl_HS_MLO. Thanks to this fix, the binary is properly installed
and deployed.
Signed-off-by: Julien Panis <jpanis@baylibre.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe only provides the sysfw binaries compiled for the r5
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ti-sci-fw should be needed by the binman u-boot build only for the k3r5
machines and not for the k3 machines
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OP-TEE OS provides a handful of TAs itself. While these are often meant
to be built-in, when they are not we should deploy them as part of the
OP-TEE OS package so they can be loaded at runtime.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Only move directories which haven't already been moved.
This prevents a build error should a subsequent bitbake execution
rerun do_install where the sources to 'mv' no longer exist.
| mv: cannot stat 'ti-img-rogue-umlibs/23.1.6404501/git/targetfs/am62_linux/lws-generic/release/lib/firmware': No such file or directory
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
multi_v7_defconfig that is used for legacy platforms enables
SMP by default.
Platforms like am335x and am473x are single core platforms that
doesnt need this option to be enabled.
This config cannot go in multi_v7_defconfig as well,
since there will be systems like am57x/dra7x or other community platforms
which can have multiple arm cores.
Adding the provision to disable SMP configuration for applicable platforms like
am335x and am437x.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updates SRCREV, PV, and BRANCH for armv7a targets and fixes
failure to mount /boot when using poky with systemd. The
kernel selected supports VFAT without initramfs as noted
here - https://lists.yoctoproject.org/g/meta-ti/message/16913
Removes defconfig patch setting LZMA, as the new kernel
already defaults to LZ4.
Tested by running `bitbake core-image-base` with this patchset,
and then booting a pair of Beaglebone Black devices from the
resulting image. Prior to the change, systemd boots to a
maintenance mode having failed to mount /boot. After the change,
the system boots normally and /boot is mounted.
Suggested-by: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Anthony J. Martinez <anthony@ajmartinez.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Jacinto platforms use first R5 MCU core for DM firmware. When DM firmware was
split out into own recipe[1], ALTERNATIVE_TARGET entries got removed from
ti-rtos-firmware recipe, but corresponding ALTERNATIVE_LINK_NAME entries
remained, causing warnings. Clean up those now.
[1] https://git.yoctoproject.org/meta-ti/commit/meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb?id=b21d29d94694ac49b97a1f4ba428c7d8cd6fb64a
Fixes these warnings:
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw or /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw: /usr/lib/firmware/j7-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw == /usr/lib/firmware/j7-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw or /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw: /usr/lib/firmware/j7200-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw == /usr/lib/firmware/j7200-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j7200-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j721s2-mcu-r5f0_0-fw-sec
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alternative target (/usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec or /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware) does not exist, skipping...
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: NOT adding alternative provide /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec.ti-rtos-firmware does not exist
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw
| WARNING: ti-rtos-firmware-08.02.00.04-r4.1 do_package: ti-rtos-firmware: alt_link == alt_target: /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec == /usr/lib/firmware/j784s4-mcu-r5f0_0-fw-sec
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There are couple of k3r5 components that need to be built for the target
and they are self-contained and don't use glibc. Moreover, when building
a cross-compile toolchain for k3r5, there's no need to build glibc and
all its dependencies. While build-time speed up is nice, the main benefit
comes when packaging a nativesdk toolchain for distribution, reducing the
number of packages and the resulting size of the toolchain installer.
To avoid potential namespace conflict in package feeds between nativesdk
binary packages of Linux glibc and k3r5 baremetal toolchains, adjust the
package suffix accordingly.
This also requires a rather impactful change in the deployment structure,
which affects CIs and user experience. By default different TCLIBC builds
(e.g. glibc and baremetal in this case) are built in separate TMPDIRs to
avoid conflicts, especially on the nativesdk side. Also the default config
has DEPLOY_DIR residing under corresponding TMPDIR. Of course, this can be
changed by local.conf or <distro>.conf, which meta-ti-bsp has no control
over. Unlike multiconfig-image-packager example that can access deployed
artifacts across multiconfigs to package in an image, we use wic and its
IMAGE_BOOT_FILES list to package a final image. Unfortunately, wic cannot
access deployed artifacts across multiconfigs in separate TMPDIRs, as it
uses DEPLOY_DIR_IMAGE to collect the artifacts. To overcome this, we need
to set up a "common" deploy directory for images and sdks produced by
multiconfigs, which is located outside of TMPDIRs, set by TI_COMMON_DEPLOY
variable that can be changed or adjusted by distros as needed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Make sure shortname R5 SPL symlink is not the same as the main K3 SPL
one, as they will overlap/overwrite each other when deployed into a
common location. Latest code in master now checks for this and errors
out.
Also remove unused UBOOT_SPI_* variables.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
- Add A53 and R5 machine configurations for am62xxsip-evm.
- Use UBOOT_CONFIG_FRAGMENTS as am62xsip_sk_r5.config in R5 machine configuration. This will ensure we
build u-boot-r5 with baseconfig as am62x_evm_r5_defconfig and config fragment as am62xsip_sk_r5.config.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
- U-boot recipe in OE-Core supports out-of-tree config fragments that are passed via
SRC_URI and automatically merges all *.cfg files as fragments. This makes specifying
config fragments in the machine configuration a bit difficult. Hence, add a logic which
will ensure we handle u-boot config fragments using a new variable UBOOT_CONFIG_FRAGMENTS.
- The u-boot-mergeconfig.inc will allow us to build u-boot with list of config fragments
specified in UBOOT_CONFIG_FRAGMENTS along with the base defconfig mentioned in UBOOT_MACHINE.
- Include u-boot-mergeconfig.inc in u-boot-ti.inc
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OE-Core is switching layer compatibility to nanbield for the upcoming release.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Meta-clang provides a bbappend for mesa to use clang to accelerate it's
rasterization with runtime code generation through the use of llvmpipe.
With the addition of mesa-pvr we no longer get this for free with the
blanket mesa bbappend on the devices that explicitly request mesa-pvr so
lets add a dynamic layer to append the same args meta-clang does.
Though the number of devices that would select pvr-mesa and still want
to use software rendering is small, it's not zero due to debug and
testing purposes.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The uboot config for am65 is moving to a merged build for both GP and
HS. Until the yocto configs catch up, we need to keep am65xx-hs-evm
working.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SRCREV change corresponds to a commit that changes from make to
cmake for building k3conf, so we need to update the recipe as well.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
A recent change to oe-core [1], has caused a pile of QA errors during
packaging for this binary package. The effect of the change in oe-core
was to remove the dependency on the compiler and other compiler adjacent
libraries. But the binary packages need some of the compiler tools as
part of the packaging flow (ie. objdump).
Until the above gets reverted, this patch will fix the issue and can be
reverted itself once oe-core is fixed.
[1] https://git.openembedded.org/openembedded-core/commit/?h=master&id=d1d09bd4d7be88f0e341d5fccbfbefeb98d4b727
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Previously k3 mcdepends for k3r5 artifacts has been changed from do_image_wic
to support non-wic builds in other layers and do_image_complete was believed
to be sufficient. Switching k3r5 to baremetal builds has exposed another race
when some pieces come from sstate and hence requires using do_image instead.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the QA checks done on the build artifacts to include [buildpaths] since
the PRU linker includes these paths in its output. This avoids build warnings
or errors of the type:
pru-icss-6.2.0-r1 do_package_qa: QA Issue: File /lib/firmware/pru/PRU_Halt.out in package pru-icss-halt contains reference to TMPDIR [buildpaths]
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Sometimes on am335x devices, no more output is printed after
"Starting kernel..." message. Modify UBOOT_EXTLINUX_KERNEL_ARGS
to enable the console before standard serial driver is probed.
Signed-off-by: Julien Panis <jpanis@baylibre.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The latest kernel has made the change to add vendor subdirectories into
the arch/arm/boot/dts directory. This effectively breaks the
KERNEL_DEVICETREE settings in the machine configs for 32bit platforms,
so switch them over to using the PREFIX variable. Also change the
linux-ti-next to use the PREFIX setting for KERNEL_DEVICETREE.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
With the change to the vendored arch/arm/boot/dts directory, we need to
add support to the KERNEL_DEVICETREE_DTBMERGE to make it a search
pattern instead of a fixed list.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add in missing *-sec links pointing to signed files especially for
j784s4. Reformat file a little to make the groupings easier to
manage in the future when looking to see if -sec links are missing.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The following MACHINE_FEATURES are not matched against anywhere, remove:
* kernel26
* ethernet
* mmc
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit 5f9be22839 ("machine: Add AM62Q HS-SE evm configuration")
has added am62xx-lp.inc which is used by am62xx-lp-evm machine.
The features listed in am62xx.inc are common between machines
am62xx-evm and am62xx-lp-evm. (Ex: MACHINE_FEATURES = "gpu")
Hence updating the necessary include file to have
common features to be enabled between these two platform variants.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Suggested-by: Randolph Sapp <rs@ti.com>
Reviewed-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the SRCREV for the umlibs and driver package to include some fixes
for Jacinto devices. These patches do the following:
- Fix virtual memory addressing
- Resolve an issue with APM and debug requests
- Attempt to resolve most of the cache coherency related issues on
Jacinto devices
- Introduce some extra cache maintenance operations in the kernel
module
It also introduces the following known issues:
- Visual artifacting on the second-to-last EGL/GLES context on BXS
based devices (J721S2/J784S4)
We're still working on that last one, but the stability improvements
make this worth while for now.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The address 0x80008000 was used in pre-K3 devices. ARM64 requires the
kernel loaded to a 2MB aligned address when not using KASLR. For FIT
set the address to 0x81000000 which gives the kernel 32MB before running
into the FDT at 0x83000000.
If you get this error someday then your kernel is too large and either it
or FDT needs relocated in memory:
ERROR: image is not a fdt - must RESET the board to recover.
Signed-off-by: Andrew Davis <afd@ti.com>
Tested-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upgrade to v6.2.0 version.
This release supports Linux kernel 6.1.
The RPMsg library in previous versions of the PSSP will not work with
the PRU RPMsg drivers in Linux kernel 6.1.
Other changes in this version:
* Bug fixes:
- Getting Started Labs, fix "zero" command clearing too many bytes
- Include files, add a missing parentheses to pru_cfg, pru_ctrl, pru_ecap
* Update ReadMe files to point to the latest URLs
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update ti-rpmsg-char library to fix wrong rpmsg-ctrl
device ids observed when multiple remote procs are present
with multiple channels opened.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The following patch was dropped from the SRC_URI one of my previous
graphics overhaul patches:
0001-compiler-support-OpenEmbedded-nodistro-internal-aarc.patch
Actually remove it from the source tree now that upstream is carrying
the equivalent to help enable other tools.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream changed to not be so picky about compilers. Bump SRCREV so the
odd things using our recipes are happy again.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Edit the file paths so they point at files in the source directory
explicitly. For some reason shell glob were previously only respected by
some machines.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* rpmsg_client_sample is a test module and should not be autoloaded
* Both k3_r5 and k3_dsp remoteproc modules depend on virtio_rpmsg_bus
Cc: Denys Dmytriyenko <denys@ti.com>
Cc: Ryan Eatmon <reatmon@ti.com>
Cc: Praneeth Bajjuri <praneeth@ti.com>
Cc: Apurva Nandan <a-nandan@ti.com>
Cc: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use RRECOMMENDS for components. Apparently I made an resolvable
dependency cycle that Yocto silently clipped. My best guess at the
culprit was: mesa-megadriver (RR) -> rogue-km (RR) -> rogue-um (RD) ->
libgles1-rogue (RD) -> mesa-megadriver
That killed the ti-img-rogue-umlibs recipe during do_rootfs. The rogue
GLES libs do depend on mesa-megadriver at runtime but I guess the UM
components should only really recommend the rogue GLES components be
present at runtime to make the cycle resolvable by opkg.
Fixes:
1705f6d3 (ti-img-rogue-umlibs: make all components optional, 2023-06-21)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that driver support is added to support switch mode
for AM64, update recipes to package the switch firmware.
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We need to package up new HSR firmware for am65x-sr2. Add dependencies
for them on the correct platforms.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bumping into the limitations of the binary_package class. This change
allows all rogue components to be optionally packaged without blowing
out the dependency chain.
Add a python function to fetch file paths from the FILE vars for each
component so we don't end up double tracking files. Add variables to
track component packages if things split up more later. Add a package
config string to set runtime dependencies and recommendations. Change
all logic to revolve around the PACKAGECONFIG instead of distro
features.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When the ti-eth-fw recipe was split out from the ti-rtos-firmware recipe
we forgot to add it as a dependency.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add TI logo bitmap image as image boot file so that it gets
copied to boot partition and A53 SPL or U-boot proper
can load it and display during board bootup.
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Early splash screen support for AM62x has been enabled in u-boot
and it requires bitmap tarball to be present in boot partition
as per the default environment settings done in u-boot [1].
Copy the ti logo bitmap tarball to boot partition of wic image in order
to enable out of box early display on AM62x.
[1] https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am62x/am62x.env
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This firmware is shipped with the rest of ti-sysfw blobs, it shares
the same versions too and so should be simply bundled with the same.
This stub is also built into U-Boot and not loaded during kernel
runtime anymore, so remove the RDEPENDS in kernel.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There are some features that will either never be accepted into the
upstream kernel, or are not ready to be accepted. ti-extras allows for
controlling the kernel and u-boot repos, breanches, and srcrevs to gain
access to those features via the TI_EXTRAS variable in the local.conf
file.
Initial support for TI_EXTRAS=tie-jailhouse is being added by this
patch.
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Acked-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Well, flew a bit too close to the sun on that last patch. Apparently
there are a few hidden runtime dependencies on the API devlinks that
make things like EGL upset when they aren't present.
We may circle back to this at some point but for now we're fine shipping
the devlinks in the base API packages as these links don't step on any
other package.
Fixes: 1899f5ea (ti-img-rogue-umlibs: bump version and explicitly
package, 2023-06-01)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Apply the ti_rt.config fragment to all the linux-ti-staging-rt-6.1
defconfigs so we can properly build the RT kernel for our devices.
Signed-off-by: Bryan Brattlof <bb@ti.com>
Acked-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
SR2.0 firmware binaries should be used here as SR1.0 has been descoped.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This matches how we had the symlink for tiboot3.bin before binman.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This matches how we had the symlink for tiboot3.bin before binman.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot with binman will do the signing as these images are packaged.
Do not rename the DM image as the signed image.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot with binman will do the signing as these images are packaged.
Remove signing steps here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
U-Boot with binman will do the signing as these images are packaged.
Remove signing steps here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The platforms with combined boot image have full names for tiboot3.bin
and to keep things consistent we can do the same here. Deploy these files.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The platforms with combined boot image have full names for tiboot3.bin
and to keep things consistent we can do the same here. Deploy these files.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In U-Boot the names of these files have been updated to match our
expected defaults. Remove these fixups.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The defaults set in am62xx.inc are correct now and these can be dropped.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Everything is the same, so just include the non-HS config to set vars.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Everything is the same, so just include the non-HS config to set vars.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The HS boards use the SR2 version of the silicon, ship that version
of the sysfw.itb image.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These are not used anymore and most have been removed, these look
to be leftovers, remove them.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the ti-rpmsg-char library to 0.6.1 version to fix rpmsg_ctlr
id on v6.1 kernel when multiple channels are created.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This converts ti-sci-fw into a standard firmware provider package. We do
not need to do anything additional here with that firmware as U-Boot now
does that for us with binman.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This will no longer build after we switch away from k3-image-gen. Remove
this version and make 2023.04 the default.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This will no longer build after we switch away from k3-image-gen. Remove
this version until it can be rebased on the latest U-Boot with binman
support. For now switch current users of this over to u-boot-ti v2021.01.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
K3-image-gen is going away and we don't do SRCIPK packages like this
anymore anyway. Remove this recipe.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Set the variables needed to put the DTBs into the same vendored
directory structure as they are in the kernel.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the version and explicitly package all Khronos APIs separately.
This should be nice for those folks that want a headless opencl system
for tinkering and such.
This version includes experimental GEM support (for applications like
Chromium that like to poke at the render node) and a new Vulkan ICD
loader interface for better support with the Vulkan ICD loaders present
in Yocto.
This lifts a method from mesa used to force a common naming convention
for Vulkan, OpenCL, and OpenGLES libs to make things a little easier to
follow. Without it the target package names get scrambled based on the
shared object name.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move recipes to new subdir since we offer more than just libgles now.
Reusing the naming convention of the subdirectory used for the km
components for now.
Signed-off-by: Randolph Sapp <rs@ti.com>
Acked-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There is only one user of these include files, expand the files inside
the one user and remove the includes.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This file should be whittled away over time, remove currently unused
paths to help us take inventory of what remains.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Minor changes to match with Kirkstone for consistency.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Cleanup the J* APM patch a little. Apparently I could have stood to read
the docs a little more. Found some better runtime pm functions and also
discovered something new about the power island definition.
Notes from upstream:
- Add the CCB coherency HACK from DDK 1.15 to improve stability
on J* devices
- Fix power island support on J* devices
- Use better APM calls so user modification to power domains
don't cause the device to enter a bad state
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the ti-rpmsg-char library to 0.6.0 version that enables the
support for 6.1 kernel.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rename the .wks to .wks.in so the EFI_PROVIDER variable is expanded
properly. We only ever set a soft recommendation for GRUB. If anyone
attempted to change that previously it was ignored (for more than just
the reason here, but that's out of my control).
Add a timeout for the bootloader menu. Currently setting it to 3
seconds.
Remove the read only flag on the rootfs. Not sure why that was there.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that are past the inital stages of our LTS migration, we can remove
the DEFAULT_PREFERENCE settings that prevented these recipes from being
the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As part of the initial LTS migration, move to the latest commits for the
various repos.
- ti-linux-fw
- u-boot-ti-staging_2021.01
- u-boot-ti-staging_2023.04
- k3conf_git
- linux-ti-staging-rt_5.10
- linux-ti-staging-rt_6.1
- linux-ti-staging_5.10
- linux-ti-staging_6.1
Going forward all updates will come from the CICD flow.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the src revision to enable the following features on Jacinto:
- Active power managment
- Power island control via firmware
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Stop looking for the rpmsg_rpc.h in the kernel. While we are doing the
LTS migration for kirkstone, this file is not going to be in the kernel
for a bit. This patch works in conjunction with a recipe change that
downloads the header and adds a -I to the CFLAGS to pick it up. This
will be removed once the 6.1 kernel has been updated.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
uboot will now use a merged defconfig build so keep the defconfig same
for hs here
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
u-boot 2023.04 merged def configs for HS and GP EVM into one.
This patch updates config for J721S2 HS EVM for both A72 and R5.
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
u-boot 2023.04 merged def configs for HS and GP EVM into one.
This patch updates config for J7200 HS EVM for both A72 and R5.
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When creating the boot partition we copy all of the images for the
different board types (gp, hs-fs, hs-se), but one of those we consider
to be a default. That default is not copied with the longer name, but
rather with the tiboot3.bin name.
The issue comes when someone wants to boot with a different bin file.
They need to copy the approriate longer named .bin file to tiboot3.bin.
But then the original name of what tiboot3.bin is lost unless the use
backs it up.
This patch just additionally copies that longer named bin file so that
anyone who wants to look at the boot partiion and decide to boot for a
different board can know which file to copy to tiboot3.bin and does not
need to worry about making a backup.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Avoid inheriting ti-secdev class and adding unconditional dependency
on TI_SECURE_DEV_PKG and other variables, when meta-ti-bsp is in the
bblayers.conf stack, but not building for TI platforms. This solves
yocto-check-layer signature test for Yocto Project compliance.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Avoid inheriting ti-secdev class and adding unconditional dependency
on TI_SECURE_DEV_PKG and other variables, when meta-ti-bsp is in the
bblayers.conf stack, but not building for TI platforms. This solves
yocto-check-layer signature test for Yocto Project compliance.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There are some unobvious issues with adding PVR support to Mesa
via a bbappend:
1. We need to mark mesa package as machine-specific, due to
differences in builds between SGX, Rogue and software-rendering
2. We also need to then mark mesa package as providing safe
ABIs (EGL/GLES/GBM) in order for all generic dependent packages
to not be treated as machine-specific, allowing their re-use
across different machines of the same architecture
But doing the above alters the upstream mesa package and changes
its signatures even when not building for TI platforms, which is
a Yocto Project compliance violation.
In order to resolve this issue, convert Mesa bbappend, that adds
PVR support, into its own standalone alternative provider, called
mesa-pvr and allow selecting it with PREFERRED_PROVIDER settings.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Some of the settings for KERNEL_DEVICETREE_PREFIX were missed in the
first pass. Additionally, some new dts files that were not present in
upstream are now there and can be updated in KERNEL_DEVICETREE.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OE-Core recently added non-flat directory structure for device trees
and overlays packaging:
https://git.openembedded.org/openembedded-core/commit/?id=04ab57d20009d85eb566e83ae6fe1dcea4db7300
But it only packages 2 levels - top KERNEL_DTBDEST and one level down
for vendored device trees. But linux-bb.org installs own overlays in
"overlays" subdir of the "ti" vendor directory, making it the third
level. Add those overlays into the package as weel.
Cc: Randolph Sapp <rs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The DT name k3-am62-lp-sk.dts was adopted instead of k3-am62x-lp-sk.dts
because the community prefers avoiding the wildcard letter 'x'.[1]
Drop the letter 'x' from the strings in KERNEL_DEVICETREE_PREFIX and
KERNEL_DEVICETREE to accurately reflect the DT names.
Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com>
[1]:
https://lore.kernel.org/all/06cbcd7d-bc83-bfeb-0821-72c7caf9a5e7@linaro.org/
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add and enable Jailhouse support for TI's k3-am625-sk similarly to how other
TI platforms were added and enabled in the past by adding platform-specific
configuration variables for the root cell DTB overlay, and the Linux demo inmate
DTB, configuration, and Kernel command line settings.
Migrate the jailhouse recipe to kirkstone from dunfell.
Switch to latest upstream source tree for jailhouse. The TI Jailhouse repo has
gone stale and now upstream is really the happening place where new development
happens including for new devices such as AM62x. Hence go ahead and switch to
using the upstream repo.
Update the platform-specific config files to such that the root cell DTB overlay
gets included in the file system images.
Enable additional console on ttyS3 (usually mapped to main_uart1) and ttyS2 for
the Linux demo inmate to use.
Add patches for the Jailhouse source tree for am62xx.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Only include the ti-img-rogue-umlibs-vulkan package if the
DISTRO_FEATURES x11 is enabled. Right now, this recipe has a failed
build dependency on images without x11.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Select the correct WKS file according to the MACHINE_FEATURE efi.
Right now, the sdimage-2part-efi.wks is set by default. Switch to the
sdimage-2part.wks file, if efi was removed from MACHINE_FEATURES to allow
non-efi boot methods.
Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Split the firmware into it's own package so we can make the insane
checks a little more paranoid again.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Cairo can either be built for use with OpenGL or OpenGLES. By default it
assumes it can use OpenGL if X11 is provided as a distro feature. This
assumption is not true when using the proprietary SGX / Rogue drivers.
Vulkan libraries need some X libs at runtime now, so we need to manually
override the PACKAGECONFIG for cairo to use OpenGLES.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the required vulkan configuration options and the new PVR WSI file to
the corresponding package.
Also bump the PV to match the version of Mesa actually being shipped.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the source revision for the following upstream changes:
- Drop the included ICD loader. Use the Mesa/Khronos one
instead.
- Enable all vulkan window system extensions
Separate the vulkan libs into their own package so people can choose to
ignore them if they want, considering the new runtime deps.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Add support for additional config fragments passed via semi-standard
KERNEL_CONFIG_FRAGMENTS variable
* Also don't build all DTBs, only those specified in the machine config
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the rogue graphics recipes to point at the new 23.1.6404501
release. This adds support for:
- kernel 6.1
- vulkan
- opencl (more testing needed)
- zink (more testing needed)
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the pvr-mesa include to use the 22.3.5 patches from
oe-core/master and the branch for DDK version 23.1 on freedesktop.
Also remove the PACKAGECONFIG options elf-tls and xvmc as those
functions were dropped by the oe-core/master version of this package and
mesa package respectively.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Locally overlay verbatim copies of mesa 22.3.5 patches from
oe-core/master, so the same codebase works in kirkstone and master.
Also drop the old patches from 22.0 that were from the tip of
oe-core/kirkstone previously.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently we move this firmware around and put it in a directories named
pdk-ipc/ and ethfw/. This does not match what is in linux-firmware which
is what projects should expect /lib/firmware to match. This causes issues
for projects that want to work both on meta-ti and also on any other distro.
Switch to shipping the same directory structure as linux-firmware here.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The version information should come from the ti-linux-fw.inc and this
version is old anyway.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
For TI platforms with SGX and Rogue graphics we patch upstream Mesa with
PVR support and conditionally enable features based on virtual/gpudriver
preference. This makes Mesa package platform-specific and it contains the
corresponding PACKAGE_ARCH = "${MACHINE_ARCH}" line.
In order to get greater re-use from generic non-machine-speciofic packages
down the dependency chain, such as Wayland, Weston, Qt5 modules, etc. we
need to mark mesa recipe as still providing stable OpenGL ABIs, such as
EGL, GLES, GBM, etc. - add it to SIGGEN_EXCLUDERECIPES_ABISAFE list.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Neither of recipes nor their ABI is all that stable. OpenGL might be
slightly more stable, but that is not what these provide anymore.
The variable helps with re-use of generic packages down the dependency
tree, when they depend on a machine-specific package. SGX UM used to
provide different standard OpenGL ABIs (EGL, GLES, GBM) and hence was
listed here. Now those ABIs are provided by Mesa, so SGX is removed.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use these to select build type and window system support to match how
the Rouge driver does the same. No functional change.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Of the K3 family only the AM65x device is currently supported by this
driver. COMPATIBLE_MACHINE should match.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The "clean" target has been fixed along with some other issues that
caused us to need these set. Remove them now.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Small changes, the "upstream" doesn't look to be maintained anymore,
so if we get any more breaks it might be time to remove this recipe.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The traditional order of serial consoles for K3 has ttyS2 being the
primary UART attached console. ttyS0 is also a common choice for
distros and the TI kernel may switch at some point. To prepare
we check both UARTs on all K3 devices. Move this common check
to a K3 common location.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Was used to build kernel DTBs prior to KERNEL_DEVICETREE getting populated
with the list of preset of upstream DTBs. Not needed anymore so remove.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Not sure if anyone is testing on this device with -next, but for
completeness add its defconfig.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Mainline should test the mainline kernel as it is, not with out-of-tree
changes like new DTB/DTBOs. Use only upstream DTB/DTBOs. As that was the
last thing provided by ti-upstream-tools, remove it here.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Mainline should test the mainline kernel as it is, not with out-of-tree
changes like to the default configuration that one would get when using
a stock distro. Use only upstream configuration.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The check-layer command caught that we were missing the Upstream-Status
on a few older patches, and I found a few new ones.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
meta-arm now has all optee components updated to the latest 3.20 version
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Switch 32-bit beaglebone and beagle-x15 platforms to use linux-bb.org and
u-boot-bb.org recipes for simplicity and for additional Beagle-specific
features that are added on top of TI reference kernel, such as dynamic
management of capes and other OOBE enhancements.
Cc: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Add configs for BeaglePlay Cortex-A53 and Cortex-R5F cores (am62xx SoC family)
* Uses corresponding linux-bb.org and u-boot-bb.org recipes
* U-boot for now uses a separate branch for BeaglePlay
Cc: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* 5.10.162 added 2 new DT overlays
* Remove duplicate settings that are already set in SoC config
Cc: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use dedicated branch for BB-AI64 that includes recent changes for new
memory part.
Cc: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Update both 32 and 64-bit trees to 5.10.162
* Switch from using a common branch that gets periodically rebased to using
dedicated per-merge branches
* Patch 32-bit defconfig to use LZMA compression instead of LZO, that is
being deprecated in OE-Core
Cc: Robert Nelson <robertcnelson@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When trying to support OpenBMC, we found that our use of do_image_wic
and do_image_tar for adding depends and mcdepends was too limiting.
Moving to do_image_complete is a higher level in the tree that means
for any image type the dependencies will be correct.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
When sysvinit is in DISTRO_FEATURES, the update-rc.d class must only be
inherited when the script referenced by INITSCRIPT_NAME actually exists,
or the update-rc.d command in the generated postinst script will fail.
Reported-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Reviewed-by: Andrew Davis <afd@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are preparing to migrate our u-boot version to 2023.04. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this u-boot in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
2021.01 u-boot and make this the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
We are preparing to migrate our kernel version to 6.1. As we are still
working on the migration, mark the default preference low for this
version. We will enable building with this kernel in a meta-arago brand
in the near future. Once the migration is complete, we will remove the
5.10 kernel and make this the default.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We often carry more dtbs/dtbos in our kernel than we have upstreamed.
The inclusion of all of the dtb/dtbo in the KERNEL_DEVICETREE has become
problematic as we start testing the linux-next and 6.1 as part of our
LTS migration. To address this issue we are adding in two step method
for managing the KERNEL_DEVICETREE.
Going forward we will only accept dtb/dtbo in KERNEL_DEVICETREE if it is
available in upstream. This way we ensure that the variable is more
accurate for whichever kernel you might be looking at. We have also
added a new variable KERNEL_DEVICETREE_PREFIX which our kernel recipes
will use to auto set KERNEL_DEVICETREE based on what files are in the
kernel and not a fixed list in the conf files.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While we are mirgrating to kernel v6.1 and u-boot v2023.04, we want to
keep kernel v5.10 and u-boot v2021.01 "working" for anyone looking at
kirkstone. One of the items we are looking at changing is the signing
of entries in the fitImage.
To try and acheive a limited parity with dunfell while we work on the
migration, this commit creates a class that implements the logic that was in
dunfell and applies that class to the 5.10 kernel.
This is a temporary patch that will be remvoed when we remove the 5.10
recipe down the road. This logic will not apply to the 6.1 kernel.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are seeing some testing issues where the new code that signs all of
the files at all times is causing issues. So rollback the logic and
only sign for platforms that support it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are seeing some testing issues where the new code that signs all of
the files at all times is causing issues. So rollback the logic and
only sign for platforms that support it.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
After moving to the oe-core kernel-fitimage.bbclass we found that the
dtb names we were searching for did not match. This was due to the
KERNEL_DEVICETREE entries including the vendor subdir in the section
names of the fitImage file. This patch updates support in 2021 so that
we can temporarily get to a stable boot point before starting our LTS
migration and changing a lot of things in the recipes.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Doing multiple do_install:prepend overrides does not guarantee the
order - it was observed that signing could fail as it was happening
prior to symlinking to the correct name. Move signing code inside the
main do_install, so the machine-specific do_install:prepend works
correctly.
Also, pass -f flag for symlinking, otherwise it could fail with "file
already exists" error when trying to re-build the recipe again.
Several IPC list/matrix fixes:
* j721e was missing MCU_1_1_FW entry
* j721s2 was also missing MCU_1_1_FW entry
* j721s2 had a second MCU_2_0_FW in place of MCU_3_0_FW
* j784s4 was missing MCU_4_0_FW and MCU_4_1_FW entries
Other minor cleanups and indentation fixes.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SK-Ethernet-DC01 Add-On Ethernet Card for AM62A-SK board supports
RGMII mode.
Add overlay to enable the second CPSW3G port in RGMII-RXID mode with the
Add-On Ethernet Card.
Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the MCSPI loopback overlay file for J784S4 EVM which helps
users to enable MCU-MAIN MCSPI loopback applications, even though
the overlay is named j7200-mcspi-loopback.dtbo, same can be used
for testing on other J7 platforms as well.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the MCSPI loopback overlay file for J721S2 EVM which helps
users to enable MCU-MAIN MCSPI loopback applications, even though
the overlay is named j7200-mcspi-loopback.dtbo, same can be used
for testing on other J7 platforms as well.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the MCSPI loopback overlay file for J721E EVM which helps
users to enable MCU-MAIN MCSPI loopback applications, even though
the overlay is named j7200-mcspi-loopback.dtbo, same can be used
for testing on other J7 platforms as well.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add device tree overlay for extending support for mcu_uart0 as well as
wkup_uart0 for boards with J784S4 SoC. This overlay will mainly be used
for the purpose of testing uart instances.
Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add device tree overlay for extending support for mcu_uart0 as well as
wkup_uart0 for boards with J721S2 SoC. This overlay will mainly be used
for the purpose of testing uart instances.
Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add device tree overlay for extending support for mcu_uart0 as well as
wkup_uart0 for boards with J721E SoC. This overlay will mainly be used
for the purpose of testing uart instances.
Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add device tree overlay for extending support for mcu_uart0 as well as
wkup_uart0 for boards with J7200 SoC. This overlay will mainly be used
for the purpose of testing uart instances.
Signed-off-by: Bhavya Kapoor <b-kapoor@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The AM69 SK has PWM output pins connected to its RPi header. Add
overlay file to enable PWM pins.
Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The AM68 SK has PWM output pins connected to its RPi headers. Add
overlay file to enable PWM pins.
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the overlay files for AM69 SK:
1. Fusion board (For FPDLink-III cameras).
2. IMX390 FPDLink-III camera module that includes both the CM and
RCM type of modules.
Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the overlay files, over AM68 SK, for the following:
1. Fusion board (For FPDLink-III cameras).
2. IMX390 FPDLink-III camera module which includes both the CM and
RCM type of modules.
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The extension for OV5640 overlay is incorrect. Therefore, update the
correct extension to build the overlay with .dtbo
Fixes: f67e9805 ("conf: machine: j721s2: Add AM68 SK specific dtb and dtbo to KERNEL_DEVICETREE")
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
AM69 Starter Kit is a single board designed based on TI's AM69 SOC
providing advanced system integration in automotive ADAS applications,
autonomous mobile robot and edge AI applications. Add support
for the same to include the board dtb file into the root filesystem.
Add DT overlays support for the following features on AM69 SK:
* Add DTBO entry to support OV5640 camera
* Add DTBO entry to support RPi(IMX219) camera
* Add DTBO entry for the DDR memory carveout.
[1]:https://www.ti.com/lit/zip/spruj52
Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
IMX390 is a 2MP FPDLink-III raw camera. This sensor was originally
targeted for J7-based devices, but AM62A can re-use the existing
overlays. Both the CM and RCM type of modules are supported.
As AM62A only has one CSI-RX port, we only use 4 out of the 8 total
FPDLink ports on the fusion board.
Signed-off-by: Jai Luthra <j-luthra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
AM68 Starter Kit is a low cost, small form factor board designed for
TI's AM68/J721S2 SoC[1] which is optimized to provide best in class performance
for industrial applications. Add DTB entry for the same.
AM68 SK features camera support with MIPI(OV5640) and RPi(IMX219) connectors.
Add DTBO for the same. Also, add DTBO entry for the DDR memory carveout.
[1]:http://www.ti.com/lit/zip/spruj28
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the following overlay files on AM62A SK:
1. Fusion board (For FPDLink-III cameras)
2. OV2312 FPDLink camera module
3. IMX219 RPi-compatible camera module
Signed-off-by: Jai Luthra <j-luthra@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the basic J784S4 HS-FS configuration.
* Add configurations to support both HS-FS and GP keeping GP as default.
* Add ti-sci-firmware overrides for HS-FS.
* Remove evm conf file inclusion in hs-evm conf.
* Add j784s4 hs-evm specific config to hs-evm conf.
Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lets add the basic AM62A configuration
- Add machine conf for AM62A.
- The wic images will boot on AM62A HS-FS devices by default.
- The sysfw image for GP and HS-SE will be packaged in the wic image as
tiboot3-am62ax-gp-evm.bin and tiboot3-am62ax-hs-evm.bin respectively.
- Add ti-sci-firmware overrides.
- Sign ATF, OPTEE and RTOS Firmware.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the basic J721S2 HS-FS configuration.
- Add configurations to support both HS-FS and GP keeping GP
as default.
- Add ti-sci-firmware overrides for HS-FS.
- Remove evm conf file inclusion in hs-evm conf.
- Add j721s2 hs-evm specific config to hs-evm conf.
Signed-off-by: Aniket Limaye <a-limaye@ti.com>
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
With the advent of using multiconfigs to build all of the versions of
the machines (gp, hs-se, hs-fs, etc...) the sysfw.itb has become a point
of contention for do_deploy. To resolve the duplicate file copy errors
from bitbake we need to uniquify the sysfw.itb file names. So, let's do
the same thing we do with the tiboot3.bin file and add the SYSFW_SUFFIX
into the name.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lets add the basic AM62x LP HS-FS configuration
- Add machine conf for AM62x LP HS-FS.
- The wic images will boot on AM62x LP HS-FS devices by default.
- The sysfw image for HS-SE will be packaged in the wic image as
tiboot3-am62x-hs-evm.bin.
- Add ti-sci-firmware overrides.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lets add the basic AM62x HS-FS configuration
- Add machine conf for AM62x HS-FS.
- The wic images will boot on AM62x HS-FS devices by default.
- The sysfw image for GP and HS-SE will be packaged in the wic image as
tiboot3-am62x-gp-evm.bin and tiboot3-am62x-hs-evm.bin respectively.
- Add ti-sci-firmware overrides.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
K3 platforms include the FIT image-based kernel by default. The bootloader
loads the kernel and DTB from the FIT image. The DTB/DTBOs are added to the
FIT image but the load address is not included in the image section of
each DTB/DTBO. This load address is determined by the LOADADDRESS macros
in the kernel-fitmage class.
Hence, define the RD/DTB/DTBOs LOADADDRESS and OFFSET macros in the K3 common
include, and remove those macros defined in the K3 board specific config files.
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Reviewed-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This installs shared OPTEE-OS APIs and needs to match in order for latest
client/test/examples to be able to build.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OPTEE tests is not being upgraded due to a newer python dependency for
the build
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lets add the basic AM62x HS-SE configuration.
- Add machine conf for AM62x HS-SE.
- The wic images will boot on AM62x GP devices by default.
- To boot on AM62x HS-SE, simply switch out the SYSFW image:
$ cd /mnt/sd-card/boot
$ mv tiboot3-am62x-hs-evm.bin tiboot3.bin
- Add ti-sci-firmware overrides.
- Add support to sign ATF and OPTEE.
Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update the SHA of k3conf to pickup am62ax support
Signed-off-by: Bryan Brattlof <bb@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upgrade arm-trusted-firmare to v2.8-226-g2fcd408bb.
This upgrade picks up K3 L2 cache, snoop delayed, and EA
handling updates from upstream master.
Do not update to tip of master due to PSCI system off
support breaking AM62x and AM62q platforms.
Signed-off-by: Judith Mendez <jm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Tested-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit 98506a4a07 ("optee-os: Update SRCREV for OP-TEE TRNG in AM62X")
Disables SW PRNG => Enabling Hardware RNG. This is breaking Suspend Resume
on AM62xx EVM variants. To fix this keep using SOFTWARE_PRNG enabled as
it was.
Cc: vibhore@ti.com
Cc: Andrew Davis <afd@ti.com>
Signed-off-by: Dhruva Gole <d-gole@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In addition to releasing the signed versions of the bl31.bin and
bl32.bin files, also release the unsigned original versions.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lower the log level for am62axx platform
commit 27641e1f2d ("optee-os: Lower log level for AM62x")
changes the log level for am62xx platforms.
This patch is to extend the same for am62axx
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reported-by: Sai Sree Kartheek Adivi <s-adivi@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
optee-os is already at 3.20 tag but the others were still outdated.
Updates other optee components to 3.19 tag
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While removing SOFTWARE_PRNG support
commit:98506a4a07363a1b57012ccfaee263f47e5b46c4,
accidently removed the changes applied
by commit:27641e1f2d7f6696fd7bbd8f24fcac20766b6234
(optee-os: Lower log level for AM62x).
Reverting those changes back
Signed-off-by: Kamlesh Gurudasani <kamlesh@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
With a recent patch to the TI kernel that includes debug symbols,
the vmlinux.gz file grew in size that impacted the testing.
This file is not needed to be in the final image so remove it
from the list.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Changes to support new j784s4-hs platform in:
1) ti-sci-fw_git: Update firmware prefix for j784s4-hs
2) atf: sign the image
4) optee: sign the image
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Machine conf for J784S4 HS platform.
Used J721S2 hs as reference.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Having signed firmware is needed for the HS platforms, but does not
cause any issues for non-HS. To keep things simple, let's deploy
both sets unconditionally. This prevents mistakes when adding HS
support and further reduces the image delta between the two types.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Firmware belongs in the nonarch lib directory. Use the right variable.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Using a table makes it easier to see what firmware is included with
each machine build. It also helps prevent errors here.
Since the same functions run across machines we now sign all the firmware
without needing to add a new signing function for each new machine.
Another fix is that we install the DM firmware to the deploy directory
for all machines that use need it. This was added for J7x machines
but missed for AM62x.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This allows us to change the name in one spot and avoid duplication.
It also helps prevent hard to see changes/typos in the firmware names.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
If we rename files in the source directory the next time we need to rebuild
the original files will be gone and build will fail. Use symlinks instead.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The firmware for AM64x and AM62x are renamed to match the other platforms,
but we don't actually change them to match. Remove baremetal from the
names.
These are only referenced to by softlink, so this change will have no
effect on Linux users.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since these TARGET defines are only used on the machine for which
an ALTERNATIVE is defined and always have the same name, these
provide nothing. Drop them.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since this directory path will not change, let's avoid use
of ti-paths.inc which is set to be removed.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
For K3 machines the SECDEV selection happens in the recipes that use it.
This assignment is therefor no longer needed. Remove it.
Suggested-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use the new ti-k3-secdev package to pull in the signing tools if they are
not provided by the environment.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use ti-k3-secdev native package to provide secure-binary-image.sh script
when it is not passed on as an environment variable. This fixes an issue
with AM64xx which is always HS but should not require TI_SECURE_DEV_PKG
when building for HS-FS or GP platforms.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use the new ti-k3-secdev package to pull in the signing tools if they are
not provided by the environment. This allows us to use these tools
unconditionally. Remove the checks for the script and do the signing
for all K3 machines. The signature is automatically stripped from
the binaries on non-HS devices at boot time as needed so this change
is harmless for GP devices.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use the new ti-k3-secdev package to pull in the signing tools if they are
not provided by the environment. This allows us to use these tools
unconditionally. Remove the checks for the script and do the signing
for all K3 machines. The signature is automatically stripped from
the binaries on non-HS devices at boot time as needed so this change
is harmless for GP devices.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use the new ti-k3-secdev package to pull in the signing tools if they are
not provided by the environment. This allows us to use these tools
unconditionally. Remove the checks for the script and do the signing
for all K3 machines. The signature is automatically stripped from
the binaries on non-HS devices at boot time as needed so this change
is harmless for GP devices.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The setup here is common to all packages that require signing with
the TI Security Development Tools. Add a helper class to factor out
this commonality.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While here update FW versions and remove those no longer used.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-img-rogue-umlibs package is not obeying usrmerge distro feature. /lib should be relocated to /usr. [usrmerge]
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Some machine configs didn't specify their use of screen and touchscreen
machine features correctly, fix them.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While we are working to update our platforms to support Weston 10 and
beyond, we are falling back to software rendering for platforms that do
not currently have a solution for GPU drivers (namely the boards that
use SGX).
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Set SGX display controller alias variables accordingly, as SGX has a few
different aliases across platforms.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove default preferences for virtual/egl, virtual/libgles and virtual/libgbm
from machine configs to follow the new dependency chains via mesa in oder to
support accelerated and software-rendered graphics, which is selected by
virtual/gpudriver preference.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Patched mesa will now be configured based on what virtual/gpudriver
preferred provider is selected. The gpu drivers will now runtime
recommend the associated UM components.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Locally overlay verbatim copies of mesa 22.0 patches from oe-core/kirkstone,
so the same codebase works in kirkstone and master. Since upstream version
of mesa in master is now 22.3 and no longer carries these patches, but they
are still needed for 22.0-based PVR fork of mesa used with Rogue driver.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
While we are working to update our platforms to support Weston 10 and
beyond, we are falling back to software rendering for platforms that do
not currently have a solution for GPU drivers (namely the boards that
use SGX).
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Attempt to update the SGX display controller alias variable according to
what Andrew told me. SGX apparently had a few different aliases across
platforms.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove all gpu machine features and instead rely on the new dependency
chain for resolving gpu dependencies. Set preferred providers for
virtual/gpudriver where needed.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Patched mesa will now be configured based on what virtual/gpudriver
preferred provider is selected. The gpu drivers will now runtime
recommend the associated um components.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Original READMEs with bootflows were reworked and moved to a dedicated doc/
folder in more recent U-boot versions. Update links in the k3r5 config file
accordingly to provide some basic explanation of K3 bootflows.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
UIO drivers are generally frowned upon in the community, and for PRU
we now have much better alternatives in RProc, RPmsg, and PRU-Consumer.
Let's not send the wrong message by continuing to support this crufty
interface. Remove the kernel module, DTBs, and test recipe.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
BeagleBone AI-64 (https://beagleboard.org/ai-64) uses Texas Instruments
Jacinto TDA4VM/J721e SoC. Officially BeagleBone AI-64 supports Debian
Linux and builds its BSP on top of meta-ti and TI SDK, but adds custom
DTBs and DTBO overlays, plus integrates other drivers and features.
Let's add corresponding recipes for beagleboard.org kernel and u-boot
along with the BeagleBone AI-64 machine config.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The ti-sgx-ddk driver requires an additional userspace initialization
step after the kernel module has probed the device. Without this
initialization, no EGL context can be created and Weston etc. will fail to
start.
The driver package contains an init script, but this does not work on pure
systemd-based systems without sysvinit compat support (as provided by the
systemd-compat-units package). Introduce an enabled-by-default
PACKAGECONFIG that installs a udev rule instead to run the init command
automatically when the driver is loaded, solving the issue without
depending on a specific init system. On builds without udev, this
PACKAGECONFIG can be disabled, reverting to the old init script-based
solution.
udev reports several events when the pvrsrvkm module is loaded:
- add event for the kernel module
- add events for two DRM devices
- bind event for the GPU platform device
The DRM devices aren't nice to match on, and the kernel module add is
too early to run `pvrsrvctl --start`, so we trigger on the platform
device bind.
Tested with Weston 9.0.0 on the AM65x-based TQ-Systems MBa65xx.
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These URIs have been updated in dunfell, but two instances were
forgotten in kirkstone/master.
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The TI_K3_SECDEV_INSTALL_DIR is defined on the meta-ti-extras layer
so when the layer is not used the variable is undefined.
For such cases we can use default value that is the same defined
on the recipes-ti/includes/ti-paths.inc
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The TI_K3_SECDEV_INSTALL_DIR_RECIPE is defined on the meta-ti-extras layer
so when the layer is not used the variable is undefined.
For such cases we can use default value that is the same defined
on the recipes-ti/includes/ti-paths.inc
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Acked-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The meta-ti-bsp layer is still broken for K3 HS platforms.
The patch [1] makes the check-layer happy again as it does not
fail any more during bitbake parsing but it will be difficult
for the end user to discover this dependency on meta-ti-extras.
On the other side, meta-ti-extras depends on meta-ti-bsp so
this is a circular dependency.
Currently the layer is broken for am62xx-evm/am64xx-evm machines:
| ERROR: Nothing PROVIDES 'ti-k3-secdev-native' (but mc:k3r5:/srv/oe/build/conf/../../layers/meta-ti/meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb DEPENDS on or otherwise requires it). Close matches:
| libtspi-dev-native
| makedevs-native
[1] - 8e43835c ti-sci-fw: make dependency on meta-ti-extras soft
Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Acked-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The WIC image for K3 depends on the TI-SCI firmware, on AM65x and J721e
also the bootloader. Make this clear by only depending on firmware in
the base k3.inc file, then adding the bootloader dependency in AM65x and
J721e specific includes.
Remove unneeded overrides from the evm level files.
Remove do_image_tar dependencies as the tar files do not include
the bootloader nor TI-SCI firmware, only the boot partition of
the WIC file needs these.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These defines are specific to a SoC, not a SoC family (K3) nor
any specific board. Move these to the SoC level for all boards
to be consistent with boards already doing this correctly.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This was used in the base Linaro optee-os_git.bb recipe, it is
no longer used, remove it from our boards.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
J7 is an unneeded level of grouping that is now causing issues and
leading to mistakes when adding new J7 based platforms. Each J7x
family device should use the SoC name specifically to prevent
accidentally adding or removing features that are not meant
for the new SoC.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Now that we have SoC names, we can avoid adding features based on the
board name. We expect folks to create their own boards based on these
SoCs, and so using the TI made EVM board name everywhere adds extra churn
when adding a new board. Plus it is more correct for most of these
features as they depend on the SoC, not on the EVM board.
One other thing we do here is to not use the generic "j7" name,
the current and future J7 devices are far to feature diverse
to group at this level. Grouping like that will lead to the wrong
things getting enabled as new J7 SoCs are added.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Like we do with J721e, J7200, and J721s2, use a SoC header include file
to define common properties. This eases adding new boards based on these
SoC.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Multi-cert is already now the default, no need to add a comment on that.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Upstream meta-arm has updated optee-os to 3.19 and our local changes
conflict with that. Update bbappend to match upstream.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These were in the meta-arago layer, but any distro should be able
to run on HS devices. So move the classes and setup to the BSP layer.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In many spots we have to use the full EVM name for each EVM using the
AM57x SoC leading to missed features on some EVMs. Add the am57xx name
so we can generically add for AM57x.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Rather than just support mickledore we should also support the other
layers that we still support to ensure that as many as different
versions we can.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move to setting the values for PREFERRED_PROVIDER using the
?= default assignment so that we can override the setting if
we would like to.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There were fuzz errors with the patch that needed to be cleaned up,
and for some reason a v2 that was supposed to move the duplicate
patches in files/ was not pushed properly before merging.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These bbappends were bumping versions to 3.17 when upstream only provided
3.16 version. Now that upstream meta-arm provides 3.18 versions, there's
no need for the bbappends, especially since they break in do_install.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Replace "require" with "include" to load ti-paths.inc and not break
parsing when meta-ti-extras is not in the BBLAYERS list.
As ti-paths.inc is only needed to define TI_K3_SECDEV_INSTALL_DIR
for ti-k3-secdev when TI_SECURE_DEV_PKG_K3 is not set and building
for K3 HS platforms. Since ti-k3-secdev resides in meta-ti-extras,
the soft dependency will still work fine and give a build error
"Nothing PROVIDES 'ti-k3-secdev-native'" when it is needed.
Also, since TI_K3_SECDEV_INSTALL_DIR can now be undefined, use
d.getVar() to access it ensuring it doesn't break the condition.
Reported-by: Daniel Díaz <mrchapp@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update_data() was removed from upstream bitbake, so we should remove
the call from our code as well.
584989ed2b
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
These patches are from upstream against v3.18, but we moved to v3.19 and the
patches are now invalid. These can be removed once upstream moves up to or
beyond v3.19.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Cleanup and unify again - omapl138-lcdk is the only platform supported in
the OMAP-L1 family. Plus there's no longer DaVinci family with corresponding
settings. Adjust accordingly.
Please note, there's currently a bug building Rust on ARMv5 platforms:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14967
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
CMEM has been deprecated for removal for some time now. All users should
have migrated to the Linux upstream DMA-BUF Heaps framework. Remove CMEM.
We only remove the kernel module part in this patch to prevent builds
from breaking in the meta-arago layer due to dependencies on the CMEM
library. These packages should either be updated or disabled. After
that we will remove the library.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest upstream master which is 3.19.0.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the source revision for the rogue pvr kernel module.
Source changelog:
- A hack was added to increase stability on J7 platforms while we are
looking into a proper fix for cache coherency issues in this module
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Otherwise undefined variable is returned literally as ${TI_SECURE_DEV_PKG_K3}
and the condition won't work.
Cc: Andrew Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Include ti-paths.inc so TI_K3_SECDEV_INSTALL_DIR_RECIPE gets defined and
artifacts are installed in the correct location.
Cc: Andrew Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update firmware name to wave521c_k3_codec_fw.bin to align with
linux-firmware main branch. the following patch is part of
ti-linux-firmware thru mainline sync.
commit 48407ffd ("cnm: update chips&media wave521c firmware.")
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OP-TEE upstream now has support for sa3ul for j721s2 platform.
Re-enable the trng driver which was disabled earlier.
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Change the OP-TEE flavour from default k3-j721e to k3-j784s4
as sa3ul support for j784s4 is upstreamed in OP-TEE and we
can use the same settings in j721s2 to access TRNG.
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add the new OP-TEE flavour for J784S4 instead of default k3-j721e.
The TI-SCI ID for MCU domain sa2ul/sa3ul are not the same for
J721E and J784S4. So a new flavour is added in upstream OP-TEE.
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the SRCREV to the commit when sa3ul support was
added in upstream OP-TEE for J784S4 platform to access rng.
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Serial console in J721S2/J784S4 EVM config was set to ttyS10. It should be ttyS2.
This caused sysv based systems (eg, tiny) to apparently hang because of no login prompt.
This didn't show up as a problem on systemd systems (eg, default) because systemd will
automatically setup a serial tty with the console option passed in on the kernel command line
(using console=...), which U-Boot correctly passes in as ttyS2 for J721S2/J784S4.
Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump the graphics recipes source revision and remove the old BVNC
switch. The BVNC is now baked into the platform Makefile that is
selected with PVR_BUILD_DIR / TARGET_PRODUCT.
Signed-off-by: Randolph Sapp <rs@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Notable changes include support for J784s4.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We missed a spot when updating all of the git access for git.ti.com
to use HTTPS.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the ti-rpmsg-char library to 0.5.1 version that enables the
support for R5F on am62x SoCs.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
devtool has a long-standing bug where it cannot handle references to ${WORKDIR}
due to externalsrc:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12677
linux-ti-mainline clones additional ti-upstream-tools repo alongside the kernel
sources into ${WORKDIR}, which exposes this devtool bug.
Work around the issue by moving ti-upstream-tools inside the kernel source tree,
i.e. inside ${S}
Reported-by: Radoslav Pesek <radoslav.pesek@microstep-mis.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The supported device types depends on the SoC, not on any specific
board or EVM. Any board can be populated with any of the 3 supported
AM64x types. Move these into the AM64x common include.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
AM64x devices will only be available as SR2.0 HS-FS. Set this as the
default type provided by the SDK. To allow SR2.0 HS-SE to continue to
boot, like we did with GP, we add an extra machine to build SR2.0 HS-SE
SYSFW. To use on SR2.0 HS-SE boards simply switch out the SYSFW image:
$ cd /mnt/sd-card/boot
$ mv tiboot3-am64x_sr2-hs-evm.bin tiboot3.bin
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
cdns mhdp bridge is present in j721s2 soc.
Add the dependency for the same
Signed-off-by: Rahul T R <r-ravikumar@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Switch the DEPENDS_append expression to use d.getVar() instead of the
usual variable expansion to prevent the inline Python command from
becoming mangled.
Signed-off-by: Randolph Sapp <rs@ti.com>
Acked-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
During resume from low power mode suspend OP-TEE prints some messages
on the UART. It seems this UART is not powered at this point in the
sequence breaking suspend/resume. We should track down the exact
prints and quiet them. Until we get that fix upstream, lets lower
the log level for this platform to unblock the LPM work.
Signed-off-by: Andrew Davis <afd@ti.com>
Acked-by: Anand Gadiyar <gadiyar@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest upstream master which is 3.18.0.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This platform is similar to the currently supported am62xx-evm, except
that we currently need new defconfigs for u-boot and new dtbs in the
filesystem.
Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
Cc: Hari Nagalla <hnagalla@ti.com>
Cc: Andrew Davis <afd@ti.com>
Cc: Praneeth Bajjuri <praneeth@ti.com>
Cc: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In the latest U-Boot the HS images for AM64x have been renamed to the
default names, and the GP have been changed to *_unsigned. Remove
the overrides to pull the now default HS images.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The HS-SE AM64xx machine can now be run on GP devices and built without
needing the TI_SECURE_DEV_PKG for the same. AM64xx will only be available
in the HS-FS type going forward. Make the HS-SE the default and remove
the original GP machine.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest commit of ti-u-boot-2021.01.
As part of this U-Boot update the non-HS AM64x-evm defconfig was removed.
This is okay as building this defconfig without defining TI_SECURE_DEV_PKG
will still result in usable binaries for the non-HS devices. Use the
HS defconfig for both the HS and non-HS machines.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This machine was missed when making combined R5 boot the default.
Add this machine to fix build failure.
Reported-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In order to support fitImage image type, kernel-fitimage class is needed.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
FIT Image based kernels are valid for all K3 devices, not just HS, deploy
this kernel image type by default so it doesn't have to be appended on
a per-device-type basis.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use multiconfig to generate a GP SYSFW image. This allows the HS SDK
to be used on GP boards by simply switching out the SYSFW image:
$ cd /mnt/sd-card/boot
$ mv tiboot3-am64x-gp-evm.bin tiboot3.bin
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This recipe deploys the raw SYSFW unconditionally which causes issues
when doing multiconfig builds. What should happen is only one deploys
these, select that the same way we select which one deploys the default
SYSFW symlink. Move the deploy step there.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The K3 TI_SECURE_DEV_PKG is the same for all devices, move this out
of each machine file and into the common K3 includes. This doesn't
have any effect on the GP machines as they make no use of it.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add SYSFW_TIBOOT3_SYMLINK and use it the same way we use SYSFW_SYMLINK
for the non-combined boot flow, to allow not setting the default for
some machine types.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Going forward, the combined tiboot3.bin is going to be the standard. Only
AM65x and J721e will still use the split boot.
Set DEPENDS and EXTRA_OEMAKE for combined boot and override only for the
two split boot platforms. This makes it easier to add new platforms and
simplifies deployment logic.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Currently we reuse UBOOT_* names which usually are the same we
want to give to the name of the SYSFW binary. This isn't always
correct, we should use a SYSFW specific variable in case the
UBOOT names are changed.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This allows us to rebuild and re-sign the SYSFW image if needed from
the deploy directory for any SoC type.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The k3-image-gen now has two new helper flags SOC_TYPE and SYSFW_DIR
that we can use to simplify this recipe. With these we do not need to do
anything different here for HS builds, the SOC_TYPE selects this now.
DL_URL also do not need cleared anymore, the k3-image-gen will no longer
download missing files when not needed for the current build type.
do_install and do_deploy can also check for the existence of either
sysfw.itb or tiboot3.bin and install/deploy as needed. k3-image-gen only
gerneates the right one now depending on the SoC. Merge all these
steps for all SoCs.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Going forward, the combined tiboot3.bin is going to be the standard. Only
AM65x and J721e will still use the split boot. Set the output of U-Boot
to be u-boot-spl.bin by default and override only for the two split boot
platforms. This makes it easier to add new platforms and simplifies
deployment logic.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Required for daily test plans. Can be enabled in local.conf or <distro>.conf:
PREFERRED_PROVIDER_virtual/kernel = "linux-ti-next"
SRCREV:pn-linux-ti-next = "${AUTOREV}"
Only uses in-tree defconfigs, does not support config fragments, builds and
packages in-tree DTBs.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest release version.
bzip2 license was added to the list, update checksum.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
lzop support has been moved from oe-core to meta-oe. Since we are not
setting FIT_KERNEL_COMP_ALG and (for minimal poky builds) we would like
to not require meta-oe just for this, just remove the dependency entirely.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This makes sense but looks like was done wrong to match AM65xx which
needed the exact EVM specified due to this only working on SR2.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We already cd into DEPLOYDIR so this is not needed. This now matches the
keystone version below. Also fixes build in some odd situations.
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Only the first two K3 devices do not support multi-cert boot so
lets make multi-cert the default and only add back sysfw.itb
for these two devices.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: lines be preserved?
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.04.01.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.04.01.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.04.01.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
For the upcoming CICD flow we need to control the branch for
all of the needed packages.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This firmware is only applicable to the j721e platform and not
all j7 devices.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.04.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.04.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.04.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
devtool does not work with the current formulation of
the LOCALVERSION variables. We need to use SRCPV to
avoid AUTOREV on bleeding builds, but there will be no
+ in the string, so we cannot split on that. Just
use SRCPV directly.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
With J7200 PG1.0 being deprecated, use PG2.0 sysfw when building images for j7200-hs-evm.
Also update k3-image-gen version to support this change.
Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update the SHA for k3conf to pickup the j721s2 fixes
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Commit bdceaa05ac added SR1.1 support for
J721e HS with the idea that the default sysfw.itb will point to SR1.1.
For that to work, the config for SR1 has to explicitly disable creating
such symlink.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The test app is not compatible with later versions of j7, so
add COMPATIBLE_MACHINE to lock these recipes down to just
j721e.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Avoid the inclusion of device tree files that do not exist upstream
when virtual/kernel is linux-ti-mainline for the am43xx machines.
Signed-off-by: Drew Fustini <dfustini@baylibre.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Avoid the inclusion of device tree files that do not exist upstream
when virtual/kernel is linux-ti-mainline for the am57xx-evm MACHINE.
Signed-off-by: Drew Fustini <dfustini@baylibre.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Avoid the inclusion of device tree files that do not exist upstream
when virtual/kernel is linux-ti-mainline for the dra7xx-evm MACHINE.
Signed-off-by: Drew Fustini <dfustini@baylibre.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.04.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.04.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.04.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The following commits in ti-linux-5.10.y kernel has introduced a new dtb.
commit: 9b05b2a89ff ("arm64: dts: ti: Add overlay for GESI to enable main CPSW2G in J721S2")
This patch on j721s2 conf is to include the new dtb.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The SA2UL driver now works on HS devices, unblock this.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The TRNG driver is not currently functional for these two platforms.
Disable the TRNG driver until fixed.
Reported-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.04.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.04.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.04.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch is to align with a recent change to how the HS platforms
are setup in the /boot partition.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.04.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.04.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.04.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.04.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
IMAGE_BOOT_FILES was being overwritten in the HS recipes leading to
incomplete binaries in /boot and the naming of the binaries were not
correct.
Fixes /boot partition for HS devices.
Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
[afd: Extended fix to all HS platforms]
Signed-off-by: Andrew Davis <afd@ti.com>
Acked-by: Manorit Chawdhry <m-chawdhry@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
update the SHA of k3conf to pickup j721s2 support
Signed-off-by: Bryan Brattlof <bb@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update to the latest upstream master which is 3.17.
We do this to add HUK and AM64x/AM62x support.
With this we need to also switch OPTEEMACHINE for AM64x/AM62x.
To build against the latest OP-TEE the support recipes need updated also.
Move these here into meta-ti so that builds will still work when not using
meta-arago-distro.
The fix patches do not look to be needed anymore.
While here switch to git checkout with https.
NOTE: The latest OP-TEE requires SYSFW 8.04+
Signed-off-by: Andrew Davis <afd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
For TF-A we work against upstream first, our fork has only been
used in the rare cases we need to ship a feature before we can
get it upstream. This is not currently the case so lets switch
to upstream repo until there is a need for our fork.
Signed-off-by: Andrew Davis <afd@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.04.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.04.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.04.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.04.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Sign the DM firmware for j721s2 similar to j7200 hs.
Duplicate all j721s2 entries for j721s2-hs as we cannot use same
keyword for match between j721s2-evm and j721s2-hs-evm.
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Machine conf for J721S2 HS platform.
Used j7200 hs as reference.
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.03.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.03.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.03.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.03.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The following commits in ti-linux-5.10.y kernel has introduced new dtbs.
a minimal skeleton and a lpm (low-power-mode) demo dtb.
commit c161df7b1ea0 ("arm64: dts: ti: Introduce k3-am625-sk-lpmdemo")
commit 61df7fcf9307 ("arm64: dts: ti: introduce minimal dt for am625")
This patch on am62xx conf is to include the new dtbs.
Reported-by: Dave Gerlach <d-gerlach@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.03.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.03.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.03.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.03.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The file extension for the overlay needs to be .dtbo.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The DM firmware binary is required for building uboot binaries for
am62xx-evm using toplevel makefile in SDK. Add this file to deploy
directory so it can be included in prebuilt-images directory of SDK
for am62xx-evm.
Signed-off-by: Aparna M <a-m1@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Pull in the GPU KM/UMLIBS that enable the unified 4K/64K page
firmware support in the IMG Rogue drivers.
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fixes this warning:
| WARNING: dsptop-1.4.0-r2.2 do_package_qa: QA Issue: dsptop: /usr/bin/dsptop is owned by uid 1000,
| which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Fixes these warnings:
| WARNING: libdce-3.00.14.00-r1 do_fetch: URL: git://git.omapzoom.org/repo/libdce.git;protocol=git
| does not set any branch parameter. The future default branch used by tools and repositories
| is uncertain and we will therefore soon require this is set in all git urls.
| WARNING: libdce-3.00.14.00-r1 do_unpack: URL: git://git.omapzoom.org/repo/libdce.git;protocol=git
| does not set any branch parameter. The future default branch used by tools and repositories
| is uncertain and we will therefore soon require this is set in all git urls.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.03.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.03.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.03.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update build flag for arm-trusted-firmware to include low power mode
support
K3_PM_SYSTEM_SUSPEND is added in arm-trusted-firmware now which enables
low power mode support for am62xx.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
upgrade arm-trusted-firmare to master which is currently v2.6+
This upgrade picks up am62x low power mode feature.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This firmware stub is required by the TI foundational security
software while transitioning to low power mode.
Add a recipe for this compatible with am62xx-evm
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As append override does not add any whitespaces, it could lead to potential
issues when two items in space-separated list get concatenated. It is always
recommended to add a leading whitespace in such cases, like EXTRA_OEMAKE.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
FILES:${PN} is being assigned twice, remove duplicate.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
meta-ti does not provide official X.org support, so no reason to set any
defaults, just assume the ones from OE-Core.
Also, drop setting MACHINE_GUI_CLASS, which is now only used by the kernel
from meta-openembedded to determine the size of the Tux during boot. Keep
those for now in community Beagle machines.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Use weak assignment for default PREFERRED_PROVIDER values to allow user to
easily overwrite them from local.conf.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Specify default 3D GLES/EGL providers for platforms using SGX and Rogue GPUs,
both kernel and user-space components.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In most cases machine features should be set in the corresponding SoC config
to be applicable to different machine variants, like GP, HS or custom board.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The module can not be compiled without patching kernel 5.10
This helps meta-ti to live in multi-BSP envs
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
meta-arm commit e03b824d7824 ("arm/optee-os: cleanup recipe") changed the
recipe's do_compile(), which broke the build of the am57xx-hs-evm and
dra7xx-hs-evm machines. Adjust the .bbappend accordingly.
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Point to an updated SRCREV that fixes a compile error with the clang
compiler.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ERROR: cmem-mod-4.20.00.01+gitAUTOINC+86269258a4-0a do_package: QA Issue: cmem-mod: Files/directories were installed but not shipped in any package:
/lib/modules/5.10.100-g4a12bec7d3/extra/cmemk.ko
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Explicitly cast the value into correct type to fix this error:
| .../services/server/devices/rogue/rgxinit.c:1345:36: error: implicit conversion from 'enum <anonymous>' to 'IMG_BOOL' {aka 'enum tag_img_bool'} [-Werror=enum-conversion]
| 1345 | bEnableAPM = false;
| | ^
Cc: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.03.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.03.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.03.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.03.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the k3conf to the latest SHA.
This adds AM62x support.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add missing k3-am625-sk-csi2-ov5640.dtb required for the camera overlay.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the ti-rpmsg-char library to 0.4.1 version that enables the
support for AM62x SoC family remote processors.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.03.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.03.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.03.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This commit adds the PRU Software Support Package (PSSP) to the AM62x Linux
Processor SDK under example-applications/pru-icss-x.x.x. It also adds prebuilt
PRU firmware to the default AM62x filesystem image under the /lib/firmware
folder.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the SDK folder example-applications/pru-icss-x.x.x to install the latest
version of the PRU Software Support Package (PSSP).
This also uses PSSP v6.1.0 to generate the PRU Halt and RPMsg binaries in the
Linux SDK default filesystem image under /lib/firmware.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Enable the GPU for am62xx and j721s2 and use IMG DDK 1.15
Migrate Imagination DDK 1.13 to DDK 1.15 for J721e
Signed-off-by: Darren Etheridge <detheridge@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.02.00.006
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.02.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.02.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.02.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.02.00.005
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.02.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.02.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.02.00.004
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
ti-sgx-ddk-um's do_install creates a symlink libGLESv2.so.1 to
libGLESv2.so. As this symlink will be installed to ti-sgx-ddk-um, but
its target libGLESv2.so is in ti-sgx-ddk-um-dev, the automated
dependency analysis will add ti-sgx-ddk-um-dev to ti-sgx-ddk-um's
RDEPENDS. This will pull in a large number of other -dev packages
through RDEPENDS and RRECOMMENDS in turn.
Avoid this by having libGLESv2.so.1 point to libGLESv2.so.2 instead of
libGLESv2.so, so the symlink's target is in ti-sgx-ddk-um as well.
Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
To allow a consistent experience across current devices, enable wic.bmap file
generation for AM3/4/5 images.
Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
bitbake git fetcher warns about protocol and fall back branches
therefore be explicit about these parameters in source uri
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The AM65xx is the only member of the K3 family with an SGX GPU.
Be specific here to avoid confusion.
Signed-off-by: Andrew Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
There are now three SoCs in the J7 family, but only the j721e variant
is currently supported. Be specific here.
Signed-off-by: Andrew Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This allows us to be more specific around what SoCs we support and
lets us add features based on the SoC family not just at the EVM or
whole J7family level.
Signed-off-by: Andrew Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
In many places we use "j7" the family when we should be using a
specific SoC or EVM and vice-versa. For instance when including
graphics drivers we add for all "j7" family, but what we really
want is only for some specific j7 SoC.
First step in untangling this is to make it clear that there is
no SoC called j7. There is a SoC called j721e with a j721e-evm.
Fix up this naming here.
Signed-off-by: Andrew Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add README for the newly added meta-ti-extras layer and update the maintainer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.02.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.02.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.02.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.02.00.003
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.02.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.02.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.02.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.02.00.002
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The VIP camera capture driver recently ported to ti-linux-5.10.y adds
a DT overlay for the OV10635 camera sensor. Add this to
KERNEL_DEVICTREE so it's added to the artifacts.
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We need to control both the source name of the firmware and
the target name, so split the current variable into two and
update the install command.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the ti-linux-fw version for 08.02.00.001
- Changed CORESDK_RTOS_VERSION version to 08.02.00.04
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the u-boot version for 08.02.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux rt version for 08.02.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Updated the linux version for 08.02.00.001
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the ti-rpmsg-char library to 0.4.0 version that enables the
support for j721s2 SoC family remote processors.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We are now using binman to generate the images for
K3 AM64 in u-boot.
tools/binman/binman needs python3-setuptools so add it to
DEPENDS.
Reported-by: Praneeth Bajjuri <praneeth@ti.com>
Suggested-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Roger Quadros <rogerq@kernel.org>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The original recipe listed the compatible platforms to
all of j7, but at this time it is limited to j721s2-evm.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This reverts commit d29025f7e8.
* associated fix in k3-image-gen is picked up now.
commit 892c86501ff7 ("Makefile: Skip signing of binaries for HS combined boot")
hence its no longer needed to carry the same fix from meta-ti here.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update ti-linux-firmware and k3-image-gen to
pick latest TIFS and DM v2022.01
This version also adds support to j721s2
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update the name of the firmware for j721s2 as the file
was renamed. Also, fix a typo in the variable name.
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lets fix the missing switch firmware binary to point to ping binary
instead. If we attempt to start alternate CPU, we get a very beserk
system.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add firmware recipe to add the Wave521cl firmware pieces in for j7
platform.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Dont forget the alternate-target as well.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lets keep ethernet switch firmware disabled till we can actually
integrate it.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Lets enumerate the C7x target instead of defaulting as a since C7x.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Actual systems may choose to use a different console from the default
Allow the machine configurations to describe the same. Since the
option provided is custom to TI K3, make this a k3 product override
capability.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Actual systems may choose to use a different console from the default
Allow the machine configurations to describe the same.
Since the option provided is custom to TI K3, make this a k3 product
override capability.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Firmware images should always be installed under /lib and hence should use
nonarch_base_libdir, as regular base_libdir is configuration-specific and
doesn't always resolve to /lib.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
base_libdir is not configuration safe while firmware binaries
should always be deployed to /lib. In configurations where
base_libdir is not /lib the firmware gets deployed to wrong
paths.
This is fixed by using the nonarch_base_libdir which is
configuration agnostic.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The AM335x SoC has a built-in 16bit/24bit RGB LCD controller, and
the BeagleBone Black uses an external chip to convert this to HDMI.
But the SoC does not have a video output port per-se, thus the "screen"
machine feature does not belong to its configuration but rather to
the machine configurations.
Move the feature (and the MACHINE_GUI_CLASS definition) out of
ti33x.inc into am335x-evm.conf and beaglebone.conf respectively.
At the same time, drop the irrelevant comments regarding the external
screen, since MACHINE_GUI_CLASS is unlikely used and the BeagleBone
Black has a micro HDMI port, not a DVI port.
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Require kernel image and device tree as machine-specific packages with
MACHINE_ESSENTIAL_EXTRA_RDEPENDS instead of appending IMAGE_INSTALL.
This binds the packages to the packagegroup-core-boot package group,
allowing one to skip their installation, e.g. for container trees.
This patch reflects commit d4cbe0e43393 [1] from meta-yocto-bsp
("beaglebone-yocto: move kernel and dtb to packagegroup-core-boot").
[1] https://git.yoctoproject.org/meta-yocto/commit/?id=d4cbe0e43393ec70e98caf006372b5311597d377
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move TI Unified Instrumentation Architecture in C (cUIA) to meta-ti-extras under
recipes-devtools.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Some .inc file now span across layers, so use fuller path to find them when
including.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Those were moved from meta-ti-bsp and used by CodeGen Tools.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Legacy platforms AM3/4/5/J6 build components for multimedia acceleration and
other DSP showcasing using SYS/BIOS, XDC, XDAIS, CodeGen Tools and different
DSP libraries. Move all of them to meta-ti-extras.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
bitbake now requires it, as default master is no longer deterministic.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
bitbake now requires it, as default master is no longer deterministic.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Move WiLink WiFi and BT components from meta-ti-bsp to meta-ti-extras layer.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Extra sub-layers will be created next and relevant content moved across them.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
After 8b2c97b585, new platforms were merged with
BUILD_DIR used as in early Dunfell days, correct those.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Newer versions of baremetal GCC toolchain available from meta-arm-toolchain.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
DSP/BIOS was the name for older versions of TI-RTOS, prior to SYS/BIOS and
used on older deprecated platforms. Remove any remnants.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Newer versions of Linux kernel selftests are available from meta-oe.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
It's not BSP core functionality and newer version is available from meta-oe.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Cleanup remaining recipes that are used by other platforms from any machine
overrides that still refer to deprecated Keystone1/2 platforms.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Remove deprecated support for compiling Keystone1/2 RTOS components and
Linux firmwares using PDK, CSL, etc.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Low Level Drivers (LLDs) were used by Keystone1/2 to access peripherals by
RTOS and Linux. Remove due to deprecation.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
As beagleboard is now deprecated and removed from future meta-ti releases.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
OMAP3 platforms used OCF-Linux, a Linux port of the OpenBSD/FreeBSD
Cryptographic Framework (OCF) for Crypto HW acceleration. Later, an
alternative Cryptodev-linux API standard became dominant for newer
platforms. Remove deprecated module.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Linux Utils were used mainly by DMAI on deprecated DaVinci and OMAP3
platforms.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Was used with deprecated DaVinci, OMAP-L1 and OMAP3 families of platforms.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
X-Loader was originally used on OMAP3/4 platforms, but eventually got
replaced by U-boot SPL.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Those platforms are being deprecated and not supported in future meta-ti releases.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Both of the local patches were merged upstream, so update the reecipe to pull
the latest SRCREV and drop those patches from the OE metadata.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Cc: Khem Raj <raj.khem@gmail.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Since corresponding functionality and FW only available on J7.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
commit ba0ddc5ae9 ("conf: am437xx-evm: Remove non-existent dtb* from
5.10") removed all non-existent dtb* for am437xx-evm as they were not
available on linux 5.10 branch at that time.
This patch reintroduces following HDMI DTBs.
- am437x-gp-evm-hdmi.dtb
- am43x-epos-evm-hdmi.dtb
The required dts have been added to the 5.10LTS by these two following
commits:
- https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/arch/arm/
boot/dts/am437x-gp-evm-hdmi.dts?h=ti-linux-5.10.y&id=25434078d3f93d1346af5
e52e0f150f9083321d8
- https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/commit/arch/arm/
boot/dts/am43x-epos-evm-hdmi.dts?h=ti-linux-5.10.y&id=c5114144b568e470a8f6
e613f7c6e8b88ad19d7e
Signed-off-by: Amjad Ouled-Ameur <aouledameur@baylibre.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This adds a patch to fix runtime problems loading the kernel module with
kernel 5.10
Adds support to build with musl targets
Add yoe to recognised OE distributions
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This reverts commit d5db414172.
We should'nt have to carry patches for u-boot or kernel, since the
upstream is now fixed since 5.14 kernel and u-boot 2021.10 tag onwards,
lets revert the patch to allow upstream to work with 5.15+ kernel and
2021.10 u-boot (from the already applied commit cae609388f
"recipes-bsp: u-boot-ti-mainline: Update to v2021.10 release").
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This adds up numerous fixes for various k3 platforms.
While at it, bump the ti-upstream-tools repo as this sync up gives us:
config: audio_display: Update cdns-mhdp configs
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
SA2UL GP driver will not work for HS. Need SA2UL HS driver.
Till it is implemented blacklist sa2ul for am64xx hs and j7200 hs
Suggested-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This is temporary fix for combined boot images for KIG in meta-ti till
the patch is integrated.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump linux and rt-linux version to 08.01.00.006
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
The application expects the pvdec_full_bin.fw to be in /lib/fimware
directory.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Found a bug in the PRU_ICSSG examples in PSSP v6.0.0, fixed in v6.0.1.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This got accidentally merged from Dunfell with the old syntax, fix it.
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch adds support for J721e HS SR1.1
HS SR1.1 requires updated sysfw binary. Both SR1.0 and SR1.1 sysfw
binary will be generated. sysfw.itb will point to SR1.1
This patch requires J7 SR 1.1 support in K3 Image gen.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
We cannot use j7200 keyword for match b'n j7200-evm and j7200-hs-evm due
to existing j7 keyword, we need to duplicate all the j7200 entries for hs.
Also sign the DM firmware for J7200 similar to J7 HS
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Machine conf for J7200 HS platform.
Used am64xx hs and j721e hs as reference.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Added missing dtbo k3-am654-evm-ov5640.dtbo required for system test
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add missing k3-am642-evm-nand.dtbo required for system test
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Added support to build combined boot image for hs build.
This required k3 image gen patch that is already merged.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Add new am64x hs platform. This requires two files to be created.
Used am65x and j7 hs platform for reference.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This patch brings k3 image gen under bleeding for nightly builds
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
This introduces a critical fix for both AM335X EVM and AM43XX EVM, which
can no longer boot because "uuid" is undefined.
v2021.10 has these two fixes, one for each platform:
- commit ff8f277e9121 ("ti: am335x_evm: Switch to DISTRO_BOOT only")
- commit e0c91ae24e5b ("ti: am43xx_evm: Switch to DISTRO_BOOT only")
Signed-off-by: Amjad Ouled-Ameur <aouledameur@baylibre.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Update k3 image gen to latest.
Bump linux firmware to v2021.09a
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump linux rt version for 08.01.00.002 release
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Bump linux version for 08.01.00.002 release
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
this is undefined behaviour, mant times devs used them together to get
the missing space at the beginning of string which append/prepend needs
but thats not intended behaviour
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
AM64x SoCs have a Cortex-M4F core in MCU domain. This core is used a
standalone device for safety applications. For non safety applications,
the device is exposed as a remote processor with Linux rpmsg framework.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
To merge j7 dtb name change patch need to bump the linux and linux rt
before the point release
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
To merge the dtb file name change patch in meta-ti for j7 need to bump
linux version
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
PRU Software Support Package (PSSP) v6.0.0 should be included in Linux Processor
SDK 8.1 for AM335x, AM437x, AM57x (if generated), AM64x, AM65x under
example-applications. For the release notes that come with v6.0.0, see
https://git.ti.com/cgit/pru-software-support-package/pru-software-support-package/tag/?h=v6.0.0
Linux Processor SDK 8.1 will be the first AM64x SDK release to include the PSSP.
PRU firmware will also be generated and placed in the default filesystem under
lib/firmware/pru.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Change to support common INC for all firmware
This will help with:
1) Eliminating requirement to change multiple recipes for firmware
update
2) This will help support AUTOREV
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Update the ti-rpmsg-char library to 0.3.1 version that enables the
support for the M4F remote processor on AM64x SoCs.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
The uboot extlinux is using kernel device tree variable to populate the
dtb files. The error occurs if the device tree files are in ti folder
since there is no ti folder in deploy directory. Fix the kernel device
tree path before using in the uboot extlinux.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
To make use of the "generic distro boot" support in U-Boot, an
extlinux.conf file needs to be generated and reside in the extlinux
directory. The extlinux.conf file will be parsed by U-Boot and the
"append" line will be evaluated and expanded and used entirely as the
bootargs passed to the kernel. Our generated extlinux.conf states
that the kernel image and device trees live one level up (so the root
directory) from it, so populate that location with our kernel and device
trees.
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
All of our platforms here support running EFI binaries. We can have wic
generate a simple grub.cfg file for us that will find the root partition
via PARTUUID and utilize the device tree that is already discoverable
via the EFI configuration tables. Assuming the EFI loader is U-Boot,
this device tree can be replaced at run-time by the normal mechanism of
loading in to memory and passing that address as an argument to bootefi.
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
When "usrmerge" distro feature is enabled, root directories /bin, /sbin, /lib
are simply symlinks pointing to their counterparts in /usr. Hence, modules
should be installed accordingly into /usr/lib/modules/...
Since IMG Makefiles don't take the direct target directory, such as
${nonarch_base_libdir}/modules/, adjust the top-level rootfs path instead.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reported-by: Vivien Didelot <vdidelot@pbsc.com>
Tested-by: Vivien Didelot <vdidelot@pbsc.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Upcoming "honister" release changes the override syntax to improve usability,
speed and memory footprint. Update recipes with the new syntax and set layer
compatibility to honister.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Tested-by: Paul Barker <paul.barker@sancloud.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Build is failing for ti-rtos-firmware when ARAGO_BRAND = "mainline"
with below error:
"ERROR: ti-rtos-firmware-08.00.00.32-r0.0 do_fetch: Fetcher failure:
Unable to find file file://0001-Revert-soc-am64x-Makefile-Move-the-
SPL-Load-address-.patch;patchdir=../imggen anywhere."
This is because the mentioned patch is not present in the current path.
Fix this by updating the path to include ti-sci-fw
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Changes for firmware update( eff643e5 ti-rtos-firmware: update the
source to ti-linux-firmware) were in-complete without soft link.
1) Added soft link missing for the rtos firmware.
2) Updated the IPC am64x firmware name to be consistent with 7.3
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Tested-by: Grygorii Strashko <grygorii.strashko@ti.com>
These are the complete changes in the patch
1) Updated the firmware to fix IPC load issue due to resource_table
placement
2) Added the INC_PR
3) Updated the RTOS version
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Update AM65x SR2.0 prueth firmware to 02.02.09.03 that adds support for
100M HD mode.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
This is temporary change to pick the 08.00.00.026 firmware from
ti-linux-firmware repos:
1) Using the ti-sci-fw to pick the latest firmware and support AUTOREV
in future
2) Kept the destination folder name same to avoid wide-spead changes to
other recipes. Since that will be changed as part of over-all clean-up
TODO:
1) Re-structure rtos firmware repo and update all dependent firmware recipes.
2) Fix the destination folder name to match src folder
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
There was a discrepancy between master and dunfell where 2 different versions
of the same patch existed, so when syncing branches, it resulted in appying
the same change twice. This cleans it up.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
The beagleboneai is not loading the MLO without this change.
A similar change was needed in meta-yocto-bsp for the beaglebone black
due to the updating of dosfstools to 4.2 in Hardknott.
[Yocto #14306]
(See also meta-yocto rev: 0c679ac53b52e631a7c961872ce58f5cf74b8629)
Signed-off-by: Theodore A. Roth <troth@openavr.org>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Update u-boot recipe to be on the latest official upstream tag.
This introduces initial support for AM64x which works with v5.13
kernel tag.
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
J721E EdgeAI Kit (EAIK) is a low cost, small form factor board designed
for TI’s J721E SoC. TI’s J721E SoC comprises of dual core A72, high
performance vision accelerators, video codec accelerators, latest C71x
and C66x DSP, high bandwidth real-time IPs for capture and display,
GPU, dedicated safety island and security accelerators.
J721E EAIK supports the following interfaces:
* 4 GB LPDDR4 RAM
* x1 Gigabit Ethernet interface
* x1 USB 3.0 Type-C port
* x3 USB 3.0 Type-A ports
* x1 PCIe M.2 E Key
* x1 PCIe M.2 M Key
* x2 CSI2 Camera interface (RPi and TI Camera connector)
* 40-pin Raspberry Pi compatible GPIO header
J721e EVM and EAIK uses the unified bootloader. Add j721e eaik dtb
for machine=j721e-evm
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
And lets work with the latest kernel and while at it bump the system up
to latest ti-upstream-tools repo to get:
* AM65x SR1.0 overlay support
* EFI configuration to allow for the eventual support
* Few more cleanups for new architectures that have popped in.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Commit 02a2433c ("ti-sci-fw: Update image gen to latest") switched to a
newer commit in k3-image-gen that also picked up TISCI firmware release,
However, does include a change where the SPL address changed.
This switch in address has been queued for upstream in a future release
(v5.14 + u-boot 2021.10) and current mainline formal tags do not support
this address change. As a result, we have a broken AM64x mainline
support.
Revert this specific change from k3-image-gen for mainline alone for
now.
NOTE: This uses ARAGO_BRAND=mainline which is NOT accurate for meta-ti
which is distro independent, hence without appropriate changes while
using alternate distros, this change will not take effect.
Reported-by: Tom Rini <trini@konsulko.com>
Suggested-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Just updating imggen to a configuration compatible with latest firmware
should not have been accepted, we should have ensured that firmware
commit has moved correspondingly as well. Fix the same, else we get a
broken system.
Fixes: 406f599822 ("ti-sci-fw: Update imggen to release 08.00.00.001 tag")
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Jailhouse support is dropped for K3 platforms. So the ivshmem
(inter VM shared memory) based UIO driver and test applications
cannot be build and are not required.
Remove the recipes for the same.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Jailhouse support is dropped for K3 platforms, remove the
recipe and corresponding patches.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Directly take the images from ti-linux-firmware instead of using pdk build,
due to inconsistency of PDK releases vs Linux SDK releases vs different
SoCs.
Update to FW version: REL.CORESDK.08.00.00.20
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
commit 9ea50db095 ("conf: am65xx-evm: Remove non-existent dtb* from 5.10")
removed all non-existent dtb* for am65xx-evm as they were not
available on linux 5.10 branch at that time.
This patch reintroduces following display overlays.
- k3-am654-evm-tc358876.dtbo
- k3-am654-evm-oldi-lcd1evm.dtbo
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
This patch adds overlay to support icssg1-dualemac
ie: 1 x CPSW3g ports and 2 x ICSSG1 ports configuration
overlay: k3-am642-evm-icssg1-dualemac.dtbo
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Add prebuilt PRU Ethernet FW for am64xx-evm which is the same as
for AM65x SR2.0.
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
Reviewed-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
commit 8b206b32ec ("conf: j7-evm: Remove unavailable dtb/o from 5.10 kernel")
removed all non-existent dtb* for j7-evm as they were not
available on linux 5.10 branch at that time.
This patch reintroduces k3-j721e-common-proc-board-infotainment.dtbo overlay.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
Added KERNEL_DTB_OVERLAY_SUPPORT to common ti-soc include. This fixes the issue
where the dtbs are build without symbols causing issue with overlays.
Please note this increases the size of the dtb for all platform
derived from ti-soc. So for custom boards disable it from local.conf to
reduce size.
Signed-off-by: Yogesh Siraswar <yogeshs@ti.com>
U-boot build process requires DM firmware to be signed for J7 HS.
It's better for ti-rtos-firmware package (that delivers DM firmware) to sign
it once and provide signed version to other packages, instead of U-boot needing
to re-sign it during build in staging location.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
With U-Boot supporting both am64xx-evm and am64xx-sk with single
defconfig, there is not need for a new machine for am64xx-sk.
So, drop support for am64xx-sk machine.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
As a step towards unification for am64xx-evm and am64xx-sk,
start including am64xx-sk dtb for machine=am64xx-evm.
Once U-Boot merges support for unified bootloader, am64xx-sk
machine can be dropped.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Update u-boot recipe to be on the bleeding upstream tag.
While at it, also update the u-boot source url to point to the new
server as per [1].
While it may be redundant, lets document the usage of URI and
PROTOCOL for those, who (cough), may get tripped otherwise.
[1] a3bbd0b912
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
ReIntroduce AM65x SR1.0 Overlay as the support for it
is added in the ti-linux-5.10.y kernel now.
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
commit 9ea50db095 ("conf: am65xx-evm: Remove non-existent dtb* from 5.10")
removed all non-existent dtb* for am65xx-evm as they were not
available on linux 5.10 branch at that time.
This patch reintroduces overlays present current on ti-linux-5.10.y kernel.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
The update brings the fix for 5.10.x linux kernel.
commit c0039f1fec25 ("cmemk: Fix 5.10 build errors for non Keystone2 platforms")
commit 8aba20e20bf7 ("cmemk: Fix build errors for 5.10+ kernels")
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
bump SRCREV to latest to pick build fix for 5.10 kernel.
this update picks
commit 816485e68430 ("Merge pull request #1 in DBG/dsptop from for-5.10 to master")
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
bump SRCREV to latest to pick build fix for 5.10 kernel.
this update picks
commit dd0c82fb5763 ("Merge pull request #1 in DBG/gdbc6x from for-5.10 to master")
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Remove the non-existent dtb* , as they are not currently present on
ti-linux-5.10.y.
- dra7-evm-lcd-osd101t2045.dtb
- dra7-evm-lcd-osd101t2587.dtb
- dra71-evm-nand.dtb
- dra71-evm-lcd-auo-g101evn01.0.dtb
- dra72-evm-lcd-osd101t2045.dtb
- dra72-evm-lcd-osd101t2587.dtb
- dra72-evm-revc-lcd-osd101t2045.dtb
- dra72-evm-revc-lcd-osd101t2587.dtb
- dra76-evm-tfp410.dtb
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Remove the non-existent dtb* , as they are not currently present on
ti-linux-5.10.y.
- am57xx-evm-cam-ov10635.dtb
- am57xx-evm-reva3-cam-ov10635.dtb
- am571x-idk-lcd-osd101t2045.dtb
- am571x-idk-lcd-osd101t2587.dtb
- am572x-idk-lcd-osd101t2045.dtb
- am572x-idk-lcd-osd101t2587.dtb
- am574x-idk-lcd-osd101t2587.dtb
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Remove the non-existent dtb* , as they are not currently present on
ti-linux-5.10.y.
- am437x-gp-evm-hdmi.dtb
- am43x-epos-evm-hdmi.dtb
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Remove the non-existent dtb* , as they are not currently present on
ti-linux-5.10.y.
- am335x-icev2-prueth.dtb
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Remove the non-existent dtb, as they are not currently present on
ti-linux-5.10.y.
- keystone-k2g-evm-lcd.dtb
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Remove jailhouse overlay as it is not currently available in
ti-linux-5.10.y branch.
Removing for now, and shall be added back once they are
available in 5.10 kernel.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
The following dtb/o are not currently available in
ti-linux-5.10.y branch.
Removing for now, and shall be added back once they are
available in 5.10 kernel.
- ti/k3-j721e-proc-board-tps65917.dtb
- ti/k3-j721e-common-proc-board-infotainment.dtbo
- ti/k3-j721e-pcie-backplane.dtbo
- ti/k3-j721e-common-proc-board-jailhouse.dtbo
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
The eglplatform.h header is updated to account for deprecation of
MESA_EGL_NO_X11_HEADERS macro. Update srcrev to pick this change.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
The additional patch for ti-sgx-ddk-km remaps the arm-oe-linux-gnueabi prefix
to the arm-linux-gnueabihf preferred target. Same should be done for the
arm-poky-linux-gnueabi prefix.
Signed-off-by: Zan Dobersek <zan@falconsigh.net>
Reviewed-by: Gowtham Tammana <g-tammana@ti.com>
It appears common-csl-ip-rtos does not require ti-sysbios dependency to build,
but ti-pdk.bbclass adds it by default. While most of PDK-based components do
require ti-sysbios to be built from sources, it is safe to remove it from CSL,
reducing the dependency tree for special cases like PRU FW based on CSL, but
not needing ti-sysbios.
This only affects firmwares built from sources against PDK and CSL, not when
RTOS firmwares are delivered in binary form for newer K3 platforms.
Build-tested on am335x, am57xx, k2g and am65xx.
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Fixes:
ERROR: cuia-1.0.0.13-r0 do_package: QA Issue: cuia: Files/directories were installed but not shipped in any package:
/usr/lib/gnu.targets.arm.rtsv5T.av5T
/usr/lib/syscalls.am3g
/usr/lib/gnu.targets.codesourcery.rtsv5T.a470MV
/usr/lib/syscalls.am4g
/usr/lib/gnu.targets.codesourcery.rtsv6.av6
/usr/lib/gnu.targets.arm.rtsv7A.av7A
/usr/lib/syscalls.am4fg
/usr/lib/gnu.targets.arm.rtsv7M.am4fg
/usr/lib/gnu.targets.arm.rtsv7M.am4g
/usr/lib/boot.am3g
/usr/lib/gnu.targets.arm.rtsv7M.am3g
/usr/lib/gnu.targets.arm.rtsv6.av6
/usr/lib/boot.am4fg
/usr/lib/boot.am4g
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
cuia: 14 installed and not shipped files. [installed-vs-shipped]
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
It is a pre-built binary, hence no control over passing correct LDFLAGS.
This used to be a warning and recently became an error. Fixes:
ERROR: vis-01.50.07.15-r1 do_package_qa: QA Issue: File /usr/bin/RadioApp in package vis doesn't have GNU_HASH (didn't pass LDFLAGS?) [ldflags]
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for these:
.../ti/drv/cppi/test/k2h/armv7/linux/fw_main.c:50: multiple definition of `coreNum';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/src/cppi_test.c:102: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_main.c:50: multiple definition of `errorCount';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/src/cppi_test.c:102: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:85: multiple definition of `fw_passCfgVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:85: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:84: multiple definition of `fw_srioCfgVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:84: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:83: multiple definition of `fw_qmssDataVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:83: first defined here
.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:82: multiple definition of `fw_qmssCfgVaddr';
./obj/k2h/cppi/test/cppi_test.o:.../ti/drv/cppi/test/k2h/armv7/linux/fw_test.h:82: first defined here
Needs to be fixed properly later:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for these:
qmss/mpm_transport_qmss_interface.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here
qmss/mpm_transport_qmss_interface.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here
qmss/mpm_transport_qmss_interface.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here
qmss/mpm_transport_qmss_interface.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here
qmss/mpm_transport_qmss.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here
qmss/mpm_transport_qmss.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here
qmss/mpm_transport_qmss.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here
qmss/mpm_transport_qmss.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0x0): multiple definition of `fw_qmssCfgVaddr'; mpm_transport.so:(.bss+0x0): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0x4): multiple definition of `fw_qmssDataVaddr'; mpm_transport.so:(.bss+0x4): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0x8): multiple definition of `fw_srioCfgVaddr'; mpm_transport.so:(.bss+0x8): first defined here
qmss/mpm_transport_qmss_osal.so:(.bss+0xc): multiple definition of `fw_srioSerdesCfgVaddr'; mpm_transport.so:(.bss+0xc): first defined here
Needs to be fixed properly later:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for the following gcc10 errors:
.../gdbc6x/gdb/varobj.h:221: multiple definition of `ada_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:221: first defined here
.../gdbc6x/gdb/varobj.h:220: multiple definition of `java_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:220: first defined here
.../gdbc6x/gdb/varobj.h:219: multiple definition of `cplus_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:219: first defined here
.../gdbc6x/gdb/varobj.h:218: multiple definition of `c_varobj_ops'; mi-cmd-var.o:.../gdbc6x/gdb/./varobj.h:218: first defined here
Needs to be resolved properly in the code later:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Workaround for this gcc10 error:
.../linux/src/api/gates/GateHWSpinlock.c:96: multiple definition of `_GateHWSpinlock_cfgParams';
.libs/Ipc.o:.../linux/src/api/Ipc.c:97: first defined here
Needs to be resolved properly in the code:
https://gcc.gnu.org/gcc-10/porting_to.html
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Cc: Suman Anna <s-anna@ti.com>
It was giving this warning for years, finally gone:
| warning: `sys_errlist' is deprecated; use `strerror' or `strerror_r' instead
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Cc: Suman Anna <s-anna@ti.com>
update am64x rtos firmware to keep pinmux and control MMRs
remain unlocked now since linux needs this to be unlock.
this fix the USB and performance degradation issues.
am64xx: 07.03.00.19
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Switch to using all of multi-certificate boot images. This allows us
to create bootable images - in this case, we are missing tiboot3.bin
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
IMAGE type and dependencies can easily be centralized to SoC include
file. This is necessary to make sure that we don't do the duplication
and having multiple places to fix up.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Switch to using all of multi-certificate boot images. This allows us
to create bootable images - in this case, we are missing tiboot3.bin
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
wic and tar dependency on trusted firmware is wrong. It is u-boot build
that depends on trusted firmware deployment and is correctly handled by
u-boot recipe. No point in duplicating that dependency, so just clean it
all up.
Reported-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
We use the default IMAGE_BOOT_FILES configuration which matches up with
legacy boot configuration. Document the same to allow folks to
understand by just looking at the SoC include file.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
We use the default IMAGE_BOOT_FILES configuration which matches up with
legacy boot configuration. Document the same to allow folks to
understand by just looking at the SoC include file.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Lets keep things consistent by providing two possibilities for platforms
to pick from - legacy boot and multi-certificate boot.
In legacy boot, the base bootloader and system firmware are
maintained as separate binaries (tiboot3.bin and sysfw.itb).
In multi-certificate boot that newer K3 devices support, ROM is smarter
and can handle multiple x509 certificate based images: so we can strip
out the sysfw.itb and integrate it as part of tiboot3.bin itself. This
improves authentication and overall system boot times since we are now
able to boot both the system controller and the boot processor in
parallel.
We do have a scheme currently to identify the images necessary for boot
etc, but things are handled on a platform conf file basis. We can
improve that by introducing the pattern at the top level include and use
the relevant pattern in platforms as needed.
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
Remove duplicate machine-specific redefines of UBOOT_BINARY, UBOOT_IMAGE and
UBOOT_SYMLINK variables, as they are already defined with same values in the
common k3r5.inc file.
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Reviewed-by: Nishanth Menon <nm@ti.com>
Fixes:
.../scripts/secure-binary-image.sh: line 69: openssl: command not found
.../scripts/secure-binary-image.sh: line 78: openssl: command not found
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
OPTEEMACHINE name as defined in the optee_os project [1] for
j721e is k3-j721e.
This patch fixes the name to correct target.
[1]: 87613cf952
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.com>
ti-upstream-tools[1] repository carries the overlays and defconfig
fragments that we don't wish to overload upstream kernel community with.
The reason for that being these are constantly on churn as our test
coverage increases etc. Currently we reuse the "BRANCH" variable to also
matchup with kernel and ti-upstream-tools repositories as well.
This can tend to be a little painful if we decide to start testing
various kernel configurations - RT etc.. So, lets just split out the
TOOLS_BRANCH separated from the branch we use for kernel. Even though
the branch remains the exact same at this point.
[1] https://git.ti.com/cgit/ti-linux-kernel/ti-upstream-tools/
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Add GNU Multiple Precision Arithmetic Library as a dependency for
mainline linux builds. These are necesary for kernel to handle gcc
plugins for builtins.h
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
The J7200/AM64 ti-sci-fw needs to be installed in the deploy
directory so that it can be packaged in Processor SDK bundle
This is required because the ti-sci-fw is needed in the
installer prebuilt-images in order to build the combined boot
image for J7200/AM64
Signed-off-by: Lucas Weaver <l-weaver@ti.com>
update ti-rtos-metadata and ti-rtos-firmware recipes of meta-ti to
pick AM64x rtos firmware from mcu-plus-sdk instead of PDK.
Other devices such as AM65x, J7 continue to use fw from PDK.
Built and tested both IPC echo test applications - "rpmsg_client_sample”
& “rpmsg_char_simple”. Both tests passed for all remote R5F cores
on AM64x EVM
Signed-off-by: Shiju Sivasankaran <shiju@ti.com>
[praneeth@ti.com: rebase to dunfell/next]
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Boards like the beaglebone currently hardcode "u-boot" as a dependency
for the image and the wic format, and this prevents one from choosing
a different bootloader via:
PREFERRED_PROVIDER_virtual/bootloader = "non-u-boot-bootloader"
Depending on "virtual/bootloader" instead of "u-boot" fixes this.
Signed-off-by: Vivien Didelot <vdidelot@pbsc.com>
Suggested-by: Denys Dmytriyenko <denis@denix.org>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Between j7200 firmware tags 07.03.00.10 to 07.03.00.16
the downloadable weburl link changed
from *processor-sdk-rtos-jacinto7 to *processor-sdk-rtos-j7200.
This patch is to fix the recipe to pick the firmware from the
expected location on the new tag.
Fixes j7200 build error reported due to
77cdfa9f65 ("ti-rtos: Update metadata and versions for RTOS firmware")
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
And lets work with the latest kernel
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Bump up our recipe version for ti-upstream-tools for updates in config
files needed for latest kernel
Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Update the image gen and linux-firmware commit SHAs so that
am65x, j7200 and j721e also picks v2021.01 sysfw and the applicable
DM update with following version
* 07.03.00.12 for J721E
* 07.03.00.10 for J7200
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Add combined boot flow support for the AM64XX SK device.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
AM642 StarterKit (SK) board is a low cost, small form factor board
designed for TI’s AM642 SoC. Add machine definition for SK board.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Update SRCREV to latest commit that includes AM64xx SK platform
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Latest versions of Linux kernel (5.10) and U-boot (2021.01) are not yet ready
for prime time in meta-ti and some features are still being migrated and causing
issues. The recipes are meant for development and not yet for production.
Normally selection of the version is done with PREFERRED_VERSION by the Distro
(e.g. Arago), but if not specified by a Distro (Poky, distroless, etc.), the
default is to use the latest version. Hence need to change the default to not
automatically pick the latest version that is not ready yet.
This can be removed/reverted once those versions are ready to be picked by
default.
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the image gen and linux-firmware commit SHAs so that
am65x, j7200 and j721e also picks v2020.12a sysfw and the applicable
DM update on j7200 and j721e based on 07.02.00.10 tag
Signed-off-by: Dan Murphy <dmurphy@ti.com>
The 7200-hs-evm does not exist as a machine and if it did then this
directive should have been j7200-hs. So just remove it as it is
unneeded.
From: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the image gen and linux-firmware commit SHAs so that
am65x, j7200 and j721e also picks v2020.12 sysfw and the applicable
DM update on j7200 and j721e based on 07.02.00.05 tag
Dan Murphy - Removed am64xx PV over ride
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
As meta-arm has this version in master, but not in dunfell, temporarily overlay
corresponding patches locally - could be removed for the next release. Need to
alter FILESEXTRAPATHS for bbappend to locate local patches.
Since meta-arm/dunfell has 3.8-specific patches in SRC_URI, let's redefine it
completely to match 3.11-specific patch list in meta-arm/master.
Last, but not least, guard all upstream recipe varibales with "ti-soc" override
to only affect platforms in meta-ti, but not any other BSPs.
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the image gen and sysfw commit SHAs so that am64x picks
v2020.12 version.
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update SRCREV to pick latest that includes AM64X support
commit 65dd16b4e ("ti: k3: Introduce lite device board support")
adds support of AM64X platform in ti-atf branch.
This patch updates the SRCREV and also updates the BOARD to "lite" to
build for the mentioned platform.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Suggested-by: Denys Dmytriyenko <denis@denix.org>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Update the ti-rpmsg-char library to 0.3.0 version that enables
the support for the various R5F remote processors on AM64x SoCs.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update to v2.4 tag merge from upstream to keep TF-A in sync.
For major changes in trusted-firmware-a, See:
https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4
TI specific fixups include:
- stub for shutdown (CPUs enter wfi)
- uart console is now configurable.
While at it, update to include PV_k3 as 2.4. We use PV_k3 instead of
PV since this allows meta-ti to not affect other platforms esp in a
multi-BSP configuration.
We also add LIC_FILES_CHKSUM_k3 to make sure that we don't let any
re-licensing in the project pass through unnoticed as that has to
be carefully examined for making sure we have all the right legal
compliance - There has been no change compared to previous versions,
but we introduce this as a protection in case there is a change in the
future.
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
Suggested-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
commit a6904f563f ("Remove redundant YYLOC global declaration")
is in ti-u-boot-2020.01 branch now.
Updating SRCREV of ti-u-boot-2020.01 to pick the patch from there.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Backport a patch from upstream to fix build on distros with gcc10+
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Use latest SRCREV on master branch to pick up all the
changes compliant with TIFS 2020.08b firmware.
The license CHKSUM also need to be updated due to a minor
change from http to https in the Copyright line.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the srcrev to pick the latest artifacts that fix some of the
redundant rpath warnings seen with Yocto.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Use latest SRCREV on master branch.
This adds support for resource management commands
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the ti-rpmsg-char library to 0.2.0 version that includes
an improvement to signal handling logic.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
The patch for supporting the general toolchain is pulled into the repo.
Removing it here from the recipe.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
This fixes problems during cross compile where it starts to peek into
build host's include and library paths and causes errors with clang and
QA warnings with gcc
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Reviewed-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Add the initial recipes for building the ti-rpmsg-char package.
The library and examples are built using two separate recipes
in ti-rpmsg-char_git.bb and ti-rpmsg-char-examples_git.bb.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Add build dependency on optee-os for legacy HS platforms in non-Arago setups.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
As meta-arm/master now builds optee out of tree, hence use ${B} instead of
out/arm-plat-${OPTEEOUTPUTMACHINE}
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
As meta-arm/master now sets ${BUILD_DIR} to also include ${B} and release/debug.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
latest OE-core does not promote using trailing slash to make pseudo's
life easier
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Reviewed-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update md5 README checksum for u-boot. No actual licensing changes.
Change is with u-boot commit
35bd70c5107f0 ("Convert CONFIG_SPLASH_SCREEN et al to Kconfig")
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Recipe in meta-arm doesn't use OPTEEFLAVOR, but optee-os Makefile can extract
it from OPTEEMACHINE.
Keep OPTEEFLAVOR for legacy platforms - used for HS signing in the output name.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
It was originally residing in meta-arago due to earlier dependency on meta-optee
layer from meta-linaro. Now optee is in meta-arm and this code can move to meta-ti.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the firmware to version 3.1.4
Signed-off-by: Roger Quadros <rogerq@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the firmware to version 5.3.9
Signed-off-by: Roger Quadros <rogerq@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update SRCREV to pick the latest artifacts. The GL headers are excluded
in the artifacts instead of it in the recipe.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Directly take the images from ti-linux-firmware instead of using pdk
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Directly take the images from ti-linux-firmware instead of using pdk
Aldo drop build for k2g as firmwares are not yet available.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update the hsr/prp firmwares to latest that includes support for
timestamping rx packets. Unfortunately version number is not
incremented for this update.
Also rename the bb file to add PV in it.
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Rename gcc-arm-none-eabi to gcc-arm-baremetal.
As meta-arm now provides baremetal gcc-arm-none-eabi version 9, and due to layer
priorities, let's rename gcc-arm-none-eabi to gcc-arm-baremetal to force picking
the right version for RTOS builds.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
As part of replacing hard-coded /lib with ${base_libdir}, rpmsg_lib.lib was
also mistakenly moved from ${libdir} to ${base_libdir}, which is incorrect
and breaks other recipes, when they try to link against this library from
${libdir}.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
j7200-evm supports virtualization with Jailhouse hypervisor.
To use Jailhouse, kernel needs to boot with an additional
DTB overlay. Include this in the list of DTBs for the machine.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Initialize the cell names and console for the j7200-evm machine
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The J7200 SoC is a part of the K3 Multicore SoC architecture platform.
It is targeted for automotive gateway, vehicle compute systems,
Vehicle-to-Vehicle (V2V) and Vehicle-to-Everything (V2X) applications.
The SoC aims to meet the complex processing needs of modern embedded
products.
Some highlights of this SoC are:
* Dual Cortex-A72s in a single cluster, two clusters of lockstep
capable dual Cortex-R5F MCUs and a Centralized Device Management and
Security Controller (DMSC).
* Configurable L3 Cache and IO-coherent architecture with high data
throughput capable distributed DMA architecture under NAVSS.
* Integrated Ethernet switch supporting up to a total of 4 external ports
in addition to legacy Ethernet switch of up to 2 ports.
* Upto 1 PCIe-GEN3 controller, 1 USB3.0 Dual-role device subsystems,
20 MCANs, 3 McASP, eMMC and SD, OSPI/HyperBus memory controller, I3C and
I2C, eCAP/eQEP, eHRPWM among other peripherals.
* One hardware accelerator block containing AES/DES/SHA/MD5 called SA2UL
management.
See J7200 Technical Reference Manual (SPRUIU1, June 2020)
for further details: https://www.ti.com/lit/pdf/spruiu1
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
AM3/4/5 PREUTH driver now supports HSR/PRP offload driver. So include
these firmwares for the required SoCs.
Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This patch adds recipe for hsr/prp firmware on am3/4/5 SoCs. The binary
files are located on ti-linux-firmware.git. This is a forward port of
the recipe from processor sdk 6.3
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
IPUMM build is showing linker error for a function
ti_sdo_ce_utils_syscbuf_SysCBuf_Module_startup__E with latest xdc tool.
A dummy version of this function is added in ipumm as a temporary solution.
Signed-off-by: Ramprasad N <x0038811@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updating the srcrev to pick the latest changes which adds an unittest.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
ti-sci-fw builds multiple config variants via multiconfig and the number
is expected to grow. Provide a recipe to package a single set of sources
for MAINMACHINE.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* libjli.so and libawt_xawt.so are now detected within the
ti-xdctools packages.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
A user of the meta-ti layer may choose to use a combination
of the machines herein with another kernel, not necessarily
the one from the machine definition.
Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
AM57xx PRUETH driver now support switch mode and needs prusw-fw to
support switch mode. Therefore include PRU switch firmware for AM57xx builds.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updating srcrev to pick latest libs
- Support for surfaceless EGL display token
- RGBA4444 format support as window surface
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
rpmsg_kdrv_switch kernel module is implicitly dependent on the
for virtual ethernet driver. Ensure that the module is auto loaded
by default foe j7-evm platfom.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Full build of all examples is not needed. Update the
recipe to build only selected examples.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
May need to limit this to HS platforms in the future, but since there's
no SOC_FAMILY defined, listing them individually is rather painful now.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
While here format it a little bit to make
mailing list address stand out
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
uio_send and uio_read are the applications used for communication
between different Virtual Machines using the ivshmem protocol.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Latest upstream jailhouse uses ttyS3 as console.
Update the conf file so that this reflects correctly in the
tiny rootfs.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Latest upstream jailhouse uses ttyS3 as the console for
inmate cell. Update the recipe to pass the correct cmdline.
Override only for j7-evm
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The License checksum has changed due to version number change, but the
license itself has not changed
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Also correct ti-cgt-arm to not reference Hewlett-Packard, only Patrick-Powell,
according to included SPDX document.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Jailhouse 0.12 does not need to define custom config flags.
Remove the steps to copy the config from do_configure task
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
As it happens, ion-tests requires gtest from by meta-oe, but meta-ti has no
dependency on meta-oe. Unfortunately this was overlooked when all ion recipes
were migrated to meta-ti. Fix this by moving just ion-tests back.
Cc: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license as such has not changed, but moved to a License file which
is not expected to change frequently
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The following is the main change done:
Use FW_RSC_ADDR_ANY for places where memory needs to be allocated
dynamically like RSC_CARVEOUT and vdev resource entries
Signed-off-by: Ramprasad N <x0038811@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update srcrev to pick the fix for rt linux build issue.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
These boards have SGX GPUs but do not build as this recipe is not
compatible with them, add compatibles for these machines.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This also allows us to do two extra tasks so lets do them here:
- Add support back for Beagleboard and Pandaboard
- Remove plugins workaround as SO names are handled correctly now
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
As multiprocmgr is a user-space app and should only use uapi headers, drop
extra -I for the kernel headers. Patch out any assumptions of direct access
to the kernel headers.
Cc: Suman Anna <s-anna@ti.com>
Cc: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update branch for zeus release. There is no change to srcrev.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update the branch id to pick the sources relevant to k5.4.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
For now only j721e_evm is supported when building for j7-evm
MACHINE target. Limit the BOARDS list in this case to what is
supported.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
python-argparse is not available in oe-core, but meta-python provides a
drop-in replacement python3-configargparse, if needed. meta-ti does not
depend on meta-python for now - can be adjusted in the distro layer.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SUBDIRS has been deprecated for a while and as of k5.4 no longer works.
Use M= instead.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This compresses better and most machines use this now, lets switch these
remaining machines over.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This package adds the xorg.conf needed for some Xorg servers. Xorg does
not need these anymore as the automatic configuration will handle this.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This program uses many software components that are not recommended
anymore making it a bad example. The original source repo is gone.
It has dependencies on very old kernel versions. Lastly it doesn't
look to have been built by anyone in a long time. Lets remove this.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Pick up latest version of ti-img-encode-decode recipe
with Makefiles using CROSS_COMPILE instead of hard coding
aarch64-linux-gnu as the cross compiler.
Signed-off-by: David Huang <d-huang@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Pick up latest version of ti-img-encode-decode with improvements
to V4L2 decoder stream restart and slice map calculation, and
encoder performance profiling options.
Signed-off-by: David Huang <d-huang@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Link the git directory into the recipe's work directory to provide
git history and commit information for recipes that may need it.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* dualemac: fix to drop PTP sync msgs from unknown master
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- Updated the Software Manifest from 5.0 -> 6.0 to account for new processors,
etc.
- Updated to PRU Software Support Package v5.6.0
updated manifest
added PRU Getting Started Labs
improved several examples
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
CMEM memory block for bbai should be 402MB to allow full EVE
acceleration and DSP use, but accounting for the BBAI only having
1GB of RAM.
Signed-off-by: Caleb Robey <c-robey@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Changing BB_NUMBER_THREADS between successive builds causes a "basehash
value changed" error. Additionally, using BB_NUMBER_THREADS to pass a
number of processes to run to xdc is wrong: PARALLEL_MAKE is the correct
variable to use.
Fix both problems by using oe.utils.parallel_make_argument() to obtain the
number of processes to run from PARALLEL_MAKE.
Fixes:
ERROR: When reparsing .../meta-ti/recipes-ti/ipc/ti-ipc-rtos_git.bb.do_configure, the basehash value changed from 63897a188012cedde03f756b5dbbfa70 to 13b80bf4f4327c367bd201eb4aa32ad7. The metadata is not deterministic and this needs to be fixed.
ERROR: When reparsing .../meta-ti/recipes-ti/ipc/ti-ipc-rtos_git.bb.do_compile, the basehash value changed from 2fb59a7db2a2f69d2c25c06c1b6a4245 to 314c664cc040afae2800fcc378dd9ae0. The metadata is not deterministic and this needs to be fixed.
Steps to reproduce:
BB_NUMBER_THREADS="3" bitbake ti-ipc-rtos ti-ipc-examples-linux
BB_NUMBER_THREADS="4" bitbake -c cleansstate osal-rtos
BB_NUMBER_THREADS="5" bitbake ti-ipc-rtos ti-ipc-examples-linux
Reported here: https://e2e.ti.com/support/processors/f/791/p/825142/3059419
Reported-by: Matthew McKee (e-mail unknown)
Suggested-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This is allow user to override them in their configuration
Signed-off-by: Ankur Tyagi <ankur.tyagi@gallagher.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* LIC_FILES_CHKSUM changed to due to a corresponding change in the
S directory.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Recently individual components and LLD sources have been combined
into a single PDK repo. Use this class to specify the common source.
Also use this class to keep the sources separate from each other when
building. This keeps the build identical to previous recipes while
keeping control on interdependencies.
Similar to gcc-source, use the ti-pdk-source recipe to unpack the
sources into a "work-shared" area. Then hard-link only the necessary
files into a recipe's WORKDIR.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This is the initial step toward Mesa-based EGL/GLES libraries which
support all the required EGL 1.5 extensions. We plan to provide a
Mesa-pvr recipe to build Mesa from source and SGX/DDK patches where
ti-sgx-ddk-um shall provide the EGL/GLES plugins only at the next step.
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
There was a typo in machine description - AM435x instead of AM335x
Reported-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
IPC-LLD provides the low-level RPMSG based
communication interface between various cores
Signed-off-by: Santosh Jha <sjha@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
It rdepends on jailhouse package which is already marked at ti-soc
compatible only, so in a multi-BSP setup it ends up breaking builds
ERROR: Nothing RPROVIDES 'jailhouse' (but
/home/jenkins/oe/world/yoe/sources/meta-ti/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
RDEPENDS on or otherwise requires it)
jailhouse was skipped: incompatible with machine qemux86-64 (not in COMPATIBLE_MACHINE)
NOTE: Runtime target 'jailhouse' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['jailhouse']
NOTE: Runtime target 'ivshmem-uio-driver-dev' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['ivshmem-uio-driver-dev', 'jailhouse']
ERROR: Nothing RPROVIDES 'ivshmem-uio-driver' (but /home/jenkins/oe/world/yoe/sources/meta-ti/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'ivshmem-uio-driver'
NOTE: Runtime target 'ivshmem-uio-driver' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ivshmem-uio-driver']
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The rpmsg-echo firmwares are not supported for Tx_PRU cores on
J721E SoCs, these cores only support the Halt images. So suppress
the build warnings around Tx_PRU rpmsg-echo firmwares by limiting
the default ALTERNATIVES and updating the list for just the
pru-icss-halt package.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
A firmware binary for guest is added to source repo, updating the
srcrev to pick the latest changes.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Erick Narvaez <e-narvaez@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This is external kernel module which enables userspace io over the
Jailhouse ivhsmem (inter VM shared memory)
This driver is useful to test the inter VM communication.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Pick up latest version of ti-img-encode-decode with fixes
for debug warnings.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Fixes
beaglebone-capes-1.0-r4 do_populate_lic: ${COREBASE}/LICENSE is not a valid license file, please use '${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM. This will become an error in the future
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- New versions uses CMake and extra modules
- Correct detection of nm/ranlib/ar for LTO
- Fix build with clang/libc++
- depend on python3, needed during build
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license checksum changed due to the version, but the license itself
has not changed since the last release (1.1.0)
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updated git commit & version number for PRU Software Support Package.
Builds J721E Halt and RPMsg examples and packages them into lib/firmware/pru
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Support for new CMA linux mem area is added, updating srcrev to pick
the latest changes.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Pick up latest version of ti-img-encode-decode with latest
bug fixes.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Updated the ethernet Fw to use PDK memory map
so that it can run along with IPC apps in
CoreSDK.
* Added stripped version of the firmware
Signed-off-by: Santhana Bharathi <santa@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
`__get_order()` API got changed to `get_order()` in the newer kernel
4.19.73. Updating the srcrev to pick the corresponding fix in the
driver.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The fix from Khem Raj to use extern "C" instead of __BEGIN_DECL/__END_DECL macros
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cc: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The source repo has been updated with latest nulldrmws artifacts and
debug binaries. Updating srcrev to pick the latest changes.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The videnc-test-app provides the video encoder test app
(tienc_encode) for j7-evm.
Signed-off-by: David Huang <d-huang@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
After libgbm was moved into the ti-sgx-ddk-um project the recipe for
libgbm was deleted, this patch was left over, remove it here.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Pick up latest version of ti-img-encode-decode which
includes updates for decoder and addition of encoder.
Also update the recipe to build the encoder module.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
OE-built internal toolchain doesn't use "-gnueabihf" suffix and instead uses
"-gnueabi" for both softfp and hardfp.
For now we only support hardfp (user-space binaries are only available in
hardfp), but would be nice to check for "callconvention-hard" before applying
the patch.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* If both INITRAMFS_IMAGE and JH_RAMFS_IMAGE are unset, variables fail to
expand, which leads to dependency errors.
* Passing full CC variable ensure all options are specified, especially
--sysroot one for internal toolchains.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updating srcrev to pick latest fixes in the libs
- GL header updates to include latest extension definitions
- Fixes for NV12 format
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Virtualization support is added to the driver. Updating srcrev here to
pick the relevant sources.
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This file was shipped as part of the DDK, but was also supplied by
libwayland so it was deleted here. This file has been removed from
the DDK, so deleting the file manually here is no longer needed.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
No one in-tree depends on this anymore. This used to be the name of the
package so this was kept here for several years for backwards
compatibility. Remove this from PROVIDES.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Although not needed for the IMG default EGL implementation this is needed
when building the Mesa EGL version of the DDK.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Although not needed for the IMG default EGL implementation libexpat
is needed when using the Mesa EGL version.
While here s/libudev/udev as 'libudev' is package shipped as part of the
eudev project, but we use systemd, so we actually depend on 'udev'.
Move the PACKAGE_ARCH and PR defines to a more natural spot that also
lines up with the RGX version of recipe for easier diffs.
One thing we could have done is remove the DEPENDS line. We do not have
any build dependencies as these are pre-made library binaries, but I use
the package rootfs generated by bitbake to build the binaries locally,
so leave it for now.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The GBM library is tightly coupled with the system graphics systems,
other hardware GPU vendors (including our Rogue DDK) and Mesa all deploy
a version of the library as part of their GPU driver. We SGX does the
same. This should ease integration for us as we now don't rely on a
separate project for this library and our deployment strategy can match
across Mesa/RGX recipes, allowing for better re-use of common components.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Configure the linux-demo to use a ramfs for the linux inmate.
* Using JH_RAMFS_IMAGE, this can be set in some global conf.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Create a package containing the jailhouse tools which are used to work
with the cells and inmates. This recipe provides a good example for
using the jailhouse-cell-linux tool.
The tools require the pyjailhouse python modules, so package them as
well.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Correcting the corelist. There is no mpu2_x or mpu3_x instead they
should be mcu2_x/mcu3_x which is present in j7-evm
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
There is no mpu2_1,mpu3_0,mpu3_1 for j7-evm. They should have been
mcu2_1,mcu3_0 and mcu3_1 respectively.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The default TI_PDK_LIMIT_CORES set in conf/machine/includes/am65xx.inc
doesn't contain mcu1_1 which sciclient supports for am65x. Hence
appending it in the recipe.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* extend to am65xx family
* and correct am65xx cell and inmate filenames.
* remove earlycon bootargs for am65xx
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This tool is not publically fetchable yet and requires pre-downloading
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The checksum has changed due to version & date, the license has not
changed
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Previous commit, while adding support for another platform, extended
ALTERNATIVE variable (which is package-specific) with machine overrides,
accidentally dropping the necessary ${PN} suffix in the process.
Restore it to make update-alternatives system work again.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The PV has not changed as this is an incremental commit id update
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updated IPC/LLD firmware binaries for AM65xx and
J721E to support WFI state for proper remote core
power-down and power-up.
Signed-off-by: Jonathan Bergsagel <jbergsagel@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The License Checksum has changed due to version, the licenses have not
changed
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Use IPC/LLD based IPC echo test binaries as an
alternative for AM65X Linux IPC testing.
Updated location of J721E firmware binaries as well,
with latest IPC/LLD commit.
Signed-off-by: Jonathan Bergsagel <jbergsagel@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license checksum changed due to version, but the licenses haven't
changed
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Please note that LIC CHKSUM has changed due to version change.
The licenses themselves have not changed.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Please note that the LIC_CHECKSUM due to date and version.
The License itself has not changed
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
ti_bin_do_unpack() detects the absence of the required 32 bit libraries,
but only emits a warning. Later on the build will fail with a mysterious
error.
Fail immediately so the user can clearly read the error message and the
(always appreciated) instructions on how to fix the problem.
Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Using clang as default compiler fails to build these
since these packages explicitly asks for gcc as compiler
this ensures that we meet that demand
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This needs to be ported and tested with non-TI SOCs
its better to limit this to just TI SOCs as of now
this makes sure that meta-ti can be used in a multi-BSP
distro
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Fixes
WARNING: python should use 4 spaces indentation, but found tabs in jailhouse_git.bb, line 85
Reported-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Fixes build with non arm architectures
Subprocess output:x86_64-yoe-linux-strip: Unable to recognise the format of the input file `TOPDIR/build/tmpfs/work/qemux86_64-yoe-linux/ti-display-sharing-fw/00.09.00.00-gitAUTOINC+4a86f16df9-r0/sysroot-destdir/lib/firmware/ti-display-sharing-j721e.bin'
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* rpmsg_client_sample is a test module and should not be autoloaded
* Both k3_r5 and k3_dsp remoteproc modules depend on virtio_rpmsg_bus
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cc: Suman Anna <s-anna@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Builds the Jailhouse kernel module, hypervisor binaries
and all the cell configs for root cell and other demos.
Generate the linux-demo loader script without initramfs.
Supports am65x and j7-evm machines
[nikhil.nd@ti.com: Update for public trees]
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Reviewed-by: Subhajit Paul <subhajit_paul@ti..com>
Tested-by: Subhajit Paul <subhajit_paul@ti..com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Adds the R5 and DSP echo_test firmware binaries to be
used for testing Linux IPC on J721E SOCs.
Signed-off-by: Jonathan Bergsagel <jbergsagel@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Pick up latest version of ti-img-encode-decode which
fixes compilation warnings/errors with RT-Linux.
Also add "COMPATIBLE_MACHINE" to the recipe.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* add firmware for the R5F core to test the detection of watchdog
timeout events to trigger SOC reset though DMSC.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
We will start supporting Wayland window system. It is good to have nulldrmws as
a debug option. GPU driver recipe already support window system option.
Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The prueth-fw-am65xx provides the same firmware but built from
sourecs.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The sources for the am65xx prueth-fw are located in within the
emac-lld sources.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The emac-lld also contains sources for the prueth-fw on am65xx.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
LIC_FILES_CHECKSUM now calculates checksum on the copyright, skipping
the year which can change. The checksum contents itself have not changed
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Add the recipe for the video decoder driver.
Signed-off-by: David Huang <d-huang@ti.com>
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Add the firmware packaging recipe for the video decoder
for J721E devices.
Signed-off-by: Angela Stegmaier <angelabaker@ti.com>
Signed-off-by: David Huang <d-huang@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Restore max_leb_cnt so that the UBI/UBIFS fits into the board flash
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Update mdio register entries to use the full address
* For AM571x, remove the entries which are available after using DT overlay
Signed-off-by: Hongmei Gou <h-gou@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The J721E SoC belongs to the K3 Multicore SoC architecture platform,
providing advanced system integration to enable lower system costs
of automotive applications such as infotainment, cluster, premium
Audio, Gateway, industrial and a range of broad market applications.
This SoC is designed around reducing the system cost by eliminating
the need of an external system MCU and is targeted towards ASIL-B/C
certification/requirements in addition to allowing complex software
and system use-cases.
Some highlights of this SoC are:
* Dual Cortex-A72s in a single cluster, three clusters of lockstep
capable dual Cortex-R5F MCUs, Deep-learning Matrix Multiply Accelerator(MMA),
C7x floating point Vector DSP, Two C66x floating point DSPs.
* 3D GPU PowerVR Rogue 8XE GE8430
* Vision Processing Accelerator (VPAC) with image signal processor and Depth
and Motion Processing Accelerator (DMPAC)
* Two Gigabit Industrial Communication Subsystems (ICSSG), each with dual
PRUs and dual RTUs
* Two CSI2.0 4L RX plus one CSI2.0 4L TX, one eDP/DP, One DSI Tx, and
up to two DPI interfaces.
* Integrated Ethernet switch supporting up to a total of 8 external ports in
addition to legacy Ethernet switch of up to 2 ports.
* System MMU (SMMU) Version 3.0 and advanced virtualisation
capabilities.
* Upto 4 PCIe-GEN3 controllers, 2 USB3.0 Dual-role device subsystems,
16 MCANs, 12 McASP, eMMC and SD, UFS, OSPI/HyperBus memory controller, QSPI,
I3C and I2C, eCAP/eQEP, eHRPWM, MLB among other peripherals.
* Two hardware accelerator block containing AES/DES/SHA/MD5 called SA2UL
management.
* Configurable L3 Cache and IO-coherent architecture with high data throughput
capable distributed DMA architecture under NAVSS
* Centralized System Controller for Security, Power, and Resource
Management (DMSC)
See J721E Technical Reference Manual (SPRUIL1, May 2019)
for further details: http://www.ti.com/lit/pdf/spruil1
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Add to the dependencies set in ti-pdk.bbclass so that we get tools
such as XDC.
* Set the edma3-lld path so the makefile can push it onto XDCPATH.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The checksum changed due to version & year changes. The licenses remain
the same
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* prueth-fw and icss-emac-lld shared the same source repo, so make
them share the same inc file which specifies the sources.
* Add the FW versions to the icss-emac-lld.inc so that there can be
a single location for updates.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
As this is a pre-built package:
* Skip the build-deps and file-rdeps checks.
* Disable package debug split.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The checksum has been changeded due to the version string and copyright
year. Licenses themselves have not changed.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license checksum change is due to version number. License has not
been changed. However Patrick powell license which was missing earlier
has been added now.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license checksum update is due to the version number update. The
licenses have not changed.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license checksum changed due to the version and also because Hewlett Packard
license is no longer applicable.
The Patrick Powell license which was present earlier too was not mentioned in
the recipe, now it has been explicitly mentioned as well.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license checksum change is due to the copyright year and version.
The license itself has not changed.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
License has been changed to include a few new licenses such as
Synopsis,Joel Sherrill,Rich Felker,Otto Moerbeek,embedded brains Gmbh,
Regents of Univ of California, Digital Equipment Corporation, John
Baldwin,WIDE project, Jeffrey Roberson, ARM Ltd, NetBSD,Michael R Nelly,
and CYGWIN license
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This upgrade brings in the following updates:
* MPEG2 Decoder Update to 01.00.18.01 from 01.00.17.01
* VC1 Decoder Update to 01.00.02.08 from 01.00.02.07
Signed-off-by: Ramprasad N <x0038811@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The firmware names expected by driver is changed
am65x-mcu-r5f0-fw -> am65x-mcu-r5f0_0-fw
am65x-mcu-r5f1-fw -> am65x-mcu-r5f0_1-fw
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- bump SRCREV to pickup kernel 4.19 support
- enable AM3/4/5 support in addition to AM6 for DDK 1.17
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- bump SRCREV to pick up UM libraries for all supported SoCs at DDK 1.17
- enable AM3/4/5 support for DDK 1.17
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Upstream has changed copyright guidelines, no actual license change:
| Copyright guidance has been changed for migration of the
| ARM run project to trustedfirmware.org where the project
| governance is different.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Hence install and deploy UBOOT_SPI_BINARY conditionally, similar to
UBOOT_SPI_SPL_BINARY and UBOOT_SPI_GPH_BINARY.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- Updated the recipe to pick sources for k4.19
- Removed the gcc8 workaround patch as the new srcrev include those fixes
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Changing the branch that the TI linux firmware is picked
up from. As this is a branch that is used for numerous
kernel versions so the version needs to be removed from the
branch name.
Changing ti-linux-firmware-4.1.y to ti-linux-firmware
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Since both systemd and update-rc.d classes are inherited, not having a
corresponding file results in postinst function to fail, which is a hard
error now. Having both init files installed does not affect functionality.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Since both systemd and update-rc.d classes are inherited, not having a
corresponding file results in postinst function to fail, which is a hard
error now. Having both init files installed does not affect functionality.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Since cmem 4.16 now supports arm64, update cmem injection code accordingly
to work with arm64 DTS files.
Cc: Sam Nelson <sam.nelson@ti.com>
Cc: Jacob Stiffler <j-stiffler@ti.com>
Cc: Suman Anna <s-anna@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
1. Package everything including hidden folders for dsplib and mathlib
2. Update SRCREVs for dsplib and mathlib related to Proc-SDK 5.2 bug fixes.
Signed-off-by: Jianzhong Xu <xuj@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
PRU Software Support Package example PRU_ADC_onChip does not work out of the box
in SDK 5.1. This update fixes the PRU_ADC_onChip example.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- um: Validate mutex before lock and unlock
- um: Fix for RefCounting with mutex held
- um: Set the default mutex type to pthread mutex
- um: Fix the install path and scripts
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
-km: pvr_drm.c: move the assert_reset from DrmRemove to DrmUnload
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Some recipes that include ti-unpack.inc also need to build nativesdk packages.
Fixes errors like this:
| ERROR: Nothing RPROVIDES 'nativesdk-ti-cgt-pru' (but .../nativesdk-packagegroup-arago-sdk-host.bb RDEPENDS on or otherwise requires it)
| nativesdk-ti-cgt-pru was skipped: incompatible with host x86_64-arago-linux (not in COMPATIBLE_HOST)
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
some OE distros can default to hardened toolchains which means PIE is
added implicitly to compiler cmdline, here this options makes sure that
whattever the default toolchain are, u-boot is not impacted
Fixes errors e.g.
| arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not fit in region `.sram'
| arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Tom Rini <trini@konsulko.com>
Cc: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Thanks for the feedback! Updated patch below. Changes:
- Change SERIAL_CONSOLE to new SERIAL_CONSOLES format.
- Move SPL_BINARY variable into lego-ev3 machine config
- Check for KERNEL_DEVICETREE_BUNDLE before uImage manipulation.
- Fix line wrapping errors introduced by MUA
Signed-off-by: Jeremy Grosser <jeremy@synack.me>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Use variables from u-boot recipe, makes it easy to switch between TI staging
and mainline u-boot from oe-core if someone wants to.
Use SPL_BINARY and UBOOT_SUFFIX to define IMAGE_BOOT_FILES
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This helps in multi-BSP scenario, where other BSP layers are also
present in the layermix
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
There have been reports recently that am335x_beaglebone_config generates bad SPL.
Until that is debugged and fixed, use generic am335x_evm_config that covers all
AM335x platforms, including BeagleBone variants.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Fixes do_package_qa warnings
<FILE> is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
by default its set like this
DISABLE_STATIC ?= " --disable-static"
but doxygen configure is not typical autoconf
generated so this option is not available, its
better to keep it empty so it can work with
dustros which disable static libs as policy
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cleanup the patch in meta-ti as the patch is merged
to ipumm repo
Signed-off-by: Ramprasad N <x0038811@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Prevent a potential error as mklib will return an error if the
library already exists.
* The error encountered is the following:
| >> ERROR: mklib: destination library .../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/ti-cgt-arm-16.9.2/ti-cgt-arm_16.9.2.LTS/lib/rtsv7R4_A_le_v3D16_eabi.lib already exists
| WARNING: .../work/x86_64-linux/ti-cgt-arm-native/16.9.2-r1/temp/run.do_compile.13758:1 exit 1 from 'lib/mklib --pattern=rtsv7R4_A_le_v3D16_eabi.lib'
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
dsplib/mathlib: do not install/deploy .metadata
Do not install/deploy .metadata folder for dsplib and mathlib packages.
This folder prevents CCS from finding and installing dsplib and mathlib.
Signed-off-by: Jianzhong Xu <xuj@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The license checksum change is due to copyright year change
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The LIC checksum update is due to copyright year change
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Remove DSPLIB recipe that downloads pre-built DSPLIB from ti.com.
Add new recipe to build DSPLIB for C66x, C674x, or C64x+ from source code.
Signed-off-by: Jianzhong Xu <xuj@ti.com>
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Remove MATHLIB recipe that downloads pre-built MATHLIB from ti.com.
Add new recipe to build MATHLIB for C66x or C674x from source code.
Signed-off-by: Jianzhong Xu <xuj@ti.com>
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Add SWTOOLS which is needed to build xdc-based processor libs such as
DSPLIB, MATHLIB, etc from source.
Signed-off-by: Jianzhong Xu <xuj@ti.com>
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update to new commit with fixes for issues related to irq set API
Fix build issue with debug files
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
rtsv7R4_A_le_v3D16_eabi.lib library is not included in the cgt package.
This library is built dynamically during linking during a single build.
Bu in case of parallel make, dynamic creation of libraries causes
failures.
Hence building and adding the library to the package.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>t
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
With systemd enabled, it is better to add the proper systemd
script instead of legacy init.d script.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
TI design TIDA-01555 is added to Processor Linux SDK 5.1 as pru-adc-1.0.
Rename the PRU SW Support Package example PRU_ADC to PRU_ADC_onChip to prevent
confusion in the future.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* This fixes a configure issue when the sources may get cleaned.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
One of the features of poky-lsb is that it brings in the
security_flags.inc file that sets a number of security-related compile
time flags. This includes changing some of the default GCC build
options. However, for building the amx3-cm3 firmware we want to ensure
that none of this enabled as it's not useful in this particular
environment. We must pass in ${SECURITY_NOPIE_CFLAGS} to disable PIE.
When security_flags.inc is not present this is an empty string so is
safe to do at all times.
Signed-off-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
1.14:
- um: fix libGLESv2.so crashing at eglMakeCurrent for certain call flows
1.17:
- tools: usc2:dce: fix GLSL compiler error
- um: wsegl: fix the double unmap problem of CPU buffer
- um: fix libGLESv2.so crashing at eglMakeCurrent for certain call flows
- um: replace the hard-coded page size with the one read from kernel
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updated the commit ID to fix the Makefile issue encountered
in the previous version of the patch.
This updates the commit ID of the PRU Software Support Package
which is pulled into the SDK. The updated PRU Software Support
Package includes:
added am65x resources:
PRU_Halt example
PRU_MAC_Multiply_Accum example
ICSSG header files
added Lab_0:
this provides a "Hello World" style beginning Linux example for
every TI processor with a supported PRU (am335x, am437x, am57x,
k2g, am65x).
expanded Lab_5:
expanded Lab 5 to provide a more advanced PRU Linux example for
every TI processor with a supported PRU (am335x, am437x, am57x,
k2g, am65x).
Kernel 4.14 new features:
updated resource table for all examples and labs to match the
new template introduced in kernel 4.14
Code cleanup/bug fixes:
update RPMsg examples to provide a more elegent way to provide
the max message length.
updated Linker Command files to better match TRM.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* License checksum changed due to updated year (2018) in license text.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
-Updates to use sciclient for configuring interrupt routing in SOC
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Sci client provides API to communicate with the core running System
firmware
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Adds support for k3 platform
NOTE:
License checksum change is just due to addition of current year
2018 to copyright
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Adds the dependency on toolchain needed for A53 and R5 cores
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Has fix for mmap issues with latest kernel 4.14.x
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This patch is to integrate IPUMM with
IPC: 3.50.01.00
BIOS: 6.73.00.12
XDC: 3.50.07.20
Signed-off-by: Ramprasad N <x0038811@ti.com>
Acked-by: Karthik Ramanan <a0393906@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* CMEM increased to 384MB is required by TIDL to run both DSP and EVEs concurrently
Signed-off-by: Djordje Senicic <x0157990@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This is to allow user to override git repository and git protocol.
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updated SRCREV to point to an updated version of the PRU Software Support
Package which includes PRU_Halt and RTU_Halt examples for am65x. PV will
get updated in the next patch.
Added PRU_Halt and RTU_Halt to do_install_append_am65xx-evm(). Decided to leave
the installation of PRU_Halt examples in each processor's do_install_append
function for now since PRU_Halt and RTU_Halt for am65x have different output
file names than the previous ICSS processors. Those different output names can
be seen in the lines ALTERNATIVE_TARGET_pru-icss-halt[am65x....].
The previous commit made several changes to account for the fact that am65x Halt
examples had not yet been added to the PRU Software Support Package. Those
changes were removed in this commit.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Note: libEGL.so is required for DDK 1.17 based 3D demo programs
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- add COMPATIBLE_MACHINE to distinguish AM3/4/5 with K3 (AM654x)
- add k3 support based on SGX DDK 1.17
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
PRU Software Support Package v5.2.1 integrates 3 bug fixes and adds am335x
PRU_ADC example. PRU Software Support Package tags were updated so that v5.2.0
corresponds to the release that will be pulled into Linux SDK 5.0, while v5.2.1
corresponds to the commit for this version of the bitbake.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The current example application is Simple Open Real-Time Ethernet (SORTE).
It is ported to Linux user space utilizing UIO.
Signed-off-by: Hongmei Gou <a0271529@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Only PRU* images were picked up, not RTU*
* Setting up alternatives for non-existing PRU_Halt FW resulted in warnings
* Since PRU_Halt FW was absent, no ${PN}-halt package was made, resulting in
error pulling it in to an image
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
1. drop use of True as second parameter, which is default, to align with master
2. there were instances of incorrectly passing 'd' as second parameter from
previous conversion from bb.data.getVar() usage
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updated SRCREV to point to the latest PRU Software Support Package.
Added support for AM65x by adding a COMPATIBLE_MACHINE, PLATFORM,
do_install_append_am65xx-evm which installs RPMsg examples,
PRU_ICSS_ALTERNATIVES, ALTERNATIVE_LINK_NAMEs,
ALTERNATIVE_TARGET_pru-icss-rpmsg-echo. Moved the installation of
PRU_Halt from do_install to the associated do_install_appends, since
am65x will require different PRU_Halts for each PRU/RTU core.
Did not yet add ALTERNATIVE_TARGET_pru-icss-halt as the am65x PRU_Halt
examples have not been written yet.
Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
b42044aaf removed the XDC tools from the main package, but this broke
the ability to include the XDC tools in an SDK. Add the tools back to
the -dev package. Also fix up INSANE_SKIP.
Change-Id: I902cc1a841e40c1a3bdc5286d03f999276119052
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The AM654 SoC is a lead device of the K3 Multicore SoC architecture
platform, targeted for broad market and industrial control with aim to
meet the complex processing needs of modern embedded products.
See AM65x Technical Reference Manual (SPRUID7, April 2018)
for further details: http://www.ti.com/lit/pdf/spruid7
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The AM654 SoC is a lead device of the K3 Multicore SoC architecture
platform, targeted for broad market and industrial control with aim to
meet the complex processing needs of modern embedded products.
See AM65x Technical Reference Manual (SPRUID7, April 2018)
for further details: http://www.ti.com/lit/pdf/spruid7
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This upgrade brings in the following updates:
* MPEG4 Decoder Update to 01.00.17.01 from 01.00.15.01
* VC1 Decoder Update to 01.00.02.07 from 01.00.02.05
* Update to IPC 3.47.01.00
* Add profiler to measure based on IVA-HD processing time
Signed-off-by: Karthik Ramanan <a0393906@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* am335x-icev2-prueth.dts is newly added in kernel 4.14, and shall be
used as the baseline to create am335x-icev2-pru-excl-uio.dts
Signed-off-by: Hongmei Gou <a0271529@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Flag variables used in setup_cmem to force it to re-run when one changes.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This way keystone_remoteproc.h can also be found in sysroots, when available.
Otherwise it can fall back to using kernel sources directly.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The new version uses make install thereby eliminating the need to do the
same in the yocto recipe. Hence removing the same from the recipe.
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This also includes rtos receipes changes required as a part of update to
02.01.01.06C
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Updating to version 1.0.0.11A and update the license checksum of the sub
component recipes
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
- pickup the latest release which includes two local patches
- remove those two local patches
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Note: This is a tentative patch to enable graphics support.
We shall merge both local patches to the ti-sgx-km repo soon.
Signed-off-by: Anand Balagopalakrishnan <anandb@ti.com>
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Since using DT overlays as a FIT image (itb,dtb,dtbo) is not yet ready
for prime time, kernel now has ability to generate all combinations of
full DTBs out of DT overlays. Use those for now until FIT image approach
to DT overlays is adopted more broadly.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The new version include the 2D API include files
Signed-off-by: Gowtham Tammana <g-tammana@ti.com>
Signed-off-by: Eric Ruei <e-ruei1@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
DRA7xx board changes have introduced dependencies on mmcsd-lld-rtos and
pm-lld-rtos. Adding these modules to the omap-a15 depends list will
bring in the dependencies for dra7xx builds
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Includes documentation correction and build optimization for examples
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* ti-xdctools is a host development package, but the target recipe is
needed to create the sourceipk used in SDKs.
* And move class extension to common include.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@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.
