| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
Add combined boot flow support for the AM64XX device.
From: Dan Murphy <dmurphy@ti.com>
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>
|