Saleae Serial Peripheral Interface (SPI) Analyzer

Saleae Serial Peripheral Interface (SPI) Analyzer

Getting Started

The following documentation describes how to build this analyzer locally. For more detailed information about the Analyzer SDK, debugging, CI builds, and more, check out the readme in the Sample Analyzer repository.

https://github.com/saleae/SampleAnalyzer

MacOS

Dependencies:

• XCode with command line tools
• CMake 3.13+
• git

Install command line tools after XCode is installed:

xcode-select --install

Then open XCode, open Preferences from the main menu, go to locations, and select the only option under 'Command line tools'.

Install CMake on MacOS:

1. Download the binary distribution for MacOS, cmake-*-Darwin-x86_64.dmg
2. Install the usual way by dragging into applications.
3. Open a terminal and run the following:

/Applications/CMake.app/Contents/bin/cmake-gui --install

Note: Errors may occur if older versions of CMake are installed.

Build the analyzer:

mkdir build
cd build
cmake ..
cmake --build .

Ubuntu 18.04+

Dependencies:

• CMake 3.13+
• gcc 4.8+
• git

Misc dependencies:

sudo apt-get install build-essential

Build the analyzer:

mkdir build
cd build
cmake ..
cmake --build .

Windows

Dependencies:

• Visual Studio 2019
• CMake 3.13+
• git

Visual Studio 2019

Note - newer and older versions of Visual Studio are likely to work.

Setup options:

• Workloads > Desktop & Mobile > "Desktop development with C++"

Note - if CMake has any problems with the MSVC compiler, it's likely a component is missing.

CMake

Download and install the latest CMake release here. https://cmake.org/download/

git

Download and install git here. https://git-scm.com/

Build the analyzer:

mkdir build
cd build
cmake .. -A x64

Then, open the newly created solution file located here: build\spi_analyzer.sln

Optionally, build from the command line without opening Visual Studio:

cmake --build .

The built analyzer DLLs will be located here:

build\Analyzers\Debug

build\Analyzers\Release

For debug and release builds, respectively.

Output Frame Format

Frame Type: "enable"

Property	Type	Description

Indicates the enable (chip select) signal has transitioned from inactive to active, present when the enable channel is used

Frame Type: "disable"

Property	Type	Description

Indicates the enable signal has transitioned back to inactive, present when the enable channel is used

Frame Type: "result"

Property	Type	Description
miso	bytes	Master in slave out, width in bits is determined by settings
mosi	bytes	Master out slave in, width in bits is determined by settings

A single word transaction, containing both MISO and MOSI

Frame Type: "error"

Property	Type	Description

Indicates that the clock was in the wrong state when the enable signal transitioned to active