0% found this document useful (0 votes)
31 views4 pages

Kinetis e 2N22J

Kinetis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
31 views4 pages

Kinetis e 2N22J

Kinetis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Freescale Semiconductor KINETIS_E_2N22J

Mask Set Errata Rev 07 NOV 2013

Mask Set Errata for Mask 2N22J

Introduction
This report applies to mask 2N22J for these products:
• KINETIS_E

Errata ID Errata Title


6946 Core: A debugger write to the I/O port might be corrupted during a processor write
6945 Core: Processor executing at HardFault priority might enter Lockup state if an NMI occurs during a waited
debugger transaction
6749 I2C: The I2C_C1[MST] bit is not automatically cleared when arbitration is lost
7331 IO: High current drive pins not in high-Z state during power up

e6946: Core: A debugger write to the I/O port might be corrupted during a processor
write
Errata type: Errata
Description: A debugger can perform memory accesses through the Cortex-M0+ processor bus matrix
while the processor is running.
Because of this erratum, a debugger write to the I/O port might be corrupted if it occurs while
the processor is executing a write. The processor write completes successfully. However,
under specific timing conditions, the matrix might incorrectly replace the debugger write data
with the value zero.
This erratum does not affect debugger writes outside the I/O port region of the memory map,
or debugger reads.
Conditions:
The following timing-specific conditions must all be met:
 The processor is running (not halted in Debug state).
 The debugger performs a write within the I/O port region of the memory map.
 The processor performs a write.

© 2014 Freescale Semiconductor, Inc.


Implications:
The debugger might corrupt the targeted memory or configure the targeted device incorrectly.

Workaround: The debugger can work around this erratum by halting the processor in Debug state before
performing writes to the I/O port region of the memory map.

e6945: Core: Processor executing at HardFault priority might enter Lockup state if an
NMI occurs during a waited debugger transaction
Errata type: Errata
Description: A debugger can perform memory accesses through the Cortex-M0+ processor bus matrix
while the processor is running.
Because of this erratum, the processor might erroneously enter Lockup state if a debugger-
initiated access on the AHB-Lite master port is subject to wait states while the processor is
running, executing at HardFault priority and taking a Non Maskable Interrupt (NMI). Under very
specific timing conditions, the processor might incorrectly stack a ReturnAddress of
0xFFFFFFFE on NMI entry. On NMI return, the processor unstacks the incorrectly stacked
ReturnAddress and enters Lockup state at HardFault priority.
Conditions:
The following timing-specific conditions must all be met:
 The processor is running (not halted in Debug state) and is executing at HardFault priority.
 The processor executes a single-cycle instruction at a word-aligned address.
 The debugger performs an access through the AHB-Lite master port that is subject to wait
states.
 An NMI becomes pending.
Implications:
The processor stops executing the code in the HardFault handler and enters Lockup state at
HardFault priority as if a fault had occurred.

Workaround: The debugger can work around this erratum by halting the processor in Debug state before
performing accesses outside the Private Peripheral Bus (PPB) region of the memory map.

e6749: I2C: The I2C_C1[MST] bit is not automatically cleared when arbitration is lost
Errata type: Errata
Description: When the I2C module is used as a master device and loses bus arbitration, it correctly
switches to be a slave device. The I2C_C1[MST] bit is not automatically cleared when this
occurs but it does correctly operate as a slave.

Workaround: When the I2C module has been configured as a master device and the I2C_S[ARB] bit is set,
indicating arbitration has been lost, the I2C_C1[MST] bit must be cleared by software before
the I2C_S[ARB] bit is cleared.

Mask Set Errata for Mask 2N22J, Rev 07 NOV 2013


2 Freescale Semiconductor, Inc.
e7331: IO: High current drive pins not in high-Z state during power up
Errata type: Errata
Description: The high current drive pins on the chip are unexpectedly driven low for a short period during
power up. All other I/O pins are high impedance. The issue happens only before VDD reaches
the power-on reset voltage. After power up the normal I/O functions on the high current drive
pins are not impacted.

Workaround: Use one or more combination of the following methods to avoid possible issues:
• Use high current drive pins as current source for LED connection, but keep total IDD <
120mA (refer to device data sheet for IDD)
• Configure the corresponding Flextimer channel output polarity as active high which are
muxed with high current drive pins
• Use high current drive pins with NPN transistor (active high) to drive relays
• Keep VDD ramp-up time greater than or equal to 1KV/s and less than or equal to 10KVs to
disable LED and/or driver action during power up

Mask Set Errata for Mask 2N22J, Rev 07 NOV 2013


Freescale Semiconductor, Inc. 3
How to Reach Us: Information in this document is provided solely to enable system and software
implementers to use Freescale products. There are no express or implied copyright
Home Page:
freescale.com licenses granted hereunder to design or fabricate any integrated circuits based on the

Web Support: information in this document.


freescale.com/support 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, and Kinetis are trademarks of Freescale Semiconductor,
Inc., Reg. U.S. Pat. & Tm. Off. All other product or service names are the property of
their respective owners. ARM and Cortex-M0+ are the registered trademarks of ARM
Limited.
© 2014 Freescale Semiconductor, Inc.

Document Number: KINETIS_E_2N22J


Rev. 07 Nov 2013

You might also like