feat(measured-boot): enable dynamic hash provisioning

Introduce dynamic hash provisioning for Measured Boot by removing the
previous static hash-selection path and allowing platforms to supply
algor

feat(measured-boot): enable dynamic hash provisioning

Introduce dynamic hash provisioning for Measured Boot by removing the
previous static hash-selection path and allowing platforms to supply
algorithm metadata at runtime. Add mboot_find_event_log_metadata() as a
common helper for resolving image metadata. Update the Event Log build
logic to use MAX_DIGEST_SIZE and MAX_HASH_COUNT, deprecate legacy
MBOOT_EL_HASH_ALG, and warn when it is used. Adjust MbedTLS
configuration to enable hash algorithms automatically when Measured Boot
is enabled.

Change-Id: I704e1a5005f6caad3d51d868bacc53699b6dd64f
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>

show more ...

fix(build): don't rely on Event Log build tree

Follow proper CMake usage by installing libeventlog and referring to
the installed artifacts rather than the build directory. The previous
approach rel

fix(build): don't rely on Event Log build tree

Follow proper CMake usage by installing libeventlog and referring to
the installed artifacts rather than the build directory. The previous
approach relied on build-tree paths, which is considered an anti-
pattern and may break across CMake versions since the build layout is
not stable or part of the public interface.

This change installs libeventlog into a staging directory and updates
the TF-A build to use the installed include and library paths. This
improves portability, stability, and compliance with CMake idioms.

Change-Id: I740a558fd6f3163a6af3b122e9e1df558a045872
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>

show more ...

fix(build): link Event Log library directly

The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This t

fix(build): link Event Log library directly

The `libraries` target is a `.PHONY` target to which various real
library targets, including the Event Log library, have been added over
the years. This target is added as a dependency to any target created
with the `MAKE_BL` function. While this might look convenient on the
surface, it also dictates that a library must be linked even to images
it is totally irrelevant for.

The Event Log library is a good example of this; the library is not
typically used by all images, but by attaching itself to the `libraries`
target it becomes mandatory for all of them.

This change returns some of the control over when and where the Event
Log goes to platform maintainers via the introduction of two new
variables:

- `LIBEVLOG_LIBS`: the path to the Event Log static library.
- `LIBEVLOG_INCLUDE_DIRS`: include directories for the public API.

These can be appended to `BLx_LIBS` and `BLx_INCLUDE_DIRS` to include
the Event Log library in the relevant bootloaders.

Change-Id: I3e1a48cd45493334590b34b2ade0c6e29cbfd47a
Signed-off-by: Chris Kay <chris.kay@arm.com>

show more ...

fix(build): forward compiler launcher to CMake

To ensure that compiler launchers like `ccache` are forwarded to CMake,
we need to provide them separately via `CMAKE_C_COMPILER_LAUNCHER`.

Change-Id:

fix(build): forward compiler launcher to CMake

To ensure that compiler launchers like `ccache` are forwarded to CMake,
we need to provide them separately via `CMAKE_C_COMPILER_LAUNCHER`.

Change-Id: I943d2fb5aaefe3915dbe424cb29277bac6dae799
Signed-off-by: Chris Kay <chris.kay@arm.com>

show more ...

fix(build): force CMake to cross-compile

CMake provides the `CMAKE_SYSTEM_NAME` variable, which identifies the
target operating system that the project is being built for. By default
this variable i

fix(build): force CMake to cross-compile

CMake provides the `CMAKE_SYSTEM_NAME` variable, which identifies the
target operating system that the project is being built for. By default
this variable inherits its value from `CMAKE_HOST_SYSTEM_NAME`, which
identifies the operating system of the host machine.

If these two variables differ in value, CMake determines that the
project is being cross-compiled, and changes some of its behaviours.

For example: on macOS, unless cross-compiling is enabled, CMake passes
Apple Clang's `-arch` flag to the C compiler whether it is Apple Clang
or not.

To resolve this, this change now sets the following CMake variables:

- `CMAKE_SYSTEM_NAME` to `Generic`, indicating no specific system.
- `CMAKE_SYSTEM_VERSION` to ``, to un-inherit the host system version.

See the CMake documentation for the following variables:

- https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER.html
- https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_HOST_COMPILER.html
- https://cmake.org/cmake/help/latest/variable/CMAKE_CROSSCOMPILING.html

Change-Id: Id5406c61baec459f56b6a105b3b507d238ff2847
Signed-off-by: Chris Kay <chris.kay@arm.com>

show more ...

fix(build): correctly forward C compiler to CMake

When `$($(ARCH)-cc)` does not represent a valid program name or path,
CMake fails to configure the Event Log library.

This occurs because CMake tre

fix(build): correctly forward C compiler to CMake

When `$($(ARCH)-cc)` does not represent a valid program name or path,
CMake fails to configure the Event Log library.

This occurs because CMake treats `CMAKE_C_COMPILER` as a
semicolon-delimited list of arguments to pass to `exec()`, whereas we
provide it the value of `$($(ARCH)-cc)`, which is a shell fragment that
does not necessarily represent a correct program path.

This change ensures that we pass a semicolon-delimited list as is
expected by CMake.

Change-Id: I1dd3e53624054c4b5c881be1ab99e77ea22ceba2
Signed-off-by: Chris Kay <chris.kay@arm.com>

show more ...

fix(dice): prevent compiler warnings

LTO builds make the compiler observe possible unitialised accesses.
That's not the case, but calm it down with a 0. It also doesn't like the
declaration mismatch

fix(dice): prevent compiler warnings

