ATMEGA64M1-AU Atmel, ATMEGA64M1-AU Datasheet - Page 174

• Manufacturer Part Number: ATMEGA64M1-AU
• Description: IC MCU AVR 64K FLASH 32TQFP
• Manufacturer: Atmel
• Series: AVR® ATmegar

Specifications of ATMEGA64M1-AU

• Core Processor: AVR
• Core Size: 8-Bit
• Speed: 16MHz
• Connectivity: CAN, LIN, SPI, UART/USART
• Peripherals: Brown-out Detect/Reset, POR, PWM, Temp Sensor, WDT
• Program Memory Size: 64KB (32K x 16)
• Program Memory Type: FLASH
• Eeprom Size: 2K x 8
• Ram Size: 4K x 8
• Voltage - Supply (vcc/vdd): 2.7 V ~ 5.5 V
• Data Converters: A/D 11x10b; D/A 1x10b
• Oscillator Type: Internal
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 32-TQFP, 32-VQFP
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Number Of I /o: -
• Lead Free Status / Rohs Status: Details

19.6.2.4
19.6.2.5
174
ATmega16M1/32M1/64M1
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 buffer
completed flag (or interrupt) - BXOK - will rise only when all the MObs of the set will have
received their dedicated CAN frame.
2. The MOb is ready to receive a data or a remote frame when the MOb configuration is
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. All the parameters and data are available in the MOb until a new initialization
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. MObs in frame buffer receive mode need to be initialized as MObs in standard receive
2. The MObs are ready to receive data (or a remote) frames when their respective config-
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 (not
6. When the reception in the last MOb of the set is completed, the frame buffer completed
7. All the parameters and data are available in the MObs until a new initialization
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)
– 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
mode
urations are set (CONMOB)
MObs in receive mode, tries to find the MOb having the highest priority which is
matching
incoming (frame) values
for remote frame) in the data buffer of the matched MOb and the RXOK flag is set
(interrupt)
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 173
Section 19.6.2.3 “Rx
8209D–AVR–11/10