summaryrefslogtreecommitdiffstats
path: root/soc/j7200
Commit message (Collapse)AuthorAgeFilesLines
* build: Introduce COMBINED_TIFS_BRDCFG build variable for split boardcfgDave Gerlach2021-01-051-1/+1
| | | | | | | | | | | | | | | | | | J7200 supports using a split firmware where TIFS firmware runs on the DMSC and DM firmware runs on an R5, and each are able to receive their own boardcfg loaded from the tiboot3.bin image. Currently COMBINED_SYSFW_BRDCFG can represent both a full set of boardcfg for platforms using a single DMSC firmware or only the TIFS boardcfg when using split firmware. To make this less confusing, introduce a COMBINED_TIFS_BRDCFG build variable to be used only for TIFS BOARDCFG when using split firmware so that COMBINED_SYSFW_BRDCFG always represents a complete set of boardcfg. This allows SoCs to build bootable binaries supporting ROM combined boot images with both splt TIFS/DM firmware or complete DMSC firmware. Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
* Makefile: Introduce SCIFS variable to account for SYSFW name variations07.01.00.005Suman Anna2020-11-061-0/+1
| | | | | | | | | | | | The System Firmware functionality on K3 J721E and J7200 SoCs has been reduced to only cater to the foundational security pieces starting from SYSFW 2020.08, and the binaries have been renamed accordingly. Introduce a Makefile variable SCIFS to account for these changes. Signed-off-by: Suman Anna <s-anna@ti.com> Acked-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Dan Murphy <dmurphy@ti.com>
* soc: j7200: Update block copy allocation for UDMA channelsNikhil Devshatwar2020-10-192-25/+193
| | | | | | | | | | | | | | | | | | To use UDMA channels for block copy, the Tx and Rx channel number has to be the same. When UDMA channels are allocated with just a single range, sometimes it is not possible to allocate the ranges such that the channels can be used for block copy usecase. Fix this by allocating the channels in two ranges, first range for block copy and second range for other usage. When there are no channels for block copy, an entry with 0 count is added. This is to maintain consistency when querying SYSFW about the ranges allocated for a host. Also adjust the MCU NAVSS INTA/INTR allocation after the HSM re architecture Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* scripts: gen_x509_combined_cert: modify to support multiple boardcfg imagesDave Gerlach2020-10-161-1/+2
| | | | | | | | | | | | With the new bootflows being introduced, it is possible for boards to have multiple boardcfg images provided. Modify the gen_x509_combined_cert script to accept two different boardcfg binaries and load them to the defined addresses. This mandates that all platforms using combined bootflow will use the split boardcfg images. Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
* sec-cfg: Add secure_handover_config sectionDave Gerlach2020-10-161-0/+11
| | | | | | | | | | | Update the common.h headers to add new defines from SYSFW 2020.08. Starting from SYSFW v2020.08, a secure_handover_config section is mandatory in the security config. Otherwise the boot fails on all SoCs. Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
* Makefile: Set LOADADDR in each SOC MakefileDave Gerlach2020-10-161-0/+1
| | | | | | | | | Each SOC has its own Makefile and some SOCs may have a need for a different load address, so define the LOADADDR variable in the SOC specific Makefile. Signed-off-by: Dave Gerlach <d-gerlach@ti.com> Reviewed-by: Suman Anna <s-anna@ti.com>
* soc: j7200: rm-cfg: Allocate one HC channel pair for A7207.01.00.003Vignesh Raghavendra2020-09-212-17/+73
| | | | | | | | Allocate 1 HC channel pair each in MAIN UDMA and MCU UDMA for A72 so as to enable Linux/U-Boot to demonstrate max performance with HyperFlash and OSPI. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
* soc: j7200: Update RM board config with latest dataNikhil Devshatwar2020-08-192-198/+520
| | | | | | | | | | * Increase resource allocation for meeting RTOS use cases * Add block copy channel allocation Auto generated from k3-resource-partitioning tool commit ID 8e058012d5bcc457ae1f9212425d0d0ccd534752 Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
* sec-cfg: Add secure_debug_config sectionSuman Anna2020-08-141-0/+12
| | | | | | | | | | | | | | | 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>
* soc: Introduce SoC specific MakefilesLokesh Vutla2020-08-141-0/+41
| | | | | | | | | | | Now that SoCs have different boot image targets, introduce SOC specific Makefiles to represent boot targets. Below are boot targets: - AM65x: sysfw.itb - AM65x SR2: sysfw.itb - J721E: sysfw.itb - J7200: tiboot3.bin, sysfw.itb Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
* soc: j7200: rm-cfg: Auto generate from host-toolsNikhil Devshatwar2020-08-142-3/+1613
| | | | | | | | | | Auto generated from the host-tools with: Commit ID: 1f48ea8844cff145d6b12fee3d8a0b19e0602a66 Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com> Signed-off-by: Suman Anna <s-anna@ti.com> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
* soc: j7200: Add sysfw board config dataLokesh Vutla2020-08-145-0/+342
Add the following board configurations specific to j7200 SoC: - board-cfg - pm-cfg - rm-cfg - sec-cfg Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com> Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>