AT90CAN128-16AE ATMEL Corporation, AT90CAN128-16AE Datasheet - Page 383

• Manufacturer Part Number: AT90CAN128-16AE
• Description: 8-bit Avr Microcontroller With 128K Bytes of Isp Flash And CAN Controller.flash (Kbytes) 128 Vcc (V) 2.7-5.5 EEPROM (Kbytes) 4 SRAM (bytes) 4K CAN (mess. Obj.) 15
• Manufacturer: ATMEL Corporation

Erratas
AT90CAN128 Rev. A
4250C–CAN–03/04
The revision letter in this section refers to the revision of the AT90CAN128 device.
There are no errata for this revision of AT90CAN128. However, a proposal for solving
problems regarding the JTAG instruction IDCODE is presented below.
IDCODE masks data from TDI input
The public but optional JTAG instruction IDCODE is not implemented correctly
according to IEEE1149.1; a logic one is scanned into the shift register instead of the
TDI input while shifting the Device ID Register. Hence, captured data from the pre-
ceding devices in the boundary scan chain are lost and replaced by all-ones, and
data to succeeding devices are replaced by all-ones during Update-DR.
If AT90CAN128 is the only device in the scan chain, the problem is not visible.
Problem Fix / Workaround
Select the Device ID Register of the AT90CAN128 (Either 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. Note that data to succeeding devices cannot be entered
during this scan, but data to preceding devices can. Issue the BYPASS instruction
to the AT90CAN128 to select its Bypass Register while reading the Device ID Reg-
isters of preceding devices of the boundary scan chain. Never read data from
succeeding devices in the boundary scan chain or upload data to the succeeding
devices while the Device ID Register is selected for the AT90CAN128. Note that the
IDCODE instruction is the default instruction selected by the Test-Logic-Reset state
of the TAP-controller.
Alternative Problem Fix / Workaround
If the Device IDs of all devices in the boundary scan chain must be captured simul-
taneously (for instance if blind interrogation is used), the boundary scan chain can
be connected in such way that the AT90CAN128 is the fist device in the chain.
Update-DR will still not work for the succeeding devices in the boundary scan chain
as long as IDCODE is present in the JTAG Instruction Register, but the Device ID
registered cannot be uploaded in any case.
AT90CAN128
383