MK60FX512VLQ15 - Freescale Semiconductor

KINETIS_3N96B

Rev. 07 A U G 2013

Mask Set Errata for Mask 3N96B

This document contains a subset of errata for Kinetis Mask Set 3N96B.

Errata for security-related modules are not included in this document

and are only available after a nondisclosure agreement (NDA) has

been signed.

For more information on obtaining an NDA and viewing the

comprehensive errata list for this mask set, please contact your local

Freescale sales representative.

Introduction

This report applies to mask for these products:

• KINETIS_3N96B

Errata ID Errata Title

6378 Cache: Cache write buffer error enable (MCM_ISCR[CWBEE]) does not work

6939 Core: Interrupted loads to SP can cause erroneous behavior

6940 Core: VDIV or VSQRT instructions might not complete correctly when very short ISRs are used

5243 DDRMC: It is possible for data corruption to occur If the value programmed in RDLATADJ is larger than

the CAS latency,

5241 DDRMC: Putting the memory into a power down mode while DDR_CR11[AREFMODE] is set can prevent

the DDRMC from providing refreshes to the memory while it is powered down.

5263 DDRMC: While the memory is in a power down state, setting DDR_CR11[AREF] in an attempt to force a

refresh command will cause a refresh cycle to be missed.

4588 DMAMUX: When using PIT with "always enabled" request, DMA request does not deassert correctly

6358 ENET: Write to Transmit Descriptor Active Register (ENET_TDAR) is ignored

5861 FTM: FTM2 and FTM3 do not correctly enter BDM mode when a debugger connection is active

4710 FTM: FTMx_PWMLOAD register does not support 8-/16-bit accesses

6484 FTM: The process of clearing the FTMx_SC[TOF] bit does not work as expected under a certain condition

when the FTM counter reaches FTM_MOD value.

6573 JTAG: JTAG TDO function on the PTA2 disables the pull resistor

3964 JTAGC: When debug is active a wakeup from STOP or VLPS with interrupt causes a hard fault interrupt.

4553 LCDC: Cursor Color Limited in 24bpp Mode

4569 LCDC: Graphic Window Color Key Limited in 24bpp Mode

4570 LCDC: Graphic Window May Shift Pixel Data

4571 LCDC: LCDC can only use half of internal SRAM for frame buffer

3898 MCG: Setting the MCG_C6[PLLS] bit will enable both OSC0 and OSC1.

4590 MCG: Transitioning from VLPS to VLPR low power modes while in BLPI clock mode is not supported.

Table continues on the next page...

Freescale Semiconductor KINETIS_3N96B_

Mask Set Errata Rev 07 AUG 2013

Mask Set Errata for Mask

Errata ID Errata Title

4176 NMI: NMI interrupt service routine (ISR) might not be called when MCU wakes up from VLLSx modes.

3794 NVIC: NMI interrupt does not wakeup MCU from STOP and VLPS

5927 Operating requirements: Change to minimum VDD spec

5667 PMC: When used as an input to ADC or CMP modules, the PMC bandgap 1-V voltage reference is not

available in VLPx, LLS, or VLLSx modes

5130 SAI: Under certain conditions, the CPU cannot reenter STOP mode via an asynchronous interrupt

wakeup event

3981 SDHC: ADMA fails when data length in the last descriptor is less or equal to 4 bytes

3982 SDHC: ADMA transfer error when the block size is not a multiple of four

4624 SDHC: AutoCMD12 and R1b polling problem

3977 SDHC: Does not support Infinite Block Transfer Mode

4627 SDHC: Erroneous CMD CRC error and CMD Index error may occur on sending new CMD during data

transfer

3980 SDHC: Glitch is generated on card clock with software reset or clock divider change

6934 SDHC: Issues with card removal/insertion detection

3983 SDHC: Problem when ADMA2 last descriptor is LINK or NOP

3978 SDHC: Software can not clear DMA interrupt status bit after read operation

3984 SDHC: eSDHC misses SDIO interrupt when CINT is disabled

3941 SIM/DDR: SIM_SOPT2[FBSL] does not determine allowable DDR controller accesses when security is

enabled

4218 SIM/FLEXBUS: SIM_SCGC7[FLEXBUS] bit should be cleared when the FlexBus is not being used.

5952 SMC: Wakeup via the LLWU from LLS/VLLS to RUN to VLPR incorrectly triggers an immediate wakeup

from the next low power mode entry

7166 SOC: SDHC, NFC, USBOTG, and cache modules are not clocked correctly in low-power modes

3926 TSI: The TSI will run several scan cycles during reference clock instead of scanning each electrode once

2638 TSI: The counter registers are not immediately updated after the EOSF bit is set.

4546 TSI: The counter values reported from TSI increase when in low power modes (LLS, VLLS1, VLLS2,

VLLS3)

4181 TSI: When the overrun flag is set, the TSI scanning sequence will exhibit undefined behavior.

4935 UART: CEA709.1 features not supported

7027 UART: During ISO-7816 T=0 initial character detection invalid initial characters are stored in the RxFIFO

7028 UART: During ISO-7816 initial character detection the parity, framing, and noise error flags can set

6472 UART: ETU compensation needed for ISO-7816 wait time (WT) and block wait time (BWT)

4647 UART: Flow control timing issue can result in loss of characters if FIFO is not enabled

4945 UART: ISO-7816 T=1 mode receive data format with a single stop bit is not supported

3892 UART: ISO-7816 automatic initial character detect feature not working correctly

7029 UART: In ISO-7816 T=1 mode, CWT interrupts assert at both character and block boundaries

7090 UART: In ISO-7816 mode, timer interrupts flags do not clear

7031 UART: In single wire receive mode UART will attempt to transmit if data is written to UART_D

5704 UART: TC bit in UARTx_S1 register is set before the last character is sent out in ISO7816 T=0 mode

7091 UART: UART_S1[NF] and UART_S1[PE] can set erroneously while UART_S1[FE] is set

7092 UART: UART_S1[TC] is not cleared by queuing a preamble or break character

Table continues on the next page...

Mask Set Errata for Mask, Rev 07 AUG 2013

2 Freescale Semiconductor, Inc.

Errata ID Errata Title

5928 USBOTG: USBx_USBTRC0[USBRESET] bit does not operate as expected in all cases

6933 eDMA: Possible misbehavior of a preempted channel when using continuous link mode

e6378: Cache: Cache write buffer error enable (MCM_ISCR[CWBEE]) does not work

Errata type: Errata

Description: The CM4 cache contains a one entry write buffer. The one entry write buffer is controlled by

the write buffer enable bit in the cache control registers. If enabled, it will buffer all writethrough

and non-cacheable writes. Also, if enabled, it will break the direct association between a write

bus fault and the processor completing the write (i.e.write fault imprecise).

The processor will then not see this fault. It is possible to enable fault reporting and capture

fault information on buffered writes that create bus errors. This logic is in the MCM

(Miscellaneous Control Module). The CWBEE (Cache Write Buffer Error Enable) bit in the

MCM_ISCR (Interrupt Status and Control Register) enables an interrupt to be generated on

buffered writes that fault. There are also registers in the MCM to capture fault information

(address, attributes, write data) plus a sticky bit to indicate a write buffer fault or multiple write

buffer bus faults have occurred. This interrupt will be imprecise and occur sometime after the

write fault.

However, due to a logic error, the CWBEE function is not working. On write buffer accesses

