Age | Commit message (Collapse) | Author |
|
Change all SPs to use the same RPC UUID as their FF-A UUID. The SPs will
keep their SP UUID as the name of the binary but the UUID stored in the
SP manifest will be the protocol UUID. This means all clients will
discover TS SPs build with this option with the same UUID.
Signed-off-by: Jelle Sels <jelle.sels@arm.com>
Signed-off-by: Imre Kis <imre.kis@arm.com>
Signed-off-by: Gyorgy Szing <Gyorgy.Szing@arm.com>
Change-Id: I662b6209cd9526b058016a907308a880c1944e7d
|
|
Due to a bug in TF-A v2.6 sptool if the UUID field is present in the SP
package's json, the sptool will crash. Since currently we don't rely on
this field, it's redundant and it can simply be removed.
Signed-off-by: Balint Dobszay <balint.dobszay@arm.com>
Change-Id: I33503252c6dd40f54f2d24a105e08ac222fc34c0
|
|
Currently in the SP manifest the UUID is represented as big-endian.
Change this to little-endian to get better aligned with OP-TEE and TF-A
which expect this format.
Signed-off-by: Balint Dobszay <balint.dobszay@arm.com>
Change-Id: I1ed9e64aab624121fa2c6586c64036f60d727fc8
|
|
Adding UUID field to opteesp/sp_pkg.json.in to prevent TF-A FIP build
to try to extract the UUID from the manifest as this may result in an
incorrect UUID endianness in the FIP package which prevents loading
the SP.
Signed-off-by: Imre Kis <imre.kis@arm.com>
Change-Id: Id6ab6e3608d210608076d79dad64f68acf81c962
|
|
Configure a JSON file for each SP and export it to the install dir. The
individual files should be merged by the integrator to form the
SP_LAYOUT_FILE JSON used by TF-A to create the SP packages.
Signed-off-by: Balint Dobszay <balint.dobszay@arm.com>
Change-Id: I63674e8e584dd3285490f3be51c228718f39a998
|