Information

Workaround: Because the MCR[DONE] flag can be set too soon, a delay needs to be inserted between
setting the MCR[ESUS] or MCR[PSUS] and reading the same flash partition. The minimum
duration of the delay should be 40us to guarantee correct operation. The Freescale flash
programming driver includes this workaround.
e3659: FLASH: Resuming after a suspend during an Erase may prevent the erase from
completing.
Errata type: Errata
Description: If an erase suspend (including the flash put into sleep or disabled mode) is done on any block
in the low Address Space (LAS) or the Mid-Address Space (MAS) except the 16 KB blocks, or
if a suspend is done with multiple non-adjacent blocks (including the High Address Space
[HAS]), the flash state machine may not set the FLASH_MCR[DONE] bit in the flash Module
Control Register. This condition only occurs if the suspend occurs during certain internal flash
erase operations. The likelihood of an issue occurring is reduced by limiting the frequency of
suspending the erase operation.
Workaround: If the suspend feature (including disable and sleep modes) of the flash is used, then software
should ensure that if the maximum time allowed for an erase operation occurs without a valid
completion flag from the flash (FLASH_MCR[DONE] = 1), the software should abort the erase
operation (by first clearing the Enable High Voltage (FLASH_MCR[EHV] ) bit, then clearing the
Erase read/Write bit (FLASH_MCR[ERS] bit) and the erase operation should be restarted.
Note: The cycle count of the sector is increased by this abort and restart operation.
e3407: FlexCAN: CAN Transmitter Stall in case of no Remote Frame in response to Tx
packet with RTR=1
Errata type: Errata
Description: FlexCAN does not transmit an expected message when the same node detects an incoming
Remote Request message asking for any remote answer.
The issue happens when two specific conditions occur:
1) The Message Buffer (MB) configured for remote answer (with code "a") is the last MB. The
last MB is specified by Maximum MB field in the Module Configuration Register
(MCR[MAXMB] ).
2) The incoming Remote Request message does not match its ID against the last MB ID.
While an incoming Remote Request message is being received, the FlexCAN also scans the
transmit (Tx) MBs to select the one with the higher priority for the next bus arbitration. It is
expected that by the Intermission field it ends up with a selected candidate (winner). The
coincidence of conditions (1) and (2) above creates an internal corner case that cancels the Tx
winner and therefore no message will be selected for transmission in the next frame. This
gives the appearance that the FlexCAN transmitter is stalled or "stops transmitting".
The problem can be detectable only if the message traffic ceases and the CAN bus enters into
Idle state after the described sequence of events.
There is NO ISSUE if any of the conditions below holds:
a) The incoming message matches the remote answer MB with code "a".
b) The MB configured as remote answer with code "a" is not the last one.
Mask Set Errata for Mask 3M17W, Rev 13 SEP 2013
Freescale Semiconductor, Inc. 7