View detail for Atmel AT15007: Differences between ATmega328/P and ATmega328PB

Atmel AVR 8-bit Microcontrollers
AT15007: Differences between ATmega328/P and
ATmega328PB
APPLICATION NOTE
Introduction
®
This application note assists the users of Atmel ATmega328 variants to
understand the differences and use Atmel ATmega328PB.
ATmega328PB is not a drop-in replacement for ATmega328 variants, but a
new device. However, the functions are backward compatible with the
existing ATmega328 functions. Existing code for these devices will work in
the new devices without changing existing configuration or enabling new
functions. The code that is available for your existing ATmega328 variants
will continue to work on the new ATmega328PB device.
®
The ATmega328PB is the first 8-bit Atmel AVR device to feature the
®
successful Atmel QTouch Peripheral Touch Controller (PTC).
For differences in errata, typical, and electrical characteristics between
ATmega328 variants and ATmega328PB, refer to the specific device
datasheets.
For complete device details, refer to the latest version of the ATmega328PB
datasheet available at www.atmel.com.
Features
•
•
•
Pin functionality difference
Code compatibility
Enhancement and added features
Note: Code compiled for ATmega328 variants are compatible and can be
executed in the ATmega328PB device. Whereas, reverse code compatibility
is not guaranteed.
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
Table of Contents
Introduction......................................................................................................................1
Features.......................................................................................................................... 1
1. Pin Functionality Difference....................................................................................... 3
1.1.
1.2.
Additional Pin Functionalities........................................................................................................3
Alternate Pin Configuration...........................................................................................................3
2. Enhancement and Additional Features in ATmega328PB.........................................4
2.1.
2.2.
2.3.
2.4.
2.5.
2.6.
2.7.
2.8.
2.9.
PTC - Peripheral Touch Controller................................................................................................4
CFD - Clock Failure Detection mechanism.................................................................................. 5
OCM1C2 - Output Compare Modulator........................................................................................5
USART......................................................................................................................................... 5
Analog Comparator...................................................................................................................... 6
Unique Device ID..........................................................................................................................6
Additional SPI...............................................................................................................................6
Additional TWI.............................................................................................................................. 6
Additional Timer/Counters............................................................................................................ 6
3. Register Description.................................................................................................. 7
3.1.
3.2.
3.3.
3.4.
3.5.
3.6.
3.7.
3.8.
3.9.
3.10.
Port E Input Pins Address............................................................................................................ 8
Port E Data Direction Register..................................................................................................... 9
Port E Data Register...................................................................................................................10
XOSC Failure Detection Control And Status Register................................................................11
USART Control and Status Register 0 D....................................................................................12
USART Control and Status Register n D....................................................................................13
Analog Comparator Control and Status Register B....................................................................14
Device ID byte 0......................................................................................................................... 15
Device ID byte 1......................................................................................................................... 16
Device ID byte 2......................................................................................................................... 17
3.11.
3.12.
3.13.
3.14.
3.15.
Device ID byte 3......................................................................................................................... 18
Device ID byte 4......................................................................................................................... 19
Device ID byte 5......................................................................................................................... 20
Device ID byte 6......................................................................................................................... 21
Device ID byte 7......................................................................................................................... 22
3.16. Device ID byte 8......................................................................................................................... 23
4. Revision History.......................................................................................................24
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
2
1.
1.1.
Pin Functionality Difference
Additional Pin Functionalities
ATmega328PB supports four additional GPIOs on PORTE [3:0].
The GPIO pins PE2 and PE3 are assigned to Pin19 and Pin22. PE2 and PE3 are multiplexed with ADC6
and ADC7.
Pin3 (GND) and Pin6 (VCC) are replaced by PE0 and PE1 respectively. PE0 is multiplexed with ACO.
Table 1-1 Pin Functionality Difference between ATmega328 Variants and ATmega328PB
1.2.
32-pin TQFP/MLF package
ATmega328 variants
ATmega328PB
Pin 3
GND
PE0/ACO
Pin 6
VCC
PE1
Pin 19
ADC6
ADC6/PE2
Pin 22
ADC7
ADC7/PE3
Alternate Pin Configuration
The alternate pin configurations are:
•
•
•
•
ADC7– Port E, Bit 3
PE3 can also be used as ADC input channel 7.
Note: ADC input channel 7 uses analog power AVCC.
ADC6 – Port E, Bit 2
PE2 can also be used as ADC input channel 6.
Note: ADC input channel 6 uses analog power AVCC.
None – Port E, Bit 1
No alternate function.
ACO – Port E, Bit 0
ACO Analog Compare Output pin is multiplexed with PE0.
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
3
2.
Enhancement and Additional Features in ATmega328PB
Compared to existing ATmega328 variants, the following enhancements or additional features are
available in ATmega328PB:
•
PTC - Peripheral Touch Controller.
•
CFD - Clock Failure Detection mechanism.
•
OCM1C2 - Output Compare Modulator.
•
USART start frame detection is available in all sleep modes
•
Analog Comparator output is available on a pin. This pin is multiplexed with PE0.
•
Unique device ID to identify the device
•
Additional SPI
•
Additional TWI
•
Additional Timer/Counters
2.1.
PTC - Peripheral Touch Controller
The ATmega328PB is the first 8-bit Atmel AVR device to feature the successful Atmel QTouch Peripheral
Touch Controller (PTC). The Peripheral Touch Controller (PTC) acquires signals in order to detect touch
on capacitive sensors. The external capacitive touch sensor is typically formed on a PCB, and the sensor
electrodes are connected to the analog front end of the PTC through the I/O pins in the device. The PTC
supports both self and mutual capacitance sensors.
The PTC supports 24 buttons in self-capacitance mode and up to 144 buttons in mutual-capacitance
mode. It is possible to mix and match mutual-and self-capacitance sensors. Only one pin is required per
electrode—no external components are required providing considerable savings on the BOM cost
compared to competing solutions.
In mutual-capacitance mode, sensing is performed using capacitive touch matrices in various X-Y
configurations. Whereas in self-capacitance mode, the PTC requires only one pin (Y-line) for each touch
sensor.
Refer to the chapter I/O Multiplexing in the ATmega328PB device datasheet for details on the pin
mapping for this peripheral. A signal can be mapped on several pins.
2.1.1.
PTC Functional Description
To access the PTC, the user must use the QTouch Composer tool to configure and link the QTouch
Library firmware with the application code. QTouch Library can be used to implement buttons, sliders,
wheels, and proximity sensor in a variety of combinations on a single interface.
Figure 2-1 QTouch Library Usage
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
4
2.2.
CFD - Clock Failure Detection mechanism
Clock Failure Detection and Switching Mechanism is a new feature introduced in ATmega328PB. This
digital logic detects the failure of the Low power crystal oscillator, Full swing crystal oscillator, and external
clocks. If a failure is detected, this logic will automatically switch the clock to 1MHz internal RC system
clock.
The Clock Failure Detection mechanism for the device is enabled by an active high fuse. When the CFD
fuse is enabled, 128kHz oscillator will be enabled and the CFD circuit works using that clock.
CFD will be automatically disabled when the chip enters power save/down sleep mode. It will be enabled
by itself when the chip returns to active mode. CFD will be enabled only when the system frequency is
greater than 256kHz.
2.3.
OCM1C2 - Output Compare Modulator
The Output Compare Modulator (OCM) allows generation of waveforms modulated with a carrier
frequency. The modulator uses the outputs from the Output Compare Unit B of the 16-bit Timer/Counter3
and the Output Compare Unit of the 16-bit Timer/Counter4. When the modulator is enabled, the two
output compare channels are modulated together as shown in the block diagram.
Figure 2-2 Output Compare Modulator - Block Diagram
The Output Comparator unit 3B and Output compare unit 4B shares the PD2 port pin for output. The
outputs of the Output Compare units (OC3B and OC4B) overrides the normal PORTD2 bit when one of
them is enabled (that is, when COMnx1:0 is not equal to zero). When both OC3B and OC4B are enabled
simultaneously, the modulator is automatically enabled.
2.4.
USART
ATmega328PB has one additional USART with start-of-frame detection, which can wake up the MCU
from all sleep modes - when a start bit is detected. Two USART modules are available in the
ATmega328PB with individual configuration registers, refer Register Description section under the
USART module in the ATmega328PB device datasheet for detailed description of these registers. They
also have separate TX, RX, and XCK pins. For details on the pin mapping for this peripheral, refer to the
I/O Multiplexing section in the ATmega328PB device datasheet.
When a high-to-low transition is detected on RxDn, the internal 8MHz oscillator is powered up and the
USART clock is enabled. After start-up the rest of the data frame can be received, provided that the baud
rate is slow enough to allow the internal 8MHz oscillator to start up. Start-up time of the internal 8MHz
oscillator varies with supply voltage and temperature.
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
5
The USART start frame detection works both in asynchronous and synchronous modes. It is enabled by
writing the Start Frame Detection Enable bit (SFDEn). If the USART Start- Interrupt Enable (RXSIE) bit is
set, the USART Receive Start Interrupt is generated immediately when a start is detected.
When using the feature without the Receive Start Interrupt, the start detection logic activates the internal
8MHz oscillator and the USART clock while the frame is being received only. Other clocks remain
stopped until the Receive Complete Interrupt optionally wakes up the MCU.
The maximum baud rate depends on the sleep mode the device is woken up from.
In synchronous mode:
•
•
Idle or ADC Noise Reduction sleep mode: system clock frequency divided by four
Standby or Power-down: 500kbps
In asynchronous mode:
•
Idle sleep mode: the same as in active mode
2.5.
Analog Comparator
Analog Comparator output is available on a pin. The analog comparator’s output is Multiplexed to PE0
when the AC output is enabled by writing a one to the Analog Comparator Output Enable bit (ACOE) in
“ACSR0 – Analog Comparator Output Control Register”.
2.6.
Unique Device ID
In Atmel ATmega328PB, the unique device ID is now accessible through I/O registers. This unique device
ID is available from I/O address 0xF0 - 0xF8. The ID is created by concatenating the nine bytes read out
from these registers. These registers are read-only.
2.7.
Additional SPI
ATmega328PB has one Additional SPI. There are two SPIs with individual configuration registers. Refer
to the Register Description section in the SPI peripheral in the ATmega328PB device datasheet for
detailed description of these registers. They also have a separate MOSI, MISO, SCK, and SS pins. Refer
to the I/O Multiplexing section in the ATmega328PB device datasheet for details about the pin mapping
for this peripheral.
2.8.
Additional TWI
ATmega328PB has one additional byte-oriented 2-wire serial interface (TWI). There are two TWI
peripheral with individual configuration registers. Refer the Register Description section under the TWI 2-wire Serial Interface module in the ATmega328PB device datasheet for detailed description of these
registers. Separate SDA and SDL pins are also available. Refer to the section I/O Multiplexing in the
ATmega328PB device datasheet for details on the pin mapping for this peripheral.
2.9.
Additional Timer/Counters
ATmega328PB has two additional 16-bit Timer/Counters(TC3 and TC4) with separate Prescaler,
Compare Mode, and Capture Mode. There are three 16-bit Timer/Counters (TC1, TC3, and TC4) and ten
PWM channels available in ATmega328PB. Refer to the I/O Multiplexing section in the ATmega328PB
device datasheet for details about the pin mapping for this peripheral.
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
6
3.
Register Description
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
7
3.1.
Port E Input Pins Address
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PINE
Offset: 0x2C
Reset: N/A
Property: When addressing as I/O Register: address offset is 0x0C
Bit
Access
Reset
7
6
5
4
3
2
1
0
PINE6
PINE5
PINE4
PINE3
PINE2
PINE1
PINE0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
x
x
x
x
x
x
x
Bits 3:0 – PINEn: Port E Input Pins Address [n = 3:0]
Writing to the pin register provides toggle functionality for I/O.
Bits 6:0 – PINEn: Port E Input Pins Address [n = 6:0]
Writing to the pin register provides toggle functionality for I/O.
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
8
3.2.
Port E Data Direction Register
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: DDRE
Offset: 0x2D
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x0D
Bit
Access
Reset
7
6
5
4
3
2
1
0
DDRE6
DDRE5
DDRE4
DDRE3
DDRE2
DDRE1
DDRE0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
Bits 3:0 – DDREn: Port E Data Direction [n = 3:0]
Bits 6:0 – DDREn: Port E Data Direction [n = 6:0]
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
9
3.3.
Port E Data Register
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: PORTE
Offset: 0x2E
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x0E
Bit
Access
Reset
7
6
5
4
3
2
1
0
PORTE6
PORTE5
PORTE4
PORTE3
PORTE2
PORTE1
PORTE0
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0
0
0
0
0
0
0
Bits 3:0 – PORTEn: Port E Data [n = 3:0]
Bits 6:0 – PORTEn: Port E Data [n = 6:0]
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
10
3.4.
XOSC Failure Detection Control And Status Register
Name: XFDCSR
Offset: 0x62
Reset: 0x00
Property: Bit
7
6
5
4
3
2
1
0
XFDIF
XFDIE
Access
R
R/W
Reset
0
0
Bit 1 – XFDIF: Failure Detection Interrupt Flag
This bit is set when a failure is detected. It serves as status bit for CFD.
Note: This bit is read only.
Bit 0 – XFDIE: Failure Detection Interrupt Enable
Setting this bit will enable the interrupt which will be issued when XFDIF is set.This bit is enable only.
Once enabled, it is not possible for the user to disable.
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
11
3.5.
USART Control and Status Register 0 D
This register is not used in Master SPI Mode (UMSEL0[1:0] = 11)
Name: UCSR0D
Offset: 0xC3
Reset: 0x00
Property: Bit
Access
Reset
7
6
5
RXIE
RXS
SFDE
4
R/W
R/W
R/W
0
0
0
3
2
1
0
Bit 7 – RXIE: USART RX Start Interrupt Enable
Writing this bit to one enables the interrupt on the RXS flag. In sleep modes this bit enables start frame
detector that can wake up the MCU when a start condition is detected on the RxD line. The USART RX
Start Interrupt is generated only, if the RXSIE bit, the Global Interrupt flag, and RXS are set.
Bit 6 – RXS: USART RX Start
The RXS flag is set when a start condition is detected on the RxD line. If the RXSIE bit and the Global
Interrupt Enable flag are set, an RX Start Interrupt will be generated when the flag is set. The flag can
only be cleared by writing a logical one on the RXS bit location.
If the start frame detector is enabled (RXSIE = 1) and the Global Interrupt Enable flag is set, the RX Start
Interrupt will wake up the MCU from all sleep modes.
Bit 5 – SFDE: Start Frame Detection Enable
Writing this bit to one enables the USART Start Frame Detection mode. The start frame detector is able to
wake up the MCU from sleep mode when a start condition, i.e. a high (IDLE) to low (START) transition, is
detected on the RxD line.
Table 3-1 USART Start Frame Detection Modes
SFDE RXSIE RXCIE Description
0
X
X
Start frame detector disabled
1
0
0
Reserved
1
0
1
Start frame detector enabled. RXC flag wakes up MCU from all sleep modes
1
1
0
Start frame detector enabled. RXS flag wakes up MCU from all sleep modes
1
1
1
Start frame detector enabled. Both RXC and RXS wake up the MCU from all
sleep modes
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
12
3.6.
USART Control and Status Register n D
This register is not used in Master SPI Mode (UCSRnC.UMSEL[1:0] = 11)
Name: UCSR0D, UCSR1D
Offset: 0xC3 + n*0x08 [n=0..1]
Reset: 0x00
Property: Bit
Access
Reset
7
6
5
RXIE
RXS
SFDE
4
R/W
R/W
R/W
0
0
0
3
2
1
0
Bit 7 – RXIE: USART RX Start Interrupt Enable
Writing this bit to one enables the interrupt on the RXS flag. In sleep modes this bit enables start frame
detector that can wake up the MCU when a start condition is detected on the RxD line. The USART RX
Start Interrupt is generated only, if the RXSIE bit, the Global Interrupt flag, and RXS are set.
Bit 6 – RXS: USART RX Start
The RXS flag is set when a start condition is detected on the RxD line. If the RXSIE bit and the Global
Interrupt Enable flag are set, an RX Start Interrupt will be generated when the flag is set. The flag can
only be cleared by writing a logical one on the RXS bit location.
If the start frame detector is enabled (RXSIE = 1) and the Global Interrupt Enable flag is set, the RX Start
Interrupt will wake up the MCU from all sleep modes.
Bit 5 – SFDE: Start Frame Detection Enable
Writing this bit to one enables the USART Start Frame Detection mode. The start frame detector is able to
wake up the MCU from sleep mode when a start condition, i.e. a high (IDLE) to low (START) transition, is
detected on the RxD line.
Table 3-2 USART Start Frame Detection Modes
SFDE RXSIE RXCIE Description
0
X
X
Start frame detector disabled
1
0
0
Reserved
1
0
1
Start frame detector enabled. RXC flag wakes up MCU from all sleep modes
1
1
0
Start frame detector enabled. RXS flag wakes up MCU from all sleep modes
1
1
1
Start frame detector enabled. Both RXC and RXS wake up the MCU from all
sleep modes
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
13
3.7.
Analog Comparator Control and Status Register B
The Store Program Memory Control and Status Register contains the control bits needed to control the
Boot Loader operations.
When addressing I/O Registers as data space using LD and ST instructions, the provided offset must be
used. When using the I/O specific commands IN and OUT, the offset is reduced by 0x20, resulting in an
I/O address offset within 0x00 - 0x3F.
Name: ACSRB
Offset: 0x4F
Reset: 0x00
Property: When addressing as I/O Register: address offset is 0x2F
Bit
7
6
5
4
3
2
1
0
ACOE
Access
R/W
Reset
0
Bit 0 – ACOE: Analog Comparator Output Enable
When this bit is set, the analog comparator output is connected to the ACO pin.
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
14
3.8.
Device ID byte 0
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID0
Offset: 0xF0
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 0[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 0[7:0]: Device ID byte 0
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
15
3.9.
Device ID byte 1
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID1
Offset: 0xF1
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 1[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 1[7:0]: Device ID byte 1
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
16
3.10.
Device ID byte 2
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID2
Offset: 0xF2
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 2[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 2[7:0]: Device ID byte 2
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
17
3.11.
Device ID byte 3
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID3
Offset: 0xF3
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 3[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 3[7:0]: Device ID byte 3
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
18
3.12.
Device ID byte 4
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID4
Offset: 0xF4
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 4[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 4[7:0]: Device ID byte 4
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
19
3.13.
Device ID byte 5
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID5
Offset: 0xF5
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 5[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 5[7:0]: Device ID byte 5
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
20
3.14.
Device ID byte 6
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID6
Offset: 0xF6
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 6[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 6[7:0]: Device ID byte 6
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
21
3.15.
Device ID byte 7
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID7
Offset: 0xF7
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 7[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 7[7:0]: Device ID byte 7
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
22
3.16.
Device ID byte 8
Each individual part has a specific unique device ID. This can be used to identify a specific part while it is
in the field. The Device ID consist of nine bytes in which the user can access directly from the registers.
The register address locations are located at 0xF0 to 0xF8.
Name: DEVID8
Offset: 0xF8
Reset: Device ID value
Property: Bit
7
6
5
4
3
2
1
0
Device ID byte 8[7:0]
Access
R
R
R
R
R
R
R
R
Reset
x
x
x
x
x
x
x
x
Bits 7:0 – Device ID byte 8[7:0]: Device ID byte 8
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
23
4.
Revision History
Doc. Rev.
Date
Comments
42626A
11/2015
Initial document release
Atmel AT15007: Differences between ATmega328/P and ATmega328PB [APPLICATION
NOTE]
Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
24
Atmel Corporation
©
1600 Technology Drive, San Jose, CA 95110 USA
T: (+1)(408) 441.0311
F: (+1)(408) 436.4200
|
www.atmel.com
2015 Atmel Corporation. / Rev.: Atmel-42559A-Differences-between-ATmega328P-and-ATmega328PB_AT15007_Application Note-11/2015
®
®
®
®
Atmel , Atmel logo and combinations thereof, Enabling Unlimited Possibilities , AVR , QTouch , and others are registered trademarks or trademarks of Atmel
Corporation in U.S. and other countries. Other terms and product names may be trademarks of others.
DISCLAIMER: The information in this document is provided in connection with Atmel products. No license, express or implied, by estoppel or otherwise, to any
intellectual property right is granted by this document or in connection with the sale of Atmel products. EXCEPT AS SET FORTH IN THE ATMEL TERMS AND
CONDITIONS OF SALES LOCATED ON THE ATMEL WEBSITE, ATMEL ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED
OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL ATMEL BE LIABLE FOR ANY DIRECT, INDIRECT,
CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS AND PROFITS, BUSINESS
INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF ATMEL HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES. Atmel makes no representations or warranties with respect to the accuracy or completeness of the contents of this
document and reserves the right to make changes to specifications and products descriptions at any time without notice. Atmel does not make any commitment to
update the information contained herein. Unless specifically provided otherwise, Atmel products are not suitable for, and shall not be used in, automotive
applications. Atmel products are not intended, authorized, or warranted for use as components in applications intended to support or sustain life.
SAFETY-CRITICAL, MILITARY, AND AUTOMOTIVE APPLICATIONS DISCLAIMER: Atmel products are not designed for and will not be used in connection with any
applications where the failure of such products would reasonably be expected to result in significant personal injury or death (“Safety-Critical Applications”) without
an Atmel officer's specific written consent. Safety-Critical Applications include, without limitation, life support devices and systems, equipment or systems for the
operation of nuclear facilities and weapons systems. Atmel products are not designed nor intended for use in military or aerospace applications or environments
unless specifically designated by Atmel as military-grade. Atmel products are not designed nor intended for use in automotive applications unless specifically
designated by Atmel as automotive-grade.