LTO builds make the compiler observe possible unitialised accesses.
That's not the case, but calm it down with a 0. It also doesn't like the
declaration mismatch in tc so bring it in line.

Change-Id: I0276257d05d1cb1d4f7e1e0d914c48c8ab3d308d
Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com>

show more ...

build(measured-boot)!: move to ext event log lib

Removes in-tree Event Log library implementation and updates all
references to use the external submodule. Updates include paths,
Makefile macros, an

build(measured-boot)!: move to ext event log lib

Removes in-tree Event Log library implementation and updates all
references to use the external submodule. Updates include paths,
Makefile macros, and platform integration logic to link with lib as a
static library.

If you cloned TF-A without the `--recurse-submodules` flag, you can
ensure that this submodule is present by running:

git submodule update --init --recursive

BREAKING-CHANGE: LibEventLog is now included in TF-A as a submodule.
Please run `git submodule update --init --recursive` if you encounter
issues after migrating to the latest version of TF-A.

Change-Id: I723f493033c178759a45ea04118e7cc295dc2438
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>

show more ...

feat(measured-boot): add fw handoff event log utils

Add utilities for handling an event log from a transfer list. These
handle initialisation, and extension of an existing event log.

Change-Id: I42

feat(measured-boot): add fw handoff event log utils

Add utilities for handling an event log from a transfer list. These
handle initialisation, and extension of an existing event log.

Change-Id: I42d8b65a7fa82fa866d8ac258d9eeb58af730a96
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>

show more ...

refactor(measured-boot): refine event log lib docs

Add comments for all exported functions and move these descriptions to
the header file. Moving the descriptions to the header file allows the
docum

refactor(measured-boot): refine event log lib docs

Add comments for all exported functions and move these descriptions to
the header file. Moving the descriptions to the header file allows the
documentation to be easily accessible to any code that includes the
header file, without having to look through the source file where the
function implementation is located.

Change-Id: I78ad777cb3de1707f9e9df59c721cd6370317c05
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>

show more ...

feat(measured-boot): make event log lib standalone

Remove dependencies on TF-A so the library can be conveniently exported
by other projets. The main changes are to remove explicit error
handling, a

feat(measured-boot): make event log lib standalone

Remove dependencies on TF-A so the library can be conveniently exported
by other projets. The main changes are to remove explicit error
handling, and ensure that functions instead return errno codes that
consumers can rely on instead. Some work has also been done to make the
function naming a little more consistent.

Change-Id: Ic182dfe7dd6f56a4b73e0da4c9051813938cfe44
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>

show more ...

refactor(measured-boot): standardize function names

Rename existing printer functions to follow the `event_log_{func}`
convention used in other parts of the logging library. This is the first
in a s

refactor(measured-boot): standardize function names

Rename existing printer functions to follow the `event_log_{func}`
convention used in other parts of the logging library. This is the first
in a series of changes to prepare the event log library to be a
standalone component.

Change-Id: I11c924587c0f67af383f7c68d64d78bbe931cfcd
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>

show more ...

feat(tpm): add tpm drivers and framework

Add tpm2 drivers to tf-a with adequate framework
-implement a fifo spi interface that works
with discrete tpm chip.
-implement tpm command layer interfaces

feat(tpm): add tpm drivers and framework

Add tpm2 drivers to tf-a with adequate framework
-implement a fifo spi interface that works
with discrete tpm chip.
-implement tpm command layer interfaces that are used
to initialize, start and make measurements and
close the interface.
-tpm drivers are built using their own make file
to allow for ease in porting across platforms,
and across different interfaces.

Signed-off-by: Tushar Khandelwal <tushar.khandelwal@arm.com>
Signed-off-by: Abhi Singh <abhi.singh@arm.com>
Change-Id: Ie1a189f45c80f26f4dea16c3bd71b1503709e0ea

show more ...

feat(tc): provide target_locality info of AP FW components

The target_locality attribute is meant to specify that
a certain SW component is expected to run and thereby
send DPE commands from a given

feat(tc): provide target_locality info of AP FW components

The target_locality attribute is meant to specify that
a certain SW component is expected to run and thereby
send DPE commands from a given security domain. The DPE
service must be capable of determining the locality of
a client on his own. RSE determines the client's locality
based on the MHU channel used for communication.

If the expected locality (specified by the parent component)
is not matching with the determined locality by DPE
service then command fails.

The goal is to protect against spoofing when a
context_handle is stolen and used by a component
that should not have access.

Signed-off-by: Tamas Ban <tamas.ban@arm.com>
Change-Id: I96d255de231611cfed10eef4335a47b91c2c94de

show more ...

refactor(dice): save parent context handle

Improve the restart handling of DPE. In the case of a restart
scenario where only that core is restarted which executes
the DPE client, but the core execut

refactor(dice): save parent context handle

Improve the restart handling of DPE. In the case of a restart
scenario where only that core is restarted which executes
the DPE client, but the core executes the DPE service
remains up and running. In this case, client needs to save
a valid context handle to be able to send commands again
to the DPE service during the new boot sequence.

BL1 saves a valid parent context handle to SDS
before passing the execution to BL2. This handle
can be used in case of a restart scenario when AP
is restarted but RSE is not. Because in that case
RSE does not save an initial context handle to SDS,
which meant to be used by AP during the boot process.

By then the very first initial context handle is
invalidated because it was already used in the
previous boot cycle by BL1.

BL2 does not need to do this, because the cold
boot starts with BL1.

Signed-off-by: Tamas Ban <tamas.ban@arm.com>
Change-Id: Id14eefd2ec758f89f672af176e4f5386a397fa35

show more ...