ATmega16M1 Automotive Atmel Corporation, ATmega16M1 Automotive Datasheet - Page 278

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

Specifications of ATmega16M1 Automotive

• Flash (kbytes): 16 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): 1
• Eeprom (bytes): 512
• 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: 14
• Input Capture Channels: 1
• Pwm Channels: 10
• 32khz Rtc: No
• Calibrated Rc Oscillator: Yes

23.4
23.5
23.6
23.6.1
278
Software Break Points
Limitations of debugWIRE
debugWIRE Related Register in I/O Memory
Atmel ATmega16/32/64/M1/C1
debugWire Data Register – DWDR
When designing a system where debugWIRE will be used, the following observations must be
made for correct operation:
debugWIRE supports Program memory Break Points by the AVR Break instruction. Setting a
Break Point in AVR Studio
instruction replaced by the BREAK instruction will be stored. When program execution is con-
tinued, the stored instruction will be executed before continuing from the Program memory. A
break can be inserted manually by putting the BREAK instruction in the program.
The Flash must be re-programmed each time a Break Point is changed. This is automatically
handled by AVR Studio through the debugWIRE interface. The use of Break Points will there-
fore reduce the Flash Data retention. Devices used for debugging purposes should not be
shipped to end customers.
The debugWIRE communication pin (dW) is physically located on the same pin as External
Reset (RESET). An External Reset source is therefore not supported when the debugWIRE is
enabled.
The debugWIRE system accurately emulates all I/O functions when running at full speed, i.e.,
when the program in the CPU is running. When the CPU is stopped, care must be taken while
accessing some of the I/O Registers via the debugger (AVR Studio).
A programmed DWEN Fuse enables some parts of the clock system to be running in all sleep
modes. This will increase the power consumption while in sleep. Thus, the DWEN Fuse
should be disabled when debugWire is not used.
The following section describes the registers used with the debugWire.
The DWDR Register provides a communication channel from the running program in the MCU
to the debugger. This register is only accessible by the debugWIRE and can therefore not be
used as a general purpose register in the normal operations.
Bit
Read/Write
Initial Value
• Pull-up resistors on the dW/(RESET) line must not be smaller than 10k . The pull-up
• Connecting the RESET pin directly to V
• Capacitors connected to the RESET pin must be disconnected when using debugWire.
• All external reset sources must be disconnected.
resistor is not required for debugWIRE functionality.
R/W
7
0
R/W
6
0
®
will insert a BREAK instruction in the Program memory. The
R/W
5
0
R/W
CC
4
0
DWDR[7:0]
will not work.
R/W
3
0
R/W
2
0
R/W
1
0
R/W
0
0
7647G–AVR–09/11
DWDR