ATmega32C1 Automotive Atmel Corporation, ATmega32C1 Automotive Datasheet - Page 180

• Manufacturer Part Number: ATmega32C1 Automotive
• Manufacturer: Atmel Corporation

Specifications of ATmega32C1 Automotive

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

16.5.2.4
16.5.2.5
16.5.3
180
Atmel ATmega16/32/64/M1/C1
Acceptance Filter
Automatic Reply
Frame Buffer Receive Mode
A reply (data frame) to a remote frame can be automatically sent after reception of the
expected remote frame.
This mode is useful to receive multi frames. The priority between MObs offers a management
for these incoming frames. One set MObs (including non-consecutive MObs) is created when
the MObs are set in this mode. Due to the mode setting, only one set is possible. A frame buf-
fer completed flag (or interrupt) - BXOK - will rise only when all the MObs of the set will have
received their dedicated CAN frame.
Upon a reception hit (i.e., a good comparison between the ID + RTR + RBn + IDE received and
an IDT+ RTRTAG + RBnTAG + IDE specified while taking the comparison mask into account) the
IDT + RTRTAG + RBnTAG + IDE received are updated in the MOb (written over the registers).
1. Several fields must be initialized before receiving the remote frame:
2. When a remote frame matches, automatically the RTRTAG and the reply valid bit
3. When the transmission of the reply is completed the TXOK flag is set (interrupt).
4. All the parameters and data are available in the MOb until a new initialization.
1.
2. The MObs are ready to receive data (or a remote) frames when their respective con-
3. When a frame identifier is received on CAN network, the CAN channel scans all the
4. On a hit, the IDT, the IDE and the DLC of the matched MOb are updated from the
5. Once the reception is completed, the data bytes of the received message are stored
6. When the reception in the last MOb of the set is completed, the frame buffer com-
7. All the parameters and data are available in the MObs until a new initialization.
– Reply valid (RPLV) in a identical flow to the one described in
(RPLV) are reset. No flag (or interrupt) is set at this time. Since the CAN data buffer
has not been used by the incoming remote frame, the MOb is then ready to be in
transmit mode without any more setting. The IDT, the IDE, the other tags and the
DLC of the received remote frame are used for the reply.
MObs in frame buffer receive mode need to be initialized as MObs in standard receive mode.
figurations are set (CONMOB).
MObs in receive mode, tries to find the MOb having the highest priority which is
matching.
incoming (frame) values.
(not for remote frame) in the data buffer of the matched MOb and the RXOK flag is set
(interrupt).
pleted BXOK flag is set (interrupt). BXOK flag can be cleared only if all CONMOB
fields of the set have been re-written before.
Data & Remote Frame” on page
179.
Section 16.5.2.3 “Rx
7647G–AVR–09/11