This document describes how to use the SEN-SPI-BOX kit for NXP automotive sensor
evaluation with the “NXP First Field Verification Tool” software.
The intent of this document is to get started, from the hardware configuration to the
software manipulation, in order to communicate with NXP sensors and get interactive
data.
2.2 Finding kit resources and information on the NXP website
NXP Semiconductors provides online resources for this evaluation board and supported
devices on http://www.nxp.com. The information page for the SEN-SPI-BOX evaluation
board is at http://nxp.com/SEN-SPI-BOX. 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 SEN-SPI-BOX evaluation board, including the downloadable
assets referenced in this document.
3Hardware description
The NXP SEN-SPI-BOX kit provides a full-solution of built-in functionalities to
communicate with any SPI/I²C sensor. The kit graphs real-time data, executes custom
scripts and verifies sensor status. The board is a generic SPI/I²C evaluation board,
compatible with some of the NXP sensor families such as FXLS9xxxx automotive digital
accelerometers. The list of compatible sensors is non-exhaustive and may evolve in the
future.
Figure 3 shows how to couple the SEN-SPI-BOX with a SEN-GEN6-SKT board for the
FXLS9xxxx evaluation.
UM11524
First Field Verification Tool User manual
Figure 3. Attaching the SEN-GEN6-SKT board to the SEN-SPI-BOX
3.1 Kit overview
The kit contains an NXP SEN-SPI-BOX evaluation board, three different cables
compatible with dedicated NXP sensor boards, a microSD card for built-in boot loading
capability, and a USB Type-B cable to connect the kit to a computer.
The kit is powered by an NXP Kinetis® K64F Cortex M4 Microcontroller.
Go to http://www.nxp.com/SEN-SPI-BOX to download the software.
4.1.2 System requirements
The computer system hosting the Sensor FFV Tool software and SEN-SPI-BOX
hardware must meet the following requirements:
• Windows 10 (x86, x64). Although Windows Vista, 7 are anticipated to work as well,
these systems have not been tested and are not supported.
• For each SEN-SPI-BOX, a USB (V3.0) port must be available on the host PC. NXP
anticipates the SEN-SPI-BOX will work with USB V1.1 or V2.0 ports. However, NXP
has not tested the SEN-SPI-BOX with USB V1.1 or V2.0 ports.
• The screen size shall be at least 1024 x 768 pixels. NXP does not recommend using
screens with resolution smaller than 1024 x 768 pixels. Although the software runs on
screens with lower resolution, the GUI and forms are less convenient to use.
• Software to display Adobe PDF documents is required to read the documentation and
the data sheets.
UM11524
First Field Verification Tool User manual
4.1.3 Setup
Double-click the downloaded .msi file and follow the instructions.
Figure 11. NXP Sensor FFV tool setup
NXP recommends using the default installation folder, however the installation location
can be customized.
Figure 16. Select a script in the First Field Verification tool
There are several ways to open projects.
Previously Opened Project: Previously opened projects are listed in “Recent projects”.
Double-click the "recent project" to reopen the project. To learn more, refer to Section 6.
Figure 17. Open an existing project
NXP Compatible sensor without dedicated package file: The user has an NXP
compatible sensor but does not have a dedicated package file. Click the menu bar and
review the existing “Predefined sensor packages”. To learn more, refer to Section 6.
Figure 18. Open a compatible sensor without a dedicated package file
NXP .ffvpkg file: The user has an NXP-provided .ffvpkg file. Click the “Browse” button,
select the file and open it. Alternately, drag and drop the file in “Recent projects” adding
the file to the "recent projects" list. To learn more, refer to Section 6.
Unsupported device or missing package to communicate with the device: The
user has an unsupported device or lacks the necessary package to communicate with
the sensor. In this case, use the “Standard communication protocols”. These protocols
provide basic functions to communicate with SPI, I2C, PSI5, or DSI3 sensors. To learn
more, refer to Section 5.
Figure 19. Open an unsupported device or missing a package
Note: PSI5 and DSI3 protocols necessitate special hardware which is sold separately
from the SEN-SPI-BOX kit. (SEN-PSI5-ADAPTER and SEN-DSI3-ADAPTER).
4.2.2.3 FFV kit search
The software scans all the compatible devices. If this operation fails, ensure that
everything is properly connected and retry.
VCCIO is the logic voltage of the SPI and I²C interfaces. It must be set to a value
compatible with the sensor VCC supply.
4.2.2.4.3 VPP
VPP is the high-voltage supply which could be used in specific cases. It must be carefully
used and may damage the sensor if not used correctly.
5Using standard communication protocols
The SEN-SPI-BOX supports natively SPI and I2C protocols.
To add PSI5 and/or DSI3 automotive protocol interfaces to the SEN-SPI-BOX, adapter
boards may be purchased separately.
5.1 Native protocols
When SPI or I2C protocol is selected from the “Standard communication protocol” block,
it opens as shown in Figure 22.
UM11524
First Field Verification Tool User manual
Figure 22. Example of custom GUI selection for SPI interface
Choose the power supplies as explained Section 4.2.2.4. Select the SEN-SPI-BOX kit
(green button bottom right).
Use the debug cable provided in the kit to connect the sensor with the SEN-SPI-BOX
board.
Click on the "Select" button once erverything is configured. The software opens the
form corresponding to the selected protocol (SPI or I2C) as detailed in Section 5.1.1 and
The SPI menu offers the necessary functions to transfer data. It supports frequencies
up to 10 MHz and the four different SPÏ modes. Transfer width supports 8 to 32 bits data
transfers. There are two selections for Chip Select that correspond to the NXP MDI and
Beagle terminals.
UM11524
First Field Verification Tool User manual
Figure 23. SPI functions for data transfer
Once the configuration set, data can be easily transferred using the “Send” button.
5.1.2 I2C
This I2C interface supports up to 64 byte data transfers.
Configure the 7-bit sensor address and the frequency of the bus (up to 1 MHz).
Figure 24. I2C Interface
5.1.2.1 I2C scanner
The SEN-SPI-BOX is able to scan for I2C sensor addresses. To see all compatible
connected sensors, click the “Scan” button.
Select a register start address and the number of data to read. The result is shown as an
array of 8-bit data.
5.1.2.3 Write
Select a start register and write the value in hexadecimal. Separate multiple values using
a semicolon (;).
5.2 Optional protocols
The selection of DSI3 or PSI5 protocol in the “Standard communication protocol” block
necessitates a special adapter board (SEN-PSI5-ADAPTER or SEN-DSI3-ADAPTER) for
each protocol.
1. Check and set the compatible power supply. Always refer to and set the power
2. Connect the adapter board on the SEN-SPI-BOX using the NXP MDI terminal.
3. Click the Scan button.
4. Select the PSI5/DSI3 transceiver listed.
UM11524
First Field Verification Tool User manual
settings using the value printed on the bottom of the board.Table 3 provides a
summary for convenience.
Table 3. DSI3/PSI5 adapter power settings summary
SEN-DSI3-ADAPTERSEN-PSI5-ADAPTER
VCC, VCCIO5 V3.3 V
VPP13.5 V10.5 V
Components are on the top. Check the connector coding to avoid mistakes.
Figure 25. Transceiver selection
5.2.1 DSI3
Two DSI3 interfaces are available on the SEN-DSI3-ADAPTER board: DSI3 channel 0
and DSI3 channel 1.
To enable or disable the interface for each channel, use the “DSI3 channel enable”
checkbox.
Enabling a channel automatically sends discovery pulses. Every compatible device
present on the bus is assigned a unique physical address.
Figure 26. Enable or disable the DSI3 channel
To exit PDCM mode, the corresponding DSI3 channel must be disabled.
5.2.1.1 Command and response mode (CRM)
By default the transceiver boots in CRM mode. If a sensor is connected to the bus and
owns a physical address, users may be able to send a CRM command.
The sensor manufacturer specifies the commands and the data to send.
UM11524
First Field Verification Tool User manual
Figure 27. CRM settings
5.2.1.2 Periodic data collection mode (PDCM)
Once the sensor is configured using CRM commands, the user must set the DSI3
receiver correctly for PDCM operations.
1. Selected chip time (transceiver chip time must be identical to the chip time of the DSI3
sensor).
2. Associate source ID to timeslot. If a mismatch occurs between the frame source ID
and the slot number, the mismatch raises an error.
3. Choose whether Broad Read Command (BRC) is sent every 500 µs or manually
(when the user clicks the "Update" button.
The user can then switch the DSI3 transceiver to PDCM mode by clicking the “Enter”
button. The transceiver stays in PCDM mode while the bus is powered.
To return to CRM mode, the user must power off, then power on, the associated channel
to return to CRM mode.
PSI5 supports both synchronous (P) and asynchronous (A) modes. Figure 30 provides a
visual summary of the PSI5 operation modes and Table 4 provides details for each field.
Table 4. PSI5 operation mode details
FieldPossible values
Cycling time200 µs to 8360 µs (32 µs step)
Number of slots per cycle1 to 6
UM11524
First Field Verification Tool User manual
Synchronous: PCommunication mode
Asynchronous: A
16-bit: 16Number of data bits
10-bit: 10
CRC: CError detection
Parity: P
Plug the sensor to the Sensor FFV kit. If provided by NXP, use the NXP socket board, or
connect your own board. The pinout is described in Section 3.2.
6.2 Scan for sensor
In the software, press the “Scan” button.
UM11524
Figure 31. Sensor selection page
A list of the compatible sensors appears.
6.3 Configure the sensor
Select the sensor from the list and if available, configure the SPI/I²C settings.
Note: The new configuration is applied only when the "Select" button is activated.
6.3.1 Advanced window for advanced features
To open the advanced windows, right-click any compatible sensor.
Note: This feature should be used with special care and is not synchronized with
standard functions.
This capability means that users can overwrite the sensor register without seeing it in the
other window if it is not updated.
UM11524
First Field Verification Tool User manual
Currently, there are two advanced forms:
• Register table: Quick and easy way to read and modify the sensor memory.
• Scripting: To configure the sensor, automate actions with a command list.
6.3.1.1 Register table
Figure 33 presents the values found in the registers of the sensor.
Figure 33. Register sensor content
The data presented in the sensor table, shown in Figure 33, is not real time and a
mismatch could exist between the value in the table and the actual register value. The
value is displayed in hexadecimal format.
If available, press the wrench icon to change the test settings. Users can skip some tests
by unchecking the test in the list.
UM11524
First Field Verification Tool User manual
Figure 36. Test of an FXLS90422AES inertial sensor
6.5.1.2 Run the test
Once everything is configured, press the “Run” button. Wait while the sequence is being
executed. To view the details of the selected test, click the folder icon.
When complete, export the test results by clicking “Save”. A “.ffvreport” file and a .pdf is
generated. The results are visible later when opening the file.
Close the software.
6.5.1.3 Open a test report
Open a test report file by double-clicking a “.ffvreport” file or by launching the software
and selecting the file from the window browser.
This form is read-only. Re-executing any test from here is not possible.
6.5.1.4 Create a custom test file using C# .Net
Custom test files can be developed using Visual Studio IDE with C# .Net framework.
Special documentation is available from the FFV software by clicking “Create advanced
C# script” from the launcher.
6.5.2 Datalogger file
6.5.2.1 Configure the sensor
UM11524
First Field Verification Tool User manual
Figure 39. Example of configuration interface
The left panel offers many high-level settings the user may access to configure the
sensor. Do not forget to apply the settings before starting any data steam.
This panel may display differently depending on the selected file/sensor.
6.5.2.2 Configure the streaming settings
The streaming panel is split in 3 different sub panels.
6.5.2.2.1 Stream settings
The Stream settings panel allows users to select:
• “Sampling time” between two data (make sure that the communication frequency is
high enough to support the highest rate).
• “Count”: The number of samples to be collected (any non-number value is turned into
infinite).
• “Acquisition time”: Not selectable. It just gives the result of “Count” x “Sampling Time”.
• “Unit in LSB”: Unchecked. Shows the plot with the standard units, else shows in LSB.
• MR <addess(es)> <multiplier> <delay> [options]: Multi read register command, real
time.
– address(es): Can be [@1, @2, @3] or range as [@1 - @3] (up to 1024 bytes).
– multiplier: Repeat the address sequence.
– delay: Time in µs between each command. (up to 100 ms, check the bus speed
– source Id: Can be [1, 2, 3] or range as [1 - 3].
– multiplier: Repeat the source Id sequence.
– delay: Time in µs between each command. (up to 100 ms, check the bus speed
UM11524
First Field Verification Tool User manual
compatibility).
compatibility).
6.5.3.1.3 Generic SPI commands (low level)
• S32 <data> [options]: 32-bit SPI transfer.
• S24 <data> [options]: 24-bit SPI transfer.
• S16 <data> [options]: 16-bit SPI transfer.
• S8 <data> [options]: 8-bit SPI transfer.
6.5.3.1.4 Generic I²C commands (low level)
Not supported yet.
6.5.3.1.5 Other commands (low level)
• SETV <channel> <voltage> [options]: Power supply command (Special care is required
when using this command. Applying an incorrect voltage may damage a sensor.).
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.
7.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.
Suitability for use — NXP Semiconductors products are not designed,
authorized or warranted to be suitable for use in life support, life-critical or
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.
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
UM11524
First Field Verification Tool User manual
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.
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.
7.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.
7Legal information .............................................. 32
Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section 'Legal information'.