4 years agorm-cfg: j721e: Partition generic IR resource across core0/core1 ti2019.06 ti2019.06-rc5 ti2020-rc1 ti2020.00-rc1
rm-cfg: j721e: Partition generic IR resource across core0/core1
Main NAVSS interrupt router for MCU R5 subsystem is shared between
both CPU cores.
However, SYSFW models them to core specific devices where it
appears that the interrupt router is dedicated for each core.
MCU NAVSS IR is dedicated per MCU core but main NAVSS IR is not.
Due to this, drivers calling GET_RANGE gets the same range on
both cores, causing conflict in the interrupt partitioning.
Fix this by partitioning the shared interrupt pool between
MCU R5 core0 and core1.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Main NAVSS interrupt router for MCU R5 subsystem is shared between
both CPU cores.
However, SYSFW models them to core specific devices where it
appears that the interrupt router is dedicated for each core.
MCU NAVSS IR is dedicated per MCU core but main NAVSS IR is not.
Due to this, drivers calling GET_RANGE gets the same range on
both cores, causing conflict in the interrupt partitioning.
Fix this by partitioning the shared interrupt pool between
MCU R5 core0 and core1.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.12
Update the Makefile to automatically fetch and build the v2019.12
version of the sysfw binaries for both AM65x and J721E SoCs.
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the Makefile to automatically fetch and build the v2019.12
version of the sysfw binaries for both AM65x and J721E SoCs.
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Dan Murphy <dmurphy@ti.com>
HACK: soc: j721e: Do not cross max limit for RM entries
Maximum number of entries supported in RM board config is
currently limited to 276 (2 * RESASG_UTYPE_CNT)
Any board config with more entries than this count will be
rejected and causes boot failure.
This needs to be fixed by increasing the max limit in SYSFW.
In the absence of this bugfix, restrict the number of entries
by folding all of R5, C6x, C7x host_id entries into single entry.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Maximum number of entries supported in RM board config is
currently limited to 276 (2 * RESASG_UTYPE_CNT)
Any board config with more entries than this count will be
rejected and causes boot failure.
This needs to be fixed by increasing the max limit in SYSFW.
In the absence of this bugfix, restrict the number of entries
by folding all of R5, C6x, C7x host_id entries into single entry.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
soc: j721e: Partition nonsecure proxy and ring monitors
Define the resources for non secure proxy and ring monitor
allocation across different hosts.
Update the total count of resources.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Define the resources for non secure proxy and ring monitor
allocation across different hosts.
Update the total count of resources.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
j721e: am65x: sec-cfg: Add otp_config section
Update the common.h headers to add new defines from SYSFW 2019.12.
Starting from SYSFW v2019.12, an otp_config section is mandatory in
the security config. Otherwise the boot fails.
Fix this by adding a section for opt_config with no other host
having permission to OTP array.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Update the common.h headers to add new defines from SYSFW 2019.12.
Starting from SYSFW v2019.12, an otp_config section is mandatory in
the security config. Otherwise the boot fails.
Fix this by adding a section for opt_config with no other host
having permission to OTP array.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
include: j721e: am65x: Add new types and subtypes from SYSFW 2019.12
Add new types and subtypes for non secure proxies and ring monitors
supported in the SYSFW 2019.12 headers.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Add new types and subtypes for non secure proxies and ring monitors
supported in the SYSFW 2019.12 headers.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.10a
Update the Makefile to automatically fetch and build the v2019.10a
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Tested-by: Andreas Dannenberg <dannenberg@ti.com>
Acked-by: Suman Anna <s-anna@ti.com>
Update the Makefile to automatically fetch and build the v2019.10a
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Tested-by: Andreas Dannenberg <dannenberg@ti.com>
Acked-by: Suman Anna <s-anna@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.10
Update the Makefile to automatically fetch and build the v2019.10
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Reviewed-by: Andreas Dannenberg <dannenberg@ti.com>
Update the Makefile to automatically fetch and build the v2019.10
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Reviewed-by: Andreas Dannenberg <dannenberg@ti.com>
4 years agobuild: Sign board configuration data on HS ti2019.05 ti2019.05-rc2 ti2019.05-rc3 ti2019.05-rc4
build: Sign board configuration data on HS
Starting with SYSFW v2019.09 it will be required for board config
binaries to be signed to ensure trust through authentication.
Add this signing step here.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Starting with SYSFW v2019.09 it will be required for board config
binaries to be signed to ensure trust through authentication.
Add this signing step here.
Signed-off-by: Andrew F. Davis <afd@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.09
Update the Makefile to automatically fetch and build the v2019.09
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update the Makefile to automatically fetch and build the v2019.09
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
4 years agolinux-firmware: Update am65x/j721e sysfw to v2019.08 ti2019.04 ti2019.04-rc1 ti2019.04-rc2 ti2019.04-rc3 ti2019.04-rc4 ti2019.04-rc5
linux-firmware: Update am65x/j721e sysfw to v2019.08
Update the Makefile to automatically fetch and build the v2019.08
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the Makefile to automatically fetch and build the v2019.08
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.07a
Update the Makefile to automatically fetch and build the v2019.07a
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the Makefile to automatically fetch and build the v2019.07a
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
am65x: Correct R5F core 1 Host ID
HOST_ID_R5_1 is to be used only with secure context.
HOST_ID_R5_2 is the right Host Id to use for R5F core 1
Fixes: 54933d505c4d ("rm-cfg: Partition interrupt resources between R5F contexts")
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Acked-by: Suman Anna <s-anna@ti.com>
HOST_ID_R5_1 is to be used only with secure context.
HOST_ID_R5_2 is the right Host Id to use for R5F core 1
Fixes: 54933d505c4d ("rm-cfg: Partition interrupt resources between R5F contexts")
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Acked-by: Suman Anna <s-anna@ti.com>
build: Add support for enabling sysfw traces
Sysfw provides a provision for enabling sysfw traces while booting.
This has to be enabled in board-cfg. In order to ease debug, enable
the sysfw trace support with the help of a build option. Use the
option to enable it:
$ make ENABLE_TRACE=1
Reported-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Sysfw provides a provision for enabling sysfw traces while booting.
This has to be enabled in board-cfg. In order to ease debug, enable
the sysfw trace support with the help of a build option. Use the
option to enable it:
$ make ENABLE_TRACE=1
Reported-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
4 years agoHACK: j721e: rm-cfg: Use HOST_ALL for ethernet firmware flows ti2019.03 ti2019.03-rc2 ti2019.03-rc3 ti2019.03-rc4
HACK: j721e: rm-cfg: Use HOST_ALL for ethernet firmware flows
Ethernet firmware acts as server for providing networking functionality
to other clients. It allocates few flows from its pool for the client
and then retuns the same to the client.
Client does not own the resource it is borrowing from server and
currently SYSFW lacks any APIs to allow shared ownership of this
resource dyanmically.
In absence of such an API, mark the ethernet firmware flows are HOST_ALL
so that clients can call FLOW_CONFIG with the borrowed flow.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Ethernet firmware acts as server for providing networking functionality
to other clients. It allocates few flows from its pool for the client
and then retuns the same to the client.
Client does not own the resource it is borrowing from server and
currently SYSFW lacks any APIs to allow shared ownership of this
resource dyanmically.
In absence of such an API, mark the ethernet firmware flows are HOST_ALL
so that clients can call FLOW_CONFIG with the borrowed flow.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
j721e: rm-cfg: Partition GPIO interrupt router
Currently the Main GPIO interrupt router is only assigned to A72_2.
Partition the IR lines such that few lines are assigned to
A72_3 for usage from another Virtual machine.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Currently the Main GPIO interrupt router is only assigned to A72_2.
Partition the IR lines such that few lines are assigned to
A72_3 for usage from another Virtual machine.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.07
Update the Makefile to automatically fetch and build the v2019.07
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Update the Makefile to automatically fetch and build the v2019.07
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
am65x: rm-cfg: Add resources for secure context of MCU R5
ROM boots up MCU R5 in secure context and R5 SPL continues to run in the
same context. In order for R5 SPL to use DMA (e.g: with OSPI) add MCU
NAVSS resources with MCU R5 secure host ID that is used by R5 SPL.
Resources allocated are same as those allocated for A53.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
ROM boots up MCU R5 in secure context and R5 SPL continues to run in the
same context. In order for R5 SPL to use DMA (e.g: with OSPI) add MCU
NAVSS resources with MCU R5 secure host ID that is used by R5 SPL.
Resources allocated are same as those allocated for A53.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
j721e: rm-cfg: Add resources for secure context of MCU R5
ROM boots up MCU R5 in secure context and R5 SPL continues to run in the
same context. In order for R5 SPL to use DMA (e.g: with OSPI) add MCU
NAVSS resources with MCU R5 secure host ID that is used by R5 SPL.
Resources allocated are same as those allocated for non secure context.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
ROM boots up MCU R5 in secure context and R5 SPL continues to run in the
same context. In order for R5 SPL to use DMA (e.g: with OSPI) add MCU
NAVSS resources with MCU R5 secure host ID that is used by R5 SPL.
Resources allocated are same as those allocated for non secure context.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
j721e: board-cfg: Drop MSMC cache size from 4MB to 3MB
Reduce the amount of MSMC memory allocated by System Firmware for the
main compute cluster's L3 cache from 4MB to 3MB.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Acked-by: Nishanth Menon <nm@ti.com>
Acked-by: Sunita Nadampalli <sunitan@ti.com>
Acked-by: Carlos Hernandez <ceh@ti.com>
Reduce the amount of MSMC memory allocated by System Firmware for the
main compute cluster's L3 cache from 4MB to 3MB.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Acked-by: Nishanth Menon <nm@ti.com>
Acked-by: Sunita Nadampalli <sunitan@ti.com>
Acked-by: Carlos Hernandez <ceh@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.06a
Update the Makefile to automatically fetch and build the v2019.06a
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Update the Makefile to automatically fetch and build the v2019.06a
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
j721e: rm-cfg: Start MAIN_0_R5_2 Tx and Rx at same level
Channel allocation for MAIN_0_R5_2 is done such that
Main NAV UDMA Tx and Rx channels start with different offsets.
This cannot be used for block copy carveout since the Tx and Rx channels
are not overlapping at start or end of the range.
Fix this by allocating more channels to MAIN_0_R5_0 so that the
MAIN_0_R5_2 channel ranges start at same value.
Autogen table takes care of the corresponding ring allocations as well.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Channel allocation for MAIN_0_R5_2 is done such that
Main NAV UDMA Tx and Rx channels start with different offsets.
This cannot be used for block copy carveout since the Tx and Rx channels
are not overlapping at start or end of the range.
Fix this by allocating more channels to MAIN_0_R5_0 so that the
MAIN_0_R5_2 channel ranges start at same value.
Autogen table takes care of the corresponding ring allocations as well.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
j721e: rm-cfg: Updated 2019.02 RM config
This is auto generated RM config file to describe the
resource partitioning for 2019.02 use cases.
* Assign few channels/rings for A72_3 to be used by VMs
* Assign extended channels for DRU/VPAC/DMPAC
* Adjust resources for Main R5_0_1 for ethernet firmware
* Reduce resources for R5_1_* cores since nothing is running there
* Update the resource entry count
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Acked-by: Vignesh Raghavendra <vigneshr@ti.com>
This is auto generated RM config file to describe the
resource partitioning for 2019.02 use cases.
* Assign few channels/rings for A72_3 to be used by VMs
* Assign extended channels for DRU/VPAC/DMPAC
* Adjust resources for Main R5_0_1 for ethernet firmware
* Reduce resources for R5_1_* cores since nothing is running there
* Update the resource entry count
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Acked-by: Vignesh Raghavendra <vigneshr@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.06
Update the Makefile to automatically fetch and build the v2019.06
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Suman Anna <s-anna@ti.com>
Update the Makefile to automatically fetch and build the v2019.06
version of the sysfw binaries for both AM65x and J721E SoCs.
Signed-off-by: Suman Anna <s-anna@ti.com>
Makefile: Fix HS builds by removing version reporting dependency
The rule for making the HS sysfw.bin file concatenates all its
dependencies, the rule for 'sysfw_version' is a phony target and does
not produce a file. Drop this dependency for HS.
While we are here lets do the same for non-HS builds. Phony targets
force the rebuilding of any rule that depends on them, this can
cause Make to perform more build steps than are actually needed.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@ti.com>
The rule for making the HS sysfw.bin file concatenates all its
dependencies, the rule for 'sysfw_version' is a phony target and does
not produce a file. Drop this dependency for HS.
While we are here lets do the same for non-HS builds. Phony targets
force the rebuilding of any rule that depends on them, this can
cause Make to perform more build steps than are actually needed.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Tested-by: Denys Dmytriyenko <denys@ti.com>
linux-firmware: Update am65x/j721e sysfw to v2019.05
Update the sysfw to v2019.05 from v2019.04a. Doing so also adds support
for the K3 family J721E SoCs which are now being represented with a
dedicated firmware image in the 'ti-linux-firmware' repository.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Update the sysfw to v2019.05 from v2019.04a. Doing so also adds support
for the K3 family J721E SoCs which are now being represented with a
dedicated firmware image in the 'ti-linux-firmware' repository.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
readme: Update TI firmware Git repository branch name
The official TI firmware Git repository branch name to download
firmware files from including but not limited to System Firmware is
'ti-linux-firmware'. Update the readme document to reflect the same.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
The official TI firmware Git repository branch name to download
firmware files from including but not limited to System Firmware is
'ti-linux-firmware'. Update the readme document to reflect the same.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Introduce initial J721E EVM support
Add the consolidated configuration files that were arrived at during
J721E silicon wakeup. Note that SYSFW debug trace both to memory as well
as to the UART is disabled in alignment with the production configuration
used on AM65x. If debug trace output is desired during development refer
to the SYSFW release documentation (referenced in the included README.md
file) discussion related to 'trace_dst_enables' and 'trace_src_enables'.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Cc: Nishanth Menon <nm@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Nikhil Devshatwar <nikhil.nd@ti.com>
Add the consolidated configuration files that were arrived at during
J721E silicon wakeup. Note that SYSFW debug trace both to memory as well
as to the UART is disabled in alignment with the production configuration
used on AM65x. If debug trace output is desired during development refer
to the SYSFW release documentation (referenced in the included README.md
file) discussion related to 'trace_dst_enables' and 'trace_src_enables'.
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Cc: Nishanth Menon <nm@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Lokesh Vutla <lokeshvutla@ti.com>
Cc: Nikhil Devshatwar <nikhil.nd@ti.com>
include: Add J721E specific headers corresponding to SYSFW
Introduce initial J721E specific headers
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Introduce initial J721E specific headers
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
gen_its.sh: Add SIG version and build info into the generated itb
Introduce the version of System Firmware Image Generator (SIG) as well
as the SOC variant and used CONFIG back into the generated image tree
blob so we can track those important aspects after deployment.
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 the version of System Firmware Image Generator (SIG) as well
as the SOC variant and used CONFIG back into the generated image tree
blob so we can track those important aspects after deployment.
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: Allow for builds for multiple SoCs
Allow for multiple SoCs to be built and object file names per SoC.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Allow for multiple SoCs to be built and object file names per SoC.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
common.h: Move to be inside include folder
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
common.h: Drop all AM65x specific header definitions
Drop all the AM65x specific header 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>
Drop all the AM65x specific header 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>
common.h: Make board config data structure names generic
Rename board config data structures for better alignment as well as
to be SoC independent. While at it drop the exporting of those data
structures that was inherited from a previous project which is no
longer necessary.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Rename board config data structures for better alignment as well as
to be SoC independent. While at it drop the exporting of those data
structures that was inherited from a previous project which is no
longer necessary.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
common.h: Make AM65_BOARDCFG_RM_RESASG_ENTRIES generic
Make AM65_BOARDCFG_RM_RESASG_ENTRIES to be generic to allow for cross
SoC usage. While at it, add include guards to the header file.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
Make AM65_BOARDCFG_RM_RESASG_ENTRIES to be generic to allow for cross
SoC usage. While at it, add include guards to the header file.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Andreas Dannenberg <dannenberg@ti.com>
Reviewed-by: Suman Anna <s-anna@ti.com>
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>
4 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>