NXP Semiconductors
UM11227
NTM88 family of tire pressure monitor sensors
UM11227 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2020. All rights reserved.
User manual Rev. 6 — 24 April 2020
3 / 205
Prototype samples may be configured and delivered with the firmware remaining in
the flash memory upon special request. The series production process will erase the
firmware from flash memory to facilitate customers choice of the firmware routines, while
excluding specific firmware routines the application software does not require. Consult
the appropriate NTM88 firmware user guide for a description of the available firmware
routines, either as firmware in flash, or as library releases.
4.2 Electronic encoding - "CodeH"
Consult the appropriate NTM88 product data sheet for a description of the CodeH
traceability which allows users to extract:
• configuration values holding the assembly revision
• final test pressure
• accelerometer calibrations
4.3 Device identification
The bytes assigned to identify the device and its options are described below. This data
can be read using the TPMS_READ_ID routine.
Table 2. Device ID coding summary
BIT
ID Address
Register
Name
7 6 5 4 3 2 1 0
00 CODEF Consult the appropriate NTM88 product data sheet for a description.
01 CODEH Consult the appropriate NTM88 product data sheet for a description.
02 CODE2 ID7 ID6 ID5 ID4 ID3 ID2 ID1 ID0
03 CODE3 ID15 ID14 ID13 ID12 ID11 ID10 ID9 ID8
04 CODE4 ID23 ID22 ID21 ID20 ID19 ID18 ID17 ID16
05 CODE5 ID31 ID30 ID29 ID28 ID27 ID26 ID25 ID24
ID13:0 — Device ID within each assembly lot - 16k devices in each lot
ID26:14 — Lower 13 bits of assembly lot ID - 32k lots
ID27 — 1 to identify NTM88 family
ID28:29 — Upper 2 bits of assembly lot ID
ID30 — 0x1 to identify sub-con B, 0x0 to identify sub-con A
ID31 — 0x1 to identify NXP as device supplier
Note: Prior to erasing the flash memory, users are advised to first copy the contents of
the CODEF through CODE5 data into a secure and retrievable database when using, for
example, a custom gang programmer in lieu of the CodeWarrior IDE tool. The contents
of CODEF through CODE5 are unique to each part number, configuration of pressure
and accelerometer ranges, and serial numbers, and must be replaced as part of the user
flash programming processes.
To Next Page
Loading...
Need help?
General