Datasheet

946

32142D–06/2013

ATUC64/128/256L3/4U

Issue a dummy read to address 0x100000000 before issuing the

MEMORY_SPEED_REQUEST command and use this formula instead:

38.4 Flash

2. Corrupted data in flash may happen after flash page write operations

After a flash page write operation from an external programmer, reading (data read or code

fetch) in flash may fail. This may lead to an exception or to others errors derived from this

corrupted read access.

Fix/Workaround

Before any flash page write operation, each write in the page buffer must preceded by a

write in the page buffer with 0xFFFF_FFFF content at any address in the page.

38.5 Rev. A

38.5.1 Device

3. JTAGID is wrong

The JTAGID reads 0x021DF03F for all devices.

Fix/Workaround

None.

38.5.2 FLASHCDW

1. General-purpose fuse programming does not work

The general-purpose fuses cannot be programmed and are stuck at 1. Please refer to the

Fuse Settings chapter in the FLASHCDW for more information about what functions are

affected.

Fix/Workaround

None.

2. Set Security Bit command does not work

The Set Security Bit (SSB) command of the FLASHCDW does not work. The device cannot

be locked from external JTAG, aWire, or other debug accesses.

Fix/Workaround

None.

3. Flash programming time is longer than specified

sab

CV 3–

-----------------=