NXP provides the enclosed product(s) under the following conditions:
This evaluation kit is intended for use of ENGINEERING DEVELOPMENT OR EVALUATION PURPOSES ONLY. It is provided as a
sample IC pre-soldered to a printed circuit board to make it easier to access inputs, outputs, and supply terminals. This evaluation board
may be used with any development system or other source of I/O signals by simply connecting it to the host MCU or computer board via
off-the-shelf cables. This evaluation board is not a Reference Design and is not intended to represent a final design recommendation for
any particular application. Final device in an application will be heavily dependent on proper printed circuit board layout and heat sinking
design as well as attention to supply filtering, transient suppression, and I/O signal quality.
The goods provided may not be complete in terms of required design, marketing, and or manufacturing related protective considerations,
including product safety measures typically found in the end product incorporating the goods. Due to the open construction of the product,
it is the user's responsibility to take any and all appropriate precautions with regard to electrostatic discharge. In order to minimize risks
associated with the customers applications, adequate design and operating safeguards must be provided by the customer to minimize
inherent or procedural hazards. For any safety concerns, contact NXP sales and technical support services.
Should this evaluation kit not meet the specifications indicated in the kit, it may be returned within 30 days from the date of delivery and will
be replaced by a new kit.
NXP reserves the right to make changes without further notice to any products herein. NXP makes no warranty, representation or
guarantee regarding the suitability of its products for any particular purpose, nor does NXP 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 can and do vary in different applications and actual performance may vary over time. All operating
parameters, including Typical, must be validated for each customer application by customer’s technical experts.
NXP does not convey any license under its patent rights nor the rights of others. NXP products are not designed, intended, or authorized
for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for
any other application in which the failure of the NXP product could create a situation where personal injury or death may occur.
Should the Buyer purchase or use NXP products for any such unintended or unauthorized application, the Buyer shall indemnify and hold
NXP and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and
reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or
unauthorized use, even if such claim alleges NXP was negligent regarding the design or manufacture of the part.
NXP Semiconductors
KITFS26AEEVM evaluation board
1Introduction
This document is the user guide for the KITFS26AEEVM evaluation board.
This document is intended for the engineers involved in the evaluation, design,
implementation, and validation of FS2600 Fail-safe system basis chip with multiple
SMPS and LDO.
The scope of this document is to provide the user with information to evaluate the
FS2600 Fail-safe system basis chip with multiple SMPS and LDO. This document covers
connecting the hardware, installing the software and tools, configuring the environment
and using the kit.
It is delivered with empty OTP content in order to leave the opportunity to the user to
burn the OTP configuration. The board contains a superset device (PFS2630AMDA0AD),
allowing tests on all the FS26 derivatives.
2Finding kit resources and information on the NXP web site
NXP Semiconductors provides online resources for this evaluation board and its
supported device(s) on http://www.nxp.com.
UM11503
The information page for KITFS26AEEVM evaluation board is at http://www.nxp.com/
KITFS26AEEVM. The information page provides overview information, documentation,
software and tools, parametrics, ordering information and a Getting Started tab. The
Getting Started tab provides quick-reference information applicable to using the
KITFS26AEEVM evaluation board, including the downloadable assets referenced in this
document.
2.1 Collaborate in the NXP community
The NXP community is for sharing ideas and tips, ask and answer technical questions,
and receive input on just about any embedded design topic.
The NXP community is at http://community.nxp.com.
3Getting ready
Working with the KITFS26AEEVM requires the kit contents, additional hardware and a
Windows PC workstation with installed software.
3.1 Kit contents
• Assembled and tested evaluation board and preprogrammed FRDM-KL25Z
• 3.0 ft USB-STD A to USB-B-mini cable
• Two connectors, terminal block plug, 2 pos., str. 3.81 mm
• Three connectors, terminal block plug, 3 pos., str. 3.81 mm
• Jumpers mounted on board
microcontroller board in an anti-static bag
3.2 Additional hardware
In addition to the kit contents, the following hardware is necessary or beneficial when
working with this kit.
• Power supply with a range of 8.0 V to 40 V and a current limit set initially to 1.0 A
3.3 Windows PC workstation
This evaluation board requires a Windows PC workstation. Meeting these minimum
specifications should produce great results when working with this evaluation board.
• USB-enabled computer with Windows 7 or Windows 10
3.4 Software
Installing software is necessary to work with this evaluation board.
• NXP GUI installation package
4Getting to know the hardware
The KITFS26AEEVM provides flexibility to play with all the features of the device and
make measurements on the main part of the application. The FRDM-KL25Z connected
to the board, combined with the FS26 NXP GUI software allows full configuration and
control of the FS26 SBC.
UM11503
KITFS26AEEVM evaluation board
4.1 Kit overview
The FS26 family can be evaluated with this board as it is populated with a superset part.
The FS26xx part soldered on the board can be fused one time or it is possible to test as
many configurations as needed in Emulation mode.
This board was designed to sustain up to 2.0 A total on VPRE. Layout is done using sixlayer PCB stack up. Set initial current limitation of 1 A.
4.1.1 KITFS26AEEVM features
• VBAT power supply connectors (Jack and Phoenix)
• VPRE output capability up to 2.0 A
• VBOOST in independent mode or in front-end topology to support battery cranking
profiles
• VCORE up to 1.5 A peak
• LDO1 and LDO2 from 3.3 V or 5.0 V, up to 400 mA
• VTRK1 and VTRK2, from 3.3 V or 5.0 V, up to 125 mA
• VREF 1 % accuracy regulator for external ADC reference
• FS0B, FS1b external safety pins
• USB to SPI protocol for easy connection to software GUI
• LEDs that indicate signal or regulator status
• Manual or Automated OTP fuse programming
• Advance system monitoring via AMUX or external ADC
• Analog variable resistor to test external VMON
4.2 Kit featured components
Figure 2 identifies important components on the board.
Figure 2. Evaluation board featured component locations
4.2.1 FS26: Safety system basis chip with low power and fit for ASIL D
The FS26 is a family of automotive Safety SBC devices with multiple power supplies,
designed to support entry and mid-range safety microcontrollers like the S32K3 series
while maintaining flexibility to fit other microcontrollers targeting automotive electrification
such as power train, chassis, safety and low-end gateway applications.
This family of devices is composed of several versions, pin to pin and software
compatible, to support a wide range of applications, offering choice in number of output
rails, output voltage setting, operating frequency, power up sequencing, and integrated
system level features to address multiple applications with Automotive Safety Integrity
Levels (ASIL) B or D.
It features multiple switch mode regulators as well as LDO voltage regulators to supply
the microcontroller, sensors, peripheral ICs, and communication interface. It offers a
high precision voltage reference available to the system as well as reference voltage for
two independent voltage tracking regulators as well as various functionalities for system
control and diagnostics such as Analog multiplexer, GPIOS and selectable wake up
events from I/O, long duration timer or SPI communication.
The FS26 is developed in compliance with the ISO 26262 standard, and it includes
enhanced safety features, with multiple fail-safe outputs, becoming a full part of a safetyoriented system partitioning, covering both ASIL B and ASIL D safety integrity level, with
the latest on-demand latent fault monitoring.
Operating range
• 40 V DC maximum input voltage
• Handles severe cranking operation (3.2 V battery) thanks to its BOOST controller
• Supports operating voltage range down to battery 6.0 V without BOOST
• Low-power Off mode with very low sleep current (50 µA typ)
• Low-power Standby mode, VPRE active
• LDO1 or LDO2 active selectable via OTP configuration (50 µA typ)
UM11503
KITFS26AEEVM evaluation board
4.2.2 VBAT connectors
There are two ways of supplying the board: either by a Phoenix Connector (J2) or a Jack
connector (J2). The selection of the supplying connector is done using a three-position
switch (SW1).
Figure 3 shows related schematic. Nominal VBAT voltage is 12 V and can support up to
40 V.
Table 1. VBAT Phoenix connector (J1)
Schematic labelSignal nameDescription
J1-1VBATBattery voltage supply input
J1-2GNDGround
Table 2. VBAT three position connector (SW1)
Schematic labelSignal nameDescription
SW1 pin 2-3VBAT PhoenixBoard supplied by Phoenix connector
SW1 pin 2 (middle position)VBATBoard not supplied
SW1 pin 2-1VBAT jackBoard supplied by Jack connector
There are two power topologies available depending on the application and OTP
configuration. The device can be supplied directly by the battery after diode and pi filter;
on the other side, the boost regulator can be connected in front-end topology to support
cold cranking profiles.
It is possible to evaluate both power topologies with this board since external boost
components for each topology are soldered separately as shown in Figure 4.
A set of jumper configurations allows you to select between the two options. See Figure 5
and Table 3. Default jumper configuration is boost in front-end topology.
UM11503
KITFS26AEEVM evaluation board
In front-end topology boost is connected to the battery after reverse diode; the output
of the boost supplies the device during cold cranking profiles. Otherwise, boost stops
switching, and it is bypassed. See FS26 data sheet for more information.
In back-end topology or independent boost, the device is supplied by the battery, and the
boost is supplied by the buck regulator VPRE.
Figure 6 shows a simplified diagram of jumper configuration to associated device pins.
Figure 6. Simplified diagram of jumper configuration for front-end and back-end topologies
When testing the FS26 SBC with a front-end configuration at very low battery level and
loading product at its maximum rating, make sure that the power supply is capable of
providing at least 4.0 A.
Output regulators are accessible through test points or Phoenix connectors in order to
make measurement or plug loads. Male connectors are included on this kit to plug or
unplug wires easily. All output regulators are located at the top edge of the board as
shown in Figure 2.
J23_10VMONEXT_0.8VVMONEXT IC side, for access or disconnect R39 to apply
J23_11FCCU2FCCU2
J23_12AMUXAMUX pin read
J23_13GPIO1_INGPIO1 input side
J23_14VDDIOVDDIO IC side access
J23_15GPIO2_INGPIO2 input side
J23_16VSUPVSUP pin access
J23_17DBG_OTPDBG_OTP power supply (8.0 V) access
J23_18VBATVBAT access
J23_19GNDGND
J23_20GNDGND
UM11503
KITFS26AEEVM evaluation board
0.8 V externally
4.2.6 Indicators
The LED indicators on the board display VBAT regulators, safety outputs, and GPIO
status. For VBAT, regulators and GPIOs there are green LEDs indicating that the output
is powered on. The power supply of these indicators is usually VPRE, and it is controlled
by a low voltage MOSFET by the corresponding signal or regulator.
These regulators can be turned Off manually at any time with the switch SW4 in order to
avoid undesired losses and obtain more accurate current consumption measurements.
LED indicators are turned On and Off when the safety output is released. LEDs can also
be disabled using switch SW5.
The color of the safety output LED indicators is red. When the safety output is asserted,
NXP Semiconductors
aaa-039516
VDDIO
D
4
RED
A
C
R18
1.5
K
D
6
RED
A
C
R20
1.5
K
SW5
SW DIP-4/SM
123
4
876
5
R21
1.5
K
D
5
RED
A
C
R19
1.5
K
D
7
RED
A
C
RST
b
INT
B
FS0
b
FS1
b
aaa-039528
Debug
Through hole test point
s
TEST POINTS
Groun
d
Power
GND
GND
VBA
T
VSU
P
VPI
GND
GND
VDDIO
VBS
T
VBST_PG_OUT
VBOOS
T
GND
GND
VRE
F
VLDO1
FS0
B
VCORE
VLDO2
FS1
B
VPR
E
VTRK1
RST
B
VTRK2
INT
B
AMU
X
VBST_FE_L
S
VBST_BE_L
S
VPRE_SW
VCORE_S
W
VDEBU
G
VMONEXT_0.8
V
VBST_PG
VBO
S
TP7
BH1
MTG
1
TP4
4
TP1
1
TP3
4
TP2
5
TP3
2
BH3
MTG
1
TP3
5
TP3
0
TP2
8
TP2
0
TP1
5
TP4
1
TP1
6
TP3
6
TP2
7
TP4
2
TP1
9
BH2
MTG
1
TP2
2
TP1
8
TP5
TP1
4
TP2
6
TP1
0
BH4
MTG
1
TP4
3
TP1
2
TP2
1
TP8
TP1
7
TP6
TP1
3
TP2
4
TP9
TP2
3
Figure 10. Safety output LED indicators
4.2.7 Test points
The KITFS26AEEVM evaluation board has several test points for easy access and
measurements. The test points are color coded, and can be different part numbers or
without a part number, as shown in Figure 11.
UM11503
KITFS26AEEVM evaluation board
• Orange: test loop access to safety outputs and analog signals
• Red: test loop access for power supplies
• Black: test loop access to GND
• Blue: not a part; through hole small test points on board close to the signal
VDDIO reference can be supplied by 3.3 V or 5.0 V depending on the system. The
supply can be generated on the board, from a voltage regulator, or from an external
source.
11 / 60
NXP Semiconductors
aaa-039529
GNDGN
D
VDDIO
P3V3_KL25
Z
P5V_KL25Z
VCORE
VLDO1
VLDO2
C30
1.0UF
DNP
R36
0
C31
1.0UF
DNP
J22
1
2
3
J12
HDR_2X6
1
2
3
4
6
5
7
8
910
111
2
VDDIO_USB
VDDIO_EXT
VDDIO_USB
aaa-039530
VBA
T
GNDGN
D
GND
GND
WAKE1_I
N
WAKE2_I
N
5.1
K
R
6
R55.1
K
0.01u
F
C15
DNP
0.01u
F
C17
SW2
1
2
SW3
1
2
WAKE2
2
WAKE1
4
7
0.022uF
C14
R86
0.022uF
C16
R35.1
K
5.1
K
R
4
WAKE1
WAKE2
WAKE1_I
N
WAKE2_I
N
J12 allows selection of the supply source, as shown in Table 12.
Table 12. VDDIO connector (J12)
Schematic labelSignal nameDescription
J12_1-2VCOREVDDIO supply is VCORE
J12_3-4 (default)VDDIO_USBVDDIO supply is VDDIO_USB (J22_2)
J12_5-6VDDIO_EXTVDDIO supply is VDDIO_EXT (J23_3)
J12_7-8NCVDDIO Not connected
J12_9-10VLDO1VDDIO supply is VLDO1
J12_11-12VLDO2VDDIO supply is VLDO2
UM11503
KITFS26AEEVM evaluation board
Figure 12. VDDIO source selector headers
4.2.9 Wake input switches
Wake inputs can be exercised by switches SW2 for WAKE1_IN and SW3 for WAKE2_IN.
These interrupts are supplied by the battery to VBAT signal.
Figure 13. WAKE pins control switches
4.2.10 VDEBUG pin voltage control
VDEBUG pin allows FS26 SBC to enter the different operating modes to perform debug
or programming by applying different voltage thresholds or sequences. These thresholds
can be generated on the board and debug pin can be controlled manually or fully
automated by KL25Z.
The selection for manual (default) or automatic is done by J13.
Table 13. Debug control selector (J13)
Schematic labelSignal nameDescription
J13_1-2Manual (default)Debug thresholds are control by SW6 and SW7
J13_2-3Automatic (feature not
enabled)
Debug thresholds are controlled by KL25Z
Different voltage levels and sequences can be used to enter Debug mode; emulate an
OTP configuration, or burn an OTP configuration to the fuses. The threshold levels are:
The power supply to generate the debug entry voltage threshold comes from KL25Z
USB. This means that Freedom board and USB must be plugged in. Burning voltage for
OTP is generated by an onboard boost IC that is also powered by FRDM-KL25Z.
For manual mode, use SW6 to allow connection to 5.0 V power supply, and SW7 to
connect to 8.0 V power supply; when VDBG65TH is reached a blue LED (D19) turns On.
Table 14 shows the possible output voltage level to apply to VDebug pin depending on
SW6 and SW7 positions.
Table 14. SW6 and SW7 VDebug output configuration
SW6SW7VDebug (J13-2) voltage level
OFFOFF0 V
OFFON7.8 V
ONOFF4.5 V
ONON7.8 V
UM11503
KITFS26AEEVM evaluation board
When automatic mode is selected on connector J13 and KL25Z is plugged in and used,
5.0 V and 8.0 V thresholds can be controlled on the NXP GUI by KL25Z signals. It is also
possible to control VBAT by a MCU signal to generate automated sequences for program
and emulations; these signals are:
VBAT_Ctrl: Open or close VBAT power supply
MCU_DBG5V: 5.0 V on VDEBUG pin
MCU_DBG8V: 8.0 V on VDEBUG pin
Debug mode entry
To enter debug mode, follow the sequence:
1. VBAT Off (SW1)
2. VDebug (J13) > VDBG4TH
3. VBAT On (SW1)
4. At this step Debug mode is enabled and you can emulate an OTP configuration or
access the SPI register map. You can read FS_STATES register to verify you are in
Debug mode.
To burn an OTP configuration on the fuses permanently, the following sequence must
be applied. More detailed instructions are provided in Section 8.5 "Program an OTP
configuration".
UM11503
KITFS26AEEVM evaluation board
1. VBAT OFF (SW1)
2. VDebug (J13) > VDBG4TH (SW6 On).
3. VBAT On (SW1)
4. At this step, Debug mode is enabled and you can emulate an OTP configuration or
access the SPI register map. You can read FS_STATES register to verify you are in
Debug mode.
5. VDebug (J13) > VDBG65TH (SW7 On). If the threshold is applied, D19 blue LED
turns On.
6. Load an OTP configuration file and wait until all commands are sent.
7. Put VDebug (J13) to 0 V (first SW7, and then SW6).
8. The device should power up with selected OTP configuration or you can restart the
device power supply to load the burned OTP configuration from fuses.
Figure 15. OTP programming voltage sequence
Figure 16 shows the VDebug voltage sources and its selection.
FS26 VMONEXT monitoring pin can be accessed in different ways. If used, VMONEXT
value should always be 0.8 V. VMONEXT signal can be supplied by any source or
regulator and VMONEXT_0.8V value can be adjusted by using a screwdriver on R37
potentiometer. Default bridge resistor is 22.2 kΩ.
To apply 0.8 V directly to VMONEXT_0.8V, remove R39 and apply 0.8 V to connector
J23_1.
Figure 17. VMONEXT voltage resistor bridge schematic
GPIO1 and GPIO2 FS26 pins are connected by default as outputs, and can be accessed
by J23 connector.
• J23_5 for GPIO1
15 / 60
NXP Semiconductors
aaa-039535
GNDGN
D
GND
GND
GND
GND
GPIO1_I
N
GPIO2_I
N
0.01u
F
C80
0.01u
F
C82
5.1
K
R88
R875.1K
DNP
0.022uF
C79
0.022uF
C81
GPIO1
3
GPIO2
6
R89
5.1KDNP
5.1
K
R86
GPIO1
GPIO2
• J23_7 for GPIO2
To exercise GPIO pins as inputs, R87 and R89 must be populated in order to apply
voltage before RC filter. GPIO input supply can be applied through J23 header.
• GPIO1_IN can be accessed through J23_13; R87 must be populated.
• GPIO2_IN can be accessed through J23_15; R89 must be populated.
Figure 18. GPIO1 and GPIO2 schematics
Note: There are no external pull-ups or pull-downs for the GPIO. If the internal pull-ups
or pull-downs are not enabled by OTP, external PU/PD can be added through J23.
4.3 Schematic, board layout and bill of materials
The schematic, board layout and bill of materials for the KITFS26AEEVM evaluation
board are available at http://www.nxp.com/KITFS26AEEVM.
UM11503
KITFS26AEEVM evaluation board
5Installing and configuring software and tools
5.1 Flashing or updating the GUI firmware
The KITFS26AEEVM is delivered with the GUI firmware flashed. If MCU firmware is
flashed, ignore this section. If it is specified to update the firmware or it is malfunctioning,
follow the instructions in Section 5.1.1 "Flashing Freedom board firmware for Windows 7"
and Section 5.1.2 "Flashing Freedom board firmware from Windows 10".
5.1.1 Flashing Freedom board firmware for Windows 7
Steps 1 and 2 are not required if BOOTLOADER is already loaded in the Freedom board.
1. Press the RST push-button and connect the USB cable into the SDA port on the
Freedom board.
• A new “BOOTLOADER” device should appear on the left pane of the File explorer.
2. Drag and drop the file “MSD-DEBUG-FRDM-KL25Z_Pemicro_v118.SDA” into the
BOOTLOADER drive.
Note: Make sure to allow enough time for the firmware to be saved in the Bootloader.
3. Disconnect and reconnect the USB cable into the SDA port.
• This time without pressing the RST push-button, FRDM_KL25Z device should
appear on the left pane of the File explorer.
4. Locate the file “nxp-gui-fw-frdmkl25z-usb_hid-fs2630_vX.Y.bin” from the package and
drag and drop the file into the FRDM_KL25Z device.
Note: Make sure to allow enough time for the firmware to be saved.
5. Freedom board firmware is successfully loaded. Disconnect and reconnect the USB
cable into the KL25Z USB port.
5.1.2 Flashing Freedom board firmware from Windows 10
1. Disable the storage services: run the services, double-click on the storage service
from the list and press STOP.
UM11503
KITFS26AEEVM evaluation board
Steps 2 and 3 are not required if BOOTLOADER is already loaded in the Freedom
board.
2. Press the RST push-button and connect the USB cable into the SDA port on the
Freedom board.
a. A new “BOOTLOADER” device should appear on the left pane of the File explorer.
3. Drag and drop the file “MSD-DEBUG-FRDM-KL25Z_Pemicro_v118.SDA” into the
BOOTLOADER drive.
Note: Make sure to allow enough time for the firmware to be saved in the
BOOTLOADER.
4. Disconnect and reconnect the USB cable into the SDA port.
• This time without pressing the RST push-button, FRDM_KL25Z device should
appear on the left pane of the File explorer.
5. Locate the file “nxp-gui-fw-frdmkl25z-usb_hid-fs2630_vX.Y.bin” from the package and
drag and drop the file into the FRDM_KL25Z device.
Note: Make sure to allow enough time for the firmware to be saved.
6. Freedom board Firmware is successfully loaded. Disconnect and reconnect the USB
cable into the KL25Z USB port.
To configure the hardware and workstation, complete the following procedure:
1. With SW1 in middle position, set DC power supply to 12 V and current limit to 1.0 A.
Attach the DC power supply positive and negative output to KITFS26AEEVM VBAT
Phoenix connector(J1). Or connect 12 V power supply to VBAT Jack (J2).
Table 15. VBAT Phoenix connector (J1)
Schematic labelSignal nameDescription
J1-1VBATBattery voltage supply input
J1-2GNDGround
Table 16. VBAT three position connector (SW1)
Schematic labelSignal nameDescription
SW1 pin 2-3VBAT PhoenixBoard supplied by Phoenix connector
SW1 pin 2 (middle position)VBATBoard not supplied
SW1 pin 2-1VBAT jackBoard supplied by Jack connector
2. Connect the Windows PC USB port to the KL25Z USB side of the freedom board
included in the kit, using the provided USB 2.0 cable.
Note: At this step, the product is in debug mode and all regulators are turned Off. The
user can then power up with OTP configuration or configure the mirror registers before
power up. Power up is effective as soon as SW6 is turned Off.
7FS26 NXP GUI
Once the kit is ready and the NXP GUI is installed, launch the kit from the Windows
search bar.
Launching FS26_GUI application
1. When the NXP GUI is launched, the Kit Selection window is displayed. Check for the
following settings and then select OK.
UM11503
KITFS26AEEVM evaluation board
2. To avoid the kit selection window on every launch, select the box “Use this
configuration and do not ask again”.
Tab content: Content of each tool or tab; there can be more tabs, boxes, or windows
inside.
7.1.1 Framework settings
The NXP GUI main menu has five GUI elements: File, View, Export, NXP, and Help.
7.1.1.1 File
Load or save a configuration or exit the application. Load and save are only enabled
when OTP tool tab is active.
UM11503
KITFS26AEEVM evaluation board
• Load: Loads an existing configuration file previously exported from OTP tool to
continue to modify it on the OTP tool. This file has a .cfg extension. It is identified as:
FS26_ProgIDASILlevel_CONFIG.cfg.
Example: FS26_A0D_CONFIG.cfg.
• Save: Saves the current configuration of the OTP tool as a .cfg file.
• Use default configuration: Loads default values into the OTP tool.
• Exit: Exits NXP GUI application
7.1.1.2 View
This main menu has options related to GUI display.
• Display
• Show
• Naming Conventions
Display: It consists of Connection Tool Bar (enabled by default) option. To show or hide,go to View → Display, and then select Connection Tool Bar.
Figure 25. Display options
Show: This option can be used to access various sections of the GUI.
Register: Go to View → Naming Conventions → Register. This mode helps to view the
register names as register's technical names throughout the OTP Tool.
Example: VSUP UV threshold → VSUP_UVTH_OTP
7.1.1.3 Export
This option allows user to export the current OTP from the OTP tool into different script
formats.
• OTP: Exports OTP configuration into OTP script file for programming.
• TBB: Exports OTP configuration into a TBB script file for emulation
• I-HEX: Exports to Intel Hex script file
• S-HEX: Exports to Simple Hex script file
UM11503
KITFS26AEEVM evaluation board
Figure 29. Export options
This option is enabled only in OTP Tool and remains disabled in other sections of the
GUI.
7.2 Device manager
The device manager allows start/stop of communication with device as well as enter/exit
of the test mode; it also allows quick access to execute useful system scripts.
Figure 30. Device manager
7.2.1 Device connection
If USB is detected from USB and device status bar, the USB status changes from NOT
DETECTED to DISCONNECTED. Start button is enabled.
Click Start to initiate communication with FS26 device.
When connected successfully, FS26 color changes to green and other buttons are
enabled. USB status changes to CONNECTED.
Apply test mode to send Main and Fail-safe Test mode entry keys. If test mode is entered
correctly, button changes to “Exit test mode”.
When test mode is entered, options requiring test mode are enabled, such as Mirrors and
device programming.
UM11503
KITFS26AEEVM evaluation board
Click Polling to do a continuous check of test mode entry.
If the device versioning bits are already programmed with an existing part number, the
NXP GUI decodes and displays the assigned Device ID. The following example displays
FS2633D.
7.2.2 Script shortcuts
To find a section with system script shortcuts, select the script and click execute. This
does not warrant the entry or acknowledge of the device. Device must be in INIT FS
state in most cases.
7.3 Access
7.3.1 Register map
The register access tab allows read/write to the FS26 Main and Fail-safe register maps
and is divided into following sections:
• Functional: Main functional SPI registers (diagnostics, configuration, and controls)
• Safety: Safety SPI registers (diagnostics and configuration)
• Write_INIT_Safety: Safety registers that can be configured during INIT FS state (for
example, WD configuration and WD window).
UM11503
KITFS26AEEVM evaluation board
There are three types of registers: read only (only read button), write only (only write
button) or read/write (read and write buttons).
7.3.1.1 Register read only
To read the values of a register, click READ; the value is read from the device and
displayed on label near READ button, and is displayed on the log window.
Figure 31. Read only register
To view the values of all the bits from a register after read operation, click Edit button.
Bits are read with their corresponding values displayed as a pop-up window.
Figure 32. Register read with values and description
7.3.1.2 Register read/write
To read or write the bit values individually, click each bit button; the value is read from the
bit or written to the bit based on its properties and displayed on the log window and in the
label near READ and text box near WRITE button correspondingly. The bit button color
changes accordingly.
7.3.1.3 Global read/write
UM11503
KITFS26AEEVM evaluation board
The global read/write and reset option is located at the bottom left section of the register
tab.
The SELECT ALL option selects all the registers on the tab.
Figure 33. Global read/write
WRITE: Writes data to all selected registers at once
READ: Reads data back from the selected register at once
RESET: Resets all the input textbox to 0x00. Write bits are set to 0 and change register
Configure reaction of safety outputs for VMON, FCCU, ERRMON, and configure Fault
Monitor. It is required to be in INIT FS to configure registers. Click Read All to get current
configuration, then modify it.
Click the combo box controls to select configuration, then click Write.
Click Read or Read All to get configuration; read values appear to the right of controls.
UM11503
KITFS26AEEVM evaluation board
Figure 34. INIT Safety
To get current state, click FS_STATES display from USB and Device status bar on the
bottom.
7.3.3 FS Config
This tab helps to configure safety features such as Watchdog and fault error counter.
Enable or disable FS26 regulators. Check enable or disable box, then click Write button.
These registers do not provide regulator status; it writes ‘1’ to apply the command then
restart to 0. Write ‘0’ has no effect. VPRE can be only enabled or disabled in test mode.
This tab can be accessed from Toolbar → REG ACCESS or View → Show → Registry
Map → AMUX Registers.
This tab allows selection of AMUX pin channel and gets its current value by using KL25Z
AMUX ADC pin. The voltage or temperature graph can do a single read or dynamically
display various channels.
The displayed values apply to the divider and temperature formulas.
To use the dynamic graph, select the channel then click + button to add to the graph and
then start polling with Poll button.
Click Poll again to stop measurements.
7.4 Script editor
The script editor allows you to create or send existing sequences to the device. You can
read/write individually to a register, to an I/O, or to an analog pin. You can emulate an
OTP configuration as well with this tab.
This tab can be accessed from Toolbar → SCRIPT or View → Show → Script Editor.
Figure 38. Script editor
The script can be written by selecting and configuring the pins and registers that are
available on the script commands section, or by loading a previously exported .txt file.
To write to a bit group, modify the controls of each register, then click Write.
UM11503
KITFS26AEEVM evaluation board
Figure 42. Write bit group
7.5.2 Read/write all and write all operation
Read All reads the bits of each block from all mirror registers.
Read values appear at the right of each register as well on the window log.
Figure 43. Read All
To write all OTP bit groups configuration, click Write All.
7.5.3 Mirror registers export option
This operation generates a configuration file and this file is saved as a text file in local
device which can be imported later into this tab. Figure 44 shows the generated .txt
configuration file.
This option is used to import the configuration file previously saved. Click OTP Import
and select the the.txt configuration file previously saved from this tab.
Figure 45. OTP Import for reference
7.6 INT
This option allows access to monitor the regulators and safety events. To access the
Interrupt Editor window, click Menu → INT or View → Show → Interrupt Editor.
It is separated in two tabs: Interrupt Configuration and Safety Diagnostic.
The below legend and functions apply to both tabs:
• Blue means Low or not activated
• Yellow means High or activated.
• To clear flags, click each check box from clear column or click Clear All.
• To mask the interruption, check the box of each interruption from mask column.
• Click Read on each box to read the current status or Read all to update the whole tab.
• Use Poll button to read each box periodically.
Sense status can be read only.
7.6.1 Interrupt Configuration
This tab allows the user to monitor the regulators, Wake inputs, I/O and communication
events or status. It allows read, write and poll over/under voltage, over temperature and
over current of device. You can read, clear or mask an interruption.
If an event occurs flag changes to red. When regulators are red or ‘1’ they are turned ON.
Safety Diagnostics tab allows the monitoring of safety events such as VMON status, bad
WD, SPI communication errors, FCCU pins, safety outputs, ABIST1 and ABIST2 status.
Figure 48. Safety diagnostics tab
ABIST1_PASS Yellow means that it is done and PASS, since we can read ‘1’ from its
register. 0 or blue after execution means fail.
7.7 Device programming
This section is used to burn permanently an OTP configuration on the OTP fuses. To
enable this window device must be in test mode.
To program an OTP configuration Vdebug pin must be higher than VDBG65TH. To apply
this voltage, turn on SW7 (Apply 8.0 V to Vdebug).
Click on Browse to select an OTP script file, then click on program button to run the
script. If Vdebug not set to 8.0 V, a pop-up appears asking to turn on SW7, or it turns On
automatically if jumper J13 is on Automatic mode J13 3-2.
UM11503
KITFS26AEEVM evaluation board
If the required conditions are met (sectors available), the programming starts. Otherwise
the execution is cancelled. To verify sectors are available, click Read from Fuse Box
Status.
OTP is programmed into SECTBE2 of Main and Fail-safe. SECTBE1 and SECTBE0 are
reserved for NXP users only.
Blue or ‘0’: Available
Yellow or ‘1’: Not available
When programming is complete, a pop-up appears to request to turn Off SW7 and SW6
(set Vdebug to 0 V).
If the device was programmed correctly the power-up sequence starts. Fuse box status
can be read to verify if sectors are burned. In some conditions a power up could be
required.
7.8 OTP tool
This option allows user to configure OTP registers, save configurations, and generate
scripts in different file formats which can be burnt (OTP script) or emulated (TBB script)
into the FS26 SBC. See Section 7.1.1.3 "Export".
To access the FS26 OTP tool, launch NXP GUI application and navigate to OTP. To
access OTP Tool from menu, go to View → Show/Hide → OTP Tool.
It is possible to save a configuration to visualize or modify it later. Click Save Config to
export or go to File and then select Save. To import, click Import or go to File and then
select Load.
7.8.1 OTP tool application
All blocks in the OTP tool use default values configured on launch. It consists of the
following configuration sections:
This block consists of the parameter (bits) settings that are related to the system
configuration registers of FS26. It displays block diagram with the selected regulators
output values from Regulators section. It contains the power up sequence configuration
which is displayed in the sequence diagram. You can configure the I/O and wake inputs
as well.
The switching regulators can configure VPRE, VBST and VCORE output values and its
internal parameters. Select the Power topology by configuring the VBST_CFG_OTP bit
group.
Figure 53. VBST configuration
The Regulators tab consists of VLDO1, VLDO2, VTRK1, VTRK2, VREF output values
and its TSD behavior.
7.8.2.3 System Safety Configuration
This tab allows user to configure ABIST1 for each regulator, configure system reaction in
case of Fault or enable and disable Watchdog timer.
This tab allows user to configure FS26 voltage monitoring and consists of the following:
UM11503
KITFS26AEEVM evaluation board
• VMONPRE configuration
• VMONLDO1 configuration
• VMONCORE configuration
• VMONLDO2 configuration
• VMONEXT configuration
• VMONREF configuration
Make sure that each VMON is assigned with the same voltage output value configured
on Regulators tab, then select its fault OV/UV threshold and filtering time.
Figure 55. Voltage Monitoring
7.8.2.5 OTP ID
Displays OTP ID. Only NXP users can create a new OTP ID.
This section can control some I/Os connected to the KL25Z plugged-in Freedom. It can
read the device safety outputs externally or control different voltage sources in order to
apply sequences to apply debug mode without moving any switches.
The input pins are the pins that can be read from the MCU; they are input pins from MCU
point of view. This section contains the safety outputs FS0B, FS1B and RSTB. It can be
read once with Read button, or you can select at which frequency you want to the read
the pins. Select the duration then start polling with Poll button.
UM11503
KITFS26AEEVM evaluation board
Figure 57. I/O pins
The output pins are thresholds that can be controlled with MCU. These pins are
described in Section 4.2.10 "VDEBUG pin voltage control"
VBAT_Ctrl: Open or close VBAT power supply
MCU_DBG5V: 5 V on VDebug pin
MCU_DBG8V: 8 V on VDebug pin
They can be used instead of the Manual switches SW6 and SW7. In order to use
MCU_DBG5V and MCU_DBG8V for debug pin control, J13 must be on ‘’Auto mode’’ J13
position 3-2. Select high or low to control the pins, default is low.
To use VBAT_Ctrl the red jumper JP1 next to the VBAT switch must be OFF. Once JP1 is
removed, use VBAT_Ctrl instead of SW1 to turn the power supply on or off.
These pins are also accessible from script editor and be used to create script sequences.
8Using FS26 NXP GUI
UM11503
KITFS26AEEVM evaluation board
Once the NXP GUI (Section 5.2 "Installing GUI software package") is installed, follow
these instructions for a quick power up, debug, programming, or entering the different
operating modes of the FS26 SBC.
8.1 Power up
If the FS26 device contains an OTP configuration, connect a power supply to the VBAT
Phoenix connector or the VBAT jack connector. See Section 4.2.2 "VBAT connectors".
It is recommended to set the power supply to an initial value of 12 V and limit current to
1.0 A.
Make sure the board has the correct jumper configuration. Every kit is delivered with a
default configuration shown in the following figure. This configuration is enabled for a
boost in front-end topology.
Verify that the KL25Z Freedom is plugged in, as well as the USB cable on KL25Z USB
connector side. It is important that the USB cable is connected since in addition to
enabling the communication with the NXP GUI, it provides voltages and references to
some circuits on board as well as generates the VDDIO reference for the IC.
Since all the previous statements are valid or considered, switch SW1 can be used to
power on the board.
If the OTP configuration has many safety features enabled, the device may restart or
power Off after a few seconds. To prevent this, enter debug mode to waive some of those
features.
To modify any parameters or to communicate with the IC, enter debug mode. Refer to the
power and connection statements from Section 8.1 "Power up".
Once the kit is ready, follow the next steps:
1. Make sure the device is powered Off (SW1 middle position).
2. Turn On SW6 to apply 5.0 V to the VDebug pin. Make sure the jumper of J13 has
the right configuration, default is Manual. See Section 4.2.10 "VDEBUG pin voltage
control" for more details.
UM11503
KITFS26AEEVM evaluation board
3. Power on VBAT, and the device enters debug mode, this allows access to the register
map, to emulate or to program an OTP configuration on the NXP GUI.
4. To verify debug mode, use the NXP GUI Register map window to Read
FS_STATES(0x17) or click on FS_STATES display from USB and device status bar.
It is possible to start power up sequence and stay in debug mode. In order to start power
up sequence, turn SW6 to put VDebug pin to 0 V.
8.3 Test mode entry
To enter test mode, the device must be in Debug mode. Test mode can be accessed by
writing the appropriate key sequences.
Access test mode from NXP GUI device manager or write the keys to the script editor.
From Device Manager: Click Apply test mode to send the Main and Failsafe test mode
entry keys.
2. Turn On the SW6 to apply ~4.5 V to the VDebug pin. Make sure that the jumper
of J13 has the right configuration; default is Manual. See Section 4.2.2 "VBAT
connectors" for more details.
3. Power On VBAT(SW1), and the device enters debug mode.
If already in debug entry:
UM11503
KITFS26AEEVM evaluation board
1. Open the NXP GUI, connect the device, and open the script editor.
2. Open the provided or created OTP configuration script (TBB) to load into the mirror
registers.
3. Click Run Script.
A TBB script contains usually Test mode entry keys; if it does not have it, see Section 8.3
"Test mode entry" to enter test mode.
After running the script, read the mirror registers to verify the loaded OTP configuration
in the OTP Mirrors tab. Turn the VDebug (SW6) switch to 0 V to start the power up
sequence.
8.5 Program an OTP configuration
This section is intended to burn an OTP configuration permanently into the fuses. The
device sectors can be programmed only one time. Make sure that sectors are available.
You can program an OTP configuration from Device Programming tab or from the script
editor. See Section 7.7 "Device programming".
1. If not in debug mode, see Section 8.2 "Debug mode entry".
2. Turn SW7 On to apply ~8 V to the VDebug pin in order to reach the OTP burning
threshold VDBG65TH. A blue LED (D19) indicates if this voltage is turned on
Burning voltage LED indicator (D19):
UM11503
KITFS26AEEVM evaluation board
3. Open the NXP GUI, connect the device, and go to the script editor.
4. Open the provided or created OTP configuration script to load on the mirror registers.
Then click Run to run the script.
5. Once the script has been sent, turn Off SW7, then SW6.
6. Device should power up with the burned OTP configuration or perform a POR on
VBAT to verify the fused OTP configuration.
8.6 Go to INIT FS
From power up:
UM11503
KITFS26AEEVM evaluation board
1. Put Debug pin to 5.0 V (SW6 On) to access debug entry.
2. Device powers up (SW1).
3. If the device does not have an OTP configuration emulate or program an OTP
configuration. See Section 8.4 "Emulate an OTP configuration" for emulation or
Section 8.5 "Program an OTP configuration" for programming.
4. Turn Off SW6 to continue the state machine and access INIT FS. You can verify
current state from USB and device status bar, then click display to refresh.
8.7 Go to INIT FS in debug mode
From power up:
1. Put Debug pin to 5.0 V (SW6 On) to access debug entry.
2. Device power up (SW1)
3. If the device does not have an OTP configuration emulate or program an OTP
configuration. See Section 8.4 "Emulate an OTP configuration" for emulation or
Section 8.5 "Program an OTP configuration" for programming.
4. Turn Off SW6 to continue the state machine and access INIT FS. Verify current state
from USB and device status bar, and click display to refresh.
8.8 Go to Normal mode
To enter Normal mode from GUI, you must be in debug mode and in INIT FS state. If
simple Watchdog, use a script to release safety outputs FS0B and FS1B. If Watchdog
challenger, sequence must be sent manually.
1. Once in INIT FS, Verify ABIST1 passes from Safety diagnostics tab.
2. Configure or verify Watchdog type from Mirrors tab.
3. Use a script to release safety outputs; use script A for watchdog simple or script B for
watchdog challenger. Script to release safety outputs is available in device manager
scripts section, rr from script editor → Generator → Safety outputs release script and
run.
a. Sequence to enter normal mode with a Watchdog simple
b. Sequence to enter normal mode with a Watchdog Challenger
UM11503
KITFS26AEEVM evaluation board
//INIT FS and simple WD enabled required
//Open WD window
SET_REG:FS26:Safety:FS_WDW_DURATION:0x008B
SET_REG:FS26:Safety:FS_NOT_WDW_DURATION:0xF144
//Send 1 good wd refresh to close INIT window
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5AB2
//clean fault error counter
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5AB2
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5AB2
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5AB2
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5AB2
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5AB2
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5AB2
//Exit dbg mode
SET_REG:FS26:Safety:FS_STATES:0x4000
//release FS0B and FS1B
SET_REG:FS26:Safety:FS_RELEASE_FS0B_FS1B:0xB2A5
//INIT FS and WD Challenger required
//Open WD window
SET_REG:FS26:Safety:FS_WDW_DURATION:0x008B
SET_REG:FS26:Safety:FS_NOT_WDW_DURATION:0xF144
//Send 1 ZD refresh to close INIT window
SET_REG:FS26:Safety:FS_WD_ANSWER:0xa54d
//clean fault error counter
SET_REG:FS26:Safety:FS_WD_ANSWER:0x4a9a
SET_REG:FS26:Safety:FS_WD_ANSWER:0x9535
SET_REG:FS26:Safety:FS_WD_ANSWER:0x2a6a
SET_REG:FS26:Safety:FS_WD_ANSWER:0x54d4
SET_REG:FS26:Safety:FS_WD_ANSWER:0xa9a9
SET_REG:FS26:Safety:FS_WD_ANSWER:0x5353
//Exit dbg mode
SET_REG:FS26:Safety:FS_STATES:0x4000
//release FS0B and FS1B
SET_REG:FS26:Safety:FS_RELEASE_FS0B_FS1B:0xA565
Release safety outputs without script
To release safety outputs step by step, continue with these instructions:
1. Configure WD window. Since it is not possible to send a WD refresh periodically,
Open WD Window. From FS config tab, go to WD window box, select INFINITE
window, and then click Write.
Or from device manager select Open WD Window script, and then click execute.
2. Send one good WD refresh to move on the state machine. From FS Config tab, click
WD challenger or WD simple one time.
UM11503
KITFS26AEEVM evaluation board
Or execute it from script editor or device manager.
3. Send the number selected good WD refresh to clean the Fault error counter. Example:
default number is 6. Click six times on WD Challenger or WD simple button. Verify
that the Fault error count is now 0 (FLT_ERR_CNT) in FS config tab.
4. Exit debug mode. Write 1 to exit debug mode bit in FS_STATES. Go to register map,
then to safety tab.
5. Send “FS0b release” or “FS0b and FS1b release” command to move to normal mode.
You can find these buttons in FS config tab.
6. After these steps, device should move to Normal mode. To verify current state, click
FS states display from USB and device status bar.
8.9 Low power mode
Once in INIT FS or Normal mode, select a way to exit the low power modes. Write 1 to
the event or events that can wake the product from the low power modes.
8.9.1 Go to standby
Execute Go to Standby script from device manager.
UM11503
KITFS26AEEVM evaluation board
Or from Script editor → Generator, select Go to Standby script and run it.
Device should go to standby mode. Only VPRE stays turn On and LDOs as configured.
8.9.2 Go to LPOFF
Once in INIT FS or Normal mode, execute Go to LPOFF script from device manager. Or
from Script editor → Generator, select Go to LPOFF script and run it.
Device should go to LPOFF mode. Only VPRE stays turned On.
Draft — A draft status on a document indicates that the content is still
under internal review and subject to formal approval, which may result
in modifications or additions. NXP Semiconductors does not give any
representations or warranties as to the accuracy or completeness of
information included in a draft version of a document and shall have no
liability for the consequences of use of such information.
10.2 Disclaimers
Limited warranty and liability — Information in this document is believed
to be accurate and reliable. However, NXP Semiconductors does not
give any representations or warranties, expressed or implied, as to the
accuracy or completeness of such information and shall have no liability
for the consequences of use of such information. NXP Semiconductors
takes no responsibility for the content in this document if provided by an
information source outside of NXP Semiconductors. In no event shall NXP
Semiconductors be liable for any indirect, incidental, punitive, special or
consequential damages (including - without limitation - lost profits, lost
savings, business interruption, costs related to the removal or replacement
of any products or rework charges) whether or not such damages are based
on tort (including negligence), warranty, breach of contract or any other
legal theory. Notwithstanding any damages that customer might incur for
any reason whatsoever, NXP Semiconductors’ aggregate and cumulative
liability towards customer for the products described herein shall be limited
in accordance with the Terms and conditions of commercial sale of NXP
Semiconductors.
Right to make changes — NXP Semiconductors reserves the right to
make changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior
to the publication hereof.
Applications — Applications that are described herein for any of these
products are for illustrative purposes only. NXP Semiconductors makes
no representation or warranty that such applications will be suitable
for the specified use without further testing or modification. Customers
are responsible for the design and operation of their applications and
products using NXP Semiconductors products, and NXP Semiconductors
accepts no liability for any assistance with applications or customer product
design. It is customer’s sole responsibility to determine whether the NXP
Semiconductors product is suitable and fit for the customer’s applications
and products planned, as well as for the planned application and use of
customer’s third party customer(s). Customers should provide appropriate
design and operating safeguards to minimize the risks associated with
their applications and products. NXP Semiconductors does not accept any
liability related to any default, damage, costs or problem which is based
on any weakness or default in the customer’s applications or products, or
the application or use by customer’s third party customer(s). Customer is
responsible for doing all necessary testing for the customer’s applications
and products using NXP Semiconductors products in order to avoid a
default of the applications and the products or of the application or use by
customer’s third party customer(s). NXP does not accept any liability in this
respect.
Suitability for use in automotive applications — This NXP
Semiconductors product has been qualified for use in automotive
applications. Unless otherwise agreed in writing, the product is not designed,
authorized or warranted to be suitable for use in life support, life-critical or
UM11503
KITFS26AEEVM evaluation board
safety-critical systems or equipment, nor in applications where failure or
malfunction of an NXP Semiconductors product can reasonably be expected
to result in personal injury, death or severe property or environmental
damage. NXP Semiconductors and its suppliers accept no liability for
inclusion and/or use of NXP Semiconductors products in such equipment or
applications and therefore such inclusion and/or use is at the customer's own
risk.
Export control — This document as well as the item(s) described herein
may be subject to export control regulations. Export might require a prior
authorization from competent authorities.
Evaluation products — This product is provided on an “as is” and “with all
faults” basis for evaluation purposes only. NXP Semiconductors, its affiliates
and their suppliers expressly disclaim all warranties, whether express,
implied or statutory, including but not limited to the implied warranties of
non-infringement, merchantability and fitness for a particular purpose. The
entire risk as to the quality, or arising out of the use or performance, of this
product remains with customer. In no event shall NXP Semiconductors, its
affiliates or their suppliers be liable to customer for any special, indirect,
consequential, punitive or incidental damages (including without limitation
damages for loss of business, business interruption, loss of use, loss of
data or information, and the like) arising out the use of or inability to use
the product, whether or not based on tort (including negligence), strict
liability, breach of contract, breach of warranty or any other theory, even if
advised of the possibility of such damages. Notwithstanding any damages
that customer might incur for any reason whatsoever (including without
limitation, all damages referenced above and all direct or general damages),
the entire liability of NXP Semiconductors, its affiliates and their suppliers
and customer’s exclusive remedy for all of the foregoing shall be limited to
actual damages incurred by customer based on reasonable reliance up to
the greater of the amount actually paid by customer for the product or five
dollars (US$5.00). The foregoing limitations, exclusions and disclaimers shall
apply to the maximum extent permitted by applicable law, even if any remedy
fails of its essential purpose.
Translations — A non-English (translated) version of a document is for
reference only. The English version shall prevail in case of any discrepancy
between the translated and English versions.
Security — Customer understands that all NXP products may be subject
to unidentified or documented vulnerabilities. Customer is responsible
for the design and operation of its applications and products throughout
their lifecycles to reduce the effect of these vulnerabilities on customer’s
applications and products. Customer’s responsibility also extends to other
open and/or proprietary technologies supported by NXP products for use
in customer’s applications. NXP accepts no liability for any vulnerability.
Customer should regularly check security updates from NXP and follow up
appropriately. Customer shall select products with security features that best
meet rules, regulations, and standards of the intended application and make
the ultimate design decisions regarding its products and is solely responsible
for compliance with all legal, regulatory, and security related requirements
concerning its products, regardless of any information or support that may
be provided by NXP. NXP has a Product Security Incident Response Team
(PSIRT) (reachable at PSIRT@nxp.com) that manages the investigation,
reporting, and solution release to security vulnerabilities of NXP products.
10.3 Trademarks
Notice: All referenced brands, product names, service names and
trademarks are the property of their respective owners.
NXP — wordmark and logo are trademarks of NXP B.V.
8.4Emulate an OTP configuration ........................ 50
8.5Program an OTP configuration ........................ 51
8.6Go to INIT FS ..................................................53
8.7Go to INIT FS in debug mode ......................... 53
8.8Go to Normal mode ......................................... 53
8.9Low power mode ............................................. 56
8.9.1Go to standby .................................................. 56
8.9.2Go to LPOFF ................................................... 56
9Revision history ................................................ 57
10Legal information .............................................. 58
Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section 'Legal information'.