QSPI Analyzer for Saleae Logic/KingstVIS

---

V1.0.0

Analyzer for low level debugging of the QSPI Protocol, for use with Saleae and Kingst Logic Analyzers.

Features

• Command, Address, Dummy and Data blocks.
• Supports SIO, DIO, and QIO for Command, Address, and data. Dummy is SIO.
• Endianess, CPOL/CPHA, CS Idle State, Extra CS Pre and Post cycles
• All settings simulated.

Images

KingstVIS

Saleae Logic 1

Saleae Logic 2

Saleae Logic 2 Settings

Future Plans

• Octal IO
• Operation without chip select
• DDR

Usage

---

KingstVIS (Windows)

• Download and install Kingst Virtual Instruments Studio
• Place QSpiAnalyzer.dll into your \KingstVIS\Analyzer folder. (Default C:\Program Files\KingstVIS\Analyzer)
• Open KingstVIS and add "QSPI" to Analyzer list
• Set the channels and settings to match your QSPI master device.
• Capture data from Logic Analyzer or press play without device connected, which will simulate data.

Saleae Logic 1 & 2

• Download and install Saleae Logic 1 or Download and install Saleae Logic 2
• Custom Analyzer Install Instructions
• Add "QSPI" to Analyzer list
• Set the channels and settings to match your QSPI master device.
• Capture data from Logic Analyzer or press play without device connected to simulate data.

Building/Debugging

---

Note: Saleae users must also run git submodule update --init --recursive to download the Saleae Analyzer SDK.

Windows

Building

1. Open Project in Visual Studio with Administrative rights *1
2. Select either the "KingstVIS" or "Saleae project" depending on which software you are using.
3. Hit Play, and your software will launch with a debugger attached.

The following steps are "optionally required" if any of the following are true

• Your software was not installed to default location
• Your system is 32 bit
• You are using Saleae Logic 1

1. Edit Project Properties->Debugging->Command to target your software's executable
2. Edit Project Properties->Build Events->Post-Build Event->Command Line to make sure the copy target is your software's Analyzers folder.

*1 Only required to run as admin when your software is installed in a protected folder like Program Files, and if you wish to use post-build event to copy DLL directly to your analyzers folder

Linux/Mac

---

KingstVIS I edited the make files that were included with the SDK to target the source, includes and library. All that should need to be done is the preprocessor definitions.

Saleae CMake build configuration is included.

mkdir build && cd build
cmake ..
make

The library can be found in the build/Analyzers directory

Included Libraries

---

They are both almost identical, but unfortunately are not compatible. The only difference I noticed at first glance was the "Analyzers SDK" has/uses the Analyzer2 class which derives from Analyzer.

• Analyzer SDK (Saleae)
• Custom Protocol Analyzers SDK (Kingst)

License

---

• QSPI Analyzer
• Analyzer SDK

Author

---

• Author : Addio
• Website : www.Addio.io