
R01UH0336EJ0102 Rev.1.02
Page 1160 of 1538
Jul 17, 2014
V850E2/PG4-L
Section 20 CAN Controller (FCN)
Note 1.
Check FCNnMmCTL.FCNnMmMUCF and FCNnMmCTL.FCNnMmDTNF bits
in one read access.
Note 2.
Depending of the processing target of the application, two ways are possible:
– Way A: The message is not processed within this pass, but with the next
pass, depending on the latest timing at which the message is processed
with the next reception interrupt. Other messages are processed earlier.
– Way B: The message is processed within this pass, and the loop enters
the waiting state with this message. Other messages are processed later.
Note 3.
Also check the FCNnGMCLSSMO flag at the beginning and at the end of the
interrupt routine, in order to check the access to the message buffers as well
as receive history list registers of the FCN module, in case a pending sleep
mode had been executed. If FCNnGMCLSSMO is detected to be cleared at
any check, re-set FCNnGMCLSSMO, discard actions and results of the
processing, and then perform processing again.
It is recommended that all sleep mode requests be cancelled before
processing reception interrupts.
Note 4.
Once FCNnCMRGRX.FCNnCMRGRVFF is set, the receive history list is
inconsistent. Consider to examine all configured receive buffers to check
reception.
Note 5.
Figure 20-33, Reception via Interrupt (Using FCNnCMRGRX Register),
Alternative Way, Alternative Way, is available as an alternative of Figure 20-32,
Reception via Interrupt (Using FCNnCMRGRX Register).