PXI-based SPI Validation Suite & Service
Soliton’s SPI Validation Suite allows users to verify SPI protocol timings and spec compliance and perform break-the part-validation of the SPI interface for any SPI Slave Device. The suite lets users configure & skew/shmoo bus timing parameters, induce glitches, induce packet formation faults, sweep voltage parameters and measure bus timing parameters. If one wants to use LabVIEW to perform SPI Validation, the suite natively supports that. However, the suite can be accessed as an engine from any programming language using our interface APIs (DLLs).
The suite can be used to generate a timing, syntax, and fault tolerance report for any SPI Slave Device within a matter of minutes, with 3-4 hours of prior remote training from Soliton and supported by overnight Soliton support. Alternatively, customers can also ship 3 DUT boards containing their desired slave device to Soliton Technologies and we will characterize the DUT and send the customer a comprehensive SPI Test Report, within a cycle time of 1 week.
SPI (Serial Peripheral Interface) is a synchronous, 4-wire serial communication protocol. The four signals are
1. Chip Select (CS) [also called Slave Select(SS)]
2. Serial Clock (SCLK)
3. Master Output Slave Input (MOSI)
4. Master Input Slave Output (MISO)
SPI devices communicate with each other using a master-slave architecture. SPI is a single-master, multiple-slave communication protocol. Multiple slaves are supported through individual Chip Select (CS) / Slave Select (SS) lines.
NI PXI Digital Pattern Instrument – PXIe 6570
– SCLK Frequency (Hz)
– SCLK High (ns)
– SCLK Low (ns)
– CS Lead (ns)
– CS Trail (ns)
– CS Idle Start (ns)
– CS Idle End (ns)
– MOSI Setup (ns)
– MOSI Hold (ns)
VIL – LOW-level input voltage
VIH – HIGH-level input voltage
– Send additional clock bit
– Skip a clock bit
– Skip Chip Select(CS) assertion
– Invert the Clock Polarity & Clock Phase
– Send invalid Register Address, invalid Data Byte
tvd;sdo – SDO Valid Time
Since API allows for some variation in how a packet is formed, the software suite accommodates this by allowing the user to define the SPI Read-Write communication pattern in a CSV file. The suite reads the pattern file and replaces the user input like Address/Write Byte and bursts the SPI pattern.
– Write Register (1 byte)
– Read Register (1 byte)
– Write Block (n bytes)
– Read Block (n bytes)
(The software suite allows user to configure SPI pattern file for each of the above communication APIs)
Say, if the pattern has CRC field which must be calculated based on Address & Data field and embedded into each packet, the software suite provides an option to enable this.
Test Plan Editor – Test Plan Editor allows users to create Test Scripts by drag & drop of the Test steps in a sequence, and to configure the test parameters. The SPI Tester comes with all the Test Scripts that are needed for doing SPI compliance tests. If the device contains any special wakeup process, or if the test has to extended beyond the SPI spec, the user can script and then execute the test.
SPI Compliance report – The tool creates a compliance report for each test parameter at the end of script execution
Please fill in the following form and get access to SPI Parametric Validation Suite & Service quotes.
Please fill in the following form and get access to sample SPI Reports.
Please fill in the following form and get access to SPI Parametric Validation Suite Product Sheet.
Please fill in the following form and we shall get in touch with you soon to set up a demo of the requested service/product. Thank you![contact-form-7 404 "Not Found"]
Fill in this form and submit for your download to start automatically
Submit this form and the PRIM Brochure document will be sent to your email.