Secure Request Framework Configuration

General Description

The Secure Request Framework (SRF) requires modules be defined with unique values.

The values used do not matter, only that they are unique. Below are two sample modules - one for the Periphal Driver Library (PDL) and one for the user.

This file is owned by the application. The expectation is for the user to add modules as needed. Should the user wish to use a middleware library that depends on the SRF, that middleware will not add the module itself - the user must do so.

Macros
#define	MTB_SRF_MAX_ARG_IN_SIZE   (5U * sizeof(uint32_t))
	Maximum input argument count in bytes, adjusting the default BSP-generated pool.
#define	MTB_SRF_MAX_ARG_OUT_SIZE   (1U * sizeof(uint32_t))
	Maximum output argument count in bytes, adjusting the default BSP-generated pool.
#define	MTB_SRF_SECURE_ARG_BUFFER_LEN
	Size in bytes of the secure scratch buffer into which secure request inputs are copied before processing. More...
#define	MTB_SRF_POOL_SIZE   (1U)
	Number of secure requests object allocated, adjusting the default BSP-generated pool.
#define	MTB_SRF_IPC_SERVICE_TIMEOUT_US   (MTB_SRF_NEVER_TIMEOUT)
	IPC integration specific defines, adjusting the default BSP-generated setup. More...
#define	MTB_SRF_MODULE_COUNT   (2U)
	Number of modules.
#define	MTB_SRF_MODULE_PDL   (0U)
	Module for PDL operations.
#define	MTB_SRF_MODULE_USER   (1U)
	Module for User operations.

Macro Definition Documentation

MTB_SRF_SECURE_ARG_BUFFER_LEN

#define MTB_SRF_SECURE_ARG_BUFFER_LEN

Value:

    (MTB_SRF_MAX_ARG_IN_SIZE + sizeof(mtb_srf_input_ns_t) + \
     MTB_SRF_MAX_ARG_OUT_SIZE + sizeof(mtb_srf_output_ns_t) + \
     128u)

Size in bytes of the secure scratch buffer into which secure request inputs are copied before processing.

The size must be a multiple of 4 bytes, and be large enough to hold:

• An mtb_srf_input_ns_t struct
• The maximum number of scalar input arguments (MTB_SRF_MAX_ARG_IN_SIZE)
• The largest input argument passed by pointer, excluding buffers whose contents are simply sent over a communications interface without requiring validation.
• An mtb_srf_output_ns_t struct
• The maximum number of scalar output arguments (MTB_SRF_MAX_ARG_OUT_SIZE)

MTB_SRF_IPC_SERVICE_TIMEOUT_US

#define MTB_SRF_IPC_SERVICE_TIMEOUT_US   (MTB_SRF_NEVER_TIMEOUT)

IPC integration specific defines, adjusting the default BSP-generated setup.

Default timeout for sending a request that requires IPC