NXP^® Semiconductors	MSE9S12G240_0N95B
Mask Set Errata	Rev. October 15, 2014

MC9S12G240, Mask 0N95B

Introduction

This errata sheet applies to the following devices:

MC9S12G240, MC9S12G192

MCU Device Mask Set Identification

The mask set is identified by a 5-character code consisting of a version number, a letter, two numerical digits, and a letter, for example 1K79X. All standard devices are marked with a mask set number and a date code.

MCU Device Date Codes

Device markings indicate the week of manufacture and the mask set used. The date is coded as four numerical digits where the first two digits indicate the year and the last two digits indicate the work week. For instance, the date code "0201" indicates the first week of the year 2002.

MCU Device Part Number Prefixes

Some MCU samples and devices are marked with an SC, PC, or XC prefix. An SC prefix denotes special/custom device. A PC prefix indicates a prototype device which has undergone basic testing only. An XC prefix denotes that the device is tested but is not fully characterized or qualified over the full range of normal manufacturing process variations. After full characterization and qualification, devices will be marked with the MC or SC prefix.

Errata System Tracking Numbers

MUCtsXXXXX is the tracking number for device errata. It can be used with the mask set and date code to identify a specific erratum.

Errata Summary

Errata Number	Module affected	Brief Description	Work- around
MUCts04243	sci	SCI: RXEDGIF occurs more times than expected in IR mode	YES
MUCts04258	sci	SCI: RXEDGIF interrupt miss while enter STOP	YES

SCI: RXEDGIF occurs more times than expected in IR mode

MUCts04243

Description

Configured for Infrared Receive mode, the SCI may incorrectly set the 

RXEDGIF bit if there are consecutive '00' data bits. There are two 

cases:    



Case 1: due to re-sync of the RXD input, the received edge may be 

delayed by one bus cycle. If an edge (bit = '0') is detected near 

an SCI clock edge, the next edge (bit = '0') may be detected one 

SCI clock later than expected due to re-sync logic. 



Case 2: if external baud is slower than SCI receiver, the next edge 

may be detected later than expected.



This glitch can be detected by the RXEDGIF circuit, but it does not 

impact the final data result because the SCI receive and data recovery 

logic takes samples at RT8, RT9, and RT10.

Workaround

Case 1 and case 2 may occurs at same time. To avoid those unexpected 

RXEDGIF at IR mode, the external baud should be kept a little bit 

faster than receiver baud by:

                 P > (1/16)/(SBR)

                        or

                 (P)(SBR)(16)> 1



Where SBR is baud of receiver, P is external baud faster ratio. 

For example:

1.- When SBR = 16, P = 0.4%, this means the external baud should be at 

least 0.4% faster than receiver.

2.- When SBR = 4, P = 1.6%, this means the external baud should be at 

least 1.6% faster than receiver.

 

Case 1 will cover case 2, i.e. case 1 is the worst case. If case1 is 

solved, case 2 is also solved.

SCI: RXEDGIF interrupt miss while enter STOP

MUCts04258

Description

If an active edge (falling if RXPOL=0, rising if RXPOL=1) on the RXD

input occurs shortly after the execution of the STOP instruction the

RXEDGIF is not asserted and the CPU is not woken up. The time window in

during which the edge is missed starts about 10 bus cycles after the

STOP instruction and is 2-3 bus cycles wide.

Workaround

(1) If more than one edge with a minimum distance of 4 bus cycles occur,

the 2nd edge will wake up the CPU. This is the case for instance in a

LIN bus system. "The Wake Up Signal consists of a dominant pulse minimum

250 microseconds and maximum 5 milliseconds in length, and it may be

sent by any LIN node."

(2) Use the API to enforce a periodic wake up and check the level of the

RXD input.

(3) Reduce the likelihood of occurrence by increasing the bus frequency.