AT89C51CC03_14 Datasheet, PDF (5/7 Pages) ATMEL Corporation – Read/Write Flash and EEPROM Memories

AT89C51CC03/C/U Errata Sheet
Workaround
The FLIP software is not impacted by this CAN frame.
7. Start of the Bootloader from Application Using api_start_isp Doesn’t Work
The API to start the bootloader directly in CAN communication open does not work.
Workaround
Start the bootloader using api_start_bootloader and send the CAN command to open the communication with the CAN
bootloader.
8. Start application with software security set
The start application with or without reset doesn’t work if the software security are set.
Workaround
Use the SSB API to secure the device in the application.
9. Write column latches robustness improvement
The data bytes from the CAN messages are directly written in the column latches until the 128 bytes page is filled or
the end of the program is reached. Afterward, the column latches are written in the flash page. If a CAN failure ocurs
during the load process, it will leave the column latches partially written. A reset will be needed before starting over
again.
Workaround
Use 1.0.3 revision: Incoming bytes are stored in RAM. Once the full page transfer is successfull, the 128 bytes RAM
will be copied into the column latches, then the column latches copied into the flash. If a CAN failure occurs, nothing
will be written in the column latches and flash page.
10. CAN autobaud
Due to uninitialized RAM cells, the CAN autobaud process may require additional time to synchronise properly with the
In System Programing Interface (up to 30seconds).
Workarounds
Use 1.0.4 bootloader revision.
Or
When using ATMEL “Flip” In Sytem Programing Interface:
Update to 2.4.6 version and set timeout parameter to 30sec.
When using a custom In System Programing Interface:
Wait up to 30sec for the “Node Connect” frame to be acknowledged by the CAN bootloader.
5
4293G–CAN–06/05