1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
//! Security configuration for TrustZone-enabled chips.
//!
//! # Introduction to TrustZone in ModusToolbox
//!
//! [TrustZone][trustzone] is an ARM feature that provides low-overhead software fault isolation by
//! compartmentalizing an application into "secure" and "non-secure" sub-applications, and limiting
//! access to memory and hardware peripherals based on the security state of the processor.
//!
//! Under TrustZone, the CPU core has two execution contexts with independent sets of registers:
//! the secure- and non-secure context. Each bus transaction also has a "security" attribute bit
//! indicating whether the transaction is a secure- or non-secure transaction. The secure context
//! may issue either secure- or non-secure transactions, whereas the non-secure context may only
//! issue non-secure transactions.
//!
//! On Infineon devices, every memory and peripheral region has a Memory Protection Controller
//! (MPC) or Peripheral Protection Controller (PPC) that configures the region's security
//! properties. MPCs and PPCs can be configured to allow access from either secure or non-secure
//! transactions (but not both).
//!
//! Whether the CPU issues a secure- or non-secure transaction is a property of the address. On
//! Infineon devices, bit 28 of the request address is used as a flag to determine the transaction
//! type. If the non-secure context attempts to access an address with bit 28 set, it will result
//! in a fault.
//!
//! # Interactions with drivers
//!
//! Drivers in this crate carry a generic parameter indicating the security attribute that will be
//! used to access the peripheral. When building a non-secure application, the only valid value for
//! this parameter is `NS`. When building a secure application, either `S` or `NS` may be used, with
//! the parameter defaulting to `S`. Generally, you should leave this parameter at its default
//! value; the only time you need to override it is when sharing peripherals between a secure- and
//! non-secure context (in which case the peripheral must be accessed as non-secure from both
//! contexts).
//!
//! [trustzone]: https://developer.arm.com/documentation/100690/0201/Arm-TrustZone-technology
// Copyright (c) 2026, Infineon Technologies AG or an affiliate of Infineon Technologies AG.
// SPDX-License-Identifier: Apache-2.0
//
// Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
// in compliance with the License. You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software distributed under the
// License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either
// express or implied. See the License for the specific language governing permissions and
// limitations under the License.
use crateregs;
/// The address bit used to indicate secure- vs. non-secure access.
pub const SECURE_ADDRESS_MASK: usize = 1 << 28;
cfg_select!
/// Trait representing a secure- or non-secure attribute.
/// Helper trait for applying a security attribute to a register address.
/// Typestate for the secure attribute.
;
/// Typestate for the non-secure attribute.
;
/// An enum representing a security attribute.