The CAN_IFCxCMD Busy bit is set to one after the nessage number has been written to bits [7:0] in CAN_IFCxCMD. The bit is cleared after read/write action has been finished.
How many clock cycles it takes to finish a read/write action?
Thanks.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
The CAN_IFCxCMD Busy bit is set to one after the nessage number has been written to bits [7:0] in CAN_IFCxCMD. The bit is cleared after read/write action has been finished.
How many clock cycles it takes to finish a read/write action?
Thanks.
Demis,
The next revision of the TRM will have this information:
The IF1/IF2 Command Registers configure and initiate the transfer between the IF1/IF2 Register sets and the Message RAM. It is configurable which portions of the message object should be transferred. A transfer is started when the CPU writes the message number to bits [7:0] of the IF1/IF2 Command Register. With this write operation, the Busy bit is automatically set to '1' to indicate that a transfer is in progress. After 4 to 14 clock cycles, the transfer between the Interface Register and the Message RAM will be completed and the Busy bit is cleared. The maximum number of cycles is needed when the message transfer coincides with a CAN message transmission, acceptance filtering, or message storage.
Does this answer your question?