![]() |
TF-M Reference Manual
1.2.0
TrustedFirmware-M
|
#include <string.h>
#include "tfm/tfm_core_svc.h"
#include "tfm_secure_api.h"
#include "region_defs.h"
#include "spm_func.h"
#include "spm_partition_defs.h"
#include "tfm_api.h"
#include "tfm_memory_utils.h"
#include "tfm_arch.h"
#include "tfm_peripherals_def.h"
#include "tfm_irq_list.h"
#include "common/tfm_boot_data.h"
#include "tfm_secure_irq_handlers.inc"
Go to the source code of this file.
Functions | |
uint32_t | tfm_core_svc_handler (uint32_t *svc_args, uint32_t lr, uint32_t *msp) |
void | tfm_access_violation_handler (void) |
Should be called in case of access violation. More... | |
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 96 of file tfm_core_svcalls_func.c.
uint32_t tfm_core_svc_handler | ( | uint32_t * | svc_args, |
uint32_t | lr, | ||
uint32_t * | msp | ||
) |