Back to DRIVERS page
AVR UC3 Series Software Framework: ADC Driver
Copyright © 2007 Atmel Corporation
Introduction
The PEVC (Peripheral EVent Controler) offers a set of features that allows
peripherals to interact without intervention from the CPU. The PEVC connects
Event Generators to Event Users.
The PEVC software driver philosophy of usage is:
Configure one PEVC channel at a time: connect it to an Event Generator and
configure the Event Shaper if the event generator signal is an asynchronous or external signal [pevc_channel_configure]
(Note that the Event Generator peripheral and the Event User peripheral must be configured too; these configurations
are done outside the PEVC software driver)
Enable one (or several) channels, [pevc_channels_enable() or PEVC_CHANNELS_ENABLE()]
Eventually check if a channel is enabled, [pevc_get_channel_status() or PEVC_GET_CHANNEL_STATUS()]
Check the state of a channel (Idle/Busy), [pevc_get_channel_state() or PEVC_GET_CHANNEL_STATE()]
PEVC operations can be traced using the trigger interrupt API and the overrun interrupt API
Eventually enable a Software Event as event source for a channel: [pevc_channel_sev_enable() or PEVC_CHANNEL_SEV_ENABLE()]
(note that when the Software Event is enabled, the Event Generator is ignored)
Eventually trigger a Software Event to one (or several) channels: [pevc_channels_trigger_sev() or PEVC_CHANNELS_TRIGGER_SEV()]
Eventually disable a Software Event as event source for a channel: [pevc_channel_sev_disable() or PEVC_CHANNEL_SEV_DISABLE()]
Eventually disable one (or several)channels [pevc_channels_disable() or PEVC_CHANNELS_DISABLE()]
Note that each API function except pevc_channel_configure() has a macro equivalent
PEVC Driver
The driver is composed of pevc.c and pevc.h.
Examples are available:
EXAMPLE1: Control PDCA transfer using event from AST
EXAMPLE2: Control PDCA transfer uing generic clock transfert
EXAMPLE3: Control PDCA Transfer using PEVC Generic Pad
>