mbed-os5 only for TYBLE16

Dependents:   TYBLE16_simple_data_logger TYBLE16_MP3_Air

Committer:
kenjiArai
Date:
Tue Dec 31 06:02:27 2019 +0000
Revision:
1:9db0e321a9f4
Parent:
0:5b88d5760320
updated based on mbed-os5.15.0

Who changed what in which revision?

UserRevisionLine numberNew contents of line
kenjiArai 0:5b88d5760320 1 /*
kenjiArai 0:5b88d5760320 2 * Copyright (c) 2018, Arm Limited. All rights reserved.
kenjiArai 0:5b88d5760320 3 *
kenjiArai 0:5b88d5760320 4 * SPDX-License-Identifier: BSD-3-Clause
kenjiArai 0:5b88d5760320 5 *
kenjiArai 0:5b88d5760320 6 */
kenjiArai 0:5b88d5760320 7
kenjiArai 0:5b88d5760320 8 #ifndef __TFM_PLATFORM_CORE_API_H__
kenjiArai 0:5b88d5760320 9 #define __TFM_PLATFORM_CORE_API_H__
kenjiArai 0:5b88d5760320 10
kenjiArai 0:5b88d5760320 11 /**
kenjiArai 0:5b88d5760320 12 * \brief Should be called in case of access violation.
kenjiArai 0:5b88d5760320 13 *
kenjiArai 0:5b88d5760320 14 * There might be platform specific means, by which it is possible on a
kenjiArai 0:5b88d5760320 15 * subsystem to detect access violation. For example a platform can have a
kenjiArai 0:5b88d5760320 16 * Peripheral Protection Controller, to detect unauthorised accesses to
kenjiArai 0:5b88d5760320 17 * peripheral registers. Setting up the protection, and handling the violation
kenjiArai 0:5b88d5760320 18 * is implemented in platform specific code. However TF-M should be able to
kenjiArai 0:5b88d5760320 19 * decide how to proceed if a violation happens. So to notify TF-M, platform
kenjiArai 0:5b88d5760320 20 * code have to call this function, if a violation happens.
kenjiArai 0:5b88d5760320 21 */
kenjiArai 0:5b88d5760320 22 void tfm_access_violation_handler(void);
kenjiArai 0:5b88d5760320 23
kenjiArai 0:5b88d5760320 24 #endif /* __TFM_PLATFORM_CORE_API_H__ */