AT32UC3C2256C Atmel Corporation, AT32UC3C2256C Datasheet - Page 228

• Manufacturer Part Number: AT32UC3C2256C
• Manufacturer: Atmel Corporation

Specifications of AT32UC3C2256C

• Flash (kbytes): 256 Kbytes
• Pin Count: 64
• Max. Operating Frequency: 66 MHz
• Cpu: 32-bit AVR
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 45
• Ext Interrupts: 64
• Usb Transceiver: 1
• Quadrature Decoder Channels: 1
• Usb Speed: Full Speed
• Usb Interface: Device + OTG
• Spi: 5
• Twi (i2c): 2
• Uart: 4
• Can: 2
• Lin: 4
• Ssc: 1
• Ethernet: 1
• Graphic Lcd: No
• Video Decoder: No
• Camera Interface: No
• Adc Channels: 11
• Adc Resolution (bits): 12
• Adc Speed (ksps): 2000
• Analog Comparators: 2
• Resistive Touch Screen: No
• Dac Channels: 2
• Dac Resolution (bits): 12
• Temp. Sensor: No
• Crypto Engine: No
• Sram (kbytes): 68
• Self Program Memory: YES
• Dram Memory: No
• Nand Interface: No
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 3.0 to 3.6 or 4.5 to 5.5
• Operating Voltage (vcc): 3.0 to 3.6 or 4.5 to 5.5
• Fpu: Yes
• Mpu / Mmu: Yes / No
• Timers: 3
• Output Compare Channels: 13
• Input Capture Channels: 6
• Pwm Channels: 14
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: Yes

14.6
14.6.1
14.6.1.1
14.6.1.2
14.6.1.3
32117C–AVR-08/11
Functional Description
PEVC Channel Operation
Channel Setup
Channel Operation
Software Event
PEVC routes incoming events to users by means of one channel per user. Channels operate in
parallel, allowing multiple users to listen to the same generator.
The Channel Multiplexer Register (CHMXn) is written to allocate a generator to a given channel.
The Event Multiplexer field (EVMX) selects between the different generators, while the Software
Event Multiplexer bit (SMX) selects Software Events.
The channel is then enabled by writing a one to the appropriate bit in the Channel Enable Regis-
ter (CHER). It is disabled by writing a one to the appropriate bit in the Channel Disable Register
(CHDR).
To safely program a channel, user software must:
When the channel is enabled, the user signals its busy/ready state to the channel, to determine
how an incoming event will be handled:
The Busy Register (BUSY) is used to determine the current activity of a channel/user. A busy
status has one of two causes:
A Software Event can be initiated by software writing to the Software Event Register (SEV). This
is intended for application debugging.
The channel must first be programmed by writing a one to the Software Event Multiplexer bit
(SMX) of CHMXn.
Writing a one to the appropriate bit of SEV will then trigger a Software Event on the channel.
• disable the channel by writing a one to CHDR
• program CHMXn
• enable the channel by writing a one to CHER
• If the user is ready, an incoming event is forwarded. The corresponding Trigger Status
• If the user is busy (because of a previous event, or for some other cause), the new event is
• A peripheral event is being relayed by the channel and handled by the user,
• No event relayed, but user is not ready (e.g. not initialized, or handling some other request).
Register (TRISR) flag is set allowing an interrupt to be generated for tracking PEVC
operations.
not forwarded. The corresponding Overrun Status Register (OVSR) flag is set allowing an
interrupt to be generated.
AT32UC3C
228