![]() |
TF-M Reference Manual
1.2.0
TrustedFirmware-M
|
#include <string.h>
#include "region.h"
#include "spm_ipc.h"
#include "tfm_api.h"
#include "tfm_arch.h"
#include "tfm_core_trustzone.h"
#include "tfm_svcalls.h"
#include "utilities.h"
#include "tfm/tfm_core_svc.h"
#include "common/tfm_boot_data.h"
#include "common/psa_client_service_apis.h"
Go to the source code of this file.
Functions | |
REGION_DECLARE (Image $$, TFM_UNPRIV_CODE,$$RO $$Base) | |
uint32_t | tfm_core_svc_handler (uint32_t *svc_args, uint32_t exc_return) |
The C source of SVCall handlers. More... | |
void | tfm_core_handler_mode (void) |
Move to handler mode by a SVC for specific purpose. More... | |
void | tfm_access_violation_handler (void) |
Should be called in case of access violation. More... | |
REGION_DECLARE | ( | Image | $$, |
TFM_UNPRIV_CODE | , | ||
$$RO | |||
) |
void tfm_access_violation_handler | ( | void | ) |
Should be called in case of access violation.
There might be platform specific means, by which it is possible on a subsystem to detect access violation. For example a platform can have a Peripheral Protection Controller, to detect unauthorised accesses to peripheral registers. Setting up the protection, and handling the violation is implemented in platform specific code. However TF-M should be able to decide how to proceed if a violation happens. So to notify TF-M, platform code have to call this function, if a violation happens.
Definition at line 164 of file tfm_core_svcalls_ipc.c.
void tfm_core_handler_mode | ( | void | ) |
Move to handler mode by a SVC for specific purpose.
Definition at line 157 of file tfm_core_svcalls_ipc.c.
uint32_t tfm_core_svc_handler | ( | uint32_t * | svc_args, |
uint32_t | exc_return | ||
) |
The C source of SVCall handlers.
[in] | svc_args | The arguments list. |
[in] | exc_return | EXC_RETURN value of the SVC. |
Definition at line 121 of file tfm_core_svcalls_ipc.c.