ATxmega32D4 Atmel Corporation, ATxmega32D4 Datasheet - Page 46

• Manufacturer Part Number: ATxmega32D4
• Manufacturer: Atmel Corporation

Specifications of ATxmega32D4

• Flash (kbytes): 32 Kbytes
• Pin Count: 44
• Max. Operating Frequency: 32 MHz
• Cpu: 8-bit AVR
• # Of Touch Channels: 16
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 34
• Ext Interrupts: 34
• Usb Speed: No
• Usb Interface: No
• Spi: 4
• Twi (i2c): 2
• Uart: 2
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 12
• Adc Resolution (bits): 12
• Adc Speed (ksps): 200
• Analog Comparators: 2
• Resistive Touch Screen: No
• Temp. Sensor: Yes
• Crypto Engine: No
• Sram (kbytes): 4
• Eeprom (bytes): 1024
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: No
• Picopower: Yes
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 1.6 to 3.6
• Operating Voltage (vcc): 1.6 to 3.6
• Fpu: No
• Mpu / Mmu: no / no
• Timers: 4
• Output Compare Channels: 14
• Input Capture Channels: 14
• Pwm Channels: 14
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: Yes

5.3.1
5.3.2
5.3.3
5.4
8210B–AVR–04/10
Event Routing Network
Signaling Events
Data Events
Manually Generating Events
Events can be manually generated by writing to the STROBE and DATA registers.
Signaling events are the most basic type of events. A signaling event does not contain any infor-
mation apart from the indication of a change in a peripheral. Most peripherals can only generate
and use signaling events. Unless otherwise stated, all occurrences of the word 'event' is to be
understood as a signaling event.
Data events differ from signaling events in that they contain additional information that event
users can decode to decide event actions based on the receiver information.
The Event Routing Network can route all events to all event users. Event users that are only
meant for using signaling events have limited decode capabilities and cannot fully utilize data.
How event users decode data events is shown in
Event users that can utilize Data Events can also use Signaling Events. This is configurable, and
is described in the datasheet module for each peripheral.
Events can be generated manually by writing the DATA and STROBE register. This can be done
from software, and by accessing the registers directly during on-chip debugging. The DATA reg-
ister must be written first since writing the STROBE register triggers the operation. The DATA
and STROBE registers contain one bit for each event channel. Bit n corresponds to event chan-
nel n. It is possible to generate events on several channels at the same time by writing to several
bit locations at once.
Manually generated events last for one clock cycle and will overwrite events from other event
during that clock cycle. When manually generating events, event channels where no events are
entered will let other events through.
Table 5-1 on page 46
they are decoded.
Table 5-1.
The Event Routing Network routes events between peripherals. It consists of eight multiplexers
(CHnMUX), where events from all event sources are routed into all multiplexers. The multiplex-
ers select which event is routed back as input to all peripherals. The output from a multiplexer is
referred to as an Event Channel. For each peripheral it is selectable if and how incoming events
should trigger event actions. Details on these are described in the datasheet for each peripheral.
The Event Routing Network is shown on
STROBE
0
0
1
1
DATA
Manually Generated Events and decoding of events
0
1
0
1
shows the different events, how they can be manually generated and how
Data Event User
No Event
Data Event 01
Data Event 02
Data Event 03
Figure 5-3 on page
Table 5-1 on page
Signaling Event User
No Event
Signaling Event
Signaling Event
No Event
47.
46.
XMEGA D
46