that fault, the write fault address, attributes and data are correctly captured in the MCM fault

information registers but even if CWBEE is set, no interrupt is generated.

Workaround: 1. If a write buffer is enabled and a write access is being run to an address area that may fault,

directly check the Cache Write Buffer Fault indicator in the MCM module.

2. Don't enable the cache write buffers, keeping all writethrough and non-cacheable write

faults precise.

e6939: Core: Interrupted loads to SP can cause erroneous behavior

Errata type: Errata

Description: ARM Errata 752770: Interrupted loads to SP can cause erroneous behavior

Affects: Cortex-M4, Cortex-M4F

Fault Type: Programmer Category B

Fault Status: Present in: r0p0, r0p1 Open.

Description

If an interrupt occurs during the data-phase of a single word load to the stack-pointer (SP/

R13), erroneous behavior can occur. In all cases, returning from the interrupt will result in the

load instruction being executed an additional time. For all instructions performing an update to

the base register, the base register will be erroneously updated on each execution, resulting in

the stack-pointer being loaded from an incorrect memory location.

The affected instructions that can result in the load transaction being repeated are:

1) LDR SP,[Rn],#imm

2) LDR SP,[Rn,#imm]!

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 3

3) LDR SP,[Rn,#imm]

4) LDR SP,[Rn]

5) LDR SP,[Rn,Rm]

The affected instructions that can result in the stack-pointer being loaded from an incorrect

memory address are:

1) LDR SP,[Rn],#imm

2) LDR SP,[Rn,#imm]!

Conditions

1) An LDR is executed, with SP/R13 as the destination

2) The address for the LDR is successfully issued to the memory system

3) An interrupt is taken before the data has been returned and written to the stack-pointer.

Implications

Unless the load is being performed to Device or Strongly-Ordered memory, there should be no

implications from the repetition of the load. In the unlikely event that the load is being

performed to Device or Strongly-Ordered memory, the repeated read can result in the final

stack-pointer value being different than had only a single load been performed.

Interruption of the two write-back forms of the instruction can result in both the base register

value and final stack-pointer value being incorrect. This can result in apparent stack corruption

and subsequent unintended modification of memory.

Workaround: Both issues may be worked around by replacing the direct load to the stack-pointer, with an

intermediate load to a general-purpose register followed by a move to the stack-pointer.

If repeated reads are acceptable, then the base-update issue may be worked around by

performing the stack pointer load without the base increment followed by a subsequent ADD or

SUB instruction to perform the appropriate update to the base register.

e6940: Core: VDIV or VSQRT instructions might not complete correctly when very

short ISRs are used

Errata type: Errata

Description: ARM Errata 709718: VDIV or VSQRT instructions might not complete correctly when very

short ISRs are used

Affects: Cortex-M4F

Fault Type: Programmer Category B

Fault Status: Present in: r0p0, r0p1 Open.

On Cortex-M4 with FPU, the VDIV and VSQRT instructions take 14 cycles to execute. When

an interrupt is taken a VDIV or VSQRT instruction is not terminated, and completes its

execution while the interrupt stacking occurs. If lazy context save of floating point state is

enabled then the automatic stacking of the floating point context does not occur until a floating

point instruction is executed inside the interrupt service routine.

Lazy context save is enabled by default. When it is enabled, the minimum time for the first

instruction in the interrupt service routine to start executing is 12 cycles. In certain timing

conditions, and if there is only one or two instructions inside the interrupt service routine, then

the VDIV or VSQRT instruction might not write its result to the register bank or to the FPSCR.

Mask Set Errata for Mask, Rev 07 AUG 2013

4 Freescale Semiconductor, Inc.

Workaround: A workaround is only required if the floating point unit is present and enabled. A workaround is

not required if the memory system inserts one or more wait states to every stack transaction.

There are two workarounds:

1) Disable lazy context save of floating point state by clearing LSPEN to 0 (bit 30 of the

FPCCR at address 0xE000EF34).

2) Ensure that every interrupt service routine contains more than 2 instructions in addition to

the exception return instruction.

e5243: DDRMC: It is possible for data corruption to occur If the value programmed in

RDLATADJ is larger than the CAS latency,

Errata type: Errata

Description: If DDR_CR56[RDLATADJ] is programmed to be larger than the CAS latency of the device

there is the possibility that data corruption may occur because the controller will pre-maturely

issue DFI update requests.

Workaround: Do not set DDR_CR56[RDLATADJ] to a value larger than the CAS latency of the device. If a

larger delay is required, set the RDLATADJ equal to the CAS latency of the device and use the

DDR_CR52[RDDTENBAS] parameter to add any additional delay that is required.

e5241: DDRMC: Putting the memory into a power down mode while

DDR_CR11[AREFMODE] is set can prevent the DDRMC from providing

refreshes to the memory while it is powered down.

Errata type: Errata

Description: The DDR_CR11[AREFMODE] parameter is used to determine when a refresh command is

issued to the memory. The refresh command can either be issued at the next memory

command boundary, or it can be held off and issued only at the next system command

boundary. One system command may result in many memory commands, depending on how

much data the system command is moving.

When the AREFMODE parameter is set, if a refresh is needed the controller will hold off this

refresh until the next system command boundary. If the memory is manually placed into power

down, and this happens at a memory command boundary but not at a system command

boundary the logic holding off the refresh will erroneously continue to hold off the refresh for

the duration of time the memory is placed in power down.

If the memory does not receive refreshes while in power down it is possible for the contents of

the memory to degrade and become corrupted.

This condition can only occur if the low-power mode entry is done manually. This is not an

issue if you are using the LPAUTO parameter to automatically enter low-power modes.

Workaround: Always clear the DDR_CR11[AREFMODE] bit before manually entering a power-down mode.

If you wish to have normal operations with the AREFMODE bit set, you can do so, but ensure

that you clear it before you manually place the memory into power down. After you bring the

memory out of power down you can then set the AREFMODE bit again.

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 5

e5263: DDRMC: While the memory is in a power down state, setting DDR_CR11[AREF]

in an attempt to force a refresh command will cause a refresh cycle to be

missed.

Errata type: Errata

Description: When the DDRMC has the auto refresh mode enabled (DDR_CR11[TREFEN] = 1), it will load

a counter with the value in the TREF parameter, count to zero, then issue a refresh to the

memory, reload the counter and repeat this cycle. There are several events which use the

count value of zero from this counter to function. If a refresh is requested via a write to the

AREF parameter, the counter associated with the automatic issuance of refreshes by the

DDRMC will automatically be reloaded with the value in the TREF parameter and will not be

able to achieve a count of zero.

One of the key pieces of logic which monitors the refresh counter equaling zero is logic

associated with bringing the memory out of a power down state to enable the controller to

issue a refresh command to the memory. So if the memory is in a power down state and a

refresh is requested via a method other than the automatic refresh counter reaching zero the

memory will not be able to be brought out of the power down state to allow the refresh to

occur. This will result in extra delay before the refresh can be issued to the memory, or will

result in the memory never being refreshed while in a power down state if the automatic

refresh counter is disabled.

Example

Assume the memory is in a power down state and the automatic refresh mode of the DDRMC

is enabled. The counter will be loaded with the value in the TREF parameter and will begin

counting down. If, when the counter reaches a value near zero (but not zero), software write to

AREF paramter, the counter will be automatically reloaded with the value in the TREF

parameter and will then have to count down to 0 before the controller will bring the memory out

