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>
Robert Nelson
Khem Raj
Matthias Schiffer
Theodore A. Roth
Ryan Eatmon
Denys Dmytriyenko
Siddharth Vadapalli
Vaishnav Achath
Bhavya Kapoor
Dasnavis Sabiya
Aradhya Bhatia
Sinthu Raja
Jai Luthra
Sai Sree Kartheek Adivi
Chirag Shilwant
Manorit Chawdhry