You are reading a single comment by @fanoush and its replies.
Click here to read the full conversation.
-
a solution is to run software i2c on top. This way the bangle's integrated events can be used instead of the interrupt pin, works very nice.
Interesting that it works. Bangle firmware already use (software) i2c on top of same touch i2c pins, in fact many of them seen here
So you have yet another
new I2C()that yousetup()to have same pins as one of those bangle internal ones.That may still be OK but I wonder what happens when the touch irq comes in the middle of your i2c code call and bangle native irq handler runs some read over same pins via its own I2C object.
fanoush
enaon
in the case someone else want to have control of the touch like I do, a solution is to run software i2c on top. This way the bangle's integrated events can be used instead of the interrupt pin, works very nice.