include: Add AM65X specific headers corresponding to SYSFW
Introduce initial AM65X specific headers
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Introduce initial AM65X specific headers
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Makefile: Use SoC variable to pick up relevant binaries and include paths
Let's use the define and use an SoC variable to pick up various include
definitions.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Let's use the define and use an SoC variable to pick up various include
definitions.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Makefile: Add -f to rm so that we can ignore nonexistent files
Stop complaining that files don't exist if folks do multiple cleans or
mrpropers.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Stop complaining that files don't exist if folks do multiple cleans or
mrpropers.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Makefile: Drop the asm rule
We dont build ASM, so, why have a rule for the same.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
We dont build ASM, so, why have a rule for the same.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
build: Default to use TI degenerate key for signing on non-HS devices
Switch to using the TI degenerate key to sign the system firmware binary
image on GP devices during the image tree blob build process. Using this
key speeds up the time needed by the ROM code execution for processing
this image and with this shortens our boot time.
The previous default behavior of signing with a random key can still
be triggered by passing an empty KEY variable to the make command as
follows:
$ make KEY=""
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Switch to using the TI degenerate key to sign the system firmware binary
image on GP devices during the image tree blob build process. Using this
key speeds up the time needed by the ROM code execution for processing
this image and with this shortens our boot time.
The previous default behavior of signing with a random key can still
be triggered by passing an empty KEY variable to the make command as
follows:
$ make KEY=""
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
build: Allow signing SYSFW with custom key on non-HS devices
Enable the existing make variable KEY that was introduced to specify
the signing key used to sign SYSFW for use on HS devices to also be
used to sign SYSFW images destined for GP devices, overriding the
default random key that is used for signing.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Enable the existing make variable KEY that was introduced to specify
the signing key used to sign SYSFW for use on HS devices to also be
used to sign SYSFW images destined for GP devices, overriding the
default random key that is used for signing.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
3 years agolinux-firmware: Update am65x sysfw to v2019.04a ti2019.01 ti2019.01-rc3 ti2019.01-rc4 ti2019.01-rc5
linux-firmware: Update am65x sysfw to v2019.04a
Update the sysfw to v2019.04a from v2019.02
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Update the sysfw to v2019.04a from v2019.02
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
common: Add basic BIT(x) macro defininiton
For that we can use macros that rely on BIT(x) in the different
configuration files we need to actually have that underlying macro
defined in the first place so go ahead and add the missing
definition.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Acked-by: Suman Anna <s-anna@ti.com>
For that we can use macros that rely on BIT(x) in the different
configuration files we need to actually have that underlying macro
defined in the first place so go ahead and add the missing
definition.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Acked-by: Suman Anna <s-anna@ti.com>
build: Add support for HS devices
This tool can be used to download and sign HS SYSFW images, add
support for this here. Usage is described in the README.
Signed-off-by: Andrew F. Davis <afd@ti.com>
This tool can be used to download and sign HS SYSFW images, add
support for this here. Usage is described in the README.
Signed-off-by: Andrew F. Davis <afd@ti.com>
build: Use TI support email as default instead of Albert
Use a slightly more valid default certificate signer.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Use a slightly more valid default certificate signer.
Signed-off-by: Andrew F. Davis <afd@ti.com>
linux-firmware: Update am65x sysfw to v2019.02
Update the sysfw to v2019.02 from v2018.10. Also update
the license year.
Signed-off-by: Suman Anna <s-anna@ti.com>
Update the sysfw to v2019.02 from v2018.10. Also update
the license year.
Signed-off-by: Suman Anna <s-anna@ti.com>
linux-firmware: Update am65x sysfw to v2018.10
Update the sysfw to v2018.10 from v2018.09.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Update the sysfw to v2018.10 from v2018.09.
Signed-off-by: Andrew F. Davis <afd@ti.com>
linux-firmware: Update am65x sysfw to v2018.09
Update the sysfw to v2018.09 from v2018.08b.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Update the sysfw to v2018.09 from v2018.08b.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
rm-cfg: Partition interrupt resources between R5F contexts
Partitioning the MCU R5F IRQs to be distributed between R5F context 0
and context 1.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Partitioning the MCU R5F IRQs to be distributed between R5F context 0
and context 1.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Add software manifest as required for external release
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Introduce framework to build SYSFW and config data into an ITB
In order to be able to consume system firmware (SYSFW) as well as the
associated configuration data from the boot media introduce a framework
that allows building the SYSFW image itself as well as the different
domain-specific configuration fragments (board, pm, rm, and sec) into an
image tree blob (ITB) file called sysfw.itb.
To establish a known-good starting point for development and testing use
U-Boot commit 7501705610 ("arm: K3: am654: Update board config for
v2018.07a enforcement in 2018.08 release of sysfw") as a baseline for the
AM654x board configuration data. Furthermore integrate SYSFW v2018.08b as
released on 09/12/2018 by way of download URL.
See included README.md for a more complete description.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
In order to be able to consume system firmware (SYSFW) as well as the
associated configuration data from the boot media introduce a framework
that allows building the SYSFW image itself as well as the different
domain-specific configuration fragments (board, pm, rm, and sec) into an
image tree blob (ITB) file called sysfw.itb.
To establish a known-good starting point for development and testing use
U-Boot commit 7501705610 ("arm: K3: am654: Update board config for
v2018.07a enforcement in 2018.08 release of sysfw") as a baseline for the
AM654x board configuration data. Furthermore integrate SYSFW v2018.08b as
released on 09/12/2018 by way of download URL.
See included README.md for a more complete description.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>