of the power down state and issue the refresh. In this case the memory will fail to receive one

refresh.

Workaround: Do not use the DDR_CR11[AREF] bit to attempt a refresh command to the memory while the

memory is in power down mode. Always enable the automatic refresh feature of the DDRMC

(set DDR_CR11[TREFEN]) and rely on it to provide refreshes to the memory.

e4588: DMAMUX: When using PIT with "always enabled" request, DMA request does

not deassert correctly

Errata type: Errata

Description: The PIT module is not assigned as a stand-alone DMA request source in the DMA request

mux. Instead, the PIT is used as the trigger for the DMAMUX periodic trigger mode. If you want

to use one of the PIT channels for periodic DMA requests, you would use the periodic trigger

mode in conjunction with one of the "always enabled" DMA requests. However, the DMA

request does not assert correctly in this case.

Instead of sending a single DMA request every time the PIT expires, the first time the PIT

triggers a DMA transfer the "always enabled" source will not negate its request. This results in

the DMA request remaining asserted continuously after the first trigger.

Workaround: Use of the PIT to trigger DMA channels where the major loop count is greater than one is not

recommended. For periodic triggering of DMA requests with major loop counts greater than

one, we recommended using another timer module instead of the PIT.

Mask Set Errata for Mask, Rev 07 AUG 2013

6 Freescale Semiconductor, Inc.

If using the PIT to trigger a DMA channel where the major loop count is set to one, then in

order to get the desired periodic triggering, the DMA must do the following in the interrupt

service routine for the DMA_DONE interrupt:

1. Set the DMA_TCDn_CSR[DREQ] bit and configure DMAMUX_CHCFGn[ENBL] = 0

2. Then again DMAMUX_CHCFGn[ENBL] = 1, DMASREQ=channel in your DMA DONE

interrupt service routine so that "always enabled" source could negate its request then DMA

request could be negated.

This will allow the desired periodic triggering to function as expected.

e6358: ENET: Write to Transmit Descriptor Active Register (ENET_TDAR) is ignored

Errata type: Errata

Description: If the ready bit in the transmit buffer descriptor (TxBD[R]) is previously detected as not set

during a prior frame transmission, then the ENET_TDAR[TDAR] bit is cleared at a later time,

even if additional TxBDs were added to the ring and the ENET_TDAR[TDAR] bit is set. This

results in frames not being transmitted until there is a 0-to-1 transition on ENET_TDAR[TDAR].

Workaround: Code can use the transmit frame interrupt flag (ENET_EIR[TXF]) as a method to detect

whether the ENET has completed transmission and the ENET_TDAR[TDAR] has been

cleared. If ENET_TDAR[TDAR] is detected as cleared when packets are queued and waiting

for transmit, then a write to the TDAR bit will restart TxBD processing.

e5861: FTM: FTM2 and FTM3 do not correctly enter BDM mode when a debugger

connection is active

Errata type: Errata

Description: The FTM modules include an FTMxCONF[BDMMODE] field that can be configured to control

the operation of the FTM when debugging. There is a connection error in the FTM2 and FTM3

integration that prevents those modules from detecting when debug is active. As a result these

two modules will operate in normal functional mode even while debugging.

Workaround: The FTMs behave as expected during normal operation (no debugger present). The issue only

impacts the ability to control the operation and stop the timers while debugging.

e4710: FTM: FTMx_PWMLOAD register does not support 8-/16-bit accesses

Errata type: Errata

Description: The FTM PWM Load register should support 8-bit and 16-bit accesses. However, the

FTMx_PWMLOAD[LDOK] bit is cleared automatically by FTM with these sized accesses, thus

disabling the loading of the FTMx_MOD, FTMx_CNTIN, and FTMx_CnV registers.

Workaround: Always use a 32-bit write access to modify contents of the FTMx_PWMLOAD register.

e6484: FTM: The process of clearing the FTMx_SC[TOF] bit does not work as expected

under a certain condition when the FTM counter reaches FTM_MOD value.

Errata type: Errata

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 7

Description: The process of clearing the TOF bit does not work as expected when

FTMx_CONF[NUMTOF] != 0 and the current TOF count is less than FTMx_CONF[NUMTOF],

if the FTM counter reaches the FTM_MOD value between the reading of the TOF bit and the

writing of 0 to the TOF bit. If the above condition is met, the TOF bit remains set, and if the

TOF interrupt is enabled (FTMx_SC[TOIE] = 1), the TOF interrupt also remains asserted.

Workaround: Two possible workarounds exist for this erratum and the decision on which one to use is based

on the requirements of your particular application.

1) Repeat the clearing sequence mechanism until the TOF bit is cleared.

Below is a pseudo-code snippet that would need to be included in the TOF interrupt routine.

while (FTM_SC[TOF]!=0)

{

void FTM_SC() ; // Read SC register

FTM_SC[TOF]=0 ; // Write 0 to TOF bit

}

2) With FTMx_CONF[TOFNUM] = 0 and a variable in the software, count the number of times

that the TOF bit is set. In the TOF interrupt routine, clear the TOF bit and increment the

variable that counts the number of times that the TOF bit was set.

e6573: JTAG: JTAG TDO function on the PTA2 disables the pull resistor

Errata type: Errata

Description: The JTAG TDO function on the PTA2 pin disables the pull resistor, but keeps the input buffer

enabled. Because the JTAG will tri-state this pin during JTAG reset (or other conditions), this

pin will float with the input buffer enabled. If the pin is unconnected in the circuit, there can be

increased power consumption in low power modes for some devices.

Workaround: Disable JTAG TDO functionality when the JTAG interface is not needed and left floating in a

circuit. Modify the PORTA_PCR2 mux before entering low power modes. Set the mux to a pin

function other than ALT7. If set up as a digital input and left unconnected in the circuit, then a

pull-up or pull-down should be enabled. Alternatively, an external pull device or external source

can be added to the pin.

Note: Enabling the pull resistor on the JTAG TDO function violates the JTAG specification.

e3964: JTAGC: When debug is active a wakeup from STOP or VLPS with interrupt

causes a hard fault interrupt.

Errata type: Errata

Description: When exiting STOP or VLPS back into RUN mode with an interrupt a hard fault interrupt is

caused when the JTAG debuger is enabled.

The MCU enters a pseudo STOP mode when the debugger is enabled.

The user cannot use the debugger to test code that wakes up from STOP with an interrupt.

Workaround: a. Disable the debugger with a Power off and on cycle before testing code that exits STOP or

VLPS with an interrupt.

Mask Set Errata for Mask, Rev 07 AUG 2013

8 Freescale Semiconductor, Inc.

b. From the debugger, while in STOP or VLPS, halt the MCU with the debugger tools before

triggering an interrupt.

e4553: LCDC: Cursor Color Limited in 24bpp Mode

Errata type: Errata

Description: The LCCMR register which determines the cursor color has a maximum of 6 bits per color

(18bpp). Thus when trying to use the cursor in 24bpp mode, the first two bits of each 8-bit

cursor color sent to the LCD are zero.

Workaround: The least significant 6 bits of each color can be used for the cursor color in 24bpp mode.

e4569: LCDC: Graphic Window Color Key Limited in 24bpp Mode

Errata type: Errata

Description: The GWCKR, GWCKG, and GWCKB fields in the LGWCR register determine which color in

the graphic window is transparent. These fields are each 6 bits in length (18bpp). This limits

the colors that can be used for the color key in 24bpp mode.

