# GPIO stops working after several hours

**URL:** <https://mangoh.discourse.group/t/gpio-stops-working-after-several-hours/1273>\
**Category:** mangOH Red\
**Created:** [March 25, 2018, 5:26pm UTC](https://mangoh.discourse.group/t/gpio-stops-working-after-several-hours/1273 "2018-03-25T17:26:24Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![coastalbrandon](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/coastalbrandon/32/264_2.png) [@coastalbrandon](https://mangoh.discourse.group/u/coastalbrandon)\
**Post date:** [May 1, 2018, 4:38pm UTC](https://mangoh.discourse.group/t/gpio-stops-working-after-several-hours/1273/24 "2018-05-01T16:38:34Z")

</div>

For everyone’s reference here’s what we discovered:

- We had not included the I2C hub in our electrical design. We have now included the hub and have ALL devices connected to the I2C hub and a single data line going back to the WP8548. This resolved our ‘bus busy’ problem at boot.
- We have found one unit so far (out of five) that has had a ‘bus busy’ after several hours, which may be indicative of the problem originally referenced in this thread. This is a unit that has the I2C hub in place.

---

_[View the full topic](https://mangoh.discourse.group/t/gpio-stops-working-after-several-hours/1273)._