| Bus | File Name | Interface | Signals | Protocol | Frequency | Period | Bits | Data | Non-FF | Decoded | Issues | Waveform | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| No files loaded. Drop CSV files above to begin analysis. | |||||||||||||
| 0x50 | Find byte 0x50 |
| 0x5080 | Find sequence 0x50 0x80 |
| 0x50 0x80 | Same as above (space-separated) |
| !0x50 | Find bytes NOT equal to 0x50 |
| !0x50 && !0x51 | Exclude both 0x50 and 0x51 |
| 0x50 || 0x51 | Find 0x50 OR 0x51 |
| All | Search addresses and data |
| Address | Search only I2C addresses |
| Data | Search only data bytes |
| Read/Write | Filter by transaction type |
This tool analyzes digital signal captures from logic analyzers. It extracts clock-synchronized data bits and can decode various protocols.
The tool accepts CSV files from Kingst Logic Analyzer software, KVDAT captures, and oscilloscope waveform CSVs with metadata before the data header. The CSV should have:
Single-channel waveform CSVs can be selected with the Bus checkboxes and combined with Create Bus. Files named like SDA/Data and SCL/CLK are paired automatically when dropped together.
Time[s], clock, dat 2.00000000, 1, 1 2.30403414, 0, 1 2.30403514, 1, 1 2.30403614, 0, 1 2.30403714, 1, 0 2.30403814, 0, 0 2.30403914, 1, 1
The tool auto-detects available interface types based on the number of columns in your CSV:
| Interface | Signals | Min Columns | Protocols |
|---|---|---|---|
| 2-Wire | CLK, DATA | 2 | FSI, IยฒC, SMBus, PMBus |
| SPI (4-Wire) | CLK, MOSI, MISO, CS | 4 | SPI |
| Dual SPI | CLK, IO0, IO1, CS | 4 | Dual SPI |
| Quad SPI | CLK, IO0-3, CS | 6 | QSPI |
| Setting | Description | Default |
|---|---|---|
Interface | Select the interface type (auto-filtered by column count) | 2-Wire |
Signals | Column index for each signal (1-based after time column) | Sequential |
Protocol | Protocol decoder (filtered by interface type) | None |
Note: Sampling edge and bit order are determined by the selected protocol.
Protocol definitions are loaded from the protocols/ folder as JSON files. Currently supported:
Protocols are automatically filtered based on the selected interface type. Add new protocols by placing JSON definition files in the protocols/ directory with an interface section.
| 0x50 | Find byte 0x50 |
| 0x5080 | Find sequence 0x50 0x80 |
| 0x50 0x80 | Same as above (space-separated) |
| !0x50 | Find bytes NOT equal to 0x50 |
| !0x50 && !0x51 | Exclude both 0x50 and 0x51 |
| 0x50 || 0x51 | Find 0x50 OR 0x51 |
| All | Search addresses and data |
| Address | Search only I2C addresses |
| Data | Search only data bytes |
| Read/Write | Filter by transaction type |