Workaround: In 24bpp mode, the color that is being keyed out must have the first two bits be zero for the

comparison to work. The lower 6 bits will be compared as usual.

e4570: LCDC: Graphic Window May Shift Pixel Data

Errata type: Errata

Description: When a graphic window is located at location (0,0) or (1,0), the data output to the LCD in the

graphic window will be shifted over by one pixel.

This means that the first piece of pixel data in your frame buffer will be the second pixel sent

out instead of the first pixel as expected. Then the second piece of data will be the third pixel

sent out, and so on. This continues throughout the buffer, so that the first pixel of the graphic

window display will come from the very end of the frame buffer data instead of from the very

front.

The end result is a pixel-wide line of data that should be on the far right of the graphic window

is instead displayed on the far left of the graphic window. The data displayed in the graphic

window is also one pixel further to the right than it should be.

Workaround: Ensure your graphic window is not located at either (0,0) or (1,0) or account for this shift in the

data being used for the graphic window.

e4571: LCDC: LCDC can only use half of internal SRAM for frame buffer

Errata type: Errata

Description: The LCDC background plane or graphic window requires that its frame buffer be with-in a 4MB

boundary, as address A[31:22] has a fixed value for a picture's image. As the LCDC tries to

read data from the internal SRAM, it will loop back to the start of that 4MB boundary, and into

invalid memory space, upon reaching address 0x2000_0000.

Thus only half of the available SRAM is available for a frame buffer instead of the entire

SRAM.

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 9

Workaround: Use the background plane to display data located in the first half of the SRAM, and place the

image in RAM so that it will be at the end of a line when it reaches location 0x1FFF_FFFF.

Then use the graphic window to display the data from the other half of SRAM starting at

0x2000_0000, taking care to place the graphic window so as to line up seamlessly with the

end of the background plane.

e3898: MCG: Setting the MCG_C6[PLLS] bit will enable both OSC0 and OSC1.

Errata type: Errata

Description: When the PLL is enabled by means of setting the MCG_C6[PLLS] bit, both OSC0 and OSC1

will be enabled. This will only occur when moving the MCG to PBE, BLPE or PEE modes.

Workaround: If an oscillator is not being used and PBE, BLPE or PEE modes are to be used, ensure that the

EREFS bit associated with the unused oscillator is cleared. The IO pins associated with that

oscillator should also be configured as GPIO outputs driving a logic 0. This will place the IO

pads in a consistent state and keep excess current consumption to a minimum level.

e4590: MCG: Transitioning from VLPS to VLPR low power modes while in BLPI clock

mode is not supported.

Errata type: Errata

Description: Transitioning from VLPS mode back to VLPR (LPWUI control bit = 0) while using BLPI clock

mode only, is not supported. During Fast IRC startup, the output clock frequency may exceed

the maximum VLPR operating frequency. This does not apply to the BLPE clock mode.

Workaround: There are two options for workarounds

a) Exit to Run instead of VLPR. Before entering VLPR set the LPWUI bit so that when exiting

VLPS mode the MCU exits to RUN mode instead of VLPR mode. With LPWUI set any interrupt

will exit VLPR or VLPS back into RUN mode. To minimize the impact of the higher RUN

current re-enter VLPR quickly.

b) Utilize MCG clock mode BLPE when transitioning from VLPS to VLPR modes.

e4176: NMI: NMI interrupt service routine (ISR) might not be called when MCU wakes

up from VLLSx modes.

Errata type: Errata

Description: When MCU wakes up from VLLSx modes via NMI pin the NMI ISR might not be called if the

NMI pulse width is lower than 120us..

Workaround: NMI pulse width must be asserted for at least 120usec to ensure NMI ISR is called and

entered. Note that a short NMI pulse will still wakeup the part, and the LLWU ISR will still be

entered.

Mask Set Errata for Mask, Rev 07 AUG 2013

10 Freescale Semiconductor, Inc.

e3794: NVIC: NMI interrupt does not wakeup MCU from STOP and VLPS

Errata type: Errata

Description: NMI interrupt does not wakeup MCU from STOP and VLPS when the bits CSYSPWRUPREQ

and CDBGPWRUPREQ in the Control/Status Register of the DAP Port are cleared.

Workaround: If a debugger connection is established, the CSYSPWRUPREQ and CDBGPWRUPREQ bits

are set by default, so an NMI interrupt will wake up the MCU from STOP and VLPS modes. In

the absence of a debug connection and after a POR event, the bits will be cleared and thus an

NMI interrupt will not wake the MCU.

e5927: Operating requirements: Change to minimum VDD spec

Errata type: Errata

Description: The minimum operating voltage for VDD is 2.0V.

Workaround: Ensure that VDD is 2.0V or higher. Keep in mind that if VDD_DDR is used, that VDD must also

be higher than VDD_DDR as per the original specification.

e5667: PMC: When used as an input to ADC or CMP modules, the PMC bandgap 1-V

voltage reference is not available in VLPx, LLS, or VLLSx modes

Errata type: Errata

Description: The Power Management Controller (PMC) bandgap 1-V reference is not available as an input

to the Analog-to-Digital Converter (ADC) module (using ADC input channel AD27) or the

Comparator (CMP) module (using CMP input IN6) in Very Low Power Run (VLPR), Very Low

Power Wait (VLPW), Very Low Power Stop (VLPS), Low Leakage Stop (LLS), Very Low

Leakage Stop3 (VLLS3), Very Low Leakage Stop2 (VLLS2), Very Low Leakage Stop1

(VLLS1), or Very Low Leakage Stop0 (VLLS0) modes.

This erratum does not apply to the VREF module 1.2 V reference voltage.

Workaround: Use of the PMC bandgap 1-V reference voltage as an input to the ADC and CMP modules

requires the MCU to be in Run, Wait, or Stop modes.

e5130: SAI: Under certain conditions, the CPU cannot reenter STOP mode via an

asynchronous interrupt wakeup event

Errata type: Errata

Description: If the SAI generates an asynchronous interrupt to wake the core and it attempts to reenter

STOP mode, then under certain conditions the STOP mode entry is blocked and the

asynchronous interrupt will remain set.

This issue applies to interrupt wakeups due to the FIFO request flags or FIFO warning flags

and then only if the time between the STOP mode exit and subsequent STOP mode reentry is

less than 3 asynchronous bit clock cycles.

Workaround: Ensure that at least 3 bit clock cycles elapse following an asynchronous interrupt wakeup

event, before STOP mode is reentered.

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 11

e3981: SDHC: ADMA fails when data length in the last descriptor is less or equal to 4

bytes

Errata type: Errata

Description: A possible data corruption or incorrect bus transactions on the internal AHB bus, causing

possible system corruption or a stall, can occur under the combination of the following

conditions:

1. ADMA2 or ADMA1 type descriptor

2. TRANS descriptor with END flag

3. Data length is less than or equal to 4 bytes (the length field of the corresponding descriptor

is set to 1, 2, 3, or 4) and the ADMA transfers one 32-bit word on the bus

4. Block Count Enable mode

Workaround: The software should avoid setting ADMA type last descriptor (TRANS descriptor with END

flag) to data length less than or equal to 4 bytes. In ADMA1 mode, if needed, a last NOP

descriptor can be appended to the descriptors list. In ADMA2 mode this workaround is not

feasible due to ERR003983.

e3982: SDHC: ADMA transfer error when the block size is not a multiple of four

Errata type: Errata

