Age | Commit message (Collapse) | Author |
|
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>
|
|
OPTEEMACHINE name as defined in the optee_os project [1] for
j721e is k3-j721e.
This patch fixes the name to correct target.
[1]: https://github.com/OP-TEE/optee_os/commit/87613cf9520db2e65bc8367d3e13c4217c13bdad
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Acked-by: Denys Dmytriyenko <denys@konsulko.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>
|
|
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>
|
|
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
The AM64 is a follow on device of the AM65xx K3 multicore SoC architecture.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
|
|
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>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@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>
|
|
K3 Multicore SoC architecture defines different functional domains, each
containing specific processing cores and peripherals. Early boot is normally
handled by running bootloader and loading SYSFW on MCU Cortex-R5F core:
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/am65x/README
https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/board/ti/j721e/README
This change adds support for building bootloader and SYSFW ITB image for
K3 Cortex-R5F cores via multiconfig.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
* am335x-icev2-prueth.dtb
* am335x-boneblack-prusuart.dtb
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
This reverts commit 517864fb4f37b424877a823da76ea7b780e5a45d.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Eric Ruei <e-ruei1@ti.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>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Now that meta-yocto-bsp renamed reference machine to beaglebone-yocto
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
opencl-monitor does not distinguish between dra7xx and am57xx devices,
treating both as the same and attempting to build for am57xx regardless.
However, this is dependent on common-csl-ip-rtos, a component of PDK,
which in general does handle these devices differently. The definition
of am57xx SOCs in the PDK list from omap-15.conf gets inherited by
dra7xx-evm.conf, thereby creating a rule that all dra7xx PDK recipes
must build am57xx libraries. This results in a dra7xx image which is
much larger than necessary, and more severely, creates an artifical
dependency link between these two devices and introduces build failures
for various PDK recipes.
Instead, we now override the PDK SOC definition in dra7xx-evm.conf, and
only in the CSL RTOS recipe do we append the am57xx SOCS for dra7xx-evm
machine build. This allows for opencl-monitor to build successfully for
dra7xx while preventing any other PDK recipes from attempting to build
libraries for am57xx devices.
This is a workaround that must stay in place until opencl build can
properly comprehend am57xx and dra7xx independently, and/or omap-a15
is not implied to be synonymous with am57xx in various recipes.
Signed-off-by: Stephen Molfetta <sjmolfetta@ti.com>
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Mahesh Radhakrishnan <m-radhakrishnan2@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Hongmei Gou <a0271529@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
* The omapl137 family does not have linux support and is only
supported by baremetal and TI RTOS.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
|
|
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Acked-by: Jacob Stiffler <j-stiffler@ti.com>
|