| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the common.h headers to add new defines from
SYSFW 2020.07-rc1.
Starting from SYSFW v2020.07-rc1, a secure_debug_config section
is mandatory in the security config. Otherwise the boot fails
on all SoCs.
Fix this by adding a section for secure_debug_config with
appropriate parameters configured on all on AM65x, AM65x SR2.0,
J721E and J7200 SoCs.
Signed-off-by: Suman Anna <s-anna@ti.com>
|
|
|
|
|
|
|
|
|
|
| |
The number of Main NavSS rings reserved by DMSC for High capacity Rx
channels is off by one. Update the board configuration validation
script and fix the RM cfg resource entries for the same on both AM65x
and AM65x SR2.0 SoCs.
Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each of the MCU R5F cores are represented by different HOST_IDs, and
the ABI 3.0 RM changes have reassigned all the MAIN2MCU interrupt router
outputs back to only the MCU R5F Core0. This breaks the IPC use-cases
when the MCU R5FSS cluster is configured for Split-mode.
Partition both the MAIN2MCU_LVL and MAIN2MCU_PLS Interrupt Router
outputs equally between the non-secure contexts of both the MCU
R5F cores.
Signed-off-by: Suman Anna <s-anna@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Main NavSS IR on AM65x SoCs has a total of 152 output interrupt
lines, out of which the first 16 are reserved for System Firmware.
The ABI 3.0 resource updates have assigned all the remaining IR
output lines to the A53 host context HOST_ID_A53_2, which is wrong.
The Main NavSS IR also supports some interrupt lines for the MCU
R5F cores (connected through MAIN2MCU LVL IR) and for each of the
3 ICSSG subsystems.
Fix up the Main NavSS IR outputs properly by adding resources for
each of the processor subsystems. The output lines [120:127] are
split equally for each of the MCU R5F cores (to support Split-mode),
leaving only 104 usable interrupts for the A53 core. The output
lines [128:151] are associated with the ICSSG subsystems.
Signed-off-by: Suman Anna <s-anna@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the common.h headers to add new defines from SYSFW 2020.04.
Starting from SYSFW v2020.04, an sa2ul_config section is mandatory in
the security config. Otherwise the boot fails.
Fix this by adding a section for sa2ul_config with all parameters
configured to 0.
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update the common.h headers to add new defines from SYSFW 2020.03.
Starting from SYSFW v2020.03, a dkek_config section is mandatory in
the security config. Otherwise the boot fails.
Fix this by adding a section for dkek_config with HOST_ID_ALL in
allowed_hosts and allow_dkek_export_tisci set.
Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
Tested-by: Suman Anna <s-anna@ti.com>
|
|
|
|
|
|
|
| |
Update the AM65x RM board configuration to use ABI 3.0 resource type
definitions.
Signed-off-by: Lokesh Vutla <lokeshvutla@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>
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
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>
|