Description: Issue in eSDHC ADMA mode operation. The eSDHC read transfer is not completed when

block size is not a multiple of 4 in transfer mode ADMA1 or ADMA2. The eSDHC DMA

controller is stuck waiting for the IRQSTAT[TC] bit in the interrupt status register.

The following examples trigger this issue:

1. Working with an SD card while setting ADMA1 mode in the eSDHC

2. Performing partial block read

3. Writing one block of length 0x200

4. Reading two blocks of length 0x22 each. Reading from the address where the write

operation is performed. Start address is 0x512 aligned. Watermark is set as one word during

read. This read is performed using only one ADMA1 descriptor in which the total size of the

transfer is programmed as 0x44 (2 blocks of 0x22).

Workaround: When the ADMA1 or ADMA2 mode is used and the block size is not a multiple of 4, the block

size should be rounded to the next multiple of 4 bytes via software. In case of write, the

software should add the corresponding number of bytes at each block end, before the write is

initialized. In case of read, the software should remove the dummy bytes after the read is

completed.

For example, if the original block length is 22 bytes, and there are several blocks to transfer,

the software should set the block size to 24. The following data is written/stored in the external

memory:

4 Bytes valid data

Mask Set Errata for Mask, Rev 07 AUG 2013

12 Freescale Semiconductor, Inc.

4 Bytes valid data

2 Bytes valid data + 2 Byte dummy data

4 Bytes valid data

2 Bytes valid data + 2 Byte dummy data

In this example, 48 (24 x 2) bytes are transferred instead of 44 bytes. The software should

remove the dummy data.

e4624: SDHC: AutoCMD12 and R1b polling problem

Errata type: Errata

Description: Occurs when a pending command which issues busy is completed. For a command with R1b

response, the proper software sequence is to poll the DLA for R1b commands to determine

busy state completion. The DLA polling is not working properly for the ESDHC module and

thus the DLA bit in PRSSTAT register cannot be polled to wait for busy state ompletion. This is

relevant for all eSDHC ports (eSDHC1-4 ports).

Workaround: Poll bit 24 in PRSSTAT register (DLSL[0] bit) to check that wait busy state is over.

e3977: SDHC: Does not support Infinite Block Transfer Mode

Errata type: Errata

Description: The eSDHC does not support infinite data transfers, if the Block Count register is set to one,

even when block count enable is not set.

Workaround: The following software workaround can be used instead of the infinite block mode:

1. Set BCEN bit to one and enable block count

2. Set the BLKCNT to the maximum value in Block Attributes Register (BLKATTR) (0xFFFFfor

65535 blocks)

e4627: SDHC: Erroneous CMD CRC error and CMD Index error may occur on sending

new CMD during data transfer

Errata type: Errata

Description: When sending new, non data CMD during data transfer between the eSDHC and EMMC card,

the module may return an erroneous CMD CRC error and CMD Index error. This occurs when

the CMD response has arrived at the moment the FIFO clock is stopped. The following bits

after the start bit of the response are wrongly interpreted as index, generating the CRC and

Index errors.

The data transfer itself is not impacted.

The rate of occurrence of the issue is very small, as there is a need for the following

combination of conditions to occur at the same cycle:

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 13

• The FIFO clock is stopped due to FIFO full or FIFO empty

• The CMD response start bit is received

Workaround: The recommendation is to not set FIFO watermark level to a too small value in order to reduce

frequency of clock pauses.

The problem is identified by receiving the CMD CRC error and CMD Index error. Once this

issue occurs, one can send the same CMD again until operation is successful.

e3980: SDHC: Glitch is generated on card clock with software reset or clock divider

change

Errata type: Errata

Description: A glitch may occur on the SDHC card clock when the software sets the RSTA bit (software

reset) in the system control register. It can also be generated by setting the clock divider value.

The glitch produced can cause the external card to switch to an unknown state. The

occurrence is not deterministic.

Workaround: A simple workaround is to disable the SD card clock before the software reset, and enable it

when the module resumes the normal operation. The Host and the SD card are in a master-

slave relationship. The Host provides clock and control transfer across the interface.

Therefore, any existing operation is discarded when the Host controller is reset.

The recommended flow is as follows:

1. Software disable bit[3], SDCLKEN, of the System Control Register

2. Trigger software reset and/or set clock divider

3. Check bit[3], SDSTB, of the Present State Register for stable clock

4. Enable bit[3], SDCLKEN, of the System Control Register.

Using the above method, the eSDHC cannot send command or transfer data when there is a

glitch in the clock line, and the glitch does not cause any issue.

e6934: SDHC: Issues with card removal/insertion detection

Errata type: Errata

Description: SD cards include a 50K pullup that is used to detect when a card is inserted. A weak (500K)

pulldown on the line is sufficient to allow for the first card insertion to be detected (the 50K

pullup on the card will dominate the pulldown and cause the signal to go high).

The 5 V tolerant I/O cells used on this processor require a pulldown resistor stronger than 50K

to ensure that a signal will reach a proper low voltage level after the pin has been high. A

stronger pulldown cannot be used on the SD card detect signal because it would prevent the

card detection from working correctly. Because of this, the automatic card removal detection

will not work reliably.

Workaround: A software workaround can be used to check for card removal or verify that a card is still

present by redetecting it.

1. Temporarily change the appropriate PORTx_PCRn to configure the SD card detect pin as a

GPIO.

2. Configure the GPIO as an output driving low.

Mask Set Errata for Mask, Rev 07 AUG 2013

14 Freescale Semiconductor, Inc.

3. Leave the pin in this state for several us. The exact amount of time required can vary

depending on pin loading.

4. Change the PORTx_PCRn to switch the pin back to its SDHC function.

When this sequence is complete the SDHC will be ready to detect card insertion again. The

sequence above should be run periodically or if an unexpected response is received from the

SD card. The procedure will discharge the I/O cell so that the card detect pin is low and an SD

card (if present) can be detected.

e3983: SDHC: Problem when ADMA2 last descriptor is LINK or NOP

Errata type: Errata

Description: ADMA2 mode in the eSDHC is used for transfers to/from the SD card. There are three types of

ADMA2 descriptors: TRANS, LINK or NOP. The eSDHC has a problem when the last

descriptor (which has the End bit '1') is a LINK descriptor or a NOP descriptor.

In this case, the eSDHC completes the transfers associated with this descriptor set, whereas it

does not even start the transfers associated with the new data command. For example, if a

WRITE transfer operation is performed on the card using ADMA2, and the last descriptor of

the WRITE descriptor set is a LINK descriptor, then the WRITE is successfully finished. Now, if

a READ transfer is programmed from the SD card using ADMA2, then this transfer does not go

through.

Workaround: Software workaround is to always program TRANS descriptor as the last descriptor.

e3978: SDHC: Software can not clear DMA interrupt status bit after read operation

Errata type: Errata

Description: After DMA read operation, if the SDHC System Clock is automatically gated off, the DINT

status can not be cleared by software.

Workaround: Set HCKEN bit before starting DMA read operation, to disable SDHC System Clock auto-

gating feature; after the DINT and TC bit received when read operation is done, clear HCKEN

bit to re-enable the SDHC System Clock auto-gating feature.

e3984: SDHC: eSDHC misses SDIO interrupt when CINT is disabled

Errata type: Errata

Description: An issue is identified when interfacing the SDIO card. There is a case where an SDIO interrupt

from the card is not recognized by the hardware, resulting in a hang.

