| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
Lets generate bmap files for bmaptool to use as well as default to use
with wic files.
NOTE: bmaptool can speed up flashing SD cards by 2x-3x by skipping
empty blocks of the image.
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#flashing-images-using-bmaptool
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>
|
|
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: 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>
|
Denys Dmytriyenko
Nishanth Menon
Denys Dmytriyenko
Daniel D?az
e-ruei1@ti.com