AT32UC3C0128C

Manufacturer Part NumberAT32UC3C0128C
ManufacturerAtmel Corporation
AT32UC3C0128C datasheets

Availability: In stock

International delivery:

Warranty: 60 days

Shipping & payment terms

Added to cart

 

Specifications of AT32UC3C0128C

Flash (kbytes)128 KbytesPin Count144
Max. Operating Frequency66 MHzCpu32-bit AVR
Hardware Qtouch AcquisitionNoMax I/o Pins123
Ext Interrupts144Usb Transceiver1
Quadrature Decoder Channels2Usb SpeedFull Speed
Usb InterfaceDevice + OTGSpi7
Twi (i2c)3Uart5
Can2Lin5
Ssc1Ethernet1
Graphic LcdNoVideo DecoderNo
Camera InterfaceNoAdc Channels16
Adc Resolution (bits)12Adc Speed (ksps)2000
Analog Comparators4Resistive Touch ScreenNo
Dac Channels4Dac Resolution (bits)12
Temp. SensorNoCrypto EngineNo
Sram (kbytes)36Self Program MemoryYES
External Bus Interface1Dram Memorysdram
Nand InterfaceNoPicopowerNo
Temp. Range (deg C)-40 to 85I/o Supply Class3.0 to 3.6 or 4.5 to 5.5
Operating Voltage (vcc)3.0 to 3.6 or 4.5 to 5.5FpuYes
Mpu / MmuYes / NoTimers6
Output Compare Channels22Input Capture Channels12
Pwm Channels2032khz RtcYes
Calibrated Rc OscillatorYes  
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
Page 91
92
Page 92
93
Page 93
94
Page 94
95
Page 95
96
Page 96
97
Page 97
98
Page 98
99
Page 99
100
Page 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
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
Page 92/377

Download datasheet (5Mb)Embed
PrevNext
8.4
Event priority
Several instructions may be in the pipeline at the same time, and several events may be issued
in each pipeline stage. This implies that several pending exceptions may be in the pipeline
simultaneously. Priorities must therefore be imposed, ensuring that the correct event is serviced
first. The priority scheme obeys the following rules:
1. If several instructions trigger events, the instruction furthest down the pipeline is ser-
viced first, even if upstream instructions have pending events of higher priority.
2. If this instruction has several pending events, the event with the highest priority is ser-
viced first. After this event has been serviced, all pending events are cleared and the
instruction is restarted.
Details about the timing of events is IMPLEMENTATION DEFINED, and given in the hardware
manual for the specific implementation.
8.5
Event handling in secure state
Interrupt and exception handling in AVR32A and AVR32B has been described in the previous
chapters. This behavior is modified in the following way when interrupts and exceptions are
received in secure state:
• A sscall instruction will set SR[GM]. In secure state, SR[GM] masks both INT0-INT3, and
NMI. Clearing SR[GM], INT0-INT3 and NMI will remove the mask of these event sources.
INT0-INT3 are still additionally masked by the I0M-I3M bits in the status register.
• sscall has handler address at offset 0x4 relative to the reset handler address.
• Exceptions have a handler address at offset 0x8 relative to the reset handler address.
• NMI has a handler address at offset 0xC relative to the reset handler address.
• BREAKPOINT has a handler address at offset 0x10 relative to the reset handler address.
• INT0-INT3 are not autovectored, but have a common handler address at offset 0x14 relative
to the reset handler address.
Note that in the secure state, all exception sources share the same handler address. It is there-
fore not possible to separate different exception causes when in the secure world. The secure
world system must be designed to support this, the most obvious solution is to design the secure
software so that exceptions will not arise.
AVR32
92
32000D–04/2011