If the SDIO card lowers the DAT1 line (which indicates an interrupt) when the SDIO interrupt is

disabled in the eSDHC registers (that is, CINTEN bits in IRQSTATEN and IRQSIGEN are set

to zero), then, after the SDIO interrupt is enabled (by setting the CINTEN bits in IRQSTATEN

and IRQSIGEN registers), the eSDHC does not sense that the DAT1 line is low. Therefore, it

fails to set the CINT interrupt in IRQSTAT even if DAT1 is low.

Generally, CINTEN bit is disabled in interrupt service.

The SDIO interrupt service steps are as follows:

1. Clear CINTEN bit in IRQSTATEN and IRQSIGEN.

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 15

2. Reset the interrupt factors in the SDIO card and write 1 to clear the CINT interrupt in

IRQSTAT.

3. Re-enable CINTEN bit in IRQSTATEN and IRQSIGEN.

If a new SDIO interrupt from the card occurs between step 2 and step 3, the eSDHC skips it.

Workaround: The workaround interrupt service steps are as follows:

1. Clear CINTEN bit in IRQSTATEN and IRQSIGEN.

2. Reset the interrupt factors in the SDIO card and write 1 to clear CINT interrupt in IRQSTAT.

3. Clear and then set D3CD bit in the PROCTL register. Clearing D3CD bit sets the reverse

signal of DAT1 to low, even if DAT1 is low. After D3CD bit is re-enabled, the eSDHC can catch

the posedge of the reversed DAT1 signal, if the DAT1 line is still low.

4. Re-enable CINTEN bit in IRQSTATEN and IRQSIGEN.

e3941: SIM/DDR: SIM_SOPT2[FBSL] does not determine allowable DDR controller

accesses when security is enabled

Errata type: Errata

Description: On devices that include a DDR controller, the SIM_SOPT2[FBSL] field should determine what

FlexBus and DDR accesses are allowed when the device is secure, but currently the FBSL

field only controls the allowable FlexBus accesses.

Workaround: Until the feature is corrected customers should be aware that DDR could be used to execute

code even when the device is secure. Some applications might want to avoid using DDR when

secure and/or use the MPU to restrict the DDR to supervisor access only.

e4218: SIM/FLEXBUS: SIM_SCGC7[FLEXBUS] bit should be cleared when the FlexBus

is not being used.

Errata type: Errata

Description: The SIM_SCGC7[FLEXBUS] bit is set by default. This means that the FlexBus will be enabled

and come up in global chip select mode.

With some code sequence and register value combinations the core could attempt to prefetch

from the FlexBus even though it might not actually use the value it prefetched. In the case

where the FlexBus is unconfigured, this can result in a hung bus cycle on the FlexBus.

Workaround: If the FlexBus is not being used, disabled the clock to the FlexBus during chip initialization by

clearing the SIM_SCGC7[FLEXBUS] bit.

If the FlexBus will be used, then enable at least one chip select as early in the chip initialization

process as possible.

e5952: SMC: Wakeup via the LLWU from LLS/VLLS to RUN to VLPR incorrectly

triggers an immediate wakeup from the next low power mode entry

Errata type: Errata

Mask Set Errata for Mask, Rev 07 AUG 2013

16 Freescale Semiconductor, Inc.

Description: Entering VLPR immediately after an LLWU wakeup event from LLS/VLLS, will cause any

subsequent entry into LLS/VLLS to fail if entry into VLPR mode occurs before clearing the

pending LLWU interrupt.

Workaround: After an LLWU wakeup event from LLS/VLLS, the user must clear the LLWU interrupt prior to

entering VLPR mode.

e7166: SOC: SDHC, NFC, USBOTG, and cache modules are not clocked correctly in

low-power modes

Errata type: Errata

Description: The SDHC, NFC, and USBOTG are connected to a single master port on the crossbar switch

through a multiplexer. The modules themselves are still clocked in Wait mode, but the

multiplexer connecting them to the crossbar switch has its clock shut off immediately during

entry into low-power modes. This prevents these three modules from completing bus

transactions during any low-power mode entry or starting new bus transactions when the

system enters Wait mode (even though the modules themselves remain clocked in Wait).

In addition the cache tag and data RAMs have their clock gated off in Wait mode. This can

lead to corruption of cache contents during low-power entry.

Workaround: To resolve the low-power mode entry issue with the SDHC, NFC, and USBOTG, software

should ensure that all bus master operations for these three modules are complete before

requesting the system entry into any of the low-power modes. In addition, no bus traffic from

these modules should be generated while the system is in Wait.

To avoid cache corruption during low-power mode entry, the following code sequence should

be used for entry into low-power modes when the cache is enabled:

/* The LMEM writes below will perform NOP operations on both of the caches */

LMEM_PCCLCR = 0x09000001;

LMEM_PSCLCR = 0x09000001;

/* Wait for cache command to complete */

While (LMEM_PCCLCR & 1);

/* Wait for cache command to complete */

While (LMEM_PSCLCR & 1);

Asm(“DSB”);

Asm(“WFI”);

Asm("NOP");

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 17

The code sequence above must be executed from a memory location that is not cached

(SRAM_L is recommended). In addition, the start of the code sequence through the WFI must

execute uninterrupted. If an interrupt occurs between the start of the sequence and the WFI

instruction, then the code sequence must be restarted from the beginning. The NOPs in the

sequence can be replaced with other code if desired, as long as that code doesn't make

reference to any cached addresses.

e3926: TSI: The TSI will run several scan cycles during reference clock instead of

scanning each electrode once

Errata type: Errata

Description: The TSI will run several scan cycles during reference clock instead of scanning each electrode

once. For each automatic scanning period determined by AMCLKS (clock source), AMPSC

(prescaler) and SMOD (period modulo), TSI will scan during one reference clock cycle divided

by the AMPSC prescaler.

This does not affect the count result from TSI because TSI counters keep the last scan result.

Workaround: 1. Because counter results are not affected, a simple workaround is to use the smallest

prescaler possible and use a bigger SMOD value, this will minimize the number of extra scans,

thus also minimizing the amount of average extra current used by the module.

2. If strict control of number of scan cycles is needed, trigger scans with software control (using

the SWTS bit) and control time between scans with a separate timer. This solution is only

recommended if strict control of scan cycles is needed, if not, recommendation is to use

workaround 1.

e2638: TSI: The counter registers are not immediately updated after the EOSF bit is

set.

Errata type: Errata

Description: The counter registers are not immediately updated after the end of scan event (EOSF is set).

The counter registers will become available 0.25 ms after the EOSF flag is set. This also

applies for the end-of-scan interrupt, as it is triggered with the EOSF flag. This behavior will

occur both in continuous scan and in software triggered scan modes.

Workaround: Insert a delay of 0.25 ms or greater prior to accessing the counter registers after an end of

scan event or an end of scan interrupt that is triggered by the EOSF flag. This delay does not

need to be a blocking delay, so it can be executing other actions before reading the counter

registers. Notice that the out-of-range flag (OUTRGF) and interrupt occur after the counters

have been updated, so if the OUTRGF flag is polled or the out-of-range interrupt is used, the

workaround is not necessary.

e4546: TSI: The counter values reported from TSI increase when in low power modes

(LLS, VLLS1, VLLS2, VLLS3)

Errata type: Errata

Description: When the MCU goes into LLS or VLLSx modes, with the TSI enabled for wakeup, the counter

