| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
| |
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 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>
|
| |
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
| |
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>
|
|
|
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>
|
