feat(auth): introducing auth.mkIntroducing authentication specific makefile auth.mk to include commonauth source files.Signed-off-by: Lauren Wehrmeister <lauren.wehrmeister@arm.com>Change-Id: I
feat(auth): introducing auth.mkIntroducing authentication specific makefile auth.mk to include commonauth source files.Signed-off-by: Lauren Wehrmeister <lauren.wehrmeister@arm.com>Change-Id: Ifb07c48861fe415d82cb7390c3a5f6e60ba699d9
show more ...
fix(build): ensure `$(ROT_KEY)` depends on correct directory rulesIn order for directories to be automatically created when used as adependency, they must end with a forward slash (`/`). This is b
fix(build): ensure `$(ROT_KEY)` depends on correct directory rulesIn order for directories to be automatically created when used as adependency, they must end with a forward slash (`/`). This is because wehave a pattern rule (`%/`) to create a directory anywhere where adirectory is required as a direct dependency.Change-Id: Ib632d59da0745f6cadb0a839a62360aeca25c178Signed-off-by: Chris Kay <chris.kay@arm.com>
build: unify verbosity handlingThis change introduces a few helper variables for dealing with verboseand silent build modes: `silent`, `verbose`, `q` and `s`.The `silent` and `verbose` variables
build: unify verbosity handlingThis change introduces a few helper variables for dealing with verboseand silent build modes: `silent`, `verbose`, `q` and `s`.The `silent` and `verbose` variables are boolean values determiningwhether the build system has been configured to run silently orverbosely respectively (i.e. with `--silent` or `V=1`).These two modes cannot be used together - if `silent` is truthy then`verbose` is always falsy. As such: make --silent V=1... results in a silent build.In addition to these boolean variables, we also introduce two newvariables - `s` and `q` - for use in rule recipes to conditionallysuppress the output of commands.When building silently, `s` expands to a value which disables thecommand that follows, and `q` expands to a value which supppressesechoing of the command: $(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed but not echoed'When building verbosely, `s` expands to a value which disables thecommand that follows, and `q` expands to nothing: $(s)echo 'This command is neither echoed nor executed' $(q)echo 'This command is executed and echoed'In all other cases, both `s` and `q` expand to a value which suppressesechoing of the command that follows: $(s)echo 'This command is executed but not echoed' $(q)echo 'This command is executed but not echoed'The `s` variable is predominantly useful for `echo` commands, where youalways want to suppress echoing of the command itself, whilst `q` ismore useful for all other commands.Change-Id: I8d8ff6ed714d3cb401946c52955887ed7dca602bSigned-off-by: Chris Kay <chris.kay@arm.com>
fix: make TF-A use provided OpenSSL binaryCurrently Tf-A uses whatever openssl binary is on the system to signimages. However if OPENSSL_DIR is specified in the build flags this canlead to linkin
fix: make TF-A use provided OpenSSL binaryCurrently Tf-A uses whatever openssl binary is on the system to signimages. However if OPENSSL_DIR is specified in the build flags this canlead to linking issues as the system binary can end up being linkedagainst shared libraries provided in OPENSSL_DIR/lib if both binaries(the system's and the on in OPENSSL_DIR/bin) are the same version.This patch ensures that the binary used is always the one given byOPENSSL_DIR to avoid those link issues.Signed-off-by: Salome Thirot <salome.thirot@arm.com>Change-Id: Ib534e06ebc8482e4391e376d3791a87968de4a99
feat(layerscape): add CHASSIS 3 support for tbbrSupport CHASSIS 3.0(such as SoC LS1088A).Signed-off-by: Biwen Li <biwen.li@nxp.com>Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>Change-Id: I6084
feat(layerscape): add CHASSIS 3 support for tbbrSupport CHASSIS 3.0(such as SoC LS1088A).Signed-off-by: Biwen Li <biwen.li@nxp.com>Signed-off-by: Jiafei Pan <Jiafei.Pan@nxp.com>Change-Id: I60843bc4d604f0de1d91c6d3ad5eb4921cdcc91a
nxp: supports two mode of trusted board bootNXP SoC supports two TBB mode:- MBED_TLS based -- ROTK key hash is placed as part of the BL2 binary at section: --- .rodata.nxp_rotpk_hash -- S
nxp: supports two mode of trusted board bootNXP SoC supports two TBB mode:- MBED_TLS based -- ROTK key hash is placed as part of the BL2 binary at section: --- .rodata.nxp_rotpk_hash -- Supporting non-volatile counter via SFP. -- platform function used by TFA common authentication code.- NXP CSF based -- ROTK key deployment vary from MBEDTLSSigned-off-by: Ruchika Gupta <ruchika.gupta@nxp.com>Signed-off-by: Pankaj Gupta <pankaj.gupta@nxp.com>Change-Id: Ib0f0bf024fd93de906c5d4f609383ae9e02b2fbc