Analyzer for low level debugging of the QSPI Protocol, for use with Saleae and Kingst Logic Analyzers.
- 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.
- Octal IO
- Operation without chip select
- DDR
- 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.
- 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.
Note: Saleae users must also run git submodule update --init --recursive
to download the Saleae Analyzer SDK.
- Open Project in Visual Studio with Administrative rights *1
- Select a configuration that is relative to your software (Logic1, Logic2, or KingstVIS)
- Confirm debugger, and build event paths are correct.
- Hit Play, and your software will launch with a debugger attached.
*1 Build event requires running VS with administrative rights, to copy the DLL to your analyzers folder.
Debugger Path and Post Build Event:
The commands will manually copy the DLL to your analyzers folder, and start your software, before attaching a debugger when you hit Start Debugging or F5.
The following steps are required if any of the following are true
- Your software was not installed to default location
- Your system is 32 bit
- You are using Logic 2 (Logic 2 does not have a default folder for custom analyzers)
- Edit Project
Properties->Debugging->Command
to target your software's executable - Edit Project
Properties->Build Events->Post-Build Event->Command Line
to make sure the copy target is your software's Analyzers folder.
Note: Logic 1 may throw an exception when debugger is auto-attached. If this happens, use Debug->Start without debugging or Ctrl+F5. You may be able to attach the debugger after using Debug->Attach To Process... or Ctrl+Alt+P. Note2: For some reason yesterday I was only able to attach a debugger using Attach To Process, but now today even that isn't working.
- For Windows - simply open
Visual Studio
->Continue Without Code
->File
->Open
->CMake
and select the corresponding CMakeLists.txt from the project folder. Then just select the target configuration(Release or Debug x64) and build it. - For Linux, execute the following in the cloned repository folder
mkdir build && cd build
cmake -G"Unix Makefiles" -DCMAKE_BUILD_TYPE=Release ..
cmake --build .
Then just copy libQSPI_Analyzer.so
to the directory where you'd like to store Saleae plugins.
They are both almost identical, but unfortunately are not compatible.
The only difference I noticed at first glance was the "Analyzers SDK" uses the Analyzer2
class.
- Author : Addio
- Website : www.Addio.io