value reported by the TSI increases with respect to what was reported in active mode.

Because the wakeup threshold is calculated in active mode, it is highly likely that MCU will

wakeup immediately after going to low power.

Mask Set Errata for Mask, Rev 07 AUG 2013

18 Freescale Semiconductor, Inc.

Workaround: 1. Use Wait, Stop, or VLPS. These modes do not require any wakeup threshold calibration as

TSI remains in active mode and wakes up each end of scan so that normal baseline tracking

algorithm can be used.

2. To use LLS or VLLSx modes with the TSI as a wakeup source, calibrate the wakeup

threshold using the desired low power mode. During application initialization, configure the TSI

to exit low power via the LLWUI (low-leakage wake-up interrupt) with an End of Scan using the

desired wakeup electrode. For example enter LLS mode with automatic scanning enabled so

that after the first scan the TSI module causes an exit from low power at the end of scan. After

the wakeup event, read the TSIx_WUCNTR Register, this register will have the value for the

count during low power mode. Use this value to calculate THRSHLD register value.

e4181: TSI: When the overrun flag is set, the TSI scanning sequence will exhibit

undefined behavior.

Errata type: Errata

Description: When the overrun flag is set, the TSI scanning sequence will exhibit undefined behavior, so

the results of measurements are invalid at this point. In order to continue reading valid

measurements, disable the TSI module and reconfigure it.

Workaround: During development make sure to measure the required scanning time for all the electrodes in

your system and configure the scanning time with AMCLKS, AMPSC and SMOD so that an

overrun will not happen. Consider adding about 30 to 70% more time as headroom to make

sure overrun is not triggered. If scanning time is critical and added scan time is not acceptable,

detect the overrun condition either by polling the overrun flag in a loop or through the TSI

interrupt. Once overrun is detected, disable the TSI module, clear all flags and reconfigure.

During reconfiguration, SMOD can be increased by 10% or more of the current value to reduce

the number of overrun occurrences.

e4935: UART: CEA709.1 features not supported

Errata type: Errata

Description: Due to some issues that affect compliance with the specification, the CEA709.1 features of the

UART module are not supported. Normal UART mode, IrDA, and ISO-7816 are unaffected.

Workaround: Do not use the UART in CEA709.1 mode.

e7027: UART: During ISO-7816 T=0 initial character detection invalid initial characters

are stored in the RxFIFO

Errata type: Errata

Description: When performing initial character detection (UART_C7816[INIT] = 1) in ISO-7816 T=0 mode

with UART_C7816[ANACK] cleared, the UART samples incoming traffic looking for a valid

initial character. Instead of discarding any invalid initial characters that are received, the UART

will store them in the receive FIFO.

Workaround: After a valid initial charcter is detected (UART_IS7816[INITD] sets), flush the RxFIFO to

discard any invalid initial characters that might have been received before the valid initial

character.

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 19

e7028: UART: During ISO-7816 initial character detection the parity, framing, and noise

error flags can set

Errata type: Errata

Description: When performing initial character detection (UART_C7816[INIT] = 1) in ISO-7816 mode the

UART should not set error flags for any receive traffic before a valid initial character is

detected, but the UART will still set these error flags if any of the conditions are true.

Workaround: After a valid initial charcter is detected (UART_IS7816[INITD] sets), check the UART_S1[NF,

FE, and PF] flags. If any of them are set, then clear them.

e6472: UART: ETU compensation needed for ISO-7816 wait time (WT) and block wait

time (BWT)

Errata type: Errata

Description: When using the default ISO-7816 values for wait time integer (UARTx_WP7816T0[WI]), guard

time FD multiplier (UARTx_WF7816[GTFD]), and block wait time integer

(UARTx_WP7816T1[BWI]), the calculated values for Wait Time (WT) and Block Wait Time

(BWT) as defined in the Reference Manual will be 1 ETU less than the ISO-7816-3

requirement.

Workaround: To comply with ISO-7816 requirements, compensation for the extra 1 ETU is needed. This

compensation can be achieved by using a timer, such as the low-power timer (LPTMR), to

introduce a 1 ETU delay after the WT or BWT expires.

e4647: UART: Flow control timing issue can result in loss of characters if FIFO is not

enabled

Errata type: Errata

Description: On UART0 and UART1 when /RTS flow control signal is used in receiver request-to-send

mode, the /RTS signal is negated if the number of characters in the Receive FIFO is equal to

or greater than the receive watermark. The /RTS signal will not negate until after the last

character (the one that makes the condition for /RTS negation true) is completely received and

recognized. This creates a delay between the end of the STOP bit and the negation of the /

RTS signal. In some cases this delay can be long enough that a transmitter will start

transmission of another character before it has a chance to recognize the negation of the /RTS

signal (the /CTS input to the transmitter).

Workaround: Always enable the RxFIFO if you are using flow control for UART0 or UART1. The receive

watermark should be set to seven or less. This will ensure that there is space for at least one

more character in the FIFO when /RTS negates. So in this case no data would be lost.

Note that only UART0 and UART1 are affected. The UARTs that do not have the RxFIFO

feature are not affected.

e4945: UART: ISO-7816 T=1 mode receive data format with a single stop bit is not

supported

Errata type: Errata

Mask Set Errata for Mask, Rev 07 AUG 2013

20 Freescale Semiconductor, Inc.

Description: Transmission of ISO-7816 data frames with single stop bit is supported in T=1 mode. Currently

in order to receive a frame, two or more stop bits are required. This means that 11 ETU

reception based on T=1 protocol is not supported. T=0 protocol is unaffected.

Workaround: Do not send T=1, 11 ETU frames to the UART in ISO-7816 mode. Use 12 ETU transmissions

for T=1 protocol instead.

e3892: UART: ISO-7816 automatic initial character detect feature not working correctly

Errata type: Errata

Description: The ISO-7816 automatic initial character detection feature does not work. The direct

convention initial character can be detected correctly, but the inverse convention initial

character will only be detected if the S2[MSBF] and S2[RXINV] bits are set. This defeats the

purpose of the initial character detection and automatic configuration of the S2[MSBF],

S2[RXINV], and C3[TXINV] bits.

Workaround: Use software to manually detect initial characters. Configure the UART with S2[MSBF] and

S2[RXINV] cleared. Then check UART receive characters looking for 0x3B or 0x03. If 0x3B is

received, then the connected card is direct convention. If 0x03 is received, then the connected

card is inverse convention. If an inverse convention card is detected, then software should set

S2[MSBF], S2[RXINV], and C3[TXINV].

e7029: UART: In ISO-7816 T=1 mode, CWT interrupts assert at both character and

block boundaries

Errata type: Errata

Description: When operating in ISO-7816 T=1 mode and switching from transmission to reception block,

the character wait time interrupt flag (UART_IS7816[CWT]) should not be set, only block type

interrupts should be valid. However, the UART can set the CWT flag while switching from

transmit to receive block and at the start of transmit blocks.

Workaround: If a CWT interrupt is detected at a block boundary instead of a character boundary, then the

interrupt flag should be cleared and otherwise ignored.

e7090: UART: In ISO-7816 mode, timer interrupts flags do not clear

Errata type: Errata

Description: In ISO-7816, when any of the timer counter expires, the corresponding interrupt status register

bits gets set. The timer register bits cannot be cleared by software without additional steps,

because the counter expired signal remains asserted internally. Therefore, these bits can be

cleared only after forcing the counters to reload.

