# I2C Parsing Bug

**URL:** <https://discuss.saleae.com/t/i2c-parsing-bug/962>\
**Category:** Logic 2 Software\
**Created:** [March 17, 2021, 1:10am UTC](https://discuss.saleae.com/t/i2c-parsing-bug/962 "2021-03-17T01:10:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrey](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/andrey/32/776_2.png) [@andrey](https://discuss.saleae.com/u/andrey)\
**Post date:** [March 17, 2021, 1:10am UTC](https://discuss.saleae.com/t/i2c-parsing-bug/962/1 "2021-03-17T01:10:20Z")

</div>

Seems like the I2C parsing is incorrect in Logic 2.  
Logic 1 parses the address correctly - 0x52.  
Logic 2 parses it as 0x29 = 0x52 \>\> 1.

 ![logic-1](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/51c6d00a6adcccf601aad1c9c8df060f83f410cd.png) ![logic-2](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/c93e4a54a3d52a82c6a95091b16b09887cb2b6c8.png)

NVM, not a bug, I2C address display is limited to ‘as 7-bit numbers’, here’s an extension to override it [Viewing I2C Addresses as 8-bit - Saleae Support](https://support.saleae.com/faq/technical-faq/viewing-i2c-addresses-as-8-bit)

---

<div class="post-metadata">

**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:** [March 17, 2021, 10:37pm UTC](https://discuss.saleae.com/t/i2c-parsing-bug/962/2 "2021-03-17T22:37:27Z")

</div>

@andrey Sorry for the misunderstanding with that! Yes, you are correct in that the I2C address display is limited to 7-bit numbers. The extension you mentioned is in fact the solution for this. Thanks for posting that!