# Morse Micro SPI Analyzer Saleae Extension

**URL:** <https://community.morsemicro.com/t/morse-micro-spi-analyzer-saleae-extension/1206>\
**Category:** Projects\
**Created:** [December 30, 2025, 4:44pm UTC](https://community.morsemicro.com/t/morse-micro-spi-analyzer-saleae-extension/1206 "2025-12-30T16:44:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Luisschubert](https://avatars.discourse-cdn.com/v4/letter/l/ee7513/32.png) [@Luisschubert](https://community.morsemicro.com/u/Luisschubert)\
**Post date:** [December 30, 2025, 4:44pm UTC](https://community.morsemicro.com/t/morse-micro-spi-analyzer-saleae-extension/1206/1 "2025-12-30T16:44:51Z")

</div>

I created an extension for Saleae’s Logic 2 that I used a lot when debugging my system’s performance over SPI.  
It’s proved very useful to understand what is happening on the device and thought others might find it useful as well.

You can find the source code here: [GitHub - luisschubert/morse\_micro\_spi\_analyzer](https://github.com/luisschubert/morse_micro_spi_analyzer)

 ![overview](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/1X/33da51408160e68574ab4e443072f116eeaca0a0.jpeg)

Note that currently the analyzer can only make sense of what the complete address is when it gets the full trace from the beginning otherwise it shows unknown window. but it’s generally easy to deduce from the trace all the major transactions are 8011XXXX, but looking at the window update register commands will show that.

 ![Screenshot 2025-12-30 at 8.42.21 AM](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/1X/ddc52ccabbc8631aac9894f69a59aa6f36a0bfc2.png)
