http://www.atmel-wm.com 2 / 5
Atmel Wireless & Microcontrollers
Q6: What is happen when the Customer needs his own special Boot Loader?
A6: Of course, the customer can write his own boot loader. Finally there are two possibilities for its location.
Either the customer boot loader will replace the default Boot Loader in the Boot Flash Memory or the default Boot
Loader is used to place the customer boot loader also in the User Flash Memory.
Q7: What is API?
A7: API stands for “Application Programming Interfaces”. These software routines also called “driver” handle
e.g. the CAN Controller management, read and write access to all on-chip non-volatile memories, etc.
All these APIs are part of the Atmel Wireless & Microcontrollers CANary offering.
Q8: Is the ISP also applicable to the EEPROM?
A8: Of course, also the EEPROM can be programmed or altered via CAN bus. A very important point, because
the EEPROM is often used to store application parameters. These will change in embedded applications during
the lifetime of a product.
Q9: What else is special on our non-volatile Memories?
A9: The Flash memories and EEPROM are programmable by byte or by page (including 128 Bytes) or by a
number of bytes in a page. No need for a special erase cycle before any programming. Our Non-volatile
memories are self-erasure.
Q10: What means ‘channel’?
A10: T89C51CC02 has 15 channels. Each channel can treat one message object, consisting of 20 bytes each,
including an 8 bytes cyclic data shift register. Each unit works independently following the configuration chosen
as:
- Receiver
- Transmitter
- Receiver Buffer
- Either on the 2.0A or 2.0B CAN protocol.
Q11: What is the use of the other 12 bytes of one channel?
A11:
- 4 bytes for programming the identifier (ID Tag register)
- 4 bytes for masking the identifier bits (ID Mask register)
- 2 bytes for Status & Control
- 2 bytes for the Time Stamp Register
Q12: I understand Receiver, Transmitter, but what does Receiver Buffer mean?
A12: After ‘flexibility’ here a further important feature of our CAN Controller: In Receiver Buffer mode 1 to 15
channels can participate, in a non-consecutive sequence, to built-up a 120 byte wide data receiver buffer. In this
case all concerned ID Tag registers are programmed on the same identifier.
The lowest channel number will be served first.
This feature, in older days also called “Basic CAN Feature” will help that no important message on the CAN bus
is missed or to ease the transfer of data strings longer than 8 bytes. (One CAN frame is limited to 8 data bytes).