ATMEGA128 datasheet(21/31 Pages) ATMEL

21 / 31 page

ATmega128

2467OS–AVR–10/06

Stabilizing time needed when changing OSCCAL Register

After increasing the source clock frequency more than 2% with settings in the OSC-

CAL register, the device may execute some of the subsequent instructions

incorrectly.

Problem Fix / Workaround

The behavior follows errata number 1., and the same Fix / Workaround is applicable

on this errata.

IDCODE masks data from TDI input

The JTAG instruction IDCODE is not working correctly. Data to succeeding devices

are replaced by all-ones during Update-DR.

Problem Fix / Workaround

–

If ATmega128 is the only device in the scan chain, the problem is not visible.

–

Select the Device ID Register of the ATmega128 by issuing the IDCODE

instruction or by entering the Test-Logic-Reset state of the TAP controller to

read out the contents of its Device ID Register and possibly data from

succeeding devices of the scan chain. Issue the BYPASS instruction to the

ATmega128 while reading the Device ID Registers of preceding devices of

the boundary scan chain.

–

If the Device IDs of all devices in the boundary scan chain must be captured

simultaneously, the ATmega128 must be the fist device in the chain.

ATmega128 Rev. H

• First Analog Comparator conversion may be delayed

• Interrupts may be lost when writing the timer registers in the asynchronous timer

• Stabilizing time needed when changing XDIV Register

• Stabilizing time needed when changing OSCCAL Register

• IDCODE masks data from TDI input

First Analog Comparator conversion may be delayed

If the device is powered by a slow rising V

CC, the first Analog Comparator conver-

sion will take longer than expected on some devices.

Problem Fix/Workaround

When the device has been powered or reset, disable then enable theAnalog Com-

parator before the first conversion.

Interrupts may be lost when writing the timer registers in the asynchronous

timer

If one of the timer registers which is synchronized to the asynchronous timer2 clock

is written in the cycle before a overflow interrupt occurs, the interrupt may be lost.

Problem Fix/Workaround

Always check that the Timer2 Timer/Counter register, TCNT2, does not have the

value 0xFF before writing the Timer2 Control Register, TCCR2, or Output Compare

Stabilizing time needed when changing XDIV Register

After increasing the source clock frequency more than 2% with settings in the XDIV

ATMEGA128 датащи(PDF) 21 Page - ATMEL Corporation

ATMEGA128 датащи(HTML) 21 Page - ATMEL Corporation

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

датащи скачать

ссылки URL