Note: This page describes bus-transaction monitoring in the discontinued Windows application Accordion Pilot. The current interface is the browser-based Web UI – Bus Transactions; the concepts apply to Accordion Shell’s
i2ccommand as well.
Overview
The Transactions view provides real-time monitoring and analysis of bus communications including I2C, SPI, UART and socket transactions — essential for debugging communication, verifying protocol correctness and understanding device behaviour.
Supported transaction types
- I2C — sensor comms, EEPROM, PMBus, RTC, I/O expanders. Details: address, operation (read/write/combined), data, ACK/NACK status, timing.
- SPI — flash, ADC/DAC, displays, SD cards. Details: chip select, mode (clock polarity/phase), MOSI/MISO data, clock speed, bit order.
- UART — serial console, GPS, Bluetooth, debug. Details: direction (TX/RX), data, baud rate, format (data/parity/stop), errors.
- Socket — TCP/UDP network comms. Details: protocol, IP:port, direction, payload, status.
Transaction log
Each transaction shows timestamp, type, direction, address/channel, data (hex), status, duration and details. Auto-scroll follows the newest transactions; the log keeps a configurable number of recent transactions (default 1000) and drops the oldest.
Filtering
Filter by type (I2C/SPI/UART/Socket), by address or channel (e.g. 0x3C, I2C_BUS_0), by direction (read/write), by time range, and by searching the data content for a byte pattern.
Transaction details
Expand a transaction for the full byte sequence and timing. For example, an I2C read is START → ADDR+W → ACK → REG → ACK → RESTART → ADDR+R → ACK → DATA → NACK → STOP; a write omits the restart/read. Errors (NACK, timeout, framing/parity for UART, connection loss for sockets) are highlighted in red.
Sending custom commands
Trigger transactions from the Channels view, or from Accordion Shell:
accordionshell i2c --channel "I2C_BUS_0" --address 0x3C --data "01 02 03"
accordionshell i2c --channel "I2C_BUS_0" --address 0x3C --read --length 4
Export & history
Export visible transactions to CSV/Excel for archiving or analysis, and clear the log between tests. Filter aggressively and clear regularly to keep performance up during long sessions.