ATtiny1616/3216
tinyAVR® 1-series
Introduction
The ATtiny1616/3216 are members of the tinyAVR® 1-series of microcontrollers, using the AVR®
processor with hardware multiplier, running at up to 20 MHz, with 16/32 KB Flash, 2 KB of SRAM, and
256 bytes of EEPROM in a 20-pin package. The tinyAVR® 1-series uses the latest technologies with a
flexible, low-power architecture including Event System and SleepWalking, accurate analog features, and
Core Independent Peripherals. Capacitive touch interfaces with driven shield are supported with the
integrated QTouch® peripheral touch controller.
Attention: Automotive products are documented in separate data sheets.
Features
• CPU
– AVR® CPU
– Running at up to 20 MHz
– Single-cycle I/O access
– Two-level interrupt controller
– Two-cycle hardware multiplier
• Memories
– 32/16 KB In-system self-programmable Flash memory
– 256 bytes EEPROM
– 2 KB SRAM
– Write/erase endurance:
• Flash 10,000 cycles
• EEPROM 100,000 cycles
– Data retention:
• 40 years at 55°C
• System
– Power-on Reset (POR)
– Brown-out Detector (BOD)
– Clock options:
• 16/20 MHz low-power internal RC oscillator
• 32.768 kHz Ultra Low-Power (ULP) internal RC oscillator
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 1
ATtiny1616/3216
• 32.768 kHz external crystal oscillator
• External clock input
– Single-pin Unified Program and Debug Interface (UPDI)
– Three sleep modes:
• Idle with all peripherals running for immediate wake-up
• Standby
– Configurable operation of selected peripherals
– SleepWalking peripherals
• Power-Down with full data retention
• Peripherals
– One 16-bit Timer/Counter type A (TCA) with dedicated period register and three compare
channels
– Two 16-bit Timer/Counter type B (TCB) with input capture
– One 12-bit Timer/Counter type D (TCD) optimized for control applications
– One 16-bit Real-Time Counter (RTC) running from an external crystal, external clock, or internal
RC oscillator
– Watchdog Timer (WDT) with Window mode, with a separate on-chip oscillator
– One USART with fractional baud rate generator, auto-baud, and start-of-frame detection
– One master/slave Serial Peripheral Interface (SPI)
– One Two-Wire Interface (TWI) with dual address match
• Philips I2C compatible
• Standard mode (Sm, 100 kHz)
• Fast mode (Fm, 400 kHz)
• Fast mode plus (Fm+, 1 MHz)
– Three Analog Comparators (AC) with low propagation delay
– Two 10-bit 115 ksps Analog-to-Digital Converters (ADC)
– Three 8-bit Digital-to-Analog Converters (DAC) with one external channel
– Multiple voltage references (VREF):
• 0.55V
• 1.1V
• 1.5V
• 2.5V
• 4.3V
– Event System (EVSYS) for CPU independent and predictable inter-peripheral signaling
– Configurable Custom Logic (CCL) with two programmable look-up tables
– Automated CRC memory scan
– Peripheral Touch Controller (PTC)
• Capacitive touch buttons, sliders, wheels and 2D surfaces
• Wake-up on touch
• Driven shield for improved moisture and noise handling performance
• Up to 12 self capacitance channels
• Up to 36 mutual capacitance channels
– External interrupt on all general purpose pins
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 2
ATtiny1616/3216
• I/O and Packages:
– 18 programmable I/O lines
– 20-pin VQFN 3x3 mm
– 20-pin SOIC300
• Temperature Ranges:
– -40°C to 105°C
– -40°C to 125°C
• Speed Grades:
– 0-5 MHz @ 1.8V – 5.5V
– 0-10 MHz @ 2.7V – 5.5V
– 0-20 MHz @ 4.5V – 5.5V
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 3
ATtiny1616/3216
Table of Contents
Introduction......................................................................................................................1
Features.......................................................................................................................... 1
1. Silicon Errata and Data Sheet Clarification Document............................................ 11
2. tinyAVR® 1-series Overview.................................................................................... 12
2.1.
Configuration Summary..............................................................................................................12
3. Block Diagram......................................................................................................... 14
4. Pinout...................................................................................................................... 15
4.1.
4.2.
20-Pin SOIC............................................................................................................................... 15
20-Pin VQFN.............................................................................................................................. 16
5. I/O Multiplexing and Considerations........................................................................17
5.1.
Multiplexed Signals.................................................................................................................... 17
6. Memories.................................................................................................................18
6.1.
6.2.
6.3.
6.4.
6.5.
6.6.
6.7.
6.8.
6.9.
6.10.
Overview.................................................................................................................................... 18
Memory Map.............................................................................................................................. 19
In-System Reprogrammable Flash Program Memory................................................................20
SRAM Data Memory.................................................................................................................. 20
EEPROM Data Memory............................................................................................................. 21
User Row....................................................................................................................................21
Signature Bytes.......................................................................................................................... 21
I/O Memory.................................................................................................................................21
Memory Section Access from CPU and UPDI on Locked Device..............................................22
Configuration and User Fuses (FUSE).......................................................................................23
7. Peripherals and Architecture................................................................................... 44
7.1.
7.2.
7.3.
Peripheral Module Address Map................................................................................................ 44
Interrupt Vector Mapping............................................................................................................ 45
System Configuration (SYSCFG)...............................................................................................47
8. AVR CPU................................................................................................................. 50
8.1.
8.2.
8.3.
8.4.
8.5.
8.6.
8.7.
Features..................................................................................................................................... 50
Overview.................................................................................................................................... 50
Architecture................................................................................................................................ 50
Arithmetic Logic Unit (ALU)........................................................................................................ 52
Functional Description................................................................................................................53
Register Summary - CPU...........................................................................................................58
Register Description................................................................................................................... 58
9. NVMCTRL - Nonvolatile Memory Controller............................................................62
9.1.
Features..................................................................................................................................... 62
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 4
ATtiny1616/3216
9.2.
9.3.
9.4.
9.5.
Overview.................................................................................................................................... 62
Functional Description................................................................................................................63
Register Summary - NVMCTRL................................................................................................. 69
Register Description................................................................................................................... 69
10. CLKCTRL - Clock Controller................................................................................... 77
10.1.
10.2.
10.3.
10.4.
10.5.
Features..................................................................................................................................... 77
Overview.................................................................................................................................... 77
Functional Description................................................................................................................79
Register Summary - CLKCTRL.................................................................................................. 84
Register Description................................................................................................................... 84
11. SLPCTRL - Sleep Controller................................................................................... 94
11.1.
11.2.
11.3.
11.4.
11.5.
Features..................................................................................................................................... 94
Overview.................................................................................................................................... 94
Functional Description................................................................................................................96
Register Summary - SLPCTRL.................................................................................................. 99
Register Description................................................................................................................... 99
12. RSTCTRL - Reset Controller.................................................................................101
12.1.
12.2.
12.3.
12.4.
12.5.
Features................................................................................................................................... 101
Overview.................................................................................................................................. 101
Functional Description..............................................................................................................102
Register Summary - RSTCTRL................................................................................................105
Register Description................................................................................................................. 105
13. CPUINT - CPU Interrupt Controller....................................................................... 108
13.1.
13.2.
13.3.
13.4.
13.5.
Features................................................................................................................................... 108
Overview.................................................................................................................................. 108
Functional Description.............................................................................................................. 110
Register Summary - CPUINT................................................................................................... 117
Register Description................................................................................................................. 117
14. EVSYS - Event System......................................................................................... 122
14.1.
14.2.
14.3.
14.4.
14.5.
Features................................................................................................................................... 122
Overview.................................................................................................................................. 122
Functional Description..............................................................................................................125
Register Summary - EVSYS.................................................................................................... 127
Register Description................................................................................................................. 127
15. PORTMUX - Port Multiplexer................................................................................ 136
15.1. Overview.................................................................................................................................. 136
15.2. Register Summary - PORTMUX.............................................................................................. 137
15.3. Register Description................................................................................................................. 137
16. PORT - I/O Pin Configuration................................................................................ 142
16.1. Features................................................................................................................................... 142
16.2. Overview.................................................................................................................................. 142
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 5
ATtiny1616/3216
16.3.
16.4.
16.5.
16.6.
16.7.
Functional Description..............................................................................................................144
Register Summary - PORT...................................................................................................... 148
Register Description - Ports..................................................................................................... 148
Register Summary - VPORT.................................................................................................... 160
Register Description - Virtual Ports.......................................................................................... 160
17. BOD - Brown-out Detector.....................................................................................165
17.1.
17.2.
17.3.
17.4.
17.5.
Features................................................................................................................................... 165
Overview.................................................................................................................................. 165
Functional Description..............................................................................................................167
Register Summary - BOD.........................................................................................................169
Register Description................................................................................................................. 169
18. VREF - Voltage Reference.................................................................................... 176
18.1.
18.2.
18.3.
18.4.
18.5.
Features................................................................................................................................... 176
Overview.................................................................................................................................. 176
Functional Description..............................................................................................................176
Register Summary - VREF.......................................................................................................178
Register Description................................................................................................................. 178
19. WDT - Watchdog Timer......................................................................................... 183
19.1.
19.2.
19.3.
19.4.
19.5.
Features................................................................................................................................... 183
Overview.................................................................................................................................. 183
Functional Description..............................................................................................................185
Register Summary - WDT........................................................................................................ 189
Register Description................................................................................................................. 189
20. TCA - 16-bit Timer/Counter Type A....................................................................... 193
20.1.
20.2.
20.3.
20.4.
20.5.
20.6.
20.7.
Features................................................................................................................................... 193
Overview.................................................................................................................................. 193
Functional Description..............................................................................................................197
Register Summary - TCA in Normal Mode (CTRLD.SPLITM=0)............................................. 207
Register Description - Normal Mode........................................................................................ 207
Register Summary - TCA in Split Mode (CTRLD.SPLITM=1).................................................. 227
Register Description - Split Mode.............................................................................................227
21. TCB - 16-bit Timer/Counter Type B....................................................................... 243
21.1.
21.2.
21.3.
21.4.
21.5.
Features................................................................................................................................... 243
Overview.................................................................................................................................. 243
Functional Description..............................................................................................................246
Register Summary - TCB......................................................................................................... 254
Register Description................................................................................................................. 254
22. TCD - 12-Bit Timer/Counter Type D...................................................................... 266
22.1.
22.2.
22.3.
22.4.
Features................................................................................................................................... 266
Overview.................................................................................................................................. 266
Functional Description..............................................................................................................270
Register Summary - TCD......................................................................................................... 292
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 6
ATtiny1616/3216
22.5. Register Description................................................................................................................. 292
23. RTC - Real-Time Counter......................................................................................312
23.1. Features................................................................................................................................... 312
23.2. Overview.................................................................................................................................. 312
23.3. RTC Functional Description..................................................................................................... 315
23.4. PIT Functional Description....................................................................................................... 315
23.5. Events...................................................................................................................................... 317
23.6. Interrupts.................................................................................................................................. 318
23.7. Sleep Mode Operation............................................................................................................. 318
23.8. Synchronization........................................................................................................................319
23.9. Configuration Change Protection............................................................................................. 319
23.10. Register Summary - RTC.........................................................................................................320
23.11. Register Description................................................................................................................. 320
24. USART - Universal Synchronous and Asynchronous Receiver and Transmitter.. 336
24.1.
24.2.
24.3.
24.4.
24.5.
Features................................................................................................................................... 336
Overview.................................................................................................................................. 336
Functional Description..............................................................................................................339
Register Summary - USART.................................................................................................... 355
Register Description................................................................................................................. 355
25. SPI - Serial Peripheral Interface............................................................................ 374
25.1.
25.2.
25.3.
25.4.
25.5.
Features................................................................................................................................... 374
Overview.................................................................................................................................. 374
Functional Description..............................................................................................................377
Register Summary - SPI...........................................................................................................387
Register Description................................................................................................................. 387
26. TWI - Two-Wire Interface.......................................................................................394
26.1.
26.2.
26.3.
26.4.
26.5.
Features................................................................................................................................... 394
Overview.................................................................................................................................. 394
Functional Description..............................................................................................................396
Register Summary - TWI..........................................................................................................410
Register Description................................................................................................................. 410
27. CRCSCAN - Cyclic Redundancy Check Memory Scan........................................ 428
27.1.
27.2.
27.3.
27.4.
27.5.
Features................................................................................................................................... 428
Overview.................................................................................................................................. 428
Functional Description..............................................................................................................430
Register Summary - CRCSCAN...............................................................................................433
Register Description................................................................................................................. 433
28. CCL - Configurable Custom Logic.........................................................................437
28.1.
28.2.
28.3.
28.4.
Features................................................................................................................................... 437
Overview.................................................................................................................................. 437
Functional Description..............................................................................................................439
Register Summary - CCL......................................................................................................... 448
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 7
ATtiny1616/3216
28.5. Register Description................................................................................................................. 448
29. AC - Analog Comparator....................................................................................... 456
29.1.
29.2.
29.3.
29.4.
29.5.
Features................................................................................................................................... 456
Overview.................................................................................................................................. 456
Functional Description..............................................................................................................458
Register Summary - AC........................................................................................................... 461
Register Description................................................................................................................. 461
30. ADC - Analog-to-Digital Converter........................................................................ 466
30.1.
30.2.
30.3.
30.4.
30.5.
Features................................................................................................................................... 466
Overview.................................................................................................................................. 466
Functional Description..............................................................................................................470
Register Summary - ADCn.......................................................................................................478
Register Description................................................................................................................. 478
31. DAC - Digital-to-Analog Converter........................................................................ 496
31.1.
31.2.
31.3.
31.4.
31.5.
Features................................................................................................................................... 496
Overview.................................................................................................................................. 496
Functional Description..............................................................................................................498
Register Summary - DAC.........................................................................................................500
Register Description................................................................................................................. 500
32. Peripheral Touch Controller (PTC)........................................................................ 503
32.1.
32.2.
32.3.
32.4.
32.5.
32.6.
Overview.................................................................................................................................. 503
Features................................................................................................................................... 503
Block Diagram.......................................................................................................................... 504
Signal Description.................................................................................................................... 504
System Dependencies............................................................................................................. 505
Functional Description..............................................................................................................506
33. UPDI - Unified Program and Debug Interface....................................................... 508
33.1.
33.2.
33.3.
33.4.
33.5.
Features................................................................................................................................... 508
Overview.................................................................................................................................. 508
Functional Description.............................................................................................................. 511
Register Summary - UPDI........................................................................................................531
Register Description................................................................................................................. 531
34. Instruction Set Summary....................................................................................... 542
35. Conventions...........................................................................................................547
35.1.
35.2.
35.3.
35.4.
Numerical Notation...................................................................................................................547
Memory Size and Type.............................................................................................................547
Frequency and Time.................................................................................................................547
Registers and Bits.................................................................................................................... 548
36. Acronyms and Abbreviations.................................................................................549
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 8
ATtiny1616/3216
37. Electrical Characteristics ...................................................................................... 552
37.1. Disclaimer.................................................................................................................................552
37.2. Absolute Maximum Ratings .....................................................................................................552
37.3. General Operating Ratings ......................................................................................................553
37.4. Power Consumption for ATtiny1616.........................................................................................554
37.5. Power Consumption for ATtiny3216.........................................................................................555
37.6. Wake-Up Time..........................................................................................................................557
37.7. Power Consumption of Peripherals..........................................................................................557
37.8. BOD and POR Characteristics................................................................................................. 558
37.9. External Reset Characteristics................................................................................................. 559
37.10. Oscillators and Clocks..............................................................................................................559
37.11. I/O Pin Characteristics..............................................................................................................561
37.12. USART..................................................................................................................................... 562
37.13. SPI........................................................................................................................................... 563
37.14. TWI...........................................................................................................................................565
37.15. VREF........................................................................................................................................567
37.16. ADC..........................................................................................................................................568
37.17. DAC..........................................................................................................................................570
37.18. AC............................................................................................................................................ 571
37.19. PTC.......................................................................................................................................... 572
37.20. UPDI Timing.............................................................................................................................573
37.21. Programming Time...................................................................................................................574
38. Typical Characteristics...........................................................................................575
38.1.
38.2.
38.3.
38.4.
38.5.
38.6.
38.7.
38.8.
Power Consumption................................................................................................................. 575
GPIO........................................................................................................................................ 589
VREF Characteristics............................................................................................................... 597
BOD Characteristics.................................................................................................................599
ADC Characteristics................................................................................................................. 602
AC Characteristics....................................................................................................................607
OSC20M Characteristics.......................................................................................................... 611
OSCULP32K Characteristics................................................................................................... 613
39. Ordering Information..............................................................................................614
39.1. Product Information.................................................................................................................. 614
39.2. Product Identification System...................................................................................................614
40. Package Drawings.................................................................................................615
40.1. Online Package Drawings........................................................................................................ 615
40.2. 20-Pin SOIC300....................................................................................................................... 616
40.3. 20-Pin VQFN............................................................................................................................ 620
41. Thermal Considerations........................................................................................ 624
41.1. Thermal Resistance Data.........................................................................................................624
41.2. Junction Temperature...............................................................................................................624
42. Errata.....................................................................................................................625
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 9
ATtiny1616/3216
42.1. Errata - ATtiny1616/3216......................................................................................................... 625
43. Data Sheet Revision History..................................................................................626
43.1. Rev. C - 07/2019...................................................................................................................... 626
43.2. Rev. B - 06/2018.......................................................................................................................627
43.3. Rev. A - 06/2018.......................................................................................................................627
The Microchip Website................................................................................................ 628
Product Change Notification Service...........................................................................628
Customer Support....................................................................................................... 628
Product Identification System...................................................................................... 629
Microchip Devices Code Protection Feature............................................................... 629
Legal Notice.................................................................................................................629
Trademarks................................................................................................................. 629
Quality Management System...................................................................................... 630
Worldwide Sales and Service......................................................................................631
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 10
ATtiny1616/3216
Silicon Errata and Data Sheet Clarification ...
1.
Silicon Errata and Data Sheet Clarification Document
Our intention is to provide our customers with the best documentation possible to ensure successful use
of Microchip products. Between data sheet updates, a Silicon Errata and Data Sheet Clarification
Document will contain the most recent information for the data sheet. The ATtiny1616/3216 Silicon Errata
and Data Sheet Clarification Document is available at the device product page on https://
www.microchip.com.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 11
ATtiny1616/3216
tinyAVR® 1-series Overview
2.
tinyAVR® 1-series Overview
The figure below shows the tinyAVR® 1-series devices, laying out pin count variants and memory sizes:
• Vertical migration upwards is possible without code modification, as these devices are pin compatible
and provide the same or more features. Downward migration may require code modification due to
fewer available instances of some peripherals.
• Horizontal migration to the left reduces the pin count and therefore, the available features.
Figure 2-1. tinyAVR® 1-series Overview
Flash
Legend:
ATtiny~~
48 KB
devices
ATtiny~~
common data sheet
32 KB
ATtiny3216
ATtiny3217
16 KB
ATtiny1614
ATtiny1616
ATtiny1617
8 KB
ATtiny814
ATtiny816
ATtiny817
ATtiny416
ATtiny417
4 KB
ATtiny412
ATtiny414
2 KB
ATtiny212
ATtiny214
8
14
20
24
Pins
Devices with different Flash memory size typically also have different SRAM and EEPROM.
Related Links
6. Memories
2.1
Configuration Summary
ATtiny1616
ATtiny3216
2.1.1
Peripheral Summary
Table 2-1. Peripheral Summary
Pins
20
20
SRAM
2 KB
2 KB
Flash
16 KB
32 KB
EEPROM
256B
256B
Max. frequency (MHz)
20
20
16-bit Timer/Counter type A (TCA)
1
1
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 12
ATtiny1616/3216
tinyAVR® 1-series Overview
ATtiny1616
ATtiny3216
...........continued
16-bit Timer/Counter type B (TCB)
2
2
12-bit Timer/Counter type D (TCD)
1
1
Real-Time Counter (RTC)
1
1
USART
1
1
SPI
1
1
1
1
ADC
2
2
ADC channels
12+8
12+8
DAC
3
3
3
3
1
1
PTC number of self capacitance
channels(1)
12XY
12XY
PTC number of mutual capacitance
channels(1)
36
36
Configurable Custom Logic
1
1
Window Watchdog
1
1
Event System channels
6
6
General purpose I/O
18
18
External interrupts
18
18
CRCSCAN
1
1
TWI
(I2C)
AC
Peripheral Touch Controller
(PTC)(1)
Note:
1. The PTC takes control over the ADC0 while the PTC is used.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 13
ATtiny1616/3216
Block Diagram
3.
Block Diagram
Figure 3-1. ATtiny1616/3216 Block Diagram
analog peripherals
®
analog
peripherals
digital peripherals
analog
peripherals
core components
UPDI
UPDI / RESET
CRC
CPU
analog
peripherals
clocks/generators
OCD
To
detectors
M
M
Flash
M
S
SRAM
BUS Matrix
S
EEPROM
S
S
AINP[3:0]
AINN[1:0]
OUT
OUT
AIN[11:0]
X[13:0]
Y[13:0]
LUTn-IN[2:0]
LUTn-OUT
WO[5:0]
WO
GPIOR
DAC [2:0]
REFA
AIN[11:0]
PORTS
AC [2:0]
ADC0 / PTC
ADC1
CCL
TCA0
TCB[1:0]
NVMCTRL
E
V
E
N
T
R
O
U
T
I
N
G
N
E
T
W
O
R
K
D
A
T
A
B
U
S
CPUINT
I
N
/
O
U
T
D
A
T
A
B
U
S
System
Management
MISO
MOSI
SCK
SS
SPI0
SDA
SCL
TWI0
BOD
VLM
SLPCTRL
Clock generation
CLKOUT
OSC20M
OSC32K
TOSC1
XOSC32K
TOSC2
EXTCLK
© 2019 Microchip Technology Inc.
POR
CLKCTRL
RTC
USART0
RST
Bandgap
TCD0
RXD
TXD
XCK
XDIR
Detectors/
References
RSTCTRL
WDT
WO[A,B,C,D]
PA[7:0]
PB[7:0]
PC[5:0]
EVSYS
Preliminary Datasheet
EXTCLK
EVOUT[n:0]
40001997C-page 14
ATtiny1616/3216
Pinout
4.
Pinout
4.1
20-Pin SOIC
VDD
1
20
GND
PA4
2
19
PA3/EXTCLK
PA5
3
18
PA2
PA6
4
17
PA1
PA7
5
16
PA0/RESET/UPDI
PB5
6
15
PC3
PB4
7
14
PC2
TOSC1/PB3
8
13
PC1
TOSC2/PB2
9
12
PC0
PB1
10
11
PB0
Input supply
Programming, Debug, Reset
Ground
Clock, crystal
GPIO VDD power domain
Digital function only
Analog function
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 15
ATtiny1616/3216
Pinout
PA1
PA0/RESET/UPDI
PC3
PC2
PC1
20
19
18
17
16
20-Pin VQFN
3
13
PB1
VDD
4
12
PB2/TOSC2
PA4
5
11
PB3/TOSC1
10
GND
PB4
PB0
9
14
PB5
2
8
EXTCLK /PA3
PA7
PC0
7
15
PA6
1
6
PA2
PA5
4.2
Input supply
Programming, Debug, Reset
Ground
Clock, crystal
GPIO VDD power domain
Digital function only
Analog function
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 16
ATtiny1616/3216
I/O Multiplexing and Considerations
5.
I/O Multiplexing and Considerations
5.1
Multiplexed Signals
SOIC 20-Pin
VQFN 20-Pin
Table 5-1. PORT Function Multiplexing
Pin Name (1,2) Other/Special
19 16 PA0
RESET/ UPDI
ADC0 ADC1 PTC(4)
AC0
AC1
AC2
DAC0 USART0 SPI0
TCA0
TCBn
TCD0 CCL
AIN0
LUT0-IN0
1
18 PA2
EVOUT0
AIN2
TxD(3)
RxD(3)
2
19 PA3
EXTCLK
AIN3
XCK(3)
3
20 GND
4
1
5
2
PA4
AIN4
AIN0 X0/Y0
6
3
PA5
VREFA
AIN5
AIN1 X1/Y1
OUT
7
4
PA6
AIN6
AIN2 X2/Y2
AINN0 AINP1 AINP0 OUT
8
5
PA7
AIN7
AIN3 X3/Y3
AINP0 AINP0 AINN0
9
6
PB5
10 7
PB4
20 17 PA1
TWI0
AIN1
MOSI
SCK
MISO
SDA(3)
SCL(3)
LUT0-IN1
LUT0-IN2
WO3
TCB1 WO
VDD
CLKOUT
11 8
PB3
TOSC1
12 9
PB2
TOSC2, EVOUT1
AIN8
X12/Y12 AINP1
AIN9
X13/Y13 AINN1 AINP3
X4/Y4
14 11 PB0
AIN11
X5/Y5
15 12 PC0
AIN6 X6/Y6
16 13 PC1
AIN7 X7/Y7
EVOUT2
18 15 PC3
AIN8 X8/Y8
AIN9 X9/Y9
AINP2 AINP1
WOB
LUT1-OUT
LUT0-OUT(3)
WO0(3)
RxD
AINP2
WOA LUT0-OUT
TCB0 WO
WO2(3)
WO1(3)
AINP2
OUT
AIN10
WO4
WO5
OUT
13 10 PB1
17 14 PC2
XDIR(3) SS
AINN0
TxD
WO2
XCK
SDA
WO1
XDIR
SCL
WO0
SCK(3)
MISO(3)
MOSI(3)
SS(3)
TCB0 WO(3) WOC
WOD LUT1-OUT(3)
WO3(3)
LUT1-IN0
Note:
1. Pin names are of type Pxn, with x being the PORT instance (A, B) and n the pin number. Notation
for signals is PORTx_PINn. All pins can be used as event input.
2. All pins can be used for external interrupt, where pins Px2 and Px6 of each port have full
asynchronous detection.
3. Alternate pin positions. For selecting the alternate positions, refer to the PORTMUX documentation.
4. Every PTC line can be configured as X- or Y-line.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 17
ATtiny1616/3216
Memories
6.
Memories
6.1
Overview
The main memories are SRAM data memory, EEPROM data memory, and Flash program memory. In
addition, the peripheral registers are located in the I/O memory space.
Table 6-1. Physical Properties of EEPROM
Property
ATtiny1616
ATtiny3216
Size
256 bytes
256 bytes
Page size
32 bytes
64 bytes
Number of pages
8
4
Start address
0x1400
0x1400
Table 6-2. Physical Properties of SRAM
Property
ATtiny1616
ATtiny3216
Size
2 KB
2 KB
Start address
0x3800
0x3800
Table 6-3. Physical Properties of Flash Memory
Property
ATtiny1616
ATtiny3216
Size
16 KB
32 KB
Page size
64 bytes
128 bytes
Number of pages
256
256
Start address
0x8000
0x8000
Related Links
6.2 Memory Map
6.5 EEPROM Data Memory
6.4 SRAM Data Memory
6.3 In-System Reprogrammable Flash Program Memory
9. NVMCTRL - Nonvolatile Memory Controller
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 18
ATtiny1616/3216
Memories
6.2
Memory Map
Figure 6-1. Memory Map ATtiny3216
64 I/O Registers
0x0000 – 0x003F
960 Ext I/O Registers
0x0040 – 0x0FFF
NVM I/O Registers and Data
0x1000 – 0x13FF
EEPROM 256 bytes
0x1400 – 0x14FF
(Reserved)
Internal SRAM
2KB
0x3800 – 0x3FFF
(Reserved)
Boot
Flash
32KB
Application
Code
Application
Data
© 2019 Microchip Technology Inc.
0x8000
0xFFFF
Preliminary Datasheet
40001997C-page 19
ATtiny1616/3216
Memories
Figure 6-2. Memory Map ATtiny1616
64 I/O Registers
0x0000 – 0x003F
960 Ext I/O Registers
0x0040 – 0x0FFF
NVM I/O Registers and Data
0x1000 – 0x13FF
EEPROM 256 bytes
0x1400 – 0x14FF
(Reserved)
Internal SRAM
2KB
0x3800 – 0x3FFF
(Reserved)
Boot
Flash
16KB
0x8000 - BOOTEND
Application
Code
App Data
APPEND
0xBFFF
(Reserved)
0xFFFF
6.3
In-System Reprogrammable Flash Program Memory
The ATtiny1616/3216 contains 32/16 KB on-chip in-system reprogrammable Flash memory for program
storage. Since all AVR instructions are 16 or 32 bits wide, the Flash is organized as 4K x 16. For write
protection, the Flash program memory space can be divided into three sections (see the illustration
below): Bootloader section, application code section, and application data section, with restricted access
rights among them.
The Program Counter (PC) is 13/14 bits wide to address the whole program memory. The procedure for
writing Flash memory is described in detail in the documentation of the Nonvolatile Memory Controller
(NVMCTRL) peripheral.
The entire Flash memory is mapped in the memory space and is accessible with normal LD/ST
instructions as well as the LPM instruction. For LD/ST instructions, the Flash is mapped from address
0x8000. For the LPM instruction, the Flash start address is 0x0000.
The ATtiny1616/3216 also has a CRC peripheral that is a master on the bus.
Related Links
2.1 Configuration Summary
9. NVMCTRL - Nonvolatile Memory Controller
6.4
SRAM Data Memory
The 2 KB SRAM is used for data storage and stack.
Related Links
8. AVR CPU
8.5.4 Stack and Stack Pointer
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 20
ATtiny1616/3216
Memories
6.5
EEPROM Data Memory
The ATtiny1616/3216 has 256 bytes of EEPROM data memory, see Memory Map section. The EEPROM
memory supports single byte read and write. The EEPROM is controlled by the Nonvolatile Memory
Controller (NVMCTRL).
Related Links
6.2 Memory Map
9. NVMCTRL - Nonvolatile Memory Controller
17. BOD - Brown-out Detector
6.6
User Row
In addition to the EEPROM, the ATtiny1616/3216 has one extra page of EEPROM memory that can be
used for firmware settings, the User Row (USERROW). This memory supports single byte read and write
as the normal EEPROM. The CPU can write and read this memory as normal EEPROM and the UPDI
can write and read it as a normal EEPROM memory if the part is unlocked. The User Row can be written
by the UPDI when the part is locked. USERROW is not affected by a chip erase.
Related Links
6.2 Memory Map
9. NVMCTRL - Nonvolatile Memory Controller
33. UPDI - Unified Program and Debug Interface
6.7
Signature Bytes
All ATtiny microcontrollers have a 3-byte signature code that identifies the device. The three bytes reside
in a separate address space. For the device, the signature bytes are given in the following table.
Note: When the device is locked, only the System Information Block (SIB) can be obtained.
Table 6-4. Device ID
Device Name
Signature Bytes Address
0x00
0x01
0x02
ATtiny1616
0x1E
0x94
0x21
ATtiny3216
0x1E
0x95
0x21
Related Links
33.3.6 System Information Block
6.8
I/O Memory
All ATtiny1616/3216 I/Os and peripherals are located in the I/O memory space. The I/O address range
from 0x00 to 0x3F can be accessed in a single cycle using IN and OUT instructions. The extended I/O
memory space from 0x0040 - 0x0FFF can be accessed by the LD/LDS/LDD and ST/STS/STD instructions,
transferring data between the 32 general purpose working registers and the I/O memory space.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 21
ATtiny1616/3216
Memories
I/O registers within the address range 0x00 - 0x1F are directly bit accessible using the SBI and CBI
instructions. In these registers, the value of single bits can be checked by using the SBIS and SBIC
instructions. Refer to the Instruction Set section for more details.
For compatibility with future devices, reserved bits should be written to zero if accessed. Reserved I/O
memory addresses should never be written.
Some of the interrupt flags are cleared by writing a '1' to them. On ATtiny1616/3216 devices, the CBI and
SBI instructions will only operate on the specified bit and can be used on registers containing such
interrupt flags. The CBI and SBI instructions work with registers 0x00 - 0x1F only.
General Purpose I/O Registers
The ATtiny1616/3216 devices provide four general purpose I/O registers. These registers can be used for
storing any information, and they are particularly useful for storing global variables and interrupt flags.
General purpose I/O registers, which reside in the address range 0x1C - 0x1F, are directly bit accessible
using the SBI, CBI, SBIS, and SBIC instructions.
Related Links
6.2 Memory Map
34. Instruction Set Summary
6.9
Memory Section Access from CPU and UPDI on Locked Device
The device can be locked so that the memories cannot be read using the UPDI. The locking protects both
the Flash (all BOOT, APPCODE, and APPDATA sections), SRAM, and the EEPROM including the FUSE
data. This prevents successful reading of application data or code using the debugger interface. Regular
memory access from within the application still is enabled.
The device is locked by writing any non-valid value to the LOCKBIT bit field in FUSE.LOCKBIT.
Table 6-5. Memory Access in Unlocked Mode (FUSE.LOCKBIT Valid)(1)
Memory Section
CPU Access
UPDI Access
Read
Write
Read
Write
SRAM
Yes
Yes
Yes
Yes
Registers
Yes
Yes
Yes
Yes
Flash
Yes
Yes
Yes
Yes
EEPROM
Yes
Yes
Yes
Yes
USERROW
Yes
Yes
Yes
Yes
SIGROW
Yes
No
Yes
No
Other Fuses
Yes
No
Yes
Yes
Table 6-6. Memory Access in Locked Mode (FUSE.LOCKBIT Invalid)(1)
Memory Section
SRAM
CPU Access
UPDI Access
Read
Write
Read
Write
Yes
Yes
No
No
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 22
ATtiny1616/3216
Memories
...........continued
Memory Section
CPU Access
UPDI Access
Read
Write
Read
Write
Registers
Yes
Yes
No
No
Flash
Yes
Yes
No
No
EEPROM
Yes
No
No
No
USERROW
Yes
Yes
No
Yes(2)
SIGROW
Yes
No
No
No
Other Fuses
Yes
No
No
No
Note:
1. Read operations marked No in the tables may appear to be successful, but the data is corrupt.
Hence, any attempt of code validation through the UPDI will fail on these memory sections.
2. In Locked mode, the USERROW can be written blindly using the fuse Write command, but the
current USERROW values cannot be read out.
Important: The only way to unlock a device is a CHIPERASE, which will erase all device
memories to factory default so that no application data is retained.
Related Links
6.10.3 Fuse Summary - FUSE
6.10.4.9 LOCKBIT
33. UPDI - Unified Program and Debug Interface
33.3.7 Enabling of KEY Protected Interfaces
6.10
Configuration and User Fuses (FUSE)
Fuses are part of the nonvolatile memory and hold factory calibration data and device configuration. The
fuses are available from device power-up. The fuses can be read by the CPU or the UPDI, but can only
be programmed or cleared by the UPDI. The configuration and calibration values stored in the fuses are
written to their respective target registers at the end of the start-up sequence.
The content of the Signature Row fuses (SIGROW) is pre-programmed and cannot be altered. SIGROW
holds information such as device ID, serial number, and calibration values.
The fuses for peripheral configuration (FUSE) are pre-programmed but can be altered by the user.
Altered values in the configuration fuse will be effective only after a Reset.
Note: When writing the fuses write all reserved bits to ‘1’.
This device provides a User Row fuse area (USERROW) that can hold application data. The USERROW
can be programmed on a locked device by the UPDI. This can be used for final configuration without
having programming or debugging capabilities enabled.
Related Links
6.10.1 SIGROW - Signature Row Summary
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 23
ATtiny1616/3216
Memories
6.10.3 Fuse Summary - FUSE
7.1 Peripheral Module Address Map
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 24
ATtiny1616/3216
Memories
6.10.1
SIGROW - Signature Row Summary
Offset
Name
Bit Pos.
0x00
DEVICEID0
7:0
DEVICEID[7:0]
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
0x0D
...
0x1F
0x20
0x21
0x22
0x23
0x24
0x25
DEVICEID1
DEVICEID2
SERNUM0
SERNUM1
SERNUM2
SERNUM3
SERNUM4
SERNUM5
SERNUM6
SERNUM7
SERNUM8
SERNUM9
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
DEVICEID[7:0]
DEVICEID[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
SERNUM[7:0]
7:0
7:0
7:0
7:0
7:0
7:0
TEMPSENSE[7:0]
TEMPSENSE[7:0]
OSC16ERR3V[7:0]
OSC16ERR5V[7:0]
OSC20ERR3V[7:0]
OSC20ERR5V[7:0]
6.10.2
Reserved
TEMPSENSE0
TEMPSENSE1
OSC16ERR3V
OSC16ERR5V
OSC20ERR3V
OSC20ERR5V
Signature Row Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 25
ATtiny1616/3216
Memories
6.10.2.1 Device ID n
Name:
Offset:
Reset:
Property:
DEVICEIDn
0x00 + n*0x01 [n=0..2]
[Device ID]
-
Each device has a device ID identifying the device and its properties; such as memory sizes, pin count,
and die revision. This can be used to identify a device and hence, the available features by software. The
Device ID consists of three bytes: SIGROW.DEVICEID[2:0].
Bit
7
6
5
4
3
2
1
0
DEVICEID[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – DEVICEID[7:0] Byte n of the Device ID
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 26
ATtiny1616/3216
Memories
6.10.2.2 Serial Number Byte n
Name:
Offset:
Reset:
Property:
SERNUMn
0x03 + n*0x01 [n=0..9]
[device serial number]
-
Each device has an individual serial number, representing a unique ID. This can be used to identify a
specific device in the field. The serial number consists of ten bytes: SIGROW.SERNUM[9:0].
Bit
7
6
5
4
3
2
1
0
Access
R
R
R
R
Reset
x
x
x
R
R
R
R
x
x
x
x
x
SERNUM[7:0]
Bits 7:0 – SERNUM[7:0] Serial Number Byte n
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 27
ATtiny1616/3216
Memories
6.10.2.3 Temperature Sensor Calibration n
Name:
Offset:
Reset:
Property:
TEMPSENSEn
0x20 + n*0x01 [n=0..1]
[Temperature sensor calibration value]
-
These registers contain correction factors for temperature measurements by the ADC.
SIGROW.TEMPSENSE0 is a correction factor for the gain/slope (unsigned), SIGROW.TEMPSENSE1 is
a correction factor for the offset (signed).
Bit
7
6
5
4
3
2
1
0
TEMPSENSE[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – TEMPSENSE[7:0] Temperature Sensor Calibration Byte n
Refer to the ADC chapter for a description on how to use this register.
Related Links
30.3.2.6 Temperature Measurement
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 28
ATtiny1616/3216
Memories
6.10.2.4 OSC16 Error at 3V
Name:
Offset:
Reset:
Property:
Bit
7
OSC16ERR3V
0x22
[Oscillator frequency error value]
-
6
5
4
3
2
1
0
OSC16ERR3V[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – OSC16ERR3V[7:0] OSC16 Error at 3V
These registers contain the signed oscillator frequency error value when running at internal 16 MHz at 3V,
as measured during production.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 29
ATtiny1616/3216
Memories
6.10.2.5 OSC16 Error at 5V
Name:
Offset:
Reset:
Property:
Bit
7
OSC16ERR5V
0x23
[Oscillator frequency error value]
-
6
5
4
3
2
1
0
OSC16ERR5V[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – OSC16ERR5V[7:0] OSC16 Error at 5V
These registers contain the signed oscillator frequency error value when running at internal 16 MHz at 5V,
as measured during production.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 30
ATtiny1616/3216
Memories
6.10.2.6 OSC20 Error at 3V
Name:
Offset:
Reset:
Property:
Bit
7
OSC20ERR3V
0x24
[Oscillator frequency error value]
-
6
5
4
3
2
1
0
OSC20ERR3V[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – OSC20ERR3V[7:0] OSC20 Error at 3V
These registers contain the signed oscillator frequency error value when running at internal 20 MHz at 3V,
as measured during production.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 31
ATtiny1616/3216
Memories
6.10.2.7 OSC20 Error at 5V
Name:
Offset:
Reset:
Property:
Bit
7
OSC20ERR5V
0x25
[Oscillator frequency error value]
-
6
5
4
3
2
1
0
OSC20ERR5V[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – OSC20ERR5V[7:0] OSC20 Error at 5V
These registers contain the signed oscillator frequency error value when running at internal 20 MHz at 5V,
as measured during production.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 32
ATtiny1616/3216
Memories
6.10.3
Fuse Summary - FUSE
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
WDTCFG
BODCFG
OSCCFG
Reserved
TCD0CFG
SYSCFG0
SYSCFG1
APPEND
BOOTEND
Reserved
LOCKBIT
7:0
7:0
7:0
6.10.4
7:0
7:0
7:0
7:0
7:0
WINDOW[3:0]
LVL[2:0]
PERIOD[3:0]
SAMPFREQ
ACTIVE[1:0]
CMPAEN
TOUTDIS
CMPD
CMPC
RSTPINCFG[1:0]
OSCLOCK
CMPDEN
CMPCEN
CRCSRC[1:0]
7:0
CMPBEN
RESERVED
SLEEP[1:0]
FREQSEL[1:0]
CMPB
RESERVED
SUT[2:0]
CMPA
EESAVE
APPEND[7:0]
BOOTEND[7:0]
LOCKBIT[7:0]
Fuse Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 33
ATtiny1616/3216
Memories
6.10.4.1 Watchdog Configuration
Name:
Offset:
Reset:
Property:
Bit
7
WDTCFG
0x00
-
6
5
4
3
2
WINDOW[3:0]
1
0
PERIOD[3:0]
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bits 7:4 – WINDOW[3:0] Watchdog Window Time-out Period
This value is loaded into the WINDOW bit field of the Watchdog Control A register (WDT.CTRLA) during
Reset.
Bits 3:0 – PERIOD[3:0] Watchdog Time-out Period
This value is loaded into the PERIOD bit field of the Watchdog Control A register (WDT.CTRLA) during
Reset.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 34
ATtiny1616/3216
Memories
6.10.4.2 BOD Configuration
Name:
Offset:
Reset:
Property:
BODCFG
0x01
-
The settings of the BOD will be reloaded from this Fuse after a Power-on Reset. For all other Resets, the
BOD configuration remains unchanged.
Bit
7
6
5
Access
R
R
R
R
Reset
0
0
0
0
LVL[2:0]
4
3
2
1
R
R
R
R
0
0
0
0
SAMPFREQ
ACTIVE[1:0]
0
SLEEP[1:0]
Bits 7:5 – LVL[2:0] BOD Level
This value is loaded into the LVL bit field of the BOD Control B register (BOD.CTRLB) during Reset.
Value
Name
Description
0x0
BODLEVEL0
1.8V
0x2
BODLEVEL2
2.6V
0x7
BODLEVEL7
4.2V
Note:
• Values in the description are typical values.
• Refer to the BOD and POR Characteristics in Electrical Characteristics for maximum and minimum
values.
Bit 4 – SAMPFREQ BOD Sample Frequency
This value is loaded into the SAMPFREQ bit of the BOD Control A register (BOD.CTRLA) during Reset.
Value
Description
0x0
Sample frequency is 1 kHz
0x1
Sample frequency is 125 Hz
Bits 3:2 – ACTIVE[1:0] BOD Operation Mode in Active and Idle
This value is loaded into the ACTIVE bit field of the BOD Control A register (BOD.CTRLA) during Reset.
Value
Description
0x0
Disabled
0x1
Enabled
0x2
Sampled
0x3
Enabled with wake-up halted until BOD is ready
Bits 1:0 – SLEEP[1:0] BOD Operation Mode in Sleep
This value is loaded into the SLEEP bit field of the BOD Control A register (BOD.CTRLA) during Reset.
Value
Description
0x0
Disabled
0x1
Enabled
0x2
Sampled
0x3
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 35
ATtiny1616/3216
Memories
6.10.4.3 Oscillator Configuration
Name:
Offset:
Reset:
Property:
Bit
7
OSCCFG
0x02
-
6
5
4
3
2
1
OSCLOCK
0
FREQSEL[1:0]
Access
R
R
R
Reset
0
1
0
Bit 7 – OSCLOCK Oscillator Lock
This fuse bit is loaded to LOCK in CLKCTRL.OSC20MCALIBB during Reset.
Value
Description
0
Calibration registers of the 20 MHz oscillator are accessible
1
Calibration registers of the 20 MHz oscillator are locked
Bits 1:0 – FREQSEL[1:0] Frequency Select
These bits select the operation frequency of the 16/20 MHz internal oscillator (OSC20M) and determine
the respective factory calibration values to be written to CAL20M in CLKCTRL.OSC20MCALIBA and
TEMPCAL20M in CLKCTRL.OSC20MCALIBB.
Value
Description
0x1
Run at 16 MHz with corresponding factory calibration
0x2
Run at 20 MHz with corresponding factory calibration
Other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 36
ATtiny1616/3216
Memories
6.10.4.4 Timer Counter Type D Configuration
Name:
Offset:
Reset:
Property:
TCD0CFG
0x04
-
The bit values of this fuse register are written to the corresponding bits in the TCD.FAULTCTRL register
of TCD0 at start-up.
The CMPEN and CMP settings of the TCD will only be reloaded from the FUSE values after a Power-on
Reset. For all other resets, the corresponding TCD settings of the device will remain unchanged.
Bit
7
6
5
4
3
2
1
0
CMPDEN
CMPCEN
CMPBEN
CMPAEN
CMPD
CMPC
CMPB
CMPA
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bits 4, 5, 6, 7 – CMPEN Compare x Enable
Value
Description
0
Compare x output on Pin is disabled
1
Compare x output on Pin is enabled
Bits 0, 1, 2, 3 – CMP Compare x
This bit selects the default state of Compare x after Reset, or when entering debug if FAULTDET is '1'.
Value
Description
0
Compare x default state is 0
1
Compare x default state is 1
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 37
ATtiny1616/3216
Memories
6.10.4.5 System Configuration 0
Name:
Offset:
Reset:
Property:
Bit
SYSCFG0
0x05
-
7
6
CRCSRC[1:0]
5
4
RESERVED
TOUTDIS
3
2
RSTPINCFG[1:0]
1
0
RESERVED
EESAVE
Access
R
R
R
R
R
R
R
R
Reset
1
1
1
1
0
1
1
0
Bits 7:6 – CRCSRC[1:0] CRC Source
See the CRC description for more information about the functionality.
Value
Name
Description
0x0
FLASH
CRC of full Flash (boot, application code and application data)
0x1
BOOT
CRC of the boot section
0x2
BOOTAPP
CRC of application code and boot sections
0x3
NOCRC
No CRC
Bit 5 – RESERVED
Bit 4 – TOUTDIS Time Out Disable
This bit can disable the blocking of NVM writes after POR.
When the TOUTDIS bit in FUSE.SYSCFG0 is ‘0’ and the RSTPINCFG bit field in FUSE.SYSCFG0 is
configured to GPIO or RESET, there will be a time out period after POR that blocks NVM writes.
The NVM Write Block will last for 768 OSC32K cycles after POR. The EEBUSY and FBUSY bits in the
NVMCTRL.STATUS register must read ‘0’ before the page buffer can be filled or NVM commands can be
issued.
Value
Description
0
NVM Write Block is enabled
1
NVM Write Block is disabled
Note: This fuse is not available for devices with 16 KB flash memory.
Bits 3:2 – RSTPINCFG[1:0] Reset Pin Configuration
These bits select the Reset/UPDI pin configuration.
Value
Description
0x0
GPIO
0x1
UPDI
0x2
RESET
Other
Reserved
Note: When configuring the Reset Pin as GPIO, there is a potential conflict between the GPIO actively
driving the output, and a 12V UPDI enable sequence initiation. To avoid this, the GPIO output driver is
disabled for 768 OSC32K cycles after a System Reset. Enable any interrupts for this pin only after this
period.
Bit 1 – RESERVED
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 38
ATtiny1616/3216
Memories
Bit 0 – EESAVE EEPROM Save during chip erase
Note: If the device is locked, the EEPROM is always erased by a chip erase, regardless of this bit.
Value
0
1
Description
EEPROM erased during chip erase
EEPROM not erased under chip erase
Related Links
27. CRCSCAN - Cyclic Redundancy Check Memory Scan
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 39
ATtiny1616/3216
Memories
6.10.4.6 System Configuration 1
Name:
Offset:
Reset:
Property:
Bit
7
SYSCFG1
0x06
-
6
5
4
3
2
1
0
SUT[2:0]
Access
R
R
R
Reset
1
1
1
Bits 2:0 – SUT[2:0] Start-Up Time Setting
These bits select the start-up time between power-on and code execution.
Value
Description
0x0
0 ms
0x1
1 ms
0x2
2 ms
0x3
4 ms
0x4
8 ms
0x5
16 ms
0x6
32 ms
0x7
64 ms
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 40
ATtiny1616/3216
Memories
6.10.4.7 Application Code End
Name:
Offset:
Reset:
Property:
Bit
7
APPEND
0x07
-
6
5
4
3
2
1
0
APPEND[7:0]
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bits 7:0 – APPEND[7:0] Application Code Section End
These bits set the end of the application code section in blocks of 256 bytes. The end of the application
code section should be set as BOOT size plus application code size. The remaining Flash will be
application data. A value of 0x00 defines the Flash from BOOTEND*256 to end of Flash as application
code. When both FUSE.APPEND and FUSE.BOOTEND are 0x00, the entire Flash is BOOT section.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 41
ATtiny1616/3216
Memories
6.10.4.8 Boot End
Name:
Offset:
Reset:
Property:
Bit
7
BOOTEND
0x08
-
6
5
4
3
2
1
0
BOOTEND[7:0]
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bits 7:0 – BOOTEND[7:0] Boot Section End
These bits set the end of the boot section in blocks of 256 bytes. A value of 0x00 defines the whole Flash
as BOOT section. When both FUSE.APPEND and FUSE.BOOTEND are 0x00, the entire Flash is BOOT
section.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 42
ATtiny1616/3216
Memories
6.10.4.9 Lockbits
Name:
Offset:
Reset:
Property:
Bit
7
LOCKBIT
0x0A
-
6
5
4
3
2
1
0
LOCKBIT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – LOCKBIT[7:0] Lockbits
When the part is locked, UPDI cannot access the system bus, so it cannot read out anything but CSspace.
Value
Description
0xC5
Valid key - the device is open
other
Invalid - the device is locked
Related Links
6.9 Memory Section Access from CPU and UPDI on Locked Device
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 43
ATtiny1616/3216
Peripherals and Architecture
7.
Peripherals and Architecture
7.1
Peripheral Module Address Map
The address map shows the base address for each peripheral. For complete register description and
summary for each peripheral module, refer to the respective module chapters.
Table 7-1. Peripheral Module Address Map
Base Address
Name
Description
0x0000
VPORTA
Virtual Port A
0x0004
VPORTB
Virtual Port B
0x0008
VPORTC
Virtual Port C
0x001C
GPIO
General Purpose I/O registers
0x0030
CPU
CPU
0x0040
RSTCTRL
Reset Controller
0x0050
SLPCTRL
Sleep Controller
0x0060
CLKCTRL
Clock Controller
0x0080
BOD
Brown-Out Detector
0x00A0
VREF
Voltage Reference
0x0100
WDT
Watchdog Timer
0x0110
CPUINT
Interrupt Controller
0x0120
CRCSCAN
Cyclic Redundancy Check Memory Scan
0x0140
RTC
Real-Time Counter
0x0180
EVSYS
Event System
0x01C0
CCL
Configurable Custom Logic
0x0200
PORTMUX
Port Multiplexer
0x0400
PORTA
Port A Configuration
0x0420
PORTB
Port B Configuration
0x0440
PORTC
Port C Configuration
0x0600
ADC0
Analog-to-Digital Converter
0x0640
ADC1
Analog-to-Digital Converter instance 1
0x0680
AC0
Analog Comparator 0
0x0688
AC1
Analog Comparator 1
0x0690
AC2
Analog Comparator 2
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 44
ATtiny1616/3216
Peripherals and Architecture
...........continued
7.2
Base Address
Name
Description
0x06A0
DAC0
Digital-to-Analog Converter 0
0x06A8
DAC1
Digital-to-Analog Converter 1
0x06B0
DAC2
Digital-to-Analog Converter 2
0x0800
USART0
Universal Synchronous Asynchronous Receiver Transmitter
0x0810
TWI0
Two-Wire Interface
0x0820
SPI0
Serial Peripheral Interface
0x0A00
TCA0
Timer/Counter Type A instance 0
0x0A40
TCB0
Timer/Counter Type B instance 0
0x0A50
TCB1
Timer/Counter Type B 1
0x0A80
TCD0
Timer/Counter Type D instance 0
0x0F00
SYSCFG
System Configuration
0x1000
NVMCTRL
Nonvolatile Memory Controller
0x1100
SIGROW
Signature Row
0x1280
FUSES
Device-specific fuses
0x1300
USERROW
User Row
Interrupt Vector Mapping
Each of the interrupt vectors is connected to one peripheral instance, as shown in the table below. A
peripheral can have one or more interrupt sources, see the Interrupt section in the Functional description
of the respective peripheral for more details on the available interrupt sources.
When the interrupt condition occurs, an Interrupt Flag (nameIF) is set in the Interrupt Flags register of the
peripheral (peripheral.INTFLAGS).
An interrupt is enabled or disabled by writing to the corresponding Interrupt Enable bit (nameIE) in the
peripheral's Interrupt Control register (peripheral.INTCTRL).
The naming of the registers may vary slightly in some peripherals.
An interrupt request is generated when the corresponding interrupt is enabled and the interrupt flag is set.
The interrupt request remains active until the interrupt flag is cleared. See the peripheral's INTFLAGS
register for details on how to clear interrupt flags.
Interrupts must be enabled globally for interrupt requests to be generated.
Table 7-2. Interrupt Vector Mapping
Vector Number
Base Address
Peripheral Source
0
0x00
RESET
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 45
ATtiny1616/3216
Peripherals and Architecture
...........continued
Vector Number
Base Address
Peripheral Source
1
0x02
NMI - Non-Maskable Interrupt
from CRC
2
0x04
VLM - Voltage Level Monitor
3
0x06
PORTA - Port A
4
0x08
PORTB - Port B
5
0x0A
PORTC - Port C
6
0x0C
RTC - Real-Time Counter
7
0x0E
PIT - Periodic Interrupt Timer (in
RTC peripheral)
8
0x10
TCA0 - Timer Counter Type A
13
0x1A
TCB0 - Timer Counter Type B
14
0x1C
TCB1 - Timer Counter Type B
15
0x1E
TCD0 - Timer Counter Type D
17
0x22
AC0 – Analog Comparator
18
0x24
AC1 – Analog Comparator
19
0x26
AC2 – Analog Comparator
20
0x28
ADC0 – Analog-to-Digital
Converter/PTC
22
0x2C
ADC1 – Analog-to-Digital
Converter
24
0x30
TWI0 - Two-Wire Interface/I2C
26
0x34
SPI0 - Serial Peripheral Interface
27
0x36
USART0 - Universal
Asynchronous ReceiverTransmitter
30
0x3C
NVM - Nonvolatile Memory
Related Links
9. NVMCTRL - Nonvolatile Memory Controller
16. PORT - I/O Pin Configuration
23. RTC - Real-Time Counter
25. SPI - Serial Peripheral Interface
24. USART - Universal Synchronous and Asynchronous Receiver and Transmitter
26. TWI - Two-Wire Interface
27. CRCSCAN - Cyclic Redundancy Check Memory Scan
20. TCA - 16-bit Timer/Counter Type A
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 46
ATtiny1616/3216
Peripherals and Architecture
21.
22.
29.
30.
7.3
TCB - 16-bit Timer/Counter Type B
TCD - 12-Bit Timer/Counter Type D
AC - Analog Comparator
ADC - Analog-to-Digital Converter
System Configuration (SYSCFG)
The system configuration contains the revision ID of the part. The revision ID is readable from the CPU,
making it useful for implementing application changes between part revisions.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 47
ATtiny1616/3216
Peripherals and Architecture
7.3.1
Register Summary - SYSCFG
Offset
Name
Bit Pos.
0x01
REVID
7:0
7.3.2
REVID[7:0]
Register Description - SYSCFG
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 48
ATtiny1616/3216
Peripherals and Architecture
7.3.2.1
Device Revision ID Register
Name:
Offset:
Reset:
Property:
REVID
0x01
[revision ID]
-
This register is read-only and displays the device revision ID.
Bit
7
6
5
4
Access
R
R
R
R
3
2
1
0
R
R
R
R
REVID[7:0]
Reset
Bits 7:0 – REVID[7:0] Revision ID
These bits contain the device revision. 0x00 = A, 0x01 = B, and so on.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 49
ATtiny1616/3216
AVR CPU
8.
AVR CPU
8.1
Features
• 8-Bit, High-Performance AVR RISC CPU:
– 135 instructions
– Hardware multiplier
• 32 8-Bit Registers Directly Connected to the Arithmetic Logic Unit (ALU)
• Stack in RAM
• Stack Pointer Accessible in I/O Memory Space
• Direct Addressing of up to 64 KB of Unified Memory:
– Entire Flash accessible with all LD/ST instructions
• True 16/24-Bit Access to 16/24-Bit I/O Registers
• Efficient Support for 8-, 16-, and 32-Bit Arithmetic
• Configuration Change Protection for System Critical Features
8.2
Overview
All AVR devices use the 8-bit AVR CPU. The CPU is able to access memories, perform calculations,
control peripherals, and execute instructions in the program memory. Interrupt handling is described in a
separate section.
Related Links
6. Memories
9. NVMCTRL - Nonvolatile Memory Controller
13. CPUINT - CPU Interrupt Controller
8.3
Architecture
In order to maximize performance and parallelism, the AVR CPU uses a Harvard architecture with
separate buses for program and data. Instructions in the program memory are executed with single-level
pipelining. While one instruction is being executed, the next instruction is prefetched from the program
memory. This enables instructions to be executed on every clock cycle.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 50
ATtiny1616/3216
AVR CPU
Figure 8-1. AVR CPU Architecture
Register file
R31 (ZH)
R29 (YH)
R27 (XH)
R25
R23
R21
R19
R17
R15
R13
R11
R9
R7
R5
R3
R1
R30 (ZL)
R28 (YL)
R26 (XL)
R24
R22
R20
R18
R16
R14
R12
R10
R8
R6
R4
R2
R0
Program
Counter
Flash Program
Memory
Instruction
Register
Instruction
Decode
Data Memory
Stack
Pointer
STATUS
Register
ALU
The Arithmetic Logic Unit (ALU) supports arithmetic and logic operations between registers or between a
constant and a register. Also, single-register operations can be executed in the ALU. After an arithmetic
operation, the STATUS register is updated to reflect information about the result of the operation.
The ALU is directly connected to the fast-access register file. The 32 8-bit general purpose working
registers all have single clock cycle access time allowing single-cycle arithmetic logic unit operation
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 51
ATtiny1616/3216
AVR CPU
between registers or between a register and an immediate. Six of the 32 registers can be used as three
16-bit Address Pointers for program and data space addressing, enabling efficient address calculations.
The program memory bus is connected to Flash, and the first program memory Flash address is 0x0000.
The data memory space is divided into I/O registers, SRAM, EEPROM, and Flash.
All I/O Status and Control registers reside in the lowest 4 KB addresses of the data memory. This is
referred to as the I/O memory space. The lowest 64 addresses are accessed directly with single-cycle
IN/OUT instructions, or as the data space locations from 0x00 to 0x3F. These addresses can be accessed
using load (LD/LDS/LDD) and store (ST/STS/STD) instructions. The lowest 32 addresses can even be
accessed with single-cycle SBI/CBI instructions and SBIS/SBIC instructions. The rest is the extended
I/O memory space, ranging from 0x0040 to 0x0FFF. The I/O registers here must be accessed as data
space locations using load and store instructions.
Data addresses 0x1000 to 0x1800 are reserved for memory mapping of fuses, the NVM controller and
EEPROM. The addresses from 0x1800 to 0x7FFF are reserved for other memories, such as SRAM.
The Flash is mapped in the data space from and above. The Flash can be accessed with all load and
store instructions by using addresses above . The LPM instruction accesses the Flash similar to the code
space, where the Flash starts at address 0x0000.
For a summary of all AVR instructions, refer to the Instruction Set Summary section. For details of all AVR
instructions, refer to http://www.microchip.com/design-centers/8-bit.
Related Links
9. NVMCTRL - Nonvolatile Memory Controller
6. Memories
34. Instruction Set Summary
8.4
Arithmetic Logic Unit (ALU)
The Arithmetic Logic Unit (ALU) supports arithmetic and logic operations between registers, or between a
constant and a register. Also, single-register operations can be executed.
The ALU operates in direct connection with all 32 general purpose registers. Arithmetic operations
between general purpose registers or between a register and an immediate are executed in a single clock
cycle, and the result is stored in the register file. After an arithmetic or logic operation, the Status register
(CPU.SREG) is updated to reflect information about the result of the operation.
ALU operations are divided into three main categories – arithmetic, logical, and bit functions. Both 8- and
16-bit arithmetic are supported, and the instruction set allows for efficient implementation of 32-bit
arithmetic. The hardware multiplier supports signed and unsigned multiplication and fractional format.
8.4.1
Hardware Multiplier
The multiplier is capable of multiplying two 8-bit numbers into a 16-bit result. The hardware multiplier
supports different variations of signed and unsigned integer and fractional numbers:
•
•
•
•
Multiplication of signed/unsigned integers
Multiplication of signed/unsigned fractional numbers
Multiplication of a signed integer with an unsigned integer
Multiplication of a signed fractional number with an unsigned one
A multiplication takes two CPU clock cycles.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 52
ATtiny1616/3216
AVR CPU
8.5
Functional Description
8.5.1
Program Flow
After Reset, the CPU will execute instructions from the lowest address in the Flash program memory,
0x0000. The Program Counter (PC) addresses the next instruction to be fetched.
Program flow is supported by conditional and unconditional JUMP and CALL instructions, capable of
addressing the whole address space directly. Most AVR instructions use a 16-bit word format, and a
limited number use a 32-bit format.
During interrupts and subroutine calls, the return address PC is stored on the stack as a word pointer.
The stack is allocated in the general data SRAM, and consequently, the stack size is only limited by the
total SRAM size and the usage of the SRAM. After Reset, the Stack Pointer (SP) points to the highest
address in the internal SRAM. The SP is read/write accessible in the I/O memory space, enabling easy
implementation of multiple stacks or stack areas. The data SRAM can easily be accessed through the
five different addressing modes supported by the AVR CPU.
8.5.2
Instruction Execution Timing
The AVR CPU is clocked by the CPU clock: CLK_CPU. No internal clock division is applied. The figure
below shows the parallel instruction fetches and instruction executions enabled by the Harvard
architecture and the fast-access register file concept. This is the basic pipelining concept enabling up to 1
MIPS/MHz performance with high efficiency.
Figure 8-2. The Parallel Instruction Fetches and Instruction Executions
T1
T2
T3
T4
clkCPU
1st Instruction Fetch
1st Instruction Execute
2nd Instruction Fetch
2nd Instruction Execute
3rd Instruction Fetch
3rd Instruction Execute
4th Instruction Fetch
The following figure shows the internal timing concept for the register file. In a single clock cycle, an ALU
operation using two register operands is executed and the result is stored in the destination register.
Figure 8-3. Single Cycle ALU Operation
T1
T2
T3
T4
clkCPU
Total Execution Time
Register Operands Fetch
ALU Operation Execute
Result Write Back
8.5.3
Status Register
The Status register (CPU.SREG) contains information about the result of the most recently executed
arithmetic or logic instruction. This information can be used for altering program flow in order to perform
conditional operations.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 53
ATtiny1616/3216
AVR CPU
CPU.SREG is updated after all ALU operations, as specified in the Instruction Set Summary. This will in
many cases remove the need for using the dedicated compare instructions, resulting in faster and more
compact code. CPU.SREG is not automatically stored/restored when entering/returning from an Interrupt
Service Routine. Maintaining the Status register between context switches must, therefore, be handled by
user-defined software. CPU.SREG is accessible in the I/O memory space.
Related Links
34. Instruction Set Summary
8.5.4
Stack and Stack Pointer
The stack is used for storing return addresses after interrupts and subroutine calls. Also, it can be used
for storing temporary data. The Stack Pointer (SP) always points to the top of the stack. The SP is
defined by the Stack Pointer bits in the Stack Pointer register (CPU.SP). The CPU.SP is implemented as
two 8-bit registers that are accessible in the I/O memory space.
Data is pushed and popped from the stack using the PUSH and POP instructions. The stack grows from
higher to lower memory locations. This implies that pushing data onto the stack decreases the SP, and
popping data off the stack increases the SP. The Stack Pointer is automatically set to the highest address
of the internal SRAM after Reset. If the stack is changed, it must be set to point above address 0x2000,
and it must be defined before any subroutine calls are executed and before interrupts are enabled.
During interrupts or subroutine calls the return address is automatically pushed on the stack as a word
pointer and the SP is decremented by '2'. The return address consists of two bytes and the Least
Significant Byte is pushed on the stack first (at the higher address). As an example, a byte pointer return
address of 0x0006 is saved on the stack as 0x0003 (shifted one bit to the right), pointing to the fourth 16bit instruction word in the program memory. The return address is popped off the stack with RETI (when
returning from interrupts) and RET (when returning from subroutine calls) and the SP is incremented by
two.
The SP is decremented by '1' when data is pushed on the stack with the PUSH instruction, and
incremented by '1' when data is popped off the stack using the POP instruction.
To prevent corruption when updating the Stack Pointer from software, a write to SPL will automatically
disable interrupts for up to four instructions or until the next I/O memory write.
8.5.5
Register File
The register file consists of 32 8-bit general purpose working registers with single clock cycle access time.
The register file supports the following input/output schemes:
•
•
•
•
One 8-bit output operand and one 8-bit result input
Two 8-bit output operands and one 8-bit result input
Two 8-bit output operands and one 16-bit result input
One 16-bit output operand and one 16-bit result input
Six of the 32 registers can be used as three 16-bit Address Register Pointers for data space addressing,
enabling efficient address calculations.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 54
ATtiny1616/3216
AVR CPU
Figure 8-4. AVR CPU General Purpose Working Registers
R0
R1
R2
Addr.
0x00
0x01
0x02
R13
R14
R15
R16
R17
0x0D
0x0E
0x0F
0x10
0x11
R26
R27
R28
R29
R30
R31
0x1A
0x1B
0x1C
0x1D
0x1E
0x1F
0
7
...
...
X-register Low Byte
X-register High Byte
Y-register Low Byte
Y-register High Byte
Z-register Low Byte
Z-register High Byte
The register file is located in a separate address space and is, therefore, not accessible through
instructions operation on data memory.
8.5.5.1
The X-, Y-, and Z-Registers
Registers R26...R31 have added functions besides their general purpose usage.
These registers can form 16-bit Address Pointers for addressing data memory. These three address
registers are called the X-register, Y-register, and Z-register. Load and store instructions can use all X-,
Y-, and Z-registers, while the LPM instructions can only use the Z-register. Indirect calls and jumps
(ICALL and IJMP ) also use the Z-register.
Refer to the instruction set or Instruction Set Summary for more information about how the X-, Y-, and Zregisters are used.
Figure 8-5. The X-, Y-, and Z-Registers
Bit (individually)
7
X-register
15
Bit (individually)
7
Y-register
Bit (individually)
R29
7
8
7
0
7
8
7
7
R31
0
7
0
0
R28
0
YL
ZH
15
R26
XL
YH
15
Z-register
Bit (Z-register)
0
XH
Bit (X-register)
Bit (Y-register)
R27
0
R30
0
ZL
8
7
0
The lowest register address holds the Least Significant Byte (LSB), and the highest register address
holds the Most Significant Byte (MSB). In the different addressing modes, these address registers
function as fixed displacement, automatic increment, and automatic decrement.
Related Links
34. Instruction Set Summary
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 55
ATtiny1616/3216
AVR CPU
8.5.6
Accessing 16-Bit Registers
The AVR data bus has a width of 8 bits, and so accessing 16-bit registers requires atomic operations.
These registers must be byte accessed using two read or write operations. 16-bit registers are connected
to the 8-bit bus and a temporary register using a 16-bit bus.
For a write operation, the low byte of the 16-bit register must be written before the high byte. The low byte
is then written into the temporary register. When the high byte of the 16-bit register is written, the
temporary register is copied into the low byte of the 16-bit register in the same clock cycle.
For a read operation, the low byte of the 16-bit register must be read before the high byte. When the low
byte register is read by the CPU, the high byte of the 16-bit register is copied into the temporary register
in the same clock cycle as the low byte is read. When the high byte is read, it is then read from the
temporary register.
This ensures that the low and high bytes of 16-bit registers are always accessed simultaneously when
reading or writing the register.
Interrupts can corrupt the timed sequence if an interrupt is triggered and accesses the same 16-bit
register during an atomic 16-bit read/write operation. To prevent this, interrupts can be disabled when
writing or reading 16-bit registers.
The temporary registers can be read and written directly from user software.
8.5.6.1
Accessing 24-Bit Registers
For 24-bit registers, the read and write access is done in the same way as described for 16-bit registers,
except there are two temporary registers for 24-bit registers. The Least Significant Byte must be written
first when doing a write, and read first when doing a read.
8.5.7
Configuration Change Protection (CCP)
System critical I/O register settings are protected from accidental modification. Flash self-programming
(via store to NVM controller) is protected from accidental execution. This is handled globally by the
Configuration Change Protection (CCP) register.
Changes to the protected I/O registers or bits, or execution of protected instructions, are only possible
after the CPU writes a signature to the CCP register. The different signatures are listed in the description
of the CCP register (CPU.CCP).
There are two modes of operation: one for protected I/O registers, and one for the protected selfprogramming.
Related Links
8.7.1 CCP
8.5.7.1
Sequence for Write Operation to Configuration Change Protected I/O Registers
In order to write to registers protected by CCP, these steps are required:
1.
2.
The software writes the signature that enables change of protected I/O registers to the CCP bit field
in the CPU.CCP register.
Within four instructions, the software must write the appropriate data to the protected register.
Most protected registers also contain a write enable/change enable/lock bit. This bit must be written
to '1' in the same operation as the data are written.
The protected change is immediately disabled if the CPU performs write operations to the I/O
register or data memory, if load or store accesses to Flash, NVMCTRL, EEPROM are conducted,
or if the SLEEP instruction is executed.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 56
ATtiny1616/3216
AVR CPU
8.5.7.2
Sequence for Execution of Self-Programming
In order to execute self-programming (the execution of writes to the NVM controller's command register),
the following steps are required:
1.
2.
The software temporarily enables self-programming by writing the SPM signature to the CCP
register (CPU.CCP).
Within four instructions, the software must execute the appropriate instruction. The protected
change is immediately disabled if the CPU performs accesses to the Flash, NVMCTRL, or
EEPROM, or if the SLEEP instruction is executed.
Once the correct signature is written by the CPU, interrupts will be ignored for the duration of the
configuration change enable period. Any interrupt request (including non-maskable interrupts) during the
CCP period will set the corresponding interrupt flag as normal, and the request is kept pending. After the
CCP period is completed, any pending interrupts are executed according to their level and priority.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 57
ATtiny1616/3216
AVR CPU
8.6
Register Summary - CPU
Offset
Name
Bit Pos.
0x04
0x05
...
0x0C
CCP
7:0
CCP[7:0]
7:0
15:8
7:0
SP[7:0]
SP[15:8]
Reserved
0x0D
SP
0x0F
SREG
8.7
I
T
H
S
V
N
Z
C
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 58
ATtiny1616/3216
AVR CPU
8.7.1
Configuration Change Protection
Name:
Offset:
Reset:
Property:
Bit
CCP
0x04
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
CCP[7:0]
Access
Reset
Bits 7:0 – CCP[7:0] Configuration Change Protection
Writing the correct signature to this bit field allows changing protected I/O registers or executing protected
instructions within the next four CPU instructions executed.
All interrupts are ignored during these cycles. After these cycles, interrupts will automatically be handled
again by the CPU, and any pending interrupts will be executed according to their level and priority.
When the protected I/O register signature is written, CCP[0] will read as '1' as long as the CCP feature is
enabled.
When the protected self-programming signature is written, CCP[1] will read as '1' as long as the CCP
feature is enabled.
CCP[7:2] will always read as zero.
Value
Name
Description
0x9D
SPM
Allow Self-Programming
0xD8
IOREG
Un-protect protected I/O registers
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 59
ATtiny1616/3216
AVR CPU
8.7.2
Stack Pointer
Name:
Offset:
Reset:
Property:
SP
0x0D
Top of stack
-
The CPU.SP holds the Stack Pointer (SP) that points to the top of the stack. After Reset, the Stack
Pointer points to the highest internal SRAM address.
Only the number of bits required to address the available data memory including external memory (up to
64 KB) is implemented for each device. Unused bits will always read as zero.
The CPU.SPL and CPU.SPH register pair represents the 16-bit value, CPU.SP. The low byte [7:0] (suffix
L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01.
To prevent corruption when updating the SP from software, a write to CPU.SPL will automatically disable
interrupts for the next four instructions or until the next I/O memory write.
Bit
15
14
13
12
11
10
9
8
R/W
R/W
R/W
R/W
3
2
1
0
R/W
R/W
R/W
R/W
SP[15:8]
Access
R/W
R/W
R/W
R/W
7
6
5
4
Reset
Bit
SP[7:0]
Access
R/W
R/W
R/W
R/W
Reset
Bits 15:8 – SP[15:8] Stack Pointer High Byte
These bits hold the MSB of the 16-bit register.
Bits 7:0 – SP[7:0] Stack Pointer Low Byte
These bits hold the LSB of the 16-bit register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 60
ATtiny1616/3216
AVR CPU
8.7.3
Status Register
Name:
Offset:
Reset:
Property:
SREG
0x0F
0x00
-
The Status register contains information about the result of the most recently executed arithmetic or logic
instruction. For details about the bits in this register and how they are affected by the different
instructions, see the Instruction Set Summary.
Bit
Access
Reset
7
6
5
4
3
2
1
0
I
T
H
S
V
N
Z
C
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bit 7 – I Global Interrupt Enable
Writing a '1' to this bit enables interrupts on the device.
Writing a '0' to this bit disables interrupts on the device, independent of the individual interrupt enable
settings of the peripherals.
This bit is not cleared by hardware after an interrupt has occurred.
This bit can be set and cleared by software with the SEI and CLI instructions.
Changing the I flag through the I/O register results in a one-cycle Wait state on the access.
Bit 6 – T Bit Copy Storage
The bit copy instructions bit load (BLD) and bit store (BST) use the T bit as source or destination for the
operated bit.
A bit from a register in the register file can be copied into this bit by the BST instruction, and this bit can
be copied into a bit in a register in the register file by the BLD instruction.
Bit 5 – H Half Carry Flag
This bit indicates a half carry in some arithmetic operations. Half carry is useful in BCD arithmetic.
Bit 4 – S Sign Bit, S = N ⊕ V
The sign bit (S) is always an exclusive or (xor) between the negative flag (N) and the two’s complement
overflow flag (V).
Bit 3 – V Two’s Complement Overflow Flag
The two’s complement overflow flag (V) supports two’s complement arithmetic.
Bit 2 – N Negative Flag
The negative flag (N) indicates a negative result in an arithmetic or logic operation.
Bit 1 – Z Zero Flag
The zero flag (Z) indicates a zero result in an arithmetic or logic operation.
Bit 0 – C Carry Flag
The carry flag (C) indicates a carry in an arithmetic or logic operation.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 61
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.
NVMCTRL - Nonvolatile Memory Controller
9.1
Features
•
•
•
•
Unified Memory
In-System Programmable
Self-Programming and Boot Loader Support
Configurable Sections for Write Protection:
– Boot section for boot loader code or application code
– Application code section for application code
– Application data section for application code or data storage
• Signature Row for Factory-Programmed Data:
– ID for each device type
– Serial number for each device
– Calibration bytes for factory calibrated peripherals
• User Row for Application Data:
– 64/32 bytes in size
– Can be read and written from software
– Can be written from UPDI on locked device
– Content is kept after chip erase
9.2
Overview
The NVM Controller (NVMCTRL) is the interface between the device, the Flash, and the EEPROM. The
Flash and EEPROM are reprogrammable memory blocks that retain their values even when not powered.
The Flash is mainly used for program storage and can be used for data storage. The EEPROM is used
for data storage and can be programmed while the CPU is running the program from the Flash.
9.2.1
Block Diagram
Figure 9-1. NVMCTRL Block Diagram
NVM Block
Program Memory Bus
Flash
NVMCTRL
Data Memory Bus
EEPROM
Signature Row
User Row
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 62
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.2.2
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 9-1. NVMCTRL System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
No
-
Interrupts
Yes
CPUINT
Events
No
-
Debug
Yes
UPDI
Related Links
9.2.2.1 Clocks
9.2.2.5 Debug Operation
9.2.2.3 Interrupts
9.2.2.1
Clocks
This peripheral always runs on the CPU clock (CLK_CPU). It will request this clock also in sleep modes if
a write/erase is ongoing.
Related Links
10. CLKCTRL - Clock Controller
9.2.2.2
I/O Lines and Connections
Not applicable.
9.2.2.3
Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
9.2.2.4
Events
Not applicable.
9.2.2.5
Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
Related Links
33. UPDI - Unified Program and Debug Interface
9.3
Functional Description
9.3.1
Memory Organization
9.3.1.1
Flash
The Flash is divided into a set of pages. A page is the basic unit addressed when programming the Flash.
It is only possible to write or erase a whole page at a time. One page consists of several words.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 63
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
The Flash can be divided into three sections in blocks of 256 bytes for different security. The three
different sections are BOOT, Application Code (APPCODE), and Application Data (APPDATA).
Figure 9-2. Flash Sections
Section Sizes
The sizes of these sections are set by the Boot Section End fuse (FUSE.BOOTEND) and Application
Code Section End fuse (FUSE.APPEND).
The fuses select the section sizes in blocks of 256 bytes. The BOOT section stretches from the start of
the Flash until BOOTEND. The APPCODE section runs from BOOTEND until APPEND. The remaining
area is the APPDATA section. If APPEND is written to 0, the APPCODE section runs from BOOTEND to
the end of Flash (removing the APPDATA section). If BOOTEND and APPEND are written to 0, the entire
Flash is regarded as BOOT section. APPEND should either be set to 0 or a value greater or equal than
BOOTEND.
Table 9-2. Setting Up Flash Sections
BOOTEND APPEND
BOOT Section
APPCODE Section
APPDATA Section
0
0
0 to FLASHEND
-
-
>0
0
0 to 256*BOOTEND
256*BOOTEND to
FLASHEND
-
>0
==
BOOTEND
0 to 256*BOOTEND
-
256*BOOTEND to
FLASHEND
>0
>
BOOTEND
0 to 256*BOOTEND
256*BOOTEND to
256*APPEND
256*APPEND to
FLASHEND
Note:
• See also the BOOTEND and APPEND descriptions.
• Interrupt vectors are by default located after the BOOT section. This can be changed in the interrupt
controller.
If FUSE.BOOTEND is written to 0x04 and FUSE.APPEND is written to 0x08, the first
4*256 bytes will be BOOT, the next 4*256 bytes will be APPCODE, and the remaining
Flash will be APPDATA.
Inter-Section Write Protection
Between the three Flash sections, a directional write protection is implemented:
• The code in the BOOT section can write to APPCODE and APPDATA
• The code in APPCODE can write to APPDATA
• The code in APPDATA cannot write to Flash or EEPROM
Boot Section Lock and Application Code Section Write Protection
The two lockbits (APCWP and BOOTLOCK in NVMCTRL.CTRLB) can be set to lock further updates of
the respective APPCODE or BOOT section until the next Reset.
The CPU can never write to the BOOT section. NVMCTRL_CTRLB.BOOTLOCK prevents reads and
execution of code from the BOOT section.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 64
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.3.1.2
EEPROM
The EEPROM is divided into a set of pages where one page consists of multiple bytes. The EEPROM
has byte granularity on erase/write. Within one page only the bytes marked to be updated will be erased/
written. The byte is marked by writing a new value to the page buffer for that address location.
9.3.1.3
User Row
The User Row is one extra page of EEPROM. This page can be used to store various data, such as
calibration/configuration data and serial numbers. This page is not erased by a chip erase. The User Row
is written as normal EEPROM, but in addition, it can be written through UPDI on a locked device.
9.3.2
9.3.2.1
Memory Access
Read
Reading of the Flash and EEPROM is done by using load instructions with an address according to the
memory map. Reading any of the arrays while a write or erase is in progress will result in a bus wait, and
the instruction will be suspended until the ongoing operation is complete.
9.3.2.2
Page Buffer Load
The page buffer is loaded by writing directly to the memories as defined in the memory map. Flash,
EEPROM, and User Row share the same page buffer so only one section can be programmed at a time.
The Least Significant bits (LSb) of the address are used to select where in the page buffer the data is
written. The resulting data will be a binary and operation between the new and the previous content of the
page buffer. The page buffer will automatically be erased (all bits set) after:
• A device Reset
• Any page write or erase operation
• A Clear Page Buffer command
• The device wakes up from any sleep mode
9.3.2.3
Programming
For page programming, filling the page buffer and writing the page buffer into Flash, User Row, and
EEPROM are two separate operations.
Before programming a Flash page with the data in the page buffer, the Flash page must be erased. The
page buffer is also erased when the device enters a sleep mode. Programming an unerased Flash page
will corrupt its content.
The Flash can either be written with the erase and write separately, or one command handling both:
Alternative 1:
• Fill the page buffer
• Write the page buffer to Flash with the Erase/Write Page command
Alternative 2:
•
•
•
•
Write to a location on the page to set up the address
Perform an Erase Page command
Fill the page buffer
Perform a Write Page command
The NVM command set supports both a single erase and write operation, and split Page Erase and Page
Write commands. This split commands enable shorter programming time for each command, and the
erase operations can be done during non-time-critical programming execution.
The EEPROM programming is similar, but only the bytes updated in the page buffer will be written or
erased in the EEPROM.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 65
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.3.2.4
Commands
Reading of the Flash/EEPROM and writing of the page buffer is handled with normal load/store
instructions. Other operations, such as writing and erasing the memory arrays, are handled by commands
in the NVM.
To execute a command in the NVM:
1. Confirm that any previous operation is completed by reading the Busy Flags (EEBUSY and
FBUSY) in the NVMCTRL.STATUS register.
2. Write the NVM command unlock to the Configuration Change Protection register in the CPU
(CPU.CCP).
3. Write the desired command value to the CMD bits in the Control A register (NVMCTRL.CTRLA)
within the next four instructions.
9.3.2.4.1 Write Command
The Write command of the Flash controller writes the content of the page buffer to the Flash or EEPROM.
If the write is to the Flash, the CPU will stop executing code as long as the Flash is busy with the write
operation. If the write is to the EEPROM, the CPU can continue executing code while the operation is
ongoing.
The page buffer will be automatically cleared after the operation is finished.
9.3.2.4.2 Erase Command
The Erase command erases the current page. There must be one byte written in the page buffer for the
Erase command to take effect.
For erasing the Flash, first, write to one address in the desired page, then execute the command. The
whole page in the Flash will then be erased. The CPU will be halted while the erase is ongoing.
For the EEPROM, only the bytes written in the page buffer will be erased when the command is
executed. To erase a specific byte, write to its corresponding address before executing the command. To
erase a whole page all the bytes in the page buffer have to be updated before executing the command.
The CPU can continue running code while the operation is ongoing.
The page buffer will automatically be cleared after the operation is finished.
9.3.2.4.3 Erase-Write Operation
The Erase/Write command is a combination of the Erase and Write command, but without clearing the
page buffer after the Erase command: The erase/write operation first erases the selected page, then it
writes the content of the page buffer to the same page.
When executed on the Flash, the CPU will be halted when the operations are ongoing. When executed
on EEPROM, the CPU can continue executing code.
The page buffer will automatically be cleared after the operation is finished.
9.3.2.4.4 Page Buffer Clear Command
The Page Buffer Clear command clears the page buffer. The contents of the page buffer will be all 1’s
after the operation. The CPU will be halted when the operation executes (seven CPU cycles).
9.3.2.4.5 Chip Erase Command
The Chip Erase command erases the Flash and the EEPROM. The EEPROM is unaltered if the
EEPROM Save During Chip Erase (EESAVE) fuse in FUSE.SYSCFG0 is set. The Flash will not be
protected by Boot Section Lock (BOOTLOCK) or Application Code Section Write Protection (APCWP) in
NVMCTRL.CTRLB. The memory will be all 1’s after the operation.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 66
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.3.2.4.6 EEPROM Erase Command
The EEPROM Erase command erases the EEPROM. The EEPROM will be all 1’s after the operation.
The CPU will be halted while the EEPROM is being erased.
9.3.2.4.7 Fuse Write Command
The Fuse Write command writes the fuses. It can only be used by the UPDI, the CPU cannot start this
command.
Follow this procedure to use this command:
• Write the address of the fuse to the Address register (NVMCTRL.ADDR)
• Write the data to be written to the fuse to the Data register (NVMCTRL.DATA)
• Execute the Fuse Write command.
• After the fuse is written, a Reset is required for the updated value to take effect.
For reading fuses, use a regular read on the memory location.
9.3.3
Preventing Flash/EEPROM Corruption
During periods of low VDD, the Flash program or EEPROM data can be corrupted if the supply voltage is
too low for the CPU and the Flash/EEPROM to operate properly. These issues are the same as for board
level systems using Flash/EEPROM, and the same design solutions should be applied.
A Flash/EEPROM corruption can be caused by two situations when the voltage is too low:
1. A regular write sequence to the Flash, which requires a minimum voltage to operate correctly.
2. The CPU itself can execute instructions incorrectly when the supply voltage is too low.
See the Electrical Characteristics chapter for Maximum Frequency vs. VDD.
Flash/EEPROM corruption can be avoided by these measures:
• Keep the device in Reset during periods of insufficient power supply voltage. This can be done by
enabling the internal Brown-Out Detector (BOD).
• The voltage level monitor in the BOD can be used to prevent starting a write to the EEPROM close to
the BOD level.
• If the detection levels of the internal BOD don’t match the required detection level, an external low
VDD Reset protection circuit can be used. If a Reset occurs while a write operation is ongoing, the
write operation will be aborted.
Related Links
37.3 General Operating Ratings
17. BOD - Brown-out Detector
9.3.4
Interrupts
Table 9-3. Available Interrupt Vectors and Sources
Offset Name
Vector Description
Conditions
0x00
NVM
The EEPROM is ready for new write/erase operations.
EEREADY
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (NVMCTRL.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding bit in the peripheral's Interrupt
Enable register (NVMCTRL.INTEN).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 67
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
9.3.5
Sleep Mode Operation
If there is no ongoing write operation, the NVMCTRL will enter sleep mode when the system enters sleep
mode.
If a write operation is ongoing when the system enters a sleep mode, the NVM block, the NVM Controller,
and the system clock will remain ON until the write is finished. This is valid for all sleep modes, including
Power-Down Sleep mode.
The EEPROM Ready interrupt will wake up the device only from Idle Sleep mode.
The page buffer is cleared when waking up from Sleep.
9.3.6
Configuration Change Protection
This peripheral has registers that are under Configuration Change Protection (CCP). In order to write to
these, a certain key must be written to the CPU.CCP register first, followed by a write access to the
protected bits within four CPU instructions.
Attempting to write to a protected register without following the appropriate CCP unlock sequence leaves
the protected register unchanged.
The following registers are under CCP:
Table 9-4. NVMCTRL - Registers under Configuration Change Protection
Register
Key
NVMCTRL.CTRLA
SPM
Related Links
8.5.7.2 Sequence for Execution of Self-Programming
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 68
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.4
Register Summary - NVMCTRL
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
CTRLA
CTRLB
STATUS
INTCTRL
INTFLAGS
Reserved
7:0
7:0
7:0
7:0
7:0
0x06
DATA
0x08
ADDR
9.5
7:0
15:8
7:0
15:8
WRERROR
CMD[2:0]
BOOTLOCK
EEBUSY
APCWP
FBUSY
EEREADY
EEREADY
DATA[7:0]
DATA[15:8]
ADDR[7:0]
ADDR[15:8]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 69
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
Configuration Change Protection
6
5
4
3
2
1
0
CMD[2:0]
Access
Reset
R/W
R/W
R/W
0
0
0
Bits 2:0 – CMD[2:0] Command
Write this bit field to issue a command. The Configuration Change Protection key for self-programming
(SPM) has to be written within four instructions before this write.
Value
Name Description
0x0
No command
0x1
WP
Write page buffer to memory (NVMCTRL.ADDR selects which memory)
0x2
ER
Erase page (NVMCTRL.ADDR selects which memory)
0x3
ERWP Erase and write page (NVMCTRL.ADDR selects which memory)
0x4
PBC
Page buffer clear
0x5
CHER Chip erase: erase Flash and EEPROM (unless EESAVE in FUSE.SYSCFG is '1')
0x6
EEER EEPROM Erase
0x7
WFU
Write fuse (only accessible through UPDI)
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 70
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.5.2
Control B
Name:
Offset:
Reset:
Property:
Bit
7
CTRLB
0x01
0x00
-
6
5
4
3
2
Access
Reset
1
0
BOOTLOCK
APCWP
R/W
R/W
0
0
Bit 1 – BOOTLOCK Boot Section Lock
Writing a ’1’ to this bit locks the boot section from read and instruction fetch.
If this bit is ’1’, a read from the boot section will return ’0’. A fetch from the boot section will also return ‘0’
as instruction.
This bit can be written from the boot section only. It can only be cleared to ’0’ by a Reset.
This bit will take effect only when the boot section is left the first time after the bit is written.
Bit 0 – APCWP Application Code Section Write Protection
Writing a ’1’ to this bit protects the application code section from further writes.
This bit can only be written to ’1’. It is cleared to ’0’ only by Reset.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 71
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.5.3
Status
Name:
Offset:
Reset:
Property:
Bit
7
STATUS
0x02
0x00
-
6
5
4
3
2
1
0
WRERROR
EEBUSY
FBUSY
Access
R
R
R
Reset
0
0
0
Bit 2 – WRERROR Write Error
This bit will read '1' when a write error has happened. A write error could be writing to different sections
before doing a page write or writing to a protected area. This bit is valid for the last operation.
Bit 1 – EEBUSY EEPROM Busy
This bit will read '1' when the EEPROM is busy with a command.
Bit 0 – FBUSY Flash Busy
This bit will read '1' when the Flash is busy with a command.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 72
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.5.4
Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
INTCTRL
0x03
0x00
-
6
5
4
3
2
1
0
EEREADY
Access
R/W
Reset
0
Bit 0 – EEREADY EEPROM Ready Interrupt
Writing a '1' to this bit enables the interrupt, which indicates that the EEPROM is ready for new write/
erase operations.
This is a level interrupt that will be triggered only when the EEREADY flag in the INTFLAGS register is set
to zero. Thus, the interrupt should not be enabled before triggering an NVM command, as the EEREADY
flag will not be set before the NVM command issued. The interrupt should be disabled in the interrupt
handler.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 73
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.5.5
Interrupt Flags
Name:
Offset:
Reset:
Property:
Bit
7
INTFLAGS
0x04
0x00
-
6
5
4
3
2
1
0
EEREADY
Access
R/W
Reset
0
Bit 0 – EEREADY EEREADY Interrupt Flag
This flag is set continuously as long as the EEPROM is not busy. This flag is cleared by writing a '1' to it.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 74
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.5.6
Data
Name:
Offset:
Reset:
Property:
DATA
0x06
0x00
-
The NVMCTRL.DATAL and NVMCTRL.DATAH register pair represents the 16-bit value,
NVMCTRL.DATA. The low byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8]
(suffix H) can be accessed at offset + 0x01.
Bit
15
14
13
12
11
10
9
8
DATA[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
DATA[7:0]
Access
Reset
Bits 15:0 – DATA[15:0] Data Register
This register is used by the UPDI for fuse write operations.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 75
ATtiny1616/3216
NVMCTRL - Nonvolatile Memory Controller
9.5.7
Address
Name:
Offset:
Reset:
Property:
ADDR
0x08
0x00
-
The NVMCTRL.ADDRL and NVMCTRL.ADDRH register pair represents the 16-bit value,
NVMCTRL.ADDR. The low byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8]
(suffix H) can be accessed at offset + 0x01.
Bit
15
14
13
12
11
10
9
8
ADDR[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
ADDR[7:0]
Access
Reset
Bits 15:0 – ADDR[15:0] Address
The Address register contains the address to the last memory location that has been updated.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 76
ATtiny1616/3216
CLKCTRL - Clock Controller
10.
CLKCTRL - Clock Controller
10.1
Features
• All clocks and clock sources are automatically enabled when requested by peripherals
• Internal Oscillators:
– 16/20 MHz Oscillator (OSC20M)
– 32 KHz Ultra Low-Power Oscillator (OSCULP32K)
• External Clock Options:
– 32.768 kHz Crystal Oscillator (XOSC32K)
– External clock
• Main Clock Features:
– Safe run-time switching
– Prescaler with 1x to 64x division in 12 different settings
10.2
Overview
The Clock Controller peripheral (CLKCTRL) controls, distributes, and prescales the clock signals from the
available oscillators. The CLKCTRL supports internal and external clock sources.
The CLKCTRL is based on an automatic clock request system, implemented in all peripherals on the
device. The peripherals will automatically request the clocks needed. If multiple clock sources are
available, the request is routed to the correct clock source.
The Main Clock (CLK_MAIN) is used by the CPU, RAM, and the I/O bus. The main clock source can be
selected and prescaled. Some peripherals can share the same clock source as the main clock, or run
asynchronously to the main clock domain.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 77
ATtiny1616/3216
CLKCTRL - Clock Controller
10.2.1
Block Diagram - CLKCTRL
Figure 10-1. CLKCTRL Block Diagram
NVM
RAM
CPU
CLK_CPU
Other
Peripherals
CLKOUT
CLK_PER
RTC
WDT
INT
BOD
TCD
PRESCALER
CLK_RTC
CLK_WDT
CLK_BOD
CLK_TCD
TCD
CLKCSEL
Main Clock Prescaler
CLK_MAIN
RTC
CLKSEL
Main Clock Switch
DIV32
XOSC32K
OSCULP32K
OSC20M
XOSC32K
SEL
OSC20M
int. Oscillator
32 KHz ULP
Int. Oscillator
32.768 kHz
ext. Crystal Osc.
TOSC2
TOSC1
EXTCLK
The clock system consists of the main clock and other asynchronous clocks:
• Main Clock
This clock is used by the CPU, RAM, Flash, the I/O bus, and all peripherals connected to the I/O bus.
It is always running in Active and Idle Sleep mode and can be running in Standby Sleep mode if
requested.
The main clock CLK_MAIN is prescaled and distributed by the clock controller:
• CLK_CPU is used by the CPU, SRAM, and the NVMCTRL peripheral to access the nonvolatile
memory
• CLK_PER is used by all peripherals that are not listed under asynchronous clocks.
• Clocks running asynchronously to the main clock domain:
– CLK_RTC is used by the RTC/PIT. It will be requested when the RTC/PIT is enabled. The clock
source for CLK_RTC should only be changed if the peripheral is disabled.
– CLK_WDT is used by the WDT. It will be requested when the WDT is enabled.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 78
ATtiny1616/3216
CLKCTRL - Clock Controller
– CLK_BOD is used by the BOD. It will be requested when the BOD is enabled in Sampled mode.
The clock source for the for the main clock domain is configured by writing to the Clock Select bits
(CLKSEL) in the Main Clock Control A register (CLKCTRL.MCLKCTRLA). The asynchronous clock
sources are configured by registers in the respective peripheral.
10.2.2
Signal Description
Signal
Type
Description
CLKOUT
Digital output
CLK_PER output
Related Links
5. I/O Multiplexing and Considerations
10.3
Functional Description
10.3.1
Sleep Mode Operation
When a clock source is not used/requested it will turn OFF. It is possible to request a clock source directly
by writing a '1' to the Run Standby bit (RUNSTDBY) in the respective oscillator's Control A register
(CLKCTRL.[osc]CTRLA). This will cause the oscillator to run constantly, except for Power-Down Sleep
mode. Additionally, when this bit is written to '1' the oscillator start-up time is eliminated when the clock
source is requested by a peripheral.
The main clock will always run in Active and Idle Sleep mode. In Standby Sleep mode, the main clock will
only run if any peripheral is requesting it, or the Run in Standby bit (RUNSTDBY) in the respective
oscillator's Control A register (CLKCTRL.[osc]CTRLA) is written to '1'.
In Power-Down Sleep mode, the main clock will stop after all NVM operations are completed.
10.3.2
Main Clock Selection and Prescaler
All internal oscillators can be used as the main clock source for CLK_MAIN. The main clock source is
selectable from software and can be safely changed during normal operation.
Built-in hardware protection prevents unsafe clock switching:
Upon selection of an external clock source, a switch to the chosen clock source will only occur if edges
are detected, indicating it is stable. Until a sufficient number of clock edges are detected, the switch will
not occur and it will not be possible to change to another clock source again without executing a Reset.
An ongoing clock source switch is indicated by the System Oscillator Changing flag (SOSC) in the Main
Clock Status register (CLKCTRL.MCLKSTATUS). The stability of the external clock sources is indicated
by the respective status flags (EXTS and XOSC32KS in CLKCTRL.MCLKSTATUS).
CAUTION
If an external clock source fails while used as CLK_MAIN source, only the WDT can provide a
mechanism to switch back via System Reset.
CLK_MAIN is fed into a prescaler before it is used by the peripherals (CLK_PER) in the device. The
prescaler divide CLK_MAIN by a factor from 1 to 64.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 79
ATtiny1616/3216
CLKCTRL - Clock Controller
Figure 10-2. Main Clock and Prescaler
OSC20M
32 kHz Osc.
CLK_MAIN
Main Clock Prescaler
(Div 1, 2, 4, 8, 16, 32,
64, 6, 10, 24, 48)
32.768 kHz crystal Osc.
External clock
CLK_PER
The Main Clock and Prescaler configuration registers (CLKCTRL.MCLKCTRLA,
CLKCTRL.MCLKCTRLB) are protected by the Configuration Change Protection Mechanism, employing a
timed write procedure for changing these registers.
Related Links
8.5.7 Configuration Change Protection (CCP)
10.3.3
Main Clock After Reset
After any Reset, CLK_MAIN is provided by the 16/20 MHz Oscillator (OSC20M) and with a prescaler
division factor of 6. Since the actual frequency of the OSC20M is determined by the Frequency Select
bits (FREQSEL) of the Oscillator Configuration fuse (FUSE.OSCCFG), these frequencies are possible
after Reset:
Table 10-1. Peripheral Clock Frequencies After Reset
CLK_MAIN
as Per FREQSEL in FUSE.OSCCFG
Resulting CLK_PER
16 MHz
2.66 MHz
20 MHz
3.3 MHz
See the OSC20M description for further details.
Related Links
10.3.4.1.1 16/20 MHz Oscillator (OSC20M)
10.3.4
Clock Sources
All internal clock sources are enabled automatically when they are requested by a peripheral. The crystal
oscillator, based on an external crystal, must be enabled by writing a '1' to the ENABLE bit in the 32 KHz
Crystal Oscillator Control A register (CLKCTRL.XOSC32KCTRLA) before it can serve as a clock source.
The respective Oscillator Status bits in the Main Clock Status register (CLKCTRL.MCLKSTATUS) indicate
whether the clock source is running and stable.
Related Links
6.10 Configuration and User Fuses (FUSE)
8.5.7 Configuration Change Protection (CCP)
10.3.4.1 Internal Oscillators
The internal oscillators do not require any external components to run. See the related links for accuracy
and electrical characteristics.
Related Links
37. Electrical Characteristics
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 80
ATtiny1616/3216
CLKCTRL - Clock Controller
10.3.4.1.1 16/20 MHz Oscillator (OSC20M)
This oscillator can operate at multiple frequencies, selected by the value of the Frequency Select bits
(FREQSEL) in the Oscillator Configuration Fuse (FUSE.OSCCFG). The center frequencies are:
• 16 MHz
• 20 MHz
After a system Reset, FUSE.OSCCFG determines the initial frequency of CLK_MAIN.
During Reset, the calibration values for the OSC20M are loaded from fuses. There are two different
calibration bit fields:
• The Calibration bit field (CAL20M) in the Calibration A register (CLKCTRL.OSC20MCALIBA) enables
calibration around the current center frequency.
• The Oscillator Temperature Coefficient Calibration bit field (TEMPCAL20M) in the Calibration B
register (CLKCTRL.OSC20MCALIBB) enables adjustment of the slope of the temperature drift
compensation.
For applications requiring more fine-tuned frequency setting than the oscillator calibration provides,
factory stored frequency error after calibrations are available.
The oscillator calibration can be locked by the Oscillator Lock (OSCLOCK) Fuse (FUSE.OSCCFG). When
this fuse is ‘1’, it is not possible to change the calibration. The calibration is locked if this oscillator is used
as the main clock source and the Lock Enable bit (LOCKEN) in the Control B register
(CLKCTRL.OSC20MCALIBB) is ‘1’.
The calibration bits are protected by the Configuration Change Protection Mechanism, requiring a timed
write procedure for changing the main clock and prescaler settings.
The start-up time of this oscillator is the analog start-up time plus four oscillator cycles. Refer to the
Electrical Characteristics section for the start-up time.
When changing the oscillator calibration value, the frequency may overshoot. If the oscillator is used as
the main clock (CLK_MAIN) it is recommended to change the main clock prescaler so that the main clock
frequency does not exceed ¼ of the maximum operation main clock frequency as described in the
General Operating Ratings section. The system clock prescaler can be changed back after the oscillator
calibration value has been updated.
Related Links
6.10 Configuration and User Fuses (FUSE)
10.3.5 Configuration Change Protection
37.3 General Operating Ratings
10.3.3 Main Clock After Reset
37.10 Oscillators and Clocks
OSC20M Stored Frequency Error Compensation
This oscillator can operate at multiple frequencies, selected by the value of the Frequency Select bits
(FREQSEL) in the Oscillator Configuration fuse (FUSE.OSCCFG) at Reset. As previously mentioned
appropriate calibration values are loaded to adjust to center frequency (OSC20M), and temperature drift
compensation (TEMPCAL20M), meeting the specifications defined in the internal oscillator
characteristics. For applications requiring wider operating range, the relative factory stored frequency
error after calibrations can be used. The four errors are measured at different settings and are available in
the signature row as signed byte values.
• SIGROW.OSC16ERR3V is the frequency error from 16 MHz measured at 3V
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 81
ATtiny1616/3216
CLKCTRL - Clock Controller
• SIGROW.OSC16ERR5V is the frequency error from 16 MHz measured at 5V
• SIGROW.OSC20ERR3V is the frequency error from 20 MHz measured at 3V
• SIGROW.OSC20ERR5V is the frequency error from 20 MHz measured at 5V
The error is stored as a compressed Q1.10 fixed point 8-bit value, in order not to lose resolution, where
the MSB is the sign bit and the seven LSBs the lower bits of the Q1.10.
BAUDact��� = BAUD����� +
BAUD����� * �����������
1024
The minimum legal BAUD register value is 0x40, the target BAUD register value should therefore not be
lower than 0x4A to ensure that the compensated BAUD value stays within the legal range, even for parts
with negative compensation values. The example code below demonstrates how to apply this value for
more accurate USART baud rate:
#include
/* Baud rate compensated with factory stored frequency error */
/* Asynchronous communication without Auto-baud (Sync Field) */
/* 16MHz Clock, 3V and 600 BAUD
*/
int8_t sigrow_val
int32_t baud_reg_val
= SIGROW.OSC16ERR3V;
= 600;
assert (baud_reg_val >= 0x4A);
value with max neg comp
baud_reg_val *= (1024 + sigrow_val);
baud_reg_val /= 1024;
USART0.BAUD = (int16_t) baud_reg_val;
// read signed error
// ideal BAUD register value
// Verify legal min BAUD register
// sum resolution + error
// divide by resolution
// set adjusted baud rate
Related Links
37.10 Oscillators and Clocks
10.3.4.1.2 32 KHz Oscillator (OSCULP32K)
The 32 KHz oscillator is optimized for Ultra Low-Power (ULP) operation. Power consumption is
decreased at the cost of decreased accuracy compared to an external crystal oscillator.
This oscillator provides the 1 KHz signal for the Real-Time Counter (RTC), the Watchdog Timer (WDT),
and the Brown-out Detector (BOD).
The start-up time of this oscillator is the oscillator start-up time plus four oscillator cycles. Refer to the
Electrical Characteristics chapter for the start-up time.
Related Links
17. BOD - Brown-out Detector
19. WDT - Watchdog Timer
23. RTC - Real-Time Counter
10.3.4.2 External Clock Sources
These external clock sources are available:
• External Clock from pin EXTCLK
• The TOSC1 and TOSC2 pins are dedicated to driving a 32.768 kHz Crystal Oscillator (XOSC32K).
• Instead of a crystal oscillator, TOSC1 can be configured to accept an external clock source.
10.3.4.2.1 32.768 kHz Crystal Oscillator (XOSC32K)
This oscillator supports two input options: Either a crystal is connected to the pins TOSC1 and TOSC2, or
an external clock running at 32 KHz is connected to TOSC1. The input option must be configured by
writing the Source Select bit (SEL) in the XOSC32K Control A register (CLKCTRL.XOSC32KCTRLA).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 82
ATtiny1616/3216
CLKCTRL - Clock Controller
The XOSC32K is enabled by writing a '1' to its ENABLE bit in CLKCTRL.XOSC32KCTRLA. When
enabled, the configuration of the GPIO pins used by the XOSC32K is overridden as TOSC1, TOSC2 pins.
The Enable bit needs to be set for the oscillator to start running when requested.
The start-up time of a given crystal oscillator can be accommodated by writing to the Crystal Start-up
Time bits (CSUT) in CLKCTRL.XOSC32KCTRLA.
When XOSC32K is configured to use an external clock on TOSC1, the start-up time is fixed to two cycles.
10.3.4.2.2 External Clock (EXTCLK)
The EXTCLK is taken directly from the pin. This GPIO pin is automatically configured for EXTCLK if any
peripheral is requesting this clock.
This clock source has a start-up time of two cycles when first requested.
10.3.5
Configuration Change Protection
This peripheral has registers that are under Configuration Change Protection (CCP). In order to write to
these, a certain key must be written to the CPU.CCP register first, followed by a write access to the
protected bits within four CPU instructions.
Attempting to write to a protected register without following the appropriate CCP unlock sequence leaves
the protected register unchanged.
The following registers are under CCP:
Table 10-2. CLKCTRL - Registers Under Configuration Change Protection
Register
Key
CLKCTRL.MCLKCTRLB
IOREG
CLKCTRL.MCLKLOCK
IOREG
CLKCTRL.XOSC32KCTRLA
IOREG
CLKCTRL.MCLKCTRLA
IOREG
CLKCTRL.OSC20MCTRLA
IOREG
CLKCTRL.OSC20MCALIBA
IOREG
CLKCTRL.OSC20MCALIBB
IOREG
CLKCTRL.OSC32KCTRLA
IOREG
Related Links
8.5.7.1 Sequence for Write Operation to Configuration Change Protected I/O Registers
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 83
ATtiny1616/3216
CLKCTRL - Clock Controller
10.4
Register Summary - CLKCTRL
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
...
0x0F
0x10
0x11
0x12
0x13
...
0x17
0x18
0x19
...
0x1B
0x1C
MCLKCTRLA
MCLKCTRLB
MCLKLOCK
MCLKSTATUS
7:0
7:0
7:0
7:0
10.5
CLKOUT
CLKSEL[1:0]
PEN
LOCKEN
SOSC
PDIV[3:0]
EXTS
XOSC32KS
OSC32KS
OSC20MS
Reserved
OSC20MCTRLA
OSC20MCALIBA
OSC20MCALIBB
7:0
7:0
7:0
RUNSTDBY
CAL20M[5:0]
TEMPCAL20M[3:0]
LOCK
Reserved
OSC32KCTRLA
7:0
RUNSTDBY
Reserved
XOSC32KCTRLA
7:0
CSUT[1:0]
SEL
RUNSTDBY
ENABLE
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 84
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.1
Main Clock Control A
Name:
Offset:
Reset:
Property:
Bit
7
MCLKCTRLA
0x00
0x00
Configuration Change Protection
6
5
4
3
2
1
CLKOUT
Access
Reset
0
CLKSEL[1:0]
R/W
R/W
R/W
0
0
0
Bit 7 – CLKOUT System Clock Out
When this bit is written to '1', the system clock is output to CLKOUT pin.
When the device is in a Sleep mode, there is no clock output unless a peripheral is using the system
clock.
Bits 1:0 – CLKSEL[1:0] Clock Select
This bit field selects the source for the Main Clock (CLK_MAIN).
Value
Name
Description
0x0
OSC20M
16/20 MHz internal oscillator
0x1
OSCULP32K
32 KHz internal ultra low-power oscillator
0x2
XOSC32K
32.768 kHz external crystal oscillator
0x3
EXTCLK
External clock
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 85
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.2
Main Clock Control B
Name:
Offset:
Reset:
Property:
Bit
7
MCLKCTRLB
0x01
0x11
Configuration Change Protection
6
5
4
3
2
1
R/W
R/W
R/W
R/W
1
R/W
0
0
0
1
PDIV[3:0]
Access
Reset
0
PEN
Bits 4:1 – PDIV[3:0] Prescaler Division
If the Prescaler Enable (PEN) bit is written to ‘1’, these bits define the division ratio of the main clock
prescaler.
These bits can be written during run-time to vary the clock frequency of the system to suit the application
requirements.
The user software must ensure a correct configuration of input frequency (CLK_MAIN) and prescaler
settings, such that the resulting frequency of CLK_PER never exceeds the allowed maximum (see
Electrical Characteristics).
Value
Description
Value
Division
0x0
2
0x1
4
0x2
8
0x3
16
0x4
32
0x5
64
0x8
6
0x9
10
0xA
12
0xB
24
0xC
48
other
Reserved
Bit 0 – PEN Prescaler Enable
This bit must be written '1' to enable the prescaler. When enabled, the division ratio is selected by the
PDIV bit field.
When this bit is written to '0', the main clock will pass through undivided (CLK_PER=CLK_MAIN),
regardless of the value of PDIV.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 86
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.3
Main Clock Lock
Name:
Offset:
Reset:
Property:
Bit
7
MCLKLOCK
0x02
Based on OSCLOCK in FUSE.OSCCFG
Configuration Change Protection
6
5
4
3
2
1
0
LOCKEN
Access
R/W
Reset
x
Bit 0 – LOCKEN Lock Enable
Writing this bit to '1' will lock the CLKCTRL.MCLKCTRLA and CLKCTRL.MCLKCTRLB registers, and, if
applicable, the calibration settings for the current main clock source from further software updates. Once
locked, the CLKCTRL.MCLKLOCK registers cannot be accessed until the next hardware Reset.
This provides protection for the CLKCTRL.MCLKCTRLA and CLKCTRL.MCLKCTRLB registers and
calibration settings for the main clock source from unintentional modification by software.
At Reset, the LOCKEN bit is loaded based on the OSCLOCK bit in FUSE.OSCCFG.
Related Links
6.10 Configuration and User Fuses (FUSE)
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 87
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.4
Main Clock Status
Name:
Offset:
Reset:
Property:
Bit
MCLKSTATUS
0x03
0x00
-
7
6
5
4
3
2
1
0
EXTS
XOSC32KS
OSC32KS
OSC20MS
SOSC
Access
R
R
R
R
R
Reset
0
0
0
0
0
Bit 7 – EXTS External Clock Status
Value
Description
0
EXTCLK has not started
1
EXTCLK has started
Bit 6 – XOSC32KS XOSC32K Status
The Status bit will only be available if the source is requested as the main clock or by another module. If
the oscillator RUNSTDBY bit is set but the oscillator is unused/not requested, this bit will be 0.
Value
Description
0
XOSC32K is not stable
1
XOSC32K is stable
Bit 5 – OSC32KS OSCULP32K Status
The Status bit will only be available if the source is requested as the main clock or by another module. If
the oscillator RUNSTDBY bit is set but the oscillator is unused/not requested, this bit will be 0.
Value
Description
0
OSCULP32K is not stable
1
OSCULP32K is stable
Bit 4 – OSC20MS OSC20M Status
The Status bit will only be available if the source is requested as the main clock or by another module. If
the oscillator RUNSTDBY bit is set but the oscillator is unused/not requested, this bit will be 0.
Value
Description
0
OSC20M is not stable
1
OSC20M is stable
Bit 0 – SOSC Main Clock Oscillator Changing
Value
Description
0
The clock source for CLK_MAIN is not undergoing a switch
1
The clock source for CLK_MAIN is undergoing a switch and will change as soon as the new
source is stable
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 88
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.5
16/20 MHz Oscillator Control A
Name:
Offset:
Reset:
Property:
Bit
7
OSC20MCTRLA
0x10
0x00
Configuration Change Protection
6
5
4
3
2
1
0
RUNSTDBY
Access
R/W
Reset
0
Bit 1 – RUNSTDBY Run Standby
This bit forces the oscillator ON in all modes, even when unused by the system. In Standby Sleep mode
this can be used to ensure immediate wake-up and not waiting for oscillator start-up time.
When not requested by peripherals, no oscillator output is provided.
It takes four oscillator cycles to open the clock gate after a request but the oscillator analog start-up time
will be removed when this bit is set.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 89
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.6
16/20 MHz Oscillator Calibration A
Name:
Offset:
Reset:
Property:
Bit
7
OSC20MCALIBA
0x11
Based on FREQSEL in FUSE.OSCCFG
Configuration Change Protection
6
5
4
3
2
1
0
R/W
R/W
R/W
x
x
R/W
R/W
R/W
x
x
x
x
CAL20M[5:0]
Access
Reset
Bits 5:0 – CAL20M[5:0] Calibration
These bits change the frequency around the current center frequency of the OSC20M for fine-tuning.
At Reset, the factory calibrated values are loaded based on the FREQSEL bits in FUSE.OSCCFG.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 90
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.7
16/20 MHz Oscillator Calibration B
Name:
Offset:
Reset:
Property:
Bit
7
OSC20MCALIBB
0x12
Based on FUSE.OSCCFG
Configuration Change Protection
6
5
4
3
2
LOCK
1
0
TEMPCAL20M[3:0]
Access
R
R/W
R/W
R/W
R/W
Reset
x
x
x
x
x
Bit 7 – LOCK Oscillator Calibration Locked by Fuse
When this bit is set, the calibration settings in CLKCTRL.OSC20MCALIBA and
CLKCTRL.OSC20MCALIBB cannot be changed.
The reset value is loaded from the OSCLOCK bit in the Oscillator Configuration Fuse (FUSE.OSCCFG).
Bits 3:0 – TEMPCAL20M[3:0] Oscillator Temperature Coefficient Calibration
These bits tune the slope of the temperature compensation.
At Reset, the factory calibrated values are loaded based on the FREQSEL bits in FUSE.OSCCFG.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 91
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.8
32 KHz Oscillator Control A
Name:
Offset:
Reset:
Property:
Bit
7
OSC32KCTRLA
0x18
0x00
Configuration Change Protection
6
5
4
3
2
1
0
RUNSTDBY
Access
R/W
Reset
0
Bit 1 – RUNSTDBY Run Standby
This bit forces the oscillator ON in all modes, even when unused by the system. In Standby Sleep mode
this can be used to ensure immediate wake-up and not waiting for the oscillator start-up time.
When not requested by peripherals, no oscillator output is provided.
It takes four oscillator cycles to open the clock gate after a request but the oscillator analog start-up time
will be removed when this bit is set.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 92
ATtiny1616/3216
CLKCTRL - Clock Controller
10.5.9
32.768 kHz Crystal Oscillator Control A
Name:
Offset:
Reset:
Property:
XOSC32KCTRLA
0x1C
0x00
Configuration Change Protection
The SEL and CSUT bits cannot be changed as long as the ENABLE bit is set or the XOSC32K Stable bit
(XOSC32KS) in CLKCTRL.MCLKSTATUS is high.
To change settings in a safe way: write a '0' to the ENABLE bit and wait until XOSC32KS is '0' before reenabling the XOSC32K with new settings.
Bit
7
6
5
4
3
CSUT[1:0]
Access
Reset
2
1
0
SEL
RUNSTDBY
ENABLE
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
Bits 5:4 – CSUT[1:0] Crystal Start-Up Time
These bits select the start-up time for the XOSC32K. It is write protected when the oscillator is enabled
(ENABLE=1).
If SEL=1, the start-up time will not be applied.
Value
Name
Description
0x0
1K
1k cycles
0x1
16K
16k cycles
0x2
32K
32k cycles
0x3
64K
64k cycles
Bit 2 – SEL Source Select
This bit selects the external source type. It is write protected when the oscillator is enabled (ENABLE=1).
Value
Description
0
External crystal
1
External clock on TOSC1 pin
Bit 1 – RUNSTDBY Run Standby
Writing this bit to '1' starts the crystal oscillator and forces the oscillator ON in all modes, even when
unused by the system if the ENABLE bit is set. In Standby Sleep mode this can be used to ensure
immediate wake-up and not waiting for oscillator start-up time. When this bit is '0', the crystal oscillator is
only running when requested and the ENABLE bit is set.
The output of XOSC32K is not sent to other peripherals unless it is requested by one or more peripherals.
When the RUNSTDBY bit is set there will only be a delay of two to three crystal oscillator cycles after a
request until the oscillator output is received, if the initial crystal start-up time has already completed.
According to RUNSTBY bit, the oscillator will be turned ON all the time if the device is in Active, Idle, or
Standby Sleep mode, or only be enabled when requested.
This bit is I/O protected to prevent unintentional enabling of the oscillator.
Bit 0 – ENABLE Enable
When this bit is written to '1', the configuration of the respective input pins is overridden to TOSC1 and
TOSC2. Also, the Source Select bit (SEL) and Crystal Start-Up Time (CSUT) become read-only.
This bit is I/O protected to prevent unintentional enabling of the oscillator.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 93
ATtiny1616/3216
SLPCTRL - Sleep Controller
11.
SLPCTRL - Sleep Controller
11.1
Features
• Power management for adjusting power consumption and functions
• Three sleep modes:
– Idle
– Standby
– Power-Down
• Configurable Standby Sleep mode where peripherals can be configured as ON or OFF.
11.2
Overview
Sleep modes are used to shut down peripherals and clock domains in the device in order to save power.
The Sleep Controller (SLPCTRL) controls and handles the transitions between active and sleep mode.
There are in total four modes available:
• One active mode in which the software is executed
• Three sleep modes:
– Idle
– Standby
– Power-Down
All sleep modes are available and can be entered from active mode. In active mode, the CPU is
executing application code. When the device enters sleep mode, program execution is stopped and
interrupts or a reset is used to wake the device again. The application code decides which sleep mode to
enter and when.
Interrupts are used to wake the device from sleep. The available interrupt wake-up sources depend on
the configured sleep mode. When an interrupt occurs, the device will wake up and execute the interrupt
service routine before continuing normal program execution from the first instruction after the SLEEP
instruction. Any Reset will take the device out of a sleep mode.
The content of the register file, SRAM and registers are kept during sleep. If a Reset occurs during sleep,
the device will reset, start, and execute from the Reset vector.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 94
ATtiny1616/3216
SLPCTRL - Sleep Controller
11.2.1
Block Diagram
Figure 11-1. Sleep Controller in System
SLEEP Instruction
Interrupt Request
SLPCTRL
CPU
Sleep State
Interrupt Request
Peripheral
11.2.2
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 11-1. SLPCTRL System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
No
-
Interrupts
No
-
Events
No
-
Debug
Yes
UPDI
11.2.2.1 Clocks
This peripheral depends on the peripheral clock.
Related Links
10. CLKCTRL - Clock Controller
11.2.2.2 I/O Lines and Connections
Not applicable.
11.2.2.3 Interrupts
Not applicable.
11.2.2.4 Events
Not applicable.
11.2.2.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. The SLPCTRL is only affected
by a break in debug operation: If the SLPCTRL is in a sleep mode when a break occurs, the device will
wake up and the SLPCTRL will go to Active mode, even if there are no pending interrupt requests.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 95
ATtiny1616/3216
SLPCTRL - Sleep Controller
11.3
Functional Description
11.3.1
Initialization
To put the device into a sleep mode, follow these steps:
• Configure and enable the interrupts that shall be able to wake the device from sleep. Also, enable
global interrupts.
WARNING
If there are no interrupts enabled when going to sleep, the device cannot wake up again.
Only a Reset will allow the device to continue operation.
• Select the sleep mode to be entered and enable the Sleep Controller by writing to the Sleep Mode
bits (SMODE) and the Enable bit (SEN) in the Control A register (SLPCTRL.CTRLA). A SLEEP
instruction must be run to make the device actually go to sleep.
11.3.2
Operation
11.3.2.1 Sleep Modes
In addition to Active mode, there are three different sleep modes, with decreasing power consumption
and functionality.
Idle
Standby
PowerDown
The CPU stops executing code, no peripherals are disabled.
All interrupt sources can wake-up the device.
The user can configure peripherals to be enabled or not, using the respective RUNSTBY bit.
This means that the power consumption is highly dependent on what functionality is enabled,
and thus may vary between the Idle and Power-Down levels.
SleepWalking is available for the ADC module.
The wake-up sources are pin interrupts, TWI address match, UART Start-of-Frame interrupt
(if USART is enabled to run in Standby), ADC window interrupt (if PTC enabled to run in
Standby), RTC interrupt (if RTC enabled to run in Standby), and TCB interrupt.
Only the WDT and the PIT (a component of the RTC) are active.
The only wake-up sources are the pin change interrupt and TWI address match.
Table 11-2. Sleep Mode Activity Overview
Group
Peripheral
Active in Sleep Mode
Clock
Active Clock
Domain
Idle
Standby
Power-Down
CPU
CLK_CPU
Peripherals
CLK_PER
X
RTC
CLK_RTC
X
X*
ADC/PTC
CLK_PER
X
X*
PIT (RTC)
CLK_RTC
X
X
X
WDT
CLK_WDT
X
X
X
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 96
ATtiny1616/3216
SLPCTRL - Sleep Controller
...........continued
Group
Peripheral
Active in Sleep Mode
Clock
Oscillators
Wake-Up
Sources
Idle
Standby
Power-Down
Main Clock Source
X
X*
RTC Clock Source
X
X*
WDT Oscillator
X
X
X
INTn and Pin Change
X
X
X
TWI Address Match
X
X
X
Periodic Interrupt Timer
X
X
X
UART Start-of-Frame
X
X*
ADC/PTC Window
X
X*
RTC Interrupt
X
X*
All other Interrupts
X
Note:
• X means active. X* indicates that the RUNSTBY bit of the corresponding peripheral must be set to
enter the active state.
11.3.2.2 Wake-Up Time
The normal wake-up time for the device is six main clock cycles (CLK_PER), plus the time it takes to start
up the main clock source:
• In Idle Sleep mode, the main clock source is kept running so it will not be any extra wake-up time.
• In Standby Sleep mode, the main clock might be running so it depends on the peripheral
configuration.
• In Power-Down Sleep mode, only the ULP 32 KHz oscillator and RTC clock may be running if it is
used by the BOD or WDT. All other clock sources will be OFF.
Table 11-3. Sleep Modes and Start-Up Time
Sleep Mode
Start-Up Time
IDLE
6 CLK
Standby
6 CLK + OSC start-up
Power-Down
6 CLK + OSC start-up
The start-up time for the different clock sources is described in the Clock Controller (CLKCTRL) section.
In addition to the normal wake-up time, it is possible to make the device wait until the BOD is ready
before executing code. This is done by writing 0x3 to the BOD Operation mode in Active and Idle bits
(ACTIVE) in the BOD Configuration fuse (FUSE.BODCFG). If the BOD is ready before the normal wakeup time, the total wake-up time will be the same. If the BOD takes longer than the normal wake-up time,
the wake-up time will be extended until the BOD is ready. This ensures correct supply voltage whenever
code is executed.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 97
ATtiny1616/3216
SLPCTRL - Sleep Controller
11.3.3
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 98
ATtiny1616/3216
SLPCTRL - Sleep Controller
11.4
Register Summary - SLPCTRL
Offset
Name
Bit Pos.
0x00
CTRLA
7:0
11.5
SMODE[1:0]
SEN
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 99
ATtiny1616/3216
SLPCTRL - Sleep Controller
11.5.1
Control A
Name:
Offset:
Reset:
Property:
CTRLA
0x00
0x00
-
Bit
7
6
5
4
3
2
1
Access
R
R
R
R
R
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
SMODE[1:0]
0
SEN
Bits 2:1 – SMODE[1:0] Sleep Mode
Writing these bits selects the sleep mode entered when the Sleep Enable bit (SEN) is written to '1' and
the SLEEP instruction is executed.
Value
Name
Description
0x0
IDLE
Idle Sleep mode enabled
0x1
STANDBY
Standby Sleep mode enabled
0x2
PDOWN
Power-Down Sleep mode enabled
other
Reserved
Bit 0 – SEN Sleep Enable
This bit must be written to '1' before the SLEEP instruction is executed to make the MCU enter the
selected sleep mode.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 100
ATtiny1616/3216
RSTCTRL - Reset Controller
12.
RSTCTRL - Reset Controller
12.1
Features
• Reset the device and set it to an initial state
• Reset Flag register for identifying the Reset source in the software
• Multiple Reset sources:
– Power supply Reset sources: Brown-out Detect (BOD), Power-on Reset (POR)
– User Reset sources: External Reset pin (RESET), Watchdog Reset (WDT), Software Reset
(SW), and UPDI Reset
12.2
Overview
The Reset Controller (RSTCTRL) manages the Reset of the device. It issues a device Reset, sets the
device to its initial state, and allows the Reset source to be identified by the software.
12.2.1
Block Diagram
Figure 12-1. Reset System Overview
RESET SOURCES
VDD
POR
Pull-up
Resistor
RESET
TCD pin
override settings
(Loaded from fuses)
RESET CONTROLLER
BOD
FILTER
UPDI
External Reset
WDT
All other
Peripherals
UPDI
CPU (SW)
12.2.2
Signal Description
Signal
Description
Type
RESET
External Reset (active-low)
Digital input
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 101
ATtiny1616/3216
RSTCTRL - Reset Controller
12.3
Functional Description
12.3.1
Initialization
The Reset Controller (RSTCTRL) is always enabled, but some of the Reset sources must be enabled
(either by fuses or by software) before they can request a Reset.
After any Reset, the Reset source that caused the Reset is found in the Reset Flag register
(RSTCTRL.RSTFR).
After a Power-on Reset, only the POR flag will be set.
The flags are kept until they are cleared by writing a '1' to them.
After Reset from any source, all registers that are loaded from fuses are reloaded.
12.3.2
Operation
12.3.2.1 Reset Sources
There are two kinds of sources for Resets:
• Power supply Resets, which are caused by changes in the power supply voltage: Power-on Reset
(POR) and Brown-out Detector (BOD).
• User Resets, which are issued by the application, by the debug operation, or by pin changes
(Software Reset, Watchdog Reset, UPDI Reset, and external Reset pin RESET).
12.3.2.1.1 Power-On Reset (POR)
A Power-on Reset (POR) is generated by an on-chip detection circuit. The POR is activated when the
VDD rises until it reaches the POR threshold voltage. The POR is always enabled and will also detect
when the VDD falls below the threshold voltage.
All volatile logic is reset on POR. All fuses are reloaded after the Reset is released.
12.3.2.1.2 Brown-Out Detector (BOD) Reset Source
The on-chip Brown-out Detection circuit will monitor the VDD level during operation by comparing it to a
fixed trigger level. The trigger level for the BOD can be selected by fuses. If BOD is unused in the
application, it is forced to a configured level in order to ensure safe operation during chip erase.
All logic is reset on BOD Reset, except the BOD configuration. All fuses are reloaded after the Reset is
released.
Related Links
17. BOD - Brown-out Detector
12.3.2.1.3 Software Reset
The software Reset makes it possible to issue a system Reset from software. The Reset is generated by
writing a '1' to the Software Reset Enable bit (SWRE) in the Software Reset register (RSTCTRL.SWRR).
The Reset will take place immediately after the bit is written and the device will be kept in reset until the
Reset sequence is completed. All logic is reset on software Reset, except UPDI and BOD configuration.
All fuses are reloaded after the Reset is released.
12.3.2.1.4 External Reset
The external Reset is enabled by fuse (see fuse map).
When enabled, the external Reset requests a Reset as long as the RESET pin is low. The device will stay
in Reset until RESET is high again. All logic is reset on external reset, except UPDI and BOD
configuration. All fuses are reloaded after the Reset is released.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 102
ATtiny1616/3216
RSTCTRL - Reset Controller
Related Links
6.10 Configuration and User Fuses (FUSE)
12.3.2.1.5 Watchdog Reset
The Watchdog Timer (WDT) is a system function for monitoring correct program operation. If the WDT is
not reset from software according to the programmed time-out period, a Watchdog Reset will be issued.
See the WDT documentation for further details.
All logic is reset on WDT Reset, except UPDI and BOD configuration. All fuses are reloaded after the
Reset is released.
Related Links
19. WDT - Watchdog Timer
12.3.2.1.6 Universal Program Debug Interface (UPDI) Reset
The UPDI contains a separate Reset source that is used to reset the device during external programming
and debugging. The Reset source is accessible only from external debuggers and programmers. All logic
is reset on UPDI Reset, except the UPDI itself and BOD configuration. All fuses are reloaded after the
Reset is released. See UPDI chapter on how to generate a UPDI Reset request.
Related Links
33. UPDI - Unified Program and Debug Interface
12.3.2.2 Reset Time
The Reset time can be split in two.
The first part is when any of the Reset sources are active. This part depends on the input to the Reset
sources. The external Reset is active as long as the RESET pin is low, the Power-on Reset (POR) and
Brown-out Detector (BOD) is active as long as the supply voltage is below the Reset source threshold.
When all the Reset sources are released, an internal Reset initialization of the device is done. This time
will be increased with the start-up time given by the start-up time fuse setting (SUT in FUSE.SYSCFG1).
The internal Reset initialization time will also increase if the CRCSCAN is configured to run at start-up
(CRCSRC in FUSE.SYSCFG0).
12.3.3
Sleep Mode Operation
The Reset Controller continues to operate in all active and sleep modes.
12.3.4
Configuration Change Protection
This peripheral has registers that are under Configuration Change Protection (CCP). In order to write to
these, a certain key must be written to the CPU.CCP register first, followed by a write access to the
protected bits within four CPU instructions.
Attempting to write to a protected register without following the appropriate CCP unlock sequence leaves
the protected register unchanged.
The following registers are under CCP:
Table 12-1. RSTCTRL - Registers Under Configuration Change Protection
Register
Key
RSTCTRL.SWRR
IOREG
Related Links
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 103
ATtiny1616/3216
RSTCTRL - Reset Controller
8.5.7.1 Sequence for Write Operation to Configuration Change Protected I/O Registers
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 104
ATtiny1616/3216
RSTCTRL - Reset Controller
12.4
Register Summary - RSTCTRL
Offset
Name
Bit Pos.
0x00
0x01
RSTFR
SWRR
7:0
7:0
12.5
UPDIRF
SWRF
WDRF
EXTRF
BORF
PORF
SWRE
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 105
ATtiny1616/3216
RSTCTRL - Reset Controller
12.5.1
Reset Flag Register
Name:
Offset:
Reset:
Property:
RSTFR
0x00
0xXX
-
All flags are cleared by writing a '1' to them. They are also cleared by a Power-on Reset, with the
exception of the Power-On Reset Flag (PORF).
Bit
7
6
5
4
3
2
1
0
UPDIRF
SWRF
WDRF
EXTRF
BORF
PORF
Access
R
R
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
x
x
x
x
x
x
Bit 5 – UPDIRF UPDI Reset Flag
This bit is set if a UPDI Reset occurs.
Bit 4 – SWRF Software Reset Flag
This bit is set if a Software Reset occurs.
Bit 3 – WDRF Watchdog Reset Flag
This bit is set if a Watchdog Reset occurs.
Bit 2 – EXTRF External Reset Flag
This bit is set if an External Reset occurs.
Bit 1 – BORF Brown-Out Reset Flag
This bit is set if a Brown-out Reset occurs.
Bit 0 – PORF Power-On Reset Flag
This bit is set if a Power-on Reset occurs.
This flag is only cleared by writing a '1' to it.
After a POR, only the POR flag is set and all other flags are cleared. No other flags can be set before a
full system boot is run after the POR.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 106
ATtiny1616/3216
RSTCTRL - Reset Controller
12.5.2
Software Reset Register
Name:
Offset:
Reset:
Property:
SWRR
0x01
0x00
Configuration Change Protection
Bit
7
6
5
4
3
2
1
0
Access
R
R
R
R
R
R
R
R/W
Reset
0
0
0
0
0
0
0
0
SWRE
Bit 0 – SWRE Software Reset Enable
When this bit is written to '1', a software Reset will occur.
This bit will always read as '0'.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 107
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.
CPUINT - CPU Interrupt Controller
13.1
Features
•
•
•
•
•
•
Short and Predictable Interrupt Response Time
Separate Interrupt Configuration and Vector Address for Each Interrupt
Interrupt Prioritizing by Level and Vector Address
Non-Maskable Interrupts (NMI) for Critical Functions
Two Interrupt Priority Levels: 0 (normal) and 1 (high)
– One of the interrupt requests can optionally be assigned as a priority level 1 interrupt
– Optional round robin priority scheme for priority level 0 interrupts
• Interrupt Vectors Optionally Placed in the Application Section or the Boot Loader Section
• Selectable Compact Vector Table
13.2
Overview
An interrupt request signals a change of state inside a peripheral and can be used to alter program
execution. Peripherals can have one or more interrupts, and all are individually enabled and configured.
When an interrupt is enabled and configured, it will generate an interrupt request when the interrupt
condition occurs.
The CPU Interrupt Controller (CPUINT) handles and prioritizes interrupt requests. When an interrupt is
enabled and the interrupt condition occurs, the CPUINT will receive the interrupt request. Based on the
interrupt's priority level and the priority level of any ongoing interrupts, the interrupt request is either
acknowledged or kept pending until it has priority. When an interrupt request is acknowledged by the
CPUINT, the Program Counter is set to point to the interrupt vector. The interrupt vector is normally a
jump to the interrupt handler (i.e., the software routine that handles the interrupt). After returning from the
interrupt handler, program execution continues from where it was before the interrupt occurred. One
instruction is always executed before any pending interrupt is served.
The CPUINT Status register (CPUINT.STATUS) contains state information that ensures that the CPUINT
returns to the correct interrupt level when the RETI (interrupt return) instruction is executed at the end of
an interrupt handler. Returning from an interrupt will return the CPUINT to the state it had before entering
the interrupt. CPUINT.STATUS is not saved automatically upon an interrupt request.
By default, all peripherals are priority level 0. It is possible to set one single interrupt vector to the higher
priority level 1. Interrupts are prioritized according to their priority level and their interrupt vector address.
Priority level 1 interrupts will interrupt level 0 interrupt handlers. Among priority level 0 interrupts, the
priority is determined from the interrupt vector address, where the lowest interrupt vector address has the
highest interrupt priority.
Optionally, a round robin scheduling scheme can be enabled for priority level 0 interrupts. This ensures
that all interrupts are serviced within a certain amount of time.
Interrupt generation must be globally enabled by writing a '1' to the Global Interrupt Enable bit (I) in the
CPU Status register (CPU.SREG). This bit is not cleared when an interrupt is acknowledged.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 108
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.2.1
Block Diagram
Figure 13-1. CPUINT Block Diagram
Interrupt Controller
Priority
Decoder
Peripheral 1
INT REQ
CPU "RETI"
CPU INT ACK
CPU
INT LEVEL
Peripheral
n
INT REQ
CPU INT REQ
INT REQ
INT ACK
STATUS
LVL0PRI
LVL1VEC
Global
Interrupt
Enable
Wake-up
CPU.SREG
Sleep
Controller
13.2.2
Signal Description
Not applicable.
13.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 13-1. CPUINT System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
No
-
Interrupts
No
-
Events
No
-
Debug
Yes
UPDI
Related Links
13.2.3.5 Debug Operation
13.2.3.1 Clocks
13.2.3.1 Clocks
This peripheral depends on the peripheral clock.
Related Links
10. CLKCTRL - Clock Controller
13.2.3.2 I/O Lines and Connections
Not applicable.
13.2.3.3 Interrupts
Not applicable.
13.2.3.4 Events
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 109
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
Related Links
33. UPDI - Unified Program and Debug Interface
13.3
Functional Description
13.3.1
Initialization
An interrupt must be initialized in the following order:
1.
2.
3.
13.3.2
Configure the CPUINT if the default configuration is not adequate (optional):
– Vector handling is configured by writing to the respective bits (IVSEL and CVT) in the Control A
register (CPUINT.CTRLA).
– Vector prioritizing by round robin is enabled by writing a '1' to the Round Robin Priority Enable
bit (LVL0RR) in CPUINT.CTRLA.
– Select the priority level 1 vector by writing its address to the Interrupt Vector (LVL1VEC) in the
Level 1 Priority register (CPUINT.LVL1VEC).
Configure the interrupt conditions within the peripheral, and enable the peripheral's interrupt.
Enable interrupts globally by writing a '1' to the Global Interrupt Enable bit (I) in the CPU Status
register (CPU.SREG).
Operation
13.3.2.1 Enabling, Disabling, and Resetting
Global enabling of interrupts is done by writing a '1' to the Global Interrupt Enable bit (I) in the CPU Status
register (CPU.SREG). To disable interrupts globally, write a '0' to the I bit in CPU.SREG.
The desired interrupt lines must also be enabled in the respective peripheral, by writing to the peripheral's
Interrupt Control register (peripheral.INTCTRL).
Interrupt flags are not automatically cleared after the interrupt is executed. The respective INTFLAGS
register descriptions provide information on how to clear specific flags.
13.3.2.2 Interrupt Vector Locations
The interrupt vector placement is dependent on the value of Interrupt Vector Select bit (IVSEL) in the
Control A register (CPUINT.CTRLA). Refer to the IVSEL description in CPUINT.CTRLA for the possible
locations.
If the program never enables an interrupt source, the interrupt vectors are not used, and regular program
code can be placed at these locations.
13.3.2.3 Interrupt Response Time
The minimum interrupt response time for all enabled interrupts is three CPU clock cycles: one cycle to
finish the ongoing instruction, two cycles to store the Program Counter to the stack, and three cycles(1) to
jump to the interrupt handler (JMP).
After the Program Counter is pushed on the stack, the program vector for the interrupt is executed. See
Figure 13-2, first diagram.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 110
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
The jump to the interrupt handler takes three clock cycles(1). If an interrupt occurs during execution of a
multicycle instruction, this instruction is completed before the interrupt is served. See Figure 13-2, second
diagram.
If an interrupt occurs when the device is in sleep mode, the interrupt execution response time is
increased by five clock cycles. In addition, the response time is increased by the start-up time from the
selected sleep mode. See Figure 13-2, third diagram.
A return from an interrupt handling routine takes four to five clock cycles, depending on the size of the
Program Counter. During these clock cycles, the Program Counter is popped from the stack and the
Stack Pointer is incremented.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 111
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
Figure 13-2. Interrupt Execution of a Single-Cycle Instruction, Multicycle Instruction, and From
Sleep(1)
Single-Cycle Instruction
Multicycle Instruction
Sleep
Note:
1. Devices with 8 KB of Flash or less use RJMP instead of JMP, which takes only two clock cycles.
13.3.2.4 Interrupt Priority
All interrupt vectors are assigned to one of three possible priority levels as shown in the table. An
interrupt request from a high priority source will interrupt any ongoing interrupt handler from a normal
priority source. When returning from the high priority interrupt handler, the execution of the normal priority
interrupt handler will resume.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 112
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
Table 13-2. Interrupt Priority Levels
Priority
Level
Source
Highest
Non-Maskable Interrupt (NMI)
Device dependent and statically
assigned
...
High Priority (Level 1)
One vector is optionally user
selectable as Level 1
Lowest
Normal Priority (Level 0)
The remaining interrupt vectors
13.3.2.5 Scheduling of Normal Priority Interrupts
13.3.2.5.1 Non-Maskable Interrupts (NMI)
An NMI will be executed regardless of the setting of the I bit in CPU.SREG, and it will never change the I
bit. No other interrupt can interrupt an NMI handler. If more than one NMI is requested at the same time,
priority is static according to the interrupt vector address, where the lowest address has the highest
priority.
Which interrupts are non-maskable is device-dependent and not subject to configuration. Non-maskable
interrupts must be enabled before they can be used. Refer to the Interrupt Vector Mapping of the device
for available NMI lines.
Related Links
7.2 Interrupt Vector Mapping
13.3.2.5.2 Static Scheduling
If several level 0 interrupt requests are pending at the same time, the one with the highest priority is
scheduled for execution first. The CPUINT.LVL0PRI register makes it possible to change the default
priority. The Reset value for CPUINT.LVL0PRI is zero, resulting in a default priority as shown in the
following figure. As the figure shows, IVEC0 has the highest priority, and IVECn has the lowest priority.
Figure 13-3. Static Scheduling when CPUINT.LVL0PRI is Zero
Lowest Address
IVEC 0
Highest Priority
IVEC 1
:
:
:
IVEC Y
IVEC Y+1
:
:
:
Highest Address
IVEC n
Lowest Priority
The default priority can be changed by writing to the CPUINT.LVL0PRI register. The value written to the
register will identify the vector number with the lowest priority. The next interrupt vector in IVEC will have
the highest priority, see the following figure. In this figure, the value Y has been written to
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 113
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
CPUINT.LVL0PRI, so that interrupt vector Y+1 has the highest priority. Note that in this case, the priorities
will "wrap" so that IVEC0 has lower priority than IVECn.
Refer to the Interrupt Vector Mapping of the device for available interrupt requests and their interrupt
vector number.
Figure 13-4. Static Scheduling when CPUINT.LVL0PRI is Different From Zero
Lowest Address
IVEC 0
IVEC 1
:
:
:
IVEC Y
Lowest Priority
IVEC Y+1
Highest Priority
:
:
:
Highest Address
IVEC n
Related Links
7.2 Interrupt Vector Mapping
13.3.2.5.3 Round Robin Scheduling
Static scheduling may cause starvation, i.e. some interrupts might never be serviced. To avoid this, the
CPUINT offers round robin scheduling for normal priority (LVL0) interrupts. In round robin scheduling,
CPUINT.LVL0PRI contains the number of the vector number in IVEC with the lowest priority. This register
is automatically updated by hardware with the interrupt vector number for the last acknowledged LVL0
interrupt. This interrupt vector will, therefore, have the lowest priority next time one or more LVL0
interrupts are pending. Figure 13-5 explains the new priority ordering after IVEC Y was the last interrupt
to be acknowledged, and after IVEC Y+1 was the last interrupt to be acknowledged.
Round robin scheduling for LVL0 interrupt requests is enabled by writing a ‘1’ to the Round Robin Priority
Enable bit (LVL0RR) in the Control A register (CPUINT.CTRLA).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 114
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
Figure 13-5. Round Robin Scheduling
IVEC Y was last acknowledged
interrupt
IVEC Y+1 was last acknowledged
interrupt
IVEC 0
IVEC 0
:
:
:
:
:
:
IVEC Y
Lowest Priority
IVEC Y
IVEC Y+1
Highest Priority
IVEC Y+1
Lowest Priority
IVEC Y+2
Highest Priority
:
:
:
IVEC n
:
:
:
IVEC n
13.3.2.5.4 Compact Vector Table
The Compact Vector Table (CVT) is a feature to allow writing of compact code.
When CVT is enabled by writing a '1' to the CVT bit in the Control A register (CPUINT.CTRLA), the vector
table contains these three interrupt vectors:
1. The non-maskable interrupts (NMI) at vector address 1.
2. The priority level 1 (LVL1) interrupt at vector address 2.
3. All priority level 0 (LVL0) interrupts share vector address 3.
This feature is most suitable for applications using a small number of interrupt generators.
13.3.3
Events
Not applicable.
13.3.4
Sleep Mode Operation
Not applicable.
13.3.5
Configuration Change Protection
This peripheral has registers that are under Configuration Change Protection (CCP). In order to write to
these, a certain key must be written to the CPU.CCP register first, followed by a write access to the
protected bits within four CPU instructions.
Attempting to write to a protected register without following the appropriate CCP unlock sequence leaves
the protected register unchanged.
The following registers are under CCP:
Table 13-3. INTCTRL - Registers under Configuration Change Protection
Register
Key
IVSEL in CPUINT.CTRLA
IOREG
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 115
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
...........continued
Register
Key
CVT in CPUINT.CTRLA
IOREG
Related Links
8.5.7.1 Sequence for Write Operation to Configuration Change Protected I/O Registers
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 116
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.4
Register Summary - CPUINT
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
CTRLA
STATUS
LVL0PRI
LVL1VEC
7:0
7:0
7:0
7:0
13.5
IVSEL
CVT
NMIEX
LVL1EX
LVL0RR
LVL0EX
LVL0PRI[7:0]
LVL1VEC[7:0]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 117
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLA
0x00
0x00
Configuration Change Protection
6
5
4
3
2
1
0
IVSEL
CVT
LVL0RR
R/W
R/W
R/W
0
0
0
Bit 6 – IVSEL Interrupt Vector Select
If the boot section is defined, it will be placed before the application section. The actual start address of
the application section is determined by the BOOTEND fuse.
This bit is protected by the Configuration Change Protection mechanism.
Value
Description
0
Interrupt vectors are placed at the start of the application section of the Flash
1
Interrupt vectors are placed at the start of the boot section of the Flash
Bit 5 – CVT Compact Vector Table
This bit is protected by the Configuration Change Protection mechanism.
Value
Description
0
Compact Vector Table function is disabled
1
Compact Vector Table function is enabled
Bit 0 – LVL0RR Round Robin Priority Enable
This bit is not protected by the Configuration Change Protection mechanism.
Value
Description
0
Priority is fixed for priority level 0 interrupt requests: The lowest interrupt vector address has
the highest priority.
1
Round Robin priority scheme is enabled for priority level 0 interrupt requests
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 118
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.5.2
Status
Name:
Offset:
Reset:
Property:
Bit
7
STATUS
0x01
0x00
-
6
5
4
3
2
1
0
NMIEX
LVL1EX
LVL0EX
Access
R
R
R
Reset
0
0
0
Bit 7 – NMIEX Non-Maskable Interrupt Executing
This flag is set if a non-maskable interrupt is executing. The flag is cleared when returning (RETI) from
the interrupt handler.
Bit 1 – LVL1EX Level 1 Interrupt Executing
This flag is set when a priority level 1 interrupt is executing, or when the interrupt handler has been
interrupted by an NMI. The flag is cleared when returning (RETI) from the interrupt handler.
Bit 0 – LVL0EX Level 0 Interrupt Executing
This flag is set when a priority level 0 interrupt is executing, or when the interrupt handler has been
interrupted by a priority level 1 interrupt or an NMI. The flag is cleared when returning (RETI) from the
interrupt handler.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 119
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.5.3
Interrupt Priority Level 0
Name:
Offset:
Reset:
Property:
Bit
LVL0PRI
0x02
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
LVL0PRI[7:0]
Access
Reset
Bits 7:0 – LVL0PRI[7:0] Interrupt Priority Level 0
When Round Robin is enabled (the LVL0RR bit in CPUINT.CTRLA is '1'), this bit field stores the vector of
the last acknowledged priority level 0 (LVL0) interrupt. The stored vector will have the lowest priority next
time one or more LVL0 interrupts are pending.
If Round Robin is disabled (the LVL0RR bit in CPUINT.CTRLA is '0'), the vector address-based priority
scheme (lowest address has the highest priority) is governing the priorities of LVL0 interrupt requests.
If a system Reset is asserted, the lowest interrupt vector address will have the highest priority within the
LVL0.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 120
ATtiny1616/3216
CPUINT - CPU Interrupt Controller
13.5.4
Interrupt Vector with Priority Level 1
Name:
Offset:
Reset:
Property:
Bit
LVL1VEC
0x03
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
LVL1VEC[7:0]
Access
Reset
Bits 7:0 – LVL1VEC[7:0] Interrupt Vector with Priority Level 1
This bit field contains the number of the single vector with increased priority level 1 (LVL1).
If this bit field has the value 0x00, no vector has LVL1. Consequently, the LVL1 interrupt is disabled.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 121
ATtiny1616/3216
EVSYS - Event System
14.
EVSYS - Event System
14.1
Features
•
•
•
•
•
•
•
•
14.2
System for Direct Peripheral-to-Peripheral Signaling
Peripherals can Directly Produce, Use, and React to Peripheral Events
Short Response Time
Up to Six Parallel Event Channels Available; Four Asynchronous and Two Synchronous
Channels can be Configured to Have One Triggering Peripheral Action and Multiple Peripheral Users
Peripherals can Directly Trigger and React to Events from Other Peripherals
Events can be Sent and/or Received by Most Peripherals, and by Software
Works in Active mode and Standby Sleep mode
Overview
The Event System (EVSYS) enables direct peripheral-to-peripheral signaling. It allows a change in one
peripheral (the event generator) to trigger actions in other peripherals (the event users) through event
channels, without using the CPU. It is designed to provide short and predictable response times between
peripherals, allowing for autonomous peripheral control and interaction, and also for the synchronized
timing of actions in several peripheral modules. It is thus a powerful tool for reducing the complexity, size,
and the execution time of the software.
A change of the event generator's state is referred to as an event and usually corresponds to one of the
peripheral's interrupt conditions. Events can be directly forwarded to other peripherals using the
dedicated event routing network. The routing of each channel is configured in software, including event
generation and use.
Only one trigger from an event generator peripheral can be routed on each channel, but multiple
channels can use the same generator source. Multiple peripherals can use events from the same
channel.
A channel path can be either asynchronous or synchronous to the main clock. The mode must be
selected based on the requirements of the application.
The Event System can directly connect analog and digital converters, analog comparators, I/O port pins,
the real-time counter, timer/counters, and the configurable custom logic peripheral. Events can also be
generated from software and the peripheral clock.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 122
ATtiny1616/3216
EVSYS - Event System
14.2.1
Block Diagram
Figure 14-1. Block Diagram
Sync user x
Sync event channel ”k”
Sync event channel 0
Sync source 0
Sync source 1
Sync user 0
Sync source n
SYNCCH
SYNCSTROBE
..
.
..
.
..
.
Async source m
ASYNCCH
SYNCUSER
Async user y
Async user 0
Async event channel ”l”
Async event channel 0
Async source 0
Async source 1
To sync user
..
.
..
.
ASYNCSTROBE
To async user
ASYNCUSER
Figure 14-2. Example of Event Source, Generator, User, and Action
Event Generator
Event User
Timer/Counter
ADC
Compare Match
Over-/Underflow
|
Event
Routing
Network
Error
Channel Sweep
Single
Conversion
Event Action Selection
Event Source
Event Action
Note:
1. For an overview of peripherals supporting events, refer the block diagram of the device.
2. For a list of event generators, refer to the Channel n Generator Selection registers
(EVSYS.SYNCCH and EVSYS.ASYNCCH).
3. For a list of event users, refer to the User Channel n Input Selection registers (EVSYS.SYNCUSER
and EVSYS.ASYNCUSER).
Related Links
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 123
ATtiny1616/3216
EVSYS - Event System
14.5.4
14.5.3
14.5.6
14.5.5
14.2.2
SYNCCH
ASYNCCH
SYNCUSER
ASYNCUSER
Signal Description
Internal Event Signaling
The event signaling can happen either synchronously or asynchronously to the main clock (CLK_MAIN).
Depending on the underlying event, the event signal can be a pulse with a duration of one clock cycle, or
a level signal (similar to a status flag).
Event Output to Pin
Signal
Type
Description
EVOUT[2:0]
Digital Output
Event Output
Related Links
14.2.3.2 I/O Lines
10.2.1 Block Diagram - CLKCTRL
14.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 14-1. EVSYS System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORTMUX
Interrupts
No
-
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
14.2.3.1 Clocks
14.3.5 Debug Operation
14.2.3.1 Clocks
The EVSYS uses the peripheral clock for I/O registers and software events. When correctly set up, the
routing network can also be used in sleep modes without any clock. Software events will not work in
sleep modes where the peripheral clock is halted.
Related Links
10. CLKCTRL - Clock Controller
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 124
ATtiny1616/3216
EVSYS - Event System
14.2.3.2 I/O Lines
The EVSYS can output three event channels asynchronously on pins. The output signals are called
EVOUT[2:0].
1. Configure which event channel (one of SYNCCH[1:0] or ASYNCCH[3:0]) is output on which
EVOUTn bit by writing to EVSYS.ASYNCUSER10, EVSYS.ASYNCUSER9, or
EVSYS.ASYNCUSER8, respectively.
2. Optional: configure the pin properties using the port peripheral.
3. Enable the pin output by writing '1' to the respective EVOUTn bit in the Control A register of the
PORTMUX peripheral (PORTMUX.CTRLA).
Related Links
15. PORTMUX - Port Multiplexer
16. PORT - I/O Pin Configuration
14.5.5 ASYNCUSER
14.3
Functional Description
14.3.1
Initialization
Before enabling events within the device, the event users multiplexer and event channels must be
configured.
Related Links
14.3.2.1 Event User Multiplexer Setup
14.3.2.2 Event System Channel
14.3.2
Operation
14.3.2.1 Event User Multiplexer Setup
The event user multiplexer selects the channel for an event user. Each event user has one dedicated
event user multiplexer. Each multiplexer is connected to the supported event channel outputs and can be
configured to select one of these channels.
Event users, which support asynchronous events, also support synchronous events. There are also event
users that support only synchronous events.
The event user multiplexers are configured by writing to the corresponding registers:
• Event users supporting both synchronous and asynchronous events are configured by writing to the
respective asynchronous User Channel Input Selection n register (EVSYS.ASYNCUSERn).
• The users of synchronous-only events are configured by writing to the respective Synchronous User
Channel Input Selection n register (EVSYS.SYNCUSERn).
The default setup of all user multiplexers is OFF.
14.3.2.2 Event System Channel
An event channel can be connected to one of the event generators. Event channels support either
asynchronous generators or synchronous generators.
The source for each asynchronous event channel is configured by writing to the respective Asynchronous
Channel n Input Selection register (EVSYS.ASYNCCHn).
The source for each synchronous event channel is configured by writing to the respective Synchronous
Channel n Input Selection register (EVSYS.SYNCCHn).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 125
ATtiny1616/3216
EVSYS - Event System
14.3.2.3 Event Generators
Each event channel can receive the events from several event generators. For details on event
generation, refer to the documentation of the corresponding peripheral.
For each event channel, there are several possible event generators, only one of which can be selected
at a time. The event generator trigger is selected for each channel by writing to the respective channel
registers (EVSYS.ASYNCCHn, EVSYS.SYNCCHn). By default, the channels are not connected to any
event generator.
14.3.2.4 Software Event
In a software event, the CPU will “strobe” an event channel by inverting the current value for one system
clock cycle.
A software event is triggered on a channel by writing a '1' to the respective Strobe bit in the appropriate
Channel Strobe register:
• Software events on asynchronous channel l are initiated by writing a '1' to the ASYNCSTROBE[l] bit
in the Asynchronous Channel Strobe register (EVSYS.ASYNCSTROBE).
• Software events on synchronous channel k are initiated by writing a '1' to the SYNCSTROBE[k] bit in
the Synchronous Channel Strobe register (EVSYS.SYNCSTROBE).
Software events are no different to those produced by event generator peripherals with respect to event
users: when the bit is written to '1', an event will be generated on the respective channel, and received
and processed by the event user.
14.3.3
Interrupts
Not applicable.
14.3.4
Sleep Mode Operation
When configured, the Event System will work in all sleep modes. One exception is software events that
require a system clock.
14.3.5
Debug Operation
This peripheral is unaffected by entering Debug mode.
Related Links
33. UPDI - Unified Program and Debug Interface
14.3.6
Synchronization
Asynchronous events are synchronized and handled by the compatible event users. Event user
peripherals not compatible with asynchronous events can only be configured to listen to synchronous
event channels.
14.3.7
Configuration Change Protection
Not applicable.
Related Links
8.5.7.1 Sequence for Write Operation to Configuration Change Protected I/O Registers
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 126
ATtiny1616/3216
EVSYS - Event System
14.4
Register Summary - EVSYS
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
...
0x09
0x0A
0x0B
0x0C
...
0x11
0x12
...
0x1E
0x1F
...
0x21
0x22
0x23
ASYNCSTROBE
SYNCSTROBE
ASYNCCH0
ASYNCCH1
ASYNCCH2
ASYNCCH3
7:0
7:0
7:0
7:0
7:0
7:0
ASYNCSTROBE[7:0]
SYNCSTROBE[7:0]
ASYNCCH[7:0]
ASYNCCH[7:0]
ASYNCCH[7:0]
ASYNCCH[7:0]
7:0
7:0
SYNCCH[7:0]
SYNCCH[7:0]
ASYNCUSER0
7:0
ASYNCUSER[7:0]
ASYNCUSER12
7:0
ASYNCUSER[7:0]
7:0
7:0
SYNCUSER[7:0]
SYNCUSER[7:0]
14.5
Reserved
SYNCCH0
SYNCCH1
Reserved
Reserved
SYNCUSER0
SYNCUSER1
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 127
ATtiny1616/3216
EVSYS - Event System
14.5.1
Asynchronous Channel Strobe
Name:
Offset:
Reset:
Property:
Bit
ASYNCSTROBE
0x00
0x00
-
7
6
5
4
R/W
R/W
R/W
R/W
0
0
0
0
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
0
ASYNCSTROBE[7:0]
Access
Reset
Bits 7:0 – ASYNCSTROBE[7:0] Asynchronous Channel Strobe
If the Strobe register location is written, each event channel will be inverted for one system clock cycle
(i.e., a single event is generated).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 128
ATtiny1616/3216
EVSYS - Event System
14.5.2
Synchronous Channel Strobe
Name:
Offset:
Reset:
Property:
Bit
SYNCSTROBE
0x01
0x00
-
7
6
5
4
R/W
R/W
R/W
R/W
0
0
0
0
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
0
SYNCSTROBE[7:0]
Access
Reset
Bits 7:0 – SYNCSTROBE[7:0] Synchronous Channel Strobe
If the Strobe register location is written, each event channel will be inverted for one system clock cycle
(i.e., a single event is generated).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 129
ATtiny1616/3216
EVSYS - Event System
14.5.3
Asynchronous Channel n Generator Selection
Name:
Offset:
Reset:
Property:
Bit
ASYNCCH
0x02 + n*0x01 [n=0..3]
0x00
-
7
6
5
4
3
R/W
R/W
R/W
R/W
0
0
0
0
2
1
0
R/W
R/W
R/W
R/W
0
0
0
0
ASYNCCH[7:0]
Access
Reset
Bits 7:0 – ASYNCCH[7:0] Asynchronous Channel Generator Selection
Table 14-2. Asynchronous Channel Generator Selection
Value
ASYNCCH0
ASYNCCH1
ASYNCCH2
ASYNCCH3
0x00
OFF
OFF
OFF
OFF
0x01
CCL_LUT0
0x02
CCL_LUT1
0x03
AC0_OUT
0x04
TCD0_CMPBCLR
0x05
TCD0_CMPASET
0x06
TCD0_CMPBSET
0x07
TCD0_PROGEV
0x08
RTC_OVF
0x09
RTC_CMP
0x0A
PORTA_PIN0
PORTB_PIN0
PORTC_PIN0
PIT_DIV8192
0x0B
PORTA_PIN1
PORTB_PIN1
PORTC_PIN1
PIT_DIV4096
0x0C
PORTA_PIN2
PORTB_PIN2
PORTC_PIN2
PIT_DIV2048
0x0D
PORTA_PIN3
PORTB_PIN3
PORTC_PIN3
PIT_DIV1024
0x0E
PORTA_PIN4
PORTB_PIN4
PORTC_PIN4
PIT_DIV512
0x0F
PORTA_PIN5
PORTB_PIN5
PORTC_PIN5
PIT_DIV256
0x10
PORTA_PIN6
PORTB_PIN6
AC1_OUT
PIT_DIV128
0x11
PORTA_PIN7
PORTB_PIN7
AC2_OUT
PIT_DIV64
0x12
UPDI
AC1_OUT
-
AC1_OUT
0x13
AC1_OUT
AC2_OUT
-
AC2_OUT
0x14
AC2_OUT
-
-
-
Other
-
-
-
-
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 130
ATtiny1616/3216
EVSYS - Event System
Note: Not all pins of a port are actually available on devices with low pin counts. Check the Pinout
Diagram and/or the I/O Multiplexing table for details.
Related Links
4. Pinout
5. I/O Multiplexing and Considerations
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 131
ATtiny1616/3216
EVSYS - Event System
14.5.4
Synchronous Channel n Generator Selection
Name:
Offset:
Reset:
Property:
Bit
SYNCCH
0x0A + n*0x01 [n=0..1]
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
SYNCCH[7:0]
Access
Reset
Bits 7:0 – SYNCCH[7:0] Synchronous Channel Generator Selection
Table 14-3. Synchronous Channel Generator Selection
Value
SYNCCH0
SYNCCH1
0x00
OFF
0x01
TCB0
0x02
TCA0_OVF_LUNF
0x03
TCA0_HUNF
0x04
TCA0_CMP0
0x05
TCA0_CMP1
0x06
TCA0_CMP2
0x07
PORTC_PIN0
-
0x08
PORTC_PIN1
PORTB_PIN0
0x09
PORTC_PIN2
PORTB_PIN1
0x0A
PORTC_PIN3
PORTB_PIN2
0x0B
PORTC_PIN4
PORTB_PIN3
0x0C
PORTC_PIN5
PORTB_PIN4
0x0D
PORTA_PIN0
PORTB_PIN5
0x0E
PORTA_PIN1
PORTB_PIN6
0x0F
PORTA_PIN2
PORTB_PIN7
0x10
PORTA_PIN3
TCB1
0x11
PORTA_PIN4
-
0x12
PORTA_PIN5
-
0x13
PORTA_PIN6
-
0x14
PORTA_PIN7
-
0x15
TCB1
-
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 132
ATtiny1616/3216
EVSYS - Event System
...........continued
Value
SYNCCH0
SYNCCH1
Other
-
-
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 133
ATtiny1616/3216
EVSYS - Event System
14.5.5
Asynchronous User Channel n Input Selection
Name:
Offset:
Reset:
Property:
Bit
ASYNCUSER
0x12 + n*0x01 [n=0..12]
0x00
-
7
6
5
4
R/W
R/W
R/W
R/W
0
0
0
0
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
0
ASYNCUSER[7:0]
Access
Reset
Bits 7:0 – ASYNCUSER[7:0] Asynchronous User Channel Selection
Table 14-4. User Multiplexer Numbers
USERn
User Multiplexer
Description
n=0
TCB0
Timer/Counter B 0
n=1
ADC0
ADC 0
n=2
CCL_LUT0EV0
CCL LUT0 Event 0
n=3
CCL_LUT1EV0
CCL LUT1 Event 0
n=4
CCL_LUT0EV1
CCL LUT0 Event 1
n=5
CCL_LUT1EV1
CCL LUT1 Event 1
n=6
TCD0_EV0
Timer Counter D 0 Event 0
n=7
TCD0_EV1
Timer Counter D 0 Event 1
n=8
EVOUT0
Event OUT 0
n=9
EVOUT1
Event OUT 1
n=10
EVOUT2
Event OUT 2
n=11
TCB1
Timer/Counter B 1
n=12
ADC1
ADC 1
Value
0x0
0x1
0x2
0x3
0x4
0x5
0x6
Description
OFF
SYNCCH0
SYNCCH1
ASYNCCH0
ASYNCCH1
ASYNCCH2
ASYNCCH3
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 134
ATtiny1616/3216
EVSYS - Event System
14.5.6
Synchronous User Channel n Input Selection
Name:
Offset:
Reset:
Property:
Bit
SYNCUSER
0x22 + n*0x01 [n=0..1]
0x00
-
7
6
5
4
R/W
R/W
R/W
R/W
0
0
0
0
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
0
SYNCUSER[7:0]
Access
Reset
Bits 7:0 – SYNCUSER[7:0] Synchronous User Channel Selection
Table 14-5. User Multiplexer Numbers
USERn
User Multiplexer
Description
n=0
TCA0
Timer/Counter A
n=1
USART0
USART
Value
0x0
0x1
0x2
Name
OFF
SYNCCH0
SYNCCH1
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 135
ATtiny1616/3216
PORTMUX - Port Multiplexer
15.
PORTMUX - Port Multiplexer
15.1
Overview
The Port Multiplexer (PORTMUX) can either enable or disable functionality of pins, or change between
default and alternative pin positions. This depends on the actual pin and property and is described in
detail in the PORTMUX register map.
For available pins and functionalities, refer to the Multiplexed Signals table.
Related Links
5. I/O Multiplexing and Considerations
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 136
ATtiny1616/3216
PORTMUX - Port Multiplexer
15.2
Register Summary - PORTMUX
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
CTRLA
CTRLB
CTRLC
CTRLD
7:0
7:0
7:0
7:0
15.3
LUT1
TCA05
LUT0
TWI0
TCA04
TCA03
EVOUT2
SPI0
TCA02
EVOUT1
TCA01
TCB1
EVOUT0
USART0
TCA00
TCB0
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 137
ATtiny1616/3216
PORTMUX - Port Multiplexer
15.3.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
-
6
Access
Reset
5
4
LUT1
R/W
0
3
2
1
0
LUT0
EVOUT2
EVOUT1
EVOUT0
R/W
R/W
R/W
R/W
0
0
0
0
Bit 5 – LUT1 CCL LUT 1 output
Write this bit to '1' to select alternative pin location for CCL LUT 1.
Bit 4 – LUT0 CCL LUT 0 output
Write this bit to '1' to select alternative pin location for CCL LUT 0.
Bit 2 – EVOUT2 Event Output 2
Write this bit to '1' to enable event output 2.
Bit 1 – EVOUT1 Event Output 1
Write this bit to '1' to enable event output 1.
Bit 0 – EVOUT0 Event Output 0
Write this bit to '1' to enable event output 0.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 138
ATtiny1616/3216
PORTMUX - Port Multiplexer
15.3.2
Control B
Name:
Offset:
Reset:
Property:
Bit
7
CTRLB
0x01
0x00
-
6
Access
Reset
5
4
3
2
1
0
TWI0
SPI0
USART0
R/W
R/W
R/W
0
0
0
Bit 4 – TWI0 TWI 0 communication
Write this bit to '1' to select alternative communication pins for TWI 0.
Bit 2 – SPI0 SPI 0 communication
Write this bit to '1' to select alternative communication pins for SPI 0.
Bit 0 – USART0 USART 0 communication
Write this bit to '1' to select alternative communication pins for USART 0.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 139
ATtiny1616/3216
PORTMUX - Port Multiplexer
15.3.3
Control C
Name:
Offset:
Reset:
Property:
Bit
7
CTRLC
0x02
0x00
-
6
Access
Reset
5
4
3
2
1
0
TCA05
TCA04
TCA03
TCA02
TCA01
TCA00
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bit 5 – TCA05 TCA0 Waveform output 5
Write this bit to '1' to select alternative output pin for TCA0 waveform output 5 in Split mode.
Not applicable when TCA in normal mode.
Bit 4 – TCA04 TCA0 Waveform output 4
Write this bit to '1' to select alternative output pin for TCA0 waveform output 4 in Split mode.
Not applicable when TCA in normal mode.
Bit 3 – TCA03 TCA0 Waveform output 3
Write this bit to '1' to select alternative output pin for TCA0 waveform output 3 in Split mode.
Not applicable when TCA in normal mode.
Bit 2 – TCA02 TCA0 Waveform output 2
Write this bit to '1' to select alternative output pin for TCA0 waveform output 2.
In Split Mode, this bit controls output from low byte compare channel 2.
Bit 1 – TCA01 TCA0 Waveform output 1
Write this bit to '1' to select alternative output pin for TCA0 waveform output 1.
In Split mode, this bit controls output from low byte compare channel 1.
Bit 0 – TCA00 TCA0 Waveform output 0
Write this bit to '1' to select alternative output pin for TCA0 waveform output 0.
In Split mode, this bit controls output from low byte compare channel 0.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 140
ATtiny1616/3216
PORTMUX - Port Multiplexer
15.3.4
Control D
Name:
Offset:
Reset:
Property:
Bit
7
CTRLD
0x03
0x00
-
6
5
4
3
2
Access
Reset
1
0
TCB1
TCB0
R/W
R/W
0
0
Bit 1 – TCB1 TCB1 output
Write this bit to '1' to select alternative output pin for 16-bit timer/counter B 1.
Bit 0 – TCB0 TCB0 output
Write this bit to '1' to select alternative output pin for 16-bit timer/counter B 0.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 141
ATtiny1616/3216
PORT - I/O Pin Configuration
16.
PORT - I/O Pin Configuration
16.1
Features
• General Purpose Input and Output Pins with Individual Configuration
• Output Driver with Configurable Inverted I/O and Pull-up
• Input with Interrupts and Events:
– Sense both edges
– Sense rising edges
– Sense falling edges
– Sense low level
• Asynchronous Pin Change Sensing That Can Wake the Device From all Sleep Modes
• Efficient and Safe Access to Port Pins
– Hardware read-modify-write through dedicated toggle/clear/set registers
– Mapping of often-used PORT registers into bit-accessible I/O memory space (virtual ports)
16.2
Overview
The I/O pins of the device are controlled by instances of the Port Peripheral registers. This device has the
following instances of the I/O pin configuration (PORT): PORTA, PORTB, and PORTC.
Refer to the I/O multiplexing table to see which pins are controlled by what instance of port. The offsets of
the port instances and of the corresponding virtual port instances are listed in the Peripherals and
Architecture section.
Each of the port pins has a corresponding bit in the Data Direction (PORT.DIR) and Data Output Value
(PORT.OUT) registers to enable that pin as an output and to define the output state. For example, pin
PA3 is controlled by DIR[3] and OUT[3] of the PORTA instance.
The Data Input Value (PORT.IN) is set as the input value of a port pin with resynchronization to the main
clock. To reduce power consumption, these input synchronizers are not clocked if the Input Sense
Configuration bit field (ISC) in PORT.PINnCTRL is INPUT_DISABLE. The value of the pin can always be
read, whether the pin is configured as input or output.
The port supports synchronous and asynchronous input sensing with interrupts for selectable pin change
conditions. Asynchronous pin-change sensing means that a pin change can wake the device from all
sleep modes, including the modes where no clocks are running.
All pin functions are configurable individually per pin. The pins have hardware read-modify-write (RMW)
functionality for a safe and correct change of drive value and/or pull resistor configuration. The direction
of one port pin can be changed without unintentionally changing the direction of any other pin.
The port pin configuration controls input and output selection of other device functions.
Related Links
5. I/O Multiplexing and Considerations
7. Peripherals and Architecture
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 142
ATtiny1616/3216
PORT - I/O Pin Configuration
16.2.1
Block Diagram
Figure 16-1. PORT Block Diagram
Pullup Enable
Invert Enable
OUTn
Q
D
Pxn
OUT Override
R
DIRn
Q
D
DIR
Override
R
Interrupt
Interrupt
Generator
Input Disable
Input
Disable
Override
Synchronizer
INn
Synchronized
Input
Q
D Q
R
D
R
Digital Input /
Asynchronous Event
Analog Input/Output
16.2.2
Signal Description
Signal
Type
Description
Pxn
I/O pin
I/O pin n on PORTx
Related Links
5. I/O Multiplexing and Considerations
16.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 143
ATtiny1616/3216
PORT - I/O Pin Configuration
Table 16-1. PORT System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
No
-
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
No
-
Related Links
16.2.3.4 Events
16.2.3.1 Clocks
16.2.3.3 Interrupts
16.2.3.1 Clocks
This peripheral depends on the peripheral clock.
16.2.3.2 I/O Lines and Connections
Not applicable.
16.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
16.3.3 Interrupts
8.7.3 SREG
16.2.3.4 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
16.2.3.5 Debug Operation
This peripheral is unaffected by entering Debug mode.
16.3
Functional Description
16.3.1
Initialization
After Reset, all standard function device I/O pads are connected to the port with outputs tri-stated and
input buffers enabled, even if there is no clock running.
Power consumption can be reduced by disabling digital input buffers for all unused pins and for pins used
as analog inputs or outputs.
Specific pins, such as those used for connecting a debugger, may be configured differently, as required
by their special function.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 144
ATtiny1616/3216
PORT - I/O Pin Configuration
16.3.2
Operation
16.3.2.1 Basic Functions
Each I/O pin Pxn can be controlled by the registers in PORTx. Each pin group x has its own set of PORT
registers. The base address of the register set for pin n is at the byte address PORT + 0x10 + � . The
index within that register set is n.
To use pin number n as an output only, write bit n of the PORTx.DIR register to '1'. This can be done by
writing bit n in the PORTx.DIRSET register to '1', which will avoid disturbing the configuration of other pins
in that group. The nth bit in the PORTx.OUT register must be written to the desired output value.
Similarly, writing a PORTx.OUTSET bit to '1' will set the corresponding bit in the PORTx.OUT register to
'1'. Writing a bit in PORTx.OUTCLR to '1' will clear that bit in PORTx.OUT to zero. Writing a bit in
PORTx.OUTTGL or PORTx.IN to '1' will toggle that bit in PORTx.OUT.
To use pin n as an input, bit n in the PORTx.DIR register must be written to '0' to disable the output driver.
This can be done by writing bit n in the PORTx.DIRCLR register to '1', which will avoid disturbing the
configuration of other pins in that group. The input value can be read from bit n in register PORTx.IN as
long as the ISC bit is not set to INPUT_DISABLE.
Writing a bit to '1' in PORTx.DIRTGL will toggle that bit in PORTx.DIR and toggle the direction of the
corresponding pin.
16.3.2.2 Virtual Ports
The Virtual PORT registers map the most frequently used regular PORT registers into the bit-accessible
I/O space. Writing to the Virtual PORT registers has the same effect as writing to the regular registers, but
allows for memory-specific instructions, such as bit-manipulation instructions, which are not valid for the
extended I/O memory space where the regular PORT registers reside.
Table 16-2. Virtual Port Mapping
Regular PORT Register
Mapped to Virtual PORT Register
PORT.DIR
VPORT.DIR
PORT.OUT
VPORT.OUT
PORT.IN
VPORT.IN
PORT.INTFLAG
VPORT.INTFLAG
Related Links
16.6 Register Summary - VPORT
5. I/O Multiplexing and Considerations
7. Peripherals and Architecture
16.3.2.3 Pin Configuration
The Pin n Configuration register (PORT.PINnCTRL) is used to configure inverted I/O, pullup, and input
sensing of a pin.
All input and output on the respective pin n can be inverted by writing a '1' to the Inverted I/O Enable bit
(INVEN) in PORT.PINnCTRL.
Toggling the INVEN bit causes an edge on the pin, which can be detected by all peripherals using this
pin, and is seen by interrupts or events if enabled.
Pullup of pin n is enabled by writing a '1' to the Pullup Enable bit (PULLUPEN) in PORT.PINnCTRL.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 145
ATtiny1616/3216
PORT - I/O Pin Configuration
Changes of the signal on a pin can trigger an interrupt. The exact conditions are defined by writing to the
Input/Sense bit field (ISC) in PORT.PINnCTRL.
When setting or changing interrupt settings, take these points into account:
• If an INVEN bit is toggled in the same cycle as the interrupt setting, the edge caused by the inversion
toggling may not cause an interrupt request.
• If an input is disabled while synchronizing an interrupt, that interrupt may be requested on reenabling the input, even if it is re-enabled with a different interrupt setting.
• If the interrupt setting is changed while synchronizing an interrupt, that interrupt may not be
accepted.
• Only a few pins support full asynchronous interrupt detection, see I/O Multiplexing and
Considerations. These limitations apply for waking the system from sleep:
Interrupt Type
Fully Asynchronous Pins
Other Pins
BOTHEDGES
Will wake the system
Will wake the system
RISING
Will wake the system
Will not wake the system
FALLING
Will wake the system
Will not wake the system
LEVEL
Will wake the system
Will wake the system
Related Links
5. I/O Multiplexing and Considerations
16.3.3
Interrupts
Table 16-3. Available Interrupt Vectors and Sources
Offset Name
0x00
Vector Description
Conditions
PORTx PORT A, B, C interrupt INTn in PORT.INTFLAGS is raised as configured by ISC bit in
PORT.PINnCTRL.
Each port pin n can be configured as an interrupt source. Each interrupt can be individually enabled or
disabled by writing to ISC in PORT.PINCTRL.
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt request is generated when the corresponding interrupt is enabled and the interrupt flag is set.
The interrupt request remains active until the interrupt flag is cleared. See the peripheral's INTFLAGS
register for details on how to clear interrupt flags.
Asynchronous Sensing Pin Properties
Table 16-4. Behavior Comparison of Fully/Partly Asynchronous Sense Pin
Property
Synchronous or Partly Asynchronous Sense
Support
Minimum pulse-width Minimum one system clock cycle
to trigger interrupt
© 2019 Microchip Technology Inc.
Preliminary Datasheet
Full Asynchronous Sense
Support
Less than a system clock
cycle
40001997C-page 146
ATtiny1616/3216
PORT - I/O Pin Configuration
...........continued
Property
Synchronous or Partly Asynchronous Sense
Support
Full Asynchronous Sense
Support
Waking the device
from sleep
From all interrupt sense configurations from sleep From all interrupt sense
modes with the main clock running. Only from
configurations from all sleep
BOTHEDGES or LEVEL interrupt sense
modes
configuration from sleep modes with the main
clock stopped.
Interrupt 'dead time'
No new interrupt for three cycles after the
previous
No limitation
Minimum wake-up
pulse length
Value on pad must be kept until the system clock
has restarted
No limitation
Related Links
8. AVR CPU
8.7.3 SREG
16.3.4
Events
All PORT pins are asynchronous event system generators. PORT has as many event generators as there
are PORT pins in the device. Each event system output from PORT is the value present on the
corresponding pin if the digital input driver is enabled. If a pin input driver is disabled, the corresponding
event system output is zero.
PORT has no event inputs.
16.3.5
Sleep Mode Operation
With the exception of interrupts and input synchronization, all pin configurations are independent of the
Sleep mode. Peripherals connected to the ports can be affected by Sleep modes, described in the
respective peripherals' documentation.
The port peripheral will always use the main clock. Input synchronization will halt when this clock stops.
16.3.6
Synchronization
Not applicable.
16.3.7
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 147
ATtiny1616/3216
PORT - I/O Pin Configuration
16.4
Register Summary - PORT
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
...
0x0F
0x10
0x11
0x12
0x13
0x14
0x15
0x16
0x17
DIR
DIRSET
DIRCLR
DIRTGL
OUT
OUTSET
OUTCLR
OUTTGL
IN
INTFLAGS
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
16.5
DIR[7:0]
DIRSET[7:0]
DIRCLR[7:0]
DIRTGL[7:0]
OUT[7:0]
OUTSET[7:0]
OUTCLR[7:0]
OUTTGL[7:0]
IN[7:0]
INT[7:0]
Reserved
PIN0CTRL
PIN1CTRL
PIN2CTRL
PIN3CTRL
PIN4CTRL
PIN5CTRL
PIN6CTRL
PIN7CTRL
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
INVEN
INVEN
INVEN
INVEN
INVEN
INVEN
INVEN
INVEN
PULLUPEN
PULLUPEN
PULLUPEN
PULLUPEN
PULLUPEN
PULLUPEN
PULLUPEN
PULLUPEN
ISC[2:0]
ISC[2:0]
ISC[2:0]
ISC[2:0]
ISC[2:0]
ISC[2:0]
ISC[2:0]
ISC[2:0]
Register Description - Ports
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 148
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.1
Data Direction
Name:
Offset:
Reset:
Property:
Bit
DIR
0x00
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DIR[7:0]
Access
Reset
Bits 7:0 – DIR[7:0] Data Direction
This bit field selects the data direction for the individual pins n of the port.
Writing a '1' to PORT.DIR[n] configures and enables pin n as an output pin.
Writing a '0' to PORT.DIR[n] configures pin n as an input pin. It can be configured by writing to the ISC bit
in PORT.PINnCTRL.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 149
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.2
Data Direction Set
Name:
Offset:
Reset:
Property:
Bit
DIRSET
0x01
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DIRSET[7:0]
Access
Reset
Bits 7:0 – DIRSET[7:0] Data Direction Set
This bit field can be used instead of a read-modify-write to set individual pins as output.
Writing a '1' to DIRSET[n] will set the corresponding PORT.DIR[n] bit.
Reading this bit field will always return the value of PORT.DIR.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 150
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.3
Data Direction Clear
Name:
Offset:
Reset:
Property:
Bit
DIRCLR
0x02
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DIRCLR[7:0]
Access
Reset
Bits 7:0 – DIRCLR[7:0] Data Direction Clear
This register can be used instead of a read-modify-write to configure individual pins as input.
Writing a '1' to DIRCLR[n] will clear the corresponding bit in PORT.DIR.
Reading this bit field will always return the value of PORT.DIR.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 151
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.4
Data Direction Toggle
Name:
Offset:
Reset:
Property:
Bit
DIRTGL
0x03
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DIRTGL[7:0]
Access
Reset
Bits 7:0 – DIRTGL[7:0] Data Direction Toggle
This bit field can be used instead of a read-modify-write to toggle the direction of individual pins.
Writing a '1' to DIRTGL[n] will toggle the corresponding bit in PORT.DIR.
Reading this bit field will always return the value of PORT.DIR.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 152
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.5
Output Value
Name:
Offset:
Reset:
Property:
Bit
OUT
0x04
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
OUT[7:0]
Access
Reset
Bits 7:0 – OUT[7:0] Output Value
This bit field defines the data output value for the individual pins n of the port.
If OUT[n] is written to '1', pin n is driven high.
If OUT[n] is written to '0', pin n is driven low.
In order to have any effect, the pin direction must be configured as output.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 153
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.6
Output Value Set
Name:
Offset:
Reset:
Property:
Bit
OUTSET
0x05
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
OUTSET[7:0]
Access
Reset
Bits 7:0 – OUTSET[7:0] Output Value Set
This bit field can be used instead of a read-modify-write to set the output value of individual pins to '1'.
Writing a '1' to OUTSET[n] will set the corresponding bit in PORT.OUT.
Reading this bit field will always return the value of PORT.OUT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 154
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.7
Output Value Clear
Name:
Offset:
Reset:
Property:
Bit
OUTCLR
0x06
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
OUTCLR[7:0]
Access
Reset
Bits 7:0 – OUTCLR[7:0] Output Value Clear
This register can be used instead of a read-modify-write to clear the output value of individual pins to '0'.
Writing a '1' to OUTCLR[n] will clear the corresponding bit in PORT.OUT.
Reading this bit field will always return the value of PORT.OUT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 155
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.8
Output Value Toggle
Name:
Offset:
Reset:
Property:
Bit
OUTTGL
0x07
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
OUTTGL[7:0]
Access
Reset
Bits 7:0 – OUTTGL[7:0] Output Value Toggle
This register can be used instead of a read-modify-write to toggle the output value of individual pins.
Writing a '1' to OUTTGL[n] will toggle the corresponding bit in PORT.OUT.
Reading this bit field will always return the value of PORT.OUT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 156
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.9
Input Value
Name:
Offset:
Reset:
Property:
Bit
IN
0x08
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
IN[7:0]
Access
Reset
Bits 7:0 – IN[7:0] Input Value
This register shows the value present on the pins if the digital input driver is enabled. IN[n] shows the
value of pin n of the port. The input is not sampled and cannot be read if the digital input buffers are
disabled.
Writing to a bit of PORT.IN will toggle the corresponding bit in PORT.OUT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 157
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.10 Interrupt Flags
Name:
Offset:
Reset:
Property:
Bit
INTFLAGS
0x09
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
INT[7:0]
Access
Reset
Bits 7:0 – INT[7:0] Interrupt Pin Flag
The INT Flag is set when a pin change/state matches the pin's input sense configuration.
Writing a '1' to a flag's bit location will clear the flag.
For enabling and executing the interrupt, refer to ISC bit description in PORT.PINnCTRL.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 158
ATtiny1616/3216
PORT - I/O Pin Configuration
16.5.11 Pin n Control
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
PINCTRL
0x10 + n*0x01 [n=0..7]
0x00
-
6
5
4
3
2
1
0
INVEN
PULLUPEN
R/W
R/W
R/W
ISC[2:0]
R/W
R/W
0
0
0
0
0
Bit 7 – INVEN Inverted I/O Enable
Value
Description
0
I/O on pin n not inverted
1
I/O on pin n inverted
Bit 3 – PULLUPEN Pullup Enable
Value
Description
0
Pullup disabled for pin n
1
Pullup enabled for pin n
Bits 2:0 – ISC[2:0] Input/Sense Configuration
These bits configure the input and sense configuration of pin n. The sense configuration determines how
a port interrupt can be triggered. If the input buffer is disabled, the input cannot be read in the IN register.
Value
Name
Description
0x0
INTDISABLE
Interrupt disabled but input buffer enabled
0x1
BOTHEDGES
Sense both edges
0x2
RISING
Sense rising edge
0x3
FALLING
Sense falling edge
0x4
INPUT_DISABLE
Digital input buffer disabled
0x5
LEVEL
Sense low level
other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 159
ATtiny1616/3216
PORT - I/O Pin Configuration
16.6
Register Summary - VPORT
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
DIR
OUT
IN
INTFLAGS
7:0
7:0
7:0
7:0
16.7
DIR[7:0]
OUT[7:0]
IN[7:0]
INT[7:0]
Register Description - Virtual Ports
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 160
ATtiny1616/3216
PORT - I/O Pin Configuration
16.7.1
Data Direction
Name:
Offset:
Reset:
Property:
DIR
0x00
0x00
-
Writing to the Virtual PORT registers has the same effect as writing to the regular registers, but allows for
memory-specific instructions, such as bit-manipulation instructions, which are not valid for the extended
I/O memory space where the regular PORT registers reside.
Bit
7
6
5
4
3
2
1
0
DIR[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – DIR[7:0] Data Direction
This bit field selects the data direction for the individual pins in the port.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 161
ATtiny1616/3216
PORT - I/O Pin Configuration
16.7.2
Output Value
Name:
Offset:
Reset:
Property:
OUT
0x01
0x00
-
Writing to the Virtual PORT registers has the same effect as writing to the regular registers, but allows for
memory-specific instructions, such as bit-manipulation instructions, which are not valid for the extended
I/O memory space where the regular PORT registers reside.
Bit
7
6
5
4
3
2
1
0
OUT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – OUT[7:0] Output Value
This bit field selects the data output value for the individual pins in the port.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 162
ATtiny1616/3216
PORT - I/O Pin Configuration
16.7.3
Input Value
Name:
Offset:
Reset:
Property:
IN
0x02
0x00
-
Writing to the Virtual PORT registers has the same effect as writing to the regular registers, but allows for
memory-specific instructions, such as bit-manipulation instructions, which are not valid for the extended
I/O memory space where the regular PORT registers reside.
Bit
7
6
5
4
3
2
1
0
IN[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – IN[7:0] Input Value
This bit field holds the value present on the pins if the digital input buffer is enabled.
Writing to a bit of VPORT.IN will toggle the corresponding bit in VPORT.OUT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 163
ATtiny1616/3216
PORT - I/O Pin Configuration
16.7.4
Interrupt Flag
Name:
Offset:
Reset:
Property:
INTFLAGS
0x03
0x00
-
Writing to the Virtual PORT registers has the same effect as writing to the regular registers, but allows for
memory-specific instructions, such as bit-manipulation instructions, which are not valid for the extended
I/O memory space where the regular PORT registers reside.
Bit
7
6
5
4
3
2
1
0
INT[7:0]
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bits 7:0 – INT[7:0] Interrupt Pin Flag
The INT flag is set when a pin change/state matches the pin's input sense configuration, and the pin is
configured as source for port interrupt.
Writing a '1' to this flag's bit location will clear the flag.
For enabling and executing the interrupt, refer to PORT_PINnCTRL.ISC.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 164
ATtiny1616/3216
BOD - Brown-out Detector
17.
BOD - Brown-out Detector
17.1
Features
• Brown-out Detection monitors the power supply to avoid operation below a programmable level
• There are three modes:
– Enabled
– Sampled
– Disabled
• Separate selection of mode for Active and Sleep modes
• Voltage Level Monitor (VLM) with Interrupt
• Programmable VLM Level Relative to the BOD Level
17.2
Overview
The Brown-out Detector (BOD) peripheral monitors the power supply and compares the voltage with two
programmable threshold levels: The brown-out threshold level defines when to generate a Reset. A
Voltage Level Monitor (VLM) monitors the power supply and compares it to a threshold higher than the
BOD threshold. The VLM can then generate an interrupt request as an "early warning" when the supply
voltage is about to drop below the VLM threshold. The VLM threshold level is expressed as a percentage
above the BOD threshold level.
The BOD is mainly controlled by fuses. The mode used in Standby Sleep mode and Power-Down Sleep
mode can be altered in normal program execution. The VLM part of the BOD is controlled by I/O registers
as well.
When activated, the BOD can operate in Enabled mode, where the BOD is continuously active, and in
Sampled mode, where the BOD is activated briefly at a given period to check the supply voltage level.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 165
ATtiny1616/3216
BOD - Brown-out Detector
17.2.1
Block Diagram
Figure 17-1. BOD Block Diagram
VDD
BOD Level
and
Calibration
-
Brown-out
Detection
+
Bandgap
VLM Interrupt Level
Bandgap
17.2.2
+
VLM Interrupt
Detection
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 17-1. BOD System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
No
-
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
17.2.2.1 Clocks
17.2.2.5 Debug Operation
17.2.2.3 Interrupts
17.2.2.4 Events
17.2.2.1 Clocks
The BOD uses the 32 KHz oscillator (OSCULP32K) as clock source for CLK_BOD.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 166
ATtiny1616/3216
BOD - Brown-out Detector
17.2.2.2 I/O Lines and Connections
Not applicable.
17.2.2.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
17.3.2 Interrupts
17.2.2.4 Events
Not applicable.
17.2.2.5 Debug Operation
This peripheral is unaffected by entering Debug mode.
The VLM interrupt will not be executed if the CPU is halted in Debug mode.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
17.3
Functional Description
17.3.1
Initialization
The BOD settings are loaded from fuses during Reset. The BOD level and operating mode in Active and
Idle Sleep mode are set by fuses and cannot be changed by the CPU. The operating mode in Standby
and Power-Down Sleep mode is loaded from fuses and can be changed by software.
The Voltage Level Monitor function can be enabled by writing a '1' to the VLM Interrupt Enable bit
(VLMIE) in the Interrupt Control register (BOD.INTCTRL). The VLM interrupt is configured by writing the
VLM Configuration bits (VLMCFG) in BOD.INTCTRL. An interrupt is requested when the supply voltage
crosses the VLM threshold either from above, from below, or from any direction.
The VLM functionality will follow the BOD mode. If the BOD is turned OFF, the VLM will not be enabled,
even if the VLMIE is '1'. If the BOD is using Sampled mode, the VLM will also be sampled. When enabling
VLM interrupt, the interrupt flag will always be set if VLMCFG equals 0x2 and may be set if VLMCFG is
configured to 0x0 or 0x1.
The VLM threshold is defined by writing the VLM Level bits (VLMLVL) in the Control A register
(BOD.VLMCTRLA).
If the BOD/VLM is enabled in Sampled mode, only VLMCFG=0x1 (crossing threshold from above) in
BOD.INTCTRL will trigger an interrupt.
17.3.2
Interrupts
Table 17-2. Available Interrupt Vectors and Sources
Offset Name Vector Description
0x00
VLM
Conditions
Voltage Level Monitor Supply voltage crossing the VLM threshold as configured by
VLMCFG in BOD.INTCTRL
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 167
ATtiny1616/3216
BOD - Brown-out Detector
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding enable bit in the peripheral's
Interrupt Control register (peripheral.INTCTRL).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
Related Links
8. AVR CPU
8.7.3 SREG
17.3.3
Sleep Mode Operation
There are two separate fuses defining the BOD configuration in different sleep modes; One fuse defines
the mode used in Active mode and Idle Sleep mode (ACTIVE in FUSE.BODCFG) and is written to the
ACTIVE bits in the Control A register (BOD.CTRLA). The second fuse (SLEEP in FUSE.BODCFG)
selects the mode used in Standby Sleep mode and Power-Down Sleep mode and is loaded into the
SLEEP bits in the Control A register (BOD.CTRLA).
The operating mode in Active mode and Idle Sleep mode (i.e., ACTIVE in BOD.CTRLA) cannot be
altered by software. The operating mode in Standby Sleep mode and Power-Down Sleep mode can be
altered by writing to the SLEEP bits in the Control A register (BOD.CTRLA).
When the device is going into Standby Sleep mode or Power-Down Sleep mode, the BOD will change
operation mode as defined by SLEEP in BOD.CTRLA. When the device is waking up from Standby or
Power-Down Sleep mode, the BOD will operate in the mode defined by the ACTIVE bit field in
BOD.CTRLA.
17.3.4
Synchronization
Not applicable.
17.3.5
Configuration Change Protection
This peripheral has registers that are under Configuration Change Protection (CCP). In order to write to
these, a certain key must be written to the CPU.CCP register first, followed by a write access to the
protected bits within four CPU instructions.
Attempting to write to a protected register without following the appropriate CCP unlock sequence leaves
the protected register unchanged.
The following registers are under CCP:
Table 17-3. Registers Under Configuration Change Protection
Register
Key
SLEEP in BOD.CTRLA
IOREG
Related Links
8.5.7.1 Sequence for Write Operation to Configuration Change Protected I/O Registers
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 168
ATtiny1616/3216
BOD - Brown-out Detector
17.4
Register Summary - BOD
Offset
Name
Bit Pos.
0x00
0x01
0x02
...
0x07
0x08
0x09
0x0A
0x0B
CTRLA
CTRLB
7:0
7:0
17.5
SAMPFREQ
ACTIVE[1:0]
SLEEP[1:0]
LVL[2:0]
Reserved
VLMCTRLA
INTCTRL
INTFLAGS
STATUS
7:0
7:0
7:0
7:0
VLMCFG[1:0]
VLMLVL[1:0]
VLMIE
VLMIF
VLMS
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 169
ATtiny1616/3216
BOD - Brown-out Detector
17.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
Loaded from fuse
Configuration Change Protection
6
5
4
3
SAMPFREQ
2
1
ACTIVE[1:0]
0
SLEEP[1:0]
Access
R
R
R
R/W
R/W
Reset
x
x
x
x
x
Bit 4 – SAMPFREQ Sample Frequency
This bit selects the BOD sample frequency.
The Reset value is loaded from the SAMPFREQ bit in FUSE.BODCFG. This bit is under Configuration
Change Protection (CCP).
Value
Description
0x0
Sample frequency is 1 kHz
0x1
Sample frequency is 125 Hz
Bits 3:2 – ACTIVE[1:0] Active
These bits select the BOD operation mode when the device is in Active or Idle mode.
The Reset value is loaded from the ACTIVE bits in FUSE.BODCFG.
Value
Description
0x0
Disabled
0x1
Enabled
0x2
Sampled
0x3
Enabled with wake-up halted until BOD is ready
Bits 1:0 – SLEEP[1:0] Sleep
These bits select the BOD operation mode when the device is in Standby or Power-Down Sleep mode.
The Reset value is loaded from the SLEEP bits in FUSE.BODCFG.
These bits are under Configuration Change Protection (CCP).
Value
Description
0x0
Disabled
0x1
Enabled
0x2
Sampled
0x3
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 170
ATtiny1616/3216
BOD - Brown-out Detector
17.5.2
Control B
Name:
Offset:
Reset:
Property:
CTRLB
0x01
Loaded from fuse
-
Bit
7
6
5
4
3
2
1
0
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
x
x
x
LVL[2:0]
Bits 2:0 – LVL[2:0] BOD Level
These bits select the BOD threshold level.
The Reset value is loaded from the BOD Level bits (LVL) in the BOD Configuration Fuse
(FUSE.BODCFG).
Value
Name
Description
0x0
BODLEVEL0
1.8V
0x2
BODLEVEL2
2.6V
0x7
BODLEVEL7
4.2V
Note:
• Values in the description are typical values.
• Refer to the BOD and POR Characteristics in Electrical Characteristics for maximum and minimum
values.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 171
ATtiny1616/3216
BOD - Brown-out Detector
17.5.3
VLM Control A
Name:
Offset:
Reset:
Property:
Bit
7
VLMCTRLA
0x08
0x00
-
6
5
4
3
2
1
0
VLMLVL[1:0]
Access
Reset
R/W
R/W
0
0
Bits 1:0 – VLMLVL[1:0] VLM Level
These bits select the VLM threshold relative to the BOD threshold (LVL in BOD.CTRLB).
Value
Description
0x0
VLM threshold 5% above BOD threshold
0x1
VLM threshold 15% above BOD threshold
0x2
VLM threshold 25% above BOD threshold
other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 172
ATtiny1616/3216
BOD - Brown-out Detector
17.5.4
Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
INTCTRL
0x09
0x00
-
6
5
4
3
2
1
VLMCFG[1:0]
Access
Reset
0
VLMIE
R/W
R/W
R/W
0
0
0
Bits 2:1 – VLMCFG[1:0] VLM Configuration
These bits select which incidents will trigger a VLM interrupt.
Value
Description
0x0
Voltage crosses VLM threshold from above
0x1
Voltage crosses VLM threshold from below
0x2
Either direction is triggering an interrupt request
Other
Reserved
Bit 0 – VLMIE VLM Interrupt Enable
Writing a '1' to this bit enables the VLM interrupt.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 173
ATtiny1616/3216
BOD - Brown-out Detector
17.5.5
VLM Interrupt Flags
Name:
Offset:
Reset:
Property:
Bit
7
INTFLAGS
0x0A
0x00
-
6
5
4
3
2
1
0
VLMIF
Access
R/W
Reset
0
Bit 0 – VLMIF VLM Interrupt Flag
This flag is set when a trigger from the VLM is given, as configured by the VLMCFG bit in the
BOD.INTCTRL register. The flag is only updated when the BOD is enabled.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 174
ATtiny1616/3216
BOD - Brown-out Detector
17.5.6
VLM Status
Name:
Offset:
Reset:
Property:
Bit
7
STATUS
0x0B
0x00
-
6
5
4
3
2
1
0
VLMS
Access
R
Reset
0
Bit 0 – VLMS VLM Status
This bit is only valid when the BOD is enabled.
Value
Description
0
The voltage is above the VLM threshold level
1
The voltage is below the VLM threshold level
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 175
ATtiny1616/3216
VREF - Voltage Reference
18.
VREF - Voltage Reference
18.1
Features
• Programmable Voltage Reference Sources:
– One for each ADC peripheral
– One for each AC and DAC peripheral
• Each Reference Source Supports Five Different Voltages:
– 0.55V
– 1.1V
– 1.5V
– 2.5V
– 4.3V
18.2
Overview
The Voltage Reference (VREF) peripheral provides control registers for the voltage reference sources
used by several peripherals. The user can select the reference voltages for the ADC0 by writing to the
ADC0 Reference Select bit field (ADC0REFSEL) in the Control A register (VREF.CTRLA), and for both
AC0 and DAC0 by writing to the DAC0 and AC0 Reference Select bit field DAC0REFSEL in
VREF.CTRLA.
A voltage reference source is enabled automatically when requested by a peripheral. The user can
enable the reference voltage sources (and thus, override the automatic disabling of unused sources) by
writing to the respective Force Enable bit (ADC0REFEN, DAC0REFEN) in the Control B register
(VREF.CTRLB). This may be desirable to decrease start-up time, at the cost of increased power
consumption.
18.2.1
Block Diagram
Figure 18-1. VREF Block Diagram
Reference reque st
Reference enable
Reference se lect
Bandgap
Reference
Gen erator
Ban dgap
ena ble
18.3
0.55V
1.1V
1.5V
2.5V
4.3V
BUF
Inte rnal
Reference
Functional Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 176
ATtiny1616/3216
VREF - Voltage Reference
18.3.1
Initialization
The default configuration will enable the respective source when the ADC0, AC0, or DAC0 is requesting a
reference voltage. The default reference voltages are 0.55V but can be configured by writing to the
respective Reference Select bit field (ADC0REFSEL, DAC0REFSEL) in the Control A register
(VREF.CTRLA).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 177
ATtiny1616/3216
VREF - Voltage Reference
18.4
Register Summary - VREF
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
CTRLA
CTRLB
CTRLC
CTRLD
7:0
7:0
7:0
7:0
18.5
ADC0REFSEL[2:0]
DAC2REFEN ADC1REFEN DAC1REFEN
ADC1REFSEL[2:0]
DAC0REFSEL[2:0]
ADC0REFEN DAC0REFEN
DAC1REFSEL[2:0]
DAC2REFSEL[2:0]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 178
ATtiny1616/3216
VREF - Voltage Reference
18.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
-
6
5
4
3
2
ADC0REFSEL[2:0]
Access
Reset
1
0
DAC0REFSEL[2:0]
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bits 6:4 – ADC0REFSEL[2:0] ADC0 Reference Select
These bits select the reference voltage for the ADC0.
Value
Description
0x0
0.55V
0x1
1.1V
0x2
2.5V
0x3
4.3V
0x4
1.5V
other
Reserved
Bits 2:0 – DAC0REFSEL[2:0] DAC0 and AC0 Reference Select
These bits select the reference voltage for the DAC0 and AC0.
Value
Description
0x0
0.55V
0x1
1.1V
0x2
2.5V
0x3
4.3V
0x4
1.5V
other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 179
ATtiny1616/3216
VREF - Voltage Reference
18.5.2
Control B
Name:
Offset:
Reset:
Property:
Bit
7
CTRLB
0x01
0x00
-
6
Access
Reset
5
4
3
DAC2REFEN
ADC1REFEN
R/W
R/W
0
0
2
1
0
DAC1REFEN
ADC0REFEN
DAC0REFEN
R/W
R/W
R/W
0
0
0
Bit 5 – DAC2REFEN DAC2 and AC2 Reference Force Enable
Writing a '1' to this bit forces the voltage reference for the DAC2 and AC2 to be running, even if it is not
requested.
Writing a '0' to this bit allows to automatic enable/disable the reference source when not requested.
Bit 4 – ADC1REFEN ADC1 Reference Force Enable
Writing a '1' to this bit forces the voltage reference for the ADC1 to be running, even if it is not requested.
Writing a '0' to this bit allows to automatic enable/disable the reference source when not requested.
Note: Do not force the internal reference enabled (ADCnREFEN=1 in VREF.CTRLB) when the ADC is
using the external reference (REFSEL bits in ADC.CTRLC).
Bit 3 – DAC1REFEN DAC1 and AC1 Reference Force Enable
Writing a '1' to this bit forces the voltage reference for the DAC1 and AC1 to be running, even if it is not
requested.
Writing a '0' to this bit allows to automatic enable/disable the reference source when not requested.
Bit 1 – ADC0REFEN ADC0 Reference Force Enable
Writing a '1' to this bit forces the voltage reference for the ADC0 to be running, even if it is not requested.
Writing a '0' to this bit allows automatic enable/disable of the reference source by the peripheral.
Note: Do not force the internal reference enabled (ADCnREFEN=1 in VREF.CTRLB) when the ADC is
using the external reference (REFSEL bits in ADC.CTRLC).
Bit 0 – DAC0REFEN DAC0 and AC0 Reference Force Enable
Writing a '1' to this bit forces the voltage reference for the DAC0 and AC0 to be running, even if it is not
requested.
Writing a '0' to this bit allows automatic enable/disable of the reference source by the peripheral.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 180
ATtiny1616/3216
VREF - Voltage Reference
18.5.3
Control C
Name:
Offset:
Reset:
Property:
Bit
7
CTRLC
0x02
0x00
-
6
5
4
3
2
ADC1REFSEL[2:0]
Access
Reset
1
0
DAC1REFSEL[2:0]
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bits 6:4 – ADC1REFSEL[2:0] ADC1 Reference Select
These bits select the reference voltage for the ADC1.
Value
Description
0x0
0.55V
0x1
1.1V
0x2
2.5V
0x3
4.3V
0x4
1.5V
other
Reserved
Bits 2:0 – DAC1REFSEL[2:0] DAC1 and AC1 Reference Select
These bits select reference voltage for the DAC1 and AC1.
Value
Description
0x0
0.55V
0x1
1.1V
0x2
2.5V
0x3
4.3V
0x4
1.5V
other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 181
ATtiny1616/3216
VREF - Voltage Reference
18.5.4
Control D
Name:
Offset:
Reset:
Property:
Bit
7
CTRLD
0x03
0x00
-
6
5
4
3
2
1
0
DAC2REFSEL[2:0]
Access
Reset
R/W
R/W
R/W
0
0
0
Bits 2:0 – DAC2REFSEL[2:0] DAC2 and AC2 Reference Select
These bits select reference voltage for the DAC2 and AC2.
Value
Description
0x0
0.55V
0x1
1.1V
0x2
2.5V
0x3
4.3V
0x4
1.5V
other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 182
ATtiny1616/3216
WDT - Watchdog Timer
19.
WDT - Watchdog Timer
19.1
Features
•
•
•
•
•
Issues a System Reset if the Watchdog Timer is not Cleared Before its Time-out Period
Operating Asynchronously from System Clock Using an Independent Oscillator
Using the 1 KHz Output of the 32 KHz Ultra Low-Power Oscillator (OSCULP32K)
11 Selectable Time-out Periods, from 8 ms to 8s
Two Operation modes:
– Normal mode
– Window mode
• Configuration Lock to Prevent Unwanted Changes
• Closed Period Timer Activation After First WDT Instruction for Easy Setup
19.2
Overview
The Watchdog Timer (WDT) is a system function for monitoring correct program operation. It allows the
system to recover from situations such as runaway or deadlocked code, by issuing a Reset. When
enabled, the WDT is a constantly running timer with a predefined time-out period. If the WDT is not reset
within the time-out period, it will issue a system Reset. The WDT is reset by executing the WDR (Watchdog
Timer Reset) instruction in software.
The WDT has two modes of operation; Normal mode and Window mode. The settings in the Control A
register (WDT.CTRLA) determine the mode of operation.
A Window mode defines a time slot or "window" inside the time-out period during which the WDT must be
reset. If the WDT is reset outside this window, either too early or too late, a system Reset will be issued.
Compared to the Normal mode, the Window mode can catch situations where a code error causes
constant WDR execution.
When enabled, the WDT will run in Active mode and all Sleep modes. It is asynchronous (i.e., running
from a CPU independent clock source). For this reason, it will continue to operate and be able to issue a
system Reset even if the main clock fails.
The CCP mechanism ensures that the WDT settings cannot be changed by accident. For increased
safety, a configuration for locking the WDT settings is available.
Related Links
8.5.7 Configuration Change Protection (CCP)
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 183
ATtiny1616/3216
WDT - Watchdog Timer
19.2.1
Block Diagram
Figure 19-1. WDT Block Diagram
"Inside closed window"
CTRLA
WINDOW
CLK_WDT
"Enable
open window
and clear count"
=
COUNT
=
PERIOD
System
Reset
CTRLA
WDR
(instruction)
19.2.2
Signal Description
Not applicable.
19.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 19-1. WDT System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
No
-
Interrupts
No
-
Events
No
-
Debug
Yes
UPDI
Related Links
19.2.3.1 Clocks
19.2.3.5 Debug Operation
19.2.3.1 Clocks
A 1 KHz Oscillator Clock (CLK_WDT_OSC) is sourced from the internal Ultra Low-Power Oscillator,
OSCULP32K. Due to the ultra low-power design, the oscillator is not very accurate, and so the exact
time-out period may vary from device to device. This variation must be kept in mind when designing
software that uses the WDT to ensure that the time-out periods used are valid for all devices.
The Counter Clock CLK_WDT_OSC is asynchronous to the system clock. Due to this asynchronicity,
writing to the WDT Control register will require synchronization between the clock domains.
19.2.3.2 I/O Lines and Connections
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 184
ATtiny1616/3216
WDT - Watchdog Timer
19.2.3.3 Interrupts
Not applicable.
19.2.3.4 Events
Not applicable.
19.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
When halting the CPU in Debug mode, the WDT counter is reset.
When starting the CPU again and the WDT is operating in Window mode, the first closed window timeout period will be disabled, and a Normal mode time-out period is executed.
Related Links
19.3.2.2 Window Mode
19.3
Functional Description
19.3.1
Initialization
• The WDT is enabled when a non-zero value is written to the Period bits (PERIOD) in the Control A
register (WDT.CTRLA).
• Optional: Write a non-zero value to the Window bits (WINDOW) in WDT.CTRLA to enable Window
mode operation.
All bits in the Control A register and the Lock bit (LOCK) in the STATUS register (WDT.STATUS) are
write-protected by the Configuration Change Protection mechanism.
The Reset value of WDT.CTRLA is defined by a fuse (FUSE.WDTCFG), so the WDT can be enabled at
boot time. If this is the case, the LOCK bit in WDT.STATUS is set at boot time.
Related Links
19.4 Register Summary - WDT
19.3.2
Operation
19.3.2.1 Normal Mode
In Normal mode operation, a single time-out period is set for the WDT. If the WDT is not reset from
software using the WDR any time before the time-out occurs, the WDT will issue a system Reset.
A new WDT time-out period will be started each time the WDT is reset by WDR.
There are 11 possible WDT time-out periods (TOWDT), selectable from 8 ms to 8s by writing to the Period
bit field (PERIOD) in the Control A register (WDT.CTRLA).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 185
ATtiny1616/3216
WDT - Watchdog Timer
Figure 19-2. Normal Mode Operation
WDT Count
Timely WDT Reset (WDR)
WDT Timeout
System Reset
Here:
TO WDT = 16 ms
5
10
15
20
25
30
TOWDT
35
t [ms]
Normal mode is enabled as long as the WINDOW bit field in the Control A register (WDT.CTRLA) is 0x0.
Related Links
19.4 Register Summary - WDT
19.3.2.2 Window Mode
In Window mode operation, the WDT uses two different time-out periods; a closed Window Time-out
period (TOWDTW) and the normal time-out period (TOWDT):
• The closed window time-out period defines a duration from 8 ms to 8s where the WDT cannot be
reset. If the WDT is reset during this period, the WDT will issue a system Reset.
• The normal WDT time-out period, which is also 8 ms to 8s, defines the duration of the open period
during which the WDT can (and should) be reset. The open period will always follow the closed
period, so the total duration of the time-out period is the sum of the closed window and the open
window time-out periods.
When enabling Window mode or when going out of Debug mode, the first closed period is activated after
the first WDR instruction.
If a second WDR is issued while a previous WDR is being synchronized, the second one will be ignored.
Figure 19-3. Window Mode Operation
WDT Count
Open
Timely WDT Reset (WDR)
Closed
WDR too early:
System Reset
Here:
TOWDTW =TOWDT = 8 ms
5
10
15
20
TOWDTW
25
30
TOWDT
35
t [ms]
The Window mode is enabled by writing a non-zero value to the WINDOW bit field in the Control A
register (WDT.CTRLA), and disabled by writing WINDOW=0x0.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 186
ATtiny1616/3216
WDT - Watchdog Timer
19.3.2.3 Configuration Protection and Lock
The WDT provides two security mechanisms to avoid unintentional changes to the WDT settings:
The first mechanism is the Configuration Change Protection mechanism, employing a timed write
procedure for changing the WDT control registers.
The second mechanism locks the configuration by writing a '1' to the LOCK bit in the STATUS register
(WDT.STATUS). When this bit is '1', the Control A register (WDT.CTRLA) cannot be changed.
Consequently, the WDT cannot be disabled from software.
LOCK in WDT.STATUS can only be written to '1'. It can only be cleared in Debug mode.
If the WDT configuration is loaded from fuses, LOCK is automatically set in WDT.STATUS.
Related Links
8.5.7 Configuration Change Protection (CCP)
19.3.3
Events
Not applicable.
19.3.4
Interrupts
Not applicable.
19.3.5
Sleep Mode Operation
The WDT will continue to operate in any sleep mode where the source clock is active.
19.3.6
Synchronization
Due to asynchronicity between the main clock domain and the peripheral clock domain, the Control A
register (WDT.CTRLA) is synchronized when written. The Synchronization Busy flag (SYNCBUSY) in the
STATUS register (WDT.STATUS) indicates if there is an ongoing synchronization.
Writing to WDT.CTRLA while SYNCBUSY=1 is not allowed.
The following registers are synchronized when written:
• PERIOD bits in Control A register (WDT.CTRLA)
• Window Period bits (WINDOW) in WDT.CTRLA
The WDR instruction will need two to three cycles of the WDT clock in order to be synchronized. Issuing a
new WDR instruction while a WDR instruction is being synchronized will be ignored.
19.3.7
Configuration Change Protection
This peripheral has registers that are under Configuration Change Protection (CCP). In order to write to
these, a certain key must be written to the CPU.CCP register first, followed by a write access to the
protected bits within four CPU instructions.
Attempting to write to a protected register without following the appropriate CCP unlock sequence leaves
the protected register unchanged.
The following registers are under CCP:
Table 19-2. WDT - Registers Under Configuration Change Protection
Register
Key
WDT.CTRLA
IOREG
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 187
ATtiny1616/3216
WDT - Watchdog Timer
...........continued
Register
Key
LOCK bit in WDT.STATUS
IOREG
List of bits/registers protected by CCP:
• Period bits in Control A register (CTRLA.PERIOD)
• Window Period bits in Control A register (CTRLA.WINDOW)
• LOCK bit in STATUS register (STATUS.LOCK)
Related Links
8.5.7 Configuration Change Protection (CCP)
8.5.7.1 Sequence for Write Operation to Configuration Change Protected I/O Registers
8.7.1 CCP
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 188
ATtiny1616/3216
WDT - Watchdog Timer
19.4
Register Summary - WDT
Offset
Name
Bit Pos.
0x00
0x01
CTRLA
STATUS
7:0
7:0
19.5
WINDOW[3:0]
LOCK
PERIOD[3:0]
SYNCBUSY
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 189
ATtiny1616/3216
WDT - Watchdog Timer
19.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
CTRLA
0x00
From FUSE.WDTCFG
Configuration Change Protection
7
6
5
4
3
2
R/W
x
1
0
R/W
R/W
R/W
R/W
R/W
x
x
x
x
R/W
R/W
x
x
x
WINDOW[3:0]
Access
Reset
PERIOD[3:0]
Bits 7:4 – WINDOW[3:0] Window
Writing a non-zero value to these bits enables the Window mode, and selects the duration of the closed
period accordingly.
The bits are optionally lock-protected:
• If LOCK bit in WDT.STATUS is '1', all bits are change-protected (Access = R)
• If LOCK bit in WDT.STATUS is '0', all bits can be changed (Access = R/W)
Value
0x0
0x1
0x2
0x3
0x4
0x5
0x6
0x7
0x8
0x9
0xA
0xB
other
Name
OFF
8CLK
16CLK
32CLK
64CLK
128CLK
256CLK
512CLK
1KCLK
2KCLK
4KCLK
8KCLK
-
Description
0.008s
0.016s
0.032s
0.064s
0.128s
0.256s
0.512s
1.024s
2.048s
4.096s
8.192s
Reserved
Bits 3:0 – PERIOD[3:0] Period
Writing a non-zero value to this bit enables the WDT, and selects the time-out period in Normal mode
accordingly. In Window mode, these bits select the duration of the open window.
The bits are optionally lock-protected:
• If LOCK in WDT.STATUS is '1', all bits are change-protected (Access = R)
• If LOCK in WDT.STATUS is '0', all bits can be changed (Access = R/W)
Value
0x0
0x1
0x2
0x3
0x4
0x5
Name
OFF
8CLK
16CLK
32CLK
64CLK
128CLK
© 2019 Microchip Technology Inc.
Description
0.008s
0.016s
0.032s
0.064s
0.128s
Preliminary Datasheet
40001997C-page 190
ATtiny1616/3216
WDT - Watchdog Timer
Value
0x6
0x7
0x8
0x9
0xA
0xB
other
Name
256CLK
512CLK
1KCLK
2KCLK
4KCLK
8KCLK
-
© 2019 Microchip Technology Inc.
Description
0.256s
0.512s
1.0s
2.0s
4.1s
8.2s
Reserved
Preliminary Datasheet
40001997C-page 191
ATtiny1616/3216
WDT - Watchdog Timer
19.5.2
Status
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
STATUS
0x01
0x00
Configuration Change Protection
6
5
4
3
2
1
0
LOCK
SYNCBUSY
R/W
R
0
0
Bit 7 – LOCK Lock
Writing this bit to '1' write-protects the WDT.CTRLA register.
It is only possible to write this bit to '1'. This bit can be cleared in Debug mode only.
If the PERIOD bits in WDT.CTRLA are different from zero after boot code, the lock will automatically be
set.
This bit is under CCP.
Bit 0 – SYNCBUSY Synchronization Busy
This bit is set after writing to the WDT.CTRLA register while the data is being synchronized from the
system clock domain to the WDT clock domain.
This bit is cleared by the system after the synchronization is finished.
This bit is not under CCP.
Related Links
19.3.6 Synchronization
19.3.7 Configuration Change Protection
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 192
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.
TCA - 16-bit Timer/Counter Type A
20.1
Features
•
•
•
•
•
•
•
•
•
20.2
16-Bit Timer/Counter
Three Compare Channels
Double-Buffered Timer Period Setting
Double-Buffered Compare Channels
Waveform Generation:
– Frequency generation
– Single-slope PWM (pulse-width modulation)
– Dual-slope PWM
Count on Event
Timer Overflow Interrupts/Events
One Compare Match per Compare Channel
Two 8-Bit Timer/Counters in Split Mode
Overview
The flexible 16-bit PWM Timer/Counter type A (TCA) provides accurate program execution timing,
frequency and waveform generation, and command execution.
A TCA consists of a base counter and a set of compare channels. The base counter can be used to count
clock cycles or events or let events control how it counts clock cycles. It has direction control and period
setting that can be used for timing. The compare channels can be used together with the base counter to
do compare match control, frequency generation, and pulse-width waveform modulation.
Depending on the mode of operation, the counter is cleared, reloaded, incremented, or decremented at
each timer/counter clock or event input.
A timer/counter can be clocked and timed from the peripheral clock with optional prescaling or from the
event system. The event system can also be used for direction control or to synchronize operations.
By default, the TCA is a 16-bit timer/counter. The timer/counter has a Split mode feature that splits it into
two 8-bit timer/counters with three compare channels each. In Split mode, each compare channel only
supports single-slope PWM waveform generation.
A block diagram of the 16-bit timer/counter with closely related peripheral modules (in grey) is shown in
the figure below.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 193
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
Figure 20-1. 16-bit Timer/Counter and Closely Related Peripherals
Timer/Counter
Base Counter
Counter
Control Logic
Compare Channel 0
Compare Channel 1
Compare Channel 2
Comparator
Buffer
Waveform
Generation
CLK_PER
Event
System
PORTS
Timer Period
Prescaler
This device provides one instance of the TCA peripheral, TCA0.
20.2.1
Block Diagram
The figure below shows a detailed block diagram of the timer/counter.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 194
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
Figure 20-2. Timer/Counter Block Diagram
Base Coun ter
PERB
CTRLA
PER
EVCTRL
Clock Select
Event
Select
"count"
"clear"
"load"
"direction"
Counter
CNT
=
=0
TOP
BOTTOM
OVF/UNF
(INT Req.)
Control Logi c
"ev"
UPDATE
BV
Compare
(Unit x = {A,B,C})
BV
CMPnBUF
Control Logi c
CMPn
=
Wav efo rm
Generation
"match"
WOn Out
CMPn
(INT Req.)
The counter register (TCAn.CNT), period registers with buffer (TCAn.PER and TCAn.PERBUF), and
compare registers with buffers (TCAn.CMPx and TCAn.CMPBUFx) are 16-bit registers. All buffer
registers have a buffer valid (BV) flag that indicates when the buffer contains a new value.
During normal operation, the counter value is continuously compared to zero and the period (PER) value
to determine whether the counter has reached TOP or BOTTOM.
The counter value is also compared to the TCAn.CMPx registers. These comparisons can be used to
generate interrupt requests. The Waveform Generator modes use these comparisons to set the waveform
period or pulse-width.
A prescaled peripheral clock and events from the event system can be used to control the counter.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 195
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
Figure 20-3. Timer/Counter Clock Logic
CLK_PER
Prescaler
Event System
event
CKSEL
EVACT
(Encoding)
CLK_TCA
CNT
CNTEI
20.2.2
Signal Description
Signal
Description(1)
Type
WO[2:0]
Digital output
Waveform output
WO[5:3]
Digital output
Waveform output - Split mode only
Note:
1. Refer to the I/O Multiplexing and Considerations section to see the availability of WOn on pins.
20.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 20-1. TCA System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
WO[5:0]
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
20.2.3.1 Clocks
20.2.3.5 Debug Operation
20.2.3.3 Interrupts
20.2.3.4 Events
20.2.3.1 Clocks
This peripheral uses the system clock CLK_PER and has its own prescaler.
Related Links
10. CLKCTRL - Clock Controller
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 196
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.2.3.2 I/O Lines and Connections
Using the I/O lines of the peripheral requires configuration of the I/O pins.
Related Links
5. I/O Multiplexing and Considerations
16. PORT - I/O Pin Configuration
20.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
20.3.5 Interrupts
20.2.3.4 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
20.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
This peripheral can be forced to operate with halted CPU by writing a '1' to the Debug Run bit (DBGRUN)
in the Debug Control register of the peripheral (peripheral.DBGCTRL).
Related Links
33. UPDI - Unified Program and Debug Interface
20.3
Functional Description
20.3.1
Definitions
The following definitions are used throughout the documentation:
Table 20-2. Timer/Counter Definitions
Name
Description
BOTTOM The counter reaches BOTTOM when it becomes zero.
MAX
The counter reaches MAXimum when it becomes all ones.
TOP
The counter reaches TOP when it becomes equal to the highest value in the count
sequence.
UPDATE The update condition is met when the timer/counter reaches BOTTOM or TOP, depending on
the Waveform Generator mode.
CNT
Counter register value.
CMP
Compare register value.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 197
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
In general, the term timer is used when the timer/counter is counting periodic clock ticks. The term
counter is used when the input signal has sporadic or irregular ticks.
20.3.2
Initialization
To start using the timer/counter in a basic mode, follow these steps:
• Write a TOP value to the Period register (TCAn.PER)
• Enable the peripheral by writing a '1' to the ENABLE bit in the Control A register (TCAn.CTRLA).
The counter will start counting clock ticks according to the prescaler setting in the Clock Select bit
field (CLKSEL) in TCAn.CTRLA.
• Optional: By writing a '1' to the Enable Count on Event Input bit (CNTEI) in the Event Control register
(TCAn.EVCTRL), event inputs are counted instead of clock ticks.
• The counter value can be read from the Counter bit field (CNT) in the Counter register (TCAn.CNT).
20.3.3
Operation
20.3.3.1 Normal Operation
In normal operation, the counter is counting clock ticks in the direction selected by the Direction bit (DIR)
in the Control E register (TCAn.CTRLE), until it reaches TOP or BOTTOM. The clock ticks are from the
peripheral clock CLK_PER, optionally prescaled, depending on the Clock Select bit field (CLKSEL) in the
Control A register (TCAn.CTRLA).
When up-counting and TOP are reached, the counter will wrap to zero at the next clock tick. When downcounting, the counter is reloaded with the Period register value (TCAn.PER) when BOTTOM is reached.
Figure 20-4. Normal Operation
CNT written
MAX
"update"
CNT
TOP
BOTTOM
DIR
It is possible to change the counter value in the Counter register (TCAn.CNT) when the counter is
running. The write access to TCAn.CNT has higher priority than count, clear, or reload, and will be
immediate. The direction of the counter can also be changed during normal operation by writing to DIR in
TCAn.CTRLE.
20.3.3.2 Double Buffering
The Period register value (TCAn.PER) and the Compare n register values (TCAn.CMPn) are all doublebuffered (TCAn.PERBUF and TCAn.CMPnBUF).
Each buffer register has a Buffer Valid flag (PERBV, CMPnBV) in the Control F register (TCAn.CTRLF),
which indicates that the buffer register contains a valid, i.e. new, value that can be copied into the
corresponding Period or Compare register. When the Period register and Compare n registers are used
for a compare operation, the BV flag is set when data is written to the buffer register and cleared on an
UPDATE condition. This is shown for a Compare register (CMPn) below.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 198
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
Figure 20-5. Period and Compare Double Buffering
"write enable"
"data write"
EN
CMPnBUF
BV
EN
UPDATE
CMPn
CNT
=
"match"
Both the TCAn.CMPn and TCAn.CMPnBUF registers are available as I/O registers. This allows
initialization and bypassing of the buffer register and the double buffering function.
20.3.3.3 Changing the Period
The Counter period is changed by writing a new TOP value to the Period register (TCAn.PER).
No Buffering: If double buffering is not used, any period update is immediate.
Figure 20-6. Changing the Period Without Buffering
Counter wrap-around
MAX
"update"
"write"
CNT
BOTTOM
New TOP written to
PER that is higher
than current CNT.
New TOP written to
PER that is lower
than current CNT.
A counter wrap-around can occur in any mode of operation when up-counting without buffering. This is
due to the fact that the TCAn.CNT and TCAn.PER registers are continuously compared: if a new TOP
value is written to TCAn.PER that is lower than the current TCAn.CNT, the counter will wrap first, before a
compare match happens.
Figure 20-7. Unbuffered Dual-Slope Operation
Counter wrap-around
MAX
"update"
"write"
CNT
BOTTOM
New TOP written to
PER that is higher
than current CNT.
© 2019 Microchip Technology Inc.
New TOP written to
PER that is lower
than current CNT.
Preliminary Datasheet
40001997C-page 199
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
With Buffering: When double buffering is used, the buffer can be written at any time and still maintain
correct operation. The TCAn.PER is always updated on the UPDATE condition, as shown for dual-slope
operation in the figure below. This prevents wrap-around and the generation of odd waveforms.
Figure 20-8. Changing the Period Using Buffering
MAX
"update"
"write"
CNT
BOTTOM
New Period written to
PERB that is higher
than current CNT.
New Period written to
PERB that is lower
than current CNT.
New PER is updated
with PERB value.
20.3.3.4 Compare Channel
Each Compare Channel n continuously compares the counter value (TCAn.CNT) with the Compare n
register (TCAn.CMPn). If TCAn.CNT equals TCAn.CMPn, the comparator n signals a match. The match
will set the Compare Channel's Interrupt flag at the next timer clock cycle, and the optional interrupt is
generated.
The Compare n Buffer register (TCAn.CMPnBUF) provides double buffer capability equivalent to that for
the period buffer. The double buffering synchronizes the update of the TCAn.CMPn register with the
buffer value to either the TOP or BOTTOM of the counting sequence, according to the UPDATE condition.
The synchronization prevents the occurrence of odd-length, non-symmetrical pulses for glitch-free output.
20.3.3.4.1 Waveform Generation
The compare channels can be used for waveform generation on the corresponding port pins. To make
the waveform visible on the connected port pin, the following requirements must be met:
1.
2.
3.
4.
5.
A Waveform Generation mode must be selected by writing the WGMODE bit field in TCAn.CTRLB.
The TCA is counting clock ticks, not events (CNTEI=0 in TCAn.EVCTRL).
The compare channels used must be enabled (CMPnEN=1 in TCAn.CTRLB). This will override the
corresponding port pin output register. An alternative pin can be selected by writing to the
respective TCA Waveform Output n bit (TCA0n) in the Control C register of the Port Multiplexer
(PORTMUX.CTRLC).
The direction for the associated port pin n must be configured as an output (PORTx.DIR[n]=1).
Optional: Enable inverted waveform output for the associated port pin n (INVEN=1 in PORTx.PINn).
20.3.3.4.2 Frequency (FRQ) Waveform Generation
For frequency generation, the period time (T) is controlled by a TCAn.CMPn register instead of the Period
register (TCAn.PER). The waveform generation output WG is toggled on each compare match between
the TCAn.CNT and TCAn.CMPn registers.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 200
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
Figure 20-9. Frequency Waveform Generation
Period (T)
Direction change
CNT written
MAX
"update"
CNT
TOP
BOTTOM
WG Output
The waveform frequency (fFRQ) is defined by the following equation:
�FRQ =
f CLK_PER
2� CMPn+1
where N represents the prescaler divider used (CLKSEL in TCAn.CTRLA), CMPn is the value of the
TCAn.CMPn register, and fCLK_PER is the system clock for the peripherals.
The maximum frequency of the waveform generated is half of the peripheral clock frequency (fCLK_PER/2)
when TCAn.CMPn is written to zero (0x0000) and no prescaling is used (N=1, CLKSEL=0x0 in
TCAn.CTRLA).
20.3.3.4.3 Single-Slope PWM Generation
For single-slope Pulse-Width Modulation (PWM) generation, the period (T) is controlled by TCAn.PER,
while the values of TCAn.CMPn control the duty-cycle of the WG output. The figure below shows how the
counter counts from BOTTOM to TOP and then restarts from BOTTOM. The waveform generator (WO)
output is set at TOP and cleared on the compare match between the TCAn.CNT and TCAn.CMPn
registers.
Figure 20-10. Single-Slope Pulse-Width Modulation
Period (T)
CMPn=BOTTOM
CMPn=TOP
MAX
TOP
"update"
"match"
CNT
CMPn
BOTTOM
Output WOn
The TCAn.PER register defines the PWM resolution. The minimum resolution is 2 bits
(TCA.PER=0x0003), and the maximum resolution is 16 bits (TCA.PER=MAX).
The following equation calculates the exact resolution for single-slope PWM (RPWM_SS):
�PWM_SS =
log PER+1
log 2
The single-slope PWM frequency (fPWM_SS) depends on the period setting (TCA_PER), the system's
peripheral clock frequency fCLK_PER, and the TCA prescaler (CLKSEL in TCAn.CTRLA). It is calculated by
the following equation where N represents the prescaler divider used:
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 201
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
�PWM_SS =
�CLK_PER
� PER+1
20.3.3.4.4 Dual-Slope PWM
For dual-slope PWM generation, the period (T) is controlled by TCAn.PER, while the values of
TCAn.CMPn control the duty-cycle of the WG output.
The figure below shows how for dual-slope PWM the counter counts repeatedly from BOTTOM to TOP
and then from TOP to BOTTOM. The waveform generator output is set on BOTTOM, cleared on compare
match when up-counting, and set on compare match when down-counting.
Figure 20-11. Dual-Slope Pulse-Width Modulation
Period (T)
CMPn=BOTTOM
CMPn=TOP
"update"
"match"
MAX
CMPn
TOP
CNT
BOTTOM
Waveform Output WOn
Using dual-slope PWM results in a lower maximum operation frequency compared to the single-slope
PWM operation.
The period register (TCAn.PER) defines the PWM resolution. The minimum resolution is 2 bits
(TCAn.PER=0x0003), and the maximum resolution is 16 bits (TCAn.PER=MAX).
The following equation calculates the exact resolution for dual-slope PWM (RPWM_DS):
�PWM_DS =
log PER+1
log 2
�PWM_DS =
�CLK_PER
2� ⋅ PER
The PWM frequency depends on the period setting (TCAn.PER), the peripheral clock frequency
(fCLK_PER), and the prescaler divider used (CLKSEL in TCAn.CTRLA). It is calculated by the following
equation:
N represents the prescaler divider used.
20.3.3.4.5 Port Override for Waveform Generation
To make the waveform generation available on the port pins, the corresponding port pin direction must be
set as output (PORTx.DIR[n]=1). The TCA will override the port pin values when the compare channel is
enabled (CMPnEN=1 in TCAn.CTRLB) and a Waveform Generation mode is selected.
The figure below shows the port override for TCA. The timer/counter compare channel will override the
port pin output value (OUT) on the corresponding port pin. Enabling inverted I/O on the port pin
(INVEN=1 in PORT.PINn) inverts the corresponding WG output.
Figure 20-12. Port Override for Timer/Counter Type A
OUT
WOn
Waveform
CMPnEN
© 2019 Microchip Technology Inc.
INVEN
Preliminary Datasheet
40001997C-page 202
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.3.3.5 Timer/Counter Commands
A set of commands can be issued by software to immediately change the state of the peripheral. These
commands give direct control of the UPDATE, RESTART, and RESET signals. A command is issued by
writing the respective value to the Command bit field (CMD) in the Control E register (TCAn.CTRLESET).
An Update command has the same effect as when an update condition occurs, except that the Update
command is not affected by the state of the Lock Update bit (LUPD) in the Control E register
(TCAn.CTRLE).
The software can force a restart of the current waveform period by issuing a Restart command. In this
case, the counter, direction, and all compare outputs are set to zero.
A Reset command will set all timer/counter registers to their initial values. A Reset can be issued only
when the timer/counter is not running (ENABLE=0 in TCAn.CTRLA).
20.3.3.6 Split Mode - Two 8-Bit Timer/Counters
Split Mode Overview
To double the number of timers and PWM channels in the TCA, a Split mode is provided. In this Split
mode, the 16-bit timer/counter acts as two separate 8-bit timers, which each have three compare
channels for PWM generation. The Split mode will only work with single-slope down-count. Split mode
does not support event action controlled operation.
Split Mode Differences to Normal Mode
• Count:
– Down-count only
– Timer/counter Counter high byte and Counter low byte are independent (TCAn.LCNT,
TCAn.HCNT)
• Waveform Generation:
– Single-slope PWM only (WGMODE=SINGLESLOPE in TCAn.CTRLB)
• Interrupt:
– No change for low byte Timer/Counter (TCAn.LCNT)
– Underflow interrupt for high byte Timer/Counter (TCAn.HCNT)
– No compare interrupt or flag for High-byte Compare n registers (TCAn.HCMPn)
• Event Actions: Not Compatible
• Buffer registers and Buffer Valid Flags: Unused
• Register Access: Byte Access to all registers
• Temp register: Unused, 16-bit register of the Normal mode are Accessed as 8-bit 'TCA_H' and
'TCA_L', Respectively
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 203
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
Block Diagram
Figure 20-13. Timer/Counter Block Diagram Split Mode
Base Counter
HPER
LPER
"count high"
"load high"
"count low"
"load low"
Counter
HCNT
Clock Select
CTRLA
LCNT
HUNF
Control Logic
(INT Req.)
LUNF
(INT Req.)
=0
BOTTOML
BOTTOMH
=0
Compare
(Unit n = {0,1,2})
LCMPn
Waveform
Generation
"match"
=
WOn Out
LCMPn
(INT Req.)
Compare
(Unit n = {0,1,2})
HCMPn
=
Waveform
Generation
WO[n+3] Out
"match"
Split Mode Initialization
When shifting between Normal mode and Split mode, the functionality of some registers and bits
changes, but their values do not. For this reason, disabling the peripheral (ENABLE=0 in TCAn.CTRLA)
and doing a hard Reset (CMD=RESET in TCAn.CTRLESET) is recommended when changing the mode
to avoid unexpected behavior.
To start using the timer/counter in basic Split mode after a hard Reset, follow these steps:
• Enable Split mode by writing a '1' to the Split mode enable bit in the Control D register (SPLITM in
TCAn.CTRLD)
• Write a TOP value to the Period registers (TCAn.PER)
• Enable the peripheral by writing a '1' to the ENABLE bit in the Control A register (TCAn.CTRLA).
The counter will start counting clock ticks according to the prescaler setting in the Clock Select bit
field (CLKSEL) in TCAn.CTRLA.
• The counter values can be read from the Counter bit field in the Counter registers (TCAn.CNT)
Activating Split mode results in changes to the functionality of some registers and register bits. The
modifications are described in a separate register map.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 204
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.3.4
Events
The TCA is an event generator. The following events will generate a one-cycle strobe on the event
channel outputs:
• Timer overflow
• Timer underflow in Split mode
• Compare match channel 0
• Compare match channel 1
• Compare match channel 2
The peripheral can take the following actions on an input event:
•
•
•
•
The counter counts positive edges of the event signal.
The counter counts both positive and negative edges of the event signal.
The counter counts prescaled clock cycles as long as the event signal is high.
The counter counts prescaled clock cycles. The event signal controls the direction of counting. Upcounting when the event signal is low and down-counting when the event signal is high.
The specific action is selected by writing to the Event Action bits (EVACT) in the Event Control register
(TCAn.EVCTRL). Events as input are enabled by writing a '1' to the Enable Count on Event Input bit
(CNTEI in TCAn.EVCTRL).
Event-controlled inputs are not used in Split mode.
20.3.5
Interrupts
Table 20-3. Available Interrupt Vectors and Sources in Normal Mode
Offset Name Vector Description
Conditions
0x00
OVF
The counter has reached its top value and wrapped to
zero.
0x04
CMP0 Compare channel 0 interrupt
Match between the counter value and the Compare 0
register.
0x06
CMP1 Compare channel 1 interrupt
Match between the counter value and the Compare 1
register.
0x08
CMP2 Compare channel 2 interrupt
Match between the counter value and the Compare 2
register.
Overflow and compare match
interrupt
Table 20-4. Available Interrupt Vectors and Sources in Split Mode
Offset Name
Vector Description
0x00
LUNF
Low byte underflow interrupt Low byte timer reaches BOTTOM.
0x02
HUNF
High byte underflow interrupt High byte timer reaches BOTTOM.
0x04
LCMP0 Compare channel 0 interrupt Match between the counter value and the low byte of
Compare 0 register.
0x06
LCMP1 Compare channel 1 interrupt Match between the counter value and the low byte of
Compare 1 register.
© 2019 Microchip Technology Inc.
Conditions
Preliminary Datasheet
40001997C-page 205
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
...........continued
Offset Name
0x08
Vector Description
Conditions
LCMP2 Compare channel 2 interrupt Match between the counter value and the low byte of the
Compare 2 register.
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding enable bit in the peripheral's
Interrupt Control register (peripheral.INTCTRL).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
Related Links
8. AVR CPU
8.7.3 SREG
20.3.6
Sleep Mode Operation
The timer/counter will continue operation in Idle Sleep mode.
20.3.7
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 206
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.4
Register Summary - TCA in Normal Mode (CTRLD.SPLITM=0)
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
...
0x0D
0x0E
0x0F
0x10
...
0x1F
CTRLA
CTRLB
CTRLC
CTRLD
CTRLECLR
CTRLESET
CTRLFCLR
CTRLFSET
Reserved
EVCTRL
INTCTRL
INTFLAGS
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
0x20
CNT
0x22
...
0x25
Reserved
0x26
PER
0x28
CMP0
0x2A
CMP1
0x2C
CMP2
0x2E
...
0x35
Reserved
0x36
PERBUF
0x38
CMP0BUF
0x3A
CMP1BUF
0x3C
CMP2BUF
20.5
7:0
7:0
7:0
CLKSEL[2:0]
CMP2EN
CMP1EN
CMP0EN
ALUPD
CMP2OV
CMD[1:0]
CMD[1:0]
CMP2BV
CMP1BV
CMP2BV
CMP1BV
ENABLE
WGMODE[2:0]
CMP1OV
LUPD
LUPD
CMP0BV
CMP0BV
EVACT[1:0]
CMP2
CMP2
CMP1
CMP1
CMP0
CMP0
CMP0OV
SPLITM
DIR
DIR
PERBV
PERBV
CNTEI
OVF
OVF
Reserved
DBGCTRL
TEMP
7:0
7:0
TEMP[7:0]
DBGRUN
7:0
15:8
CNT[7:0]
CNT[15:8]
7:0
15:8
7:0
15:8
7:0
15:8
7:0
15:8
PER[7:0]
PER[15:8]
CMP[7:0]
CMP[15:8]
CMP[7:0]
CMP[15:8]
CMP[7:0]
CMP[15:8]
7:0
15:8
7:0
15:8
7:0
15:8
7:0
15:8
PERBUF[7:0]
PERBUF[15:8]
CMPBUF[7:0]
CMPBUF[15:8]
CMPBUF[7:0]
CMPBUF[15:8]
CMPBUF[7:0]
CMPBUF[15:8]
Reserved
Register Description - Normal Mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 207
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
-
6
5
4
3
2
1
CLKSEL[2:0]
Access
Reset
0
ENABLE
R/W
R/W
R/W
R/W
0
0
0
0
Bits 3:1 – CLKSEL[2:0] Clock Select
These bits select the clock frequency for the timer/counter.
Value
Name
Description
0x0
DIV1
fTCA = fCLK_PER/1
0x1
DIV2
fTCA = fCLK_PER/2
0x2
DIV4
fTCA = fCLK_PER/4
0x3
DIV8
fTCA = fCLK_PER/8
0x4
DIV16
fTCA = fCLK_PER/16
0x5
DIV64
fTCA = fCLK_PER/64
0x6
DIV256
fTCA = fCLK_PER/256
0x7
DIV1024
fTCA = fCLK_PER/1024
Bit 0 – ENABLE Enable
Value
Description
0
The peripheral is disabled
1
The peripheral is enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 208
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.2
Control B - Normal Mode
Name:
Offset:
Reset:
Property:
Bit
CTRLB
0x01
0x00
-
7
6
5
4
3
CMP2EN
CMP1EN
CMP0EN
ALUPD
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
Access
Reset
2
1
0
WGMODE[2:0]
Bits 4, 5, 6 – CMPEN Compare n Enable
In the FRQ or PWM Waveform Generation mode, these bits will override the PORT output register for the
corresponding pin.
Value
Description
0
Port output settings for the pin with WOn output respected
1
Port output settings for pin with WOn output overridden in FRQ or PWM Waveform
Generation mode
Bit 3 – ALUPD Auto-Lock Update
The Auto-Lock Update feature controls the Lock Update (LUPD) bit in the TCAn.CTRLE register. When
ALUPD is written to ‘1’, LUPD will be set to ‘1’ until the Buffer Valid (CMPnBV) bits of all enabled compare
channels are ‘1’. This condition will clear LUPD.
It will remain cleared until the next UPDATE condition, where the buffer values will be transferred to the
CMPn registers and LUPD will be set to ‘1’ again. This makes sure that CMPnBUF register values are not
transferred to the CMPn registers until all enabled compare buffers are written.
Value
Description
0
LUPD in TCA.CTRLE not altered by system
1
LUPD in TCA.CTRLE set and cleared automatically
Bits 2:0 – WGMODE[2:0] Waveform Generation Mode
These bits select the Waveform Generation mode and control the counting sequence of the counter, TOP
value, UPDATE condition, interrupt condition, and type of waveform that is generated.
No waveform generation is performed in the Normal mode of operation. For all other modes, the result
from the waveform generator will only be directed to the port pins if the corresponding CMPnEN bit has
been set to enable this. The port pin direction must be set as output.
Table 20-5. Timer Waveform Generation Mode
WGMODE[2:0]
Group Configuration Mode of Operation
Top
Update
OVF
Normal
PER
TOP
TOP
000
NORMAL
001
FRQ
Frequency
CMP0 TOP
TOP
010
-
Reserved
-
-
-
011
SINGLESLOPE
Single-slope PWM
PER
BOTTOM BOTTOM
100
-
Reserved
-
-
101
DSTOP
Dual-slope PWM
PER
BOTTOM TOP
© 2019 Microchip Technology Inc.
Preliminary Datasheet
-
40001997C-page 209
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
...........continued
WGMODE[2:0]
Group Configuration Mode of Operation
Top
Update
OVF
110
DSBOTH
Dual-slope PWM
PER
BOTTOM TOP and BOTTOM
111
DSBOTTOM
Dual-slope PWM
PER
BOTTOM BOTTOM
Value
0x0
0x1
0x3
0x5
0x6
0x7
Other
Name
NORMAL
FRQ
SINGLESLOPE
DSTOP
DSBOTH
DSBOTTOM
-
© 2019 Microchip Technology Inc.
Description
Normal operation mode
Frequency mode
Single-slope PWM mode
Dual-slope PWM mode
Dual-slope PWM mode
Dual-slope PWM mode
Reserved
Preliminary Datasheet
40001997C-page 210
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.3
Control C - Normal Mode
Name:
Offset:
Reset:
Property:
Bit
7
CTRLC
0x02
0x00
-
6
5
4
3
Access
Reset
2
1
0
CMP2OV
CMP1OV
CMP0OV
R/W
R/W
R/W
0
0
0
Bit 2 – CMP2OV Compare Output Value 2
See CMP0OV.
Bit 1 – CMP1OV Compare Output Value 1
See CMP0OV.
Bit 0 – CMP0OV Compare Output Value 0
The CMPnOV bits allow direct access to the waveform generator's output compare value when the timer/
counter is not enabled. This is used to set or clear the WG output value when the timer/counter is not
running.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 211
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.4
Control D
Name:
Offset:
Reset:
Property:
Bit
7
CTRLD
0x03
0x00
-
6
5
4
3
2
1
0
SPLITM
Access
R/W
Reset
0
Bit 0 – SPLITM Enable Split Mode
This bit sets the timer/counter in Split mode operation. It will then work as two 8-bit timer/counters. The
register map will change compared to normal 16-bit mode.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 212
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.5
Control Register E Clear - Normal Mode
Name:
Offset:
Reset:
Property:
CTRLECLR
0x04
0x00
-
The individual Status bit can be cleared by writing a '1' to its bit location. This allows each bit to be
cleared without the use of a read-modify-write operation on a single register.
Each Status bit can be read out either by reading TCAn.CTRLESET or TCAn.CTRLECLR.
Bit
7
6
5
4
3
2
CMD[1:0]
Access
Reset
1
0
LUPD
DIR
R/W
R/W
R/W
R/W
0
0
0
0
Bits 3:2 – CMD[1:0] Command
These bits are used for software control of update, restart, and reset of the timer/counter. The command
bits are always read as '0'.
Value
Name
Description
0x0
NONE
No command
0x1
UPDATE
Force update
0x2
RESTART
Force restart
0x3
RESET
Force hard Reset (ignored if TC is enabled)
Bit 1 – LUPD Lock Update
Lock update can be used to ensure that all buffers are valid before an update is performed.
Value
Description
0
The buffered registers are updated as soon as an UPDATE condition has occurred.
1
No update of the buffered registers is performed, even though an UPDATE condition has
occurred.
Bit 0 – DIR Counter Direction
Normally this bit is controlled in hardware by the Waveform Generation mode or by event actions, but this
bit can also be changed from software.
Value
Description
0
The counter is counting up (incrementing)
1
The counter is counting down (decrementing)
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 213
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.6
Control Register E Set - Normal Mode
Name:
Offset:
Reset:
Property:
CTRLESET
0x05
0x00
-
The individual Status bit can be set by writing a '1' to its bit location. This allows each bit to be set without
the use of a read-modify-write operation on a single register.
Each Status bit can be read out either by reading TCAn.CTRLESET or TCAn.CTRLECLR.
Bit
7
6
5
4
3
2
CMD[1:0]
Access
Reset
1
0
LUPD
DIR
R/W
R/W
R/W
R/W
0
0
0
0
Bits 3:2 – CMD[1:0] Command
These bits are used for software control of update, restart, and reset the timer/counter. The command bits
are always read as '0'.
Value
Name
Description
0x0
NONE
No command
0x1
UPDATE
Force update
0x2
RESTART
Force restart
0x3
RESET
Force hard Reset (ignored if TC is enabled)
Bit 1 – LUPD Lock Update
Locking the update ensures that all buffers are valid before an update is performed.
Value
Description
0
The buffered registers are updated as soon as an UPDATE condition has occurred.
1
No update of the buffered registers is performed, even though an UPDATE condition has
occurred.
Bit 0 – DIR Counter Direction
Normally this bit is controlled in hardware by the Waveform Generation mode or by event actions, but this
bit can also be changed from software.
Value
Description
0
The counter is counting up (incrementing)
1
The counter is counting down (decrementing)
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 214
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.7
Control Register F Clear
Name:
Offset:
Reset:
Property:
CTRLFCLR
0x06
0x00
-
The individual Status bit can be cleared by writing a '1' to its bit location. This allows each bit to be
cleared without the use of a read-modify-write operation on a single register.
Bit
7
6
5
Access
Reset
4
3
2
1
0
CMP2BV
CMP1BV
CMP0BV
PERBV
R/W
R/W
R/W
R/W
0
0
0
0
Bit 3 – CMP2BV Compare 2 Buffer Valid
See CMP0BV.
Bit 2 – CMP1BV Compare 1 Buffer Valid
See CMP0BV.
Bit 1 – CMP0BV Compare 0 Buffer Valid
The CMPnBV bits are set when a new value is written to the corresponding TCAn.CMPnBUF register.
These bits are automatically cleared on an UPDATE condition.
Bit 0 – PERBV Period Buffer Valid
This bit is set when a new value is written to the TCAn.PERBUF register. This bit is automatically cleared
on an UPDATE condition.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 215
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.8
Control Register F Set
Name:
Offset:
Reset:
Property:
CTRLFSET
0x07
0x00
-
The individual status bit can be set by writing a '1' to its bit location. This allows each bit to be set without
the use of a read-modify-write operation on a single register.
Bit
7
6
5
Access
Reset
4
3
2
1
0
CMP2BV
CMP1BV
CMP0BV
PERBV
R/W
R/W
R/W
R/W
0
0
0
0
Bit 3 – CMP2BV Compare 2 Buffer Valid
See CMP0BV.
Bit 2 – CMP1BV Compare 1 Buffer Valid
See CMP0BV.
Bit 1 – CMP0BV Compare 0 Buffer Valid
The CMPnBV bits are set when a new value is written to the corresponding TCAn.CMPnBUF register.
These bits are automatically cleared on an UPDATE condition.
Bit 0 – PERBV Period Buffer Valid
This bit is set when a new value is written to the TCAn.PERBUF register. This bit is automatically cleared
on an UPDATE condition.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 216
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.9
Event Control
Name:
Offset:
Reset:
Property:
Bit
7
EVCTRL
0x09
0x00
-
6
5
4
3
2
1
EVACT[1:0]
Access
Reset
0
CNTEI
R/W
R/W
R/W
0
0
0
Bits 2:1 – EVACT[1:0] Event Action
These bits define what type of event action the counter will increment or decrement.
Value
Name
Description
0x0
EVACT_POSEDGE Count on positive edge event
0x1
EVACT_ANYEDGE Count on any edge event
0x2
EVACT_HIGHLVL Count on prescaled clock while event line is 1.
0x3
EVACT_UPDOWN Count on prescaled clock. The Event controls the count direction. Upcounting when the event line is 0, down-counting when the event line is
1.
Bit 0 – CNTEI Enable Count on Event Input
Value
Description
0
Counting on Event input is disabled
1
Counting on Event input is enabled according to EVACT bit field
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 217
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.10 Interrupt Control Register - Normal Mode
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
INTCTRL
0x0A
0x00
-
6
5
4
3
2
1
0
CMP2
CMP1
CMP0
OVF
R/W
R/W
R/W
R/W
0
0
0
0
Bit 6 – CMP2 Compare Channel 2 Interrupt Enable
See CMP0.
Bit 5 – CMP1 Compare Channel 1 Interrupt Enable
See CMP0.
Bit 4 – CMP0 Compare Channel 0 Interrupt Enable
Writing the CMPn bits to '1' enable compare interrupt from channel n.
Bit 0 – OVF Timer Overflow/Underflow Interrupt Enable
Writing the OVF bit to '1' enables overflow interrupt.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 218
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.11 Interrupt Flag Register - Normal Mode
Name:
Offset:
Reset:
Property:
INTFLAGS
0x0B
0x00
-
The individual Status bit can be cleared by writing a '1' to its bit location. This allows each bit to be set
without the use of a read-modify-write operation on a single register.
Bit
Access
Reset
7
6
5
4
CMP2
CMP1
CMP0
3
2
1
OVF
0
R/W
R/W
R/W
R/W
0
0
0
0
Bit 6 – CMP2 Compare Channel 2 Interrupt Flag
See CMP0 flag description.
Bit 5 – CMP1 Compare Channel 1 Interrupt Flag
See CMP0 flag description.
Bit 4 – CMP0 Compare Channel 0 Interrupt Flag
The Compare Interrupt flag (CMPn) is set on a compare match on the corresponding compare channel.
For all modes of operation, the CMPn flag will be set when a compare match occurs between the Count
register (TCAn.CNT) and the corresponding Compare register (TCAn.CMPn). The CMPn flag is not
cleared automatically, only by writing a ‘1’ to its bit location.
Bit 0 – OVF Overflow/Underflow Interrupt Flag
This flag is set either on a TOP (overflow) or BOTTOM (underflow) condition, depending on the
WGMODE setting. The OVF flag is not cleared automatically, only by writing a ‘1’ to its bit location.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 219
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.12 Debug Control Register
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x0E
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Run in Debug
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 220
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.13 Temporary Bits for 16-Bit Access
Name:
Offset:
Reset:
Property:
TEMP
0x0F
0x00
-
The Temporary register is used by the CPU for single-cycle, 16-bit access to the 16-bit registers of this
peripheral. It can be read and written by software. Refer to 16-bit access in the AVR CPU chapter. There
is one common Temporary register for all the 16-bit registers of this peripheral.
Bit
7
6
5
4
3
2
1
0
TEMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – TEMP[7:0] Temporary Bits for 16-bit Access
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 221
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.14 Counter Register - Normal Mode
Name:
Offset:
Reset:
Property:
CNT
0x20
0x00
-
The TCAn.CNTL and TCAn.CNTH register pair represents the 16-bit value, TCAn.CNT. The low byte [7:0]
(suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset
+ 0x01.
CPU and UPDI write access has priority over internal updates of the register.
Bit
15
14
13
12
11
10
9
8
CNT[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
CNT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – CNT[15:8] Counter High Byte
These bits hold the MSB of the 16-bit counter register.
Bits 7:0 – CNT[7:0] Counter Low Byte
These bits hold the LSB of the 16-bit counter register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 222
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.15 Period Register - Normal Mode
Name:
Offset:
Reset:
Property:
PER
0x26
0xFFFF
-
TCAn.PER contains the 16-bit TOP value in the timer/counter.
The TCAn.PERL and TCAn.PERH register pair represents the 16-bit value, TCAn.PER. The low byte
[7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset
+ 0x01.
Bit
15
14
13
12
11
10
9
8
PER[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
1
1
1
1
1
1
1
1
Bit
7
6
5
4
3
2
1
0
PER[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
1
1
1
1
1
1
1
1
Bits 15:8 – PER[15:8] Periodic High Byte
These bits hold the MSB of the 16-bit period register.
Bits 7:0 – PER[7:0] Periodic Low Byte
These bits hold the LSB of the 16-bit period register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 223
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.16 Compare n Register - Normal Mode
Name:
Offset:
Reset:
Property:
CMPn
0x28 + n*0x02 [n=0..2]
0x00
-
This register is continuously compared to the counter value. Normally, the outputs from the comparators
are then used for generating waveforms.
TCAn.CMPn registers are updated with the buffer value from their corresponding TCAn.CMPnBUF
register when an UPDATE condition occurs.
The TCAn.CMPnL and TCAn.CMPnH register pair represents the 16-bit value, TCAn.CMPn. The low
byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at
offset + 0x01.
Bit
15
14
13
12
11
10
9
8
CMP[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
CMP[7:0]
Access
Reset
Bits 15:8 – CMP[15:8] Compare High Byte
These bits hold the MSB of the 16-bit compare register.
Bits 7:0 – CMP[7:0] Compare Low Byte
These bits hold the LSB of the 16-bit compare register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 224
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.17 Period Buffer Register
Name:
Offset:
Reset:
Property:
PERBUF
0x36
0xFFFF
-
This register serves as the buffer for the period register (TCAn.PER). Accessing this register using the
CPU or UPDI will affect the PERBV flag.
The TCAn.PERBUFL and TCAn.PERBUFH register pair represents the 16-bit value, TCAn.PERBUF. The
low byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed
at offset + 0x01.
Bit
15
14
13
12
11
10
9
8
PERBUF[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
1
1
1
1
1
1
1
1
Bit
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
1
1
1
1
1
1
1
1
PERBUF[7:0]
Access
Reset
Bits 15:8 – PERBUF[15:8] Period Buffer High Byte
These bits hold the MSB of the 16-bit period buffer register.
Bits 7:0 – PERBUF[7:0] Period Buffer Low Byte
These bits hold the LSB of the 16-bit period buffer register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 225
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.5.18 Compare n Buffer Register
Name:
Offset:
Reset:
Property:
CMPBUF
0x38 + n*0x02 [n=0..2]
0x00
-
This register serves as the buffer for the associated compare registers (TCAn.CMPn). Accessing any of
these registers using the CPU or UPDI will affect the corresponding CMPnBV status bit.
The TCAn.CMPnBUFL and TCAn.CMPnBUFH register pair represents the 16-bit value, TCAn.CMPnBUF.
The low byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be
accessed at offset + 0x01.
Bit
15
14
13
12
11
10
9
8
CMPBUF[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
CMPBUF[7:0]
Access
Reset
Bits 15:8 – CMPBUF[15:8] Compare High Byte
These bits hold the MSB of the 16-bit compare buffer register.
Bits 7:0 – CMPBUF[7:0] Compare Low Byte
These bits hold the LSB of the 16-bit compare buffer register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 226
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.6
Register Summary - TCA in Split Mode (CTRLD.SPLITM=1)
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
...
0x09
0x0A
0x0B
0x0C
...
0x0D
0x0E
0x0F
...
0x1F
0x20
0x21
0x22
...
0x25
0x26
0x27
0x28
0x29
0x2A
0x2B
0x2C
0x2D
CTRLA
CTRLB
CTRLC
CTRLD
CTRLECLR
CTRLESET
7:0
7:0
7:0
7:0
7:0
7:0
20.7
HCMP2EN
HCMP2OV
HCMP1EN
HCMP1OV
HCMP0EN
HCMP0OV
CLKSEL[2:0]
LCMP2EN
LCMP2OV
CMD[1:0]
CMD[1:0]
ENABLE
LCMP0EN
LCMP0OV
SPLITM
CMDEN[1:0]
CMDEN[1:0]
LCMP1EN
LCMP1OV
Reserved
INTCTRL
INTFLAGS
7:0
7:0
LCMP2
LCMP2
LCMP1
LCMP1
LCMP0
LCMP0
HUNF
HUNF
LUNF
LUNF
Reserved
DBGCTRL
7:0
DBGRUN
Reserved
LCNT
HCNT
7:0
7:0
LCNT[7:0]
HCNT[7:0]
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
LPER[7:0]
HPER[7:0]
LCMP[7:0]
HCMP[7:0]
LCMP[7:0]
HCMP[7:0]
LCMP[7:0]
HCMP[7:0]
Reserved
LPER
HPER
LCMP0
HCMP0
LCMP1
HCMP1
LCMP2
HCMP2
Register Description - Split Mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 227
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
-
6
5
4
3
2
1
CLKSEL[2:0]
Access
Reset
0
ENABLE
R/W
R/W
R/W
R/W
0
0
0
0
Bits 3:1 – CLKSEL[2:0] Clock Select
These bits select the clock frequency for the timer/counter.
Value
Name
Description
0x0
DIV1
fTCA = fCLK_PER/1
0x1
DIV2
fTCA = fCLK_PER/2
0x2
DIV4
fTCA = fCLK_PER/4
0x3
DIV8
fTCA = fCLK_PER/8
0x4
DIV16
fTCA = fCLK_PER/16
0x5
DIV64
fTCA = fCLK_PER/64
0x6
DIV256
fTCA = fCLK_PER/256
0x7
DIV1024
fTCA = fCLK_PER/1024
Bit 0 – ENABLE Enable
Value
Description
0
The peripheral is disabled
1
The peripheral is enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 228
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.2
Control B - Split Mode
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLB
0x01
0x00
-
6
5
4
HCMP2EN
HCMP1EN
R/W
R/W
0
0
3
2
1
0
HCMP0EN
LCMP2EN
LCMP1EN
LCMP0EN
R/W
R/W
R/W
R/W
0
0
0
0
Bit 6 – HCMP2EN High byte Compare 2 Enable
See LCMP0EN.
Bit 5 – HCMP1EN High byte Compare 1 Enable
See LCMP0EN.
Bit 4 – HCMP0EN High byte Compare 0 Enable
See LCMP0EN.
Bit 2 – LCMP2EN Low byte Compare 2 Enable
See LCMP0EN.
Bit 1 – LCMP1EN Low byte Compare 1 Enable
See LCMP0EN.
Bit 0 – LCMP0EN Low byte Compare 0 Enable
Setting the LCMPnEN/HCMPnEN bits in the FRQ or PWM Waveform Generation mode of operation will
override the port output register for the corresponding WOn pin.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 229
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.3
Control C - Split Mode
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLC
0x02
0x00
-
6
5
4
HCMP2OV
HCMP1OV
R/W
R/W
0
0
3
2
1
0
HCMP0OV
LCMP2OV
LCMP1OV
LCMP0OV
R/W
R/W
R/W
R/W
0
0
0
0
Bit 6 – HCMP2OV High byte Compare 2 Output Value
See LCMP0OV.
Bit 5 – HCMP1OV High byte Compare 1 Output Value
See LCMP0OV.
Bit 4 – HCMP0OV High byte Compare 0 Output Value
See LCMP0OV.
Bit 2 – LCMP2OV Low byte Compare 2 Output Value
See LCMP0OV.
Bit 1 – LCMP1OV Low byte Compare 1 Output Value
See LCMP0OV.
Bit 0 – LCMP0OV Low byte Compare 0 Output Value
The LCMPnOV/HCMPn bits allow direct access to the waveform generator's output compare value when
the timer/counter is not enabled. This is used to set or clear the WOn output value when the timer/counter
is not running.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 230
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.4
Control D
Name:
Offset:
Reset:
Property:
Bit
7
CTRLD
0x03
0x00
-
6
5
4
3
2
1
0
SPLITM
Access
R/W
Reset
0
Bit 0 – SPLITM Enable Split Mode
This bit sets the timer/counter in Split mode operation. It will then work as two 8-bit timer/counters. The
register map will change compared to normal 16-bit mode.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 231
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.5
Control Register E Clear - Split Mode
Name:
Offset:
Reset:
Property:
CTRLECLR
0x04
0x00
-
The individual Status bit can be cleared by writing a '1' to its bit location. This allows each bit to be
cleared without the use of a read-modify-write operation on a single register.
Bit
7
6
5
4
3
2
1
CMD[1:0]
Access
Reset
0
CMDEN[1:0]
R/W
R/W
R/W
R/W
0
0
0
0
Bits 3:2 – CMD[1:0] Command
These bits are used for software control of update, restart, and reset of the timer/counter. The command
bits are always read as '0'.
Value
Name
Description
0x0
NONE
No command
0x1
Reserved
0x2
RESTART
Force restart
0x3
RESET
Force hard Reset (ignored if TC is enabled)
Bits 1:0 – CMDEN[1:0] Command enable
These bits are used to indicate for which timer/counter the command (CMD) is valid.
Value
Name
Description
0x0
NONE
None
0x1
Reserved
0x2
Reserved
0x3
BOTH
Command valid for both low-byte and high-byte T/C
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 232
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.6
Control Register E Set - Split Mode
Name:
Offset:
Reset:
Property:
CTRLESET
0x05
0x00
-
The individual Status bit can be set by writing a '1' to its bit location. This allows each bit to be set without
the use of a read-modify-write operation on a single register.
Bit
7
6
5
4
3
2
1
CMD[1:0]
Access
Reset
0
CMDEN[1:0]
R/W
R/W
R/W
R/W
0
0
0
0
Bits 3:2 – CMD[1:0] Command
These bits are used for software control of update, restart, and reset of the timer/counter. The command
bits are always read as '0'. The CMD bits must be used together with CMDEN. Using the reset command
requires that both low-byte and high-byte timer/counter is selected.
Value
Name
Description
0x0
NONE
No command
0x1
Reserved
0x2
RESTART
Force restart
0x3
RESET
Force hard Reset (ignored if TC is enabled)
Bits 1:0 – CMDEN[1:0] Command enable
These bits are used to indicate for which timer/counter the command (CMD) is valid.
Value
Name
Description
0x0
NONE
None
0x1
Reserved
0x2
Reserved
0x3
BOTH
Command valid for both low-byte and high-byte T/C
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 233
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.7
Interrupt Control Register - Split Mode
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
INTCTRL
0x0A
0x00
-
6
5
4
LCMP2
LCMP1
R/W
R/W
0
0
3
2
1
0
LCMP0
HUNF
LUNF
R/W
R/W
R/W
0
0
0
Bit 6 – LCMP2 Low byte Compare Channel 0 Interrupt Enable
See LCMP0.
Bit 5 – LCMP1 Low byte Compare Channel 1 Interrupt Enable
See LCMP0.
Bit 4 – LCMP0 Low byte Compare Channel 0 Interrupt Enable
Writing LCMPn bit to '1' enables low byte compare interrupt from channel n.
Bit 1 – HUNF High byte Underflow Interrupt Enable
Writing HUNF bit to '1' enables high byte underflow interrupt.
Bit 0 – LUNF Low byte Underflow Interrupt Enable
Writing HUNF bit to '1' enables low byte underflow interrupt.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 234
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.8
Interrupt Flag Register - Split Mode
Name:
Offset:
Reset:
Property:
INTFLAGS
0x0B
0x00
-
The individual Status bit can be cleared by writing a ‘1’ to its bit location. This allows each bit to be set
without the use of a read-modify-write operation on a single register.
Bit
Access
Reset
7
6
5
4
1
0
LCMP2
LCMP1
LCMP0
3
2
HUNF
LUNF
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
Bit 6 – LCMP2 Low byte Compare Channel 0 Interrupt Flag
See LCMP0 flag description.
Bit 5 – LCMP1 Low byte Compare Channel 0 Interrupt Flag
See LCMP0 flag description.
Bit 4 – LCMP0 Low byte Compare Channel 0 Interrupt Flag
The Compare Interrupt flag (LCMPn) is set on a compare match on the corresponding compare channel.
For all modes of operation, the LCMPn flag will be set when a compare match occurs between the Low
Byte Count register (TCAn.LCNT) and the corresponding compare register (TCAn.LCMPn). The LCMPn
flag will not be cleared automatically and has to be cleared by software. This is done by writing a ‘1’ to its
bit location.
Bit 1 – HUNF High byte Underflow Interrupt Flag
This flag is set on a high byte timer BOTTOM (underflow) condition. HUNF is not automatically cleared
and needs to be cleared by software. This is done by writing a ‘1’ to its bit location.
Bit 0 – LUNF Low byte Underflow Interrupt Flag
This flag is set on a low byte timer BOTTOM (underflow) condition. LUNF is not automatically cleared and
needs to be cleared by software. This is done by writing a ‘1’ to its bit location.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 235
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.9
Debug Control Register
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x0E
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Run in Debug
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 236
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.10 Low Byte Timer Counter Register - Split Mode
Name:
Offset:
Reset:
Property:
LCNT
0x20
0x00
-
TCAn.LCNT contains the counter value in low byte timer. CPU and UPDI write access has priority over
count, clear, or reload of the counter.
Bit
7
6
5
4
3
2
1
0
LCNT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – LCNT[7:0] Counter Value for Low Byte Timer
These bits define the counter value of the low byte timer.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 237
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.11 High Byte Timer Counter Register - Split Mode
Name:
Offset:
Reset:
Property:
HCNT
0x21
0x00
-
TCAn.HCNT contains the counter value in high byte timer. CPU and UPDI write access has priority over
count, clear, or reload of the counter.
Bit
7
6
5
4
3
2
1
0
HCNT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – HCNT[7:0] Counter Value for High Byte Timer
These bits define the counter value in high byte timer.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 238
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.12 Low Byte Timer Period Register - Split Mode
Name:
Offset:
Reset:
Property:
LPER
0x26
0x00
-
The TCAn.LPER register contains the TOP value of low byte timer.
Bit
7
6
5
4
3
2
1
0
LPER[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
1
1
1
1
1
1
1
1
Bits 7:0 – LPER[7:0] Period Value Low Byte Timer
These bits hold the TOP value of low byte timer.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 239
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.13 High Byte Period Register - Split Mode
Name:
Offset:
Reset:
Property:
HPER
0x27
0x00
-
The TCAn.HPER register contains the TOP value of high byte timer.
Bit
7
6
5
4
3
2
1
0
HPER[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
1
1
1
1
1
1
1
1
Bits 7:0 – HPER[7:0] Period Value High Byte Timer
These bits hold the TOP value of high byte timer.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 240
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.14 Compare Register n For Low Byte Timer - Split Mode
Name:
Offset:
Reset:
Property:
LCMP
0x28 + n*0x02 [n=0..2]
0x00
-
The TCAn.LCMPn register represents the compare value of compare channel n for low byte timer. This
register is continuously compared to the counter value of the low byte timer, TCAn.LCNT. Normally, the
outputs from the comparators are then used for generating waveforms.
Bit
7
6
5
4
3
2
1
0
LCMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – LCMP[7:0] Compare Value of Channel n
These bits hold the compare value of channel n that is compared to TCAn.LCNT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 241
ATtiny1616/3216
TCA - 16-bit Timer/Counter Type A
20.7.15 High Byte Compare Register n - Split Mode
Name:
Offset:
Reset:
Property:
HCMP
0x29 + n*0x02 [n=0..2]
0x00
-
The TCAn.HCMPn register represents the compare value of compare channel n for high byte timer. This
register is continuously compared to the counter value of the high byte timer, TCAn.HCNT. Normally, the
outputs from the comparators are then used for generating waveforms.
Bit
7
6
5
4
3
2
1
0
HCMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – HCMP[7:0] Compare Value of Channel n
These bits hold the compare value of channel n that is compared to TCAn.HCNT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 242
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.
TCB - 16-bit Timer/Counter Type B
21.1
Features
• 16-Bit Counter Operation Modes:
– Periodic interrupt
– Time-out check
– Input capture
• On event
• Frequency measurement
• Pulse-width measurement
• Frequency and pulse-width measurement
– Single shot
– 8-bit Pulse-Width Modulation (PWM)
• Noise Canceler on Event Input
• Optional: Operation Synchronous with TCA0
21.2
Overview
The capabilities of the 16-bit Timer/Counter type B (TCB) include frequency and waveform generation,
and input capture on event with time and frequency measurement of digital signals. The TCB consists of
a base counter and control logic which can be set in one of eight different modes, each mode providing
unique functionality. The base counter is clocked by the peripheral clock with optional prescaling.
This device has two instances of the TCB peripheral: TCB0 and TCB1.
21.2.1
Block Diagram
Figure 21-1. Timer/Counter Type B Block Diagram
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 243
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
TCB
ClockSelect
CTRLA
Mode
CTRLB
EVCTRL
Edge Select
CCMP
DIV2
Counter
"count"
"clear"
CNT
CLK_PER
Control
Logic
CLK_TCA
Event System
IF
(INT Req.)
=
TOP
BOTTOM
=0
Mode, Output enable, initial value
Synchronous
output
Output control
and
Asynchronous logic
Asynchronous
output
21.2.1.1 Noise Canceler
The noise canceler improves noise immunity by using a simple digital filter scheme. When the noise filter
is enabled, the peripheral monitors the event channel and keeps a record of the last four observed
samples. If four consecutive samples are equal, the input is considered to be stable and the signal is fed
to the edge detector.
When enabled, the noise canceler introduces an additional delay of four system clock cycles between a
change applied to the input and the update of the input compare register.
The noise canceler uses the system clock and is, therefore, not affected by the prescaler.
21.2.2
Signal Description
Signal
Description
Type
WO
Digital Asynchronous Output
Waveform Output
Related Links
5. I/O Multiplexing and Considerations
21.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 21-1. TCB System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
WO
Interrupts
Yes
CPUINT
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 244
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
...........continued
Dependency
Applicable
Peripheral
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
21.2.3.1 Clocks
21.2.3.5 Debug Operation
21.2.3.3 Interrupts
21.2.3.4 Events
21.2.3.1 Clocks
This peripheral uses the system's peripheral clock CLK_PER. The peripheral has its own local prescaler
or can be configured to run off the prescaled clock signal of the Timer Counter type A (TCA).
Related Links
10. CLKCTRL - Clock Controller
21.2.3.2 I/O Lines and Connections
Using the I/O lines of the peripheral requires configuration of the I/O pins.
Related Links
5. I/O Multiplexing and Considerations
16. PORT - I/O Pin Configuration
21.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
21.3.5 Interrupts
21.2.3.4 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
21.2.3.5 Debug Operation
When the CPU is halted in Debug mode, this peripheral will halt normal operation. This peripheral can be
forced to continue operation during debugging.
This peripheral can be forced to operate with halted CPU by writing a '1' to the Debug Run bit (DBGRUN)
in the Debug Control register of the peripheral (peripheral.DBGCTRL).
Related Links
33. UPDI - Unified Program and Debug Interface
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 245
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.3
Functional Description
21.3.1
Definitions
The following definitions are used throughout the documentation:
Table 21-2. Timer/Counter Definitions
Name
Description
BOTTOM The counter reaches BOTTOM when it becomes zero.
MAX
The counter reaches MAXimum when it becomes all ones.
TOP
The counter reaches TOP when it becomes equal to the highest value in the count
sequence.
UPDATE The update condition is met when the timer/counter reaches BOTTOM or TOP, depending on
the Waveform Generator mode.
CNT
Counter register value.
CCMP
Capture/Compare register value.
In general, the term timer is used when the timer/counter is counting periodic clock ticks. The term
counter is used when the input signal has sporadic or irregular ticks.
21.3.2
Initialization
By default, the TCB is in Periodic Interrupt mode. Follow these steps to start using it:
• Write a TOP value to the Compare/Capture register (TCBn.CCMP).
• Enable the counter by writing a '1' to the ENABLE bit in the Control A register (TCBn.CTRLA).
The counter will start counting clock ticks according to the prescaler setting in the Clock Select bit
field (CLKSEL in TCBn.CTRLA).
• The counter value can be read from the Count register (TCBn.CNT). The peripheral will generate an
interrupt when the CNT value reaches TOP.
21.3.3
Operation
21.3.3.1 Modes
The timer can be configured to run in one of the eight different modes listed below. The event pulse
needs to be longer than one system clock cycle in order to ensure edge detection.
21.3.3.1.1 Periodic Interrupt Mode
In the Periodic Interrupt mode, the counter counts to the capture value and restarts from zero. An
interrupt is generated when the counter is equal to TOP. If TOP is updated to a value lower than count,
the counter will continue until MAX and wrap around without generating an interrupt.
Figure 21-2. Periodic Interrupt Mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 246
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
TOP changed to a value
lower than CNT
Counter wraps around
MAX
"Interrupt"
TOP
CNT
BOTTOM
21.3.3.1.2 Time-Out Check Mode
In this mode, the counter counts to MAX and wraps around. On the first edge the counter is restarted and
on the second edge, the counter is stopped. If the count register (TCBn.CNT) reaches TOP before the
second edge, an interrupt will be generated. In Freeze state, the counter will restart on a new edge.
Reading count (TCBn.CNT) or compare/capture (TCBn.CCMP) register, or writing run bit (RUN in
TCBn.STATUS) in Freeze state will have no effect.
Figure 21-3. Time-Out Check Mode
Event Input
TOP changed to a value
lower than CNT
Edge detector
Counter wraps
around
MAX
“ Inter rupt”
CNT
TOP
BOTTOM
21.3.3.1.3 Input Capture on Event Mode
The counter will count from BOTTOM to MAX continuously. When an event is detected the counter value
will be transferred to the Compare/Capture register (TCBn.CCMP) and interrupt is generated. The module
has an edge detector that can be configured to trigger count capture on either rising or falling edges.
The figure below shows the input capture unit configured to capture on falling edge on the event input
signal. The interrupt flag is automatically cleared after the high byte of the Capture register has been
read.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 247
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
Figure 21-4. Input Capture on Event
" Interrupt"
Event Input
Edge detector
MAX
CNT
BOTTOM
Copy CNT to CCMP
and interrupt
Wraparound
Copy CNT to CCMP
and interrupt
It is recommended to write '0' to the TCBn.CNT register when entering this mode from any other mode.
21.3.3.1.4 Input Capture Frequency Measurement Mode
In this mode, the TCB captures the counter value and restarts on either a positive or negative edge of the
event input signal.
The interrupt flag is automatically cleared after the high byte of the Compare/Capture register
(TCBn.CCMP) has been read, and an interrupt request is generated.
The figure below illustrates this mode when configured to act on rising edge.
Figure 21-5. Input Capture Frequency Measurement
" Interrupt "
Event Input
Edge detector
MAX
CNT
BOTTOM
Copy CNT to CCMP,
interrupt and restart
© 2019 Microchip Technology Inc.
Copy CNT to CCMP,
interrupt and restart
Preliminary Datasheet
Copy CNT to CCMP,
interrupt and restart
40001997C-page 248
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.3.3.1.5 Input Capture Pulse-Width Measurement Mode
The input capture pulse-width measurement will restart the counter on a positive edge and capture on the
next falling edge before an interrupt request is generated. The interrupt flag is automatically cleared when
the high byte of the capture register is read. The timer will automatically switch between rising and falling
edge detection, but a minimum edge separation of two clock cycles is required for correct behavior.
Figure 21-6. Input Capture Pulse-Width Measurement
" Interrupt "
Event Input
Edge detector
MAX
CNT
BOTTOM
Restart
counter
Copy CNT to CCMP
and interrupt
Restart
counter
Copy CNT to CCMP
and give interrupt
Restart
counter
21.3.3.1.6 Input Capture Frequency and Pulse-Width Measurement Mode
In this mode, the timer will start counting when a positive edge is detected on the Event Input signal. On
the following falling edge, the count value is captured. The counter stops when the second rising edge of
the Event Input signal is detected and this will set the interrupt flag.
Reading the capture will clear the interrupt flag. When the capture register is read or the interrupt flag is
cleared the TC is ready for a new capture sequence. Therefore, read the counter register before the
capture register since it is reset to zero at the next positive edge.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 249
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
Figure 21-7. Input Capture Frequency and Pulse-Width Measurement
Ignore till
Capture is read
Trigger next
capture sequence
Event Input
Edge detector
MAX
" Interrupt"
CNT
BOTTOM
Start
counter
Copy CNT to
CCMP
Stop counter and
interrupt
CPU reads the
CCMP register
21.3.3.1.7 Single-Shot Mode
This mode can be used to generate a pulse with a duration that is defined by the Compare register
(TCBn.CCMP), every time a rising or falling edge is observed on a connected event channel.
When the counter is stopped, the output pin is driven to low. If an event is detected on the connected
event channel, the timer will reset and start counting from zero to TOP while driving its output high. The
RUN bit in the STATUS register can be read to see if the counter is counting or not. When the counter
register reaches the CCMP register value, the counter will stop and the output pin will go low for at least
one prescaler cycle. If a new event arrives during this time, that event will be ignored. The following figure
shows an example waveform. There is a two clock cycle delay from when the event is received until the
output is set high.
The counter will start counting as soon as the module is enabled, even without triggering an event. This is
prevented by writing TOP to the counter register. Similar behavior is seen if the EDGE bit in the
TCBn.EVCTRL register is '1' while the module is enabled. Writing TOP to the Counter register prevents
this as well.
If the ASYNC bit in TCBn.CTRLB is written to '1', the timer is reacting asynchronously to an incoming
event. An edge on the event will immediately cause the output signal to be set. The counter will still start
counting two clock cycles after the event is received.
Figure 21-8. Single-Shot Mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 250
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
Ignored
Ignored
Edge detector
TOP
CNT
" Interrupt"
BOTTOM
Output
Counter reaches
TOP value
Event starts
counter
Event starts
counter
Counter reaches
TOP value
21.3.3.1.8 8-Bit PWM Mode
This timer can be configured to run in 8-bit PWM mode where each of the register pairs in the 16-bit
Compare/Capture register (TCBn.CCMPH and TCBn.CCMPL) are used as individual compare registers.
The counter will continuously count from zero to CCMPL and the output will be set at BOTTOM and
cleared when the counter reaches CCMPH.
When this peripheral is enabled and in PWM mode, changing the value of the Compare/Capture register
will change the output, but the transition may output invalid values. It is hence recommended to:
1. Disable the peripheral.
2. Write Compare/Capture register to {CCMPH, CCMPL}.
3. Write 0x0000 to count register.
4. Re-enable the module.
CCMPH is the number of cycles for which the output will be driven high, CCMPL+1 is the period of the
output pulse.
For different capture register values the output values are:
• CCMPL = 0
Output = 0
• CCMPL = 0xFF
• CCMPH = 0
Output = 0
• 0 < CCMPH ≤ 0xFF
Output = 1 for CCMPH cycles, low for the rest of the period
• For 0 < CCMPL < 0xFF
• CCMPH = 0
Output = 0
• If 0 < CCMPH ≤ CCMPL
• CCMPH = CCMPL + 1
Output = 1 for CCMPH cycles, low for the rest of the period
Output = 1
Figure 21-9. 8-Bit PWM Mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 251
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
" Interrupt "
CCMPL
CNT
CCMPH
BOTTOM
Output
(CNT == CCMPL) and
output goes high
(CNT == CCMPH) and
output goes low
21.3.3.2 Output
If ASYNC in TCBn.CTRLB is written to '0' ('1'), the output pin is driven synchronously (asynchronously) to
the TCB clock. The CCMPINIT, CCMPEN, and CNTMODE bits in TCBn.CTRLB control how the
synchronous output is driven. The different configurations and their impact on the output are listed in the
table below.
Table 21-3. Synchronous Output
CNTMODE
Output, CTRLB=’0’,
CCMPEN=1
Output, CTRLB=’1’,
CCMPEN=1
Single-Shot mode
Output high when the counter
starts and output low when the
counter stops
Output high when event arrives
and output low when the counter
stops
8-bit PWM mode
PWM mode output
PWM mode output
Modes except single shot and
PWM
Bit CCMPINIT in TCBn.CTRLB
Bit CCMPINIT in TCBn.CTRLB
21.3.3.3 Noise Canceler
The noise canceler improves noise immunity by using a simple digital filter scheme. When the noise filter
is enabled, the peripheral monitors the event channel and keeps a record of the last four observed
samples. If four consecutive samples are equal, the input is considered to be stable and the signal is fed
to the edge detector.
When enabled, the noise canceler introduces an additional delay of four system clock cycles between a
change applied to the input and the update of the input compare register.
The noise canceler uses the system clock and is, therefore, not affected by the prescaler.
21.3.3.4 Synchronized with TCAn
TCB can be configured to use the clock (CLK_TCA) of the Timer/Counter type A (TCAn) by writing to the
Clock Select bit field (CLKSEL) in the Control A register (TCBn.CTRLA). In this setting, the TCB will count
on the exact same clock source as selected in TCA.
When the Synchronize Update bit (SYNCUPD) in the Control A register (TCBn.CTRLA) is written to ‘1’,
the TCB counter will restart when the TCA counter restarts.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 252
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
Related Links
21.2.1 Block Diagram
21.3.4
Events
The TCB is an event generator. Any condition that causes the CAPT flag in TCBn.INTFLAGS to be set
will also generate a one-cycle strobe on the event channel output.
The peripheral accepts one event input. If the Capture Event Input Enable bit (CAPTEI) in the Event
Control register (TCBn.EVCTRL) is written to '1', incoming events will result in an event action as defined
by the Event Edge bit (EDGE) in TCBn.EVCTRL. The event needs to last for at least one CLK_PER cycle
to ensure that it is recognized.
If the Asynchronous mode is enabled for Single-Shot mode, the event is edge triggered and will capture
changes on the event input shorter than one system clock cycle.
Related Links
21.5.3 EVCTRL
14. EVSYS - Event System
21.3.5
Interrupts
Table 21-4. Available Interrupt Vectors and Sources
Offset Name Vector Description Conditions
0x00
CAPT TCB interrupt
Depending on operating mode. See description of CAPT in
TCB.INTFLAG.
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding enable bit in the peripheral's
Interrupt Control register (peripheral.INTCTRL).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
Related Links
13. CPUINT - CPU Interrupt Controller
21.5.5 INTFLAGS
21.3.6
Sleep Mode Operation
TCB will halt operation in the Power-Down Sleep mode. Standby sleep operation is dependent on the
Run in Standby bit (RUNSTDBY) in the Control A register (TCB.CTRLA).
21.3.7
Synchronization
Not applicable.
21.3.8
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 253
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.4
Register Summary - TCB
Offset
Name
Bit Pos.
0x00
0x01
0x02
...
0x03
0x04
0x05
0x06
0x07
0x08
0x09
CTRLA
CTRLB
7:0
7:0
RUNSTDBY
ASYNC
EVCTRL
INTCTRL
INTFLAGS
STATUS
DBGCTRL
TEMP
FILTER
0x0A
CNT
0x0C
CCMP
7:0
7:0
7:0
7:0
7:0
7:0
7:0
15:8
7:0
15:8
21.5
CCMPINIT
SYNCUPD
CCMPEN
CLKSEL[1:0]
CNTMODE[2:0]
ENABLE
Reserved
EDGE
CAPTEI
CAPT
CAPT
RUN
DBGRUN
TEMP[7:0]
CNT[7:0]
CNT[15:8]
CCMP[7:0]
CCMP[15:8]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 254
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLA
0x00
0x00
-
6
5
4
3
2
1
0
RUNSTDBY
SYNCUPD
R/W
R/W
R/W
CLKSEL[1:0]
R/W
ENABLE
R/W
0
0
0
0
0
Bit 6 – RUNSTDBY Run in Standby
Writing a '1' to this bit will enable the peripheral to run in Standby Sleep mode. Not applicable when
CLKSEL is set to 0x2 (CLK_TCA).
Bit 4 – SYNCUPD Synchronize Update
When this bit is written to '1', the TCB will restart whenever the TCA0 counter is restarted.
Bits 2:1 – CLKSEL[1:0] Clock Select
Writing these bits selects the clock source for this peripheral.
Value
Description
0x0
CLK_PER
0x1
CLK_PER/2
0x2
Use CLK_TCA from TCA0
0x3
Reserved
Bit 0 – ENABLE Enable
Writing this bit to '1' enables the Timer/Counter type B peripheral.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 255
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.2
Control B
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLB
0x01
0x00
-
6
5
4
3
2
1
0
ASYNC
CCMPINIT
CCMPEN
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
CNTMODE[2:0]
Bit 6 – ASYNC Asynchronous Enable
Writing this bit to ‘1’ allows asynchronous updates of the TCB output signal in Single-Shot mode.
Value
Description
0
The output will go HIGH when the counter actually starts
1
The output will go HIGH when an event arrives
Bit 5 – CCMPINIT Compare/Capture Pin Initial Value
This bit is used to set the initial output value of the pin when a pin output is used.
Value
Description
0
Initial pin state is LOW
1
Initial pin state is HIGH
Bit 4 – CCMPEN Compare/Capture Output Enable
This bit is used to enable the output signal of the Compare/Capture.
Value
Description
0
Compare/Capture Output is zero
1
Compare/Capture Output has a valid value
Bits 2:0 – CNTMODE[2:0] Timer Mode
Writing these bits selects the Timer mode.
Value
Description
0x0
Periodic Interrupt mode
0x1
Time-out Check mode
0x2
Input Capture on Event mode
0x3
Input Capture Frequency Measurement mode
0x4
Input Capture Pulse-Width Measurement mode
0x5
Input Capture Frequency and Pulse-Width Measurement mode
0x6
Single-Shot mode
0x7
8-Bit PWM mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 256
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.3
Event Control
Name:
Offset:
Reset:
Property:
Bit
EVCTRL
0x04
0x00
-
7
Access
Reset
6
5
4
3
2
1
0
FILTER
EDGE
CAPTEI
R/W
R/W
R/W
0
0
0
Bit 6 – FILTER Input Capture Noise Cancellation Filter
Writing this bit to '1' enables the input capture noise cancellation unit.
Bit 4 – EDGE Event Edge
This bit is used to select the event edge. The effect of this bit is dependent on the selected Count Mode
(CNTMODE) in TCBn.CTRLB. "-" means that an event or edge has no effect in this mode.
Count Mode
EDGE Positive Edge
Negative Edge
Periodic Interrupt mode
0
-
-
1
-
-
0
Start counter
Stop counter
1
Stop counter
Start counter
0
Input Capture, interrupt
-
1
-
Input Capture, interrupt
0
Input Capture, clear and
restart counter, interrupt
-
1
-
Input Capture, clear and
restart counter, interrupt
Input Capture Pulse-Width
Measurement mode
0
Clear and restart counter
Input Capture, interrupt
1
Input Capture, interrupt
Clear and restart counter
Input Capture Frequency and
Pulse-Width Measurement mode
0
On 1st Positive: Clear and restart counter
Timeout Check mode
Input Capture on Event mode
Input Capture Frequency
Measurement mode
On following Negative: Input Capture
2nd Positive: Stop counter, interrupt
1
On 1st Negative: Clear and restart counter
On following Positive: Input Capture
2nd Negative: Stop counter, interrupt
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 257
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
...........continued
Count Mode
EDGE Positive Edge
Negative Edge
Single-Shot mode
0
Start counter
-
1
Start counter
Start counter
0
-
-
1
-
-
8-Bit PWM mode
Bit 0 – CAPTEI Capture Event Input Enable
Writing this bit to '1' enables the input capture event.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 258
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.4
Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
INTCTRL
0x05
0x00
-
6
5
4
3
2
1
0
CAPT
Access
R/W
Reset
0
Bit 0 – CAPT Capture Interrupt Enable
Writing this bit to '1' enables the capture interrupt.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 259
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.5
Interrupt Flags
Name:
Offset:
Reset:
Property:
Bit
INTFLAGS
0x06
0x00
-
7
6
5
4
3
2
1
0
CAPT
Access
R/W
Reset
0
Bit 0 – CAPT Interrupt Flag
This bit is set when an interrupt occurs. The interrupt conditions are dependent on the Counter Mode
(CNTMODE) in TCBn.CTRLB.
This bit is cleared by writing a '1' to it or when the Capture register is read in Capture mode.
Counter Mode
Interrupt Flag Behavior
Periodic Interrupt mode
Set when the counter reaches TOP
Timeout Check mode
Set when the counter reaches TOP
Input Capture on Event mode
Set when an event occurs and the Capture register is loaded,
cleared when Capture is read
Input Capture Frequency
Measurement mode
Set on an edge when the Capture register is loaded and count
initialized, cleared when Capture is read
Input Capture Pulse-Width
Measurement mode
Set on an edge when the Capture register is loaded, the previous
edge initialized the count, cleared when Capture is read
Input Capture Frequency and Pulse- Set on second (positive or negative) edge when the counter is
Width Measurement mode
stopped, cleared when Capture is read
Single-Shot mode
Set when the counter reaches TOP
8-Bit PWM mode
Set when the counter reaches CCMPL
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 260
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.6
Status
Name:
Offset:
Reset:
Property:
Bit
7
STATUS
0x07
0x00
-
6
5
4
3
2
1
0
RUN
Access
R
Reset
0
Bit 0 – RUN Run
When the counter is running, this bit is set to '1'. When the counter is stopped, this bit is cleared to '0'.
The bit is read-only and cannot be set by UPDI.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 261
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.7
Debug Control
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x08
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Debug Run
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 262
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.8
Temporary Value
Name:
Offset:
Reset:
Property:
TEMP
0x09
0x00
-
The Temporary register is used by the CPU for single-cycle, 16-bit access to the 16-bit registers of this
peripheral. It can be read and written by software. Refer to 16-bit access in the AVR CPU chapter. There
is one common Temporary register for all the 16-bit registers of this peripheral.
Bit
7
6
5
4
3
2
1
0
TEMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – TEMP[7:0] Temporary Value
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 263
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.9
Count
Name:
Offset:
Reset:
Property:
CNT
0x0A
0x00
-
The TCBn.CNTL and TCBn.CNTH register pair represents the 16-bit value TCBn.CNT. The low byte [7:0]
(suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset
+ 0x01.
CPU and UPDI write access has priority over internal updates of the register.
Bit
15
14
13
12
11
10
9
8
CNT[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
CNT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – CNT[15:8] Count Value High
These bits hold the MSB of the 16-bit Counter register.
Bits 7:0 – CNT[7:0] Count Value Low
These bits hold the LSB of the 16-bit Counter register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 264
ATtiny1616/3216
TCB - 16-bit Timer/Counter Type B
21.5.10 Capture/Compare
Name:
Offset:
Reset:
Property:
CCMP
0x0C
0x00
-
The TCBn.CCMPL and TCBn.CCMPH register pair represents the 16-bit value TCBn.CCMP. The low
byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at
offset + 0x01.
This register has different functions depending on the mode of operation:
• For capture operation, these registers contain the captured value of the counter at the time the
capture occurs
• In periodic interrupt/time-out and Single-Shot mode, this register acts as the TOP value
• In 8-bit PWM mode, TCBn.CCMPL and TCBn.CCMPH act as two independent registers
Bit
15
14
13
12
11
10
9
8
R/W
R/W
R/W
R/W
Reset
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
CCMP[15:8]
Access
CCMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – CCMP[15:8] Capture/Compare Value High Byte
These bits hold the MSB of the 16-bit compare, capture, and top value.
Bits 7:0 – CCMP[7:0] Capture/Compare Value Low Byte
These bits hold the LSB of the 16-bit compare, capture, and top value.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 265
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.
TCD - 12-Bit Timer/Counter Type D
22.1
Features
•
•
•
•
•
•
•
•
22.2
12-bit Timer/Counter
Programmable Prescaler
Double-Buffered Compare Registers
Waveform Generation:
– One Ramp mode
– Two Ramp mode
– Four Ramp mode
– Dual-Slope mode
Two Separate Input Capture, Double-Buffered
Connection to Event System by Programmable Filter
Conditional Waveform on External Events:
– Fault handling
– Input blanking
– Overload protection function
– Fast emergency stop by hardware
Supports Both Half Bridge and Full Bridge Output
Overview
The Timer/Counter type D (TCD) is a high-performance waveform controller that consists of an
asynchronous counter, a prescaler, compare logic, capture logic, and control logic. The purpose of the
TCD is to control power applications like LED, motor control, H-bridge, and power converters.
The TCD contains a counter that can run on a clock which is asynchronous from the system clock. It
contains compare logic that can generate two independent outputs with optional dead time. It is
connected to the event system for capture and deterministic fault control. The timer/counter can generate
interrupts and events on compare match and overflow.
This device provides one instance of the TCD peripheral, TCD0.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 266
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.2.1
Block Diagram
Figure 22-1. Timer/Counter Block Diagram
System
Clock
domain
TCD clock
domain
Counter and
Fractional
Accumulator
CMPASET
CMPASET_
BUF
=
CMPACLR
SET A
CMPACLR_
BUF
Event Input A
WOA
Event Input
Logic A
CAPTUREA
CAPTUREA_
BUF
CMPBSET
CMPBSET_
BUF
=
WOC
Compare/Capture
Unit B
WOD
SET B
CMPBCLR_
BUF
Waveform
generator B
WOB
CLR B
=
Event Input
Logic B
Event Input B
CAPTUREB
Waveform
generator A
CLR A
=
CMPBCLR
Compare/Capture
Unit A
CAPTUREB_
BUF
The TCD core is asynchronous to the system clock. The timer/counter consist of two compare/capture
units, each with a separate waveform output. In addition, there are two extra waveform outputs which can
be equal to the output from one of the units. The compare registers CMPxSET and CMPxCLR are stored
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 267
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
in the respective registers (TCDn.CMPxSET, TCDn.CMPxCLR), which consists of both a low and a high
byte. The registers are synchronized to the TCD domain after writing to the registers.
During normal operation, the counter value is continuously compared to the compare registers. This is
used to generate both interrupts and events.
The TCD can use the input events in ten different input modes, selected separately for the two input
events. The input mode defines how the input event will affect the outputs, and where in the TCD cycle
the counter should go when an event occurs.
22.2.2
22.2.3
Signal Description
Signal
Description
Type
WOA
TCD waveform output A
Digital output
WOB
TCD waveform output B
Digital output
WOC
TCD waveform output C
Digital output
WOD
TCD waveform output D
Digital output
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 22-1. TCD System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
WOA/B/C/D
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
22.2.3.1 Clocks
22.2.3.5 Debug Operation
22.2.3.3 Interrupts
22.2.3.4 Events
22.2.3.1 Clocks
The TCD can be connected directly to the internal 16/20 MHz RC Oscillator (OSC20M), to an external
clock, or to the system clock. This is configured by the Clock Select bit field (CLKSEL) in the Control A
register (TCD.CTRLA).
Related Links
10. CLKCTRL - Clock Controller
22.2.3.2 I/O Lines and Connections
Using the I/O lines of the peripheral requires configuration of the I/O pins.
Related Links
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 268
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
5. I/O Multiplexing and Considerations
16. PORT - I/O Pin Configuration
22.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
22.3.4 Interrupts
22.2.3.4 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
22.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
This peripheral can be forced to operate with halted CPU by writing a '1' to the Debug Run bit (DBGRUN)
in the Debug Control register of the peripheral (peripheral.DBGCTRL).
When the Fault Detection bit (FAULTDET in TCDn.DBGCTRL) is written to '1' and the CPU is halted in
Debug mode, an event/fault is created on both input event channels. These events/faults will last as long
as the break and can serve as a safeguard in Debug mode, e.g. by forcing external components OFF.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
Related Links
33. UPDI - Unified Program and Debug Interface
22.2.4
Definitions
The following definitions are used throughout the documentation:
Table 22-2. Timer/Counter Definitions
Name
Description
TCD cycle
The sequence of four states that the counter needs to go through before it
has returned to the same position.
Input Blanking
Functionality to ignore event input for a programmable time in a selectable
part of the TCD cycle.
Asynchronous output
control
Allows the Event to override the output instantly when the Event occurs. It is
used for handling non-recoverable faults.
One ramp
Counter is reset to zero once during a TCD cycle.
Two ramp
Counter is reset to zero two times during a TCD cycle.
Four ramp
Counter is reset to zero four times during a TCD cycle.
Dual ramp
Counter counts both up and down between zero and selected top value.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 269
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.3
Functional Description
22.3.1
Initialization and Disabling
To initialize the TCD:
1. Configure the static registers to the desired functionality.
2. Write desired initial values to the double-buffered registers.
3. Ensure that the Enable Ready bit (ENRDY) in the Status register (TCDn.STATUS) is set to '1'.
4. Enable the TCD by writing a '1' to the ENABLE bit in the Control A register (TCDn.CTRLA).
It is possible to disable the TCD in two different ways:
1. By writing a '0' to ENABLE in TCDn.CTRLA. This disables the TCD instantly when synchronized to
the TCD core domain.
2. By writing a '1' to the Disable at End of Cycle Strobe bit (DISEOC) in the Control E register
(TCDn.CTRLE). This disables the TCD at the end of the TCD cycle.
The bit fields in the TCDn.CTRLA register are enable-protected, with exception of the ENABLE bit. They
can only be written when ENABLE is written to '0' first.
Related Links
22.3.2.1 Register Synchronization Categories
22.3.2
Operation
22.3.2.1 Register Synchronization Categories
Most of the I/O registers need to be synchronized to the asynchronous TCD core clock domain. This is
done in different ways for different register categories:
•
•
•
•
Command and Enable Control registers
Double-buffered registers
Static registers
Normal I/O and STATUS registers
See Table 22-3 for categorized registers.
Command and Enable Registers
Because of synchronization between the clock domains, it is only possible to change the Enable bits
while the Enable Ready bit (ENRDY) in the Status register (TCDn.STATUS) is '1'.
The Control E register commands (TCDn.CTRLE) are automatically synchronized to the TCD core
domain when the TCD is enabled and as long as no synchronization is ongoing already. Check if the
Command Ready bit (CCMDRDY) is '1' in TCDn.STATUS to ensure that it is possible to write a new
command. TCDn.CTRLE is a strobe register that will clear itself when the command is done.
The Control E register commands are:
• Synchronize at the end of the TCD cycle: Synchronizes all double-buffered registers to TCD clock
domain at the end of the TCD cycle.
• Synchronize: Synchronizes all double-buffered registers to the TCD clock domain when the
command is synchronized to the TCD clock domain.
• Restart: Restarts the TCD counter.
• Software Capture A: Capture the TCD counter value to TCDn.CAPTUREA.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 270
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
• Software Capture B: Capture the TCD counter value to TCDn.CAPTUREB.
Double-Buffered Registers
The double-buffered registers can be updated in normal I/O writes while TCD is enabled and no
synchronization between the two clock domains is ongoing. Check that the CMDRDY bit in
TCDn.STATUS is '1' to ensure that it is possible to update the double-buffered I/O registers. The values
will be synchronized to the TCD core domain when a synchronization command is sent or when TCD is
enabled.
Static Registers
The static registers are kept static whenever TCD is enabled. This means that these registers must be
configured before enabling TCD. It is not possible to write to these registers as long as TCD is enabled.
To see if TCD is enabled, check if ENABLE in TCDn.CTRLA is reading '1'.
Normal I/O and Status Registers
The read-only registers inform about synchronization status and values synchronized from the core
domain. The reset of these registers and normal I/O registers are not constrained by any synchronization
between the domains.
Table 22-3. Categorization of Registers
Enable and
Command
Registers
Double-Buffered
Registers
Static Registers
Read-Only
Registers
Normal I/O
Registers
CTRLA
(ENABLE
bit)
TCDn.DLYCTRL
TCDn.CTRLA (All bits
Except ENABLE bit)
TCDn.STATUS
TCDn.INTCTRL
CTRLE
TCDn.DLYVAL
TCDn.CTRLB
TCDn.CAPTUREA
TCDn.INTFLAGS
TCDn.DITCTRL
TCDn.CTRLC
TCDn.CAPTUREB
TCDn.DITVAL
TCDn.CTRLD
TCDn.DBGCTRL
TCDn.EVCTRLA
TCDn.CMPASET
TCDn.EVCTRLB
TCDn.CMPACLR
TCDn.INPUTCTRLA
TCDn.CMPBSET
TCDn.INPUTCTRLB
TCDn.CMPBCLR
TCDn.FAULTCTRL
22.3.2.2 Clock Selection and Prescalers
The TCD can select between three different clock sources that can be prescaled. There are three
different prescalers with separate controls as shown below.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 271
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-2. Clock Selection and Prescalers Overview
CLKSEL
Counter
prescaler
OSC20M
EXTCLK
CLK_PER
CLK_TCD
Synchronization
prescaler
Counter clock
(CLK_TCD_CNT)
Synchronizer clock
(CLK_TCD_SYNC)
Delay
prescaler (1)
Delay clock
(CLK_TCD_DLY)
1. Used by input blanking/delay event out
The TCD synchronizer clock is separate from the other module clocks enabling faster synchronization
between the TCD domain and the I/O domain. The total prescaling for the counter is:
SYNCPRESC_division_factor × CNTPRESC_division_factor
The delay prescaler is used to prescale the clock used for the input blanking/delayed event output
functionality. The prescaler can be configured independently allowing separate range and accuracy
settings from the counter functionality.
22.3.2.3 Waveform Generation Modes
The TCD provides four different Waveform Generation modes. The Waveform Generation modes
determine how the counter is counting during a TCD cycle, and when the compare values are matching.
A TCD cycle is split into these states:
•
•
•
•
Dead time WOA (DTA)
On time WOA (OTA)
Dead time WOB (DTB)
On time WOB (OTB)
In a standard configuration all states are present in the order they are listed and they are nonoverlapping. The compare values Compare A Set (CMPASET), Compare A Clear (CMPACLR), Compare
B Set (CMPBSET), and Compare B Clear (CMPBCLR) defines when each of the states are ending and
the next is beginning. There are four different ways to go through a TCD cycle. The different ways are
called Waveform Generation modes. They are controlled by the Waveform Generation Mode bits
(WGMODE) in the Control A register (TCDn.CTRLA). The Waveform Generation modes are:
•
•
•
•
One Ramp mode
Two Ramp mode
Four Ramp mode
Dual Slope mode
The name indicates how the counter is operating during one TCD cycle.
22.3.2.3.1 One Ramp Mode
In One Ramp mode, the TCD counter counts up until it reaches the CMPBCLR value. Then the TCD
cycle is done and the counter restarts from 0x000, beginning a new TCD cycle. The TCD cycle period is:
�TCD_cycle =
CMPBCLR + 1
�CLK_TCD_CNT
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 272
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-3. One Ramp Mode
TCD cycle
Dead time A
compare
values
On time A
Dead time B
On time B
counter
value
CMPBCLR
CMPBSET
CMPACLR
CMPASET
WOA
WOB
In the figure above, CMPASET < CMPACLR < CMPBSET < CMPBCLR. This is required in One Ramp
mode to avoid overlapping outputs. The figure below is an example where CMPBSET < CMPASET <
CMPACLR < CMPBCLR, resulting in an overlap of the outputs.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 273
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-4. One Ramp Mode with CMPBSET < CMPASET
TCD cycle
Dead time A
On time A
On time B
Compare
values
Counter
value
CMPBCLR
CMPACLR
CMPASET
CMPBSET
WOA
WOB
If any of the other compare values are bigger than CMPBCLR it will never be triggered when running in
One Ramp mode, and if the CMPACLR is smaller than the CMPASET value, the clear value will not have
any effect.
22.3.2.3.2 Two Ramp Mode
In Two Ramp mode the TCD counter counts up until it reaches the CMPACLR value, then it Resets and
counts up until it reaches the CMPBCLR value. Then, the TCD cycle is done and the counter restarts
from 0x000, beginning a new TCD cycle. The TCD cycle period is given by:
�TCD_cycle =
CMPACLR + 1 + CMPBCLR + 1
�CLK_TCD_CNT
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 274
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-5. Two Ramp Mode
TCD cycle
Dead time A
On time A
Dead time B
On time B
counter
value
CMPBCLR
CMPACLR
CMPBSET
CMPASET
WOA
WOB
In the figure above, CMPASET < CMPACLR and CMPBSET < CMPBCLR. This causes the outputs to go
high. There are no restrictions on the CMPASET/CLR compared to the CMPBSET/CLR values.
In Two Ramp mode, it is not possible to get overlapping outputs.
22.3.2.3.3 Four Ramp Mode
In Four Ramp mode the TCD cycle is following this pattern:
1. A TCD cycle begins with the TCD counter counting up from zero until it reaches the CMPASET
value, and resets to zero.
2. The Counter counts up from zero until it reaches the CMPACLR value, and resets to zero.
3. The Counter counts up from zero until it reaches the CMPBSET value, and resets to zero.
4. The Counter counts up from zero until it reaches the CMPBCLR value, and ends the TCD cycle by
resetting to zero.
The TCD cycle period is given by:
�TCD_cycle =
CMPASET + 1 + CMPACLR + 1 + CMPBSET + 1 + CMPBCLR + 1
�CLK_TCD_CNT
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 275
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-6. Four Ramp Mode
TCD cycle
Dead time A
On time A
Dead time B
On time B
counter
value
CMPBCLR
CMPACLR
CMPBSET
CMPASET
WOA
WOB
There are no restrictions on the compare values compared to each other.
In Four Ramp mode, it is not possible to get overlapping outputs.
22.3.2.3.4 Dual Slope Mode
In Dual Slope mode, a TCD cycle consists of the TCD counter counting down from CMPBCLR value to
zero, and up again to the CMPBCLR value. This gives a TCD cycle period:
2 × CMPBCLR + 1
�CLK_TCD_CNT
The WOA output is set when the TCD counter counts up and matches the CMPASET value. WOA is
cleared when the TCD counter counts down and matches the CMPASET value.
�TCD_cycle =
The WOB output is set when the TCD counter counts down and matches the CMPBSET value. WOB is
cleared when the TCD counter counts up and matches the CMPBSET value.
Figure 22-7. Dual Slope Mode
TCD cycle
On time B
CMPBCLR
Dead
time A
On time A
Dead
time B
On time B
counter
value
CMPASET
CMPBSET
WOA
WOB
The outputs will be overlapping if CMPBSET > CMPASET.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 276
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
CMPACLR is not used in Dual Slope mode. Writing a value to CMPACLR has no effect.
When starting the TCD in Dual Slope mode, the TCD counter starts at the CMPBCLR value and counts
down. The WOA will not be set before the end of the first TCD cycle.
Figure 22-8. Dual Slope Mode Starting and Stopping
TCD cycle
CMPBCLR
counter
value
CMPASET
CMPBSET
WOA
WOB
Stop
Start-up
22.3.2.4 TCD Inputs
The TCD has two inputs that are connected to the Event System, Input A and Input B. Each input has
functionality that is connected to the corresponding output (WOA and WOB). That functionality is
controlled by the Event Control x registers (TCDn.EVCTRLA and TCDn.EVCTRLB) and the Input Control
x registers (TCDn.INPUTACTRL and TCDn.INPUTBCTRL).
To enable the input Events, write a '1' to the Trigger Event Input Enable bit (TRIGEI) in the Event Control
register (TCDn.EVCTRLx). The inputs will be used as a fault detect and/or capture trigger. To enable
capture trigger, write a '1' to the ACTION bit in Event Control register (TCDn.EVCTRLx).
There are ten different input modes for the fault detection. The two inputs have the same functionality,
except for input blanking which is only supported by input A. Input blanking is configured by the Delay
Control and Delay Value registers (TCDn.DLYCTRL and TCDn.DLYVAL).
The inputs are connected to the Event System. The connections between the event source and the TCD
input must be configured in the Event System.
An overview of the input system is shown below.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 277
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-9. TCD Input Overview
EVCTRLA.EDGE
Asynchonous overrride
EVCTRLA.ASYNC
Input Event A
Input processing logic
(Input mode logic A)
Digital
Filter
INPUT
BLANKING
EVCTRLA.FILTER
DLYPRESC
Change flow
INPUT
MODE
DLYTRIG
Synchronized
override
TC Core
(Timer/Counter,
compare values,
waveform generator)
DLYSEL
Output state
Output
control
INPUT
MODE
EVCTRLB.FILTER
Digital
Filter
Input Event B
EVCTRLB.EDGE
Change flow
Synchronized
override
Input processing logic
(Input mode logic B)
EVCTRLB.ASYNC
Asynchonous overrride
There is a delay of 2-3 clock cycles on the TCD synchronizer clock between receiving the input event,
processing it, and overriding the outputs. If using the asynchronous event detection, the outputs will
override instantly outside the input processing.
22.3.2.4.1 Input Blanking
Input blanking functionality is masking out the input events for a programmable time in a selectable part
of the TCD cycle. Input blanking can be used to mask out 'false' input events that are triggered right after
changes on the outputs.
To enable input blanking, write 0x1 to the Delay Select bit field in the Delay Control register (DLYSEL in
TCDn.DLYCTRL). The trigger source is selected by the Delay Trigger bit field (DLYTRIG in
TCDn.DLYCTRL).
Input blanking uses the Delay clock: after a trigger, a counter is counting up until the Delay Value
(DLYVAL in TCDn.DLYVAL) is reached before input blanking is turned OFF. The TCD delay clock is a
prescaled version of the Synchronization clock. The division factor is set by the Delay Prescaler bit field in
the Delay Control register (DLYPRESC in TCDn.DLYCTRL). The duration of the input blanking is given
by:
�BLANK =
DLYPRESC_division_factor × DLYVAL
�CLK_TCD_SYNC
Input blanking is using the same logic as the programmable output event. For this reason, it is not
possible to use both at the same time.
22.3.2.4.2 Digital Filter
The digital filter for event input x is enabled by writing a '1' to the FILTER bit in the Event Control x
register (TCDn.EVCTRLx). When the digital filter is enabled, any pulse lasting less than four counter
clock cycles will be filtered out. Any change on the incoming event will, therefore, take four counter clock
cycles before it will affect the input processing logic.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 278
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.3.2.4.3 Asynchronous Event Detection
To enable asynchronous event detection on an input event, write a '1' to the Asynchronous Event Control
bit (ASYNC) in the Event Control register (TCDn.EVCTRLx).
The asynchronous event detection makes it possible to asynchronously override the output when the
input event occurs. What the Input event will do is depending on Input Mode for the event input. The
outputs have direct override while the counter flow will be changed when the event is synchronized to the
synchronization clock.
It is not possible to use both asynchronous event detection and digital filtering at the same time.
22.3.2.4.4 Input Modes
The user can select between 10 input modes. The selection is done by writing the Input Mode bit field
(INPUTMODE) in the Input Control x register (TCDn.INPUTCTRLx).
Table 22-4. Input Mode Description
INPUTMODE
Description
0x0
Input has no action
0x1
Stop output, jump to opposite compare cycle and wait
0x2
Stop output, execute opposite compare cycle and wait
0x3
Stop output, execute opposite compare cycle while fault active
0x4
Stop all outputs, maintain frequency
0x5
Stop all outputs, execute dead time while fault active
0x6
Stop all outputs, jump to next compare cycle and wait
0x7
Stop all outputs, wait for software action
0x8
Stop output on edge, jump to next compare cycle
0x9
Stop output on edge, maintain frequency
0xA
Stop output at level, maintain frequency
other
Reserved
Not all input modes work in all Waveform Generation modes. Below is a table that shows what Waveform
Generation modes the different input modes are valid in.
Table 22-5. Ramp Mode the Different Input Modes are Valid In
INPUTMODE
One Ramp Mode
Two Ramp Mode
Four Ramp Mode
Dual Slope Mode
0x1
Valid
Valid
Valid
Do not use
0x2
Do not use
Valid
Valid
Do not use
0x3
Do not use
Valid
Valid
Do not use
0x4
Valid
Valid
Valid
Valid
0x5
Do not use
Valid
Valid
Do not use
0x6
Do not use
Valid
Valid
Do not use
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 279
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
...........continued
INPUTMODE
One Ramp Mode
Two Ramp Mode
Four Ramp Mode
Dual Slope Mode
0x7
Valid
Valid
Valid
Valid
0x8
Valid
Valid
Valid
Do not use
0x9
Valid
Valid
Valid
Do not use
0xA
Valid
Valid
Valid
Do not use
In the following sections the different Input modes are presented in detail.
Input Mode 1: Stop Output, Jump to Opposite Compare Cycle, and Wait
An input Event in Input mode 1 will stop the output signal, jump to the opposite dead time, and wait until
the input event goes low before the TCD counter continues.
If Input mode 1 is used on input A, an event will only have an effect if the TCD is in Dead-time A or Ontime A, and it will only affect the output WOA. When the event is done, the TCD counter starts at Deadtime B.
Figure 22-10. Input Mode 1 on Input A
DTA
OTA
DTB
OTB
DTA
OTA
Wait
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
If Input mode 1 is used on input B, an event will only have an effect if the TCD is in Dead-time B or Ontime B, and it will only affect the output WOB. When the event is done, the TCD counter starts at Deadtime A.
Figure 22-11. Input Mode 1 on Input B
DTA
OTA
DTB
OTB
Wait
DTA
OTA
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
Input Mode 2: Stop Output, Execute Opposite Compare Cycle, and Wait
An input Event in Input mode 2 will stop the output signal, execute to the opposite dead time and on time,
then wait until the input event goes low before the TCD counter continues. If the input is done before the
opposite dead time and on time have finished, there will be no waiting, but the opposite dead time and on
time will continue.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 280
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
If Input mode 2 is used on input A, an event will only have an effect if the TCD is in Dead-time A or Ontime A, and it will only affect the output WOA.
Figure 22-12. Input Mode 2 on Input A
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
Wait
DTA
OTA
WOA
WOB
INPUT A
INPUT B
If Input mode 2 is used on input B, an event will only have an effect if the TCD is in Dead-time B or Ontime B, and it will only affect the output WOB.
Figure 22-13. Input Mode 2 on Input B
DTA
OTA
DTB
OTB
DTA
OTA
Wait
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
Input Mode 3: Stop Output, Execute Opposite Compare Cycle while Fault Active
An input Event in Input mode 3 will stop the output signal and start executing the opposite dead time and
on time, as long as the fault/input is active. When the input is released, the ongoing dead time and/or on
time will finish and then, the normal flow will start.
If Input mode 3 is used on input A, an event will only have an effect if the TCD is in Dead-time A or Ontime A.
Figure 22-14. Input Mode 3 on Input A
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
If Input mode 3 is used on input B, an event will only have an effect if the TCD is in Dead-time B or Ontime B.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 281
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-15. Input Mode 3 on Input B
DTA
OTA
DTB
OTB
DTA
OTA
DTA
OTA
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
Input Mode 4: Stop all Outputs, Maintain Frequency
When Input mode 4 is used, both input A and input B will give the same functionality.
An input event will deactivate the outputs as long as the event is active. The TCD counter will not be
affected by events in this Input mode.
Figure 22-16. Input Mode 4
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
WOA
WOB
INPUT A/B
Input Mode 5: Stop all Outputs, Execute Dead Time while Fault Active
When Input mode 5 is used, both input A and input B give the same functionality:
The input event stops the outputs and starts on the opposite dead-time if it occurs during an on-time. If
the event occurs during a dead-time, it will continue until the next on-time should start, but instead, it will
jump to the next dead-time. As long as the input event is active, alternating dead-times will occur. When
the input event stops, the ongoing dead-time will finish and the next on-time will continue in the normal
flow.
Figure 22-17. Input Mode 5
DTA
OTA
DTB
OTB
DTA
OTA
DTB
DTA
DTB
DTA
DTB
OTB
WOA
WOB
INPUT A/B
Input Mode 6: Stop All Outputs, Jump to Next Compare Cycle, and Wait
When Input mode 6 is used both input A and input B will give the same functionality. The input event
stops the outputs and jumps to the opposite dead-time if it occurs during an on-time. If the event occurs
during a dead-time, it will continue until the next on-time should start, but instead, it will jump to the next
dead-time. As long as the input event is active, the TCD counter will wait. When the input events stops,
the next dead-time will start and normal flow will continue.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 282
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-18. Input Mode 6
DTA
OTA
DTB
Wait
DTA
OTA
Wait
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A/B
Input Mode 7: Stop all Outputs, Wait for Software Action
When Input mode 7 is used, both input A and input B will give the same functionality. The input events
stop the outputs and the TCD counter. It will be stopped until a Restart command is given. If the input
event is still high when the Restart command is given, it will just stop again. When the TCD counter
restarts, it will always start on Dead-time A.
Figure 22-19. Input Mode 7
DTA
OTA
DTB
OTB
DTA
OTA
Wait
DTA
OTA
WOA
WOB
INPUT A/B
Software Restart
command
Input Mode 8: Stop Output on Edge, Jump to Next Compare Cycle
In Input mode 8, a positive edge on the input event while the corresponding output is ON will cause the
output to stop and the TCD counter jump to the opposite dead-time.
If Input mode 8 is used on input A and a positive input event occurs while in On-time A, the TCD counter
jumps to Dead-time B.
Figure 22-20. Input Mode 8 on Input A
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
WOA
WOB
INPUT A
OR
INPUT A
If Input mode 8 is used on input B and a positive input event occurs while in On-time B, the TCD counter
jumps to Dead-time A.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 283
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-21. Input Mode 8 on Input B
DTA
OTA
DTB
OTB DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
WOA
WOB
INPUT B
OR
INPUT B
Input Mode 9: Stop Output at Level, Maintain Frequency
In Input mode 9 a positive edge on the input event while the corresponding output is ON will cause the
output to stop during the rest of the on-time. The TCD counter will not be affected by the event, only the
output.
If Input mode 9 is used on input A and a positive input event occurs while in On-time A, the output will be
OFF for the rest of the on-time.
Figure 22-22. Input Mode 9 on Input A
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
If Input mode 9 is used on input B and a positive input event occurs while in On-time B, the output will be
OFF for the rest of the on-time.
Figure 22-23. Input Mode 9 on Input B
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
Input Mode 10: Stop Output on Edge, Maintain Frequency
In Input mode 10 the input event will cause the corresponding output to stop as long as the input is active.
If the input goes low while there should have been an on-time on the corresponding output, the output will
be deactivated for the rest of the on-time, too. The TCD counter is not affected by the event, only the
output.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 284
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
If Input mode 10 is used on input A and an input event occurs, the WOA will be OFF as long as the event
lasts. If released during an on-time, it will be OFF for the rest of the on-time.
Figure 22-24. Input Mode 10 on Input A
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
If Input mode 10 is used on input B and an input event occurs, the WOB will be OFF as long as the event
lasts. If released during an on-time, it will be OFF for the rest of the on-time.
Figure 22-25. Input Mode 10 on Input B
DTA
OTA
DTB
OTB
DTA
OTA
DTB
OTB
DTA
OTA
WOA
WOB
INPUT A
INPUT B
Input Mode Summary
The table below summarizes the conditions as illustrated in the timing diagrams of the preceding
sections.
Table 22-6. Input Mode Summary
INPUTMODE
Trigger → Output Affected
Fault On/Active
Fault Release/Inactive
0x00
-
No action
No action
0x01
Input A→WOA
End current on-time and Start with dead-time for
wait
other compare
Input B→WOB
0x02
0x03
Input A→WOA
End current on-time.
Input B→WOB
Execute other compare
cycle and wait
Input A→WOA
End current on-time.
Input B→WOB
Execute other compare
cycle
© 2019 Microchip Technology Inc.
Preliminary Datasheet
Start with dead-time for
current compare
Re-enable current
compare cycle
40001997C-page 285
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
...........continued
INPUTMODE
Trigger → Output Affected
Fault On/Active
0x04
Input A→{WOA, WOB}
Deactivate outputs
Fault Release/Inactive
Input B→{WOA, WOB}
0x05
Input A→{WOA, WOB}
Execute dead-time only
Input B→{WOA, WOB}
0x06
Input A→{WOA, WOB}
End on-time and wait
Start with dead-time for
other compare
End on-time and wait
for software action
Start with dead-time for
current compare
Input B→{WOA, WOB}
0x07
Input A→{WOA, WOB}
Input B→{WOA, WOB}
0x08
Input A→WOA
Input B→WOB
0x09
Input A→WOA
Input B→WOB
0x0A
Input A→WOA
Input B→WOB
other
-
End current on-time and
continue with other offtime
Block current on-time
and continue sequence
Deactivate on-time until
end of sequence while
trigger is active
-
-
22.3.2.5 Dithering
If it is not possible to achieve the desired frequency because of prescaler/period selection limitations,
dithering can be used to approximate the desired frequency and reduce waveform drift.
Dither accumulates the fractional error of the counter clock for each cycle. When the fractional error
overflows, an additional cycle is added to the selected part of the cycle.
Example 22-1. Generate 75 kHz from 10 MHz Clock
If the timer clock frequency is 10 MHz, it will give the timer a resolution of 100 ns. The
desired output frequency is 75 kHz, which means a period of 13333 ns. This period is not
possible to achieve with a constant period with a 100 ns resolution, it would require
133.33 cycles. The output period can be set to either 133 cycles (75.188 kHz) or 134
cycles (74.626 kHz).
It is possible to change the period between the two frequencies manually in the firmware
to get an average output frequency of 75 kHz (change every 3rd period to 134 cycles).
The dither can do this automatically by accumulating the error (0.33 cycles). The
accumulator calculates when the accumulated error is larger than one clock cycle and
when that happens it adds an additional cycle to the timer period.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 286
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Figure 22-26. Dither Logic
Overflow
Dither value
ACCUMULATOR REGISTER
The user can select where in the TCD cycle the Dither will be added by writing to the Dither Selection bits
in the Dither Control register (DITHERSEL in TCDn.DITCTRL):
• On-time B
• On-time A and B
• Dead-time B
• Dead-time A and B
How much the Dithering will affect the TCD cycle time depends on what Waveform Generation mode is
used, see the table below.
Dithering is not supported in Dual Slope mode.
Table 22-7. Mode-Dependent Dithering Additions to TCD Cycle
WAVEGEN
DITHERSEL in TCDn.DITCTRL
Additional TCD Clock Cycles to TCD Cycle
One Ramp mode
On-time B
1
On-time A and B
1
Dead-time B
0
Dead-time A and B
0
On-time B
1
On-time A and B
2
Dead-time B
0
Dead-time A and B
0
On-time B
1
On-time A and B
2
Dead-time B
1
Dead-time A and B
2
Two Ramp mode
Four Ramp mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 287
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
...........continued
WAVEGEN
DITHERSEL in TCDn.DITCTRL
Additional TCD Clock Cycles to TCD Cycle
Dual Slope mode
On-time B
0 (not supported)
On-time A and B
0 (not supported)
Dead-time B
0 (not supported)
Dead-time A and B
0 (not supported)
The differences in the number of TCD clock cycles added to the TCD cycle is caused by the different
number of compare values used by the TCD cycle. For example, in One Ramp mode, only CMPBCLR
affects the TCD cycle time.
For DITHERSEL configurations where no extra cycles are added to the TCD cycles, compensation is
reached by shortening the following output state.
Example 22-2. DITHERSEL in One Ramp Mode
In One Ramp mode with DITHERSEL selecting Dead-time B, the Dead-time B will be
increased by one cycle when dither overflow occurs. This reduces On-time B by one
cycle.
22.3.2.6 TCD Counter Capture
Because the TCD counter is asynchronous to the system clock it is not possible to read out the counter
value directly. It is possible to capture the TCD counter value, synchronized to the I/O clock domain in two
different ways:
• Capture value on input events
• Software capture
The capture logic contains two separate capture blocks, CAPTUREA and CAPTUREB, that can capture
and synchronize the TCD counter value to the I/O clock domain. CAPTUREA/B can be triggered by input
event A/B or by software.
The capture values can be read by reading first TCDn.CAPTURExL and then TCDn.CAPTURExH
registers.
Captures Triggered by Input Events
To enable capture on input event, write a ‘1’ to the ACTION bit in the respective Event Control x register
(TCDn.EVCTRL) when configuring an event input.
When a capture has occurred, the TRIGA/B flag is raised in the Interrupt Flags register
(TCDn.INTFLAGS). The according TRIGA/B interrupt is executed if enabled by writing a ‘1’ to the
respective Trigger Interrupt x Enable bit (TRIGx) in the Interrupt Control register (TCDn.INTCTRL). By
polling TRIGx in TCDn.INTFLAGS, the user knows that a CAPTUREx value is available, and can read out
the value by reading first the TCDn.CAPTURExL and then TCDn.CAPTURExH registers.
Example 22-3. PWM Capture
In order to do PWM capture connect both event A and event B to the same
asynchronous event channel that contains the PWM signal. To get information on the
PWM signal, configure one event input to capture the rising edge of the signal. Configure
the other event input to capture the falling edge of the signal.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 288
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
Capture Triggered by Software
The software can capture the TCD value by writing a ‘1’ to respective Software Capture A/B Strobe bit
(SCAPTUREx) in the Control E register (TCDn.CTRLE). When this command is executed and the
Command Ready bit (CMDRDY) in the Status register (TCDn.STATUS) reads ‘1’ again, the
CAPTUREA/B value is available. It can now be read by reading first the TCDn.CAPTURExL and then the
TCDn.CAPTURExH registers.
Using Capture Together with Input Modes
The capture functionality can be used together with Input modes. The same event will then both capture
the counter value and trigger a change in the counter flow, depending on the Input mode selected.
Example 22-4. Reset One Ramp Mode by Input Event Capture
In One Ramp mode, the counter can be reset by an input event capture. To achieve this,
use input event B and write the TCDn.INPUTCTRLB register to 0x08.
Related Links
22.3.1 Initialization and Disabling
22.3.2.7 Output Control
The outputs are configured by writing to the Fault Control register (TCDn.FAULTCTRL).
TCDn.FAULTCTRL is only reset to '0' after a POR reset. During the reset sequence after any Reset,
TCDn.FAULTCTRL will get its values from the TCD Fuse (FUSE.TCDCFG).
The Compare x Enable bits (CMPxEN in TCDn.FAULTCTRL) enable the different outputs. The CMPx bits
in TCDn.FAULTCTRL set the value the registers should have after Reset or when a fault is triggered.
The TCD itself generates two different outputs, WOA and WOB. The two additional outputs WOC and
WOD can be configured by software to be connected to either WOA or WOB by writing the Compare C/D
Output Select bits (CMPCSEL and CMPDSEL) in the Control C register (TCDn.CTRLC).
The user can also override the outputs based on the TCD counter state by writing a '1' to the Compare
Output Value Override bit in the Control C register (CMPOVR in TCDn.CTRLC). The user can then select
the output values in the different dead- and on-times by writing to the Compare x Value bit fields in the
Control D register (CMPAVAL and CMPBVAL in TCDn.CTRLD).
When used in One Ramp mode, WOA will only use the setup for Dead-Time A (DTA) and On-Time A
(OTA) to set the output. WOB will only use Dead-Time B (DTB) and On-Time B (OTB) values to set the
output.
When using the override feature together with faults detection (input modes) the CMPA (and CMPC/D if
WOC/D equals WOA) bit in TCDn.FAULTCTRL should be equal to CMPAVAL[0] and [2] in CTRLD if not
the first cycle after a fault is detected can have the wrong polarity on the outputs. The same applies to
CMPB in TCDn.FAULTCTRL (and CMPC/D if WOC/D equals WOB) bit, which should be equal to
CMPBVAL[0] and [2] in TCDn.CTRLD.
Due to the asynchronous nature of the TCD, that input events immediately can affect the output signal,
there is a risk of nano-second spikes occurring on the output when there is no load on the pin. The case
occurs in any Input mode different from '0' and when an input event is triggering. The spike value will
always be in direction of the CMPx value given by the TCDn.FAULTCTRL register.
Related Links
6.10.4.4 TCD0CFG
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 289
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.3.3
Events
The TCD can generate the following output events:
•
•
•
•
TCD counter matches CMPBCLR
TCD counter matches CMPASET
TCD counter matches CMPBSET
Programmable TCD output event. The user can select the trigger and all the different compare
matches. In addition, it is possible to delay the output event from 0 to 256 TCD delay cycles.
The three events based on the counter match directly generate event strobes that last one clock cycle on
the TCD counter clock. The programmable output event generates an event strobe that last one clock
cycle on the TCD synchronizer clock.
The TCD has the possibility to receive these input events:
• Input A
• Input B
Related Links
22.3.2.4 TCD Inputs
14. EVSYS - Event System
22.3.3.1 Programmable Output Events
Programmable output event uses the same logic as the input blanking for trigger selection and delay. It is
therefore not possible to configure the functionalities independently. If the input blanking functionality is
used, the output event cannot be delayed and the trigger used for input blanking will also be used for the
output event.
The programmable output events are controlled by the TCDn.DLYCTRL and TCDn.DLYVAL registers. It is
possible to delay the output event by 0 to 256 TCD delay clock cycles if the DLYTRIG bits in
TCDn.DLYCTRL is set to 0x2. The delayed output event functionality uses the TCD delay clock and
counts until the DLYVAL value is reached before the trigger is sent out as an event. The TCD delay clock
is a prescaled version of the TCD synchronization clock and the division factor is set by the DLYPRESC
bits in the TCDn.DLYCTRL register. The output event will be delayed by TCD clock period x DLYPRESC
division factor x DLYVAL.
22.3.4
Interrupts
Table 22-8. Available Interrupt Vectors and Sources
Offset
Name
Vector Description
Conditions
0x00
OVF
Overflow interrupt
The TCD is done with one TCD cycle.
0x02
TRIG
Trigger interrupt
• TRIGA: Counter is entering On-Time A
• TRIGB: Counter is entering On-Time B
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding enable bit in the peripheral's
Interrupt Control register (peripheral.INTCTRL).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 290
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
When several interrupt request conditions are supported by an interrupt vector, the interrupt requests are
ORed together into one combined interrupt request to the interrupt controller. The user must read the
peripheral's INTFLAGS register to determine which of the interrupt conditions are present.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
22.3.5
Sleep Mode Operation
The TCD operates in Idle Sleep mode and is stopped when entering Standby and Power-Down Sleep
modes.
22.3.6
Synchronization
The TCD has two different clock domains and needs to synchronize the communication between the
domains. See the Initialization section for details on how the synchronization of values from the I/O clock
domain to the TCD clock domain is done. See the Capture section for details on how the synchronization
of values from the TCD clock domain to the I/O clock domain is done.
Related Links
22.3.1 Initialization and Disabling
22.3.2.6 TCD Counter Capture
22.3.7
Configuration Change Protection
This peripheral has registers that are under Configuration Change Protection (CCP). In order to write to
these, a certain key must be written to the CPU.CCP register first, followed by a write access to the
protected bits within four CPU instructions.
Attempting to write to a protected register without following the appropriate CCP unlock sequence leaves
the protected register unchanged.
The following registers are under CCP:
Table 22-9. TCD - Registers under Configuration Change Protection
Register
Key
FAULTCTRL
IOREG
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 291
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.4
Register Summary - TCD
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
...
0x07
0x08
0x09
0x0A
...
0x0B
0x0C
0x0D
0x0E
0x0F
0x10
0x11
0x12
0x13
0x14
0x15
0x16
...
0x17
0x18
0x19
0x1A
...
0x1D
0x1E
0x1F
...
0x21
CTRLA
CTRLB
CTRLC
CTRLD
CTRLE
7:0
7:0
7:0
7:0
7:0
0x22
EVCTRLA
EVCTRLB
INTCTRL
INTFLAGS
STATUS
Reserved
INPUTCTRLA
INPUTCTRLB
FAULTCTRL
Reserved
DLYCTRL
DLYVAL
DITCTRL
DITVAL
SCAPTUREB SCAPTUREA
7:0
7:0
CFG[1:0]
CFG[1:0]
EDGE
EDGE
ACTION
ACTION
TRIGEI
TRIGEI
7:0
7:0
7:0
7:0
7:0
7:0
TRIGB
TRIGB
TRIGA
TRIGA
OVF
OVF
ENRDY
PWMACTB
CMPDEN
7:0
7:0
PWMACTA
CMPCEN
CMDRDY
CMPBEN
CMPAEN
CMPD
DLYPRESC[1:0]
INPUTMODE[3:0]
INPUTMODE[3:0]
CMPC
CMPB
DLYTRIG[1:0]
CMPA
DLYSEL[1:0]
DLYVAL[7:0]
7:0
7:0
DITHERSEL[1:0]
DITHER[3:0]
Reserved
DBGCTRL
7:0
FAULTDET
DBGRUN
Reserved
CAPTUREA
Reserved
0x28
CMPASET
22.5
DISEOC
FIFTY
Reserved
0x26
...
0x27
0x2E
CMPCSEL
CMPBVAL[3:0]
SYNCPRES[1:0]
ENABLE
WGMODE[1:0]
AUPDATE
CMPOVR
CMPAVAL[3:0]
RESTART
SYNC
SYNCEOC
Reserved
CAPTUREB
0x2C
CMPDSEL
CNTPRES[1:0]
Reserved
0x24
0x2A
CLKSEL[1:0]
CMPACLR
CMPBSET
CMPBCLR
7:0
15:8
7:0
15:8
CAPTURE[7:0]
7:0
15:8
7:0
15:8
7:0
15:8
7:0
15:8
CMPSET[7:0]
CAPTURE[11:8]
CAPTURE[7:0]
CAPTURE[11:8]
CMPSET[11:8]
CMPCLR[7:0]
CMPCLR[11:8]
CMPSET[7:0]
CMPSET[11:8]
CMPCLR[7:0]
CMPCLR[11:8]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 292
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
Enable-protected
6
5
4
3
2
R/W
R/W
R/W
R/W
R/W
R/W
0
0
R/W
0
0
0
0
0
CLKSEL[1:0]
Access
Reset
CNTPRES[1:0]
1
SYNCPRES[1:0]
0
ENABLE
Bits 6:5 – CLKSEL[1:0] Clock Select
The clock select bits select the clock source of the TCD clock.
Value
Description
0x0
OSC20M
0x1
Reserved
0x2
External clock
0x3
System clock
Bits 4:3 – CNTPRES[1:0] Counter Prescaler
The Counter Prescaler bits select the division factor of the TCD counter clock.
Value
Description
0x0
Division factor 1
0x1
Division factor 4
0x2
Division factor 32
0x3
Reserved
Bits 2:1 – SYNCPRES[1:0] Synchronization Prescaler
The synchronization prescaler bits select the division factor of the TCD clock.
Value
Description
0x0
Division factor 1
0x1
Division factor 2
0x2
Division factor 4
0x3
Division factor 8
Bit 0 – ENABLE Enable
When this bit is written to, it will automatically be synchronized to the TCD clock domain.
This bit can be changed as long as synchronization of this bit is not ongoing, see Enable Ready bit
(ENRDY) in Status register (TCDn.STATUS).
This bit is not enable-protected.
Value
Description
0
The TCD is disabled.
1
The TCD is enabled and running.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 293
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.2
Control B
Name:
Offset:
Reset:
Property:
Bit
7
CTRLB
0x01
0x00
-
6
5
4
3
2
1
0
WGMODE[1:0]
Access
Reset
R/W
R/W
0
0
Bits 1:0 – WGMODE[1:0] Waveform Generation Mode
These bits select the waveform generation.
Value
Name
Description
0x0
ONERAMP
One Ramp mode
0x1
TWORAMP
Two Ramp mode
0x2
FOURRAMP
Four Ramp mode
0x3
DS
Dual-Slope mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 294
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.3
Control C
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
CTRLC
0x02
0x00
-
7
6
CMPDSEL
CMPCSEL
R/W
R/W
0
0
5
4
3
1
0
FIFTY
AUPDATE
CMPOVR
R/W
R/W
R/W
0
0
0
Bit 7 – CMPDSEL Compare D Output Select
Value
Name
0
PWMA
1
PWMB
Description
Waveform A
Waveform B
Bit 6 – CMPCSEL Compare C Output Select
Value
Name
0
PWMA
1
PWMB
Description
Waveform A
Waveform B
2
Bit 3 – FIFTY Fifty Percent Waveform
If the two waveforms have identical characteristics, this bit can be written to ‘1’. This will cause any values
written to register TCDn.CMPBSET/TCDn.CLR also to be written to the register TCDn.CMPASET/
TCDn.CLR.
Bit 1 – AUPDATE Automatically Update
If this bit is written to ‘1’ a synchronization at the end of the TCD cycle is automatically requested after the
Compare B Clear High register (TCDn.CMPBCLRH) is written.
If the fifty percent waveform is enabled by setting the FIFTY bit in this register, writing the Compare A
Clear High register will also request a synchronization at the end of the TCD cycle if the AUPDATE bit is
set.
Bit 0 – CMPOVR Compare Output Value Override
When this bit is written to ‘1’, default values of the Waveform Outputs A and B are overridden by the
values written in the Compare x Value in active state bit fields in the Control D register (CMPnxVAL bit in
TCDn.CTRLD). See the Control D register description for more details.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 295
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.4
Control D
Name:
Offset:
Reset:
Property:
Bit
CTRLD
0x03
0x00
-
7
6
5
4
3
2
R/W
0
1
0
R/W
R/W
R/W
R/W
R/W
0
0
0
0
R/W
R/W
0
0
0
CMPBVAL[3:0]
Access
Reset
CMPAVAL[3:0]
Bits 0:3, 4:7 – CMPVAL Compare x Value (in active state)
These bits set the active state for the different ramps for compare x.
These settings are only valid if the Compare Output Value Override bit in the Control C register
(CMPOVR bit in TCDn.CTRLC) is written to '1'.
CMPxVAL
A_off
A_on
B_off
B_on
PWMA
CMPAVAL[0]
CMPAVAL[1]
CMPAVAL[2]
CMPAVAL[3]
PWMB
CMPBVAL[0]
CMPBVAL[1]
CMPBVAL[2]
CMPBVAL[3]
In One Ramp mode, PWMA will only use A_off and A_on values and PWMB will only use B_off and B_on
values. This is due to possible overlap between the values A_off, A_on, B_off, and B_on.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 296
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.5
Control E
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLE
0x04
0x00
-
6
5
4
3
2
1
0
DISEOC
SCAPTUREB
SCAPTUREA
RESTART
SYNC
SYNCEOC
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bit 7 – DISEOC Disable at End of TCD Cycle Strobe
When this bit is written, the TCD will automatically disable at the end of the TCD cycle.
When this bit is written to ‘1’, the ENRDY in TCDn.STATUS will stay low until the TCD is disabled.
Writing to this bit has only effect if there is no ongoing synchronization of Enable. See also the ENRDY bit
in TCDn.STATUS.
Bit 4 – SCAPTUREB Software Capture B Strobe
When this bit is written to ‘1’, a software capture to Capture register B (TCDn.CAPTUREBL/H) is done as
soon as the strobe is synchronized to the TCD domain.
Writing to this bit has only effect if there is no ongoing synchronization of a command. See also the
CMDRDY bit in TCDn.STATUS.
Bit 3 – SCAPTUREA Software Capture A Strobe
When this bit is written to ‘1’, a software capture to Capture register A (TCDn.CAPTUREAL/H) is done as
soon as the strobe is synchronized to the TCD domain.
Writing to this bit has only effect if there is no ongoing synchronization of a command. See also the
CMDRDY bit in TCDn.STATUS.
Bit 2 – RESTART Restart Strobe
When this bit is written a restart of the TCD counter is executed as soon as this bit is synchronized to the
TCD domain.
Writing to this bit has only effect if there is no ongoing synchronization of a command. See also the
CMDRDY bit in TCDn.STATUS.
Bit 1 – SYNC Synchronize Strobe
When this bit is written to ‘1’ the double-buffered registers will be loaded to the TCD domain as soon as
this bit is synchronized to the TCD domain.
Writing to this bit has only effect if there is no ongoing synchronization of a command. See also the
CMDRDY bit in TCDn.STATUS.
Bit 0 – SYNCEOC Synchronize End of TCD Cycle Strobe
When this bit is written to ‘1’ the double-buffered registers will be loaded to the TCD domain at the end of
the next TCD cycle.
Writing to this bit has only effect if there is no ongoing synchronization of a command. See also the
CMDRDY bit in TCDn.STATUS.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 297
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.6
Event Control x
Name:
Offset:
Reset:
Property:
Bit
EVCTRL
0x08 + n*0x01 [n=0..1]
0x00
-
7
6
CFG[1:0]
Access
Reset
5
4
3
2
1
0
EDGE
ACTION
TRIGEI
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
Bits 7:6 – CFG[1:0] Event Configuration
When the input capture noise canceler is activated (FILTERON), the event input is filtered. The filter
function requires four successive equal valued samples of the retrigger pin for changing its output. The
input capture is therefore delayed by four clock cycles when the noise canceler is enabled.
When the Asynchronous Event is enabled (ASYNCON), the event input will qualify the output directly.
Value
Name
Description
0x0
NEITHER
Neither filter nor asynchronous event is enabled.
0x1
FILTERON
Input capture noise cancellation filter enabled.
0x2
ASYNCON
Asynchronous event output qualification enabled.
other
Reserved.
Bit 4 – EDGE Edge Selection
This bit is used to select the active edge or level for the event input.
Value
Name
Description
0
FALL_LOW The falling edge or low level of the event input generates retrigger or fault
action.
1
RISE_HIGH The rising edge or high level of the event input generates retrigger or fault
action.
Bit 2 – ACTION Event Action
This bit enables capture on event input. By default, the input will trigger a fault, depending on the Input x
register Input mode (INPUTx). It is also possible to trigger a capture on the event input.
Value
Name
Description
0
FAULT
Event triggers a fault.
1
CAPTURE
Event triggers a fault and capture.
Bit 0 – TRIGEI Trigger Event Input Enable
Writing this bit to '1' enables event as trigger for input A.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 298
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.7
Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
INTCTRL
0x0C
0x00
-
6
Access
Reset
5
4
3
2
1
0
TRIGB
TRIGA
OVF
R/W
R/W
R/W
0
0
0
Bits 2, 3 – TRIG Trigger x Interrupt Enable
Writing this bit to '1' enables executing an interrupt when trigger input x is received.
Bit 0 – OVF Counter Overflow
Writing this bit to '1' enables executing an interrupt at restart of the sequence or overflow of the counter.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 299
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.8
Interrupt Flags
Name:
Offset:
Reset:
Property:
Bit
7
INTFLAGS
0x0D
0x00
-
6
Access
Reset
5
4
3
2
1
0
TRIGB
TRIGA
OVF
R/W
R/W
R/W
0
0
0
Bits 2, 3 – TRIG Trigger x Interrupt Flag
When a capture has occurred, the TRIGA/B is raised. This bit is cleared by writing a '1' to it.
Bit 0 – OVF Overflow Interrupt Flag
When a capture is overflow, this flag is raised. This bit is cleared by writing a '1' to it.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 300
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.9
Status
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
STATUS
0x0E
0x00
-
7
6
PWMACTB
R/W
0
5
4
3
2
1
0
PWMACTA
CMDRDY
ENRDY
R/W
R
R
0
0
0
Bits 6, 7 – PWMACT PWM Activity on x
This bit is set by hardware each time the output WO toggles from 0 to 1 or from 1 to 0.
This status bit must be cleared by software by writing a '1' to it before new PWM activity can be detected.
Bit 1 – CMDRDY Command Ready
This status bit tells when a command is synced to the TCD domain and the system is ready to receive
new commands.
The following clears the CMDRDY bit:
1. TCDn.CTRLE SYNCEOC strobe.
2. TCDn.CTRLE SYNC strobe.
3. TCDn.CTRLE RESTART strobe.
4. TCDn.CTRLE SCAPTUREA Capture A strobe.
5. TCDn.CTRLE SCAPTUREB Capture B strobe.
6. TCDn.CTRLC AUPDATE written to '1' and writing to TCDn.CMPBCLRH register.
Bit 0 – ENRDY Enable Ready
This status bit tells when the ENABLE value in TCDn.CTRLA is synced to the TCD domain and is ready
to be written to again.
The following clears the ENRDY bit:
1. Writing to the ENABLE bit in TCDn.CTRLA.
2. TCDn.CTRLE DISEOC strobe.
3. Going into BREAK in an On-Chip Debugging (OCD) session while the Debug Run bit (DBGCTRL)
in TCDn.DBGCTRL is not ‘1’.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 301
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.10 Input Control x
Name:
Offset:
Reset:
Property:
Bit
7
INPUTCTRL
0x10 + n*0x01 [n=0..1]
0x00
-
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
0
INPUTMODE[3:0]
Access
Reset
Bits 3:0 – INPUTMODE[3:0] Input Mode
Value
Name
Description
0x0
NONE
Input has no action
0x1
JMPWAIT
Stop output, jump to opposite compare cycle, and wait
0x2
EXECWAIT
Stop output, execute opposite compare cycle, and wait
0x3
EXECFAULT
Stop output, execute opposite compare cycle while fault active
0x4
FREQ
Stop all outputs, maintain frequency
0x5
EXECDT
Stop all outputs, execute dead time while fault active
0x6
WAIT
Stop all outputs, jump to next compare cycle, and wait
0x7
WAITSW
Stop all outputs, wait for software action
0x8
EDGETRIG
Stop output on edge, jump to next compare cycle
0x9
EDGETRIGFREQ
Stop output on edge, maintain frequency
0xA
LVLTRIGFREQ
Stop output at level, maintain frequency
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 302
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.11 Fault Control
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
FAULTCTRL
0x12
Loaded from fuse
Configuration Change Protection
7
6
5
4
3
2
1
0
CMPDEN
CMPCEN
CMPBEN
CMPAEN
CMPD
CMPC
CMPB
CMPA
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
x
x
x
x
x
x
x
x
Bits 4, 5, 6, 7 – CMPEN Compare x Enable
These bits enable compare as output on the pin. At Reset, the content is kept and during the reset
sequence loaded from the TCD Configuration Fuse (FUSE.TCDFG).
Bits 0, 1, 2, 3 – CMP Compare Value x
These bits set the default state from Reset, or when an input event triggers a fault causing changes to the
output. At Reset, the content is kept and during the reset sequence loaded from the TCD Configuration
Fuse (FUSE.TCDFG).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 303
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.12 Delay Control
Name:
Offset:
Reset:
Property:
Bit
7
DLYCTRL
0x14
0x00
-
6
5
4
3
DLYPRESC[1:0]
Access
Reset
2
1
DLYTRIG[1:0]
0
DLYSEL[1:0]
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bits 5:4 – DLYPRESC[1:0] Delay Prescaler
These bits control the prescaler settings for the blanking or output event delay.
Value
Description
0x0
Prescaler division factor 1
0x1
Prescaler division factor 2
0x2
Prescaler division factor 4
0x3
Prescaler division factor 8
Bits 3:2 – DLYTRIG[1:0] Delay Trigger
These bits control what should trigger the blanking or output event delay.
Value
Name
Description
0x0
CMPASET
CMPASET triggers delay
0x1
CMPACLR
CMPACLR triggers delay
0x2
CMPBSET
CMPBSET triggers delay
0x3
CMPBCLR
CMPASET triggers delay (end of cycle)
Bits 1:0 – DLYSEL[1:0] Delay Select
These bits control what function should be used by the delay trigger the blanking or output event delay.
Value
Description
0x0
Delay functionality not used
0x1
Input blanking enabled
0x2
Event delay enabled
0x3
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 304
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.13 Delay Value
Name:
Offset:
Reset:
Property:
Bit
DLYVAL
0x15
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DLYVAL[7:0]
Access
Reset
Bits 7:0 – DLYVAL[7:0] Delay Value
These bits configure the blanking/output event delay time or event output synchronization delay in
number of prescaled TCD cycles.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 305
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.14 Dither Control
Name:
Offset:
Reset:
Property:
Bit
7
DITCTRL
0x18
0x00
-
6
5
4
3
2
1
0
DITHERSEL[1:0]
Access
Reset
R/W
R/W
0
0
Bits 1:0 – DITHERSEL[1:0] Dither Select
These bits select which Compare register is using the Dither function. See 22.3.2.5 Dithering.
Value
Name
Description
0x0
ONTIMEB
On-time ramp B
0x1
ONTIMEAB
On-time ramp A and B
0x2
DEADTIMEB
Dead-time ramp B
0x3
DEADTIMEAB
Dead-time ramp A and B
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 306
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.15 Dither Value
Name:
Offset:
Reset:
Property:
Bit
7
DITVAL
0x19
0x00
-
6
5
4
3
2
1
0
R/W
R/W
0
R/W
R/W
0
0
0
DITHER[3:0]
Access
Reset
Bits 3:0 – DITHER[3:0] Dither Value
These bits configure the fractional adjustment of the on-time or off-time according to Dither Selection bits
(DITHERSEL) in the Dither Control register (TCDn.DITCTRL). The DITHER value is added to a 4-bit
accumulator at the end of each TCD cycle. When the accumulator overflows the frequency adjustment
will occur.
The DITHER bits are double-buffered so the new value is copied in at an update condition.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 307
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.16 Debug Control
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x1E
0x00
-
6
5
4
3
2
1
0
FAULTDET
DBGRUN
R/W
R/W
0
0
Access
Reset
Bit 2 – FAULTDET Fault Detection
This bit defines how the peripheral behaves when stopped in Debug mode.
Value
Name Description
0
NONE No fault is generated if TCD is stopped in Debug mode.
1
FAULT A fault is generated and both trigger flags are set if TCD is halted in Debug mode.
Bit 0 – DBGRUN Debug Run
When written to '1', the peripheral will continue operating in Debug mode when the CPU is halted.
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 308
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.17 Capture x
Name:
Offset:
Reset:
Property:
CAPTURE
0x22 + n*0x02 [n=0..1]
0x00
-
For capture operation, these registers constitute the second buffer level and access point for the CPU.
The TCDn.CAPTUREx registers are updated with the buffer value when an UPDATE condition occurs.
CAPTURE A register contains the value from the TCD counter when a Trigger A or a software capture A
occurs. CAPTURE B register contains the value from the TCD counter when Trigger B or software
capture B occurs.
The TCD counter value is synchronized to CAPTUREx by either software or an event.
The capture register is blocked for an update of new capture data until TCDn.CAPTURExH is read.
Bit
15
14
13
12
11
10
9
8
CAPTURE[11:8]
Access
R
R
R
R
Reset
0
0
0
0
3
2
1
0
Bit
7
6
5
4
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
CAPTURE[7:0]
Bits 11:0 – CAPTURE[11:0] Capture Byte
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 309
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.18 Compare Set x
Name:
Offset:
Reset:
Property:
CMPSET
0x28 + n*0x04 [n=0..1]
0x00
-
For compare operation, these registers are continuously compared to the counter value. Normally, the
outputs from the comparators are then used for generating waveforms.
Bit
15
14
13
12
11
10
9
8
CMPSET[11:8]
Access
R/W
R/W
R/W
R/W
0
0
0
0
3
2
1
0
Reset
Bit
7
6
5
4
CMPSET[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 11:0 – CMPSET[11:0] Compare Set
These bits hold value of the compare register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 310
ATtiny1616/3216
TCD - 12-Bit Timer/Counter Type D
22.5.19 Compare Clear x
Name:
Offset:
Reset:
Property:
CMPCLR
0x2A + n*0x04 [n=0..1]
0x00
-
For compare operation, these registers are continuously compared to the counter value. Normally, the
outputs from the comparators are then used for generating waveforms.
Bit
15
14
13
12
11
10
9
8
CMPCLR[11:8]
Access
R/W
R/W
R/W
R/W
0
0
0
0
3
2
1
0
Reset
Bit
7
6
5
4
CMPCLR[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 11:0 – CMPCLR[11:0] Compare x Clear
These bits hold the value of the compare register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 311
ATtiny1616/3216
RTC - Real-Time Counter
23.
RTC - Real-Time Counter
23.1
Features
• 16-Bit Resolution
• Selectable Clock Source:
– 32.768 kHz external crystal (XOSC32K)
– External clock
– 32 KHz internal ULP oscillator (OSCULP32K)
– OSCULP32K divided by 32
• Programmable 15-Bit Clock Prescaling
• One Compare Register
• One Period Register
• Clear Timer On Period Overflow
• Optional Interrupt/Event on Overflow and Compare Match
• Periodic Interrupt and Event
23.2
Overview
The RTC peripheral offers two timing functions: the Real-Time Counter (RTC) and a Periodic Interrupt
Timer (PIT).
The PIT functionality can be enabled independently of the RTC functionality.
RTC - Real-Time Counter
The RTC counts (prescaled) clock cycles in a Counter register, and compares the content of the Counter
register to a Period register and a Compare register.
The RTC can generate both interrupts and events on compare match or overflow. It will generate a
compare interrupt and/or event at the first count after the counter equals the Compare register value, and
an overflow interrupt and/or event at the first count after the counter value equals the Period register
value. The overflow will also reset the counter value to zero.
The RTC peripheral typically runs continuously, including in Low-Power Sleep modes, to keep track of
time. It can wake-up the device from Sleep modes and/or interrupt the device at regular intervals.
The reference clock is typically the 32.768 kHz output from an external crystal. The RTC can also be
clocked from an external clock signal, the 32 KHz internal Ultra Low-Power Oscillator (OSCULP32K), or
the OSCULP32K divided by 32.
The RTC peripheral includes a 15-bit programmable prescaler that can scale down the reference clock
before it reaches the counter. A wide range of resolutions and time-out periods can be configured for the
RTC. With a 32.768 kHz clock source, the maximum resolution is 30.5 μs, and time-out periods can be up
to two seconds. With a resolution of 1s, the maximum time-out period is more than 18 hours (65536
seconds). The RTC can give a compare interrupt and/or event when the counter equals the compare
register value, and an overflow interrupt and/or event when it equals the period register value.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 312
ATtiny1616/3216
RTC - Real-Time Counter
PIT - Periodic Interrupt Timer
Using the same clock source as the RTC function, the PIT can request an interrupt or trigger an output
event on every nth clock period. n can be selected from {4, 8, 16,.. 32768} for interrupts, and from {64,
128, 256,... 8192} for events.
The PIT uses the same clock source (CLK_RTC) as the RTC function.
Related Links
23.3 RTC Functional Description
23.4 PIT Functional Description
23.2.1
Block Diagram
Figure 23-1. Block Diagram
EXTCLK
32KHz ULP int. Osc.
DIV32
RTC
CLK_RTC
23.2.2
Signal Description
Not applicable.
23.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 23-1. RTC System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
Yes
CPUINT
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 313
ATtiny1616/3216
RTC - Real-Time Counter
...........continued
Dependency
Applicable
Peripheral
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
23.2.3.1 Clocks
23.2.3.2 I/O Lines and Connections
23.2.3.5 Debug Operation
23.2.3.3 Interrupts
23.2.3.4 Events
23.2.3.1 Clocks
System clock (CLK_PER) is required to be at least four times faster than the RTC clock (CLK_RTC) for
reading counter value, and this is regardless of the RTC_PRESC setting.
Related Links
10. CLKCTRL - Clock Controller
23.2.3.2 I/O Lines and Connections
A 32.768 kHz crystal can be connected to the TOSC1 or TOSC2 pins, along with any required load
capacitors.
An external clock can be used on the TOSC1 pin.
Related Links
10. CLKCTRL - Clock Controller
23.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
23.6 Interrupts
23.2.3.4 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
23.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
This peripheral can be forced to operate with halted CPU by writing a '1' to the Debug Run bit (DBGRUN)
in the Debug Control register of the peripheral (peripheral.DBGCTRL).
Related Links
33. UPDI - Unified Program and Debug Interface
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 314
ATtiny1616/3216
RTC - Real-Time Counter
23.3
RTC Functional Description
The RTC peripheral offers two timing functions: the Real-Time Counter (RTC) and a Periodic Interrupt
Timer (PIT). This subsection describes the RTC.
Related Links
23.4 PIT Functional Description
23.3.1
Initialization
To operate the RTC, the source clock for the RTC counter must be configured before enabling the RTC
peripheral, and the desired actions (interrupt requests, output Events).
Related Links
10. CLKCTRL - Clock Controller
23.4 PIT Functional Description
23.3.1.1 Configure the Clock CLK_RTC
To configure CLK_RTC, follow these steps:
1.
2.
Configure the desired oscillator to operate as required, in the Clock Controller peripheral
(CLKCTRL).
Write the Clock Select bits (CLKSEL) in the Clock Selection register (RTC.CLKSEL) accordingly.
The CLK_RTC clock configuration is used by both RTC and PIT functionality.
23.3.1.2 Configure RTC
To operate the RTC, follow these steps:
1.
2.
3.
Set the compare value in the Compare register (RTC.CMP), and/or the overflow value in the Top
register (RTC.PER).
Enable the desired interrupts by writing to the respective Interrupt Enable bits (CMP, OVF) in the
Interrupt Control register (RTC.INTCTRL).
Configure the RTC internal prescaler and enable the RTC by writing the desired value to the
PRESCALER bit field and a '1' to the RTC Enable bit (RTCEN) in the Control A register
(RTC.CTRLA).
Note: The RTC peripheral is used internally during device start-up. Always check the Busy bits in the
RTC.STATUS and RTC.PITSTATUS registers, also on initial configuration.
23.3.2
Operation - RTC
23.3.2.1 Enabling, Disabling, and Resetting
The RTC is enabled by setting the Enable bit in the Control A register (ENABLE bit in RTC.CTRLA to 1).
The RTC is disabled by writing ENABLE bit in RTC.CTRLA to 0.
23.4
PIT Functional Description
The RTC peripheral offers two timing functions: the Real-Time Counter (RTC) and a Periodic Interrupt
Timer (PIT). This subsection describes the PIT.
Related Links
23.3 RTC Functional Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 315
ATtiny1616/3216
RTC - Real-Time Counter
23.4.1
Initialization
To operate the PIT, follow these steps:
1. Configure the RTC clock CLK_RTC as described in 23.3.1.1 Configure the Clock CLK_RTC.
2. Enable the interrupt by writing a '1' to the Periodic Interrupt bit (PI) in the PIT Interrupt Control
register (RTC.PITINTCTRL).
3. Select the period for the interrupt and enable the PIT by writing the desired value to the PERIOD bit
field and a '1' to the PIT Enable bit (PITEN) in the PIT Control A register (RTC.PITCTRLA).
Note: The RTC peripheral is used internally during device start-up. Always check the Busy bits in the
RTC.STATUS and RTC.PITSTATUS registers, also on initial configuration.
23.4.2
Operation - PIT
23.4.2.1 Enabling, Disabling, and Resetting
The PIT is enabled by setting the Enable bit in the PIT Control A register (the PITEN bit in
RTC.PITCTRLA to 1). The PIT is disabled by writing the PITEN bit in RTC.PITCTRLA to 0.
23.4.2.2 PIT Interrupt Timing
Timing of the First Interrupt
The PIT function and the RTC function are running off the same counter inside the prescaler, but both
functions’ periods can be configured independently:
• The RTC period is configured by writing the PRESCALER bit field in RTC.CTRLA.
• The PIT period is configured by writing the PERIOD bit field in RTC.PITCTRLA.
The prescaler is OFF when both functions are OFF (RTC Enable bit (RTCEN) in RTC.CTRLA and PIT
Enable bit (PITEN) in RTC.PITCTRLA are zero), but it is running (i.e. its internal counter is counting)
when either function is enabled.
For this reason, the timing of the first PIT interrupt output is depending on whether the RTC function is
already enabled or not:
• When RTCEN in RTC.CTRLA is zero and PITEN in RTC.PITCTRLA is written to ‘1’, the prescaler will
start operating at the next edge of CLK_RTC, counting from zero. The PIT interrupt output will then
toggle from ‘0’ to ‘1’ after a ½ period.
• When the RTC function is already enabled (RTCEN is ‘1’), the prescaler is already running. The
timing of the first interrupt output from the PIT depends on the value of the counter when the
prescaler is enabled. Since the application can’t access that value, the first interrupt output may
occur anytime between writing PITEN to ‘1’ and up to a full PIT period after.
Continuous Operation
After the first interrupt output, the PIT will continue toggling every ½ PIT period, resulting in a full PIT
period signal.
Example 23-1. PIT Timing Diagram for PERIOD=CYC16
For PERIOD=CYC16 in RTC.PITCTRLA, the PIT output effectively follows the state of
prescaler counter bit 3, so the resulting interrupt output has a period of 16 CLK_RTC
cycles.
When both RTC and PIT functions are disabled, the prescaler is OFF. The delay between
writing PITEN to ‘1’ and the first interrupt output is always ½ PIT period, with an
uncertainty of one leading CLK_RTC cycle.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 316
ATtiny1616/3216
RTC - Real-Time Counter
When the RTC and hence the prescaler are already enabled with any
PRESCALER=DIVn, the time between writing PITEN to ‘1’ and the first PIT interrupt can
vary between virtually 0 and a full PIT period of 16 CLK_RTC cycles. The precise delay
between enabling the PIT and its first output is depending on the prescaler’s counting
phase: the depicted first interrupt in the lower figure is produced by writing PITEN to ‘1’ at
any time inside the leading time window.
Figure 23-2. Timing Between PIT Enable and First Interrupt
Enabling PIT with RTC/Prescaler Disabled
CLK_RTC
..000000
..000001
..000010
..000011
..000100
..000101
..000110
..000111
..001000
..001001
..001010
..001011
..001100
..001101
..001110
..001111
..010000
..010001
..010010
..010011
..010100
..010101
..010110
..010111
..011000
..011001
..011010
..011011
..011100
..011101
..011110
..011111
..100000
..100001
..100010
..100011
..100100
..100101
prescaler
counter
value (LSb)
prescaler bit 3
(CYC16)
Continuous Operation
PITENABLE=0
1/2 PIT period
(8 CLK_RTC)
PIT output
write PITENABLE=1
first PIT output
Enabling PIT with RTC/Prescaler Enabled
prescaler
counter
value (LSb)
..000000
..000001
..000010
..000011
..000100
..000101
..000110
..000111
..001000
..001001
..001010
..001011
..001100
..001101
..001110
..001111
..010000
..010001
..010010
..010011
..010100
..010101
..010110
..010111
..011000
..011001
..011010
..011011
..011100
..011101
..011110
..011111
..100000
..100001
..100010
..100011
..100100
..100101
..100110
..100111
..101000
..101001
..101010
..101011
..101100
..101101
..101110
..101111
CLK_RTC
prescaler bit 3
(CYC16)
Continuous Operation
PITENABLE=0
PIT output
time window for writing
PITENABLE=1
first PIT output
23.5
Events
The RTC, when enabled, will generate the following output events:
• Overflow (OVF): Generated when the counter has reached its top value and wrapped to zero. The
generated strobe is synchronous with CLK_RTC and lasts one CLK_RTC cycle.
• Compare (CMP): Indicates a match between the counter value and the Compare register. The
generated strobe is synchronous with CLK_RTC and lasts one CLK_RTC cycle.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 317
ATtiny1616/3216
RTC - Real-Time Counter
When enabled, the PIT generates the following 50% duty cycle clock signals on its event outputs:
•
•
•
•
•
•
•
•
Event 0: Clock period = 8192 RTC clock cycles
Event 1: Clock period = 4096 RTC clock cycles
Event 2: Clock period = 2048 RTC clock cycles
Event 3: Clock period = 1024 RTC clock cycles
Event 4: Clock period = 512 RTC clock cycles
Event 5: Clock period = 256 RTC clock cycles
Event 6: Clock period = 128 RTC clock cycles
Event 7: Clock period = 64 RTC clock cycles
The event users are configured by the Event System (EVSYS).
Related Links
14. EVSYS - Event System
23.6
Interrupts
Table 23-2. Available Interrupt Vectors and Sources
Offset Name Vector Description
0x00
RTC
Real-time counter
overflow and compare
match interrupt
0x02
PIT
Periodic Interrupt Timer
interrupt
Conditions
• Overflow (OVF): The counter has reached its top value
and wrapped to zero.
• Compare (CMP): Match between the counter value and
the compare register.
A time period has passed, as configured in
RTC_PITCTRLA.PERIOD.
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding enable bit in the peripheral's
Interrupt Control register (peripheral.INTCTRL).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
Related Links
13. CPUINT - CPU Interrupt Controller
23.11.3 INTCTRL
23.11.13 PITINTCTRL
23.7
Sleep Mode Operation
The RTC will continue to operate in Idle Sleep mode. It will run in Standby Sleep mode if the RUNSTDBY
bit in RTC.CTRLA is set.
The PIT will continue to operate in any sleep mode.
Related Links
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 318
ATtiny1616/3216
RTC - Real-Time Counter
23.11.1 CTRLA
23.8
Synchronization
Both the RTC and the PIT are asynchronous, operating from a different clock source (CLK_RTC)
independently of the main clock (CLK_PER). For Control and Count register updates, it will take a
number of RTC clock and/or peripheral clock cycles before an updated register value is available in a
register or until a configuration change has an effect on the RTC or PIT, respectively. This synchronization
time is described for each register in the Register Description section.
For some RTC registers, a Synchronization Busy flag is available (CMPBUSY, PERBUSY, CNTBUSY,
CTRLABUSY) in the STATUS register (RTC.STATUS).
For the RTC.PITCTRLA register, a Synchronization Busy flag (SYNCBUSY) is available in the PIT
STATUS register (RTC.PITSTATUS).
Check for busy should be performed before writing to the mentioned registers.
Related Links
10. CLKCTRL - Clock Controller
23.9
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 319
ATtiny1616/3216
RTC - Real-Time Counter
23.10
Register Summary - RTC
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
CTRLA
STATUS
INTCTRL
INTFLAGS
TEMP
DBGCTRL
Reserved
CLKSEL
7:0
7:0
7:0
7:0
7:0
7:0
0x08
CNT
0x0A
PER
0x0C
CMP
0x0E
...
0x0F
0x10
0x11
0x12
0x13
0x14
0x15
23.11
RUNSTDBY
PRESCALER[3:0]
CMPBUSY
PERBUSY
CNTBUSY
CMP
CMP
RTCEN
CTRLABUSY
OVF
OVF
TEMP[7:0]
DBGRUN
7:0
7:0
15:8
7:0
15:8
7:0
15:8
CLKSEL[1:0]
CNT[7:0]
CNT[15:8]
PER[7:0]
PER[15:8]
CMP[7:0]
CMP[15:8]
Reserved
PITCTRLA
PITSTATUS
PITINTCTRL
PITINTFLAGS
Reserved
PITDBGCTRL
7:0
7:0
7:0
7:0
PERIOD[3:0]
7:0
PITEN
CTRLBUSY
PI
PI
DBGRUN
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 320
ATtiny1616/3216
RTC - Real-Time Counter
23.11.1 Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
-
6
5
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
RUNSTDBY
Access
Reset
4
3
PRESCALER[3:0]
2
1
0
RTCEN
Bit 7 – RUNSTDBY Run in Standby
Value
Description
0
RTC disabled in Standby Sleep mode
1
RTC enabled in Standby Sleep mode
Bits 6:3 – PRESCALER[3:0] Prescaler
These bits define the prescaling of the CLK_RTC clock signal. Due to synchronization between the RTC
clock and system clock domains, there is a latency of two RTC clock cycles from updating the register
until this has an effect. Application software needs to check that the CTRLABUSY flag in RTC.STATUS is
cleared before writing to this register.
Value
Name
Description
0x0
DIV1
RTC clock/1 (no prescaling)
0x1
DIV2
RTC clock/2
0x2
DIV4
RTC clock/4
0x3
DIV8
RTC clock/8
0x4
DIV16
RTC clock/16
0x5
DIV32
RTC clock/32
0x6
DIV64
RTC clock/64
0x7
DIV128
RTC clock/128
0x8
DIV256
RTC clock/256
0x9
DIV512
RTC clock/512
0xA
DIV1024
RTC clock/1024
0xB
DIV2048
RTC clock/2048
0xC
DIV4096
RTC clock/4096
0xD
DIV8192
RTC clock/8192
0xE
DIV16384
RTC clock/16384
0xF
DIV32768
RTC clock/32768
Bit 0 – RTCEN RTC Enable
Value
Description
0
RTC disabled
1
RTC enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 321
ATtiny1616/3216
RTC - Real-Time Counter
23.11.2 Status
Name:
Offset:
Reset:
Property:
Bit
7
STATUS
0x01
0x00
-
6
5
4
3
2
1
0
CMPBUSY
PERBUSY
CNTBUSY
CTRLABUSY
Access
R
R
R
R
Reset
0
0
0
0
Bit 3 – CMPBUSY Compare Synchronization Busy
This bit is indicating whether the RTC is busy synchronizing the Compare register (RTC.CMP) in RTC
clock domain.
Bit 2 – PERBUSY Period Synchronization Busy
This bit is indicating whether the RTC is busy synchronizing the Period register (RTC.PER) in RTC clock
domain.
Bit 1 – CNTBUSY Counter Synchronization Busy
This bit is indicating whether the RTC is busy synchronizing the Count register (RTC.CNT) in RTC clock
domain.
Bit 0 – CTRLABUSY Control A Synchronization Busy
This bit is indicating whether the RTC is busy synchronizing the Control A register (RTC.CTRLA) in RTC
clock domain.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 322
ATtiny1616/3216
RTC - Real-Time Counter
23.11.3 Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
INTCTRL
0x02
0x00
-
6
5
4
3
Access
Reset
2
1
0
CMP
OVF
R/W
R/W
0
0
Bit 1 – CMP Compare Match Interrupt Enable
Enable interrupt-on-compare match (i.e., when the Counter value (CNT) matches the Compare value
(CMP)).
Bit 0 – OVF Overflow Interrupt Enable
Enable interrupt-on-counter overflow (i.e., when the Counter value (CNT) matched the Period value
(PER) and wraps around to zero).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 323
ATtiny1616/3216
RTC - Real-Time Counter
23.11.4 Interrupt Flag
Name:
Offset:
Reset:
Property:
Bit
7
INTFLAGS
0x03
0x00
-
6
5
4
3
2
1
0
CMP
OVF
Access
R
R
Reset
0
0
Bit 1 – CMP Compare Match Interrupt Flag
This flag is set when the Counter value (CNT) matches the Compare value (CMP).
Writing a '1' to this bit clears the flag.
Bit 0 – OVF Overflow Interrupt Flag
This flag is set when the Counter value (CNT) has reached the Period value (PER) and wrapped to zero.
Writing a '1' to this bit clears the flag.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 324
ATtiny1616/3216
RTC - Real-Time Counter
23.11.5 Temporary
Name:
Offset:
Reset:
Property:
TEMP
0x4
0x00
-
The Temporary register is used by the CPU for single-cycle, 16-bit access to the 16-bit registers of this
peripheral. It can be read and written by software. Refer to 16-bit access in the AVR CPU chapter. There
is one common Temporary register for all the 16-bit registers of this peripheral.
Bit
7
6
5
4
3
2
1
0
TEMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – TEMP[7:0] Temporary
Temporary register for read/write operations in 16-bit registers.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 325
ATtiny1616/3216
RTC - Real-Time Counter
23.11.6 Debug Control
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x05
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Debug Run
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 326
ATtiny1616/3216
RTC - Real-Time Counter
23.11.7 Clock Selection
Name:
Offset:
Reset:
Property:
Bit
7
CLKSEL
0x07
0x00
-
6
5
4
3
2
1
0
CLKSEL[1:0]
Access
Reset
R/W
R/W
0
0
Bits 1:0 – CLKSEL[1:0] Clock Select
Writing these bits select the source for the RTC clock (CLK_RTC).
When configuring the RTC to use either XOSC32K or the external clock on TOSC1, XOSC32K needs to
be enabled and the Source Select bit (SEL) and Run Standby bit (RUNSTDBY) in the XOSC32K Control
A register of the Clock Controller (CLKCTRL.XOSC32KCTRLA) must be configured accordingly.
Value
Name
Description
0x0
INT32K
32.768 kHz from OSCULP32K
0x1
INT1K
1.024 kHz from OSCULP32K
0x2
TOSC32K
32.768 kHz from XOSC32K or external clock from TOSC1
0x3
EXTCLK
External clock from EXTCLK pin
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 327
ATtiny1616/3216
RTC - Real-Time Counter
23.11.8 Count
Name:
Offset:
Reset:
Property:
CNT
0x08
0x00
-
The RTC.CNTL and RTC.CNTH register pair represents the 16-bit value, CNT. The low byte [7:0] (suffix
L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers in the CPU
chapter.
Due to synchronization between the RTC clock and system clock domains, there is a latency of two RTC
clock cycles from updating the register until this has an effect. Application software needs to check that
the CNTBUSY flag in RTC.STATUS is cleared before writing to this register.
Bit
15
14
13
12
11
10
9
8
CNT[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
CNT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – CNT[15:8] Counter High Byte
These bits hold the MSB of the 16-bit Counter register.
Bits 7:0 – CNT[7:0] Counter Low Byte
These bits hold the LSB of the 16-bit Counter register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 328
ATtiny1616/3216
RTC - Real-Time Counter
23.11.9 Period
Name:
Offset:
Reset:
Property:
PER
0x0A
0xFF
-
The RTC.PERL and RTC.PERH register pair represents the 16-bit value, PER. The low byte [7:0] (suffix
L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers in the CPU
chapter.
Due to synchronization between the RTC clock and system clock domains, there is a latency of two RTC
clock cycles from updating the register until this has an effect. Application software needs to check that
the PERBUSY flag in RTC.STATUS is cleared before writing to this register.
Bit
15
14
13
12
11
10
9
8
PER[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
1
1
1
1
1
1
1
1
Bit
7
6
5
4
3
2
1
0
PER[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
1
1
1
1
1
1
1
1
Bits 15:8 – PER[15:8] Period High Byte
These bits hold the MSB of the 16-bit Period register.
Bits 7:0 – PER[7:0] Period Low Byte
These bits hold the LSB of the 16-bit Period register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 329
ATtiny1616/3216
RTC - Real-Time Counter
23.11.10 Compare
Name:
Offset:
Reset:
Property:
CMP
0x0C
0x00
-
The RTC.CMPL and RTC.CMPH register pair represents the 16-bit value, CMP. The low byte [7:0] (suffix
L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset + 0x01. For
more details on reading and writing 16-bit registers, refer to Accessing 16-bit Registers in the CPU
chapter.
Bit
15
14
13
12
11
10
9
8
R/W
R/W
R/W
R/W
Reset
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
CMP[15:8]
Access
CMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – CMP[15:8] Compare High Byte
These bits hold the MSB of the 16-bit Compare register.
Bits 7:0 – CMP[7:0] Compare Low Byte
These bits hold the LSB of the 16-bit Compare register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 330
ATtiny1616/3216
RTC - Real-Time Counter
23.11.11 Periodic Interrupt Timer Control A
Name:
Offset:
Reset:
Property:
Bit
7
PITCTRLA
0x10
0x00
-
6
5
4
3
R/W
0
2
R/W
R/W
R/W
R/W
0
0
0
0
PERIOD[3:0]
Access
Reset
1
0
PITEN
Bits 6:3 – PERIOD[3:0] Period
Writing this bit field selects the number of RTC clock cycles between each interrupt.
Value
Name
Description
0x0
OFF
No interrupt
0x1
CYC4
4 cycles
0x2
CYC8
8 cycles
0x3
CYC16
16 cycles
0x4
CYC32
32 cycles
0x5
CYC64
64 cycles
0x6
CYC128
128 cycles
0x7
CYC256
256 cycles
0x8
CYC512
512 cycles
0x9
CYC1024
1024 cycles
0xA
CYC2048
2048 cycles
0xB
CYC4096
4096 cycles
0xC
CYC8192
8192 cycles
0xD
CYC16384
16384 cycles
0xE
CYC32768
32768 cycles
0xF
Reserved
Bit 0 – PITEN Periodic Interrupt Timer Enable
Writing a '1' to this bit enables the periodic interrupt timer.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 331
ATtiny1616/3216
RTC - Real-Time Counter
23.11.12 Periodic Interrupt Timer Status
Name:
Offset:
Reset:
Property:
Bit
7
PITSTATUS
0x11
0x00
-
6
5
4
3
2
1
0
CTRLBUSY
Access
R
Reset
0
Bit 0 – CTRLBUSY PITCTRLA Synchronization Busy
This bit indicates whether the RTC is busy synchronizing the Periodic Interrupt Timer Control A register
(RTC.PITCTRLA) in the RTC clock domain.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 332
ATtiny1616/3216
RTC - Real-Time Counter
23.11.13 PIT Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
PITINTCTRL
0x12
0x00
-
6
5
4
3
2
1
0
PI
Access
R/W
Reset
0
Bit 0 – PI Periodic interrupt
Value
Description
0
The periodic interrupt is disabled
1
The periodic interrupt is enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 333
ATtiny1616/3216
RTC - Real-Time Counter
23.11.14 PIT Interrupt Flag
Name:
Offset:
Reset:
Property:
Bit
7
PITINTFLAGS
0x13
0x00
-
6
5
4
3
2
1
0
PI
Access
R
Reset
0
Bit 0 – PI Periodic interrupt Flag
This flag is set when a periodic interrupt is issued.
Writing a '1' clears the flag.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 334
ATtiny1616/3216
RTC - Real-Time Counter
23.11.15 Periodic Interrupt Timer Debug Control
Name:
Offset:
Reset:
Property:
Bit
7
PITDBGCTRL
0x15
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Debug Run
Writing this bit to '1' will enable the PIT to run in Debug mode while the CPU is halted.
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 335
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.
USART - Universal Synchronous and Asynchronous Receiver and
Transmitter
24.1
Features
• Full-Duplex or One-Wire Half-Duplex Operation
• Asynchronous or Synchronous Operation:
– Synchronous clock rates up to 1/2 of the device clock frequency
– Synchronous Slave clock rates up to 1/4 of the device clock frequency
– Asynchronous clock rates up to 1/8 of the device clock frequency
• Supports Serial Frames with:
– 5, 6, 7, 8, or 9 data bits
– Optionally even and odd parity bits
– 1 or 2 Stop bits
• Fractional Baud Rate Generator:
– Can generate desired baud rate from any system clock frequency
– No need for an external oscillator with certain frequencies
• Built-In Error Detection and Correction Schemes:
– Odd or even parity generation and parity check
– Data overrun and framing error detection
– Noise filtering includes false Start bit detection and digital low-pass filter
• Separate Interrupts for:
– Transmit complete
– Transmit Data register empty
– Receive complete
• Multiprocessor Communication mode:
– Addressing scheme to address specific devices on a multi-device bus
– Enable unaddressed devices to automatically ignore all frames
• Start Frame Detection in UART mode
• Master SPI mode:
– Double-buffered operation
– Configurable data order
– Operation up to 1/2 of the peripheral clock frequency
• IRCOM Module for IrDA® Compliant Pulse Modulation/Demodulation
• LIN Slave Support:
– Auto-baud and Break character detection
• RS-485 Support
24.2
Overview
The Universal Synchronous and Asynchronous serial Receiver and Transmitter (USART) peripheral is a
fast and flexible serial communication module. The USART supports full duplex communication,
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 336
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
asynchronous and synchronous operation, and one-wire configurations. The USART can be set in SPI
Master mode and used for SPI communication.
The USART uses three communication lines for data transfer:
• RxD for receiving
• TxD for transmitting
• XCK for the transmission clock in synchronous operation
Communication is frame based, and the frame format can be customized to support a wide range of
standards. One frame can be directly followed by a new frame, or the communication line can return to
the idle (high) state. A serial frame consists of:
• 1 Start bit
• 5, 6, 7, 8, or 9 data bits (MSb or LSb first)
• Parity bit: Even, odd, or none
• 1 or 2 Stop bits
The USART is buffered in both directions, enabling continued data transmission without any delay
between frames. Separate interrupts for receive and transmit completion allow fully interrupt driven
communication. Frame error and buffer overflow are detected in hardware and indicated with separate
status flags. Even or odd parity generation and parity check can also be enabled.
The main functional blocks are the clock generator, the transmitter, and the receiver:
• The clock generator includes a fractional Baud Rate Generator that is able to generate a wide range
of USART baud rates from any system clock frequencies. This removes the need to use an oscillator
with a specific frequency to achieve a required baud rate. It also supports external clock input in
synchronous slave operation.
• The transmitter consists of a single write buffer (DATA), a shift register, and a parity generator. The
write buffer allows continuous data transmission without any delay between frames.
• The receiver consists of a two-level receive buffer (DATA) and a Shift register. Data and clock
recovery units ensure robust synchronization and noise filtering during asynchronous data reception.
It includes frame error, buffer overflow, and parity error detection.
When the USART is set in one-wire mode, the transmitter and the receiver share the same TxD I/O pin.
When the USART is set in Master SPI mode, all USART-specific logic is disabled, leaving the transmit
and receive buffers, Shift registers, and Baud Rate Generator enabled. Pin control and interrupt
generation are identical in both modes. The registers are used in both modes, but their functionality
differs for some control settings.
An IRCOM module can be enabled for one USART to support IrDA 1.4 physical compliant pulse
modulation and demodulation for baud rates up to 115.2 kbps.
The USART can be linked to the Configurable Custom Logic unit (CCL). When used with the CCL, the
TxD/RxD data can be encoded/decoded before the signal is fed into the USART receiver or after the
signal is output from the transmitter when the USART is connected to CCL LUT outputs.
This device provides one instance of the USART peripheral, USART0.
24.2.1
Signal Description
Signal
Type
Description
RxD
Input
Receiving line
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 337
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
...........continued
Signal
Type
Description
TxD
Input/Output
Transmitting line
XCK
Input/output
Clock for synchronous operation
XDIR
Output
Transmit Enable for RS485
Related Links
5. I/O Multiplexing and Considerations
24.2.2
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 24-1. USART System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
24.2.2.5 Debug Operation
24.2.2.1 Clocks
24.2.2.2 I/O Lines and Connections
24.2.2.3 Interrupts
24.2.2.4 Events
24.2.2.1 Clocks
This peripheral depends on the peripheral clock.
Related Links
10. CLKCTRL - Clock Controller
24.2.2.2 I/O Lines and Connections
Using the I/O lines of the peripheral requires configuration of the I/O pins.
Related Links
16. PORT - I/O Pin Configuration
5. I/O Multiplexing and Considerations
24.2.2.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 338
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.3.4 Interrupts
24.2.2.4 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
24.2.2.5 Debug Operation
When the CPU is halted in Debug mode, this peripheral will continue normal operation. If the peripheral is
configured to require periodical service by the CPU through interrupts or similar, improper operation or
data loss may result during debugging. This peripheral can be forced to halt operation during debugging.
Related Links
33. UPDI - Unified Program and Debug Interface
24.2.2.6 Block Diagram
Figure 24-1. USART Block Diagram
CLOCK GENERATOR
BAUD
XCK
Baud Rate Generator
TRANSMITTER
XDIR
TXDATA
TX Shift Register
TXD
RECEIVER
RX Buffer
RX Shift Register
RXD
RXDATA
24.3
Functional Description
24.3.1
Initialization
For setting the USART in Full-Duplex mode, the following initialization sequence is recommended:
1.
2.
3.
4.
5.
Set the TxD pin value high, and optionally set the XCK pin low (OUT[n] in PORTx.OUT).
Set the TxD and optionally the XCK pin as an output (DIR[n] in PORTx.DIR).
Set the baud rate (in the USARTn.BAUD register) and frame format.
Set the mode of operation (enables XCK pin output in Synchronous mode).
Enable the transmitter or the receiver, depending on the usage.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 339
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
For interrupt-driven USART operation, global interrupts should be disabled during the initialization.
Before doing a re-initialization with a changed baud rate or frame format, be sure that there are no
ongoing transmissions while the registers are changed.
For setting the USART in One-Wire mode, the following initialization sequence is recommended:
1.
2.
3.
4.
5.
6.
Set the TxD/RxD pin value high, and optionally set the XCK pin low.
Optionally, write the ODME bit in the USARTn.CTRLB register to '1' for Wired-AND functionality.
Set the TxD/RxD and optionally the XCK pin as an output.
Select the baud rate and frame format.
Select the mode of operation (enables XCK pin output in Synchronous mode).
Enable the transmitter or the receiver, depending on the usage.
For interrupt-driven USART operation, global interrupts should be disabled during the initialization.
Before doing a re-initialization with a changed baud rate or frame format, be sure that there are no
ongoing transmissions while the registers are changed.
24.3.2
Operation
24.3.2.1 Clock Generation
The clock used for baud rate generation and for shifting and sampling data bits is generated internally by
the fractional Baud Rate Generator or externally from the transfer clock (XCK) pin. Five modes of clock
generation are supported; Normal and Double-Speed Asynchronous mode, Master and Slave
Synchronous mode, and Master SPI mode.
Figure 24-2. Clock Generation Logic Block Diagram
BAUD
RXMODE
BAUD Rate
Generator
fBAUD
/2
/4
/2
1
CLK_PER
XCK
Pin
0
1
txclk
DDR_XCK
PORT_INV
xcki
0
Sync
Register
Edge
Detector
xcko
CMODE[0]
0
1
1
0
DDR_XCK
rxclk
24.3.2.1.1 Internal Clock Generation - The Fractional Baud Rate Generator
The Baud Rate Generator is used for internal clock generation for Asynchronous modes, Synchronous
master mode, and Master SPI mode operation. The output frequency generated (fBAUD) is determined by
the baud register value (BAUD) and the peripheral clock frequency (fCLK_PER).
In Asynchronous mode, the BAUD register value uses all 16 bits. The 10 msb (BAUD[15:6]) hold the
integer part, while the 6 lsb (BAUD[5:0]) hold the fractional part. Non-standard BAUD frequencies can
result in fractional parts, which if ignored introduce an error in the approximation to the desired BAUD
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 340
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
frequency. The BAUD fractional part is used to reduce this error by adjusting the sampling point. BAUD
register values below 64 are not supported, as the integer part needs to be at least 1. The integer part
valid range is therefore 64 to 65535.
In Synchronous mode, only the 10-bit integer part of the BAUD register, i.e. BAUD[15:6], determine the
baud rate. The fractional part must be written to zero.
The following table lists equations for translating between BAUD register values and baud rates. The
equations take BAUD register bit width and fractional interpretation into consideration. The BAUD register
values calculated with these equations can be written directly to the BAUD register without any additional
scaling. Resulting rounding errors will contribute to baud rate frequency errors.
Table 24-2. Equations for Calculating Baud Rate Register Setting
Operating Mode Conditions
Asynchronous
Synchronous
Baud Rate (�����, Bits Per USART.BAUD Register Value
Calculation
Seconds)
����� ≤
����_���
�
����_���
× 26
� × ����
�����
����_���
× 26
� × �����
����� ≤
����_���
2
����_���
× 26
2 × ����
�����
����_���
× 26
2 × �����
�����.���� ≥ 64
S = 16 if in Receiver mode (USART.CTRLB, RXMODE) is configured as NORMAL, and S = 8 if
configured as CLK2X. S determines the number of samples taken for each USART symbol.
24.3.2.1.2 Synchronous Slave External Clock limitations
An External clock (XCK) is used in Synchronous Slave mode operation. The XCK clock input is sampled
on the peripheral clock frequency and the maximum XCK clock frequency (fXCK) is limited by the
following:
The USART will perform clock recovery on the external clock (XCK) signal when configured in
Synchronous Slave mode, configuring the BAUD register will therefore have no impact on the transfer
speed. The XCK signal must be sampled twice for each rising and falling edge to achieve successful
clock recovery. The maximum XCK speed in Synchronous operation mode is therefore limited by the
following:
������_���<
����_���
4
If the XCK clock has jitter, or if the high/low period duty cycle is not 50/50, the maximum XCK clock speed
must be reduced accordingly to ensure that XCK is sampled a minimum of 2 times for each edge.
24.3.2.1.3 Double Speed Operation
Double speed operation allows for higher baud rates under asynchronous operation with lower peripheral
clock frequencies. This operation mode is enabled by writing the RXMODE bit in the Control B register
(USARTn.CTRLB) to CLK2X.
When enabled, the baud rate for a given asynchronous baud rate setting shown in Table 24-2 will be
doubled. In this mode, the receiver will use half the number of samples (reduced from 16 to 8) for data
sampling and clock recovery. This requires a more accurate baud rate setting and peripheral clock. See
24.3.2.4.6 Asynchronous Data Reception for more details.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 341
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.3.2.1.4 Synchronous Clock Operation
When Synchronous mode is used, the XCK pin controls whether the transmission clock is input (Slave
mode) or output (Master mode). The corresponding port pin must be set to output for Master mode or to
input for Slave mode (PORTx.DIR[n]). The normal port operation of the XCK pin will be overridden. The
dependency between the clock edges and data sampling or data change is the same. Data input (on
RxD) is sampled at the XCK clock edge which is opposite the edge where data output (TxD) is changed.
Figure 24-3. Synchronous Mode XCK Timing
INVEN = 1
XCK
RxD / TxD
Sample
INVEN = 0
XCK
RxD / TxD
Sample
The I/O pin can be inverted by writing a '1' to the Inverted I/O Enable bit (INVEN) in the Pin n Control
register of the port peripheral (PORTx.PINnCTRL). Using the inverted I/O setting for the corresponding
XCK port pin, the XCK clock edges used for data sampling and data change can be selected. If inverted
I/O is disabled (INVEN=0), data will be changed at the rising XCK clock edge and sampled at the falling
XCK clock edge. If inverted I/O is enabled (INVEN=1), data will be changed at the falling XCK clock edge
and sampled at the rising XCK clock edge.
24.3.2.1.5 Master SPI Mode Clock Generation
For Master SPI mode operation, only internal clock generation is supported. This is identical to the
USART Synchronous Master mode, and the baud rate or BAUD setting is calculated using the same
equations (see Table 24-2).
There are four combinations of the SPI clock (SCK) phase and polarity with respect to the serial data, and
these are determined by the Clock Phase bit (UCPHA) in the Control C register (USARTn.CTRLC) and
the Inverted I/O Enable bit (INVEN) in the Pin n Control register of the port peripheral
(PORTx.PINnCTRL). The data transfer timing diagrams are shown in Figure 24-4.
Data bits are shifted out and latched in on opposite edges of the XCK signal, ensuring sufficient time for
data signals to stabilize. The settings are summarized in the table below. Changing the setting of any of
these bits during transmission will corrupt both the receiver and transmitter.
Table 24-3. Functionality of INVEN in PORTx.PINnCTRL and UCPHA in USARTn.CTRLC
SPI Mode
INVEN
UCPHA
Leading Edge
Trailing Edge
0
0
0
Rising, sample
Falling, setup
1
0
1
Rising, setup
Falling, sample
2
1
0
Falling, sample
Rising, setup
3
1
1
Falling, setup
Rising, sample
The leading edge is the first clock edge of a clock cycle. The trailing edge is the last clock edge of a clock
cycle.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 342
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Figure 24-4. UCPHA and INVEN Data Transfer Timing Diagrams
INVEN=0
INVEN=1
XCK
Data setup (TXD)
Data sample (RXD)
UCPHA=1
SPI Mode 3
XCK
Data setup (TXD)
Data sample (RXD)
UCPHA=0
SPI Mode 1
SPI Mode 0
SPI Mode 2
XCK
Data setup (TXD)
Data sample (RXD)
XCK
Data setup (TXD)
Data sample (RXD)
Related Links
24.5.9 CTRLC
24.3.2.2 Frame Formats
Data transfer is frame based, where a serial frame consists of one character of data bits with
synchronization bits (Start and Stop bits) and an optional parity bit for error checking. This does not apply
to master SPI operation (see 24.3.2.2.2 SPI Frame Formats.) The USART accepts all combinations of
the following as valid frame formats:
•
•
•
•
1 Start bit
5, 6, 7, 8, or 9 Data bits
No, even, or odd Parity bit
1 or 2 Stop bits
Figure 24-5 illustrates the possible combinations of frame formats. Bits inside brackets are optional.
Figure 24-5. Frame Formats
Table 24-4. Frame Format Nomenclature
Symbol
Meaning
St
Start bit, always low
(n)
Data bits (0 to 8)
P
Parity bit, may be odd or even
Sp
Stop bit, always high
IDLE
No transfer on the communication line (RxD or TxD). The IDLE state is always high
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 343
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.3.2.2.1 Parity
Even or odd parity can be selected for error checking by writing the Parity Mode bits (PMODE) in the
Control C register (USARTn.CTRLC). If even parity is selected, the parity bit is set to ‘1’ if the number of
logical ‘1’ data bits is odd (making the total number of logical ‘1’ even). If odd parity is selected, the parity
bit is set to ‘1’ if the number of logical ‘1’ data bits is even (making the total number of ‘1’s odd).
When enabled, the parity checker calculates the parity of the data bits in incoming frames and compares
the result with the parity bit of the corresponding frame. If a parity error is detected, the parity error flag is
set.
24.3.2.2.2 SPI Frame Formats
The serial frame in SPI mode is defined to be one character of eight data bits. The USART in master SPI
mode has two valid frame formats:
• 8-bit data, MSb first
• 8-bit data, LSb first
The data order is selected by writing to the Data Order bit (UDORD) in the Control C register
(USARTn.CTRLC).
After a complete frame is transmitted, a new frame can directly follow it, or the communication line can
return to the idle (high) state.
24.3.2.3 Data Transmission - USART Transmitter
When the transmitter has been enabled, the normal port operation of the TxD pin is overridden by the
USART and given the function as the transmitter's serial output. The direction of the pin n must be
configured as output by writing the Direction register for the corresponding port (PORTx.DIR[n]). If the
USART is configured for one-wire operation, the USART will automatically override the RxD/TxD pin to
output, when the transmitter is enabled.
Related Links
15. PORTMUX - Port Multiplexer
16. PORT - I/O Pin Configuration
24.3.2.3.1 Sending Frames
A data transmission is initiated by loading the Transmit buffer (DATA in USARTn.TXDATA) with the data
to be sent. The data in the transmit buffer is moved to the Shift register when the Shift register is empty
and ready to send a new frame. The Shift register is loaded if it is in Idle state (no ongoing transmission)
or immediately after the last Stop bit of the previous frame is transmitted. When the Shift register is
loaded with data, it will transfer one complete frame.
When the entire frame in the Shift register has been shifted out and there is no new data present in the
transmit buffer, the Transmit Complete Interrupt Flag (TXCIF in USARTn.STATUS) is set and the optional
interrupt is generated.
TXDATA can only be written when the Data Register Empty Flag (DREIF in USARTn.STATUS) is set,
indicating that the register is empty and ready for new data.
When using frames with fewer than eight bits, the Most Significant bits written to TXDATA are ignored. If
9-bit characters are used, DATA[8] in USARTn.TXDATAH has to be written before DATA[7:0] in
USARTn.TXDATAL.
24.3.2.3.2 Disabling the Transmitter
A disabling of the transmitter will not become effective until ongoing and pending transmissions are
completed; I.e., when the Transmit Shift register and Transmit Buffer register do not contain data to be
transmitted. When the transmitter is disabled, it will no longer override the TxDn pin, and the PORT
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 344
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
module regains control over the pin. To protect external circuitry the pin is automatically configured as an
input by hardware. The pin can now be used as a normal I/O pin with no port override from the USART.
24.3.2.4 Data Reception - USART Receiver
When the receiver is enabled, the RxD pin functions as the receiver's serial input. The direction of the pin
n must be set as an input in the Direction register of the Port (PORTx.DIR[n]=0), which is the default pin
setting.
24.3.2.4.1 Receiving Frames
The receiver starts data reception when it detects a valid Start bit. Each bit that follows the Start bit will be
sampled at the baud rate or XCK clock, and shifted into the Receive Shift register until the first Stop bit of
a frame is received. A second Stop bit will be ignored by the receiver. When the first Stop bit is received
and a complete serial frame is present in the Receive Shift register, the contents of the Shift register will
be moved into the receive buffer. The receive complete interrupt flag (RXCIF in USARTn.STATUS) is set,
and the optional interrupt is generated.
The receiver buffer can be read by reading RXDATA, comprising of DATA[7:0] in USARTn.RXDATAL, and
DATA[8] in USARTn.RXDATAH. RXDATA should not be read unless the Receive Complete Interrupt Flag
(RXCIF in USARTn.STATUS) is set. When using frames with fewer than eight bits, the unused Most
Significant bits are read as zero. If 9-bit characters are used, the ninth bit (DATA[8] in
USARTn.RXDATAH) must be read before the low byte (DATA[7.0] in USARTn.RXDATAL).
24.3.2.4.2 Receiver Error Flags
The USART receiver has three error flags in the Receiver Data Register High Byte register
(USARTn.RXDATAH):
• Frame Error (FERR)
• Buffer Overflow (BUFOVF)
• Parity Error (PERR)
The error flags are located in the receive FIFO buffer together with their corresponding frame. Due to the
buffering of the error flags, the USARTn.RXDATAH must be read before the USARTn.RXDATAL, since
reading the USARTn.RXDATAL changes the FIFO buffer.
24.3.2.4.3 Parity Checker
When enabled, the parity checker calculates the parity of the data bits in incoming frames and compares
the result with the parity bit of the corresponding frame. If a parity error is detected, the Parity Error flag
(PERR in USARTn.RXDATAH) is set.
If USART LIN mode is enabled (by writing RXMODE to '1' in USARTn.CTRLB), a parity check is only
performed on the protected identifier field. A parity error is detected if one of the equations below is not
true, which sets PERR in USARTn.RXDATAH.
�0 = ��0 XOR ��1 XOR ��2 XOR ��4
�1 = NOT ��1 XOR ��3 XOR ��4 XOR ��5
Figure 24-6. Protected Identifier Field and Mapping of Identifier and Parity Bits
Protected identifier field
St
ID0 ID1 ID2 ID3 ID4 ID5 P0
P1
Sp
24.3.2.4.4 Disabling the Receiver
A disabling of the receiver will be immediate. The receiver buffer will be flushed, and data from ongoing
receptions will be lost.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 345
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.3.2.4.5 Flushing the Receive Buffer
If the receive buffer has to be flushed during normal operation, read the DATA location
(USARTn.RXDATAH and USARTn.RXDATAL registers) until the Receive Complete Interrupt Flag (RXCIF
in USARTn.RXDATAH) is cleared.
24.3.2.4.6 Asynchronous Data Reception
The USART includes a clock recovery and a data recovery unit for handling asynchronous data reception.
The clock recovery unit is used for synchronizing the incoming asynchronous serial frames at the RxD pin
to the internally generated baud rate clock. It samples and low-pass filters each incoming bit, thereby
improving the noise immunity of the receiver. The asynchronous reception operational range depends on
the accuracy of the internal baud rate clock, the rate of the incoming frames, and the frame size in a
number of bits.
Asynchronous Clock Recovery
The clock recovery unit synchronizes the internal clock to the incoming serial frames. Figure 24-7
illustrates the sampling process for the Start bit of an incoming frame:
• In Normal mode, the sample rate is 16 times the baud rate.
• In Double-Speed mode, the sample rate is eight times the baud rate.
• The horizontal arrows illustrate the synchronization variation due to the sampling process. Note that
in Double-Speed mode, the variation is larger.
• Samples denoted as zero are sampled with the RxD line idle (i.e., when there is no communication
activity).
Figure 24-7. Start Bit Sampling
RxD
IDLE
START
BIT 0
Sample
(RXMODE = 0x0)
0
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
2
3
Sample
(RXMODE = 0x1)
0
1
2
3
4
5
6
7
8
1
2
When the clock recovery logic detects a high-to-low (i.e., idle-to-start) transition on the RxD line, the Start
bit detection sequence is initiated. Sample 1 denotes the first zero-sample, as shown in the figure. The
clock recovery logic then uses three subsequent samples (samples 8, 9, and 10 in Normal mode,
samples 4, 5, and 6 in Double-Speed mode) to decide if a valid Start bit is received:
• If two or three samples have a low level, the Start bit is accepted. The clock recovery unit is
synchronized, and the data recovery can begin.
• If two or three samples have a high level, the Start bit is rejected as a noise spike, and the receiver
looks for the next high-to-low transition.
The process is repeated for each Start bit.
Asynchronous Data Recovery
The data recovery unit uses sixteen samples in Normal mode and eight samples in Double-Speed mode
for each bit. The following figure shows the sampling process of data and parity bits.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 346
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Figure 24-8. Sampling of Data and Parity Bits
RxD
BIT n
Sample
(CLK2X = 0)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
1
Sample
(CLK2X = 1)
1
2
3
4
5
6
7
8
1
As for Start bit detection, an identical majority voting technique is used on the three center samples for
deciding of the logic level of the received bit. The process is repeated for each bit until a complete frame
is received. It includes the first Stop bit but excludes additional ones. If the sampled Stop bit is a '0' value,
the Frame Error (FERR in USARTn.RXDATAH) flag will be set. The next figure shows the sampling of the
Stop bit in relation to the earliest possible beginning of the next frame's Start bit.
Figure 24-9. Stop Bit and Next Start Bit Sampling
RxD
STOP 1
(A)
(B)
(C)
Sample
(CLK2X = 0)
1
2
3
4
5
6
7
8
9
10
0/1
0/1
0/1
Sample
(CLK2X = 1)
1
2
3
4
5
6
0/1
A new high-to-low transition indicating the Start bit of a new frame can come right after the last of the bits
used for majority voting. For Normal-Speed mode, the first low-level sample can be at the point marked
(A) in Stop Bit Sampling and Next Start Bit Sampling. For Double-Speed mode, the first low level must be
delayed to point (B). Point (C) marks a Stop bit of full length at the nominal baud rate. The early Start bit
detection influences the operational range of the receiver.
24.3.2.4.7 Asynchronous Operational Range
The operational range of the receiver is dependent on the mismatch between the received bit rate and
the internally generated baud rate. If an external transmitter is sending using bit rates that are too fast or
too slow, or if the internally generated baud rate of the receiver does not match the external source’s base
frequency, the receiver will not be able to synchronize the frames to the Start bit.
The following equations can be used to calculate the ratio of the incoming data rate and internal receiver
baud rate.
����� =
16 � + 1
16 � + 1 + 6
Table 24-5. Formula Nomenclature
����� =
16 � + 2
16 � + 1 + 8
Symbol
Meaning
D
Sum of character size and parity size (D = 5 to 10 bit)
Rslow
The ratio of the slowest incoming data rate that can be accepted in relation to the
receiver baud rate
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 347
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
...........continued
Symbol
Meaning
Rfast
The ratio of the fastest incoming data rate that can be accepted in relation to the
receiver baud rate
The following tables list the maximum receiver baud rate error that can be tolerated. Normal Speed mode
has higher toleration of baud rate variations.
Table 24-6. Recommended Maximum Receiver Baud Rate Error for Normal Speed Mode (CLK2X =
0)
D #(Data + Parity Bit) Rslow [%] Rfast [%] Maximum Total Error [%] Receiver Max. Receiver
Error [%]
5
93.20
106.67
+6.67/-6.80
±3.0
6
94.12
105.79
+5.79/-5.88
±2.5
7
94.81
105.11
+5.11/-5.19
±2.0
8
95.36
104.58
+4.58/-4.54
±2.0
9
95.81
104.14
+4.14/-4.19
±1.5
10
96.17
103.78
+3.78/-3.83
±1.5
Table 24-7. Recommended Maximum Receiver Baud Rate Error for Double Speed Mode (CLK2X =
1)
D #(Data + Parity Bit) Rslow [%] Rfast [%] Maximum Total Error [%] Receiver Max. Receiver
Error [%]
5
94.12
105.66
+5.66/-5.88
±2.5
6
94.92
104.92
+4.92/-5.08
±2.0
7
95.52
104.35
+4.35/-4.48
±1.5
8
96.00
103.90
+3.90/-4.00
±1.5
9
96.39
103.53
+3.53/-3.61
±1.5
10
96.70
103.23
+3.23/-3.30
±1.0
The recommendations of the maximum receiver baud rate error were made under the assumption that
the receiver and transmitter equally divide the maximum total error.
24.3.2.5 USART in Master SPI mode
Using the USART in Master SPI mode requires the transmitter to be enabled. The receiver can optionally
be enabled to serve as the serial input. The XCK pin will be used as the transfer clock.
As for the USART, a data transfer is initiated by writing to the USARTn.DATA register. This is the case for
both sending and receiving data since the transmitter controls the transfer clock. The data written to
USARTn.DATA are moved from the transmit buffer to the Shift register when the Shift register is ready to
send a new frame.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 348
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
The transmitter and receiver interrupt flags and corresponding USART interrupts used in Master SPI
mode are identical in function to their use in normal USART operation. The receiver error status flags are
not in use and are always read as zero.
Disabling of the USART transmitter or receiver in Master SPI mode is identical to their disabling in normal
USART operation.
Related Links
24.5.9 CTRLC
24.3.2.5.1 USART SPI vs. SPI
The USART in Master SPI mode is fully compatible with the stand-alone SPI module in that:
• Timing diagrams are the same
• UCPHA bit functionality is identical to that of the SPI CPHA bit
• UDORD bit functionality is identical to that of the SPI DORD bit
When the USART is set in Master SPI mode, configuration and use are in some cases different from
those of the stand-alone SPI module. In addition, the following difference exists:
• The USART in Master SPI mode does not include the SPI Write Collision feature
The USART in Master SPI mode does not include the SPI Double-Speed mode feature, but this can be
achieved by configuring the Baud Rate Generator accordingly:
• Interrupt timing is not compatible
• Pin control differs due to the master-only operation of the USART in SPI Master mode
A comparison of the USART in Master SPI mode and the SPI pins is shown in Table 24-8.
Table 24-8. Comparison of USART in Master SPI Mode and SPI Pins
USART
SPI
Comment
TxD
MOSI
Master out only
RxD
MISO
Master in only
XCK
SCK
Functionally identical
-
SS
Not supported by USART in Master SPI mode
Related Links
24.5.9 CTRLC
24.3.2.6 RS-485 Mode of Operation
The RS-485 feature enables the support of external components to comply with the RS-485 standard.
Either an external line driver is supported as shown in the figure below (RS485=0x1 in USARTn.CTRLA),
or control of the transmitter driving the TxD pin is provided (RS485=0x2).
While operating in RS-485 mode, the Transmit Direction pin (XDIR) is driven high when the transmitter is
active.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 349
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Figure 24-10. RS-485 Bus Connection
VDD
USART
RxD
XDIR
Differential
bus
TxD
The XDIR pin goes high one baud clock cycle in advance of data being shifted out, to allow some guard
time to enable the external line driver. The XDIR pin will remain high for the complete frame including
Stop bit(s).
Figure 24-11. XDIR Drive Timing
TxD
St
0
1
2
3
4
5
6
7
Sp1
XDIR
Guard
time
Stop
Related Links
24.2.1 Signal Description
24.3.2.7 Start Frame Detection
The start frame detection is supported in UART mode only. The UART start frame detector is limited to
Standby Sleep mode only and can wake up the system when a Start bit is detected.
When a high-to-low transition is detected on RxDn, the oscillator is powered up and the UART clock is
enabled. After start-up, the rest of the data frame can be received, provided that the baud rate is slow
enough in relation to the oscillator start-up time. Start-up time of the oscillators varies with supply voltage
and temperature. For details on oscillator start-up time characteristics, refer to the Electrical
Characteristics.
If a false Start bit is detected and if the system has not been woken up by another source, the clock will
automatically be turned OFF and the UART waits for the next transition.
The UART start frame detection works in Asynchronous mode only. It is enabled by writing the Start
Frame Detection bit (SFDEN) in USARTn.CTLB. If the Start bit is detected while the device is in Standby
Sleep mode, the UART Start Interrupt Flag (RXSIF) bit is set.
In Active, Idle, and Power-Down Sleep modes, the asynchronous detection is automatically disabled.
The UART receive complete flag and UART start interrupt flag share the same interrupt line, but each has
its dedicated interrupt settings. Table 24-9 shows the USART start frame detection modes, depending on
interrupt setting.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 350
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Table 24-9. USART Start Frame Detection Modes
SFDEN RXSIF Interrupt RXCIF Interrupt Comment
0
x
x
Standard mode.
1
Disabled
Disabled
Only the oscillator is powered during the frame reception.
If the interrupts are disabled and buffer overflow is
ignored, all incoming frames will be lost.
1 (1)
Disabled
Enabled
System/all clocks are awakened on Receive Complete
interrupt.
1 (1)
Enabled
x
System/all clocks are awakened on UART Start Detection.
Note:
1. The SLEEP instruction will not shut down the oscillator if there is ongoing communication.
24.3.2.8 Break Character Detection and Auto-Baud
When USART receive mode is set to LINAUTO mode (RXMODE in USARTn.CTRLB), it follows the LIN
format. All LIN frames start with a break field followed by a sync field. The USART uses a break detection
threshold of greater than 11 nominal bit times at the configured baud rate. At any time, if more than 11
consecutive dominant bits are detected on the bus, the USART detects a break field. When a break field
has been detected, the USART expects the sync field character to be 0x55. This field is used to update
the actual baud rate in order to stay synchronized. If the received sync character is not 0x55, then the
Inconsistent Sync Field Error flag (ISFIF in USARTn.STATUS) is set and the baud rate is unchanged.
Figure 24-12. LIN Break and Sync Fields
Break Field
Sync Field
Tbit
8 Tbit
After a break field is detected and the Start bit of the sync field is detected, a counter is started. The
counter is then incremented for the next eight Tbit of the sync field. At the end of these 8-bit times, the
counter is stopped. At this moment, the ten Most Significant bits of the counter (value divided by 64) gives
the new clock divider and the six Least Significant bits of this value (the remainder) gives the new
fractional part. When the sync field has been received and all bits are found valid, the clock divider and
the fractional part are updated in the Baud Rate Generator register (USARTn.BAUD). After the break and
sync fields, n characters of data can be received.
When the USART receive mode is set to GENAUTO mode, a generic Auto-baud mode is enabled. In this
mode, there are no checks of the sync character to equal 0x55. After detection of a break field, the
USART expects the next character to be a sync field, counting eight low and high bit times. If the
measured sync field results in a valid BAUD value (0x0064-0xffff), the BAUD register is updated. Setting
the Wait for Break bit (WFB in USARTn.STATUS) before receiving the next break character, the next
negative plus positive edge of RxD line is detected as a break. This makes it possible to set an arbitrary
new baud rate without knowing the current baud rate.
24.3.2.9 One-Wire Mode
In this mode, the TxD output is fed directly into the Receiver Data Register. If the receiver is enabled
when transmitting, it will receive what the transmitter is sending. This can be used to check that no one
else is trying to transmit since received data will not be the same as the transmitted data.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 351
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.3.2.10 Multiprocessor Communication Mode
The Multiprocessor Communication mode (MCPM) effectively reduces the number of incoming frames
that have to be handled by the receiver in a system with multiple microcontrollers communicating via the
same serial bus. This mode is enabled by writing a '1' to the MCPM bit in the Control B register
(USARTn.CTRLB). In this mode, a dedicated bit in the frames is used to indicate whether the frame is an
address or data frame type.
If the receiver is set up to receive frames that contain five to eight data bits, the first Stop bit is used to
indicate the frame type. If the receiver is set up for frames with nine data bits, the ninth bit is used to
indicate frame type. When the frame type bit is one, the frame contains an address. When the frame type
bit is zero, the frame is a data frame. If 5- to 8-bit character frames are used, the transmitter must be set
to use two Stop bits, since the first Stop bit is used for indicating the frame type.
If a particular slave MCU has been addressed, it will receive the following data frames as usual, while the
other slave MCUs will ignore the frames until another address frame is received.
24.3.2.10.1 Using Multiprocessor Communication Mode
The following procedure should be used to exchange data in Multiprocessor Communication mode
(MPCM):
1.
2.
3.
4.
5.
All slave MCUs are in Multiprocessor Communication mode.
The master MCU sends an address frame, and all slaves receive and read this frame.
Each slave MCU determines if it has been selected.
The addressed MCU will disable MPCM and receive all data frames. The other slave MCUs will
ignore the data frames.
When the addressed MCU has received the last data frame, it must enable MPCM again and wait
for a new address frame from the master.
The process then repeats from step 2.
Using any of the 5- to 8-bit character frame formats is impractical, as the receiver must change between
using n and n+1 character frame formats. This makes full-duplex operation difficult since the transmitter
and receiver must use the same character size setting.
24.3.2.11 IRCOM Mode of Operation
®
The IRCOM mode enables IrDA 1.4 compliant modulation and demodulation for baud rates up to 115.2
kbps. When IRCOM mode is enabled, Double-Speed mode cannot be used for the USART.
24.3.2.11.1 Overview
A USART can be configured in infrared communication mode (IRCOM) that is IrDA compatible with baud
rates up to 115.2 kbps. When enabled, the IRCOM mode enables infrared pulse encoding/decoding for
the USART.
A USART is set in IRCOM mode by writing 0x2 to the CMODE bits in USARTn.CTRLC. The data on the
TX/RX pins is the inverted value of the transmitted/received infrared pulse. It is also possible to select an
event channel from the Event System as an input for the IRCOM receiver. This will disable the RX input
from the USART pin.
For transmission, three pulse modulation schemes are available:
• 3/16 of the baud rate period
• Fixed programmable pulse time based on the peripheral clock frequency
• Pulse modulation disabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 352
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
For the reception, a fixed programmable minimum high-level pulse-width for the pulse to be decoded as a
logical ‘0’ is used. Shorter pulses will then be discarded, and the bit will be decoded to logical ‘1’ as if no
pulse was received.
24.3.2.11.2 Block Diagram
Figure 24-13. Block Diagram
IRCOM
Event System
Events
Encoded RXD
Pulse
Decoding
Decoded RXD
USART
TXD
Decoded RXD
Pulse
Encoding
RXD
Encoded RXD
24.3.2.11.3 IRCOM and Event System
The Event System can be used as the receiver input. This enables the IRCOM or USART input from the
I/O pins or sources other than the corresponding RX pin. If the Event System input is enabled, input from
the USART's RX pin is automatically disabled.
Related Links
14. EVSYS - Event System
24.3.3
Events
The USART can accept the following input events:
• IREI - IrDA Event Input
The event is enabled by writing a '1' to the IrDA Event Input bit (IREI) in the Event Control register
(USART.EVCTRL).
Related Links
14. EVSYS - Event System
24.5.12 EVCTRL
24.3.4
Interrupts
Table 24-10. Available Interrupt Vectors and Sources
Offset Name Vector Description
0x00
RXC
Receive Complete
Interrupt
0x02
DRE
Data Register Empty
Interrupt
© 2019 Microchip Technology Inc.
Conditions
• There are unread data in the receive buffer (RXCIE)
• Receive of Start-of-Frame detected (RXSIE)
• Auto-Baud Error/ISFIF flag set (ABEIE)
The transmit buffer is empty/ready to receive new data
(DREIE).
Preliminary Datasheet
40001997C-page 353
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
...........continued
Offset Name Vector Description
Conditions
0x04
The entire frame in the Transmit Shift register has been shifted
out and there are no new data in the transmit buffer (TXCIE).
TXC
Transmit Complete
Interrupt
When an interrupt condition occurs, the corresponding interrupt flag is set in the STATUS register
(USART.STATUS).
An interrupt source is enabled or disabled by writing to the corresponding bit in the Control A register
(USART.CTRLA).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the USART.STATUS
register for details on how to clear interrupt flags.
Related Links
13. CPUINT - CPU Interrupt Controller
24.5.5 STATUS
24.5.6 CTRLA
24.3.5
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 354
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.4
Register Summary - USART
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x07
RXDATAL
RXDATAH
TXDATAL
TXDATAH
STATUS
CTRLA
CTRLB
CTRLC
CTRLC
0x08
BAUD
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
15:8
0x0A
0x0B
0x0C
0x0D
0x0E
Reserved
DBGCTRL
EVCTRL
TXPLCTRL
RXPLCTRL
24.5
DATA[7:0]
RXCIF
BUFOVF
FERR
PERR
DATA[8]
DATA[7:0]
RXCIF
TXCIF
RXCIE
TXCIE
RXEN
TXEN
CMODE[1:0]
CMODE[1:0]
7:0
7:0
7:0
7:0
DREIF
DREIE
RXSIF
RXSIE
SFDEN
PMODE[1:0]
ISFIF
LBME
ODME
SBMODE
DATA[8]
BDF
WFB
ABEIE
RS485[1:0]
RXMODE[1:0]
MPCM
CHSIZE[2:0]
UDORD
UCPHA
BAUD[7:0]
BAUD[15:8]
DBGRUN
IREI
TXPL[7:0]
RXPL[6:0]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 355
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.1
Receiver Data Register Low Byte
Name:
Offset:
Reset:
Property:
RXDATAL
0x00
0x00
R
Reading the USARTn.RXDATAL Register will return the contents of the Receive Data Buffer register
(RXB).
The receive buffer consists of a two-level FIFO. The FIFO and the corresponding flags in the high byte of
RXDATA will change state whenever the receive buffer is accessed (read). If CHSIZE in USARTn.CTRLC
is set to 9BIT Low byte first, read USARTn.RXDATAL before USARTn.RXDATAH. Otherwise, always read
USARTn.RXDATAH before USARTn.RXDATAL in order to get the correct flags.
Bit
7
6
5
4
3
2
1
0
DATA[7:0]
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bits 7:0 – DATA[7:0] Receiver Data Register
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 356
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.2
Receiver Data Register High Byte
Name:
Offset:
Reset:
Property:
RXDATAH
0x01
0x00
-
Reading the USARTn.RXDATAH register location will return the contents of the ninth DATA bit plus Status
bits.
The receive buffer consists of a two-level FIFO. The FIFO and the corresponding flags in the high byte of
USARTn.RXDATAH will change state whenever the receive buffer is accessed (read). If CHSIZE in
USARTn.CTRLC is set to 9BIT Low byte first, read USARTn.RXDATAL before USARTn.RXDATAH.
Otherwise, always read USARTn.RXDATAH before USARTn.RXDATAL in order to get the correct flags.
Bit
7
6
5
4
3
2
1
0
RXCIF
BUFOVF
FERR
PERR
DATA[8]
Access
R
R
R
R
R
Reset
0
0
0
0
0
Bit 7 – RXCIF USART Receive Complete Interrupt Flag
This flag is set when there is unread data in the receive buffer and cleared when the receive buffer is
empty (i.e. does not contain any unread data). When the receiver is disabled, the receive buffer will be
flushed and consequently, the RXCIF will become '0'.
Bit 6 – BUFOVF Buffer Overflow
The BUFOVF flag indicates data loss due to a receiver buffer full condition. This flag is set if a Buffer
Overflow condition is detected. A Buffer Overflow occurs when the receive buffer is full (two characters), it
is a new character waiting in the Receive Shift register, and a new Start bit is detected. This flag is valid
until the receive buffer (USARTn.RXDATAL) is read.
This flag is not used in Master SPI mode of operation.
Bit 2 – FERR Frame Error
The FERR flag indicates the state of the first Stop bit of the next readable frame stored in the receive
buffer. The bit is set if the received character had a Frame Error (i.e. when the first Stop bit was '0' and
cleared when the Stop bit of the received data is '1'. This bit is valid until the receive buffer
(USARTn.RXDATAL) is read. The FERR is not affected by the SBMODE bit in USARTn.CTRLC since the
receiver ignores all, except for the first Stop bit.
This flag is not used in Master SPI mode of operation.
Bit 1 – PERR Parity Error
If parity checking is enabled and the next character in the receive buffer has a Parity Error this flag is set.
If Parity Check is not enabled the PERR will always be read as '0'. This bit is valid until the receive buffer
(USARTn.RXDATAL) is read. For details on parity calculation refer to 24.3.2.2.1 Parity. If USART is set to
LINAUTO mode, this bit will be a Parity Check of the protected identifier field and will be valid when
DATA[8] in USARTn.RXDATAH reads low.
This flag is not used in Master SPI mode of operation.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 357
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Bit 0 – DATA[8] Receiver Data Register
When USART receiver is set to LINAUTO mode, this bit indicates if the received data is within the
response space of a LIN frame. If the received data is the protected identifier field, this bit will be read as
'0'. Otherwise, the bit will be read as '1'. For Receiver mode other than LINAUTO mode, DATA[8] holds
the ninth data bit in the received character when operating with serial frames with nine data bits.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 358
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.3
Transmit Data Register Low Byte
Name:
Offset:
Reset:
Property:
TXDATAL
0x02
0x00
R/W
The Transmit Data Buffer (TXB) register will be the destination for data written to the USARTn.TXDATAL
register location.
For 5-, 6-, or 7-bit characters the upper unused bits will be ignored by the transmitter and set to '0' by the
receiver.
The transmit buffer can only be written when the DREIF flag in the USARTn.STATUS register is set. Data
written to DATA when the DREIF flag is not set will be ignored by the USART transmitter. When data is
written to the transmit buffer, and the transmitter is enabled, the transmitter will load the data into the
Transmit Shift register when the Shift register is empty. The data is then transmitted on the TxD pin.
Bit
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DATA[7:0]
Access
Reset
Bits 7:0 – DATA[7:0] Transmit Data Register
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 359
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.4
Transmit Data Register High Byte
Name:
Offset:
Reset:
Property:
TXDATAH
0x03
0x00
-
USARTn.TXDATAH holds the ninth data bit in the character to be transmitted when operating with serial
frames with nine data bits. When used this bit must be written before writing to USARTn.TXDATAL except
if CHSIZE in USARTn.CTRLC is set to 9BIT Low byte first where USARTn.TXDATAL should be written
first.
This bit is unused in Master SPI mode of operation.
Bit
7
6
5
4
3
2
1
0
DATA[8]
Access
W
Reset
0
Bit 0 – DATA[8] Transmit Data Register
This bit is used when CHSIZE=9BIT in USARTn.CTRLC.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 360
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.5
USART Status Register
Name:
Offset:
Reset:
Property:
Bit
STATUS
0x04
0x00
-
7
6
5
4
3
2
1
0
RXCIF
TXCIF
DREIF
RXSIF
ISFIF
BDF
WFB
Access
R
R/W
R
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
Bit 7 – RXCIF USART Receive Complete Interrupt Flag
This flag is set to ‘1’ when there is unread data in the receive buffer and cleared when the receive buffer
is empty (i.e. does not contain any unread data). When the receiver is disabled, the receive buffer will be
flushed and consequently, the RXCIF will become '0'.
When interrupt-driven data reception is used, the receive complete interrupt routine must read the
received data from RXDATA in order to clear the RXCIF. If not, a new interrupt will occur directly after the
return from the current interrupt.
Bit 6 – TXCIF USART Transmit Complete Interrupt Flag
This flag is set when the entire frame in the Transmit Shift register has been shifted out and there are no
new data in the transmit buffer (TXDATA).
This flag is automatically cleared when the transmit complete interrupt vector is executed. The flag can
also be cleared by writing a ‘1’ to its bit location.
Bit 5 – DREIF USART Data Register Empty Flag
The DREIF indicates if the transmit buffer (TXDATA) is ready to receive new data. The flag is set to ‘1’
when the transmit buffer is empty and is ‘0’ when the transmit buffer contains data to be transmitted that
has not yet been moved into the Shift register. DREIF is set after a Reset to indicate that the transmitter is
ready. Always write this bit to ‘0’ when writing the STATUS register.
DREIF is cleared to ‘0’ by writing TXDATAL. When interrupt-driven data transmission is used, the Data
Register Empty interrupt routine must either write new data to TXDATA in order to clear DREIF or disable
the Data Register Empty interrupt. If not, a new interrupt will occur directly after the return from the
current interrupt.
Bit 4 – RXSIF USART Receive Start Interrupt Flag
The RXSIF flag indicates a valid Start condition on RxD line. The flag is set when the system is in
standby modes and a high (IDLE) to low (START) valid transition is detected on the RxD line. If the start
detection is not enabled, the RXSIF will always be read as '0'. This flag can only be cleared by writing a
‘1’ to its bit location. This flag is not used in the Master SPI mode operation.
Bit 3 – ISFIF Inconsistent Sync Field Interrupt Flag
This bit is set when the auto-baud is enabled and the sync field bit time is too fast or too slow to give a
valid baud setting. It will also be set when USART is set to LINAUTO mode and the SYNC character differ
from data value 0x55.
Writing a ‘1’ to this bit will clear the flag and bring the USART back to Idle state.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 361
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Bit 1 – BDF Break Detected Flag
This bit is intended for USART configured to LINAUTO receive mode. The break detector has a fixed
threshold of 11 bits low for a Break to be detected. The BDF bit is set after a valid BREAK and SYNC
character is detected. The bit is automatically cleared when next data is received. The bit will behave
identically when USART is set to GENAUTO mode. In NORMAL or CLK2X receive mode, the BDF bit is
unused.
This bit is cleared by writing a ‘1’ to it.
Bit 0 – WFB Wait For Break
Writing this bit to ‘1’ will register the next low and high transition on RxD line as a Break character. This
can be used to wait for a Break character of arbitrary width. Combined with USART set to GENAUTO
mode, this allows the user to set any BAUD rate through BREAK and SYNC as long as it falls within the
valid range of the USARTn.BAUD register. This bit will always read ‘0’.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 362
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.6
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
CTRLA
0x05
0x00
-
7
6
5
4
3
2
1
0
RXCIE
TXCIE
DREIE
RXSIE
LBME
ABEIE
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
RS485[1:0]
Bit 7 – RXCIE Receive Complete Interrupt Enable
The bit enables the Receive Complete Interrupt (interrupt vector RXC). The enabled interrupt will be
triggered when RXCIF in the USARTn.STATUS register is set.
Bit 6 – TXCIE Transmit Complete Interrupt Enable
This bit enables the Transmit Complete Interrupt (interrupt vector TXC). The enabled interrupt will be
triggered when the TXCIF in the USARTn.STATUS register is set.
Bit 5 – DREIE Data Register Empty Interrupt Enable
This bit enables the Data Register Empty Interrupt (interrupt vector DRE). The enabled interrupt will be
triggered when the DREIF in the USART.STATUS register is set.
Bit 4 – RXSIE Receiver Start Frame Interrupt Enable
Writing a '1' to this bit enables the Start Frame Detector to generate an interrupt on interrupt vector RXC
when a start-of-frame condition is detected.
Bit 3 – LBME Loop-back Mode Enable
Writing this bit to '1' enables an internal connection between the TxD and RxD pin.
Bit 2 – ABEIE Auto-baud Error Interrupt Enable
Writing this bit to '1' enables the auto-baud error interrupt on interrupt vector RXC. The enabled interrupt
will trigger for conditions where the ISFIF flag is set.
Bits 1:0 – RS485[1:0] RS-485 Mode
These bits enable the RS-485 and select the operation mode.
Value
Name Description
0x0
OFF Disabled.
0x1
EXT Enables RS-485 mode with control of an external line driver through a dedicated
Transmit Enable (TE) pin.
0x2
INT
Enables RS-485 mode with control of the internal USART transmitter.
0x3
Reserved.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 363
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.7
Control B
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
CTRLB
0x06
0x00
-
7
6
RXEN
R/W
0
5
4
3
2
1
TXEN
SFDEN
ODME
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
RXMODE[1:0]
0
MPCM
Bit 7 – RXEN Receiver Enable
Writing this bit to ‘1’ enables the USART receiver. The receiver will override normal port operation for the
RxD pin when enabled. Disabling the receiver will flush the receive buffer invalidating the FERR,
BUFOVF, and PERR flags. In GENAUTO and LINAUTO mode, disabling the receiver will reset the autobaud detection logic.
Bit 6 – TXEN Transmitter Enable
Writing this bit to ‘1’ enables the USART transmitter. The transmitter will override normal port operation
for the TxD pin when enabled. Disabling the transmitter (writing TXEN to '0') will not become effective
until ongoing and pending transmissions are completed (i.e. when the Transmit Shift register and
Transmit Buffer register does not contain data to be transmitted). When the transmitter is disabled, it will
no longer override the TxDn pin, and the pin direction is set as input automatically by hardware, even if it
was configured as output by the user.
Bit 4 – SFDEN Start Frame Detection Enable
Writing this bit to ‘1’ enables the USART Start Frame Detection mode. The Start Frame detector is able to
wake up the system from Idle or Standby Sleep modes when a high (IDLE) to low (START) transition is
detected on the RxD line.
Bit 3 – ODME Open Drain Mode Enable
Writing this bit to ‘1’ makes the TxD pin to have open-drain functionality. A pull-up resistor is needed to
prevent the line from floating when a logic '1' is output to the TxD pin.
Bits 2:1 – RXMODE[1:0] Receiver Mode
In CLK2X mode, the divisor of the baud rate divider will be reduced from 16 to 8 effectively doubling the
transfer rate for asynchronous communication modes. For synchronous operation, the CLK2X mode has
no effect and RXMODE should always be written to '0'. RXMODE must be '0' when the USART
Communication mode is configured to IRCOM. Setting RXMODE to GENAUTO enables generic autobaud where the SYNC character is valid when eight low and high bits have been registered. In this mode,
any SYNC character that gives a valid BAUD rate will be accepted. In LINAUTO mode the SYNC
character is constrained and found valid if every two bits falls within 32 ±6 baud samples of the internal
baud rate and match data value 0x55. The GENAUTO and LINAUTO mode is only supported for USART
operated in Asynchronous Slave mode.
Value
Name
Description
0x0
NORMAL
Normal USART mode, Standard Transmission Speed
0x1
CLK2X
Normal USART mode, Double Transmission Speed
0x2
GENAUTO
Generic Auto-baud mode
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 364
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Value
0x3
Name
LINAUTO
Description
LIN Constrained Auto-baud mode
Bit 0 – MPCM Multi-Processor Communication Mode
Writing a ‘1’ to this bit enables the Multi-Processor Communication mode: the USART receiver ignores all
the incoming frames that do not contain address information. The transmitter is unaffected by the MPCM
setting. For more detailed information see 24.3.2.10 Multiprocessor Communication Mode.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 365
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.8
Control C - Async Mode
Name:
Offset:
Reset:
Property:
CTRLC
0x07
0x03
-
This register description is valid for all modes except Master SPI mode. When the USART
Communication mode bits (CMODE) in this register are written to 'MSPI', see Control C - Master SPI
Mode for the correct description.
Bit
7
6
5
CMODE[1:0]
Access
Reset
4
PMODE[1:0]
3
2
SBMODE
1
0
CHSIZE[2:0]
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
1
1
Bits 7:6 – CMODE[1:0] USART Communication Mode
Writing these bits select the Communication mode of the USART.
Writing a 0x3 to these bits alters the available bit fields in this register, see Control C - Master SPI Mode.
Value
Name
Description
0x0
ASYNCHRONOUS
Asynchronous USART
0x1
SYNCHRONOUS
Synchronous USART
0x2
IRCOM
Infrared Communication
0x3
MSPI
Master SPI
Bits 5:4 – PMODE[1:0] Parity Mode
Writing these bits enable and select the type of parity generation.
When enabled, the transmitter will automatically generate and send the parity of the transmitted data bits
within each frame. The receiver will generate a parity value for the incoming data, compare it to the
PMODE setting, and set the Parity Error flag (PERR) in the STATUS register (USARTn.STATUS) if a
mismatch is detected.
Value
Name
Description
0x0
DISABLED
Disabled
0x1
Reserved
0x2
EVEN
Enabled, Even Parity
0x3
ODD
Enabled, Odd Parity
Bit 3 – SBMODE Stop Bit Mode
Writing this bit selects the number of Stop bits to be inserted by the transmitter.
The receiver ignores this setting.
Value
Description
0
1 Stop bit
1
2 Stop bits
Bits 2:0 – CHSIZE[2:0] Character Size
Writing these bits select the number of data bits in a frame. The receiver and transmitter use the same
setting. For 9BIT character size, the order of which byte to read or write first, low or high byte of RXDATA
or TXDATA is selectable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 366
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
Value
0x0
0x1
0x2
0x3
0x4
0x5
0x6
0x7
Name
5BIT
6BIT
7BIT
8BIT
9BITL
9BITH
© 2019 Microchip Technology Inc.
Description
5-bit
6-bit
7-bit
8-bit
Reserved
Reserved
9-bit (Low byte first)
9-bit (High byte first)
Preliminary Datasheet
40001997C-page 367
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.9
Control C - Master SPI Mode
Name:
Offset:
Reset:
Property:
CTRLC
0x07
0x00
-
This register description is valid only when the USART is in Master SPI mode (CMODE written to MSPI).
For other CMODE values, see Control C - Async Mode.
See 24.3.2.5 USART in Master SPI mode for a full description of the Master SPI mode operation.
Bit
7
6
5
4
3
CMODE[1:0]
Access
Reset
2
1
UDORD
UCPHA
R/W
R/W
R/W
R/W
0
0
0
0
0
Bits 7:6 – CMODE[1:0] USART Communication Mode
Writing these bits select the communication mode of the USART.
Writing a value different than 0x3 to these bits alters the available bit fields in this register, see Control C Async Mode.
Value
Name
Description
0x0
ASYNCHRONOUS
Asynchronous USART
0x1
SYNCHRONOUS
Synchronous USART
0x2
IRCOM
Infrared Communication
0x3
MSPI
Master SPI
Bit 2 – UDORD Data Order
Writing this bit selects the frame format.
The receiver and transmitter use the same setting. Changing the setting of UDORD will corrupt all
ongoing communication for both the receiver and the transmitter.
Value
Description
0
MSB of the data word is transmitted first
1
LSB of the data word is transmitted first
Bit 1 – UCPHA Clock Phase
The UCPHA bit setting determines if data is sampled on the leading (first) edge or tailing (last) edge of
XCKn. Refer to the 24.3.2.1.5 Master SPI Mode Clock Generation for details.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 368
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.10 Baud Register
Name:
Offset:
Reset:
Property:
BAUD
0x08
0x00
-
The USARTn.BAUDL and USARTn.BAUDH register pair represents the 16-bit value, USARTn.BAUD.
The low byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be
accessed at offset + 0x01.
Ongoing transmissions of the transmitter and receiver will be corrupted if the baud rate is changed.
Writing this register will trigger an immediate update of the baud rate prescaler. For more information on
how to set the baud rate, see Table 24-2.
Bit
15
14
13
12
11
10
9
8
R/W
R/W
R/W
R/W
Reset
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
BAUD[15:8]
Access
BAUD[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – BAUD[15:8] USART Baud Rate High Byte
These bits hold the MSB of the 16-bit Baud register.
Bits 7:0 – BAUD[7:0] USART Baud Rate Low Byte
These bits hold the LSB of the 16-bit Baud register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 369
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.11 Debug Control Register
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x0B
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Debug Run
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 370
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.12 IrDA Control Register
Name:
Offset:
Reset:
Property:
Bit
7
EVCTRL
0x0C
0x00
-
6
5
4
3
2
1
0
IREI
Access
R/W
Reset
0
Bit 0 – IREI IrDA Event Input Enable
This bit enables the event source for the IRCOM Receiver. If event input is selected for the IRCOM
Receiver, the input from the USART’s RX pin is automatically disabled.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 371
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.13 IRCOM Transmitter Pulse Length Control Register
Name:
Offset:
Reset:
Property:
Bit
TXPLCTRL
0x0D
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
TXPL[7:0]
Access
Reset
Bits 7:0 – TXPL[7:0] Transmitter Pulse Length
The 8-bit value sets the pulse modulation scheme for the transmitter. Setting this register will have effect
only if IRCOM mode is selected by a USART. By leaving this register value to '0', 3/16 of the baud rate
period pulse modulation is used. Setting this value from 1 to 254 will give a fixed pulse length coding. The
8-bit value sets the number of system clock periods for the pulse. The start of the pulse will be
synchronized with the rising edge of the baud rate clock. Setting the value to 255 (0xFF) will disable pulse
coding, letting the RX and TX signals pass through the IRCOM module unaltered. This enables other
features through the IRCOM module, such as half-duplex USART, Loop-back testing, and USART RX
input from an event channel.
TXPL must be configured before the USART transmitter is enabled (TXEN).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 372
ATtiny1616/3216
USART - Universal Synchronous and Asynchrono...
24.5.14 IRCOM Receiver Pulse Length Control Register
Name:
Offset:
Reset:
Property:
Bit
7
RXPLCTRL
0x0E
0x00
-
6
5
4
R/W
R/W
R/W
0
0
0
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
0
RXPL[6:0]
Access
Reset
Bits 6:0 – RXPL[6:0] Receiver Pulse Length
The 8-bit value sets the filter coefficient for the IRCOM transceiver. Setting this register will only have
effect if IRCOM mode is selected by a USART.
By leaving this register value to '0', filtering is disabled. Setting this value between 0x01 and 0xFF will
enable filtering, where x+1 equal samples are required for the pulse to be accepted.
RXPL must be configured before USART receiver is enabled (RXEN).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 373
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.
SPI - Serial Peripheral Interface
25.1
Features
•
•
•
•
•
•
•
•
25.2
Full-Duplex, Three-Wire Synchronous Data Transfer
Master or Slave Operation
LSB First or MSB First Data Transfer
Seven Programmable Bit Rates
End of Transmission Interrupt Flag
Write Collision Flag Protection
Wake-up from Idle Mode
Double-Speed (CK/2) Master SPI Mode
Overview
The Serial Peripheral Interface (SPI) is a high-speed synchronous data transfer interface using three or
four pins. It allows full-duplex communication between an AVR device and peripheral devices or between
several microcontrollers. The SPI peripheral can be configured as either master or slave. The master
initiates and controls all data transactions.
The interconnection between master and slave devices with SPI is shown in the block diagram. The
system consists of two shift registers and a master clock generator. The SPI master initiates the
communication cycle by pulling the desired slave's slave select (SS) signal low. Master and slave prepare
the data to be sent to their respective Shift registers, and the master generates the required clock pulses
on the SCK line to exchange data. Data is always shifted from master to slave on the master output,
slave input (MOSI) line, and from slave to master on the master input, slave output (MISO) line.
This device provides one instance of the SPI peripheral, SPI0.
Related Links
25.2.1 Block Diagram
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 374
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.2.1
Block Diagram
Figure 25-1. SPI Block Diagram
MASTER
SLAVE
Transmit Data Register
(DATA)
Transmit Data Register
(DATA)
Transmit Buffer
Register
Transmit Buffer
Register
LSb
MSb
MISO
MISO
MOSI
MOSI
8-bit Shift Register
MSb
LSb
8-bit Shift Register
SPI CLOCK
GENERATOR
SCK
SCK
SS
SS
First Receive Buffer
Register
First Receive Buffer
Register
Receive Buffer
Register
Second Receive Buffer
Register
Receive Data Register
(DATA)
Receive Data Register
(DATA)
The SPI is built around an 8-bit Shift register that will shift data out and in at the same time. The Transmit
Data register and the Receive Data register are not physical registers but are mapped to other registers
when written or read: Writing the Transmit Data register (SPIn.DATA) will write the Shift register in Normal
mode and the Transmit Buffer register in Buffer mode. Reading the Receive Data register (SPIn.DATA)
will read the First Receive Buffer register in normal mode and the Second Receive Data register in Buffer
mode.
In Master mode, the SPI has a clock generator to generate the SCK clock. In Slave mode, the received
SCK clock is synchronized and sampled to trigger the shifting of data in the Shift register.
25.2.2
Signal Description
Table 25-1. Signals in Master and Slave Mode
Signal
MOSI
© 2019 Microchip Technology Inc.
Description
Pin Configuration
Master Out Slave In
Master Mode
Slave Mode
User defined
Input
Preliminary Datasheet
40001997C-page 375
ATtiny1616/3216
SPI - Serial Peripheral Interface
...........continued
Signal
Description
Pin Configuration
Master Mode
Slave Mode
MISO
Master In Slave Out
Input
User defined
SCK
Slave clock
User defined
Input
SS
Slave select
User defined
Input
When the SPI module is enabled, the data direction of the MOSI, MISO, SCK, and SS pins is overridden
according to Table 25-1.
The data direction of the pins with "User defined" pin configuration is not controlled by the SPI: The data
direction is controlled by the application software configuring the port peripheral. If these pins are
configured with data direction as input, they can be used as regular I/O pin inputs. If these pins are
configured with data direction as output, their output value is controlled by the SPI. The MISO pin has a
special behavior: When the SPI is in Slave mode and the MISO pin is configured as an output, the SS pin
controls the output buffer of the pin: If SS is low, the output buffer drives the pin, if SS is high, the pin is
tri-stated.
The data direction of the pins with "Input" pin configuration is controlled by the SPI hardware.
Related Links
5. I/O Multiplexing and Considerations
25.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 25-2. SPI System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
25.2.3.2 I/O Lines and Connections
25.2.3.5 Debug Operation
25.2.3.3 Interrupts
25.2.3.1 Clocks
25.2.3.1 Clocks
This peripheral depends on the peripheral clock.
Related Links
10. CLKCTRL - Clock Controller
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 376
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.2.3.2 I/O Lines and Connections
The SPI signals (MOSI, MISO, SCK, SS) are either inputs or outputs, depending on whether the SPI is in
Master or Slave mode, as described in the Signal Description.
Using the I/O lines requires configuration of the I/O pins as described in the Signal Description.
Related Links
5. I/O Multiplexing and Considerations
16. PORT - I/O Pin Configuration
25.2.2 Signal Description
25.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
25.3.3 Interrupts
25.2.3.4 Events
Not applicable.
25.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
Related Links
33. UPDI - Unified Program and Debug Interface
25.3
Functional Description
25.3.1
Initialization
Initialize the SPI to a basic functional state by following these steps:
1. Configure the SS pin in the port peripheral.
2. Select SPI Master/Slave operation by writing the Master/Slave Select bit (MASTER) in the Control
A register (SPIn.CTRLA).
3. In Master mode, select the clock speed by writing the Prescaler bits (PRESC) and the Clock
Double bit (CLK2X) in SPIn.CTRLA.
4. Optional: Select the Data Transfer mode by writing to the MODE bits in the Control B register
(SPIn.CTRLB).
5. Optional: Write the Data Order bit (DORD) in SPIn.CTRLA.
6. Optional: Setup Buffer mode by writing BUFEN and BUFWR bits in the Control B register
(SPIn.CTRLB).
7. Optional: To disable the multi-master support in Master mode, write ‘1’ to the Slave Select Disable
bit (SSD) in SPIn.CTRLB.
8. Enable the SPI by writing a ‘1’ to the ENABLE bit in SPIn.CTRLA.
Related Links
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 377
ATtiny1616/3216
SPI - Serial Peripheral Interface
5. I/O Multiplexing and Considerations
16. PORT - I/O Pin Configuration
25.2.2 Signal Description
25.3.2
Operation
25.3.2.1 Master Mode Operation
When the SPI is configured in Master mode, a write to the SPIn.DATA register will start a new transfer.
The SPI clock generator starts and the hardware shifts the eight bits into the selected slave. After the
byte is shifted out the interrupt flag is set (IF flag in SPIn.INTFLAGS). The SPI master can operate in two
modes, Normal and Buffered, as explained below.
25.3.2.1.1 SS Pin Functionality in Master Mode - Multi-Master Support
In Master mode, the Slave Select Disable bit in Control Register B (SSD bit in SPIn.CTRLB) controls how
the SPI uses the SS pin.
• If SSD in SPIn.CTRLB is ‘0’, the SPI can use the SS pin to transition from Master to Slave mode.
This allows multiple SPI masters on the same SPI bus.
• If SSD in SPIn.CTRLB is ‘0’, and the SS pin is configured as an output pin, it can be used as a
regular I/O pin or by other peripheral modules, and will not affect the SPI system.
• If SSD in SPIn.CTRLB is ‘1’, the SPI does not use the SS pin, and it can be used as a regular I/O
pin, or by other peripheral modules.
If the SSD bit in SPIn.CTRLB is ‘0’, and the SS is configured as an input pin, the SS pin must be held
high to ensure master SPI operation. A low level will be interpreted as another master is trying to take
control of the bus. This will switch the SPI into Slave mode, and the hardware of the SPI will perform the
following actions:
1. The Master bit in the SPI Control A Register (MASTER in SPIn.CTRLA) is cleared, and the SPI
system becomes a slave. The direction of the SPI pins will be switched when conditions in Table
25-3 are met.
2. The Interrupt Flag in the Interrupt Flags register (IF in SPIn.INTFLAGS) will be set. If the interrupt is
enabled and the global interrupts are enabled, the interrupt routine will be executed.
Table 25-3. Overview of the SS Pin Functionality when the SSD Bit in SPIn.CTRLB is ‘0’
SS Configuration
Input
Output
SS Pin-Level
Description
High
Master activated (selected)
Low
Master deactivated, switched to
Slave mode
High
Master activated (selected)
Low
Note: If the device is in Master mode and it cannot be ensured that the SS pin will stay high between
two transmissions, the status of the Master bit (the MASTER bit in SPIn.CTRLA) has to be checked
before a new byte is written. After the Master bit has been cleared by a low level on the SS line, it must
be set by the application to re-enable the SPI Master mode.
25.3.2.1.2 Normal Mode
In Normal mode, the system is single-buffered in the transmit direction and double-buffered in the receive
direction. This influences the data handling in the following ways:
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 378
ATtiny1616/3216
SPI - Serial Peripheral Interface
1.
2.
3.
4.
New bytes to be sent cannot be written to the Data register (SPIn.DATA) before the entire transfer
has completed. A premature write will cause corruption of the transmitted data, and the hardware
will set the Write Collision Flag (WRCOL flag in SPIn.INTFLAGS).
Received bytes are written to the First Receive Buffer register immediately after the transmission is
completed.
The First Receive Buffer register has to be read before the next transmission is completed or data
will be lost. This register is read by reading SPIn.DATA.
The Transmit Buffer register and Second Receive Buffer register are not used in Normal mode.
After a transfer has completed, the Interrupt Flag will be set in the Interrupt Flags register (IF flag in
SPI.INTFLAGS). This will cause the corresponding interrupt to be executed if this interrupt and the global
interrupts are enabled. Setting the Interrupt Enable (IE) bit in the Interrupt Control register
(SPIn.INTCTRL) will enable the interrupt.
25.3.2.1.3 Buffer Mode
The Buffer mode is enabled by setting the BUFEN bit in SPIn.CTRLB. The BUFWR bit in SPIn.CTRLB
has no effect in Master mode. In Buffer mode, the system is double-buffered in the transmit direction and
triple-buffered in the receive direction. This influences the data handling the following ways:
1. New bytes to be sent can be written to the Data register (SPIn.DATA) as long as the Data Register
Empty Interrupt Flag (DREIF) in the Interrupt Flag Register (SPIn.INTFLAGS) is set. The first write
will be transmitted right away and the following write will go to the Transmit Buffer register.
2. A received byte is placed in a two-entry RX FIFO comprised of the First and Second Receive Buffer
registers immediately after the transmission is completed.
3. The Data register is used to read from the RX FIFO. The RX FIFO must be read at least every
second transfer to avoid any loss of data.
If both the Shift register and the Transmit Buffer register becomes empty, the Transfer Complete Interrupt
Flag (TXCIF) in the Interrupt Flags register (SPIn.INTFLAGS) will be set. This will cause the
corresponding interrupt to be executed if this interrupt and the global interrupts are enabled. Setting the
Transfer Complete Interrupt Enable (TXCIE) in the Interrupt Control register (SPIn.INTCTRL) enables the
Transfer Complete Interrupt.
25.3.2.2 Slave Mode
In Slave mode, the SPI peripheral receives SPI clock and Slave Select from a Master. Slave mode
supports three operational modes: One unbuffered mode and two buffered modes. In Slave mode, the
control logic will sample the incoming signal on the SCK pin. To ensure correct sampling of this clock
signal, the minimum low and high periods must each be longer than two peripheral clock cycles.
25.3.2.2.1 SS Pin Functionality in Slave Mode
The Slave Select (SS) pin plays a central role in the operation of the SPI. Depending on the mode the
SPI is in and the configuration of this pin, it can be used to activate or deactivate devices. The SS pin is
used as a Chip Select pin.
In Slave mode, SS, MOSI, and SCK are always inputs. The behavior of the MISO pin depends on the
configured data direction of the pin in the port peripheral and the value of SS:
• When SS is driven low, the SPI is activated and will respond to received SCK pulses by clocking data
out on MISO if the user has configured the data direction of the MISO pin as an output.
• When SS is driven high the SPI is deactivated, meaning that it will not receive incoming data. If the
MISO pin data direction is configured as an output, the MISO pin will be tri-stated.
The following table shows an overview of the SS pin functionality.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 379
ATtiny1616/3216
SPI - Serial Peripheral Interface
Table 25-4. Overview of the SS Pin Functionality
SS Configuration
SS Pin-Level
Always Input
Description
MISO Pin Mode
Port Direction =
Output
Port Direction =
Input
High
Slave deactivated
(deselected)
Tri-stated
Input
Low
Slave activated
(selected)
Output
Input
Note:
In Slave mode, the SPI state machine will be reset when the SS pin is brought high. If the SS is brought
high during a transmission, the SPI will immediately stop sending and receiving - both data received and
data sent must be considered as lost. As the SS pin is used to signal the start and end of a transfer, it is
useful for achieving packet/byte synchronization, and keeping the Slave bit counter synchronized with the
master clock generator.
25.3.2.2.2 Normal Mode
In Normal mode, the SPI peripheral will remain idle as long as the SS pin is driven high. In this state, the
software may update the contents of the SPIn.DATA register, but the data will not be shifted out by
incoming clock pulses on the SCK pin until the SS pin is driven low. If SS is driven low, the slave will start
to shift out data on the first SCK clock pulse. When one byte has been completely shifted, the SPI
Interrupt flag (IF) in SPIn.INTFLAGS is set.
The user application may continue placing new data to be sent into the SPIn.DATA register before
reading the incoming data. New bytes to be sent cannot be written to SPIn.DATA before the entire
transfer has completed. A premature write will be ignored, and the hardware will set the Write Collision
Flag (WRCOL in SPIn.INTFLAGS).
When SS is driven high, the SPI logic is halted, and the SPI slave will not receive any new data. Any
partially received packet in the shift register will be lost.
Figure 25-2. SPI Timing Diagram in Normal Mode (Buffer Mode Not Enabled)
SS
SCK
Write DATA
Write value
0x43
0x44
0x45
0x46
WRCOL
IF
Shift Register
Data sent
0x43
0x44
0x43
0x44
0x46
0x46
The figure above shows three transfers and one write to the DATA register while the SPI is busy with a
transfer. This write will be ignored and the Write Collision Flag (WRCOL in SPIn.INTFLAGS) is set.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 380
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.3.2.2.3 Multi Slave Systems - SS Pin Functionality
The Slave Select (SS) pin plays a central role in the SPI configuration. Depending on the mode the part is
running in and the configuration of this pin, it can be used to activate or deactivate the devices. The SS
pin can be compared with a chip select pin that has some extra features.
In Master mode, the SS pin must be held high to ensure master SPI operation if this pin is configured as
an input pin. A low level will switch the SPI into Slave mode and the hardware of the SPI will perform the
following actions:
1. The master bit (MSTR) in the SPI Control Register (SPCR) is cleared and the SPI system becomes
a slave. The direction of the pins will be switched according to Table 25-5.
2. The SPI Interrupt Flag (SPIF) in the SPI Status Register (SPSR) will be set. If the SPI interrupt and
the global interrupts are enabled the interrupt routine will be executed.
This can be useful in systems with more than one master to avoid two masters accessing the SPI bus at
the same time. If the SS pin is configured as output pin it can be used as a general purpose output pin,
which does not affect the SPI system.
Note: In cases where the AVR is configured for Master mode and it can not be ensured that the SS pin
will stay high between two transmissions, the status of the MSTR bit has to be checked before a new byte
is written. After the MSTR bit has been cleared by a low level on the SS line, it must be set by the
application to re-enable SPI Master mode.
In Slave mode the SS pin is always an input. When SS is held low, the SPI is activated and MISO
becomes output if configured so by the user. All other pins are inputs. When SS is driven high, all pins are
inputs, and the SPI is passive, which means that it will not receive incoming data. The following table
shows an overview of the SS Pin Functionality.
Table 25-5. Overview of the SS Pin Functionality
Mode
SS Configuration
SS Pin-level
Description
Slave
Always Input
High
Slave deactivated (deselected)
Low
Slave activated (selected)
High
Master activated (selected)
Low
Master deactivated, switched to
Slave mode
High
Master activated (selected)
Master
Input
Output
Low
Note: In Slave mode, the SPI logic will be Reset once the SS pin is brought high. If the SS pin is brought
high during a transmission, the SPI will stop sending and receiving immediately and both data received
and data sent must be considered as lost.
As shown in the preceding table , the SS pin in Slave mode is always an input pin. A low level activates
the SPI of the device while a high level causes its deactivation. A Single Master Multiple Slave System
with an AVR configured in Master mode and SS configured as output pin is shown in the following figure.
The amount of slaves that can be connected to this AVR is only limited by the number of I/O pins to
generate the slave select signals.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 381
ATtiny1616/3216
SPI - Serial Peripheral Interface
Figure 25-3. Multi Slave System
The ability to connect several devices to the same SPI bus is based on the fact that only one master and
only one slave is active at the same time. The MISO, MOSI, and SCK lines of all the other slaves are tristated (configured as input pins of a high impedance with no pullup resistors enabled). A false
implementation (for example, if two slaves are activated at the same time) can cause a driver contention
which can lead to a CMOS latch-up state and must be avoided. Resistances of 1 to 10Ω in series with the
pins of the SPI can be used to prevent the system from latching up. However this affects the maximum
usable data rate, depending on the loading capacitance on the SPI pins.
Unidirectional SPI devices require just the clock line and one of the data lines. The device can use MISO
line or the MOSI line depending on its purpose.
25.3.2.2.4 Buffer Mode
To avoid data collisions, the SPI peripheral can be configured in buffered mode by writing a ‘1’ to the
Buffer Mode Enable bit in the Control B register (BUFEN in SPIn.CTRLB). In this mode, the SPI has
additional interrupt flags and extra buffers. The extra buffers are shown in Figure 25-1. There are two
different modes for the Buffer mode, selected with the Buffer mode Wait for Receive bit (BUFWR). The
two different modes are described below with timing diagrams.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 382
ATtiny1616/3216
SPI - Serial Peripheral Interface
Figure 25-4. SPI Timing Diagram in Buffer Mode with BUFWR in SPIn.CTRLB Written to ‘0’
SS
SCK
Write DATA
Write value
0x43
0x44
0x45
0x46
DREIF
TXCIF
RXCIF
Transmit Buffer
Shift Register
Data sent
0x43
Dummy
Dummy
0x46
0x44
0x44
0x43
0x43
0x44
0x46
0x46
All writes to the Data register goes to the Transmit Buffer register. The figure above shows that the value
0x43 is written to the Data register, but it is not immediately transferred to the shift register so the first
byte sent will be a dummy byte. The value of the dummy byte is whatever was in the shift register at the
time, usually the last received byte. After the first dummy transfer is completed the value 0x43 is
transferred to the Shift register. Then 0x44 is written to the Data register and goes to the Transmit Buffer
register. A new transfer is started and 0x43 will be sent. The value 0x45 is written to the Data register, but
the Transmit Buffer register is not updated since it is already full containing 0x44 and the Data Register
Empty Interrupt Flag (DREIF in SPIn.INTFLAGS) is low. The value 0x45 will be lost. After the transfer, the
value 0x44 is moved to the Shift register. During the next transfer, 0x46 is written to the Data register and
0x44 is sent out. After the transfer is complete, 0x46 is copied into the Shift register and sent out in the
next transfer.
The Data Register Empty Interrupt Flag (DREIF in SPIn.INTFLAGS) goes low every time the Transmit
Buffer register is written and goes high after a transfer when the previous value in the Transmit Buffer
register is copied into the Shift register. The Receive Complete Interrupt Flag (RXCIF in SPIn.INTFLAGS)
is set one cycle after the Data Register Empty Interrupt Flag goes high. The Transfer Complete Interrupt
Flag is set one cycle after the Receive Complete Interrupt Flag is set when both the value in the shift
register and the Transmit Buffer register have been sent.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 383
ATtiny1616/3216
SPI - Serial Peripheral Interface
Figure 25-5. SPI Timing Diagram in Buffer Mode with CTRLB.BUFWR Written to ‘1’
SS
SCK
Write DATA
Write value
0x43
0x44
0x45
0x46
DREIF
TXCIF
RXCIF
Transmit Buffer
Shift Register
Data sent
0x46
0x44
0x43
0x43
0x46
0x44
0x43
0x44
0x46
All writes to the Data register goes to the transmit buffer. The figure above shows that the value 0x43 is
written to the Data register and since the Slave Select pin is high it is copied to the Shift register the next
cycle. Then the next write (0x44) will go to the Transmit Buffer register. During the first transfer, the value
0x43 will be shifted out. In the figure, the value 0x45 is written to the Data register, but the Transmit Buffer
register is not updated since the Data Register Empty Interrupt Flag is low. After the transfer is
completed, the value 0x44 from the Transmit Buffer register is copied over to the Shift register. The value
0x46 is written to the Transmit Buffer register. During the next two transfers, 0x44 and 0x46 are shifted
out. The flags behave the same as with Buffer mode Wait for Receive Bit (BUFWR in SPIn.CTRLB)
written to ‘0’.
25.3.2.3 Data Modes
There are four combinations of the SCK phase and polarity with respect to serial data. The desired
combination is selected by writing to the MODE bits in the Control B register (SPIn.CTRLB).
The SPI data transfer formats are shown below. Data bits are shifted out and latched in on opposite
edges of the SCK signal, ensuring sufficient time for data signals to stabilize.
The leading edge is the first clock edge of a clock cycle. The trailing edge is the last clock edge of a clock
cycle.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 384
ATtiny1616/3216
SPI - Serial Peripheral Interface
Figure 25-6. SPI Data Transfer Modes
1
2
3
4
5
6
7
8
MISO
1
2
3
4
5
6
7
8
MOSI
1
2
3
4
5
6
7
8
SPI Mode 0
Cycle #
SS
SCK
sampling
SPI Mode 1
Cycle #
1
2
3
4
5
6
7
8
MISO
1
2
3
4
5
6
7
8
MOSI
1
2
3
4
5
6
7
8
SS
SCK
sampling
SPI Mode 2
Cycle #
1
2
3
4
5
6
7
8
MISO
1
2
3
4
5
6
7
8
MOSI
1
2
3
4
5
6
7
8
SS
SCK
sampling
SPI Mode 3
Cycle #
1
2
3
4
5
6
7
8
MISO
1
2
3
4
5
6
7
8
MOSI
1
2
3
4
5
6
7
8
SS
SCK
sampling
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 385
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.3.3
Interrupts
Table 25-6. Available Interrupt Vectors and Sources
Offset
Name
Vector Description
0x00
SPI
SPI interrupt
Conditions
•
•
•
•
SSI: Slave Select Trigger Interrupt
DRE: Data Register Empty Interrupt
TXC: Transfer Complete Interrupt
RXC: Receive Complete Interrupt
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding enable bit in the peripheral's
Interrupt Control register (peripheral.INTCTRL).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
Related Links
8.7.3 SREG
13. CPUINT - CPU Interrupt Controller
25.3.4
Sleep Mode Operation
The SPI will continue working in Idle Sleep mode. When entering any deeper sleep mode, an active
transaction will be stopped.
Related Links
11. SLPCTRL - Sleep Controller
25.3.5
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 386
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.4
Register Summary - SPI
Offset
Name
Bit Pos.
0x00
0x01
0x02
CTRLA
CTRLB
INTCTRL
7:0
7:0
7:0
BUFEN
RXCIE
0x03
INTFLAGS
7:0
RXCIF/IF
0x04
DATA
7:0
25.5
DORD
BUFWR
TXCIE
TXCIF/
WRCOL
MASTER
CLK2X
PRESC[1:0]
SSD
DREIE
SSIE
ENABLE
MODE[1:0]
IE
DREIF
SSIF
BUFOVF
DATA[7:0]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 387
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLA
0x00
0x00
-
6
5
4
3
2
1
DORD
MASTER
CLK2X
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
PRESC[1:0]
0
ENABLE
Bit 6 – DORD Data Order
Value
Description
0
The MSB of the data word is transmitted first
1
The LSB of the data word is transmitted first
Bit 5 – MASTER Master/Slave Select
This bit selects the desired SPI mode.
If SS is configured as input and driven low while this bit is ’1’, this bit is cleared, and the IF flag in
SPIn.INTFLAGS is set. The user has to write MASTER=1 again to re-enable SPI Master mode.
This behavior is controlled by the Slave Select Disable bit (SSD) in SPIn.CTRLB.
Value
Description
0
SPI Slave mode selected
1
SPI Master mode selected
Bit 4 – CLK2X Clock Double
When this bit is written to ’1’ the SPI speed (SCK frequency, after internal prescaler) is doubled in Master
mode.
Value
Description
0
SPI speed (SCK frequency) is not doubled
1
SPI speed (SCK frequency) is doubled in Master mode
Bits 2:1 – PRESC[1:0] Prescaler
This bit field controls the SPI clock rate configured in Master mode. These bits have no effect in Slave
mode. The relationship between SCK and the peripheral clock frequency (fCLK_PER) is shown below.
The output of the SPI prescaler can be doubled by writing the CLK2X bit to ’1’.
Value
Name
Description
0x0
DIV4
CLK_PER/4
0x1
DIV16
CLK_PER/16
0x2
DIV64
CLK_PER/64
0x3
DIV128
CLK_PER/128
Bit 0 – ENABLE SPI Enable
Value
Description
0
SPI is disabled
1
SPI is enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 388
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.5.2
Control B
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
CTRLB
0x01
0x00
-
7
6
5
4
3
2
1
0
BUFEN
BUFWR
SSD
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
MODE[1:0]
Bit 7 – BUFEN Buffer Mode Enable
Writing this bit to '1' enables Buffer mode, meaning two buffers in receive direction, one buffer in transmit
direction, and separate interrupt flags for both transmit complete and receive complete.
Bit 6 – BUFWR Buffer Mode Wait for Receive
When writing this bit to '0' the first data transferred will be a dummy sample.
Value
Description
0
One SPI transfer must be completed before the data is copied into the Shift register.
1
When writing to the data register when the SPI is enabled and SS is high, the first write will
go directly to the Shift register.
Bit 2 – SSD Slave Select Disable
When this bit is set and when operating as SPI Master (MASTER=1 in SPIn.CTRLA), SS does not
disable Master mode.
Value
Description
0
Enable the Slave Select line when operating as SPI Master
1
Disable the Slave Select line when operating as SPI Master
Bits 1:0 – MODE[1:0] Mode
These bits select the Transfer mode. The four combinations of SCK phase and polarity with respect to the
serial data are shown in the table below. These bits decide whether the first edge of a clock cycle (leading
edge) is rising or falling and whether data setup and sample occur on the leading or trailing edge. When
the leading edge is rising, the SCK signal is low when idle, and when the leading edge is falling, the SCK
signal is high when idle.
Value
Name
Description
0x0
0
Leading edge: Rising, sample
Trailing edge: Falling, setup
0x1
1
Leading edge: Rising, setup
Trailing edge: Falling, sample
0x2
2
Leading edge: Falling, sample
Trailing edge: Rising, setup
0x3
3
Leading edge: Falling, setup
Trailing edge: Rising, sample
Related Links
25.3.2.3 Data Modes
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 389
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.5.3
Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
INTCTRL
0x02
0x00
-
7
6
5
4
3
2
1
0
RXCIE
TXCIE
DREIE
SSIE
IE
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
Bit 7 – RXCIE Receive Complete Interrupt Enable
In Buffer mode, this bit enables the receive complete interrupt. The enabled interrupt will be triggered
when the RXCIF flag in the SPIn.INTFLAGS register is set. In the Non-Buffer mode, this bit is ‘0’.
Bit 6 – TXCIE Transfer Complete Interrupt Enable
In Buffer mode, this bit enables the transfer complete interrupt. The enabled interrupt will be triggered
when the TXCIF flag in the SPIn.INTFLAGS register is set. In the Non-Buffer mode, this bit is ‘0’.
Bit 5 – DREIE Data Register Empty Interrupt Enable
In Buffer mode, this bit enables the data register empty interrupt. The enabled interrupt will be triggered
when the DREIF flag in the SPIn.INTFLAGS register is set. In the Non-Buffer mode, this bit is ‘0’.
Bit 4 – SSIE Slave Select Trigger Interrupt Enable
In Buffer mode, this bit enables the Slave Select interrupt. The enabled interrupt will be triggered when
the SSIF flag in the SPIn.INTFLAGS register is set. In the Non-Buffer mode, this bit is ‘0’.
Bit 0 – IE Interrupt Enable
This bit enables the SPI interrupt when the SPI is not in Buffer mode. The enabled interrupt will be
triggered when RXCIF/IF is set in the SPIn.INTFLAGS register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 390
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.5.4
Interrupt Flags
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
INTFLAGS
0x03
0x00
-
7
6
5
4
3
2
1
0
RXCIF/IF
TXCIF/WRCOL
DREIF
SSIF
BUFOVF
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
Bit 7 – RXCIF/IF Receive Complete Interrupt Flag/Interrupt Flag
RXCIF: In Buffer mode, this flag is set when there is unread data in the receive buffer and cleared when
the receive buffer is empty (i.e., does not contain any unread data). In the Non-Buffer mode, this bit does
not have any effect.
When interrupt-driven data reception is used, the receive complete interrupt routine must read the
received data from SPIn.DATA in order to clear RXCIF. If not, a new interrupt will occur directly after the
return from the current interrupt. This flag can also be cleared by writing a '1' to its bit location.
IF: This flag is set when a serial transfer is complete and one byte is completely shifted in/out of the
SPIn.DATA register. If SS is configured as input and is driven low when the SPI is in Master mode, this
will also set this flag. IF is cleared by hardware when executing the corresponding interrupt vector.
Alternatively, the IF flag can be cleared by first reading the SPIn.INTFLAGS register when IF is set, and
then accessing the SPIn.DATA register.
Bit 6 – TXCIF/WRCOL Transfer Complete Interrupt Flag/Write Collision Flag
TXCIF: In Buffer mode, this flag is set when all the data in the transmit shift register has been shifted out
and there is no new data in the transmit buffer (SPIn.DATA). The flag is cleared by writing a ‘1’ to its bit
location. In the Non-Buffer mode, this bit does not have any effect.
WRCOL: The WRCOL flag is set if the SPIn.DATA register is written to before a complete byte has been
shifted out. This flag is cleared by first reading the SPIn.INTFLAGS register when WRCOL is set, and
then accessing the SPIn.DATA register.
Bit 5 – DREIF Data Register Empty Interrupt Flag
In Buffer mode, this flag indicates whether the transmit buffer (SPIn.DATA) is ready to receive new data.
The flag is ‘1’ when the transmit buffer is empty and ‘0’ when the transmit buffer contains data to be
transmitted that has not yet been moved into the Shift register. DREIF is set to ‘0’ after a reset to indicate
that the transmitter is ready. In the Non-Buffer mode, this bit is always ‘0’.
DREIF is cleared by writing SPIn.DATA. When interrupt-driven data transmission is used, the software
must either write new data to SPIn.DATA in order to clear DREIF or disable the Data register empty
interrupt. If not, a new interrupt will occur directly after the return from the current interrupt.
Bit 4 – SSIF Slave Select Trigger Interrupt Flag
In Buffer mode, this flag indicates that the SPI has been in Master mode and the SS line has been pulled
low externally so the SPI is now working in Slave mode. The flag will only be set if the Slave Select
Disable bit (SSD) is not ‘1’. The flag is cleared by writing a ‘1’ to its bit location. In the Non-Buffer mode,
this bit is always ‘0’.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 391
ATtiny1616/3216
SPI - Serial Peripheral Interface
Bit 0 – BUFOVF Buffer Overflow
This flag is only used in Buffer mode. This flag indicates data loss due to a receiver buffer full condition.
This flag is set if a buffer overflow condition is detected. A buffer overflow occurs when the receive buffer
is full (two characters) and a third byte has been received in the Shift register. If there is no transmit data
the buffer overflow will not be set before the start of a new serial transfer. This flag is valid until the
receive buffer (SPIn.DATA) is read. Always write this bit location to ‘0’ when writing the SPIn.INTFLAGS
register. In the Non-Buffer mode, this bit is always ‘0’.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 392
ATtiny1616/3216
SPI - Serial Peripheral Interface
25.5.5
Data
Name:
Offset:
Reset:
Property:
Bit
DATA
0x04
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DATA[7:0]
Access
Reset
Bits 7:0 – DATA[7:0] SPI Data
The SPIn.DATA register is used for sending and receiving data. Writing to the register initiates the data
transmission, and the byte written to the register will be shifted out on the SPI output line.
Reading this register in Buffer mode will read the second receive buffer and the contents of the first
receive buffer will be moved to the second receive buffer.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 393
ATtiny1616/3216
TWI - Two-Wire Interface
26.
TWI - Two-Wire Interface
26.1
Features
• Bidirectional, Two-Wire Communication Interface
• Philips I2C compatible:
– Standard mode (Sm/100 kHz with slew-rate limited output)
– Fast mode (Fm/400 kHz with slew-rate limited output)
– Fast mode plus (Fm+/1 MHz with ×10 output drive strength)
• System Management Bus (SMBus) Compatible (100 kHz with Slew-Rate Limited Output):
– Support arbitration between start/repeated start and data bit
– Slave arbitration allows support for the Address Resolution Protocol (ARP)
– Configurable SMBus Layer 1 time-outs in hardware
• Independent Master and Slave Operation:
– Single or multi-master bus operation with full arbitration support
• Flexible Slave Address Match Hardware Operating in All Sleep Modes, Including Power-Down:
– 7-bit and general call address recognition
– 10-bit addressing support in collaboration with software
– Address mask register allows address range masking - alternatively, it can be used as a
secondary address match
– Optional software address recognition for an unlimited number of addresses
• Input Filter For Bus Noise Suppression
26.2
Overview
The Two-Wire Interface (TWI) peripheral is a bidirectional, two-wire communication interface. It is I2C and
System Management Bus (SMBus) compatible. The only external hardware needed to implement the bus
is one pull-up resistor on each bus line.
Any device connected to the bus must act as a master or a slave. The master initiates a data transaction
by addressing a slave on the bus and telling whether it wants to transmit or receive data. One bus can
have many slaves and one or several masters that can take control of the bus. An arbitration process
handles priority if more than one master tries to transmit data at the same time. Mechanisms for resolving
bus contention are inherent in the protocol.
The TWI peripheral supports master and slave functionality. The master and slave functionality are
separated from each other and can be enabled and configured separately. The master module supports
multi-master bus operation and arbitration. It contains the Baud Rate Generator. All 100 kHz, 400 kHz,
and 1 MHz bus frequencies are supported. Quick command and Smart mode can be enabled to autotrigger operations and reduce software complexity.
The slave module implements 7-bit address match and general address call recognition in hardware. 10bit addressing is supported. A dedicated Address Mask register can act as a Second Address match
register or as a register for address range masking. The slave continues to operate in all Sleep modes,
including Power-Down mode. This enables the slave to wake-up the device from all Sleep modes on TWI
address match. It is possible to disable the address matching to let this be handled in software instead.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 394
ATtiny1616/3216
TWI - Two-Wire Interface
The TWI peripheral will detect Start and Stop conditions, bus collisions, and bus errors. Arbitration lost,
errors, collision, and clock hold on the bus are also detected and indicated in separate status flags
available in both Master and Slave modes.
This device provides one instance of the TWI peripheral; TWI0.
26.2.1
Block Diagram
Figure 26-1. TWI Block Diagram
Master
BAUD
TxDATA
SCL
0
baud rate generator
Slave
TxDATA
SCL hold low
0
SCL hold low
shift register
shift register
SDA
0
0
RxDATA
26.2.2
ADDR/ADDRMASK
RxDATA
==
Signal Description
Signal
Description
Type
SCL
Serial clock line
Digital I/O
SDA
Serial data line
Digital I/O
Related Links
5. I/O Multiplexing and Considerations
26.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 26-1. TWI System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
Yes
CPUINT
Events
No
-
Debug
Yes
UPDI
Related Links
26.2.3.1 Clocks
26.2.3.5 Debug Operation
26.2.3.2 I/O Lines and Connections
26.2.3.3 Interrupts
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 395
ATtiny1616/3216
TWI - Two-Wire Interface
26.2.3.1 Clocks
This peripheral requires the system clock (CLK_PER). The relationship between CLK_PER and the TWI
bus clock (SCL) is explained in the TWI.MBAUD register.
Related Links
10. CLKCTRL - Clock Controller
26.5.6 MBAUD
26.2.3.2 I/O Lines and Connections
Using the I/O lines of the peripheral requires configuration of the I/O pins.
26.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
26.2.3.4 Events
Not applicable.
26.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
This peripheral can be forced to operate with halted CPU by writing a '1' to the Debug Run bit (DBGRUN)
in the Debug Control register of the peripheral (peripheral.DBGCTRL).
When the CPU is halted in Debug mode and DBGRUN=1, reading/writing the DATA register will neither
trigger a bus operation nor cause transmit and clear flags.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
Related Links
33. UPDI - Unified Program and Debug Interface
26.3
Functional Description
26.3.1
Initialization
Before enabling the master or the slave unit, ensure that the correct settings for SDASETUP, SDAHOLD,
and, if used, Fast-mode plus (FMPEN) are stored in TWI.CTRLA.
Master Operation
It is recommended to write to the Master Baud Rate register (TWIn.BAUD) before enabling the TWI
master since TIMEOUT is dependent on the baud rate setting. To start the TWI master, write a ‘1’ to the
ENABLE bit and configure an appropriate TIMEOUT if using the TWI in an SMBus environment. The
ENABLE and TIMEOUT bits are all located in the Master Control A register (TWIn.MCTRLA). If no
TIMEOUT value is set, which is the case for I²C operation, the bus state must be manually set to IDLE by
writing 0x1 to BUSSTATE in TWIn.MSTATUS at a safe point in time. Note that unlike the SMBus
specification, the I²C specification does not specify when it is safe to assume that the bus is idle in a
multi-master system. The application can solve this by ensuring that after all masters connected to the
bus are enabled, one supervising master performs a transfer before any of the other masters. The stop
condition of this initial transfer will indicate to the Bus State Monitor logic that the bus is idle and ready.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 396
ATtiny1616/3216
TWI - Two-Wire Interface
Slave Operation
To start the TWI slave, write the Slave Address (TWIn.SADDR), and write a '1' to the ENABLE bit in the
Slave Control A register (TWIn.SCTRLA). The TWI peripheral will wait to receive a byte addressed to it.
26.3.2
General TWI Bus Concepts
The TWI provides a simple, bidirectional, two-wire communication bus consisting of a serial clock line
(SCL) and a serial data line (SDA). The two lines are open-collector lines (wired-AND), and pull-up
resistors (Rp) are the only external components needed to drive the bus. The pull-up resistors provide a
high level on the lines when none of the connected devices are driving the bus.
The TWI bus is a simple and efficient method of interconnecting multiple devices on a serial bus. A device
connected to the bus can be a master or slave, where the master controls the bus and all communication.
Figure 26-2 illustrates the TWI bus topology.
Figure 26-2. TWI Bus Topology
VCC
RP
RP
TWI
DEVICE #1
TWI
DEVICE #2
TWI
DEVICE #N
RS
RS
RS
RS
RS
RS
SDA
SCL
Note: RS is optional
A unique address is assigned to all slave devices connected to the bus, and the master will use this to
address a slave and initiate a data transaction.
Several masters can be connected to the same bus, called a multi-master environment. An arbitration
mechanism is provided for resolving bus ownership among masters, since only one master device may
own the bus at any given time.
A device can contain both master and slave logic and can emulate multiple slave devices by responding
to more than one address.
A master indicates the start of a transaction by issuing a Start condition (S) on the bus. An address
packet with a slave address (ADDRESS) and an indication whether the master wishes to read or write
data (R/W) are then sent. After all data packets (DATA) are transferred, the master issues a Stop
condition (P) on the bus to end the transaction. The receiver must acknowledge (A) or not-acknowledge
(A) each byte received.
Figure 26-3 shows a TWI transaction.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 397
ATtiny1616/3216
TWI - Two-Wire Interface
Figure 26-3. Basic TWI Transaction Diagram Topology for a 7-Bit Address Bus
SDA
SCL
6 ... 0
S
7 ... 0
ADDRESS
S
ADDRESS
R/W
R/W
ACK
DATA
DATA
A
7 ... 0
ACK
A
DATA
P
ACK/NACK
A/A
DATA
P
Direction
Address Packet
Data Packet #0
Data Packet #1
Transaction
The master provides data on the bus
The master or slave can provide data on the bus
The slave provides data on the bus
The master provides the clock signal for the transaction, but a device connected to the bus is allowed to
stretch the low-level period of the clock to decrease the clock speed.
26.3.2.1 Start and Stop Conditions
Two unique bus conditions are used for marking the beginning (Start) and end (Stop) of a transaction.
The master issues a Start condition (S) by indicating a high-to-low transition on the SDA line while the
SCL line is kept high. The master completes the transaction by issuing a Stop condition (P), indicated by
a low-to-high transition on the SDA line while the SCL line is kept high.
Figure 26-4. Start and Stop Conditions
SDA
SCL
S
P
START
Condition
STOP
Condition
Multiple Start conditions can be issued during a single transaction. A Start condition that is not directly
following a Stop condition is called a repeated Start condition (Sr).
26.3.2.2 Bit Transfer
As illustrated in Figure 26-5, a bit transferred on the SDA line must be stable for the entire high period of
the SCL line. Consequently, the SDA value can only be changed during the low period of the clock. This
is ensured in hardware by the TWI module.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 398
ATtiny1616/3216
TWI - Two-Wire Interface
Figure 26-5. Data Validity
SDA
SCL
DATA
Valid
Change
Allowed
Combining bit transfers result in the formation of address and data packets. These packets consist of
eight data bits (one byte) with the Most Significant bit transferred first, plus a single-bit not-Acknowledge
(NACK) or Acknowledge (ACK) response. The addressed device signals ACK by pulling the SCL line low
during the ninth clock cycle, and signals NACK by leaving the line SCL high.
26.3.2.3 Address Packet
After the Start condition, a 7-bit address followed by a read/write (R/W) bit is sent. This is always
transmitted by the master. A slave recognizing its address will ACK the address by pulling the data line
low for the next SCL cycle, while all other slaves should keep the TWI lines released and wait for the next
Start and address. The address, R/W bit, and Acknowledge bit combined is the address packet. Only one
address packet for each Start condition is allowed, also when 10-bit addressing is used.
The R/W bit specifies the direction of the transaction. If the R/W bit is low, it indicates a master write
transaction, and the master will transmit its data after the slave has acknowledged its address. If the R/W
bit is high, it indicates a master read transaction, and the slave will transmit its data after acknowledging
its address.
26.3.2.4 Data Packet
An address packet is followed by one or more data packets. All data packets are nine bits long, consisting
of one data byte and one Acknowledge bit. The direction bit in the previous address packet determines
the direction in which the data is transferred.
26.3.2.5 Transaction
A transaction is the complete transfer from a Start to a Stop condition, including any repeated Start
conditions in between. The TWI standard defines three fundamental transaction modes: Master write,
master read, and a combined transaction.
Figure 26-6 illustrates the master write transaction. The master initiates the transaction by issuing a Start
condition (S) followed by an address packet with the direction bit set to '0' (ADDRESS+W).
Figure 26-6. Master Write Transaction
Transaction
Data Packet
Address Packet
S
ADDRESS
W
A
DATA
A
DATA
A/A
P
N data packets
Assuming the slave acknowledges the address, the master can start transmitting data (DATA) and the
slave will ACK or NACK (A/A) each byte. If no data packets are to be transmitted, the master terminates
the transaction by issuing a Stop condition (P) directly after the address packet. There are no limitations
to the number of data packets that can be transferred. If the slave signals a NACK to the data, the master
must assume that the slave cannot receive any more data and terminate the transaction.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 399
ATtiny1616/3216
TWI - Two-Wire Interface
Figure 26-7 illustrates the master read transaction. The master initiates the transaction by issuing a Start
condition followed by an address packet with the direction bit set to '1' (ADDRESS+R). The addressed
slave must acknowledge the address for the master to be allowed to continue the transaction.
Figure 26-7. Master Read Transaction
Transaction
Data Packet
Address Packet
S
R
ADDRESS
A
DATA
A
DATA
A
P
N data packets
Assuming the slave acknowledges the address, the master can start receiving data from the slave. There
are no limitations to the number of data packets that can be transferred. The slave transmits the data
while the master signals ACK or NACK after each data byte. The master terminates the transfer with a
NACK before issuing a Stop condition.
Figure 26-8 illustrates a combined transaction. A combined transaction consists of several read and write
transactions separated by repeated Start conditions (Sr).
Figure 26-8. Combined Transaction
Transaction
Address Packet #1
S
ADDRESS
R/W
Address Packet #2
N Data Packets
A
DATA
A/A Sr
ADDRESS
R/W
M Data Packets
A
DATA
A/A
P
Direction
Direction
26.3.2.6 Clock and Clock Stretching
All devices connected to the bus are allowed to stretch the low period of the clock to slow down the
overall clock frequency or to insert Wait states while processing data. A device that needs to stretch the
clock can do this by holding/forcing the SCL line low after it detects a low level on the line.
Three types of clock stretching can be defined, as shown in Figure 26-9.
Figure 26-9. Clock Stretching (1)
SDA
bit 7
bit 6
bit 0
ACK/NACK
SCL
S
Wakeup clock
stretching
Periodic clock
stretching
Random clock
stretching
Note: Clock stretching is not supported by all I2C slaves and masters.
If a slave device is in Sleep mode and a Start condition is detected, the clock stretching normally works
during the wake-up period. For AVR devices, the clock stretching will be either directly before or after the
ACK/NACK bit, as AVR devices do not need to wake-up for transactions that are not addressed to it.
A slave device can slow down the bus frequency by stretching the clock periodically on a bit level. This
allows the slave to run at a lower system clock frequency. However, the overall performance of the bus
will be reduced accordingly. Both the master and slave device can randomly stretch the clock on a byte
level basis before and after the ACK/NACK bit. This provides time to process incoming or prepare
outgoing data or perform other time-critical tasks.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 400
ATtiny1616/3216
TWI - Two-Wire Interface
In the case where the slave is stretching the clock, the master will be forced into a Wait state until the
slave is ready, and vice versa.
26.3.2.7 Arbitration
A master can start a bus transaction only if it has detected that the bus is idle. As the TWI bus is a multimaster bus, it is possible that two devices may initiate a transaction at the same time. This results in
multiple masters owning the bus simultaneously. This is solved using an arbitration scheme where the
master loses control of the bus if it is not able to transmit a high level on the SDA line. The masters who
lose arbitration must then wait until the bus becomes idle (i.e., wait for a Stop condition) before attempting
to reacquire bus ownership. Slave devices are not involved in the arbitration procedure.
Figure 26-10. TWI Arbitration
DEVICE1 Loses arbitration
DEVICE1_SDA
DEVICE2_SDA
SDA
(wired-AND)
bit 7
bit 6
bit 5
bit 4
SCL
S
Figure 26-10 shows an example where two TWI masters are contending for bus ownership. Both devices
are able to issue a Start condition, but DEVICE1 loses arbitration when attempting to transmit a high level
(bit 5) while DEVICE2 is transmitting a low level.
Arbitration between a repeated start condition and a data bit, a Stop condition and a data bit, or a
repeated Start condition and a Stop condition are not allowed and will require special handling by
software.
26.3.2.8 Synchronization
A clock synchronization algorithm is necessary for solving situations where more than one master is
trying to control the SCL line at the same time. The algorithm is based on the same principles used for
the clock stretching previously described. Figure 26-11 shows an example where two masters are
competing for control over the bus clock. The SCL line is the wired-AND result of the two masters clock
outputs.
Figure 26-11. Clock Synchronization
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 401
ATtiny1616/3216
TWI - Two-Wire Interface
Low Period
Count
Wait
State
High Period
Count
DEVICE1_SCL
DEVICE2_SCL
SCL
(wired-AND)
A high-to-low transition on the SCL line will force the line low for all masters on the bus, and they will start
timing their low clock period. The timing length of the low clock period can vary among the masters.
When a master (DEVICE1 in this case) has completed its low period, it releases the SCL line. However,
the SCL line will not go high until all masters have released it. Consequently, the SCL line will be held low
by the device with the longest low period (DEVICE2). Devices with shorter low periods must insert a wait
state until the clock is released. All masters start their high period when the SCL line is released by all
devices and has gone high. The device, which first completes its high period (DEVICE1), forces the clock
line low, and the procedure is then repeated. The result is that the device with the shortest clock period
determines the high period, while the low period of the clock is determined by the device with the longest
clock period.
26.3.3
TWI Bus State Logic
The bus state logic continuously monitors the activity on the TWI bus lines when the master is enabled. It
continues to operate in all Sleep modes, including power-down.
The bus state logic includes Start and Stop condition detectors, collision detection, inactive bus time-out
detection, and a bit counter. These are used to determine the bus state. The software can get the current
bus state by reading the Bus State bits in the master STATUS register. The bus state can be unknown,
idle, busy, or owner, and is determined according to the state diagram shown in Figure 26-12. The values
of the Bus State bits according to state, are shown in binary in the figure below.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 402
ATtiny1616/3216
TWI - Two-Wire Interface
Figure 26-12. Bus State, State Diagram
RESET
UNKNOWN
(0b00)
P + Timeout
S
IDLE
BUSY
P + Timeout
(0b01)
Sr
(0b11)
Command P
Write ADDRESS
(S)
OWNER
Arbitration
Lost
(0b10)
Write
ADDRESS(Sr)
After a system Reset and/or TWI master enable, the bus state is unknown. The bus state machine can be
forced to enter idle state by writing to the Bus State bits accordingly. If no state is set by the application
software, the bus state will become idle when the first Stop condition is detected. If the master inactive
bus time-out is enabled, the bus state will change to idle on the occurrence of a time-out. After a known
bus state is established, only a system Reset or disabling of the TWI master will set the state to unknown.
When the bus is idle, it is ready for a new transaction. If a Start condition generated externally is
detected, the bus becomes busy until a Stop condition is detected. The Stop condition will change the
bus state to idle. If the master inactive bus time-out is enabled, the bus state will change from busy to idle
on the occurrence of a time-out.
If a Start condition is generated internally while in an Idle state, the owner state is entered. If the complete
transaction was performed without interference (i.e., no collisions are detected), the master will issue a
Stop condition and the bus state will change back to idle. If a collision is detected, the arbitration is
assumed lost and the bus state becomes busy until a Stop condition is detected. A repeated Start
condition will only change the bus state if arbitration is lost during the issuing of the repeated Start.
Arbitration during repeated Start can be lost only if the arbitration has been ongoing since the first Start
condition. This happens if two masters send the exact same ADDRESS+DATA before one of the masters'
issues a repeated Start (Sr).
26.3.4
Operation
26.3.4.1 Electrical Characteristics
The TWI module in AVR devices follows the electrical specifications and timing of I2C bus and SMBus.
These specifications are not 100% compliant, and so to ensure correct behavior, the inactive bus time-out
period should be set in TWI Master mode. Refer to 26.3.4.2 TWI Master Operation for more details.
26.3.4.2 TWI Master Operation
The TWI master is byte-oriented, with an optional interrupt after each byte. There are separate interrupt
flags for master write and master read. Interrupt flags can also be used for a polled operation. There are
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 403
ATtiny1616/3216
TWI - Two-Wire Interface
dedicated status flags for indicating ACK/NACK received, bus error, arbitration lost, clock hold, and bus
state.
When an interrupt flag is set, the SCL line is forced low. This will give the master time to respond or
handle any data, and will in most cases require software interaction. Figure 26-13 shows the TWI master
operation. The diamond-shaped symbols (SW) indicate where software interaction is required. Clearing
the interrupt flags releases the SCL line.
Figure 26-13. TWI Master Operation
APPLICATION
MASTER WRITE INTERRUPT + HOLD
M1
M3
M2
BUSY
P
IDLE
S
Wait for
IDLE
SW
M4
ADDRESS
R/W BUSY
SW
R/W
A
SW
P
W
A
SW
Sr
M2
IDLE
M3
BUSY
M4
A/A
DATA
SW
SW
M1
BUSY
Driver software
MASTER READ INTERRUPT + HOLD
The master provides data
on the bus
SW
Slave provides data on
the bus
A
BUSY
A
P
A
Sr
Bus state
Mn
Diagram connections
IDLE
M4
M2
M3
A
R
A
DATA
The number of interrupts generated is kept to a minimum by an automatic handling of most conditions.
26.3.4.2.1 Clock Generation
The BAUD must be set to a value that results in a TWI bus clock frequency (fSCL) equal or less than 100
kHz/400 kHz/1 MHz, dependent on the mode used by the application (Standard mode Sm/Fast mode Fm/
Fast mode plus Fm+).
The low (TLOW) and high (THIGH) times are determined by the Baud Rate register (BAUD), while the rise
(TRISE) and fall (TFALL) times are determined by the bus topology. Because of the wired-AND logic of the
bus, TFALL will be considered as part of TLOW. Likewise, TRISE will be in a state between TLOW and THIGH
until a high state has been detected.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 404
ATtiny1616/3216
TWI - Two-Wire Interface
Figure 26-14. SCL Timing
RISE
•
•
•
•
•
•
•
•
TLOW – Low period of SCL clock
TSU;STO – Setup time for Stop condition
TBUF – Bus free time between Stop and Start conditions
THD;STA – Hold time (repeated) Start condition
TSU;STA – Setup time for repeated Start condition
THIGH is timed using the SCL high time count from TWI.MBAUD
TRISE is determined by the bus impedance; for internal pull-ups. Refer to Electrical Characteristics.
TFALL is determined by the open-drain current limit and bus impedance; can typically be regarded as
zero. Refer to Electrical Characteristics for details.
The SCL frequency is given by:
�SCL =
1
�LOW + �HIGH + �RISE
�SCL =
�CLK_PER
10 + 2���� + �CLK_PER ⋅ �RISE
The TWI.MBAUD value is used to time both SCL high and SCL low which gives the following formula of
SCL frequency:
If the TWI is in Fm+ mode, only TWI.MBAUD value of three or higher is supported. This means that for
Fm+ mode to achieve baud rate of 1 MHz, the peripheral clock (CLK_PER) has to run at 16 MHz or
faster.
26.3.4.2.2 Transmitting Address Packets
After issuing a Start condition, the master starts performing a bus transaction when the Master Address
register is written with the 7-bit slave address and direction bit. If the bus is busy, the TWI master will wait
until the bus becomes idle before issuing the Start condition.
Depending on arbitration and the R/W direction bit, one of four distinct cases (M1 to M4) arises following
the address packet. The different cases must be handled in software.
Case M1: Arbitration Lost or Bus Error during Address Packet
If arbitration is lost during the sending of the address packet, both the Master Write Interrupt Flag (WIF in
TWIn.MSTATUS) and Arbitration Lost Flag (ARBLOST in TWIn.MSTATUS) are set. Serial data output to
the SDA line is disabled, and the SCL line is released. The master is no longer allowed to perform any
operation on the bus until the bus state has changed back to idle.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 405
ATtiny1616/3216
TWI - Two-Wire Interface
A bus error will behave in the same way as an arbitration lost condition, but the Bus Error Flag (BUSERR
in TWIn.MSTATUS) is set in addition to the write interrupt and arbitration lost flags.
Case M2: Address Packet Transmit Complete - Address not Acknowledged by Slave
If no slave device responds to the address, the Master Write Interrupt Flag (WIF in TWIn.MSTATUS) and
the Master Received Acknowledge Flag (RXACK in TWIn.MSTATUS) are set. The RXACK flag reflects
the physical state of the ACK bit (i.e.< no slave did pull the ACK bit low). The clock hold is active at this
point, preventing further activity on the bus.
Case M3: Address Packet Transmit Complete - Direction Bit Cleared
If the master receives an ACK from the slave, the Master Write Interrupt Flag (WIF in TWIn.MSTATUS) is
set and the Master Received Acknowledge Flag (RXACK in TWIn.MSTATUS) is cleared. The clock hold
is active at this point, preventing further activity on the bus.
Case M4: Address Packet Transmit Complete - Direction Bit Set
If the master receives an ACK from the slave, the master proceeds to receive the next byte of data from
the slave. When the first data byte is received, the Master Read Interrupt Flag (RIF in TWIn.MSTATUS) is
set and the Master Received Acknowledge Flag (RXACK in TWIn.MSTATUS) is cleared. The clock hold
is active at this point, preventing further activity on the bus.
26.3.4.2.3 Transmitting Data Packets
The slave will know when an address packet with R/W direction bit set has been successfully received. It
can then start sending data by writing to the slave data register. When a data packet transmission is
completed, the data interrupt flag is set. If the master indicates NACK, the slave must stop transmitting
data and expect a Stop or repeated Start condition.
26.3.4.2.4 Receiving Data Packets
The slave will know when an address packet with R/W direction bit cleared has been successfully
received. After acknowledging this, the slave must be ready to receive data. When a data packet is
received, the data interrupt flag is set and the slave must indicate ACK or NACK. After indicating a NACK,
the slave must expect a Stop or repeated Start condition.
26.3.4.2.5 Quick Command Mode
With Quick Command enabled (QCEN in TWIn.MCTRLA), the R/W# bit of the slave address denotes the
command. This is a SMBus specific command where the R/W bit may be used to simply turn a device
function ON or OFF, or enable/disable a low-power Standby mode. There is no data sent or received.
After the master receives an acknowledge from the slave, either RIF or WIF flag in TWIn.MSTATUS will
be set depending on the polarity of R/W. When either RIF or WIF flag is set after issuing a Quick
Command, the TWI will accept a stop command through writing the CMD bits in TWIn.MCTRLB.
Figure 26-15. Quick Command Frame Format
S
Address
R/W
A
P
26.3.4.3 TWI Slave Operation
The TWI slave is byte-oriented with optional interrupts after each byte. There are separate slave data and
address/stop interrupt flags. Interrupt flags can also be used for polled operation. There are dedicated
status flags for indicating ACK/NACK received, clock hold, collision, bus error, and read/write direction.
When an interrupt flag is set, the SCL line is forced low. This will give the slave time to respond or handle
data, and will in most cases require software interaction. Figure 26-16 shows the TWI slave operation.
The diamond-shaped symbols (SW) indicate where software interaction is required.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 406
ATtiny1616/3216
TWI - Two-Wire Interface
Figure 26-16. TWI Slave Operation
SLAVE ADDRESS INTERRUPT
S1
S3
S2
S
A
ADDRESS
R
SW
P
S2
Sr
S3
DATA
SW
S1
P
S2
Sr
S3
A/A
Driver software
The master provides data
on the bus
Slave provides data on
the bus
Sn
S1
A
A
SW
SLAVE DATA INTERRUPT
W
SW
Interrupt on STOP
Condition Enabled
SW
A/A
DATA
SW
A/A
Diagram connections
The number of interrupts generated is kept to a minimum by automatic handling of most conditions. Quick
command can be enabled to auto-trigger operations and reduce software complexity.
Address Recognition mode can be enabled to allow the slave to respond to all received addresses.
26.3.4.3.1 Receiving Address Packets
When the TWI slave is properly configured, it will wait for a Start condition to be detected. When this
happens, the successive address byte will be received and checked by the address match logic, and the
slave will ACK a correct address and store the address in the TWIn.DATA register. If the received address
is not a match, the slave will not acknowledge and store the address, but wait for a new Start condition.
The slave address/stop interrupt flag is set when a Start condition succeeded by a valid address byte is
detected. A general call address will also set the interrupt flag.
A Start condition immediately followed by a Stop condition is an illegal operation and the bus error flag is
set.
The R/W direction flag reflects the direction bit received with the address. This can be read by software to
determine the type of operation currently in progress.
Depending on the R/W direction bit and bus condition, one of four distinct cases (S1 to S4) arises
following the address packet. The different cases must be handled in software.
Case S1: Address Packet Accepted - Direction Bit Set
If the R/W direction flag is set, this indicates a master read operation. The SCL line is forced low by the
slave, stretching the bus clock. If ACK is sent by the slave, the slave hardware will set the data interrupt
flag indicating data is needed for transmit. Data, repeated Start, or Stop can be received after this. If
NACK is sent by the slave, the slave will wait for a new Start condition and address match.
Case S2: Address Packet Accepted - Direction Bit Cleared
If the R/W direction flag is cleared, this indicates a master write operation. The SCL line is forced low,
stretching the bus clock. If ACK is sent by the slave, the slave will wait for data to be received. Data,
repeated Start, or Stop can be received after this. If NACK is sent, the slave will wait for a new Start
condition and address match.
Case S3: Collision
If the slave is not able to send a high level or NACK, the collision flag is set, and it will disable the data
and acknowledge output from the slave logic. The clock hold is released. A Start or repeated Start
condition will be accepted.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 407
ATtiny1616/3216
TWI - Two-Wire Interface
Case S4: STOP Condition Received
When the Stop condition is received, the slave address/stop flag will be set, indicating that a Stop
condition, and not an address match, occurred.
26.3.4.3.2 Receiving Data Packets
The slave will know when an address packet with R/W direction bit cleared has been successfully
received. After acknowledging this, the slave must be ready to receive data. When a data packet is
received, the data interrupt flag is set and the slave must indicate ACK or NACK. After indicating a NACK,
the slave must expect a Stop or repeated Start condition.
26.3.4.3.3 Transmitting Data Packets
The slave will know when an address packet with R/W direction bit set has been successfully received. It
can then start sending data by writing to the slave data register. When a data packet transmission is
completed, the data interrupt flag is set. If the master indicates NACK, the slave must stop transmitting
data and expect a Stop or repeated Start condition.
26.3.4.4 Smart Mode
The TWI interface has a Smart mode that simplifies application code and minimizes the user interaction
needed to adhere to the I2C protocol. For TWI Master, Smart mode accomplishes this by automatically
sending an ACK as soon as data register TWI.MDATA is read. This feature is only active when the
ACKACT bit in TWIn.MCTRLA register is set to ACK. If ACKACT is set to NACK, the TWI Master will not
generate a NACK bit followed by reading the Data register.
With Smart mode enabled for TWI Slave (SMEN bit in TWIn.SCTRLA), DIF (Data Interrupt Flag) will
automatically be cleared if Data register (TWIn.SDATA) is read or written.
26.3.5
26.3.6
Events
Not applicable.
Interrupts
Table 26-2. Available Interrupt Vectors and Sources
Offset Name Vector Description Conditions
0x00
Slave
TWI Slave interrupt
0x02
Master TWI Master interrupt
• DIF: Data Interrupt Flag in 26.5.11 SSTATUS set
• APIF: Address or Stop Interrupt Flag in 26.5.11 SSTATUS
set
• RIF: Read Interrupt Flag in 26.5.5 MSTATUS set
• WIF: Write Interrupt Flag in 26.5.5 MSTATUS set
When an interrupt condition occurs, the corresponding interrupt flag is set in the Master register
(TWI.MSTATUS) or Slave Status register (TWI.SSTATUS).
When several interrupt request conditions are supported by an interrupt vector, the interrupt requests are
ORed together into one combined interrupt request to the interrupt controller. The user must read the
peripheral's INTFLAGS register to determine which of the interrupt conditions are present.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 408
ATtiny1616/3216
TWI - Two-Wire Interface
26.3.7
Sleep Mode Operation
The bus state logic and slave continue to operate in all Sleep modes, including Power-Down Sleep mode.
If a slave device is in Sleep mode and a Start condition is detected, clock stretching is active during the
wake-up period until the system clock is available. The master will stop operation in all Sleep modes.
26.3.8
Synchronization
Not applicable.
26.3.9
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 409
ATtiny1616/3216
TWI - Two-Wire Interface
26.4
Register Summary - TWI
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
0x0D
0x0E
CTRLA
Reserved
DBGCTRL
MCTRLA
MCTRLB
MSTATUS
MBAUD
MADDR
MDATA
SCTRLA
SCTRLB
SSTATUS
SADDR
SDATA
SADDRMASK
7:0
26.5
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
SDASETUP
RIEN
WIEN
RIF
WIF
DIEN
APIEN
DIF
APIF
QCEN
SDAHOLD[1:0]
TIMEOUT[1:0]
FLUSH
ACKACT
CLKHOLD
RXACK
ARBLOST
BUSERR
BAUD[7:0]
ADDR[7:0]
DATA[7:0]
PIEN
PMEN
ACKACT
CLKHOLD
RXACK
COLL
BUSERR
ADDR[7:0]
DATA[7:0]
ADDRMASK[6:0]
FMPEN
DBGRUN
SMEN
ENABLE
MCMD[1:0]
BUSSTATE[1:0]
SMEN
ENABLE
SCMD[1:0]
DIR
AP
ADDREN
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 410
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
7
CTRLA
0x00
0x00
-
6
5
4
SDASETUP
Access
Reset
3
2
SDAHOLD[1:0]
1
0
FMPEN
R/W
R/W
R/W
R/W
0
0
0
0
Bit 4 – SDASETUP SDA Setup Time
By default, there are four clock cycles of setup time on SDA out signal while reading from the slave part
of the TWI module. Writing this bit to ‘1’ will change the setup time to eight clocks.
Value
Name
Description
0
4CYC
SDA setup time is four clock cycles
1
8CYC
SDA setup time is eight clock cycle
Bits 3:2 – SDAHOLD[1:0] SDA Hold Time
Writing these bits selects the SDA hold time.
Table 26-3. SDA Hold Time
SDAHOLD[1:0] Nominal Hold Time Hold Time Range Across
All Corners in ns
Description
0x0
OFF
0
Hold time OFF.
0x1
50 ns
36 - 131
Backward compatible setting.
0x2
300 ns
180 - 630
Meets SMBus specification under
typical conditions.
0x3
500 ns
300 - 1050
Meets SMBus specification
across all corners.
Bit 1 – FMPEN FM Plus Enable
Writing these bits selects the 1 MHz bus speed (Fast mode plus, Fm+) for the TWI in default
configuration.
Value
Description
0
Fm+ disabled
1
Fm+ enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 411
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.2
Debug Control
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x02
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Debug Run
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 412
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.3
Master Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
MCTRLA
0x03
0x00
-
7
6
5
4
3
2
RIEN
WIEN
QCEN
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
TIMEOUT[1:0]
1
0
SMEN
ENABLE
R/W
R/W
0
0
Bit 7 – RIEN Read Interrupt Enable
Writing this bit to ‘1’ enables interrupt on the Master Read Interrupt Flag (RIF) in the Master Status
register (TWIn.MSTATUS). A TWI Master read interrupt would be generated only if this bit, the RIF, and
the Global Interrupt Flag (I) in CPU.SREG are all ‘1’.
Bit 6 – WIEN Write Interrupt Enable
Writing this bit to ‘1’ enables interrupt on the Master Write Interrupt Flag (WIF) in the Master Status
register (TWIn.MSTATUS). A TWI Master write interrupt will be generated only if this bit, the WIF, and the
Global Interrupt Flag (I) in CPU.SREG are all ‘1’.
Bit 4 – QCEN Quick Command Enable
Writing this bit to ‘1’ enables Quick Command. When Quick Command is enabled, the corresponding
interrupt flag is set immediately after the slave acknowledges the address. At this point, the software can
either issue a Stop command or a repeated Start by writing either the Command bits (CMD) in the Master
Control B register (TWIn.MCTRLB) or the Master Address register (TWIn.MADDR).
Bits 3:2 – TIMEOUT[1:0] Inactive Bus Time-Out
Setting the inactive bus time-out (TIMEOUT) bits to a non-zero value will enable the inactive bus time-out
supervisor. If the bus is inactive for longer than the TIMEOUT setting, the bus state logic will enter the Idle
state.
Value
Name
Description
0x0
DISABLED
Bus time-out disabled. I2C.
0x1
50US
50 µs - SMBus (assume baud is set to 100 kHz)
0x2
100US
100 µs (assume baud is set to 100 kHz)
0x3
200US
200 µs (assume baud is set to 100 kHz)
Bit 1 – SMEN Smart Mode Enable
Writing this bit to ‘1’ enables the Master Smart mode. When Smart mode is enabled, the acknowledge
action is sent immediately after reading the Master Data (TWIn.MDATA) register.
Bit 0 – ENABLE Enable TWI Master
Writing this bit to ‘1’ enables the TWI as master.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 413
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.4
Master Control B
Name:
Offset:
Reset:
Property:
Bit
MCTRLB
0x04
0x00
-
7
6
5
Access
Reset
4
3
2
1
0
FLUSH
ACKACT
R/W
R/W
R/W
R/W
0
0
0
0
MCMD[1:0]
Bit 3 – FLUSH Flush
Writing a ‘1’ to this bit generates a strobe for one clock cycle disabling and then enabling the master.
Writing ‘0’ has no effect.
The purpose is to clear the internal state of the master: For TWI master to transmit successfully, it is
recommended to write the Master Address register (TWIn.MADDR) first and then the Master Data
register (TWIn.MDATA).
The peripheral will transmit invalid data if TWIn.MDATA is written before TWIn.MADDR. To avoid this
invalid transmission, write ‘1’ to this bit to clear both registers.
Bit 2 – ACKACT Acknowledge Action
This bit defines the master’s behavior under certain conditions defined by the bus protocol state and
software interaction. The acknowledge action is performed when DATA is read, or when an execute
command is written to the CMD bits.
The ACKACT bit is not a flag or strobe, but an ordinary read/write accessible register bit. The default
ACKACT for master read interrupt is “Send ACK” (0). For master write, the code will know that no
acknowledge should be sent since it is itself sending data.
Value
Description
0
Send ACK
1
Send NACK
Bits 1:0 – MCMD[1:0] Command
The master command bits are strobes. These bits are always read as zero.
Writing to these bits triggers a master operation as defined by the table below.
Table 26-4. Command Settings
MCMD[1:0] DIR Description
0x0
X
NOACT - No action
0x1
X
REPSTART - Execute Acknowledge Action succeeded by repeated Start
0x2
0
RECVTRANS - Execute Acknowledge Action succeeded by a byte read operation
1
Execute Acknowledge Action (no action) succeeded by a byte send operation(1)
X
STOP - Execute Acknowledge Action succeeded by issuing a Stop condition
0x3
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 414
ATtiny1616/3216
TWI - Two-Wire Interface
Note:
1. For a master being a sender, it will normally wait for new data written to the Master Data register
(TWIn.MDATA).
The acknowledge action bits and command bits can be written at the same time.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 415
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.5
Master Status
Name:
Offset:
Reset:
Property:
MSTATUS
0x05
0x00
-
Normal TWI operation dictates that this register is regarded purely as a read-only register. Clearing any of
the status flags is done indirectly by accessing the Master Transmits Address (TWIn.MADDR), the Master
Data register (TWIn.MDATA), or the Command bits (CMD) in the Master Control B register
(TWIn.MCTRLB).
Bit
Access
Reset
7
6
5
4
3
2
1
0
RIF
WIF
CLKHOLD
RXACK
ARBLOST
BUSERR
R/W
R/W
R/W
R
R/W
R/W
R/W
BUSSTATE[1:0]
R/W
0
0
0
0
0
0
0
0
Bit 7 – RIF Read Interrupt Flag
This bit is set to ‘1’ when the master byte read operation is successfully completed (i.e., no arbitration lost
or bus error occurred during the operation). The read operation is triggered by software reading DATA or
writing to ADDR registers with bit ADDR[0] written to ‘1’. A slave device must have responded with an
ACK to the address and direction byte transmitted by the master for this flag to be set.
Writing a ‘1’ to this bit will clear the RIF. However, normal use of the TWI does not require the flag to be
cleared by this method.
Clearing the RIF bit will follow the same software interaction as the CLKHOLD flag.
The RIF flag can generate a master read interrupt (see the description of the RIEN control bit in the
TWIn.MCTRLA register).
Bit 6 – WIF Write Interrupt Flag
This bit is set when a master transmit address or byte write is completed, regardless of the occurrence of
a bus error or an arbitration lost condition.
Writing a ‘1’ to this bit will clear the WIF. However, normal use of the TWI does not require the flag to be
cleared by this method.
Clearing the WIF bit will follow the same software interaction as the CLKHOLD flag.
The WIF flag can generate a master write interrupt (see the description of the WIEN control bit in the
TWIn.MCTRLA register).
Bit 5 – CLKHOLD Clock Hold
If read as ‘1’, this bit indicates that the master is currently holding the TWI clock (SCL) low, stretching the
TWI clock period.
Writing a ‘1’ to this bit will clear the CLKHOLD flag. However, normal use of the TWI does not require the
CLKHOLD flag to be cleared by this method, since the flag is automatically cleared when accessing
several other TWI registers. The CLKHOLD flag can be cleared by:
1. Writing a ‘1’ to it.
2. Writing to the TWIn.MADDR register.
3. Writing to the TWIn.MDATA register.
4. Reading the TWIn.DATA register while the ACKACT control bits in TWIn.MCTRLB are set to either
send ACK or NACK.
5. Writing a valid command to the TWIn.MCTRLB register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 416
ATtiny1616/3216
TWI - Two-Wire Interface
Bit 4 – RXACK Received Acknowledge
This bit is read-only and contains the most recently received Acknowledge bit from the slave. When read
as ‘0’, the most recent acknowledge bit from the slave was ACK. When read as ‘1’, the most recent
acknowledge bit was NACK.
Bit 3 – ARBLOST Arbitration Lost
If read as ‘1’ this bit indicates that the master has lost arbitration while transmitting a high data or NACK
bit, or while issuing a Start or repeated Start condition (S/Sr) on the bus.
Writing a ‘1’ to it will clear the ARBLOST flag. However, normal use of the TWI does not require the flag to
be cleared by this method. However, as for the CLKHOLD flag, clearing the ARBLOST flag is not required
during normal use of the TWI.
Clearing the ARBLOST bit will follow the same software interaction as the CLKHOLD flag.
Given the condition where the bus ownership is lost to another master, the software must either abort
operation or resend the data packet. Either way, the next required software interaction is in both cases to
write to the TWIn.MADDR register. A write access to the TWIn.MADDR register will then clear the
ARBLOST flag.
Bit 2 – BUSERR Bus Error
The BUSERR flag indicates that an illegal bus condition has occurred. An illegal bus condition is detected
if a protocol violating Start (S), repeated Start (Sr), or Stop (P) is detected on the TWI bus lines. A Start
condition directly followed by a Stop condition is one example of protocol violation.
Writing a ‘1’ to this bit will clear the BUSERR. However, normal use of the TWI does not require the
BUSERR to be cleared by this method.
A robust TWI driver software design will treat the bus error flag similarly to the ARBLOST flag, assuming
the bus ownership is lost when the bus error flag is set. As for the ARBLOST flag, the next software
operation of writing the TWIn.MADDR register will consequently clear the BUSERR flag. For bus error to
be detected, the bus state logic must be enabled and the system frequency must be 4x the SCL
frequency.
Bits 1:0 – BUSSTATE[1:0] Bus State
These bits indicate the current TWI bus state as defined in the table below. After a System Reset or reenabling, the TWI master bus state will be unknown. The change of bus state is dependent on the bus
activity.
Writing 0x1 to the BUSSTATE bits forces the bus state logic into its Idle state. However, the bus state
logic cannot be forced into any other state. When the master is disabled, the bus state is ‘unknown’.
Value
Name
Description
0x0
UNKNOWN
Unknown bus state
0x1
IDLE
Bus is idle
0x2
OWNER
This TWI controls the bus
0x3
BUSY
The bus is busy
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 417
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.6
Master Baud Rate
Name:
Offset:
Reset:
Property:
Bit
MBAUD
0x06
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
BAUD[7:0]
Access
Reset
Bits 7:0 – BAUD[7:0] Baud Rate
This bit field is used to derive the SCL high and low time and should be written while the master is
disabled (ENABLE bit in TWIn.MCTRLA is '0').
For more information on how to calculate the frequency, see the section on Clock Generation.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 418
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.7
Master Address
Name:
Offset:
Reset:
Property:
Bit
MADDR
0x07
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
ADDR[7:0]
Access
Reset
Bits 7:0 – ADDR[7:0] Address
When this bit field is written, a Start condition and slave address protocol sequence is initiated dependent
on the bus state.
If the bus state is unknown the Master Write Interrupt Flag (WIF) and Bus Error flag (BUSERR) in the
Master Status register (TWIn.MSTATUS) are set and the operation is terminated.
If the bus is busy the master awaits further operation until the bus becomes idle. When the bus is or
becomes idle, the master generates a Start condition on the bus, copies the ADDR value into the Data
Shift register (TWIn.MDATA) and performs a byte transmit operation by sending the contents of the Data
register onto the bus. The master then receives the response (i.e., the Acknowledge bit from the slave).
After completing the operation the bus clock (SCL) is forced and held low only if arbitration was not lost.
The CLKHOLD bit in the Master Setup register (TWIn.MSETUP) is set accordingly. Completing the
operation sets the WIF in the Master Status register (TWIn.MSTATUS).
If the bus is already owned, a repeated Start (Sr) sequence is performed. In two ways the repeated Start
(Sr) sequence deviates from the Start sequence. Firstly, since the bus is already owned by the master, no
wait for idle bus state is necessary. Secondly, if the previous transaction was a read, the acknowledge
action is sent before the Repeated Start bus condition is issued on the bus.
The master receives one data byte from the slave before the master sets the Master Read Interrupt Flag
(RIF) in the Master Status register (TWIn.MSTATUS). All TWI Master flags are cleared automatically
when this bit field is written. This includes bus error, arbitration lost, and both master interrupt flags.
This register can be read at any time without interfering with ongoing bus activity, since a read access
does not trigger the master logic to perform any bus protocol related operations.
The master control logic uses bit 0 of the TWIn.MADDR register as the bus protocol’s Read/Write flag
(R/W).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 419
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.8
Master DATA
Name:
Offset:
Reset:
Property:
Bit
MDATA
0x08
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DATA[7:0]
Access
Reset
Bits 7:0 – DATA[7:0] Data
The bit field gives direct access to the master's physical Shift register which is used both to shift data out
onto the bus (write) and to shift in data received from the bus (read).
The direct access implies that the Data register cannot be accessed during byte transmissions. Built-in
logic prevents any write access to this register during the shift operations. Reading valid data or writing
data to be transmitted can only be successfully done when the bus clock (SCL) is held low by the master
(i.e., when the CLKHOLD bit in the Master Status register (TWIn.MSTATUS) is set). However, it is not
necessary to check the CLKHOLD bit in software before accessing this register if the software keeps
track of the present protocol state by using interrupts or observing the interrupt flags.
Accessing this register assumes that the master clock hold is active, auto-triggers bus operations
dependent of the state of the Acknowledge Action Command bit (ACKACT) in TWIn.MSTATUS and type
of register access (read or write).
A write access to this register will, independent of ACKACT in TWIn.MSTATUS, command the master to
perform a byte transmit operation on the bus directly followed by receiving the Acknowledge bit from the
slave. When the Acknowledge bit is received, the Master Write Interrupt Flag (WIF) in TWIn.MSTATUS is
set regardless of any bus errors or arbitration. If operating in a multi-master environment, the interrupt
handler or application software must check the Arbitration Lost Status Flag (ARBLOST) in
TWIn.MSTATUS before continuing from this point. If the arbitration was lost, the application software must
decide to either abort or to resend the packet by rewriting this register. The entire operation is performed
(i.e., all bits are clocked), regardless of winning or losing arbitration before the write interrupt flag is set.
When arbitration is lost, only '1's are transmitted for the remainder of the operation, followed by a write
interrupt with ARBLOST flag set.
Both TWI Master Interrupt Flags are cleared automatically when this register is written. However, the
Master Arbitration Lost and Bus Error flags are left unchanged.
Reading this register triggers a bus operation, dependent on the setting of the Acknowledge Action
Command bit (ACKACT) in TWIn.MSTATUS. Normally the ACKACT bit is preset to either ACK or NACK
before the register read operation. If ACK or NACK action is selected, the transmission of the
acknowledge bit precedes the release of the clock hold. The clock is released for one byte, allowing the
slave to put one byte of data on the bus. The Master Read Interrupt flag RIF in TWIn.MSTATUS is then
set if the procedure was successfully executed. However, if arbitration was lost when sending NACK, or a
bus error occurred during the time of operation, the Master Write Interrupt flag (WIF) is set instead.
Observe that the two Master Interrupt Flags are mutually exclusive (i.e., both flags will not be set
simultaneously).
Both TWI Master Interrupt Flags are cleared automatically if this register is read while ACKACT is set to
either ACK or NACK. However, arbitration lost and bus error flags are left unchanged.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 420
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.9
Slave Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
SCTRLA
0x09
0x00
-
7
6
5
DIEN
APIEN
R/W
R/W
0
0
4
3
2
1
0
PIEN
PMEN
SMEN
ENABLE
R/W
R/W
R/W
R/W
0
0
0
0
Bit 7 – DIEN Data Interrupt Enable
Writing this bit to ‘1’ enables interrupt on the Slave Data Interrupt Flag (DIF) in the Slave Status register
(TWIn.SSTATUS). A TWI slave data interrupt will be generated only if this bit, the DIF, and the Global
Interrupt Flag (I) in CPU.SREG are all ‘1’.
Bit 6 – APIEN Address or Stop Interrupt Enable
Writing this bit to ‘1’ enables an interrupt on the Slave Address or Stop Interrupt Flag (APIF) in the Slave
Status register (TWIn.SSTATUS). A TWI slave Address or Stop interrupt will be generated only if this bit,
APIF, and the Global Interrupt Flag (I) in CPU.SREG are all ‘1’.
The slave stop interrupt shares the interrupt flag and vector with the slave address interrupt. The
TWIn.SCTRAL.PIEN must be written to ‘1’ in order for the APIF to be set on a stop condition. When the
interrupt occurs the TWIn.SSTATUS.AP bit will determine whether an address match or a stop condition
caused the interrupt.
Bit 5 – PIEN Stop Interrupt Enable
Writing this bit to ‘1’ enables APIF to be set when a Stop condition occurs. To use this feature the system
frequency must be 4x the SCL frequency.
Bit 2 – PMEN Address Recognition Mode
If this bit is written to ‘1’, the slave address match logic responds to all received addresses.
If this bit is written to ‘0’, the address match logic uses the Slave Address register (TWIn.SADDR) to
determine which address to recognize as the slaves own address.
Bit 1 – SMEN Smart Mode Enable
Writing this bit to ‘1’ enables the slave Smart mode. When the Smart mode is enabled, issuing a
command with CMD or reading/writing DATA resets the interrupt and operation continues. If the Smart
mode is disabled, the slave always waits for a CMD command before continuing.
Bit 0 – ENABLE Enable TWI Slave
Writing this bit to ‘1’ enables the TWI slave.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 421
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.10 Slave Control B
Name:
Offset:
Reset:
Property:
Bit
SCTRLB
0x0A
0x00
-
7
6
5
4
3
2
1
ACKACT
Access
Reset
0
SCMD[1:0]
R/W
R/W
R/W
0
0
0
Bit 2 – ACKACT Acknowledge Action
This bit defines the slave’s behavior under certain conditions defined by the bus protocol state and
software interaction. The table below lists the acknowledge procedure performed by the slave if action is
initiated by software. The acknowledge action is performed when TWIn.SDATA is read or written, or when
an execute command is written to the CMD bits in this register.
The ACKACT bit is not a flag or strobe, but an ordinary read/write accessible register bit.
Value
Name
Description
0
ACK
Send ACK
1
NACK
Send NACK
Bits 1:0 – SCMD[1:0] Command
Unlike the acknowledge action bits, the Slave command bits are strobes. These bits always read as ‘0’.
Writing to these bits trigger a slave operation as defined in the table below.
Table 26-5. Command Settings
SCMD[1:0]
DIR Description
0x0
X
NOACT - No action
0x1
X
Reserved
0x2 - COMPTRANS Used to complete a transaction
0x3 - RESPONSE
0
Execute Acknowledge Action succeeded by waiting for any Start (S/Sr)
condition
1
Wait for any Start (S/Sr) condition
Used in response to an address interrupt (APIF)
0
Execute Acknowledge Action succeeded by reception of next byte
1
Execute Acknowledge Action succeeded by slave data interrupt
Used in response to a data interrupt (DIF)
0
Execute Acknowledge Action succeeded by reception of next byte
1
Execute a byte read operation followed by Acknowledge Action
The acknowledge action bits and command bits can be written at the same time.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 422
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.11 Slave Status
Name:
Offset:
Reset:
Property:
SSTATUS
0x0B
0x00
-
Normal TWI operation dictates that the Slave Status register should be regarded purely as a read-only
register. Clearing any of the status flags will indirectly be done when accessing the Slave Data
(TWIn.SDATA) register or the CMD bits in the Slave Control B register (TWIn.SCTRLB).
Bit
Access
Reset
7
6
5
4
3
2
1
0
DIF
APIF
CLKHOLD
RXACK
COLL
BUSERR
DIR
AP
R/W
R/W
R
R
R/W
R/W
R
R
0
0
0
0
0
0
0
0
Bit 7 – DIF Data Interrupt Flag
This flag is set when a slave byte transmit or byte receive operation is successfully completed without any
bus error. The flag can be set with an unsuccessful transaction in case of collision detection (see the
description of the COLL Status bit). Writing a ‘1’ to its bit location will clear the DIF. However, normal use
of the TWI does not require the DIF flag to be cleared by using this method, since the flag is automatically
cleared when:
1. Writing to the Slave DATA register.
2. Reading the Slave DATA register.
3. Writing a valid command to the CTRLB register.
The DIF flag can be used to generate a slave data interrupt (see the description of the DIEN control bit in
TWIn.CTRLA).
Bit 6 – APIF Address or Stop Interrupt Flag
This flag is set when the slave address match logic detects that a valid address has been received or by
a Stop condition. Writing a ‘1’ to its bit location will clear the APIF. However, normal use of the TWI does
not require the flag to be cleared by this method since the flag is cleared using the same software
interactions as described for the DIF flag.
The APIF flag can be used to generate a slave address or stop interrupt (see the description of the AIEN
control bit in TWIn.CTRLA). Take special note of that the slave stop interrupt shares the interrupt vector
with the slave address interrupt.
Bit 5 – CLKHOLD Clock Hold
If read as ‘1’, the slave clock hold flag indicates that the slave is currently holding the TWI clock (SCL)
low, stretching the TWI clock period. This is a read-only bit that is set when an address or data interrupt is
set. Resetting the corresponding interrupt will indirectly reset this flag.
Bit 4 – RXACK Received Acknowledge
This bit is read-only and contains the most recently received Acknowledge bit from the master. When
read as ‘0’, the most recent acknowledge bit from the master was ACK. When read as ‘1’, the most recent
acknowledge bit was NACK.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 423
ATtiny1616/3216
TWI - Two-Wire Interface
Bit 3 – COLL Collision
If read as ‘1’, the transmit collision flag indicates that the slave has not been able to transmit a high data
or NACK bit. If a slave transmit collision is detected, the slave will commence its operation as normal,
except no low values will be shifted out onto the SDA line (i.e., when the COLL flag is set to ‘1’ it disables
the data and acknowledge output from the slave logic). The DIF flag will be set to ‘1’ at the end as a result
of the internal completion of an unsuccessful transaction. Similarly, when a collision occurs because the
slave has not been able to transmit NACK bit, it means the address match already happened and APIF
flag is set as a result. APIF/DIF flags can only generate interrupts whose handlers can be used to check
for the collision. Writing a ‘1’ to its bit location will clear the COLL flag. However, the flag is automatically
cleared if any Start condition (S/Sr) is detected.
This flag is intended for systems where the address resolution protocol (ARP) is employed. However, a
detected collision in non-ARP situations indicates that there has been a protocol violation and should be
treated as a bus error.
Bit 2 – BUSERR Bus Error
The BUSERR flag indicates that an illegal bus condition has occurred. An illegal bus condition is detected
if a protocol violating Start (S), Repeated Start (Sr), or Stop (P) is detected on the TWI bus lines. A Start
condition directly followed by a Stop condition is one example of protocol violation. Writing a ‘1’ to its bit
location will clear the BUSERR flag. However, normal use of the TWI does not require the BUSERR to be
cleared by this method. A robust TWI driver software design will assume that the entire packet of data
has been corrupted and restart by waiting for a new Start condition (S). The TWI bus error detector is part
of the TWI Master circuitry. For bus errors to be detected, the TWI Master must be enabled (ENABLE bit
in TWIn.MCTRLA is ‘1’), and the system clock frequency must be at least four times the SCL frequency.
Bit 1 – DIR Read/Write Direction
This bit is read-only and indicates the current bus direction state. The DIR bit reflects the direction bit
value from the last address packet received from a master TWI device. If this bit is read as ‘1’, a master
read operation is in progress. Consequently, a ‘0’ indicates that a master write operation is in progress.
Bit 0 – AP Address or Stop
When the TWI slave address or Stop Interrupt Flag (APIF) is set, this bit determines whether the interrupt
is due to address detection or a Stop condition.
Value
Name
Description
0
STOP
A Stop condition generated the interrupt on APIF
1
ADR
Address detection generated the interrupt on APIF
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 424
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.12 Slave Address
Name:
Offset:
Reset:
Property:
Bit
SADDR
0x0C
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
ADDR[7:0]
Access
Reset
Bits 7:0 – ADDR[7:0] Address
The Slave Address register in combination with the Slave Address Mask register (TWIn.SADDRMASK) is
used by the slave address match logic to determine if a master TWI device has addressed the TWI slave.
The Slave Address Interrupt Flag (APIF) is set to ‘1’ if the received address is recognized. The slave
address match logic supports recognition of 7- and 10-bits addresses, and general call address.
When using 7-bit or 10-bit Address Recognition mode, the upper seven bits of the Address register
(ADDR[7:1]) represent the slave address and the Least Significant bit (ADDR[0]) is used for general call
address recognition. Writing the ADDR[0] bit to ‘1’, in this case, enables the general call address
recognition logic. The TWI slave address match logic only supports recognition of the first byte of a 10-bit
address (i.e., by setting ADDRA[7:1] = “0b11110aa” where “aa” represents bit 9 and 8, or the slave
address). The second 10-bit address byte must be handled by software.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 425
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.13 Slave Data
Name:
Offset:
Reset:
Property:
Bit
SDATA
0x0D
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DATA[7:0]
Access
Reset
Bits 7:0 – DATA[7:0] Data
The Slave Data register I/O location (DATA) provides direct access to the slave's physical Shift register,
which is used both to shift data out onto the bus (transmit) and to shift in data received from the bus
(receive). The direct access implies that the Data register cannot be accessed during byte transmissions.
Built-in logic prevents any write accesses to the Data register during the shift operations. Reading valid
data or writing data to be transmitted can only be successfully done when the bus clock (SCL) is held low
by the slave (i.e., when the slave CLKHOLD bit is set). However, it is not necessary to check the
CLKHOLD bit in software before accessing the slave DATA register if the software keeps track of the
present protocol state by using interrupts or observing the interrupt flags. Accessing the slave DATA
register, assumed that clock hold is active, auto-trigger bus operations dependent of the state of the
Slave Acknowledge Action Command bits (ACKACT) and type of register access (read or write).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 426
ATtiny1616/3216
TWI - Two-Wire Interface
26.5.14 Slave Address Mask
Name:
Offset:
Reset:
Property:
Bit
SADDRMASK
0x0E
0x00
-
7
6
5
R/W
R/W
R/W
0
0
0
4
3
2
1
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
ADDRMASK[6:0]
Access
Reset
0
ADDREN
Bits 7:1 – ADDRMASK[6:0] Address Mask
The ADDRMASK register acts as a second address match register, or an address mask register
depending on the ADDREN setting.
If ADDREN is written to '0', ADDRMASK can be loaded with a 7-bit Slave Address mask. Each of the bits
in the TWIn.SADDRMASK register can mask (disable) the corresponding address bits in the TWI slave
Address Register (TWIn.SADDR). If the mask bit is written to '1' then the address match logic ignores the
compare between the incoming address bit and the corresponding bit in slave TWIn.SADDR register. In
other words, masked bits will always match.
If ADDREN is written to '1', the TWIn.SADDRMASK can be loaded with a second slave address in
addition to the TWIn.SADDR register. In this mode, the slave will match on two unique addresses, one in
TWIn.SADDR and the other in TWIn.SADDRMASK.
Bit 0 – ADDREN Address Mask Enable
If this bit is written to '1', the slave address match logic responds to the two unique addresses in slave
TWIn.SADDR and TWIn.SADDRMASK.
If this bit is '0', the TWIn.SADDRMASK register acts as a mask to the TWIn.SADDR register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 427
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
27.
CRCSCAN - Cyclic Redundancy Check Memory Scan
27.1
Features
•
•
•
•
•
•
27.2
CRC-16-CCITT
Can Check Full Flash, Application Code, and/or Boot Section
Priority Check Mode
Selectable NMI Trigger on Failure
User Configurable Check During Internal Reset Initialization
Paused in all CPU Sleep Modes
Overview
A Cyclic Redundancy Check (CRC) takes a data stream of bytes from the NVM (either entire Flash, only
Boot section, or both application code and Boot section) and generates a checksum. The CRC peripheral
(CRCSCAN) can be used to detect errors in program memory.
The last location in the section to check has to contain the correct pre-calculated checksum for
comparison. If the checksum calculated by the CRCSCAN and the pre-calculated checksums match, a
Status bit in the CRCSCAN is set. If they do not match, the Status register will indicate that it failed. The
user can choose to let the CRCSCAN generate a Non-Maskable Interrupt (NMI) if the checksums do not
match.
An n-bit CRC, applied to a data block of arbitrary length, will detect any single alteration (error burst) up to
n bits in length. For longer error bursts, a fraction 1-2-n will be detected.
The CRC-generator supports CRC-16-CCITT.
Polynomial:
• CRC-16-CCITT: x16 + x12 + x5 + 1
The CRC reads in byte-by-byte of the content of the section(s) it is set up to check, starting with byte 0,
and generates a new checksum per byte. The byte is sent through an implementation corresponding to
Figure 27-1, starting with the Most Significant bit. If the last two bytes in the section contain the correct
checksum, the CRC will pass. See 27.3.2.1 Checksum for how to place the checksum. The initial value
of the Checksum register is 0xFFFF.
Figure 27-1. CRC Implementation Description
data
15
x14
x13
x12
x11
x10
x9
x8
x7
x6
x5
x4
x3
x2
x1
x0
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
Q D
x
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 428
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
27.2.1
Block Diagram
Figure 27-2. Cyclic Redundancy Check Block Diagram
Memory
(Boot, App,
Flash)
CTRLB
CTRLA
Source
CRC
calculation
Enable,
Reset
BUSY
STATUS
CRC OK
CHECKSUM
27.2.2
NMI Req
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 27-1. System Product Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
No
-
Interrupts
Yes
CPUINT
Events
No
-
Debug
Yes
UPDI
Related Links
11.2.2.1 Clocks
27.2.2.3 Interrupts
27.2.2.1 Clocks
This peripheral depends on the peripheral clock.
Related Links
10. CLKCTRL - Clock Controller
27.2.2.2 I/O Lines and Connections
Not applicable.
27.2.2.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
27.3.3 Interrupts
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 429
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
27.2.2.4 Events
Not applicable.
27.2.2.5 Debug Operation
Whenever the debugger accesses the device, for instance, reading or writing a peripheral or memory
location, the CRCSCAN peripheral will be disabled.
If the CRCSCAN is busy when the debugger accesses the device, the CRCSCAN will restart the ongoing
operation when the debugger accesses an internal register or when the debugger disconnects.
The BUSY bit in the Status register (CRCSCAN.STATUS) will read '1' if the CRCSCAN was busy when
the debugger caused it to disable, but it will not actively check any section as long as the debugger keeps
it disabled. There are synchronized CRC Status bits in the debugger's internal register space, which can
be read by the debugger without disabling the CRCSCAN. Reading the debugger's internal CRC status
bits will make sure that the CRCSCAN is enabled.
It is possible to write the CRCSCAN.STATUS register directly from the debugger:
• BUSY bit in CRCSCAN.STATUS:
– Writing the BUSY bit to '0' will stop the ongoing CRC operation (so that the CRCSCAN does not
restart its operation when the debugger allows it).
– Writing the BUSY bit to '1' will make the CRC start a single check with the settings in the Control
B register (CRCSCAN.CTRLB), but not until the debugger allows it.
As long as the BUSY bit in CRCSCAN.STATUS is '1', CRCSCAN.CRCTRLB and the Non-Maskable
Interrupt Enable bit (NMIEN) in the Control A register (CRCSCAN.CTRLA) cannot be altered.
• OK bit in CRCSCAN.STATUS:
– Writing the OK bit to '0' can trigger a Non-Maskable Interrupt (NMI) if the NMIEN bit in
CRCSCAN.CTRLA is '1'. If an NMI has been triggered, no writes to the CRCSCAN are allowed.
– Writing the OK bit to '1' will make the OK bit read as '1' when the BUSY bit in
CRCSCAN.STATUS is '0'.
Writes to CRCSCAN.CTRLA and CRCSCAN.CTRLB from the debugger are treated in the same way as
writes from the CPU.
Related Links
33. UPDI - Unified Program and Debug Interface
27.5.1 CTRLA
27.5.2 CTRLB
27.3
Functional Description
27.3.1
Initialization
To enable a CRC in software (or via the debugger):
1. Write the Source (SRC) bit field of the Control B register (CRCSCAN.CTRLB) to select the desired
source settings. Ensure that the MODE bit field in CRCSCAN.CTRLB is 0x0.
2. Enable the CRCSCAN by writing a '1' to the ENABLE bit in the Control A register
(CRCSCAN.CTRLA).
3. The CRC will start after three cycles, and the CPU will continue executing during these three
cycles.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 430
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
The CRCSCAN can be enabled during the internal Reset initialization to ensure the Flash is OK before
letting the CPU execute code. If the CRCSCAN fails during the internal Reset initialization, the CPU is not
allowed to start normal code execution - the device remains in Reset state instead of executing code with
unexpected behavior. The full source settings are available during the internal Reset initialization. See the
Fuse description for more information.
If the CRCSCAN was enabled during the internal Reset initialization, the CRC Control A and B registers
will reflect this when normal code execution is started:
• The ENABLE bit in CRCSCAN.CTRLA will be '1'
• The MODE bit field in CRCSCAN.CTRLB will be non-zero
• The SRC bit field in CRCSCAN.CTRLB will reflect the checked section(s).
The CRCSCAN can be enabled during Reset by configuring the CRCSRC fuse in FUSE.SYSCFG0.
Related Links
27.5.1 CTRLA
27.5.2 CTRLB
6.10 Configuration and User Fuses (FUSE)
12.3.2.2 Reset Time
27.3.2
Operation
The CRC is operating in Priority mode: the CRC peripheral has priority access to the Flash and will stall
the CPU until completed.
In Priority mode, the CRC fetches a new word (16-bit) on every third main clock cycle, or when the CRC
peripheral is configured to do a scan from start-up.
27.3.2.1 Checksum
The pre-calculated checksum must be present in the last location of the section to be checked. If the
BOOT section should be checked, the 16-bit checksum must be saved in the last two bytes of the BOOT
section, and similarly for APPLICATION and entire Flash. Table 27-2 shows explicitly how the checksum
should be stored for the different sections. Also, see the CRCSCAN.CTRLB register description for how
to configure which section to check and the device fuse description for how to configure the BOOTEND
and APPEND fuses.
Table 27-2. How to Place the Pre-Calculated 16-Bit Checksum in Flash
27.3.3
Section to Check
CHECKSUM[15:8]
CHECKSUM[7:0]
BOOT
FUSE_BOOTEND*256-2
FUSE_BOOTEND*256-1
BOOT and APPLICATION
FUSE_APPEND*256-2
FUSE_APPEND*256-1
Full Flash
FLASHEND-1
FLASHEND
Interrupts
Table 27-3. Available Interrupt Vectors and Sources
Offset
Name
Vector Description
Conditions
0x00
NMI
Non-Maskable Interrupt
Generated on CRC failure
When the interrupt condition occurs, the OK flag in the Status register (CRCSCAN.STATUS) is cleared to
'0'.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 431
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
An interrupt is enabled by writing a '1' to the respective Enable bit (NMIEN) in the Control A register
(CRCSCAN.CTRLA), but can only be disabled with a system Reset. An NMI is generated when the OK
flag in CRCSCAN.STATUS is cleared and the NMIEN bit is '1'. The NMI request remains active until a
system Reset, and cannot be disabled.
A non-maskable interrupt can be triggered even if interrupts are not globally enabled.
Related Links
27.5.1 CTRLA
27.5.3 STATUS
13. CPUINT - CPU Interrupt Controller
27.3.4
Sleep Mode Operation
CTCSCAN is halted in all sleep modes. In all CPU Sleep modes, the CRCSCAN peripheral is halted and
will resume operation when the CPU wakes up.
The CRCSCAN starts operation three cycles after writing the EN bit in CRCSCAN.CTRLA. During these
three cycles, it is possible to enter Sleep mode. In this case:
1. The CRCSCAN will not start until the CPU is woken up.
2. Any interrupt handler will execute after CRCSCAN has finished.
27.3.5
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 432
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
27.4
Register Summary - CRCSCAN
Offset
Name
Bit Pos.
0x00
0x01
0x02
CTRLA
CTRLB
STATUS
7:0
7:0
7:0
27.5
RESET
MODE[1:0]
NMIEN
ENABLE
SRC[1:0]
OK
BUSY
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 433
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
27.5.1
Control A
Name:
Offset:
Reset:
Property:
CTRLA
0x00
0x00
-
If an NMI has been triggered, this register is not writable.
Bit
Access
Reset
1
0
RESET
7
6
5
4
3
2
NMIEN
ENABLE
R/W
R/W
R/W
0
0
0
Bit 7 – RESET Reset CRCSCAN
Writing this bit to '1' resets the CRCSCAN peripheral: The CRCSCAN Control registers and STATUS
register (CTRLA, CTRLB, STATUS) will be cleared one clock cycle after the RESET bit was written to '1'.
If NMIEN is '0', this bit is writable both when the CRCSCAN is busy (the BUSY bit in CRCSCAN.STATUS
is '1') and not busy (the BUSY bit is '0'), and will take effect immediately.
If NMIEN is '1', this bit is only writable when the CRCSCAN is not busy (the BUSY bit in
CRCSCAN.STATUS is '0').
The RESET bit is a strobe bit.
Bit 1 – NMIEN Enable NMI Trigger
When this bit is written to '1', any CRC failure will trigger an NMI.
This can only be cleared by a system Reset - it is not cleared by a write to the RESET bit.
This bit can only be written to '1' when the CRCSCAN is not busy (the BUSY bit in CRCSCAN.STATUS is
'0').
Bit 0 – ENABLE Enable CRCSCAN
Writing this bit to '1' enables the CRCSCAN peripheral with the current settings. It will stay '1' even after a
CRC check has completed, but writing it to ‘1’ again will start a new check.
Writing the bit to '0' will disable the CRCSCAN after the ongoing check is completed (after reaching the
end of the section it is set up to check). A failure in the ongoing check will still be detected and can cause
an NMI if the NMIEN bit is '1'.
The CRCSCAN can be enabled during the internal Reset initialization to verify Flash sections before
letting the CPU start normal code execution (see the device data sheet fuse description). If the
CRCSCAN is enabled during the internal Reset initialization, the ENABLE bit will read as '1' when normal
code execution starts.
To see whether the CRCSCAN peripheral is busy with an ongoing check, poll the Busy bit (BUSY) in the
STATUS register (CRCSCAN.STATUS).
Related Links
6.10 Configuration and User Fuses (FUSE)
12.3.2.2 Reset Time
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 434
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
27.5.2
Control B
Name:
Offset:
Reset:
Property:
CTRLB
0x01
0x00
-
The CTRLB register contains the mode and source settings for the CRC. It is not writable when the CRC
is busy or when an NMI has been triggered.
Bit
7
6
5
4
3
2
1
MODE[1:0]
Access
Reset
0
SRC[1:0]
R/W
R/W
R/W
R/W
0
0
0
0
Bits 5:4 – MODE[1:0] CRC Flash Access Mode
The CRC can be enabled during internal Reset initialization to verify Flash sections before letting the
CPU start (see the device data sheet fuse description). If the CRC is enabled during internal Reset
initialization, the MODE bit field will read out non-zero when normal code execution starts. To ensure
proper operation of the CRC under code execution, write the MODE bit to 0x0 again.
Value
Name
Description
0x0
PRIORITY The CRC module runs a single check with priority to Flash. The CPU is halted
until the CRC completes.
other
Reserved
Bits 1:0 – SRC[1:0] CRC Source
The SRC bit field selects which section of the Flash the CRC module should check. To set up section
sizes, refer to the fuse description.
The CRC can be enabled during internal Reset initialization to verify Flash sections before letting the
CPU start (see fuse description). If the CRC is enabled during internal Reset initialization, the SRC bit
field will read out as FLASH, BOOTAPP, or BOOT when normal code execution starts (depending on the
configuration).
Value
Name
Description
0x0
FLASH
The CRC is performed on the entire Flash (boot, application code, and
application data sections).
0x1
BOOTAPP The CRC is performed on the boot and application code sections of Flash.
0x2
BOOT
The CRC is performed on the boot section of Flash.
0x3
Reserved.
Related Links
6.10 Configuration and User Fuses (FUSE)
12.3.2.2 Reset Time
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 435
ATtiny1616/3216
CRCSCAN - Cyclic Redundancy Check Memory Sca...
27.5.3
Status
Name:
Offset:
Reset:
Property:
STATUS
0x02
0x02
-
The STATUS register contains the busy and OK information. It is not writable, only readable.
Bit
7
6
5
4
3
2
1
0
OK
BUSY
Access
R
R
Reset
1
0
Bit 1 – OK CRC OK
When this bit is read as '1', the previous CRC completed successfully. The bit is set to '1' from Reset but
is cleared to '0' when enabling. As long as the CRC module is busy, it will be read '0'. When running
continuously, the CRC status must be assumed OK until it fails or is stopped by the user.
Bit 0 – BUSY CRC Busy
When this bit is read as '1', the CRC module is busy. As long as the module is busy, the access to the
control registers is limited.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 436
ATtiny1616/3216
CCL - Configurable Custom Logic
28.
CCL - Configurable Custom Logic
28.1
Features
•
•
•
•
•
•
•
•
28.2
Glue Logic for General Purpose PCB Design
Up to two Programmable Look-Up Tables LUT[1:0]
Combinatorial Logic Functions: Any Logic Expression That is a Function of up to Three Inputs.
Sequential Logic Functions:
Gated D Flip-Flop, JK Flip-Flop, gated D Latch, RS Latch
Flexible Look-Up Table Inputs Selection:
– I/Os
– Events
– Subsequent LUT output
– Internal peripherals
• Analog comparator
• Timer/counters
• USART
• SPI
Clocked by System Clock or Other Peripherals
Output Can be Connected to I/O pins or Event System
Optional Synchronizer, Filter, or Edge Detector Available on Each LUT Output
Overview
The Configurable Custom Logic (CCL) is a programmable logic peripheral which can be connected to the
device pins, to events, or to other internal peripherals. The CCL can serve as "glue logic" between the
device peripherals and external devices. The CCL can eliminate the need for external logic components,
and can also help the designer to overcome real-time constraints by combining core independent
peripherals to handle the most time-critical parts of the application independent of the CPU.
The CCL peripheral has one pair of Look-Up Tables (LUT). Each LUT consists of three inputs, a truth
table, and a filter/edge detector. Each LUT can generate an output as a user programmable logic
expression with three inputs. Inputs can be individually masked.
The output can be generated from the inputs combinatorially and can be filtered to remove spikes. An
optional sequential module can be enabled. The inputs to the sequential module are individually
controlled by two independent, adjacent LUT (LUT0/LUT1) outputs, enabling complex waveform
generation.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 437
ATtiny1616/3216
CCL - Configurable Custom Logic
28.2.1
Block Diagram
Figure 28-1. Configurable Custom Logic
LUT0
INSEL
Internal
Events
I/O
Peripherals
FILTSEL
TRUTH
Filter/
Synch
CLKSRC
EDGEDET
Edge
Detector
LUT0-OUT
CLK_MUX_OUT
LUT0-IN[2]
clkCCL
SEQSEL
Sequential
ENABLE
LUT1
INSEL
Internal
Events
I/O
Peripherals
FILTSEL
TRUTH
Filter/
Synch
CLKSRC
LUT1-IN[2]
clkCCL
EDGEDET
Edge
Detector
LUT1-OUT
CLK_MUX_OUT
ENABLE
28.2.2
Signal Description
Pin Name
Type
Description
LUTn-OUT
Digital output
Output from look-up table
LUTn-IN[2:0]
Digital input
Input to look-up table
Refer to I/O Multiplexing and Considerations for details on the pin mapping for this peripheral. One signal
can be mapped to several pins.
Related Links
5. I/O Multiplexing and Considerations
28.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 28-1. CCL System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
No
-
Events
Yes
EVSYS
Debug
Yes
UPDI
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 438
ATtiny1616/3216
CCL - Configurable Custom Logic
28.2.3.1 Clocks
By default, the CCL is using the peripheral clock of the device (CLK_PER).
Alternatively, the CCL can be clocked by a peripheral input that is available on LUT n input line 2
(LUTn_IN[2]). This is configured by writing a '1' to the Clock Source Selection bit (CLKSRC) in the LUT n
Control A register (CCL.LUTnCTRLA). The sequential block is clocked by the same clock as that of the
even LUT in the LUT pair (SEQn.clk = LUT2n.clk). It is advised to disable the peripheral by writing a '0' to
the Enable bit (ENABLE) in the Control A register (CCL.CTRLA) before configuring the CLKSRC bit in
CCL.LUTnCTRLA.
Alternatively, the input line 2 (IN[2]) of an LUT can be used to clock the LUT and the corresponding
Sequential block. This is enabled by writing a '1' to the Clock Source Selection bit (CLKSRC) in the LUT n
Control A register (CCL.LUTnCTRLA).
The CCL must be disabled before changing the LUT clock source: write a '0' to the Enable bit (ENABLE)
in Control A register (CCL.CTRLA).
Related Links
10. CLKCTRL - Clock Controller
28.2.3.2 I/O Lines
The CCL can take inputs and generate output through I/O pins. For this to function properly, the I/O pins
must be configured to be used by a Look Up Table (LUT).
Related Links
16. PORT - I/O Pin Configuration
28.2.3.3 Interrupts
Not applicable.
28.2.3.4 Debug Operation
When the CPU is halted in Debug mode the CCL continues normal operation. However, the CCL cannot
be halted when the CPU is halted in Debug mode. If the CCL is configured in a way that requires it to be
periodically serviced by the CPU, improper operation or data loss may result during debugging.
28.3
Functional Description
28.3.1
Initialization
The following bits are enable-protected, meaning that they can only be written when the corresponding
even LUT is disabled (ENABLE=0 in CCL.LUT0CTRLA):
• Sequential Selection (SEQSEL) in Sequential Control 0 register (CCL.SEQCTRL0)
The following registers are enable-protected, meaning that they can only be written when the
corresponding LUT is disabled (ENABLE=0 in CCL.LUT0CTRLA):
• LUT n Control x register, except ENABLE bit (CCL.LUTnCTRLx)
Enable-protected bits in the CCL.LUTnCTRLx registers can be written at the same time as ENABLE in
CCL.LUTnCTRLx is written to '1', but not at the same time as ENABLE is written to '0'.
Enable-protection is denoted by the enable-protected property in the register description.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 439
ATtiny1616/3216
CCL - Configurable Custom Logic
28.3.2
Operation
28.3.2.1 Enabling, Disabling, and Resetting
The CCL is enabled by writing a '1' to the ENABLE bit in the Control register (CCL.CTRLA). The CCL is
disabled by writing a '0' to that ENABLE bit.
Each LUT is enabled by writing a '1' to the LUT Enable bit (ENABLE) in the LUT n Control A register
(CCL.LUTnCTRLA). Each LUT is disabled by writing a '0' to the ENABLE bit in CCL.LUTnCTRLA.
28.3.2.2 Look-Up Table Logic
The look-up table in each LUT unit can generate a combinational logic output as a function of up to three
inputs IN[2:0]. Unused inputs can be masked (tied low). The truth table for the combinational logic
expression is defined by the bits in the CCL.TRUTHn registers. Each combination of the input bits
(IN[2:0]) corresponds to one bit in the TRUTHn register, as shown in the table below.
Table 28-2. Truth Table of LUT
IN[2]
IN[1]
IN[0]
OUT
0
0
0
TRUTH[0]
0
0
1
TRUTH[1]
0
1
0
TRUTH[2]
0
1
1
TRUTH[3]
1
0
0
TRUTH[4]
1
0
1
TRUTH[5]
1
1
0
TRUTH[6]
1
1
1
TRUTH[7]
28.3.2.3 Truth Table Inputs Selection
Input Overview
The inputs can be individually:
• Masked
• Driven by Peripherals:
– Analog Comparator (AC) output
– Timer/Counters (TC) waveform outputs
• Driven by Internal Events from Event System
• Driven by Other CCL Sub-modules
The input selection for each input y of LUT n is configured by writing the input y source selection bit in the
LUT n Control x=[B,C] registers:
• INSEL0 in CCL.LUTnCTRLB
• INSEL1 in CCL.LUTnCTRLB
• INSEL2 in CCL.LUTnCTRLC
Internal Feedback Inputs (FEEDBACK)
When selected (INSELy=FEEDBACK in CCL.LUTnCTRLx), the Sequential (SEQ) output is used as input
for the corresponding LUT.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 440
ATtiny1616/3216
CCL - Configurable Custom Logic
The output from an internal sequential module can be used as input source for the LUT, see the figure
below for an example for LUT0 and LUT1. The sequential selection for each LUT follows the formula:
IN 2N � = SEQ �
IN 2N+1 � = SEQ �
With N representing the sequencer number and i=0,1 representing the LUT input index.
For details, refer to 28.3.2.6 Sequential Logic.
Figure 28-2. Feedback Input Selection
Linked LUT (LINK)
When selecting the LINK input option, the next LUT's direct output is used as the LUT input. In general,
LUT[n+1] is linked to the input of LUT[n]. As example, LUT1 is the input for LUT0.
Figure 28-3. Linked LUT Input Selection
LUT0
SEQ 0
CTRL
(ENABLE)
LUT1
Internal Events Inputs Selection (EVENT)
Asynchronous events from the Event System can be used as input to the LUT. Two event input lines
(EVENT0 and EVENT1) are available, and can be selected as LUT input. Before selecting the EVENT
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 441
ATtiny1616/3216
CCL - Configurable Custom Logic
input option by writing to the LUT CONTROL A or B register (CCL.LUTnCTRLB or LUTnCTRLC), the
Event System must be configured.
I/O Pin Inputs (I/O)
When selecting the I/O option, the LUT input will be connected to its corresponding I/O pin. Refer to the
I/O Multiplexing section for more details about where the LUTnINy is located.
Figure 28-4. I/O Pin Input Selection
Peripherals
The different peripherals on the three input lines of each LUT are selected by writing to the respective
LUT n Input y bit fields in the LUT n Control B and C registers:
• INSEL0 in CCL.LUTnCTRLB
• INSEL1 in CCL.LUTnCTRLB
• INSEL2 in CCL.LUTnCTRLC
Related Links
5. I/O Multiplexing and Considerations
16. PORT - I/O Pin Configuration
10. CLKCTRL - Clock Controller
29. AC - Analog Comparator
20. TCA - 16-bit Timer/Counter Type A
22. TCD - 12-Bit Timer/Counter Type D
24. USART - Universal Synchronous and Asynchronous Receiver and Transmitter
25. SPI - Serial Peripheral Interface
26. TWI - Two-Wire Interface
5. I/O Multiplexing and Considerations
28.3.2.4 Filter
By default, the LUT output is a combinational function of the LUT inputs. This may cause some short
glitches when the inputs change the value. These glitches can be removed by clocking through filters if
demanded by application needs.
The Filter Selection bits (FILTSEL) in the LUT Control registers (CCL.LUTnCTRLA) define the digital filter
options. When a filter is enabled, the output will be delayed by two to five CLK cycles (peripheral clock or
alternative clock). One clock cycle after the corresponding LUT is disabled, all internal filter logic is
cleared.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 442
ATtiny1616/3216
CCL - Configurable Custom Logic
Figure 28-5. Filter
FILTSEL
Input
OUT
Q
D
R
Q
D
R
Q
D
R
D
G
Q
R
CLK_MUX_OUT
CLR
28.3.2.5 Edge Detector
The edge detector can be used to generate a pulse when detecting a rising edge on its input. To detect a
falling edge, the TRUTH table should be programmed to provide inverted output.
The edge detector is enabled by writing '1' to the Edge Selection bit (EDGEDET) in the LUT n Control A
register (CCL.LUTnCTRLA). In order to avoid unpredictable behavior, a valid filter option must be enabled
as well.
Edge detection is disabled by writing a '0' to EDGEDET in CCL.LUTnCTRLA. After disabling an LUT, the
corresponding internal Edge Detector logic is cleared one clock cycle later.
Figure 28-6. Edge Detector
CLK_MUX_OUT
28.3.2.6 Sequential Logic
Each LUT pair can be connected to an internal Sequential block. A Sequential block can function as
either D flip-flop, JK flip-flop, gated D-latch, or RS-latch. The function is selected by writing the Sequential
Selection bits (SEQSEL) in the Sequential Control register (CCL.SEQCTRLn).
The Sequential block receives its input from either LUT, filter, or edge detector, depending on the
configuration.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 443
ATtiny1616/3216
CCL - Configurable Custom Logic
The Sequential block is clocked by the same clock as the corresponding LUT, which is either the
peripheral clock or input line 2 (IN[2]). This is configured by the Clock Source bit (CLKSRC) in the LUT n
Control A register (CCL.LUTnCTRLA).
When the even LUT (LUT0) is disabled, the latch is asynchronously cleared, during which the flip-flop
Reset signal (R) is kept enabled for one clock cycle. In all other cases, the flip-flop output (OUT) is
refreshed on the rising edge of the clock, as shown in the respective Characteristics tables.
Gated D Flip-Flop (DFF)
The D-input is driven by the even LUT output (LUT0), and the G-input is driven by the odd LUT output
(LUT1).
Figure 28-7. D Flip-Flop
even LUT
CLK_MUX_OUT
odd LUT
Table 28-3. DFF Characteristics
R
G
D
OUT
1
X
X
Clear
0
1
1
Set
0
Clear
X
Hold state (no change)
0
JK Flip-Flop (JK)
The J-input is driven by the even LUT output (LUT0), and the K-input is driven by the odd LUT output
(LUT1).
Figure 28-8. JK Flip-Flop
even LUT
CLK_MUX_OUT
odd LUT
Table 28-4. JK Characteristics
R
J
K
OUT
1
X
X
Clear
0
0
0
Hold state (no change)
0
0
1
Clear
0
1
0
Set
0
1
1
Toggle
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 444
ATtiny1616/3216
CCL - Configurable Custom Logic
Gated D-Latch (DLATCH)
The D-input is driven by the even LUT output (LUT0), and the G-input is driven by the odd LUT output
(LUT1).
Figure 28-9. D-Latch
even LUT
D
odd LUT
G
Q
OUT
Table 28-5. D-Latch Characteristics
G
D
OUT
0
X
Hold state (no change)
1
0
Clear
1
1
Set
RS-Latch (RS)
The S-input is driven by the even LUT output (LUT0), and the R-input is driven by the odd LUT output
(LUT1).
Figure 28-10. RS-Latch
even LUT
S
odd LUT
R
Q
OUT
Table 28-6. RS-Latch Characteristics
S
R
OUT
0
0
Hold state (no change)
0
1
Clear
1
0
Set
1
1
Forbidden state
28.3.2.7 Clock Source Settings
The Filter, Edge Detector, and Sequential logic are by default clocked by the system clock (CLK_PER). It
is also possible to use the LUT input 2 (IN[2]) to clock these blocks (CLK_MUX_OUT in Figure 28-11).
This is configured by writing the Clock Source bit (CLKSRC) in the LUT Control A register
(CCL.LUTnCTRLA) to '1'.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 445
ATtiny1616/3216
CCL - Configurable Custom Logic
Figure 28-11. Clock Source Settings
Edge
Detector
IN[2]
Filter
CLK_MUX_OUT
CLK_CCL
CLKSRC
LUT0
Edge
Detector
IN[2]
Sequential
logic
Filter
CLK_MUX_OUT
CLK_CCL
CLKSRC
LUT1
When the Clock Source bit (CLKSRC) is '1', IN[2] is used to clock the corresponding Filter and Edge
Detector (CLK_MUX_OUT). The Sequential logic is clocked by CLK_MUX_OUT of the even LUT in the
pair. When CLKSRC bit is '1', IN[2] is treated as MASKed (low) in the TRUTH table.
The CCL peripheral must be disabled while changing the clock source to avoid undetermined outputs
from the peripheral.
28.3.3
Events
The CCL can generate the following output events:
• LUTnOUT: Look-Up Table Output Value
The CCL can take the following actions on an input event:
• INx: The event is used as input for the TRUTH table
Related Links
14. EVSYS - Event System
28.3.4
Sleep Mode Operation
Writing the Run In Standby bit (RUNSTDBY) in the Control A register (CCL.CTRLA) to '1' will allow the
system clock to be enabled in Standby Sleep mode.
If RUNSTDBY is '0' the system clock will be disabled in Standby Sleep mode. If the Filter, Edge Detector,
or Sequential logic is enabled, the LUT output will be forced to '0' in Standby Sleep mode. In Idle sleep
mode, the TRUTH table decoder will continue operation and the LUT output will be refreshed accordingly,
regardless of the RUNSTDBY bit.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 446
ATtiny1616/3216
CCL - Configurable Custom Logic
If the Clock Source bit (CLKSRC) in the LUT n Control A register (CCL.LUTnCTRLA) is written to '1', the
LUT input 2 (IN[2]) will always clock the Filter, Edge Detector, and Sequential block. The availability of the
IN[2] clock in sleep modes will depend on the sleep settings of the peripheral employed.
28.3.5
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 447
ATtiny1616/3216
CCL - Configurable Custom Logic
28.4
Register Summary - CCL
Offset
Name
Bit Pos.
0x00
0x01
0x02
...
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
CTRLA
SEQCTRL0
7:0
7:0
28.5
RUNSTDBY
ENABLE
SEQSEL[3:0]
Reserved
LUT0CTRLA
LUT0CTRLB
LUT0CTRLC
TRUTH0
LUT1CTRLA
LUT1CTRLB
LUT1CTRLC
TRUTH1
7:0
7:0
7:0
7:0
7:0
7:0
7:0
7:0
EDGEDET
EDGEDET
CLKSRC
INSEL1[3:0]
FILTSEL[1:0]
CLKSRC
INSEL1[3:0]
FILTSEL[1:0]
OUTEN
ENABLE
INSEL0[3:0]
INSEL2[3:0]
TRUTH[7:0]
OUTEN
ENABLE
INSEL0[3:0]
INSEL2[3:0]
TRUTH[7:0]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 448
ATtiny1616/3216
CCL - Configurable Custom Logic
28.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLA
0x00
0x00
-
6
5
4
3
2
1
0
RUNSTDBY
ENABLE
R/W
R/W
0
0
Bit 6 – RUNSTDBY Run in Standby
This bit indicates if the peripheral clock (CLK_PER) is kept running in Standby Sleep mode. The setting is
ignored for configurations where the CLK_PER is not required.
Value
Description
0
System clock is not required in Standby Sleep mode
1
System clock is required in Standby Sleep mode
Bit 0 – ENABLE Enable
Value
Description
0
The peripheral is disabled
1
The peripheral is enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 449
ATtiny1616/3216
CCL - Configurable Custom Logic
28.5.2
Sequential Control 0
Name:
Offset:
Reset:
Property:
Bit
7
SEQCTRL0
0x01 [ID-00000485]
0x00
Enable-Protected
6
5
4
3
2
1
0
R/W
R/W
0
R/W
R/W
0
0
0
SEQSEL[3:0]
Access
Reset
Bits 3:0 – SEQSEL[3:0] Sequential Selection
These bits select the sequential configuration.
Value
Name
Description
0x0
DISABLE
Sequential logic is disabled
0x1
DFF
D flip-flop
0x2
JK
JK flip-flop
0x3
LATCH
D latch
0x4
RS
RS latch
Other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 450
ATtiny1616/3216
CCL - Configurable Custom Logic
28.5.3
LUT n Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
LUTCTRLA
0x05 + n*0x04 [n=0..1]
0x00
Enable-Protected
7
6
5
4
EDGEDET
CLKSRC
OUTEN
ENABLE
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
FILTSEL[1:0]
3
2
1
0
Bit 7 – EDGEDET Edge Detection
Value
Description
0
Edge detector is disabled
1
Edge detector is enabled
Bit 6 – CLKSRC Clock Source Selection
This bit selects whether the peripheral clock (CLK_PER) or any input present on input line 2 (IN[2]) is
used as clock (CLK_MUX_OUT) for an LUT.
The CLK_MUX_OUT of the even LUT is used for clocking the Sequential block of an LUT pair.
Value
Description
0
CLK_PER is clocking the LUT
1
IN[2] is clocking the LUT
Bits 5:4 – FILTSEL[1:0] Filter Selection
These bits select the LUT output filter options:
Value
Name
Description
0x0
DISABLE
Filter disabled
0x1
SYNCH
Synchronizer enabled
0x2
FILTER
Filter enabled
0x3
Reserved
Bit 3 – OUTEN Output Enable
This bit enables the LUT output to the LUTnOUT pin. When written to '1', the pin configuration of the
PORT I/O Controller is overridden.
Value
Description
0
Output to pin disabled
1
Output to pin enabled
Bit 0 – ENABLE LUT Enable
Value
Description
0
The LUT is disabled
1
The LUT is enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 451
ATtiny1616/3216
CCL - Configurable Custom Logic
28.5.4
LUT n Control B
Name:
Offset:
Reset:
Property:
LUTCTRLB
0x06 + n*0x04 [n=0..1]
0x00
Enable-Protected
SPI connections to the CCL work only in master SPI mode.
USART connections to the CCL work only in asynchronous/synchronous USART Master mode.
Bit
7
6
5
4
3
2
R/W
0
1
0
R/W
R/W
R/W
R/W
R/W
0
0
0
0
R/W
R/W
0
0
0
INSEL1[3:0]
Access
Reset
INSEL0[3:0]
Bits 7:4 – INSEL1[3:0] LUT n Input 1 Source Selection
These bits select the source for input 1 of LUT n:
Value
Name
Description
0x0
MASK
Masked input
0x1
FEEDBACK
Feedback input
0x2
LINK
Linked other LUT as input source
0x3
EVENT0
Event input source 0
0x4
EVENT1
Event input source 1
0x5
IO
I/O pin LUTn-IN1 input source
0x6
AC0
AC0 OUT input source
0x7
TCB0
TCB WO input source
0x8
TCA0
TCA WO1 input source
0x9
TCD0
TCD WOB input source
0xA
USART0
USART TXD input source
0xB
SPI0
SPI MOSI input source
0xC
AC1
AC1 OUT input source
0xD
TCB1
TCB 1 W0 input source
0xE
AC2
AC2 OUT input source
Bits 3:0 – INSEL0[3:0] LUT n Input 0 Source Selection
These bits select the source for input 0 of LUT n:
Value
Name
Description
0x0
MASK
Masked input
0x1
FEEDBACK
Feedback input
0x2
LINK
Linked other LUT as input source
0x3
EVENT0
Event input source 0
0x4
EVENT1
Event input source 1
0x5
IO
I/O pin LUTn-IN0 input source
0x6
AC0
AC0 OUT input source
0x7
TCB0
TCB WO input source
0x8
TCA0
TCA WO0 input source
0x9
TCD0
TCD WOAn input source
0xA
USART0
USART XCK input source
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 452
ATtiny1616/3216
CCL - Configurable Custom Logic
Value
0xB
0xC
0xD
0xE
Other
Name
SPI0
AC1
TCB1
AC2
-
© 2019 Microchip Technology Inc.
Description
SPI SCK input source
AC1 OUT input source
TCB 1 W0 input source
AC2 OUT input source
Reserved
Preliminary Datasheet
40001997C-page 453
ATtiny1616/3216
CCL - Configurable Custom Logic
28.5.5
LUT n Control C
Name:
Offset:
Reset:
Property:
Bit
7
LUTCTRLC
0x07 + n*0x04 [n=0..1]
0x00
Enable-Protected
6
5
4
3
2
1
0
R/W
R/W
0
R/W
R/W
0
0
0
INSEL2[3:0]
Access
Reset
Bits 3:0 – INSEL2[3:0] LUT n Input 2 Source Selection
These bits select the source for input 2 of LUT n:
Value
Name
Description
0x0
MASK
Masked input
0x1
FEEDBACK
Feedback input
0x2
LINK
Linked other LUT as input source
0x3
EVENT0
Event input source 0
0x4
EVENT1
Event input source 1
0x5
IO
I/O pin LUTn-IN2 input source
0x6
AC0
AC0 OUT input source
0x7
TCB0
TCB WO input source
0x8
TCA0
TCA WO2 input source
0x9
TCD0
TCD WOA input source
0xA
Reserved
0xB
SPI0
SPI MISO input source
other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 454
ATtiny1616/3216
CCL - Configurable Custom Logic
28.5.6
TRUTHn
Name:
Offset:
Reset:
Property:
Bit
TRUTH
0x08 + n*0x04 [n=0..1]
0x00
Enable-Protected
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
TRUTH[7:0]
Access
Reset
Bits 7:0 – TRUTH[7:0] Truth Table
These bits define the value of truth logic as a function of inputs IN[2:0].
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 455
ATtiny1616/3216
AC - Analog Comparator
29.
AC - Analog Comparator
29.1
Features
•
•
•
•
•
•
•
•
•
29.2
Three Instances of the AC Controller, AC0, AC1, and AC2
50 ns Response Time for Supply Voltage Above 2.7V
Zero-Cross Detection
Selectable Hysteresis:
– None
– 10 mV
– 25 mV
– 50 mV
Analog Comparator Output Available on Pin
Comparator Output Inversion Available
Flexible Input Selection:
– Four Positive pins
– Two Negative pins
– Output from the DAC
– Internal reference voltage
Interrupt Generation On:
– Rising edge
– Falling edge
– Both edges
Event Generation:
– Comparator output
Overview
The Analog Comparator (AC) compares the voltage levels on two inputs and gives a digital output based
on this comparison. The AC can be configured to generate interrupt requests and/or events upon several
different combinations of input change.
The dynamic behavior of the AC can be adjusted by a hysteresis feature. The hysteresis can be
customized to optimize the operation for each application.
The input selection includes analog port pins, DAC output, and internal references. The analog
comparator output state can also be output on a pin for use by external devices.
The AC has one positive input and one negative input. The positive input source is one of a selection of
four analog input pins. The negative inputs are chosen either from analog input pins or from internal
inputs, such as an internal voltage reference.
The digital output from the comparator is '1' when the difference between the positive and the negative
input voltage is positive and '0' otherwise.
This device provides three instances of the AC controller, AC0, AC1, and AC2.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 456
ATtiny1616/3216
AC - Analog Comparator
29.2.1
Block Diagram
Figure 29-1. Analog Comparator
AC Controller
AINP0
MUXCTRLA
:
Invert
+
AINPn
Controller
Logic
AC
AINN0
OUT
-
:
AINNn
Hysteresis
Enable
VREF
Event
System
CTRLA
DAC
Note: Refer to 29.2.2 Signal Description for the number of AINN and AINP.
29.2.2
29.2.3
Signal Description
Signal
Description
Type
AINN0
Negative Input 0
Analog
AINN1
Negative Input 1
Analog
AINP0
Positive Input 0
Analog
AINP1
Positive Input 1
Analog
AINP2
Positive Input 2
Analog
AINP3
Positive Input 3
Analog
OUT
Comparator Output for AC
Digital
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 29-1. AC System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
Yes
UPDI
29.2.3.1 Clocks
This peripheral depends on the peripheral clock.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 457
ATtiny1616/3216
AC - Analog Comparator
29.2.3.2 I/O Lines and Connections
I/O pins AINN0-AINN1 and AINP0- AINP3 are all analog inputs to the AC.
For correct operation, the pins must be configured in the port and port multiplexing peripherals.
It is recommended to disable the GPIO input when using the AC.
29.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
29.2.3.4 Events
The events of this peripheral are connected to the Event System.
29.2.3.5 Debug Operation
This peripheral is unaffected by entering Debug mode.
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
29.3
Functional Description
29.3.1
Initialization
For basic operation, follow these steps:
• Configure the desired input pins in the port peripheral
• Select the positive and negative input sources by writing the Positive and Negative Input MUX
Selection bit fields (MUXPOS and MUXNEG) in the MUX Control A register (AC.MUXCTRLA)
• Optional: Enable the output to pin by writing a '1' to the Output Pad Enable bit (OUTEN) in the
Control A register (AC.CTRLA)
• Enable the AC by writing a '1' to the ENABLE bit in AC.CTRLA
During the start-up time after enabling the AC, the output of the AC may be invalid.
The start-up time of the AC by itself is at most 2.5 µs. If an internal reference is used, the reference startup time is normally longer than the AC start-up time. The VREF start-up time is 60 µs at most.
29.3.2
Operation
29.3.2.1 Input Hysteresis
Applying an input hysteresis helps to prevent constant toggling of the output when the noise-afflicted input
signals are close to each other.
The input hysteresis can either be disabled or have one of three levels. The hysteresis is configured by
writing to the Hysteresis Mode Select bit field (HYSMODE) in the Control A register (ACn.CTRLA).
29.3.2.2 Input Sources
The AC has one positive and one negative input. The inputs can be pins and internal sources, such as a
voltage reference.
Each input is selected by writing to the Positive and Negative Input MUX Selection bit field (MUXPOS and
MUXNEG) in the MUX Control A register (AC.MUXTRLA).
29.3.2.2.1 Pin Inputs
The following Analog input pins on the port can be selected as input to the analog comparator:
• AINN0
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 458
ATtiny1616/3216
AC - Analog Comparator
•
•
•
•
•
AINN1
AINP0
AINP1
AINP2
AINP3
29.3.2.2.2 Internal Inputs
Two internal inputs are available for the analog comparator:
• Output from the DAC
• DAC and AC voltage reference
29.3.2.3 Low-Power Mode
For power sensitive applications, the AC provides a Low-Power mode with reduced power consumption
and increased propagation delay.
This mode is enabled by writing a '1' to the Low-Power Mode bit (LPMODE) in the Control A register
(AC.CTRLA).
29.3.3
Events
The AC will generate the following event automatically when the AC is enabled:
• The digital output from the AC (OUT in the block diagram) is available as an Event System source.
The events from the AC are asynchronous to any clocks in the device.
The AC has no event inputs.
29.3.4
Interrupts
Table 29-2. Available Interrupt Vectors and Sources
Offset Name
0x00
Vector Description
Conditions
COMP0 Analog comparator interrupt AC output is toggling as configured by INTMODE in
AC.CTRLA
When an interrupt condition occurs, the corresponding interrupt flag is set in the STATUS register
(AC.STATUS).
An interrupt source is enabled or disabled by writing to the corresponding bit in the peripheral's Interrupt
Control register (AC.INTCTRL).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the AC.STATUS
register description for details on how to clear interrupt flags.
29.3.5
Sleep Mode Operation
In Idle Sleep mode, the AC will continue to operate as normal.
In Standby Sleep mode, the AC is disabled by default. If the Run in Standby Sleep mode bit
(RUNSTDBY) in the Control A register (AC.CTRLA) is written to '1', the AC will continue to operate, but
the Status register will not be updated, and no Interrupts are generated if no other modules request the
CLK_PER, but events and the pad output will be updated.
In Power-Down Sleep mode, the AC and the output to the pad are disabled.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 459
ATtiny1616/3216
AC - Analog Comparator
29.3.6
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 460
ATtiny1616/3216
AC - Analog Comparator
29.4
Register Summary - AC
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
...
0x05
0x06
0x07
CTRLA
Reserved
MUXCTRLA
7:0
RUNSTDBY
7:0
INVERT
29.5
OUTEN
INTMODE[1:0]
LPMODE
MUXPOS[1:0]
HYSMODE[1:0]
ENABLE
MUXNEG[1:0]
Reserved
INTCTRL
STATUS
7:0
7:0
STATE
CMP
CMP
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 461
ATtiny1616/3216
AC - Analog Comparator
29.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
CTRLA
0x00
0x00
-
7
6
5
4
RUNSTDBY
OUTEN
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
INTMODE[1:0]
3
LPMODE
2
1
HYSMODE[1:0]
0
ENABLE
Bit 7 – RUNSTDBY Run in Standby Mode
Writing a '1' to this bit allows the AC to continue operation in Standby Sleep mode. Since the clock is
stopped, interrupts and status flags are not updated.
Value
Description
0
In Standby Sleep mode, the peripheral is halted
1
In Standby Sleep mode, the peripheral continues operation
Bit 6 – OUTEN Analog Comparator Output Pad Enable
Writing this bit to '1' makes the OUT signal available on the pin.
Bits 5:4 – INTMODE[1:0] Interrupt Modes
Writing to these bits selects what edges of the AC output triggers an interrupt request.
Value
Name
Description
0x0
BOTHEDGE
Both negative and positive edge
0x1
Reserved
0x2
NEGEDGE
Negative edge
0x3
POSEDGE
Positive edge
Bit 3 – LPMODE Low-Power Mode
Writing a '1' to this bit reduces the current through the comparator. This reduces the power consumption
but increases the reaction time of the AC.
Value
Description
0
Low-Power mode disabled
1
Low-Power mode enabled
Bits 2:1 – HYSMODE[1:0] Hysteresis Mode Select
Writing these bits selects the Hysteresis mode for the AC input.
Value
Name
Description
0x0
OFF
OFF
0x1
10
±10 mV
0x2
25
±25 mV
0x3
50
±50 mV
Bit 0 – ENABLE Enable AC
Writing this bit to '1' enables the AC.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 462
ATtiny1616/3216
AC - Analog Comparator
29.5.2
MUX Control A
Name:
Offset:
Reset:
Property:
MUXCTRLA
0x02
0x00
-
AC.MUXCTRLA controls the analog comparator MUXes.
Bit
7
6
5
4
INVERT
Access
Reset
3
2
1
MUXPOS[1:0]
0
MUXNEG[1:0]
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
Bit 7 – INVERT Invert AC Output
Writing a ‘1’ to this bit enables inversion of the output of the AC. This effectively inverts the input to all the
peripherals connected to the signal and affects the internal status signals.
Bits 4:3 – MUXPOS[1:0] Positive Input MUX Selection
Writing to this bit field selects the input signal to the positive input of the AC.
Value
Name
Description
0x0
AINP0
Positive Pin 0
0x1
AINP1
Positive Pin 1
0x2
AINP2
Positive Pin 2
0x3
AINP3
Positive Pin 3
Bits 1:0 – MUXNEG[1:0] Negative Input MUX Selection
Writing to this bit field selects the input signal to the negative input of the AC.
Value
Name Description
0x0
AINN0 Negative Pin 0
0x1
AINN1 Negative Pin 1
0x2
VREF Voltage Reference
0x3
DAC DAC output Instance n of the AC will use instance n of the DAC: for example AC0
will use DAC0 and AC1 will use DAC1.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 463
ATtiny1616/3216
AC - Analog Comparator
29.5.3
Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
INTCTRL
0x06
0x00
-
6
5
4
3
2
1
0
CMP
Access
R/W
Reset
0
Bit 0 – CMP Analog Comparator Interrupt Enable
Writing this bit to '1' enables analog comparator interrupt.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 464
ATtiny1616/3216
AC - Analog Comparator
29.5.4
Status
Name:
Offset:
Reset:
Property:
Bit
7
STATUS
0x07
0x00
-
6
5
4
3
2
1
0
STATE
CMP
Access
R
R/W
Reset
0
0
Bit 4 – STATE Analog Comparator State
This shows the current status of the OUT signal from the AC. This will have a synchronizer delay to get
updated in the I/O register (three cycles).
Bit 0 – CMP Analog Comparator Interrupt Flag
This is the interrupt flag for AC. Writing a '1' to this bit will clear the Interrupt Flag.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 465
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.
ADC - Analog-to-Digital Converter
30.1
Features
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
30.2
10-Bit Resolution
±2 LSB Absolute Accuracy
6.5 - 260 μs Conversion Time
Up to 115 ksps at 10-Bit Resolution (150 ksps at 8-bit)
Up to Twelve Multiplexed Single-ended Input Channels
Temperature Sensor Input Channel
0V to VDD ADC Input Voltage Range
Multiple Internal ADC Reference Voltages Between 0.55V and VDD
External Reference Input VVREFA
Free-running or Single Conversion mode
Interrupt Available on ADC Conversion Complete
Optional Event Triggered Conversion
Optional Interrupt on Conversion Results
Compare Function for Accurate Monitoring or User-Defined Thresholds (Window Comparator mode)
Accumulation up to 64 Samples per Conversion
Overview
The Analog-to-Digital Converter (ADC) peripheral features a 10-bit Successive Approximation ADC
(SAR), with a sampling rate up to 115 ksps at 10-bit resolution (150 ksps at 8-bit). The ADC is connected
to a 12-channel analog multiplexer, which allows twelve single-ended voltage inputs. The single-ended
voltage inputs refer to 0V (GND). The ADC input channel can either be internal (e.g. a voltage reference)
or external through the analog input pins.
An ADC conversion can be started by software or by using the Event System (EVSYS) to route an event
from other peripherals, making it possible to do a periodic sampling of input signals, trigger an ADC
conversion on a special condition, or trigger an ADC conversion in Standby Sleep mode. A window
compare feature is available for monitoring the input signal and can be configured to only trigger an
interrupt on user-defined thresholds for under, over, inside, or outside a window, with minimum software
intervention required.
The ADC input signal is fed through a sample-and-hold circuit that ensures that the input voltage to the
ADC is held at a constant level during sampling.
The ADC supports sampling in bursts where a configurable number of conversion results are
accumulated into a single ADC result (Sample Accumulation). Further, a sample delay can be configured
to tune the ADC sampling frequency associated with a single burst. This is to tune the sampling
frequency away from any harmonic noise aliased with the ADC sampling frequency (within the burst) from
the sampled signal. An automatic sampling delay variation feature can be used to randomize this delay to
slightly change the time between samples.
Selectable voltage references from the internal Voltage Reference (VREF) peripheral, VDD supply
voltage, or external VREF pin (VREFA).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 466
ATtiny1616/3216
ADC - Analog-to-Digital Converter
This device has two instances of the ADC; ADC0 and ADC1.
When the Peripheral Touch Controller (PTC) is enabled, ADC0 is fully controlled by the PTC peripheral.
Block Diagram
Figure 30-1. Block Diagram
..
.
ADC
DAC
"enable"
VREF
TEMPREF
RES
"accumulate"
AINn
VREF
"convert"
AIN0
AIN1
Internal reference
VREFA
VDD
"sample"
30.2.1
>
<
WCOMP
(IRQ)
Control Logic
MUXPOS
CTRLA
EVCTRL
COMMAND
RESRDY
(IRQ)
WINLT
WINHT
The analog input channel is selected by writing to the MUXPOS bits in the MUXPOS register
(ADC.MUXPOS). Any of the ADC input pins, GND, or temperature sensor, can be selected as singleended input to the ADC. The ADC is enabled by writing a ‘1’ to the ADC ENABLE bit in the Control A
register (ADC.CTRLA). Voltage reference and input channel selections will not go into effect before the
ADC is enabled. The ADC does not consume power when the ENABLE bit in ADC.CTRLA is ‘0’.
The ADC generates a 10-bit result that can be read from the Result Register (ADC.RES). The result is
presented right adjusted.
30.2.2
Signal Description
Pin Name
Type
Description
AIN[11:0]
Analog input
Analog input to be converted
VREFA
Analog input
Analog reference input
Related Links
2.1 Configuration Summary
5. I/O Multiplexing and Considerations
30.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 467
ATtiny1616/3216
ADC - Analog-to-Digital Converter
Table 30-1. ADC System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
Yes
CPUINT
Events
Yes
EVSYS
Debug
Yes
UPDI
30.2.3.1 Clocks
The ADC uses the peripheral clock CLK_PER and has an internal prescaler to generate the ADC clock
source CLK_ADC.
Related Links
10. CLKCTRL - Clock Controller
30.3.2.2 Clock Generation
30.2.3.2 I/O Lines and Connections
The I/O pins (AINx and VREF) are configured by the port - I/O Pin Controller.
The digital input buffer should be disabled on the pin used as input for the ADC to disconnect the digital
domain from the analog domain to obtain the best possible ADC results. This is configured by the port I/O Pin Controller.
Related Links
16. PORT - I/O Pin Configuration
30.2.3.3 Interrupts
Using the interrupts of this peripheral requires the interrupt controller to be configured first.
Related Links
13. CPUINT - CPU Interrupt Controller
8.7.3 SREG
30.3.4 Interrupts
30.2.3.4 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
30.2.3.5 Debug Operation
When run-time debugging, this peripheral will continue normal operation. Halting the CPU in Debugging
mode will halt normal operation of the peripheral.
This peripheral can be forced to operate with halted CPU by writing a '1' to the Debug Run bit (DBGRUN)
in the Debug Control register of the peripheral (peripheral.DBGCTRL).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 468
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.2.4
Definitions
An ideal n-bit single-ended ADC converts a voltage linearly between GND and VREF in 2n steps (LSb).
The lowest code is read as 0, and the highest code is read as 2n-1. Several parameters describe the
deviation from the ideal behavior:
Offset Error
The deviation of the first transition (0x000 to 0x001) compared to the ideal
transition (at 0.5 LSb). Ideal value: 0 LSb.
Figure 30-2. Offset Error
Output Code
Ideal ADC
Actual ADC
Offset
Error
Gain Error
VREF Input Voltage
After adjusting for offset, the gain error is found as the deviation of the last
transition (0x3FE to 0x3FF) compared to the ideal transition (at 1.5 LSb below
maximum). Ideal value: 0 LSb.
Figure 30-3. Gain Error
Gain
Error
Output Code
Ideal ADC
Actual ADC
VREF
Integral NonLinearity (INL)
Input Voltage
After adjusting for offset and gain error, the INL is the maximum deviation of an
actual transition compared to an ideal transition for any code. Ideal value: 0 LSb.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 469
ATtiny1616/3216
ADC - Analog-to-Digital Converter
Figure 30-4. Integral Non-Linearity
Output Code
INL
Ideal ADC
Actual ADC
VREF
Differential NonLinearity (DNL)
Input Voltage
The maximum deviation of the actual code width (the interval between two
adjacent transitions) from the ideal code width (1 LSb). Ideal value: 0 LSb.
Figure 30-5. Differential Non-Linearity
Output Code
0x3FF
1 LSb
DNL
0x000
0
VREF
Input Voltage
Quantization Error Due to the quantization of the input voltage into a finite number of codes, a range
of input voltages (1 LSb wide) will code to the same value. Always ±0.5 LSb.
Absolute
Accuracy
The maximum deviation of an actual (unadjusted) transition compared to an ideal
transition for any code. This is the compound effect of all aforementioned errors.
Ideal value: ±0.5 LSb.
30.3
Functional Description
30.3.1
Initialization
The following steps are recommended in order to initialize ADC operation:
1. Configure the resolution by writing to the Resolution Selection bit (RESSEL) in the Control A
register (ADC.CTRLA).
2. Optional: Enable the Free-Running mode by writing a '1' to the Free-Running bit (FREERUN) in
ADC.CTRLA.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 470
ATtiny1616/3216
ADC - Analog-to-Digital Converter
3.
4.
5.
6.
7.
8.
Optional: Configure the number of samples to be accumulated per conversion by writing the
Sample Accumulation Number Select bits (SAMPNUM) in the Control B register (ADC.CTRLB).
Configure a voltage reference by writing to the Reference Selection bit (REFSEL) in the Control C
register (ADC.CTRLC). Default is the internal voltage reference of the device (VREF, as configured
there).
Configure the CLK_ADC by writing to the Prescaler bit field (PRESC) in the Control C register
(ADC.CTRLC).
Configure an input by writing to the MUXPOS bit field in the MUXPOS register (ADC.MUXPOS).
Optional: Enable Start Event input by writing a '1' to the Start Event Input bit (STARTEI) in the
Event Control register (ADC.EVCTRL). Configure the Event System accordingly.
Enable the ADC by writing a '1' to the ENABLE bit in ADC.CTRLA.
Following these steps will initialize the ADC for basic measurements, which can be triggered by an event
(if configured) or by writing a '1' to the Start Conversion bit (STCONV) in the Command register
(ADC.COMMAND).
30.3.2
Operation
30.3.2.1 Starting a Conversion
Once the input channel is selected by writing to the MUXPOS register (ADCn.MUXPOS), a conversion is
triggered by writing a '1' to the ADC Start Conversion bit (STCONV) in the Command register
(ADCn.COMMAND). This bit is '1' as long as the conversion is in progress. In Single Conversion mode,
STCONV is cleared by hardware when the conversion is completed.
If a different input channel is selected while a conversion is in progress, the ADC will finish the current
conversion before changing the channel.
Depending on the accumulator setting, the conversion result is from a single sensing operation, or from a
sequence of accumulated samples. Once the triggered operation is finished, the Result Ready flag
(RESRDY) in the Interrupt Flag register (ADCn.INTFLAG) is set. The corresponding interrupt vector is
executed if the Result Ready Interrupt Enable bit (RESRDY) in the Interrupt Control register
(ADCn.INTCTRL) is '1' and the Global Interrupt Enable bit is '1'.
A single conversion can be started by writing a '1' to the STCONV bit in ADCn.COMMAND. The STCONV
bit can be used to determine if a conversion is in progress. The STCONV bit will be set during a
conversion and cleared once the conversion is complete.
The RESRDY interrupt flag in ADCn.INTFLAG will be set even if the specific interrupt is disabled,
allowing software to check for finished conversion by polling the flag. A conversion can thus be triggered
without causing an interrupt.
Alternatively, a conversion can be triggered by an event. This is enabled by writing a '1' to the Start Event
Input bit (STARTEI) in the Event Control register (ADCn.EVCTRL). Any incoming event routed to the ADC
through the Event System (EVSYS) will trigger an ADC conversion. This provides a method to start
conversions at predictable intervals or at specific conditions.
The event trigger input is edge sensitive. When an event occurs, STCONV in ADCn.COMMAND is set.
STCONV will be cleared when the conversion is complete.
In Free-Running mode, the first conversion is started by writing the STCONV bit to '1' in
ADCn.COMMAND. A new conversion cycle is started immediately after the previous conversion cycle has
completed. A conversion complete will set the RESRDY flag in ADCn.INTFLAGS.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 471
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.3.2.2 Clock Generation
Figure 30-6. ADC Prescaler
ENABLE
"START"
Reset
8-bit PRESCALER
CTRLC
CLK_PER/256
CLK_PER/128
CLK_PER/64
CLK_PER/32
CLK_PER/16
CLK_PER/8
CLK_PER/4
CLK_PER/2
CLK_PER
PRESC
ADC clock source
(CLK_ADC)
The ADC requires an input clock frequency between 50 kHz and 1.5 MHz for maximum resolution. If a
lower resolution than 10 bits is selected, the input clock frequency to the ADC can be higher than 1.5
MHz to get a higher sample rate.
The ADC module contains a prescaler which generates the ADC clock (CLK_ADC) from any CPU clock
(CLK_PER) above 100 kHz. The prescaling is selected by writing to the Prescaler bits (PRESC) in the
Control C register (ADCn.CTRLC). The prescaler starts counting from the moment the ADC is switched
on by writing a ’1’ to the ENABLE bit in ADCn.CTRLA. The prescaler keeps running as long as the
ENABLE bit is '1'. The prescaler counter is reset to zero when the ENABLE bit is '0'.
When initiating a conversion by writing a ’1’ to the Start Conversion bit (STCONV) in the Command
register (ADCn.COMMAND) or from an event, the conversion starts at the following rising edge of the
CLK_ADC clock cycle. The prescaler is kept reset as long as there is no ongoing conversion. This
assures a fixed delay from the trigger to the actual start of a conversion in CLK_PER cycles as:
PRESCfactor
+2
2
Figure 30-7. Start Conversion and Clock Generation
StartDelay =
CLK_PER
STCONV
CLK_PER/2
CLK_PER/4
CLK_PER/8
30.3.2.3 Conversion Timing
A normal conversion takes 13 CLK_ADC cycles. The actual sample-and-hold takes place two CLK_ADC
cycles after the start of a conversion. Start of conversion is initiated by writing a ‘1’ to the STCONV bit in
ADC.COMMAND. When a conversion is complete, the result is available in the Result register
(ADC.RES), and the Result Ready interrupt flag is set (RESRDY in ADC.INTFLAG). The interrupt flag will
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 472
ATtiny1616/3216
ADC - Analog-to-Digital Converter
be cleared when the result is read from the Result registers, or by writing a ‘1’ to the RESRDY bit in
ADC.INTFLAG.
Figure 30-8. ADC Timing Diagram - Single Conversion
1
2
3
4
5
6
7
8
9
10
11
12
13
CLK_ADC
ENABLE
STCONV
RESRDY
RES
Result
sample
Both sampling time and sampling length can be adjusted using the Sample Delay bit field in Control D
(ADC.CTRLD) and sampling the Sample Length bit field in the Sample Control register
(ADC.SAMPCTRL). Both of these control the ADC sampling time in a number of CLK_ADC cycles. This
allows sampling high-impedance sources without relaxing conversion speed. See the register description
for further information. Total sampling time is given by:
SampleTime =
2 + SAMPDLY + SAMPLEN
�CLK_ADC
Figure 30-9. ADC Timing Diagram - Single Conversion With Delays
1
2
3
4
5
6
7
8
9
10
11
12
13
CLK_ADC
ENABLE
STCONV
RES
Result
INITDLY
(0 – 256
CLK_ADC cycles)
SAMPDLY
(0 – 15
CLK_ADC cycles)
SAMPLEN
(0 – 31
CLK_ADC cycles)
In Free-Running mode, a new conversion will be started immediately after the conversion completes,
while the STCONV bit is ‘1’. The sampling rate RS in free-running mode is calculated by:
�S =
�CLK_ADC
13 + SAMPDLY + SAMPLEN
Figure 30-10. ADC Timing Diagram - Free-Running Conversion
1
2
3
4
5
6
7
8
9
10
11
12
13
1
2
CLK_ADC
ENABLE
STCONV
RESRDY
RES
Result
sample
© 2019 Microchip Technology Inc.
sample
Preliminary Datasheet
40001997C-page 473
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.3.2.4 Changing Channel or Reference Selection
The MUXPOS bits in the ADCn.MUXPOS register and the REFSEL bits in the ADCn.CTRLC register are
buffered through a temporary register to which the CPU has random access. This ensures that the
channel and reference selections only take place at a safe point during the conversion. The channel and
reference selections are continuously updated until a conversion is started.
Once the conversion starts, the channel and reference selections are locked to ensure sufficient sampling
time for the ADC. Continuous updating resumes in the last CLK_ADC clock cycle before the conversion
completes (RESRDY in ADCn.INTFLAGS is set). The conversion starts on the following rising CLK_ADC
clock edge after the STCONV bit is written to '1'.
30.3.2.4.1 ADC Input Channels
When changing channel selection, the user should observe the following guidelines to ensure that the
correct channel is selected:
In Single Conversion mode: The channel should be selected before starting the conversion. The channel
selection may be changed one ADC clock cycle after writing '1' to the STCONV bit.
In Free-Running mode: The channel should be selected before starting the first conversion. The channel
selection may be changed one ADC clock cycle after writing '1' to the STCONV bit. Since the next
conversion has already started automatically, the next result will reflect the previous channel selection.
Subsequent conversions will reflect the new channel selection.
The ADC requires a settling time after switching the input channel - refer to the Electrical Characteristics
section for details.
30.3.2.4.2 ADC Voltage Reference
The reference voltage for the ADC (VREF) controls the conversion range of the ADC. Input voltages that
exceed the selected VREF will be converted to the maximum result value of the ADC, for an ideal 10-bit
ADC this is 0x3FF. VREF can be selected by writing the Reference Selection bits (REFSEL) in the Control
C register (ADC.CTRLC) as either VDD, external reference VREFA, or an internal reference from the VREF
peripheral. VDD is connected to the ADC through a passive switch.
When using the external reference voltage VREFA, configure ADCnREFSEL[0:2] in the corresponding
VREF.CTRLn register to the value that is closest, but above the applied reference voltage. For external
references higher than 4.3V, use ADCnREFSEL[0:2] = 0x3.
The internal reference is generated from an internal bandgap reference through an internal amplifier, and
is controlled by the Voltage Reference (VREF) peripheral.
Related Links
18. VREF - Voltage Reference
30.3.2.4.3 Analog Input Circuitry
The analog input circuitry is illustrated in Figure 30-11. An analog source applied to ADCn is subjected to
the pin capacitance and input leakage of that pin (represented by IH and IL), regardless of whether that
channel is selected as input for the ADC. When the channel is selected, the source must drive the S/H
capacitor through the series resistance (combined resistance in the input path).
The ADC is optimized for analog signals with an output impedance of approximately 10 kΩ or less. If such
source is used, the sampling time will be negligible. If a source with higher impedance is used, the
sampling time will depend on how long the source needs to charge the S/H capacitor, which can vary
substantially.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 474
ATtiny1616/3216
ADC - Analog-to-Digital Converter
Figure 30-11. Analog Input Schematic
IIH
ADCn
Rin
Cin
IIL
VDD/2
30.3.2.5 ADC Conversion Result
After the conversion is complete (RESRDY is '1'), the conversion result RES is available in the ADC
Result Register (ADCn.RES). The result for a 10-bit conversion is given as:
1023 × �IN
�REF
where VIN is the voltage on the selected input pin and VREF the selected voltage reference (see
description for REFSEL in ADCn.CTRLC and ADCn.MUXPOS).
RES =
30.3.2.6 Temperature Measurement
The temperature measurement is based on an on-chip temperature sensor. For a temperature
measurement, follow these steps:
1. Configure the internal voltage reference to 1.1V by configuring the VREF peripheral.
2. Select the internal voltage reference by writing the REFSEL bits in ADCn.CTRLC to 0x0.
3. Select the ADC temperature sensor channel by configuring the MUXPOS register
(ADCn.MUXPOS). This enables the temperature sensor.
4. In ADCn.CTRLD select INITDLY ≥ 32 µs × �CLK_ADC
5.
6.
7.
8.
In ADCn.SAMPCTRL select SAMPLEN ≥ 32 µs × �CLK_ADC
In ADCn.CTRLC select SAMPCAP = 1
Acquire the temperature sensor output voltage by starting a conversion.
Process the measurement result as described below.
The measured voltage has a linear relationship to the temperature. Due to process variations, the
temperature sensor output voltage varies between individual devices at the same temperature. The
individual compensation factors are determined during the production test and saved in the Signature
Row:
• SIGROW.TEMPSENSE0 is a gain/slope correction
• SIGROW.TEMPSENSE1 is an offset correction
In order to achieve accurate results, the result of the temperature sensor measurement must be
processed in the application software using factory calibration values. The temperature (in Kelvin) is
calculated by this rule:
Temp = (((RESH > 8
RESH and RESL are the high and low bytes of the Result register (ADCn.RES), and TEMPSENSEn are
the respective values from the Signature row.
It is recommended to follow these steps in user code:
int8_t sigrow_offset = SIGROW.TEMPSENSE1;
uint8_t sigrow_gain = SIGROW.TEMPSENSE0;
© 2019 Microchip Technology Inc.
// Read signed value from signature row
// Read unsigned value from signature row
Preliminary Datasheet
40001997C-page 475
ATtiny1616/3216
ADC - Analog-to-Digital Converter
uint16_t adc_reading = 0;
// ADC conversion result with 1.1 V internal reference
uint32_t temp = adc_reading - sigrow_offset;
temp *= sigrow_gain; // Result might overflow 16 bit variable (10bit+8bit)
temp += 0x80;
// Add 1/2 to get correct rounding on division below
temp >>= 8;
// Divide result to get Kelvin
uint16_t temperature_in_K = temp;
Related Links
6.10.2.3 TEMPSENSEn
30.3.2.7 Window Comparator Mode
The ADC can raise the WCOMP flag in the Interrupt and Flag register (ADCn.INTFLAG) and request an
interrupt (WCOMP) when the result of a conversion is above and/or below certain thresholds. The
available modes are:
• The result is under a threshold
• The result is over a threshold
• The result is inside a window (above a lower threshold, but below the upper one)
• The result is outside a window (either under the lower or above the upper threshold)
The thresholds are defined by writing to the Window Comparator Threshold registers (ADCn.WINLT and
ADCn.WINHT). Writing to the Window Comparator mode bit field (WINCM) in the Control E register
(ADCn.CTRLE) selects the conditions when the flag is raised and/or the interrupt is requested.
Assuming the ADC is already configured to run, follow these steps to use the Window Comparator mode:
1. Choose which Window Comparator to use (see the WINCM description in ADCn.CTRLE), and set
the required threshold(s) by writing to ADCn.WINLT and/or ADCn.WINHT.
2. Optional: enable the interrupt request by writing a '1' to the Window Comparator Interrupt Enable bit
(WCOMP) in the Interrupt Control register (ADCn.INTCTRL).
3. Enable the Window Comparator and select a mode by writing a non-zero value to the WINCM bit
field in ADCn.CTRLE.
When accumulating multiple samples, the comparison between the result and the threshold will happen
after the last sample was acquired. Consequently, the flag is raised only once, after taking the last sample
of the accumulation.
30.3.2.8 PTC Operation
When the Peripheral Touch Controller (PTC) is enabled, it takes complete control of ADC0.
When the PTC is disabled, ADC0 is available as a normal ADC.
Refer to the QTouch Library user guide for more details on using the PTC.
Related Links
32.6 Functional Description
30.3.3
Events
An ADC conversion can be triggered automatically by an event input if the Start Event Input bit
(STARTEI) in the Event Control register (ADCn.EVCTRL) is written to '1'.
See also the description of the Asynchronous User Channel n Input Selection in the Event System
(EVSYS.ASYNCUSERn).
Related Links
14.5.5 ASYNCUSER
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 476
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.3.4
Interrupts
Table 30-2. Available Interrupt Vectors and Sources
Offset Name
Vector Description
Conditions
0x00
RESRDY Result Ready interrupt
The conversion result is available in the Result
register (ADC.RES).
0x02
WCOMP Window Comparator interrupt As defined by WINCM in ADC.CTRLE.
When an interrupt condition occurs, the corresponding interrupt flag is set in the Interrupt Flags register of
the peripheral (peripheral.INTFLAGS).
An interrupt source is enabled or disabled by writing to the corresponding enable bit in the peripheral's
Interrupt Control register (peripheral.INTCTRL).
An interrupt request is generated when the corresponding interrupt source is enabled and the interrupt
flag is set. The interrupt request remains active until the interrupt flag is cleared. See the peripheral's
INTFLAGS register for details on how to clear interrupt flags.
30.3.5
Sleep Mode Operation
The ADC is by default disabled in Standby Sleep mode.
The ADC can stay fully operational in Standby Sleep mode if the Run in Standby bit (RUNSTDBY) in the
Control A register (ADC.CTRLA) is written to '1'.
When the device is entering Standby Sleep mode when RUNSTDBY is '1', the ADC will stay active,
hence any ongoing conversions will be completed and interrupts will be executed as configured.
In Standby Sleep mode an ADC conversion must be triggered via the Event System (EVSYS), or the
ADC must be in free-running mode with the first conversion triggered by software before entering sleep.
The peripheral clock is requested if needed and is turned OFF after the conversion is completed.
When an input event trigger occurs, the positive edge will be detected, the Start Conversion bit
(STCONV) in the Command register (ADC.COMMAND) will be set, and the conversion will start. When
the conversion is completed, the Result Ready Flag (RESRDY) in the Interrupt Flags register
(ADC.INTFLAGS) is set and the STCONV bit in ADC.COMMAND is cleared.
The reference source and supply infrastructure need time to stabilize when activated in Standby Sleep
mode. Configure a delay for the start of the first conversion by writing a non-zero value to the Initial Delay
bits (INITDLY) in the Control D register (ADC.CTRLD).
In Power-Down Sleep mode, no conversions are possible. Any ongoing conversions are halted and will
be resumed when going out of sleep. At the end of the conversion, the Result Ready Flag (RESRDY) will
be set, but the content of the result registers (ADC.RES) is invalid since the ADC was halted in the middle
of a conversion.
Related Links
11. SLPCTRL - Sleep Controller
30.3.6
Synchronization
Not applicable.
30.3.7
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 477
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.4
Register Summary - ADCn
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
0x0D
0x0E
...
0x0F
CTRLA
CTRLB
CTRLC
CTRLD
CTRLE
SAMPCTRL
MUXPOS
Reserved
COMMAND
EVCTRL
INTCTRL
INTFLAGS
DBGCTRL
TEMP
7:0
7:0
7:0
7:0
7:0
7:0
7:0
0x10
RES
0x12
WINLT
0x14
WINHT
0x16
CALIB
30.5
RUNSTBY
7:0
7:0
7:0
7:0
7:0
7:0
RESSEL
SAMPCAP
INITDLY[2:0]
REFSEL[1:0]
ASDV
FREERUN
SAMPNUM[2:0]
PRESC[2:0]
SAMPDLY[3:0]
WINCM[2:0]
SAMPLEN[4:0]
MUXPOS[4:0]
WCOMP
WCOMP
ENABLE
STCONV
STARTEI
RESRDY
RESRDY
DBGRUN
TEMP[7:0]
Reserved
7:0
15:8
7:0
15:8
7:0
15:8
7:0
RES[7:0]
RES[15:8]
WINLT[7:0]
WINLT[15:8]
WINHT[7:0]
WINHT[15:8]
DUTYCYC
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 478
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLA
0x00
0x00
-
6
5
4
3
2
1
0
RUNSTBY
RESSEL
FREERUN
ENABLE
R/W
R/W
R/W
R/W
0
0
0
0
Bit 7 – RUNSTBY Run in Standby
This bit determines whether the ADC needs to run when the chip is in Standby Sleep mode.
Bit 2 – RESSEL Resolution Selection
This bit selects the ADC resolution.
Value
Description
0
Full 10-bit resolution. The 10-bit ADC results are accumulated or stored in the ADC Result
register (ADC.RES).
1
8-bit resolution. The conversion results are truncated to eight bits (MSBs) before they are
accumulated or stored in the ADC Result register (ADC.RES). The two Least Significant bits
are discarded.
Bit 1 – FREERUN Free-Running
Writing a '1' to this bit will enable the Free-Running mode for the data acquisition. The first conversion is
started by writing the STCONV bit in ADC.COMMAND high. In the Free-Running mode, a new conversion
cycle is started immediately after or as soon as the previous conversion cycle has completed. This is
signaled by the RESRDY flag in ADCn.INTFLAGS.
Bit 0 – ENABLE ADC Enable
Value
Description
0
ADC is disabled
1
ADC is enabled
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 479
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.2
Control B
Name:
Offset:
Reset:
Property:
Bit
7
CTRLB
0x01
0x00
-
6
5
4
3
2
1
0
SAMPNUM[2:0]
Access
Reset
R/W
R/W
R/W
0
0
0
Bits 2:0 – SAMPNUM[2:0] Sample Accumulation Number Select
These bits select how many consecutive ADC sampling results are accumulated automatically. When this
bit is written to a value greater than 0x0, the according number of consecutive ADC sampling results are
accumulated into the ADC Result register (ADC.RES) in one complete conversion.
Value
Name
Description
0x0
NONE
No accumulation.
0x1
ACC2
2 results accumulated.
0x2
ACC4
4 results accumulated.
0x3
ACC8
8 results accumulated.
0x4
ACC16
16 results accumulated.
0x5
ACC32
32 results accumulated.
0x6
ACC64
64 results accumulated.
0x7
Reserved.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 480
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.3
Control C
Name:
Offset:
Reset:
Property:
CTRLC
0x02
0x00
-
Bit
7
6
Access
R
R/W
Reset
0
0
5
4
3
2
R/W
R/W
R
R/W
R/W
R/W
0
0
0
0
0
0
SAMPCAP
REFSEL[1:0]
1
0
PRESC[2:0]
Bit 6 – SAMPCAP Sample Capacitance Selection
This bit selects the sample capacitance, and hence, the input impedance. The best value is dependent on
the reference voltage and the application's electrical properties.
Value
Description
0
Recommended for reference voltage values below 1V.
1
Reduced size of sampling capacitance. Recommended for higher reference voltages.
Bits 5:4 – REFSEL[1:0] Reference Selection
These bits select the voltage reference for the ADC.
Note: Do not force the internal reference enabled (ADCnREFEN=1 in VREF.CTRLB) when the ADC is
using the external reference (REFSEL bits in ADC.CTRLC).
Value
0x0
0x1
0x2
Other
Name
INTERNAL
VDD
VREFA
-
Description
Internal reference
VDD
External reference VREFA
Reserved.
Bits 2:0 – PRESC[2:0] Prescaler
These bits define the division factor from the peripheral clock (CLK_PER) to the ADC clock (CLK_ADC).
Value
Name
Description
0x0
DIV2
CLK_PER divided by 2
0x1
DIV4
CLK_PER divided by 4
0x2
DIV8
CLK_PER divided by 8
0x3
DIV16
CLK_PER divided by 16
0x4
DIV32
CLK_PER divided by 32
0x5
DIV64
CLK_PER divided by 64
0x6
DIV128
CLK_PER divided by 128
0x7
DIV256
CLK_PER divided by 256
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 481
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.4
Control D
Name:
Offset:
Reset:
Property:
Bit
7
CTRLD
0x03
0x00
-
6
5
INITDLY[2:0]
Access
Reset
4
3
2
ASDV
1
0
SAMPDLY[3:0]
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:5 – INITDLY[2:0] Initialization Delay
These bits define the initialization/start-up delay before the first sample when enabling the ADC or
changing to an internal reference voltage. Setting this delay will ensure that the reference, MUXes, etc.
are ready before starting the first conversion. The initialization delay will also take place when waking up
from deep sleep to do a measurement.
The delay is expressed as a number of CLK_ADC cycles.
Value
Name
Description
0x0
DLY0
Delay 0 CLK_ADC cycles.
0x1
DLY16
Delay 16 CLK_ADC cycles.
0x2
DLY32
Delay 32 CLK_ADC cycles.
0x3
DLY64
Delay 64 CLK_ADC cycles.
0x4
DLY128
Delay 128 CLK_ADC cycles.
0x5
DLY256
Delay 256 CLK_ADC cycles.
Other
Reserved
Bit 4 – ASDV Automatic Sampling Delay Variation
Writing this bit to ’1’ enables automatic sampling delay variation between ADC conversions. The purpose
of varying sampling instant is to randomize the sampling instant and thus avoid standing frequency
components in the frequency spectrum. The value of the SAMPDLY bits is automatically incremented by
one after each sample.
When the Automatic Sampling Delay Variation is enabled and the SAMPDLY value reaches 0xF, it wraps
around to 0x0.
Value
Name
Description
0
ASVOFF
The Automatic Sampling Delay Variation is disabled.
1
ASVON
The Automatic Sampling Delay Variation is enabled.
Bits 3:0 – SAMPDLY[3:0] Sampling Delay Selection
These bits define the delay between consecutive ADC samples. The programmable Sampling Delay
allows modifying the sampling frequency during hardware accumulation, to suppress periodic noise
sources that may otherwise disturb the sampling. The SAMPDLY field can also be modified automatically
from one sampling cycle to another, by setting the ASDV bit. The delay is expressed as CLK_ADC cycles
and is given directly by the bit field setting. The sampling cap is kept open during the delay.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 482
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.5
Control E
Name:
Offset:
Reset:
Property:
Bit
7
CTRLE
0x4
0x00
-
6
5
4
3
2
1
0
WINCM[2:0]
Access
Reset
R/W
R/W
R/W
0
0
0
Bits 2:0 – WINCM[2:0] Window Comparator Mode
This field enables and defines when the interrupt flag is set in Window Comparator mode. RESULT is the
16-bit accumulator result. WINLT and WINHT are 16-bit lower threshold value and 16-bit higher threshold
value, respectively.
Value
Name
Description
0x0
NONE
No Window Comparison (default)
0x1
BELOW
RESULT < WINLT
0x2
ABOVE
RESULT > WINHT
0x3
INSIDE
WINLT < RESULT < WINHT
0x4
OUTSIDE
RESULT < WINLT or RESULT >WINHT)
Other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 483
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.6
Sample Control
Name:
Offset:
Reset:
Property:
Bit
7
SAMPCTRL
0x5
0x00
-
6
5
4
3
R/W
R/W
0
0
2
1
0
R/W
R/W
R/W
0
0
0
SAMPLEN[4:0]
Access
Reset
Bits 4:0 – SAMPLEN[4:0] Sample Length
These bits extend the ADC sampling length in a number of CLK_ADC cycles. By default, the sampling
time is two CLK_ADC cycles. Increasing the sampling length allows sampling sources with higher
impedance. The total conversion time increases with the selected sampling length.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 484
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.7
MUXPOS
Name:
Offset:
Reset:
Property:
MUXPOS
0x06
0x00
-
Bit
7
6
5
4
3
Access
R
R
R
R/W
R/W
Reset
0
0
0
0
0
2
1
0
R/W
R/W
R/W
0
0
0
MUXPOS[4:0]
Bits 4:0 – MUXPOS[4:0] MUXPOS
This bit field selects which single-ended analog input is connected to the ADC. If these bits are changed
during a conversion, the change will not take effect until this conversion is complete.
Value
Name
Description
0x00
AIN0
ADC input pin 0
0x01
AIN1
ADC input pin 1
0x02
AIN2
ADC input pin 2
0x03
AIN3
ADC input pin 3
0x04
AIN4
ADC input pin 4
0x05
AIN5
ADC input pin 5
0x06
AIN6
ADC input pin 6
0x07
AIN7
ADC input pin 7
0x08
AIN8
ADC input pin 8
0x09
AIN9
ADC input pin 9
0x0A
AIN10
ADC input pin 10
0x0B
AIN11
ADC input pin 11
0x1B
PTC
ADC0: Reserved / ADC1: DAC2
0x1C
DAC0
DAC0
0x1D
INTREF
Internal reference (from VREF peripheral)
0x1F
GND
0V (GND)
Other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 485
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.8
Command
Name:
Offset:
Reset:
Property:
COMMAND
0x08
0x00
-
Bit
7
6
5
4
3
2
1
0
Access
R
R
R
R
R
R
R
R/W
Reset
0
0
0
0
0
0
0
0
STCONV
Bit 0 – STCONV Start Conversion
Writing a '1' to this bit will start a single measurement. If in Free-Running mode this will start the first
conversion. STCONV will read as '1' as long as a conversion is in progress. When the conversion is
complete, this bit is automatically cleared.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 486
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.9
Event Control
Name:
Offset:
Reset:
Property:
Bit
7
EVCTRL
0x09
0x00
-
6
5
4
3
2
1
0
STARTEI
Access
R/W
Reset
0
Bit 0 – STARTEI Start Event Input
This bit enables using the event input as trigger for starting a conversion.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 487
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.10 Interrupt Control
Name:
Offset:
Reset:
Property:
Bit
7
INTCTRL
0x0A
0x00
-
6
5
4
3
Access
Reset
2
1
0
WCOMP
RESRDY
R/W
R/W
0
0
Bit 1 – WCOMP Window Comparator Interrupt Enable
Writing a '1' to this bit enables window comparator interrupt.
Bit 0 – RESRDY Result Ready Interrupt Enable
Writing a '1' to this bit enables result ready interrupt.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 488
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.11 Interrupt Flags
Name:
Offset:
Reset:
Property:
Bit
7
INTFLAGS
0x0B
0x00
-
6
5
4
3
Access
Reset
2
1
0
WCOMP
RESRDY
R/W
R/W
0
0
Bit 1 – WCOMP Window Comparator Interrupt Flag
This window comparator flag is set when the measurement is complete and if the result matches the
selected Window Comparator mode defined by WINCM (ADCn.CTRLE). The comparison is done at the
end of the conversion. The flag is cleared by either writing a '1' to the bit position or by reading the Result
register (ADCn.RES). Writing a '0' to this bit has no effect.
Bit 0 – RESRDY Result Ready Interrupt Flag
The result ready interrupt flag is set when a measurement is complete and a new result is ready. The flag
is cleared by either writing a '1' to the bit location or by reading the Result register (ADCn.RES). Writing a
'0' to this bit has no effect.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 489
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.12 Debug Run
Name:
Offset:
Reset:
Property:
Bit
7
DBGCTRL
0x0C
0x00
-
6
5
4
3
2
1
0
DBGRUN
Access
R/W
Reset
0
Bit 0 – DBGRUN Debug Run
Value
Description
0
The peripheral is halted in Break Debug mode and ignores events
1
The peripheral will continue to run in Break Debug mode when the CPU is halted
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 490
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.13 Temporary
Name:
Offset:
Reset:
Property:
TEMP
0x0D
0x00
-
The Temporary register is used by the CPU for single-cycle, 16-bit access to the 16-bit registers of this
peripheral. It can be read and written by software. Refer to 16-bit access in the AVR CPU chapter. There
is one common Temporary register for all the 16-bit registers of this peripheral.
Bit
7
6
5
4
3
2
1
0
TEMP[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 7:0 – TEMP[7:0] Temporary
Temporary register for read/write operations in 16-bit registers.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 491
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.14 Result
Name:
Offset:
Reset:
Property:
RES
0x10
0x00
-
The ADCn.RESL and ADCn.RESH register pair represents the 16-bit value, ADCn.RES. The low byte
[7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at offset
+ 0x01.
If the analog input is higher than the reference level of the ADC, the 10-bit ADC result will be equal the
maximum value of 0x3FF. Likewise, if the input is below 0V, the ADC result will be 0x000. As the ADC
cannot produce a result above 0x3FF values, the accumulated value will never exceed 0xFFC0 even
after the maximum allowed 64 accumulations.
Bit
15
14
13
12
11
10
9
8
RES[15:8]
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
RES[7:0]
Access
R
R
R
R
R
R
R
R
Reset
0
0
0
0
0
0
0
0
Bits 15:8 – RES[15:8] Result high byte
These bits constitute the MSB of the ADCn.RES register, where the MSb is RES[15]. The ADC itself has
a 10-bit output, ADC[9:0], where the MSb is ADC[9]. The data format in ADC and Digital Accumulation is
1’s complement, where 0x0000 represents the '0' and 0xFFFF represents the largest number (full scale).
Bits 7:0 – RES[7:0] Result low byte
These bits constitute the LSB of ADC/Accumulator Result, (ADCn.RES) register. The data format in ADC
and Digital Accumulation is 1’s complement, where 0x0000 represents the '0' and 0xFFFF represents the
largest number (full scale).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 492
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.15 Window Comparator Low Threshold
Name:
Offset:
Reset:
Property:
WINLT
0x12
0x00
-
This register is the 16-bit low threshold for the digital comparator monitoring the ADCn.RES register. The
ADC itself has a 10-bit output, RES[9:0], where the MSb is RES[9]. The data format in ADC and Digital
Accumulation is 1’s complement, where 0x0000 represents the '0' and 0xFFFF represents the largest
number (full scale).
The ADCn.WINLTH and ADCn.WINLTL register pair represents the 16-bit value, ADCn.WINLT. The low
byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at
offset + 0x01.
When accumulating samples, the window comparator thresholds are applied to the accumulated value
and not on each sample.
Bit
15
14
13
12
11
10
9
8
WINLT[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
WINLT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – WINLT[15:8] Window Comparator Low Threshold High Byte
These bits hold the MSB of the 16-bit register.
Bits 7:0 – WINLT[7:0] Window Comparator Low Threshold Low Byte
These bits hold the LSB of the 16-bit register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 493
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.16 Window Comparator High Threshold
Name:
Offset:
Reset:
Property:
WINHT
0x14
0x00
-
This register is the 16-bit high threshold for the digital comparator monitoring the ADCn.RES register. The
ADC itself has a 10-bit output, RES[9:0], where the MSb is RES[9]. The data format in ADC and Digital
Accumulation is 1’s complement, where 0x0000 represents the '0' and 0xFFFF represents the largest
number (full scale).
The ADCn.WINHTH and ADCn.WINHTL register pair represents the 16-bit value, ADCn.WINHT. The low
byte [7:0] (suffix L) is accessible at the original offset. The high byte [15:8] (suffix H) can be accessed at
offset + 0x01.
Bit
15
14
13
12
11
10
9
8
WINHT[15:8]
Access
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit
7
6
5
4
3
2
1
0
WINHT[7:0]
Access
Reset
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
0
Bits 15:8 – WINHT[15:8] Window Comparator High Threshold High Byte
These bits hold the MSB of the 16-bit register.
Bits 7:0 – WINHT[7:0] Window Comparator High Threshold Low Byte
These bits hold the LSB of the 16-bit register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 494
ATtiny1616/3216
ADC - Analog-to-Digital Converter
30.5.17 Calibration
Name:
Offset:
Reset:
Property:
Bit
7
CALIB
0x16
0x01
-
6
5
4
3
2
1
0
R/W
R/W
R/W
0
0
1
DUTYCYC
Access
Reset
Bit 0 – DUTYCYC Duty Cycle
This bit determines the duty cycle of the ADC clock.
ADCclk > 1.5 MHz requires a minimum operating voltage of 2.7V
Value
Description
0
50% Duty Cycle must be used if ADCclk > 1.5 MHz
1
25% Duty Cycle (high 25% and low 75%) must be used for ADCclk ≤ 1.5 MHz
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 495
ATtiny1616/3216
DAC - Digital-to-Analog Converter
31.
DAC - Digital-to-Analog Converter
31.1
Features
•
•
•
•
•
31.2
8-bit Resolution
Up to 350 ksps Conversion Rate
High Drive Capabilities (DAC0)
Functioning as Input to Analog Comparator (AC) or ADC
Three Instances of the Peripheral: DAC0, DAC1, DAC2
Overview
The Digital-to-Analog Converter (DAC) converts a digital value written to the Data register (DAC.DATA) to
an analog voltage. The conversion range is between GND and the selected reference voltage.
The DAC features an 8-bit resistor-string type DAC, capable of converting 350,000 samples per second
(350 ksps). The DAC uses the internal Voltage Reference (VREF) as the upper limit for conversion. The
DAC has one continuous time output with high drive capabilities, which is able to drive 5 kΩ and/or 30 pF
load. The DAC conversion can be started from the application by writing to the Data Conversion registers.
This device has three instances of the DAC peripheral, DAC0, DAC1, and DAC2.
31.2.1
Block Diagram
Figure 31-1. DAC Block Diagram
Other
Peripherals
DATA
8
DAC
OUT
Output
Driver
VREF
ENABLE
CTRLA
OUTEN
Note: Only DAC0 has an output driver for an external pin.
31.2.2
Signal Description
Signal
Description
Type
OUT
DAC output
Analog
Note: Only DAC0 has an output driver for an external pin.
Related Links
5. I/O Multiplexing and Considerations
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 496
ATtiny1616/3216
DAC - Digital-to-Analog Converter
31.2.3
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 31-1. DAC System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
No
-
Events
No
-
Debug
Yes
UPDI
Related Links
11.2.2.1 Clocks
31.2.3.2 I/O Lines and Connections
31.2.3.5 Debug Operation
31.2.3.1 Clocks
This peripheral depends on the peripheral clock.
Related Links
10. CLKCTRL - Clock Controller
31.2.3.2 I/O Lines and Connections
Using the I/O lines of the peripheral requires configuration of the I/O pins.
Table 31-2. I/O Lines
Instance
Signal
I/O Line
Peripheral Function
DAC0
OUT
PA6
A
The DAC0 has one analog output pin (OUT) that must be configured before it can be used.
A DAC is also internally connected to the AC and to the ADC. To use this internal OUT as input, both
output and input must be configured in their respective registers.
Note: Only DAC0 has an output driver for an external pin.
Related Links
16. PORT - I/O Pin Configuration
29. AC - Analog Comparator
30. ADC - Analog-to-Digital Converter
31.2.3.3 Events
Not applicable.
31.2.3.4 Interrupts
Not applicable.
31.2.3.5 Debug Operation
This peripheral is unaffected by entering Debug mode.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 497
ATtiny1616/3216
DAC - Digital-to-Analog Converter
If the peripheral is configured to require periodical service by the CPU through interrupts or similar,
improper operation or data loss may result during halted debugging.
Related Links
16. PORT - I/O Pin Configuration
31.3
Functional Description
31.3.1
Initialization
To operate the DAC, the following steps are required:
• Select the DAC reference voltage in the Voltage Reference (VREF) peripheral by writing the DAC
and AC Reference Selection bits (DAC0REFSEL) in the Control A register of the Voltage Reference
(VREF.CTRLA) for DAC0. For DAC1, use DAC1REFSEL in VREF.CTRLC. For DAC2, use
DAC2REFSEL in VREF.CTRLD.
• The conversion range is between GND and the selected reference voltage.
• Configure the further usage of the DAC output:
– Configure an internal peripheral (e.g. AC, ADC) to use the DAC output. See the according
peripheral's documentation.
– Enable the output to a pin by writing a '1' to the Output Enable bit (OUTEN) in the Control A
register (DAC.CTRLA). This requires configuration of the Port peripheral.
For DAC0, either one or both options are valid. Other instances of the DAC only support internal
signaling.
• Write an initial digital value to the Data register (DAC.DATA).
• Enable the DAC by writing a '1' to the ENABLE bit in the Control A register (DAC.CTRLA).
Related Links
18. VREF - Voltage Reference
29. AC - Analog Comparator
30. ADC - Analog-to-Digital Converter
31.3.2
Operation
31.3.2.1 Enabling, Disabling, and Resetting
The DAC is enabled by writing a '1' to the ENABLE bit in the Control A register (DACn.CTRLA), and
disabled by writing a '0' to this bit.
The OUT output to a pin is enabled by writing the Output Enable bit (OUTEN) in the CTRLA register
(DACn.CTRLA).
31.3.2.2 Starting a Conversion
When the DAC is enabled (ENABLE=1 in DACn.CTRLA), a conversion starts as soon as the Data
register (DACn.DATA) is written.
When the DAC is disabled (ENABLE=0 in DACn.CTRLA), writing DACn.DATA does not trigger a
conversion. Instead, the conversion starts on writing a '1' to ENABLE in DACn.CTRLA.
31.3.2.3 DAC as Source For Internal Peripherals
The analog output of the DAC is internally connected to both the AC and the ADC and is available to
these other peripherals when the DAC is enabled (ENABLE=1 in DAC.CTRLA). When the DAC analog
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 498
ATtiny1616/3216
DAC - Digital-to-Analog Converter
output is only being used internally, it is not necessary to enable the pin output driver (i.e. OUTEN=0 in
DAC.CTRLA is acceptable).
Note: Only DAC0 has an output driver for an external pin.
Related Links
29. AC - Analog Comparator
30. ADC - Analog-to-Digital Converter
31.3.3
Sleep Mode Operation
If the Run in Standby bit (RUNSTDBY) in the Control A register (DAC.CTRLA) is written to '1' and
CLK_PER is available, the DAC will continue to operate in Standby Sleep mode. If RUNSTDBY bit is '0',
the DAC will stop the conversion in Standby Sleep mode.
If the conversion is stopped in Standby Sleep mode, the DAC and the output buffer are disabled to
reduce power consumption. When the device is exiting Standby Sleep mode, the DAC and the output
buffer (if configured by OUTEN=1 in DAC.CTRLA) are enabled again. Therefore, a certain start-up time is
required before a new conversion is initiated.
In Power-Down Sleep mode, the DAC and output buffer are disabled to reduce the power consumption.
Note: Only DAC0 has an output driver for an external pin.
31.3.4
Configuration Change Protection
Not applicable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 499
ATtiny1616/3216
DAC - Digital-to-Analog Converter
31.4
Register Summary - DAC
Offset
Name
Bit Pos.
0x00
0x01
CTRLA
DATA
7:0
7:0
31.5
RUNSTDBY
OUTEN
ENABLE
DATA[7:0]
Register Description
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 500
ATtiny1616/3216
DAC - Digital-to-Analog Converter
31.5.1
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
CTRLA
0x00
0x00
-
7
6
5
4
3
2
1
0
RUNSTDBY
OUTEN
ENABLE
R/W
R/W
R/W
0
0
0
Bit 7 – RUNSTDBY Run in Standby Mode
If this bit is written to '1', the DAC or output buffer will not automatically be disabled when the device is
entering Standby Sleep mode.
Note: Only DAC0 has an output driver for an external pin.
Bit 6 – OUTEN Output Buffer Enable
Writing a '1' to this bit enables the output buffer and sends the OUT signal to a pin.
Note: Only DAC0 has an output driver for an external pin.
Bit 0 – ENABLE DAC Enable
Writing a '1' to this bit enables the DAC.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 501
ATtiny1616/3216
DAC - Digital-to-Analog Converter
31.5.2
DATA
Name:
Offset:
Reset:
Property:
Bit
DATA
0x01
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
DATA[7:0]
Access
Reset
Bits 7:0 – DATA[7:0] Data
These bits contain the digital data, which will be converted to an analog voltage.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 502
ATtiny1616/3216
Peripheral Touch Controller (PTC)
32.
Peripheral Touch Controller (PTC)
32.1
Overview
The Peripheral Touch Controller (PTC) acquires signals in order to detect a touch on the capacitive
sensors. The external capacitive touch sensor is typically formed on a PCB, and the sensor electrodes
are connected to the analog front end of the PTC through the I/O pins in the device. The PTC supports
both self and mutual capacitance sensors.
In the Mutual Capacitance mode, sensing is done using capacitive touch matrices in various X-Y
configurations, including indium tin oxide (ITO) sensor grids. The PTC requires one pin per X-line and one
pin per Y-line.
In the Self Capacitance mode, the PTC requires only one pin (Y-line) for each touch sensor.
The number of available pins and the assignment of X- and Y-lines is depending on both package type
and device configuration. Refer to the Configuration Summary and I/O Multiplexing table for details.
Related Links
2.1 Configuration Summary
5. I/O Multiplexing and Considerations
32.2
Features
• Low-Power, High-Sensitivity, Environmentally Robust Capacitive Touch Buttons, Sliders, and Wheels
• Supports Wake-up on Touch from power-save Sleep mode
• Supports Mutual Capacitance and Self Capacitance Sensing
– Mix-and-Match Mutual and Self Capacitance Sensors
• One Pin per Electrode – No External Components
• Load Compensating Charge Sensing
– Parasitic capacitance compensation and adjustable gain for superior sensitivity
• Zero Drift Over the Temperature and VDD Range
– Auto calibration and recalibration of sensors
• Single-shot and free-running Charge Measurement
• Hardware Noise Filtering and Noise Signal Desynchronization for High Conducted Immunity
• Driven Shield for Better Noise Immunity and Moisture Tolerance
– Any PTC X/Y line can be used for the driven shield
– All enabled sensors will be driven at the same potential as the sensor scanned
• Selectable channel change delay allows choosing the settling time on a new channel, as required
• Acquisition-start triggered by command or through auto-triggering feature
• Low CPU utilization through interrupt on acquisition-complete
• Using ADC peripheral for signal conversion and acquisition
Related Links
2.1 Configuration Summary
5. I/O Multiplexing and Considerations
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 503
ATtiny1616/3216
Peripheral Touch Controller (PTC)
32.3
Block Diagram
Figure 32-1. PTC Block Diagram Mutual Capacitance
Input
Control
Compensation
Circuit
Y0
RS
Y1
Charge
Integrator
Ym
IRQ
ADC
System
10
Result
CX0Y0
X0
X Line Driver
X1
C XnYm
Xn
Figure 32-2. PTC Block Diagram Self Capacitance
Input
Control
Compensation
Circuit
Y0
Y1
CY0
RS
Charge
Integrator
Ym
IRQ
ADC
System
10
Result
CYm
Shield Driver
X Line Driver
32.4
Signal Description
Table 32-1. Signal Description for PTC
Name
Type
Description
Y[m:0]
Analog
Y-line (Input/Output)
X[n:0]
Digital
X-line (Output)
Note: The number of X- and Y-lines are device dependent. Refer to Configuration Summary for details.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 504
ATtiny1616/3216
Peripheral Touch Controller (PTC)
Refer to I/O Multiplexing and Considerations for details on the pin mapping for this peripheral. One signal
can be mapped on several pins.
Related Links
2.1 Configuration Summary
5. I/O Multiplexing and Considerations
32.5
System Dependencies
In order to use this peripheral, configure the other components of the system as described in the following
sections.
32.5.1
I/O Lines
The I/O lines used for analog X-lines and Y-lines must be connected to external capacitive touch sensor
electrodes. External components are not required for normal operation. However, to improve the EMC
performance, a series resistor of 1 kΩ or more can be used on X-lines and Y-lines.
32.5.1.1 Mutual Capacitance Sensor Arrangement
A mutual capacitance sensor is formed between two I/O lines - an X electrode for transmitting and Y
electrode for sensing. The mutual capacitance between the X and Y electrode is measured by the
peripheral touch controller.
Figure 32-3. Mutual Capacitance Sensor Arrangement
Sensor Capacitance Cx,y
MCU
X0
X1
Xn
Cx0,y0
Cx0,y1
Cx0,ym
Cx1,y0
Cx1,y1
Cx1,ym
Cxn,y0
Cxn,y1
Cxn,ym
PTC
PTC
Module
Module
Y0
Y1
Ym
32.5.1.2 Self Capacitance Sensor Arrangement
A self capacitance sensor is connected to a single pin on the peripheral touch controller through the Y
electrode for sensing the signal. The sense electrode capacitance is measured by the peripheral touch
controller.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 505
ATtiny1616/3216
Peripheral Touch Controller (PTC)
Figure 32-4. Self-Capacitance Sensor Arrangement
MCU
Sensor Capacitance Cy
Y0
Cy0
Y1
Cy1
PTC
Module
Ym
Cym
For more information about designing the touch sensor, refer to Buttons, Sliders and Wheels Touch
Sensor Design Guide.
32.5.2
Clocks
The PTC is clocked by the CLK_PER clock. See the Related Links for details on configuring CLK_PER.
Related Links
10. CLKCTRL - Clock Controller
32.5.3
Analog-Digital Converter (ADC)
The PTC is using the ADC for signal conversion and acquisition. The ADC must be enabled and
configured appropriately to allow correct behavior of the PTC.
Related Links
30. ADC - Analog-to-Digital Converter
32.6
Functional Description
In order to access the PTC, the user must use the Atmel Start QTouch® Configurator to configure and link
the QTouch Library firmware with the application software. QTouch Library can be used to implement
buttons, sliders, and wheels in a variety of combinations on a single interface.
Figure 32-5. QTouch Library Usage
Custom Code
Compiler
Link
Application
QTouch
Library
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 506
ATtiny1616/3216
Peripheral Touch Controller (PTC)
For more information about QTouch Library, refer to the QTouch Library Peripheral Touch Controller User
Guide.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 507
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.
UPDI - Unified Program and Debug Interface
33.1
Features
• Programming:
– External programming through UPDI 1-wire (1W) interface
• Enable programming by 12V or fuse
• Uses the RESET pin of the device for programming
• No GPIO pins occupied during operation
• Asynchronous Half-Duplex UART protocol towards the programmer
• Debugging:
– Memory mapped access to device address space (NVM, RAM, I/O)
– No limitation on device clock frequency
– Unlimited number of user program breakpoints
– Two hardware breakpoints
– Run-time readout of CPU Program Counter (PC), Stack Pointer (SP), and Status register
(SREG) for code profiling
– Program flow control
• Go, Stop, Reset, Step Into
– Non-intrusive run-time chip monitoring without accessing system registers
• Monitor CRC status and sleep status
• Unified Programming and Debug Interface (UPDI):
– Built-in error detection with error signature readout
– Frequency measurement of internal oscillators using the Event System
33.2
Overview
The Unified Program and Debug Interface (UPDI) is a proprietary interface for external programming and
on-chip debugging of a device.
The UPDI supports programming of nonvolatile memory (NVM) space; FLASH, EEPROM, fuses, lockbits,
and the user row. In addition, the UPDI can access the entire I/O and data space of the device. See the
NVM controller documentation for programming via the NVM controller and executing NVM controller
commands.
Programming and debugging are done through the UPDI Physical interface (UPDI PHY), which is a 1wire UART-based half duplex interface using the RESET pin for data reception and transmission.
Clocking of UPDI PHY is done by an internal oscillator. Enabling of the 1-wire interface, by disabling the
Reset functionality, is either done by 12V programming or by fusing the RESET pin to UPDI by setting the
RESET Pin Configuration (RSTPINCFG) bits in FUSE.SYSCFG0. The UPDI access layer grants access
to the bus matrix, with memory mapped access to system blocks such as memories, NVM, and
peripherals.
The Asynchronous System Interface (ASI) provides direct interface access to On-Chip Debugging (OCD),
NVM, and System Management features. This gives the debugger direct access to system information,
without requesting bus access.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 508
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Related Links
9. NVMCTRL - Nonvolatile Memory Controller
33.3.7 Enabling of KEY Protected Interfaces
33.2.1
Block Diagram
Figure 33-1. UPDI Block Diagram
ASI
Memories
UPDI PAD
(RX/TX Data)
UPDI
Physical
layer
Bus Matrix
UPDI Controller
UPDI
Access
layer
NVM
Peripherals
ASI Access
ASI Internal Interfaces
OCD
NVM
Controller
System
Management
33.2.2
System Dependencies
In order to use this peripheral, other parts of the system must be configured correctly, as described below.
Table 33-1. UPDI System Dependencies
Dependency
Applicable
Peripheral
Clocks
Yes
CLKCTRL
I/O Lines and Connections
Yes
PORT
Interrupts
No
-
Events
Yes
EVSYS
Debug
Yes
UPDI
Related Links
33.2.2.2 I/O Lines and Connections
33.2.2.4 Power Management
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 509
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.2.2.1 Clocks
The UPDI Physical (UPDI PHY) layer and UPDI Access (UPDI ACC) layer can operate on different clock
domains. The UPDI PHY layer clock is derived from an internal oscillator, and the UPDI ACC layer clock
is the same as the system clock. There is a synchronization boundary between the UPDI PHY layer and
the UPDI ACC layer, which ensures correct operation between the clock domains. The UPDI clock output
frequency is selected through the ASI, and the default UPDI clock start-up frequency is 4 MHz after
enabling the UPDI. The UPDI clock frequency is changed by writing the UPDICLKSEL bits in the
ASI_CTRLA register.
Figure 33-2. UPDI Clock Domains
ASI
SYNCH
UPDI Controller
UPDI
Physical
layer
Clock
Controller
UPDI clk
source
~
UPDI
Access
layer
Clock
Controller
Clk_UPDI
Clk_sys
Clk_sys
UPDI
CLKSEL
~
Related Links
10. CLKCTRL - Clock Controller
33.2.2.2 I/O Lines and Connections
To operate the UPDI, the RESET pin must be set to UPDI mode. This is not done through the port I/O pin
configuration as regular I/O pins, but through setting the RESET Pin Configuration (RSTPINCFG) bits in
FUSE.SYSCFG0, as described in 33.3.2.1 UPDI Enable with Fuse Override of RESET Pin, or by
following the UPDI 12V enable sequence from 33.3.2.2 UPDI Enable with 12V Override of RESET Pin.
Pull enable, input enable, and output enable settings are automatically controlled by the UPDI when
active.
33.2.2.3 Events
The events of this peripheral are connected to the Event System.
Related Links
14. EVSYS - Event System
33.2.2.4 Power Management
The UPDI physical layer continues to operate in any Sleep mode and is always accessible for a
connected debugger, but read/write access to the system bus is restricted in Sleep modes where the
CPU clock is switched OFF. The UPDI can be enabled at any time, independent of the system Sleep
state. See 33.3.9 Sleep Mode Operation for details on UPDI operation during Sleep modes.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 510
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.3
Functional Description
33.3.1
Principle of Operation
Communication through the UPDI is based on standard UART communication, using a fixed frame
format, and automatic baud rate detection for clock and data recovery. In addition to the data frame, there
are several control frames which are important to the communication. The supported frame formats are
presented in Figure 33-3.
Figure 33-3. Supported UPDI Frame Formats
DATA
St
0
1
2
3
4
5
6
7
P
S1 S2
P
S1 S2
P
S1 S2
IDLE
BREAK
SYNCH (0x55)
St
Synch Part
End_synch
ACK (0x40)
St
Data
Frame
IDLE
Frame
BREAK
SYNCH
ACK
Data frame consists of one Start bit (always low), eight data bits, one parity bit (even parity),
and two Stop bits (always high). If the Start bit, parity bit, or Stop bits have an incorrect value,
an error will be detected and signalized by the UPDI. The parity bit-check in the UPDI can be
disabled by writing the PARD bit in UPDI.CTRLA, in which case the parity generation from the
debugger can be ignored.
Special frame that consists of 12 high bits. This is the same as keeping the transmission line
in an Idle state.
Special frame that consists of 12 low bits. The BREAK frame is used to reset the UPDI back
to its default state and is typically used for error recovery.
The SYNCH frame (0x55) is used by the Baud Rate Generator to set the baud rate for the
coming transmission. A SYNCH character is always expected by the UPDI in front of every
new instruction, and after a successful BREAK has been transmitted.
The Acknowledge (ACK) character is transmitted from the UPDI whenever an ST or STS
instruction has successfully crossed the synchronization boundary and have gained bus
access. When an ACK is received by the debugger, the next transmission can start.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 511
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.3.1.1 UPDI UART
All transmission and reception of serial data on the UPDI is achieved using the UPDI frames presented in
Figure 33-3. Communication is initiated from the master (debugger) side, and every transmission must
start with a SYNCH character upon which the UPDI can recover the transmission baud rate, and store
this setting for the coming data. The baud rate set by the SYNCH character will be used for both
reception and transmission for the instruction byte received after the SYNCH. See 33.3.3 UPDI
Instruction Set for details on when the next SYNCH character is expected in the instruction stream.
There is no writable baud rate register in the UPDI, so the baud rate sampled from the SYNCH character
is used for data recovery by sampling the Start bit, and performing a majority vote on the middle samples.
This process is repeated for all bits in the frame, including the parity bit and two Stop bits. The baud
generator uses 16 samples, and the majority voting is done on sample 7, 8, and 9.
Figure 33-4. UPDI UART Start Bit and Data/Parity/Stop Bit Sampling
RxD
IDLE
Sample
0 0
START
1
2
3
4
5
6
7
RxD
BIT 0
8 9 10 11 12 13 14 15 16 1
2
3
BIT n
Sample
1
2
3
4
5
6
7
8 9 10 11 12 13 14 15 16 1
The transmission baud rate must be set up in relation to the selected UPDI clock, which can be adjusted
by UPDICLKSEL in UPDI.ASI_CTRLA. See Table 33-2 for recommended maximum and minimum baud
rate settings.
Table 33-2. Recommended UART Baud Rate Based on UPDICLKSEL Setting
UPDICLKSEL[1:0]
MAX Recommended Baud Rate MIN Recommended Baud Rate
0x1 (16 MHz)
0.9 Mbps
0.300 kbps
0x2 (8 MHz)
450 kbps
0.150 kbps
0x3 (4 MHz) - Default
225 kbps
0.075 kbps
The UPDI Baud Rate Generator utilizes fractional baud counting to minimize the transmission error. With
the fixed frame format used by the UPDI, the maximum and recommended receiver transmission error
limits can be seen in the following table:
Table 33-3. Receiver Baud Rate Error
Data + Parity Bits
Rslow
Rfast
Max. Total Error
[%]
Recommended
Max. RX Error [%]
9
96.39
104.76
+4.76/-3.61
+1.5/-1.5
33.3.1.2 BREAK Character
The BREAK character is used to reset the internal state of the UPDI to the default setting. This is useful if
the UPDI enters an error state due to a communication error, or when the synchronization between the
debugger and the UPDI is lost.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 512
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
A single BREAK character is enough to reset the UPDI, but in some special cases where the BREAK
character is sent when the UPDI has not yet entered the error state, a double BREAK character might be
needed. A double BREAK is ensured to reset the UPDI from any state. When sending a double BREAK it
is required to have at least one Stop bit between the BREAK characters.
No SYNCH character is required before the BREAK because the BREAK is used to reset the UPDI from
any state. This means that the UPDI will sample the BREAK based on the last stored baud rate setting,
derived from the last received valid SYNCH character. If the communication error was due to an incorrect
sampling of the SYNCH character, the baud rate is unknown to the connected debugger. For this reason,
the BREAK character should be transmitted at the slowest recommended baud rate setting for the
selected UPDI clock according to Table 33-4:
Table 33-4. Recommended BREAK Character Duration
33.3.2
UPDICLKSEL[1:0]
Recommended BREAK Character Duration
0x1 (16 MHz)
6.15 ms
0x2 (8 MHz)
12.30 ms
0x3 (4 MHz) - Default
24.60 ms
Operation
The UPDI must be enabled before the UART communication can start.
33.3.2.1 UPDI Enable with Fuse Override of RESET Pin
When the RESET Pin Configuration (RSTPINCFG) bits in FUSE.SYSCFG0 are 0x1, the RESET pin will
be overridden, and the UPDI will take control of the pin and configure it as input with pull-up. When the
pull-up is detected by a connected debugger, the UPDI enable sequence, as depicted below, is started.
Figure 33-5. UPDI Enable Sequence with UPDI PAD Enabled By Fuse
1
Fuse read in. Pull-up enabled. Ready to receive init.
2
Drive low from debugger to request UPDI clock
3
UPDI clock ready; Communication channel ready.
RESET
1
2
Hi-Z
St
D0
D1
D2
Handshake / BREAK
TRES
UPDI.rxd
UPDI.txd
D3
D4
D5
D6
D7
Sp
SYNC (0x55)
(Autobaud)
(Ignore)
3
Hi-Z
Hi-Z
UPDI.txd = 0
TUPDI
debugger.
UPDI.txd
Hi-Z
Hi-Z
Debugger.txd = 0
TDeb0
Debugger.txd = z
TDebZ
When the pull-up is detected, the debugger initiates the enable sequence by driving the line low for a
duration of TDeb0 to ensure that the line is released from the debugger before the UPDI enable sequence
is done.
The negative edge is detected by the UPDI, which requests the UPDI clock. The UPDI will continue to
drive the line low until the clock is stable and ready for the UPDI to use. The duration of this TUPDI will
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 513
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
vary, depending on the status of the oscillator when the UPDI is enabled. After this duration, the data line
will be released by the UPDI and pulled high.
When the debugger detects that the line is high, the initial SYNCH character (0x55) must be sent to
properly enable the UPDI for communication. If the Start bit of the SYNCH character is not sent well
within maximum TDebZ, the UPDI will disable itself, and the enable sequence must be repeated. This time
is based on counted cycles on the 4 MHz UPDI clock, which is the default when enabling the UPDI. The
disable is performed to avoid the UPDI being enabled unintentionally.
After successful SYNCH character transmission, the first instruction frame can be transmitted.
Related Links
37.20 UPDI Timing
37.20 UPDI Timing
33.3.2.2 UPDI Enable with 12V Override of RESET Pin
GPIO or Reset functionality on the RESET pin can be overridden by the UPDI by using 12V
programming. By applying a 12V pulse to the RESET pin, the pin functionality is switched to UPDI,
independent of RSTPINCFG in FUSE.SYSCFG0. It is recommended to always reset the device before
starting the 12V enable sequence.
During power-up, the Power-on Reset (POR) must be released before the 12V pulse can be applied. The
duration of the pulse is recommended in the range from 100 μs to 1 ms, before tri-stating. When applying
the rising edge of the 12V pulse, the UPDI will be reset. After tri-stating, the UPDI will remain in Reset
until the RESET pin is driven low by the debugger. This will release the UPDI Reset and initiate the same
enable sequence as explained in 33.3.2.1 UPDI Enable with Fuse Override of RESET Pin.
The following figure shows the 12V enable sequence.
Figure 33-6. UPDI Enable Sequence by 12V Programming
1 Fused pin Function disabled; UPDI pin function enabled.
2
UPDI interface enabled with pull-up.
1
(Ignore)
St
Hi-Z
D0
D1
D2
D3
D4
D5
D6
D7
Sp
UPDIPAD
12V ramp
Tmin10ns
Tmax4ms
Handshake / BREAK
Debugger.txd = z
Tmin10us
Tmin1us
Tmax200us
Tmax10us
SYNC (0x55)
(Autobaud)
(Ignore)
UPDI.rxd
Hi-Z
UPDI.txd
Hi-Z
2
UPDI.txd = 0
Tmin10us,
Tmax200us
debugger.
UPDI.txd
debugger.
UPDI.o12v
Hi-Z
12V
Hi-Z
Debugger.txd = 0
Tmin200ns
Tmax1us
Debugger.txd = z.
Tmin200us,
Tmax14ms
Vdd
When enabled by 12V, only a POR will disable the UPDI configuration on the RESET pin, and restore the
default setting. If issuing a UPDI Disable command through the UPDIDIS bit in UPDI.CTRLB, the UPDI
will be reset and the clock request will be canceled, but the RESET pin will remain in UPDI configuration.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 514
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Note: If insufficient external protection is added to the UPDI Pin, an ESD pulse can be interpreted as a
12V override by the microcontroller and enables the UPDI.
33.3.2.3 UPDI Disable
Any programming or debug session should be terminated by writing the UPDIDIS bit in UPDI.CTRLB.
Writing this bit will reset the UPDI including any decoded KEYs and disable the oscillator request for the
module. If the disable operation is not performed the UPDI will stay enabled and request its oscillator,
causing increased power consumption for the application.
During the enable sequence the UPDI can disable itself in case of a faulty enable sequence. There are
two cases that will cause an automatic disable:
• A SYNCH character is not sent within 13.5 ms after the initial enable pulse described in 33.3.2.1
UPDI Enable with Fuse Override of RESET Pin.
• The first SYNCH character after an initiated enable is too short or too long to register as a valid
SYNCH character. See Table 33-2 for recommended baud rate operating ranges.
33.3.2.4 Output Enable Timer Protection for GPIO Configuration
When the RESET Pin Configuration (RSTPINCFG) bits in FUSE.SYSCFG0 are 0x0, the RESET pin is
configured as GPIO. To avoid a potential conflict between the GPIO actively driving the output and a 12V
UPDI enable sequence initiation, the GPIO output driver is disabled for 768 OSC32K cycles after a
System Reset. Enable any interrupts for this pin only after this period.
It is always recommended to issue a System Reset before entering the 12V programming sequence.
33.3.2.5 UPDI Communication Error Handling
The UPDI contains a comprehensive error detection system that provides information to the debugger
when recovering from an error scenario. The error detection consists of detecting physical transmission
errors like start bit error, parity error, contention error, and frame error, to more high-level errors like
access time-out error. See the PESIG bits in UPDI_STATUSB for an overview of the available error
signatures.
Whenever the UPDI detects an error, it will immediately transfer to an internal error state to avoid
unwanted system communication. In the error state, the UPDI will ignore all incoming data requests,
except if a BREAK character is transmitted. The following procedure should always be applied when
recovering from an error condition.
• Send a BREAK character. See 33.3.1.2 BREAK Character for recommended BREAK character
handling.
• Send a SYNCH character at the desired baud rate for the next data transfer. Upon receiving a
BREAK the UPDI oscillator setting in UPDI.ASI_CTRLA is reset to the 4 MHz default UPDI clock
selection. This affects the baud rate range of the UPDI according to Table 33-2.
• Do a Load Control Status (LDCS) to UPDI.STATUSB register to read the PESIG field. PESIG gives
information about the occurred error, and the error signature will be cleared when read.
• The UPDI is now recovered from the error state and ready to receive the next SYNCH character and
instruction.
33.3.2.6 Direction Change
In order to ensure correct timing for half duplex UART operation, the UPDI has a built-in Guard Time
mechanism to relax the timing when changing direction from RX mode to TX mode. The Guard Time is a
number of IDLE bits inserted before the next Start bit is transmitted. The number of IDLE bits can be
configured through GTVAL in UPDI.CTRLA. The duration of each IDLE bit is given by the baud rate used
by the current transmission.
It is not recommended to use GTVAL setting 0x7, with no additional IDLE bits.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 515
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-7. UPDI Direction Change by Inserting IDLE Bits
RX Data Frame
St
R X D a ta F ra m e
Dir Change
P
Data from
debugger to UPDI
S1
S2
I D L E b it s
TX Data Frame
St
T X D a ta F r a m e
G uard Tim e #
IDLE bits inserted
P
S1
S2
Data from UPDI to
debugger
The UPDI Guard Time is the minimum IDLE time that the connected debugger will experience when
waiting for data from the UPDI. Because of the asynchronous interface to the system, as presented in
33.2.2.1 Clocks, the ratio between the UPDI clock and the system clock will affect the synchronization
time, and how long it takes before the UPDI can transmit data. In the cases where the synchronization
delay is shorter than the current Guard Time setting, the Guard Time will be given by GTVAL directly.
33.3.3
UPDI Instruction Set
Communication through the UPDI is based on a small instruction set. The instructions are used to access
the internal UPDI and ASI Control and Status (CS) space, as well as the memory mapped system space.
All instructions are byte instructions and must be preceded by a SYNCH character to determine the baud
rate for the communication. See 33.3.1.1 UPDI UART for information about setting the baud rate for the
transmission. The following figure gives an overview of the UPDI instruction set.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 516
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-8. UPDI Instruction Set Overview
Opcode
L DS
STS
0
0
0
1
Size A
0
0
0
0
Opcode
LD
ST
0
0
0
1
Ptr
1
1
Size B
Size A/B
0
STCS
1
1
0
1
0
0
0
0
0
LD S
0
0
1
LD
0
1
0
STS
0
1
1
ST
1
0
0
L D C S ( L D S C o n t r o l/ S ta t u s )
1
0
1
REPEAT
1
1
0
S T C S ( S T S C o n tr o l/ S ta t u s )
1
1
1
KEY
S ize A - A d d re s s s ize
0
CS Address
L DCS
OPCODE
0
0
0
0
B y te
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
1
R e s e rv e d
P tr - P o in ter a c c es s
0
0
* (p tr)
0
1
* (p tr+ + )
1
0
p tr
1
1
R e s e rv e d
S ize B - D ata s ize
Size B
REPEA T
1
0
1
0
0
0
SIB
K EY
1
1
1
0
0
Size C
0
0
B y te
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
1
R e s e rv e d
C S A d d r e s s (C S - C o n t r o l /S t a t u s r e g .)
0
0
0
0
R eg 0
0
0
0
1
R eg 1
0
0
1
0
R eg 2
0
0
1
1
R eg 3
0
1
0
0
R e g 4 (A S I C S s p a c e )
......
1
1
1
1
R e s e rv e d
S ize C - K ey s ize
0
0
0
1
6 4 b it s ( 8 B y t e s )
1 2 8 b it s ( 1 6 B y t e s )
1
0
R e s e rv e d
1
1
R e s e rv e d
S IB – S y s t e m I n f o r m a t i o n B l o c k s e l .
© 2019 Microchip Technology Inc.
0
R e c e iv e K E Y
1
S e n d S IB
Preliminary Datasheet
40001997C-page 517
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.3.3.1 LDS - Load Data from Data Space Using Direct Addressing
The LDS instruction is used to load data from the bus matrix and into the serial shift register for serial
readout. The LDS instruction is based on direct addressing, and the address must be given as an
operand to the instruction for the data transfer to start. Maximum supported size for address and data is
16 bits. LDS instruction supports repeated memory access when combined with the REPEAT instruction.
As shown in Figure 33-9, after issuing the SYNCH character followed by the LDS instruction, the number
of desired address bytes, as indicated by the Size A field in the instruction, must be transmitted. The
output data size is selected by the Size B field and is issued after the specified Guard Time. When
combined with the REPEAT instruction, the address must be sent in for each iteration of the repeat,
meaning after each time the output data sampling is done. There is no automatic address increment
when using REPEAT with LDS, as it uses a direct addressing protocol.
Figure 33-9. LDS Instruction Operation
OPCODE
Size A
Size B
S ize A - A d d re s s s ize
0
L DS
0
0
0
0
0
B y te
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
1
R e s e rv e d
S ize B - D ata s ize
0
0
B y te
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
1
R e s e rv e d
ADR SIZE
Synch
(0x55)
LDS
A d r_ 0
Rx
A d r_ n
D a ta _ 0
D a ta _ n
Tx
ΔGT
33.3.3.2 STS - Store Data to Data Space Using Direct Addressing
The STS instruction is used to store data that is shifted serially into the PHY layer to the bus matrix
address space. The STS instruction is based on direct addressing, where the address is the first set of
operands, and data is the second set. The size of the address and data operands are given by the size
fields presented in the figure below. The maximum size for both address and data is 16 bits.
STS supports repeated memory access when combined with the REPEAT instruction.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 518
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-10. STS Instruction Operation
OPCODE
Size A
Size B
S ize A - A d d re s s s ize
0
STS
1
0
0
0
0
B y te
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
1
R e s e rv e d
S ize B - D ata s ize
0
0
B y te
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
1
R e s e rv e d
ADR SIZE
Synch
(0x55)
STS
A d r_ 0
DATA SIZE
A d r_ n
D a ta _ 0
Rx
D a ta _ n
ACK
ΔGT
ACK
Tx
ΔGT
The transfer protocol for an STS instruction is depicted in the figure as well, following this sequence:
1.
2.
3.
The address is sent.
An Acknowledge (ACK) is sent back from the UPDI if the transfer was successful.
The number of bytes as specified in the STS instruction is sent.
4.
A new ACK is received after the data has been successfully transferred.
33.3.3.3 LD - Load Data from Data Space Using Indirect Addressing
The LD instruction is used to load data from the bus matrix and into the serial shift register for serial
readout. The LD instruction is based on indirect addressing, which means that the Address Pointer in the
UPDI needs to be written prior to bus matrix access. Automatic pointer post-increment operation is
supported and is useful when the LD instruction is used with REPEAT. It is also possible to do an LD of the
UPDI Pointer register. The maximum supported size for address and data load is 16 bits.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 519
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-11. LD Instruction Operation
OPCODE
LD
Synch
(0x55)
0
0
Ptr
1
Size A/B
P tr - P o in ter a c c es s
0
0
0
* (p tr)
0
1
* (p tr+ + )
1
0
p tr
1
1
R e s e rv e d
S ize A - A d d re s s s ize
S ize B - D ata s ize
0
0
B y te
0
0
B y te
0
1
W o rd (2 B y te s )
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
0
R e s e rv e d
1
1
R e s e rv e d
1
1
R e s e rv e d
LD
DATA SIZE
D a ta _ 0
Rx
D a ta _ n
Tx
ΔGT
The figure above shows an example of a typical LD sequence, where data is received after the Guard
Time period. Loading data from the UPDI Pointer register follows the same transmission protocol.
33.3.3.4 ST - Store Data from Data Space Using Indirect Addressing
The ST instruction is used to store data that is shifted serially into the PHY layer to the bus matrix address
space. The ST instruction is based on indirect addressing, which means that the Address Pointer in the
UPDI needs to be written prior to bus matrix access. Automatic pointer post-increment operation is
supported, and is useful when the ST instruction is used with REPEAT. ST is also used to store the UPDI
Address Pointer into the Pointer register. The maximum supported size for storing address and data is 16
bits.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 520
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-12. ST Instruction Operation
OPCODE
ST
0
1
Ptr
1
Size A/B
P tr - P o in ter a c c es s
0
0
0
* (p tr)
0
1
* (p tr+ + )
1
0
p tr
1
1
R e s e rv e d
S ize A - A d d re s s s ize
S ize B - D ata s ize
0
0
B y te
0
0
B y te
0
1
W o rd (2 B y te s )
0
1
W o rd (2 B y te s )
1
0
R e s e rv e d
1
0
R e s e rv e d
1
1
R e s e rv e d
1
1
R e s e rv e d
ADDRESS_SIZE
Synch
(0x55)
ST
ADR _0
ADR _n
Rx
ACK
Tx
ΔGT
Block SIZE
Synch
(0x55)
ST
D a ta _ 0
Rx
D a ta _ n
ACK
Tx
ΔGT
The figure above gives an example of ST to the UPDI Pointer register and store of regular data. In both
cases, an Acknowledge (ACK) is returned by the UPDI if the store was successful and a SYNCH
character is sent before each instruction. To write the UPDI Pointer register, the following procedure
should be followed:
• Set the PTR field in the ST instruction to the signature 0x2
• Set the address size field Size A to the desired address size
• After issuing the ST instruction, send Size A bytes of address data
• Wait for the ACK character, which signifies a successful write to the Address register
After the Address register is written, sending data is done in a similar fashion:
• Set the PTR field in the ST instruction to the signature 0x0 to write to the address specified by the
UPDI Pointer register. If the PTR field is set to 0x1, the UPDI pointer is automatically updated to the
next address according to the data size Size B field of the instruction after the write is executed
• Set the Size B field in the instruction to the desired data size
• After sending the ST instruction, send Size B bytes of address data
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 521
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
• Wait for the ACK character which signifies a successful write to the bus matrix
When used with the REPEAT, it is recommended to set up the address register with the start address for
the block to be written and use the Pointer Post Increment register to automatically increase the address
for each repeat cycle. When using REPEAT, the data frame of Size B data bytes can be sent after each
received ACK.
33.3.3.5 LCDS - Load Data from Control and Status Register Space
The LCDS instruction is used to load data from the UPDI and ASI CS-space. LCDS is based on direct
addressing, where the address is part of the instruction opcode. The total address space for LCDS is 16
bytes and can only access the internal UPDI register space. This instruction only supports byte access
and the data size is not configurable.
Figure 33-13. LCDS Instruction Operation
OPCODE
L DCS
1
0
CS Address
0
CS Address (CS - Control/Status reg.)
0 0 0 0 Reg 0
0 0 0 1 Reg 1
0 0 1 0 Reg 2
0 0 1 1 Reg 3
0 1 0 0 Reg 4 (ASI CS Space)
......
1 1 1 1 Reserved
0
Synch
(0x55)
LDCS
Rx
Data
Tx
Δgt
The figure above shows a typical example of LCDS data transmission. A data byte from the LCDS space is
transmitted from the UPDI after the Guard Time is completed.
33.3.3.6 STCS (Store Data to Control and Status Register Space)
The STCS instruction is used to store data to the UPDI and ASI CS-space. STCS is based on direct
addressing, where the address is part of the instruction opcode. The total address space for STCS is 16
bytes, and can only access the internal UPDI register space. This instruction only supports byte access,
and data size is not configurable.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 522
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-14. STCS Instruction Operation
OPCODE
STCS
1
1
CS Address
0
C S A d d r e s s (C S - C o n t r o l /S t a t u s r e g .)
0
Synch
(0x55)
STCS
0
0
0
0
R eg 0
0
0
0
1
R eg 1
0
0
1
0
R eg 2
0
0
1
1
R eg 3
0
1
0
0
R e g 4 (A S I C S S p a c e )
......
1
1
1
1
R e s e rv e d
D a ta
Rx
Tx
Figure 33-14 shows the data frame transmitted after the SYNCH and instruction frames. There is no
response generated from the STCS instruction, as is the case for ST and STS.
33.3.3.7 REPEAT - Set Instruction Repeat Counter
The REPEAT instruction is used to store the repeat count value into the UPDI Repeat Counter register.
When instructions are used with REPEAT, protocol overhead for SYNCH and Instruction Frame can be
omitted on all instructions except the first instruction after the REPEAT is issued. REPEAT is most useful
for memory instructions (LD, ST, LDS, STS), but all instructions can be repeated, except the REPEAT
instruction itself.
The DATA_SIZE opcode field refers to the size of the repeat value. Only byte size (up to 255 repeats) is
supported. The instruction that is loaded directly after the REPEAT instruction will be repeated RPT_0
times. The instruction will be issued a total of RPT_0 + 1 times. An ongoing repeat can only be aborted
by sending a BREAK character.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 523
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-15. REPEAT Instruction Operation
OPCODE
REPEA T
1
0
Size B
1
0
0
0
S ize B - D ata s ize
0
0
B y te
0
1
R e s e rv e d
1
0
R e s e rv e d
1
1
R e s e rv e d
REPEAT SIZE
Synch
(0x55)
REPEA T
RPT_0
Rpt nr of Blocks of DATA_SIZE
DATA_SIZE
Synch
(0x55)
ST
(p t r + + )
D a ta _ 0
D a ta _ n
DATA_SIZE
DATA_SIZE
D a ta B _ 1
D a ta B _ n
Rx
ACK
Δd
ACK
Δd
Δd
Δd
Tx
Δd
The figure above gives an example of repeat operation with an ST instruction using pointer postincrement operation. After the REPEAT instruction is sent with RPT_0 = n, the first ST instruction is
issued with SYNCH and Instruction frame, while the next n ST instructions are executed by only sending
in data bytes according to the ST operand DATA_SIZE, and maintaining the Acknowledge (ACK)
handshake protocol.
If using indirect addressing instructions (LD/ST) it is recommended to always use the pointer post
increment option when combined with REPEAT. Otherwise, the same address will be accessed in all
repeated access operations. For direct addressing instructions (LDS/STS), the address must always be
transmitted as specified in the instruction protocol, before data can be received (LDS) or sent (STS).
33.3.3.8 KEY - Set Activation KEY
The KEY instruction is used for communicating KEY bytes to the UPDI, opening up for executing
protected features on the device. See Table 33-5 for an overview of functions that are activated by KEYs.
For the KEY instruction, only 64-bit KEY size is supported. If the System Information Block (SIB) field of
the KEY instruction is set, the KEY instruction returns the SIB instead of expecting incoming KEY bytes.
Maximum supported size for SIB is 128 bits.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 524
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
Figure 33-16. KEY Instruction Operation
SIB
K EY
1
1
1
0
Size C
0
S ize C - K ey s ize
0
0
6 4 b it s ( 8 B y t e s )
0
1
1 2 8 b it s ( 1 6 B y t e s ) ( S IB o n ly )
1
0
R e s e rv e d
1
1
R e s e rv e d
S IB – S y s t e m I n f o r m a t i o n B l o c k s e l .
0
Send KEY
1
R e c e iv e S I B
KEY SIZE
Synch
(0x55)
K EY
KEY_0
KEY_n
Rx
Tx
Synch
(0x55)
Rx
K EY
S IB _ 0
Δgt
S IB _ n
Tx
SIB SIZE
The figure above shows the transmission of a KEY and the reception of a SIB. In both cases, the SIZE_C
field in the opcode determines the number of frames being sent or received. There is no response after
sending a KEY to the UPDI. When requesting the SIB, data will be transmitted from the UPDI according to
the current Guard Time setting.
33.3.4
System Clock Measurement with UPDI
It is possible to use the UPDI to get an accurate measurement of the system clock frequency, by using
the UPDI event connected to TCB with Input Capture capabilities. A recommended setup flow for this
feature is given by the following steps:
• Set up TCBn.CTRLB with setting CNTMODE=0x3, Input Capture Frequency Measurement mode.
• Write CAPTEI=1 in TCBn.EVCTRL to enable Event Interrupt. Keep EDGE = 0 in TCBn.EVCTRL.
• Configure the Event System as described in 33.3.8 Events.
• For the SYNCH character used to generate the UPDI events, it is recommended to use a slow baud
rate in the range of 10 kbps - 50 kbps to get a more accurate measurement on the value captured by
the timer between each UPDI event. One particular thing is that if the capture is set up to trigger an
interrupt, the first captured value should be ignored. The second captured value based on the input
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 525
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
event should be used for the measurement. See the figure below for an example using 10 kbps UPDI
SYNCH character pulses, giving a capture window of 200 µs for the timer.
• It is possible to read out the captured value directly after the SYNCH character by reading the
TCBn.CCMP register or the value can be written to memory by the CPU once the capture is done.
Figure 33-17. UPDI System Clock Measurement Events
Ignore first
capture event
200us
UPDI_
Input
TCB_CCMP
33.3.5
CAPT_1
CAPT_2
CAPT_3
Interbyte Delay
When loading data with the UPDI, or reading out the System Information Block, the output data will
normally appear with two IDLE bits between each transmitted byte for a multibyte transfer. Depending on
the application on the receiver side, data might be coming out too fast when there are no extra IDLE bits
between each byte. By enabling the IBDLY feature in UPDI.CTRLB, two extra Stop bits will be inserted
between each byte to relax the sampling time for the debugger. Interbyte delay works in the same way as
a guard time, by inserting extra IDLE bits, but only a fixed number of IDLE bits and only for multibyte
transfers. The first transmitted byte after a direction change will be subject to the regular Guard Time
before it is transmitted, and the interbyte delay is not added to this time.
Figure 33-18. Interbyte Delay Example with LD and RPT
Too fast transm ission, no interbyte delay
RX
Debugger
Data
TX
RPT
CNT
LD*(ptr)
GT
Debugger
Processing
S
D0
B
D1
S
B
D2
D1lots
D0
S
B
D3
S
B
D4
D1lost
D2
S
B
D5
S
B
D4
Data sam pling ok with interbyte delay
RX
Debugger
Data
TX
RPT
CNT
Debugger
Processing
LD*(ptr)
GT
S IB
B
D0
D0
S IB
B
D1
D1
D2
D2
S IB
B
D3
S
B
D3
GT denotes the Guard Time insertion, SB is for Stop bit and IB is the inserted interbyte delay. The rest of
the frames are data and instructions.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 526
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.3.6
System Information Block
The System Information Block (SIB) can be read out at any time by setting the SIB bit in the KEY
instruction from 33.3.3.8 KEY - Set Activation KEY. The SIB provides a compact form of providing
information for the debugger, which is vital in identifying and setting up the proper communication channel
with the part. The output of the SIB should be interpreted as ASCII symbols. The KEY size field should be
set to 16 bytes when reading out the complete SIB, and an 8-byte size can be used to read out only the
Family_ID. See Figure 33-19 for SIB format description, and which data is available at different readout
sizes.
Figure 33-19. System Information Block Format
16 8
33.3.7
[Byte][Bits]
[6:0] [55:0]
[7][7:0]
[10:8][23:0]
[13:11][23:0]
[14][7:0]
[15][7:0]
Field Name
Family_ID
Reserved
NVM_VERSION
OCD_VERSION
RESERVED
DBG_OSC_FREQ
Enabling of KEY Protected Interfaces
Access to some internal interfaces and features are protected by the UPDI KEY mechanism. To activate
a KEY, the correct KEY data must be transmitted by using the KEY instruction as described in KEY
instruction. The following table describes the available KEYs, and the condition required when doing the
operation with the KEY active. There is no requirement when shifting in the KEY, but you would, for
instance, normally run a Chip Erase before enabling the NVMPROG KEY to unlock the device for
debugging. But if the NVMPROGKEY is shifted in first, it will not be reset by shifting in the Chip Erase
KEY afterward.
Table 33-5. KEY Activation Overview
KEY Name
Description
Requirements for
Operation
Reset
Chip Erase
Start NVM Chip erase.
Clear Lockbits
None
UPDI Disable/UPDI
Reset
NVMPROG
Activate NVM
Programming
Lockbits Cleared.
Programming Done/
ASI_SYS_STATUS.NVM UPDI Reset
PROG set.
USERROW-Write
Program User Row on
Locked part
Lockbits Set.
Write to KEY status bit/
ASI_SYS_STATUS.URO UPDI Reset
WPROG set.
The next table gives an overview of the available KEY signatures that must be shifted in to activate the
interfaces.
Table 33-6. KEY Activation Signatures
KEY Name
KEY Signature (LSB Written
First)
Size
Chip Erase
0x4E564D4572617365
64 bits
NVMPROG
0x4E564D50726F6720
64 bits
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 527
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
...........continued
KEY Name
KEY Signature (LSB Written
First)
Size
USERROW-Write
0x4E564D5573267465
64 bits
33.3.7.1 Chip Erase
The following steps should be followed to issue a Chip Erase.
1. Enter the CHIPERASE KEY by using the KEY instruction. See Table 33-6 for the CHIPERASE
signature.
2.
3.
4.
5.
6.
Optional: Read the Chip Erase bit in the AS Key Status register (CHIPERASE in
UPDI.ASI_KEY_STATUS) to see that the KEY is successfully activated.
Write the Reset signature into the UPDI.ASI_RESET_REQ register. This will issue a System Reset.
Write 0x00 to the ASI Reset Request register (UPDI.ASI_RESET_REQ) to clear the System Reset.
Read the Lock Status bit in the ASI System Status register (LOCKSTATUS in
UPDI.ASI_SYS_STATUS).
Chip Erase is done when LOCKSTATUS == 0 in UPDI.ASI_SYS_STATUS. If LOCKSTATUS == 1,
go to point 5 again.
After a successful Chip Erase, the Lockbits will be cleared, and the UPDI will have full access to the
system. Until Lockbits are cleared, the UPDI cannot access the system bus, and only CS-space
operations can be performed.
CAUTION
During Chip Erase, the BOD is forced ON (ACTIVE=0x1 in BOD.CTRLA) and uses the BOD
Level from the BOD Configuration fuse (LVL in BOD.CTRLB = LVL in FUSE.BODCFG). If the
supply voltage VDD is below that threshold level, the device is unserviceable until VDD is
increased adequately.
33.3.7.2 NVM Programming
If the device is unlocked, it is possible to write directly to the NVM Controller using the UPDI. This will
lead to unpredictable code execution if the CPU is active during the NVM programming. To avoid this, the
following NVM Programming sequence should be executed.
1.
2.
Follow the Chip Erase procedure as described in Chip Erase. If the part is already unlocked, this
point can be skipped.
Enter the NVMPROG KEY by using the KEY instruction. See Table 33-6 for the NVMPROG
signature.
3.
Optional: Read the NVMPROG field in the KEY_STATUS register to see that the KEY has been
activated.
4. Write the Reset signature into the ASI_RESET_REQ register. This will issue a System Reset.
5. Write 0x00 to the Reset signature in the ASI_RESET_REQ register to clear the System Reset.
6. Read NVMPROG in ASI_SYS_STATUS.
7. NVM Programming can start when NVMPROG == 1 in the ASI_SYS_STATUS register. If
NVMPROG == 0, go to point 6 again.
8. Write data to NVM through the UPDI.
9. Write the Reset signature into the ASI_RESET_REQ register. This will issue a System Reset.
10. Write 0x00 to the Reset signature in the ASI_RESET_REQ register to clear the System Reset.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 528
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
11. Programming is complete.
33.3.7.3 User Row Programming
The User Row Programming feature allows the user to program new values to the User Row
(USERROW) on a locked device. To program with this functionality enabled, the following sequence
should be followed.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Enter the USERROW-Write KEY located in Table 33-6 by using the KEY instruction. See Table 33-6
for the UROWWRITE signature.
Optional: Read the UROWWRITE bit field in UPDI.ASI_KEY_STATUS to see that the KEY has
been activated.
Write the Reset signature into the UPDI.ASI_RESET_REQ register. This will issue a System Reset.
Write 0x00 to the Reset signature in the UPDI.ASI_RESET_REQ register to clear the System
Reset.
Read the UROWPROG bit in UPDI.ASI_SYS_STATUS.
User Row Programming can start when UROWPROG == 1. If UROWPROG == 0, go to point 5
again.
The writable area has a size of one EEPROM page, 64/32 bytes, and it is only possible to write
User Row data to the first 64/32 byte addresses of the RAM. Addressing outside this memory range
will result in a non-executed write. The data will map 1:1 with the User Row space when the data is
copied into the User Row upon completion of the Programming sequence.
When all User Row data has been written to the RAM, write the UROWWRITEFINAL bit in
UPDI.ASI_SYS_CTRLA.
Read the UROWPROG bit in UPDI.ASI_SYS_STATUS.
The User Row Programming is completed when UROWPROG == 0. If UROWPROG == 1, go to
point 9 again.
Write the UROWWRITE bit in UPDI.ASI_KEY_STATUS.
Write the Reset signature into the UPDI.ASI_RESET_REQ register. This will issue a System Reset.
Write 0x00 to the Reset signature in the UPDI.ASI_RESET_REQ register to clear the System
Reset.
User Row Programming is complete.
It is not possible to read back data from the SRAM in this mode. Only writing to the first 32 bytes of the
SRAM is allowed.
33.3.8
Events
The UPDI is connected to the Event System (EVSYS) as described in the register Asynchronous Channel
n Generator Selection.
The UPDI can generate the following output events:
• SYNCH Character Positive Edge Event
This event is set on the UPDI clock for each detected positive edge in the SYNCH character, and it is not
possible to disable this event from the UPDI. The recommended application for this event is system clock
frequency measurement through the UPDI. Section 33.3.4 System Clock Measurement with UPDI
provides the details on how to set up the system for this operation.
Related Links
14. EVSYS - Event System
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 529
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.3.9
Sleep Mode Operation
The UPDI physical layer runs independently of all sleep modes and the UPDI is always accessible for a
connected debugger independent of the device sleep mode. If the system enters a sleep mode that turns
the CPU clock OFF, the UPDI will not be able to access the system bus and read memories and
peripherals. The UPDI physical layer clock is unaffected by the sleep mode settings, as long as the UPDI
is enabled. By reading the INSLEEP bit in UPDI.ASI_SYS_STATUS it is possible to monitor if the system
domain is in sleep mode. The INSLEEP bit is set if the system is in IDLE Sleep mode or deeper.
It is possible to prevent the system clock from stopping when going into sleep mode, by writing the
CLKREQ bit in UPDI.ASI_SYS_CTRL to ‘1’. If this bit is set, the system sleep mode state is emulated,
and it is possible for the UPDI to access the system bus and read the peripheral registers even in the
deepest sleep modes.
CLKREQ in UPDI.ASI_SYS_CTRL is by default ‘1’, which means that the default operation is keeping the
system clock on during sleep modes.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 530
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.4
Register Summary - UPDI
Offset
Name
Bit Pos.
0x00
0x01
0x02
0x03
0x04
...
0x06
0x07
0x08
0x09
STATUSA
STATUSB
CTRLA
CTRLB
7:0
7:0
7:0
7:0
ASI_KEY_STATUS
ASI_RESET_REQ
ASI_CTRLA
7:0
7:0
7:0
0x0A
ASI_SYS_CTRLA
7:0
0x0B
0x0C
ASI_SYS_STATUS
ASI_CRC_STATUS
7:0
7:0
33.5
UPDIREV[3:0]
IBDLY
PARD
DTD
NACKDIS
RSD
CCDETDIS
PESIG[2:0]
GTVAL[2:0]
UPDIDIS
Reserved
UROWWRITE NVMPROG CHIPERASE
RSTREQ[7:0]
RSTSYS
INSLEEP
UPDICLKSEL[1:0]
UROWWRITE
CLKREQ
_FINAL
NVMPROG UROWPROG
LOCKSTATUS
CRC_STATUS[2:0]
Register Description
These registers are readable only through the UPDI with special instructions and are NOT readable
through the CPU.
Registers at offset addresses 0x0-0x3 are the UPDI Physical configuration registers.
Registers at offset addresses 0x4-0xC are the ASI level registers.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 531
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.1
Status A
Name:
Offset:
Reset:
Property:
STATUSA
0x00
0x10
-
Bit
7
6
5
4
Access
R
R
Reset
0
R
R
0
0
1
3
2
1
0
UPDIREV[3:0]
Bits 7:4 – UPDIREV[3:0] UPDI Revision
These bits are read-only and contain the revision of the current UPDI implementation.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 532
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.2
Status B
Name:
Offset:
Reset:
Property:
Bit
STATUSB
0x01
0x00
-
7
6
5
4
3
2
1
0
PESIG[2:0]
Access
R
R
R
Reset
0
0
0
Bits 2:0 – PESIG[2:0] UPDI Error Signature
These bits describe the UPDI Error Signature and are set when an internal UPDI error condition occurs.
The PESIG field is cleared on a read from the debugger.
Table 33-7. Valid Error Signatures
PESIG[2:0] Error Type
Error Description
0x0
No error
No error detected (Default)
0x1
Parity error
Wrong sampling of the parity bit
0x2
Frame error
Wrong sampling of frame Stop bits
0x3
Access Layer Time-out Error UPDI can get no data or response from the Access layer.
Examples of error cases are system domain in Sleep or
system domain Reset.
0x4
Clock Recovery error
Wrong sampling of frame Start bit
0x5
-
Reserved
0x6
Reserved
Reserved
0x7
Contention error
Signalize Driving Contention on the UPDI RXD/TXD line
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 533
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.3
Control A
Name:
Offset:
Reset:
Property:
Bit
Access
Reset
7
CTRLA
0x02
0x00
-
6
5
4
3
2
1
0
IBDLY
PARD
DTD
RSD
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
GTVAL[2:0]
Bit 7 – IBDLY Inter-Byte Delay Enable
Writing a '1' to this bit enables a fixed inter-byte delay between each data byte transmitted from the UPDI
when doing multi-byte LD(S). The fixed length is two IDLE characters. Before the first transmitted byte,
the regular GT delay used for direction change will be used.
Bit 5 – PARD Parity Disable
Writing this bit to '1' will disable parity detection in the UPDI by ignoring the Parity bit. This feature is
recommended only during testing.
Bit 4 – DTD Disable Time-out Detection
Setting this bit disables the time-out detection on the PHY layer, which requests a response from the ACC
layer within a specified time (65536 UPDI clock cycles).
Bit 3 – RSD Response Signature Disable
Writing a '1' to this bit will disable any response signatures generated by the UPDI. This is to reduce the
protocol overhead to a minimum when writing large blocks of data to the NVM space. Disabling the
Response Signature should be used with caution, and only when the delay experienced by the UPDI
when accessing the system bus is predictable, otherwise loss of data may occur.
Bits 2:0 – GTVAL[2:0] Guard Time Value
This bit field selects the Guard Time Value that will be used by the UPDI when the transmission mode
switches from RX to TX.
Value
Description
0x0
UPDI Guard Time: 128 cycles (default)
0x1
UPDI Guard Time: 64 cycles
0x2
UPDI Guard Time: 32 cycles
0x3
UPDI Guard Time: 16 cycles
0x4
UPDI Guard Time: 8 cycles
0x5
UPDI Guard Time: 4 cycles
0x6
UPDI Guard Time: 2 cycles
0x7
GT off (no extra Idle bits inserted)
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 534
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.4
Control B
Name:
Offset:
Reset:
Property:
Bit
7
CTRLB
0x03
0x00
-
6
5
4
3
2
NACKDIS
CCDETDIS
UPDIDIS
Access
R
R
R
Reset
0
0
0
1
0
Bit 4 – NACKDIS Disable NACK Response
Writing this bit to '1' disables the NACK signature sent by the UPDI if a System Reset is issued during an
ongoing LD(S) and ST(S) operation.
Bit 3 – CCDETDIS Collision and Contention Detection Disable
If this bit is written to '1', contention detection is disabled.
Bit 2 – UPDIDIS UPDI Disable
Writing a '1' to this bit disables the UPDI PHY interface. The clock request from the UPDI is lowered, and
the UPDI is reset. All UPDI PHY configurations and KEYs will be reset when the UPDI is disabled.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 535
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.5
ASI Key Status
Name:
Offset:
Reset:
Property:
Bit
7
ASI_KEY_STATUS
0x07
0x00
-
6
Access
Reset
5
4
3
UROWWRITE
NVMPROG
CHIPERASE
R/W
R
R
0
0
0
2
1
0
Bit 5 – UROWWRITE User Row Write Key Status
This bit is set to '1' if the UROWWRITE KEY is active. Otherwise, this bit reads as zero.
Bit 4 – NVMPROG NVM Programming
This bit is set to '1' if the NVMPROG KEY is active. This bit is automatically reset after the programming
sequence is done. Otherwise, this bit reads as zero.
Bit 3 – CHIPERASE Chip Erase
This bit is set to '1' if the CHIPERASE KEY is active. This bit will automatically be reset when the Chip
Erase sequence is completed. Otherwise, this bit reads as zero.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 536
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.6
ASI Reset Request
Name:
Offset:
Reset:
Property:
Bit
ASI_RESET_REQ
0x08
0x00
-
7
6
5
4
3
2
1
0
R/W
R/W
R/W
R/W
0
0
0
R/W
R/W
R/W
R/W
0
0
0
0
0
RSTREQ[7:0]
Access
Reset
Bits 7:0 – RSTREQ[7:0] Reset Request
A Reset is signalized to the system when writing the Reset signature 0x59h to this address.
Writing any other signature to this register will clear the Reset.
When reading this register, reading bit RSTREQ[0] will tell if the UPDI is holding an active Reset on the
system. If this bit is '1', the UPDI has an active Reset request to the system. All other bits will read as '0'.
The UPDI will not be reset when issuing a system Reset from this register.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 537
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.7
ASI Control A
Name:
Offset:
Reset:
Property:
Bit
7
ASI_CTRLA
0x09
0x02
-
6
5
4
3
2
1
0
UPDICLKSEL[1:0]
Access
Reset
R/W
R/W
1
1
Bits 1:0 – UPDICLKSEL[1:0] UPDI Clock Select
Writing these bits select the UPDI clock output frequency. Default setting after Reset and enable is 4
MHz. Any other clock output selection is only recommended when the BOD is at the highest level. For all
other BOD settings, the default 4 MHz selection is recommended.
Value
Description
0x0
Reserved
0x1
16 MHz UPDI clock
0x2
8 MHz UPDI clock
0x3
4 MHz UPDI clock (Default Setting)
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 538
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.8
ASI System Control A
Name:
Offset:
Reset:
Property:
Bit
7
ASI_SYS_CTRLA
0x0A
0x00
-
6
5
4
3
2
1
0
UROWWRITE_
CLKREQ
FINAL
Access
R
R
R
R
R
R
R/W
R/W
Reset
0
0
0
0
0
0
0
0
Bit 1 – UROWWRITE_FINAL User Row Programming Done
This bit should be written through the UPDI when the user row data has been written to the RAM. Writing
this bit will start the process of programming the user row data to the Flash.
If this bit is written before the User Row code is written to RAM by the UPDI, the CPU will progress
without the written data.
This bit is only writable if the User Row-write KEY is successfully decoded.
Bit 0 – CLKREQ Request System Clock
If this bit is written to '1', the ASI is requesting the system clock, independent of system Sleep modes.
This makes it possible for the UPDI to access the ACC layer, also if the system is in Sleep mode.
Writing a '0' to this bit will lower the clock request.
This bit will be reset when the UPDI is disabled.
This bit is set by default when the UPDI is enabled in any mode (Fuse, 12V).
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 539
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.9
ASI System Status
Name:
Offset:
Reset:
Property:
Bit
7
ASI_SYS_STATUS
0x0B
0x01
-
6
5
4
3
2
1
0
RSTSYS
INSLEEP
NVMPROG
UROWPROG
LOCKSTATUS
Access
R
R
R
R
R
Reset
0
0
0
0
1
Bit 5 – RSTSYS System Reset Active
If this bit is set, there is an active Reset on the system domain. If this bit is cleared, the system is not in
Reset.
This bit is cleared on read.
A Reset held from the ASI_RESET_REQ register will also affect this bit.
Bit 4 – INSLEEP System Domain in Sleep
If this bit is set, the system domain is in IDLE or deeper Sleep mode. If this bit is cleared, the system is
not in Sleep.
Bit 3 – NVMPROG Start NVM Programming
If this bit is set, NVM Programming can start from the UPDI.
When the UPDI is done, it must reset the system through the UPDI Reset register.
Bit 2 – UROWPROG Start User Row Programming
If this bit is set, User Row Programming can start from the UPDI.
When the UPDI is done, it must write the UROWWRITE_FINAL bit in ASI_SYS_CTRLA.
Bit 0 – LOCKSTATUS NVM Lock Status
If this bit is set, the device is locked. If a Chip Erase is done, and the Lockbits are cleared, this bit will
read as '0'.
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 540
ATtiny1616/3216
UPDI - Unified Program and Debug Interface
33.5.10 ASI CRC Status
Name:
Offset:
Reset:
Property:
Bit
7
ASI_CRC_STATUS
0x0C
0x00
-
6
5
4
3
2
1
0
CRC_STATUS[2:0]
Access
R
R
R
Reset
0
0
0
Bits 2:0 – CRC_STATUS[2:0] CRC Execution Status
These bits signalize the status of the CRC conversion. The bits are one-hot encoded.
Value
Description
0x0
Not enabled
0x1
CRC enabled, busy
0x2
CRC enabled, done with OK signature
0x4
CRC enabled, done with FAILED signature
Other
Reserved
© 2019 Microchip Technology Inc.
Preliminary Datasheet
40001997C-page 541
ATtiny1616/3216
Instruction Set Summary
34.
Instruction Set Summary
Table 34-1. Arithmetic and Logic Instructions
Mnemonic
Operands
Description
ADD
Rd, Rr
Add without Carry
ADC
Rd, Rr
Add with Carry
ADIW
Rd, K
Add Immediate to Word
SUB
Rd, Rr
SUBI
Op
Flags
#Clocks
Rd
←
Rd + Rr
Z,C,N,V,S,H
1
Rd
←
Rd + Rr + C
Z,C,N,V,S,H
1
Rd + 1:Rd
←
Rd + 1:Rd + K
Z,C,N,V,S
2
Subtract without Carry
Rd
←
Rd - Rr
Z,C,N,V,S,H
1
Rd, K
Subtract Immediate
Rd
←
Rd - K
Z,C,N,V,S,H
1
SBC
Rd, Rr
Subtract with Carry
Rd
←
Rd - Rr - C
Z,C,N,V,S,H
1
SBCI
Rd, K
Subtract Immediate with Carry
Rd
←
Rd - K - C
Z,C,N,V,S,H
1
SBIW
Rd, K
Subtract Immediate from Word
Rd + 1:Rd
←
Rd + 1:Rd - K
Z,C,N,V,S
2
AND
Rd, Rr
Logical AND
Rd
←
Rd • Rr
Z,N,V,S
1
ANDI
Rd, K
Logical AND with Immediate
Rd
←
Rd • K
Z,N,V,S
1
OR
Rd, Rr
Logical OR
Rd
←
Rd v Rr
Z,N,V,S
1
ORI
Rd, K
Logical OR with Immediate
Rd
←
Rd v K
Z,N,V,S
1
EOR
Rd, Rr
Exclusive OR
Rd
←
Rd ⊕ Rr
Z,N,V,S
1
COM
Rd
One’s Complement
Rd
←
$FF - Rd
Z,C,N,V,S
1
NEG
Rd
Two’s Complement
Rd
←
$00 - Rd
Z,C,N,V,S,H
1
SBR
Rd,K
Set Bit(s) in Register
Rd
←
Rd v K
Z,N,V,S
1
CBR
Rd,K
Clear Bit(s) in Register
Rd
←
Rd • ($FFh - K)
Z,N,V,S
1
INC
Rd
Increment
Rd
←
Rd + 1
Z,N,V,S
1
DEC
Rd
Decrement
Rd
←
Rd - 1
Z,N,V,S
1
TST
Rd
Test for Zero or Minus
Rd
←
Rd • Rd
Z,N,V,S
1
CLR
Rd
Clear Register
Rd
←
Rd ⊕ Rd
Z,N,V,S
1
SER
Rd
Set Register
Rd
←
$FF
None
1
MUL
Rd,Rr
Multiply Unsigned
R1:R0
←
Rd x Rr (UU)
Z,C
2
MULS
Rd,Rr
Multiply Signed
R1:R0
←
Rd x Rr (SS)
Z,C
2
MULSU
Rd,Rr
Multiply Signed with Unsigned
R1:R0
←
Rd x Rr (SU)
Z,C
2
FMUL
Rd,Rr
Fractional Multiply Unsigned
R1:R0
←
Rd x Rr
工商网监
湘ICP备2023018690号
