# eSPI protocol **URL:** \ **Category:** Uncategorized\ **Created:** [January 16, 2024, 9:41am UTC](https://discuss.saleae.com/t/espi-protocol/2667 "2024-01-16T09:41:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![fei.wu](https://avatars.discourse-cdn.com/v4/letter/f/e274bd/32.png) [@fei.wu](https://discuss.saleae.com/u/fei.wu)\ **Post date:** [January 16, 2024, 9:41am UTC](https://discuss.saleae.com/t/espi-protocol/2667/1 "2024-01-16T09:41:35Z")
Hi Saleae team, Does Saleas support the eSPI protocol? ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [January 16, 2024, 7:25pm UTC](https://discuss.saleae.com/t/espi-protocol/2667/2 "2024-01-16T19:25:05Z")
@fei.wu We unfortunately don’t have official native support for decoding eSPI packets. We’re currently tracking this feature request in the link below and I’ve added a comment for you to track your need for this feature. Feel free to vote for it! > **[ESPI (Enhanced Serial Peripheral Interface) protocol support - Logic 2 -...](https://ideas.saleae.com/b/feature-requests/espi-enhanced-serial-peripheral-interface-protocol-support/)** > > Link to documentation of the eSPI protocol - www.intel.com/content/dam/support/us/en/documents/software/chipset-software/327432-004\_espi\_base\_specification\_rev1.0\_cb.pdf You may find some luck by using our included SPI analyzer. The issue you may run into is that our SPI analyzer has one setting for word length (e.g. you can specify an 8-bit word length), and the SPI analyzer will always decode in chunks of that setting (e.g. in 8-bit chunks). I understand that the eSPI protocol doesn’t always stick to one bit word length, so you may run into trouble with decoding synchronization if the bit word lengths are not always the same. Your best bet at the moment would be to create a custom analyzer using our protocol analyzer SDK below, however, it will require extensive C++ knowledge. > **[Protocol Analyzer SDK](https://support.saleae.com/saleae-api-and-sdk/protocol-analyzer-sdk)** ---
**Author:** ![fei.wu](https://avatars.discourse-cdn.com/v4/letter/f/e274bd/32.png) [@fei.wu](https://discuss.saleae.com/u/fei.wu)\ **Post date:** [January 17, 2024, 8:38am UTC](https://discuss.saleae.com/t/espi-protocol/2667/3 "2024-01-17T08:38:49Z")
Got it, thanks Timreyes, do you have any plan to release official eSPI decoder? ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [January 17, 2024, 8:07pm UTC](https://discuss.saleae.com/t/espi-protocol/2667/4 "2024-01-17T20:07:04Z")
@fei.wu You’re very welcome! We don’t have any plans at the moment due to other priority projects on our plate. As an alternative, I did want to mention that the folks at Binho are currently providing services to develop custom extensions and analyzers. More information on this can be found in the link below in case you are interested in reaching out to them for a custom eSPI analyzer solution. > **[Custom Protocol Analyzer Development for Saleae Logic](https://binho.io/pages/custom-protocol-analyzer-development)** > > Whether it's adding on another layer to parse I2C transactions to the specific devices on your product, a minor tweak to an existing protocol analyzer, or building a decoder for a new/proprietary protocol entirely from scratch, Binho's got the... ---
**Author:** ![fei.wu](https://avatars.discourse-cdn.com/v4/letter/f/e274bd/32.png) [@fei.wu](https://discuss.saleae.com/u/fei.wu)\ **Post date:** [January 18, 2024, 7:07am UTC](https://discuss.saleae.com/t/espi-protocol/2667/5 "2024-01-18T07:07:24Z")
Got it, thanks.