When TCP is used as a transport mechanism, this errata manifests itself as lost packets and
reduced throughput. Data continues to be received correctly because TCP requests
retransmission of bad packets. However, UDP does not include any mechanism for packet
retransmission, as it is a send and forget protocol. Consequently, while UDP should be able to
identify an incorrectly received packet (because its checksum will fail), higher level software in
the protocol stack must be capable of requesting retransmission to work around this errata.
Workaround:
Higher level Ethernet layer code should compare the length reported by the descriptor to the
length included in its header. If the lengths do not match, the packet should be truncated or
discarded as needed. The protocol stack must be responsible for requesting retransmission of
any frames that are discarded due to the data length mismatch.
Fix plan:
Currently, there are no plans to fix this.
SECF036: PLL Does Not Lock in Normal PLL Mode with External Clock Reference
Errata type:
Silicon
Affects:
PLL
Description:
During a power on reset, if the CLKMOD[1:0] equals 10 (normal PLL mode with external clock
reference), the PLL does not lock and the device never comes out of reset.
Workaround:
When configuring the PLL for normal PLL mode with external clock reference, tie CLKMOD1 to
RSTI and not straight to 3.3V. This allows the PLL to correctly detect the desired operating
mode and lock.
Fix plan:
Currently, there are no plans to fix this.
SECF010: FEC Interrupts will not Trigger on Consecutive Transmit Frames
Errata type:
Silicon
Affects:
FEC
Description:
The late collision (LC), retry limit (RL), and underrun (UN) interrupts do not trigger on
consecutive transmit frames. For example, if back-to-back frames cause a transmit underrun,
only the first frame generates an underrun interrupt. No other underrun interrupts are
generated until a frame is transmitted that does not underrun or the FEC is reset.
Workaround:
Because late collision, retry limit, and underrun errors are not directly correlated to a specific
transmit frame, in most cases a workaround for this problem is not needed. If a workaround is
required, there are two independent workarounds:
Ensure that a correct frame is transmitted after a late collision, retry limit, or underrun
errors are detected.
Perform a soft reset of the FEC by setting ECR[RESET] when a late collision, retry limit,
or underrun errors are detected.
Fix plan:
Currently, there are no plans to fix this.
SECF038: Possible QADC Command Conversion Word (CCW) Table Corruption
Errata type:
Silicon
Affects:
QADC
MCF5282 Chip Errata, Rev 8, 02/2015
Freescale Semiconductor, Inc. 7
Description:
A CCW table location may be corrupted by writing any other CCW or results table location
while any queue is active. If a CCW table or result table write occurs while either queue is
active, it is possible for another CCW location to be corrupted. This bug only occurs if the write
cycle is simultaneous with the queue state machine reading the next CCW location. The odds
of this happening are one in the number of clocks in a conversion.
Workaround:
Make sure that both queues have completed or are paused before updating a CCW table or
result table location.
Workaround:
If workaround one is not possible, the application code can monitor the CWP bits in the
QASR0. After it changes, it is safe to write a CCW table or result register location. The safe
time is equal to the input sample time of the next conversion (4-18 QCLKs).
Workaround:
If workarounds one and two are not possible, it is possible to update a CCW or result register
location while a queue is active by using the following sequence:
Read status register 0 and save the CWP value
Perform the write
Read CCW locations pointed to by CWP and CWP+1 to check if they are corrupted
Fix any of the possibly corrupted locations
The above sequence should be safe. If a CCW location is corrupted, it is not used until a
queue wraps around back to this CCW. The user has one conversion time to perform the
corruption checks and fixes. There should be plenty of time to do this without worrying about
another CCW corruption.
Fix plan:
Currently, there are no plans to fix this.
SECF031: GPIO Inputs Behave Inappropriately with 10k Ohm Pull Downs
Errata type:
Silicon
Affects:
Ports
Description:
GPIO inputs that shouldn't have internal pull-ups, behave as if internal pull-ups are enabled
when pull-down resistors larger than 10k ohm are used.
To achieve 5V tolerance for the I/O pads, a pull-up device is used to latch the input value of
the pads while protecting internal circuitry to direct exposure to potentials above 3.6V. These
pull-up devices are not disabled after stimulus is removed and a pull-down resistor value larger
than 10k ohm is used.
Workaround:
To disable the pull-up, a pull-down resistor value of 10k Ohm or less is needed.
Fix plan:
Currently, there are no plans to fix this.
SECF037: Phase Relationship Between CLKOUT and CLKIN Not Preserved When Using
PLL
Errata type:
Silicon
Affects:
PLL
Description:
In all PLL modes, the CLKOUT phase relationship to the input clock drifts by 25-33%.
MCF5282 Chip Errata, Rev 8, 02/2015
8 Freescale Semiconductor, Inc.
Workaround:
Use bypass mode, by setting CLKMOD[1:0] to 00. The CLKOUT to CLKIN phase relationship
is maintained.
Fix plan:
Currently, there are no plans to fix this.
SECF006: FEC Duplicate Transmission
Errata type:
Silicon
Affects:
FEC
Description:
In some cases, the FEC transmits single frames more than once. The FEC fetches transmit
buffer descriptors (TxBDs) and the corresponding Tx data continuously until the Tx FIFO is full.
It does not determine whether the TxBD to be fetched is already being processed internally (as
a result of a wrap). As the FEC nears the end of the transmission of one frame, it begins to
DMA the data for the next frame. To remain one BD ahead of the DMA, it also fetches the
TxBD for the next frame. It is possible that the FEC fetches from memory a BD that has
already been processed but not yet written back (it is read a second time with the R bit set). In
this case, the data is fetched and transmitted again.
Workaround:
Using at least three TxBDs fixes this problem for large frames, but not for small frames. To
ensure correct operation for large or small frames, one of the following must be true:
The FEC software driver ensures that there is always at least one TxBD with the Ready
bit cleared.
Every frame uses more than one TxBD and every TxBD, but the last is written back
immediately after the data is fetched.
The FEC software driver ensures a minimum frame size, n. The minimum number of TxBDs is
then rounded up to the nearest integer (though the result cannot be less than 3). The default
Tx FIFO size is 192 Bytes; this size is programmable.
Fix plan:
Currently, there are no plans to fix this.
SECF123: FlexCAN Writing to an Active Receive MB May Corrupt MB Contents
Errata type:
Silicon
Affects:
FlexCAN
Description:
Deactivating a FlexCAN receive message buffer (MB) may cause corruption of another active
receive MB, including the ID field, if the following sequence occurs.
1.
A receive MB is locked via reading the control/status word, and has a pending frame in
the temporary receive serial message buffer (SMB).
2. A second frame is received that matches a second receive MB, and is queued in the
second SMB.
3. The first MB is unlocked during the time between receiving the CRC field and the sixth bit
of end of frame (EOF) of the second frame.
4. The second MB is deactivated within nine bus clock cycles of the sixth bit of EOF,
resulting in corruption of the first MB.
During standard use of the FlexCAN hardware, the errata can appear during heavy
communications with several Rx MBs at a low baudrate and while using Rx extended MB’s
IDs. This can be easily observed by checking ID value overwrite. In all cases, CAN
transmissions from the processor are not affected at any moment.
MCF5282 Chip Errata, Rev 8, 02/2015
Freescale Semiconductor, Inc. 9

MCF5281CVM80

Mfr. #:
Manufacturer:
NXP / Freescale
Description:
32-bit Microcontrollers - MCU MCF5281 V2CORE 256KFLASH
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union