Workaround: Follow these steps to clear the UART_IS7816 WT, CWT, or BWT bits:

1. Clear the UART_C7816[ISO_7816E] bit, to temporarily disable ISO-7816 mode.

2. Write 1 to the WT, CWT, or BWT bits that need to be cleared.

3. Set UART_C7816[ISO_7816E] to re-enable ISO-7816 mode.

Note that the timers will start counting again as soon as the ISO_7816E bit is set. To avoid

unwanted timeouts, software might need to wait until new transmit or receive traffic is expected

or desired before re-enabling ISO-7816 mode.

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 21

e7031: UART: In single wire receive mode UART will attempt to transmit if data is

written to UART_D

Errata type: Errata

Description: If transmit data is loaded into the UART_D register while the UART is configured for single wire

receive mode, the UART will attempt to send the data. The data will not be driven on the pin,

but it will be shifted out of the FIFO and the UART_S1[TDRE] bit will set when the character

shifting is complete.

Workaround: Do not queue up characters to transmit while the UART is in receive mode. Always write

UART_C3[TXDIR] = 1 before writing to UART_D in single wire mode.

e5704: UART: TC bit in UARTx_S1 register is set before the last character is sent out in

ISO7816 T=0 mode

Errata type: Errata

Description: When using the UART in ISO-7816 mode, the UARTx_S1[TC] flag sets after a NACK is

received, but before guard time expires.

Workaround: If using the UART in ISO-7816 mode with T=0 and a guard time of 12 ETU, check the

UARTn_S1[TC] bit after each byte is transmitted. If a NACK is detected, then the transmitter

should be reset.

The recommended code sequence is:

UART0_C2 &= ~UART_C2_TE_MASK; //make sure the transmitter is disabled at first

UART0_C3 |= UART_C3_TXDIR_MASK; //set the TX pin as output

UART0_C2 |= UART_C2_TE_MASK; //enable TX

UART0_C2 |= UART_C2_RE_MASK; //enable RX to detect NACK

for(i=0;i<length;i++)

{

while(!(UART0_S1&UART_S1_TDRE_MASK)){}

UART0_D = data[i];

while(!(UART0_S1&UART_S1_TC_MASK)){}//check for NACK

if(UART0_IS7816 & UART_IS7816_TXT_MASK)//check if TXT flag set

{

/* Disable transmit to clear the internal NACK detection counter */

UART0_C2 &= ~UART_C2_TE_MASK;

UART0_IS7816 = UART_IS7816_TXT_MASK;// write one to clear TXT

UART0_C2 |= UART_C2_TE_MASK; // re-enable transmit

}

UART0_C2 &= ~UART_C2_TE_MASK; //disable after transmit

Mask Set Errata for Mask, Rev 07 AUG 2013

22 Freescale Semiconductor, Inc.

e7091: UART: UART_S1[NF] and UART_S1[PE] can set erroneously while

UART_S1[FE] is set

Errata type: Errata

Description: While the UART_S1[FE] framing error flag is set the UART will discard any received data.

Even though the data is discarded, if characters are received that include noise or parity

errors, then the UART_S1[NF] or UART_S1[PE] bits can still set. This can lead to triggering of

unwanted interrupts if the parity or noise error interrupts are enabled and framing error

interrupts are disabled.

Workaround: If a framing error is detected (UART_S1[FE] = 1), then the noise and parity error flags can be

ignored until the FE flag is cleared. Note: the process to clear the FE bit will also clear the NF

and PE bits.

e7092: UART: UART_S1[TC] is not cleared by queuing a preamble or break character

Errata type: Errata

Description: The UART_S1[TC] flag can be cleared by first reading UART_S1 with TC set and then

performing one of the following: writing to UART_D, queuing a preamble, or queuing a break

character. If the TC flag is cleared by queuing a preamble or break character, then the flag will

clear as expected the first time. When TC sets again, the flag can be cleared by any of the

three clearing mechanisms without reading the UART_S1 register first. This can cause a TC

flag occurrence to be missed.

Workaround: If preamble and break characters are never used to clear the TC flag, then no workaround is

required.

If a preamble or break character is used to clear TC, then write UART_D immediately after

queuing the preamble or break character.

e5928: USBOTG: USBx_USBTRC0[USBRESET] bit does not operate as expected in all

cases

Errata type: Errata

Description: The USBx_USBTCR0[USBRESET] bit is not properly synchronized. In some cases using the

bit can cause the USB module to enter an undefined state.

Workaround: Do not use the USBx_USBTCR0[USBRESET] bit. If USB registers need to be written to their

reset states, then write those registers manually instead of using the module reset bit.

e6933: eDMA: Possible misbehavior of a preempted channel when using continuous

link mode

Errata type: Errata

Mask Set Errata for Mask, Rev 07 AUG 2013

Freescale Semiconductor, Inc. 23

Description: When using continuous link mode (DMA_CR[CLM] = 1) with a high priority channel linking to

itself, if the high priority channel preempts a lower priority channel on the cycle before its last

read/write sequence, the counters for the preempted channel (the lower priority channel) are

corrupted. When the preempted channel is restored, it runs past its "done" point instead of

performing a single read/write sequence and retiring.

The preempting channel (the higher priority channel) will execute as expected.

Workaround: Disable continuous link mode (DMA_CR[CLM]=0) if a high priority channel is using minor loop

channel linking to itself and preemption is enabled. The second activation of the preempting

channel will experience the normal startup latency (one read/write sequence + startup) instead

of the shortened latency (startup only) provided by continuous link mode.

Mask Set Errata for Mask, Rev 07 AUG 2013

24 Freescale Semiconductor, Inc.

How to Reach Us:

Home Page:

freescale.com

Web Support:

freescale.com/support

Information in this document is provided solely to enable system and

software implementers to use Freescale products. There are no express

or implied copyright licenses granted hereunder to design or fabricate

any integrated circuits based on the information in this document.

Freescale reserves the right to make changes without further notice to

any products herein. Freescale makes no warranty, representation, or

guarantee regarding the suitability of its products for any particular

purpose, nor does Freescale assume any liability arising out of the

application or use of any product or circuit, and specifically disclaims

any and all liability, including without limitation consequential or

incidental damages. “Typical” parameters that may be provided in

Freescale data sheets and/or specifications can and do vary in different

applications, and actual performance may vary over time. All operating

parameters, including “typicals,” must be validated for each customer

application by customer's technical experts. Freescale does not convey

any license under its patent rights nor the rights of others. Freescale

sells products pursuant to standard terms and conditions of sale, which

can be found at the following address: freescale.com/

SalesTermsandConditions.

Freescale, the Freescale logo, AltiVec, C-5, CodeTest, CodeWarrior,

ColdFire, ColdFire+, C-Ware, Energy Efficient Solutions logo, Kinetis,

mobileGT, PowerQUICC, Processor Expert, QorIQ, Qorivva, StarCore,

Symphony, and VortiQa are trademarks of Freescale Semiconductor,

Inc., Reg. U.S. Pat. & Tm. Off. Airfast, BeeKit, BeeStack, CoreNet,

Flexis, Layerscape, MagniV, MXC, Platform in a Package, QorIQ

Qonverge, QUICC Engine, Ready Play, SafeAssure, SafeAssure logo,

SMARTMOS, Tower, TurboLink, Vybrid, and Xtrinsic are trademarks of

Freescale Semiconductor, Inc. All other product or service names are

the property of their respective owners.