semvec/pypi-packages huggingface dataset:
pysigrok-decoder-xspiflash 0.0.1
PySigrok decoder for multibit SPI flash transactions.
Requires Python: >=3.7


# SPI Flash Analyzer for Logic 2


[![Box with Discord user count](https://img.shields.io/discord/327254708534116352.svg)](https://adafru.it/discord)
[![Box with MIT license](https://img.shields.io/badge/License-MIT-brightgreen.svg)](https://choosealicense.com/licenses/mit/)

This is a basic high level analyzer for Saleae Logic 2 that interprets semi-standard SPI flash commands. The output can be limited by command type and data commands can also be limited by address. One can add the analyzer multiple times to get separate analysis tracks for different types of commands.

![Screenshot of the extension](screenshot.png)

## Installation

In Logic 2, click extensions on the right hand side.

### To Use

Under the three dot, more menu, click `Check for Updates` then install the `SPI Flash` extension.

### To Develop

1. Clone this repo locally.
2. Under the three dot, more menu, click `Load Existing Extension...` and then select the local repo location.

## Usage

### Normal SPI
1. Click the analyzers tab.
2. Add a `SPI` analyzer and configure it for your capture.
3. Add a `SPI Flash` analyzer.
4. Set the `SPI` analyzer as the Input Analyzer.
5. `Min Address`, `Max Address` and `Decode Level` are optional.
6. Change `Address Bytes` to match

### Quad SPI
1. Click the analyzers tab.
2. Add a `Simple Parallel` analyzer. (You may need to search for it.)
3. Configure it for your capture.
  1. Set D0 to MOSI.
  2. Set D1 to MISO.
  3. Set D2 to IO2 (WP on 8 pin flashes usually.)
  4. Set D3 to IO3 (HOLD on 8 pin flashes usually.)
  5. Set D15 to CS (used to ignore extra clocks.)
  6. Set the clock to the clock pin with the correct edge set.
4. Add a `SPI Flash` analyzer.
5. Set the `Simple Parallel` analyzer as the Input Analyzer.
6. `Min Address`, `Max Address` and `Decode Level` are optional.
7. Change `Address Bytes` to match

Note: When using Simple Parallel input, it is assumed the CS line goes high between parallel captures that are greater than 4 times the time separation of the closest clocks seen thus far. So, beware of spurious clocks and SPI transmissions that pause between bytes but leave CS low. This analyzer may incorrectly partition the transactions.