adafruit / adafruit/Adafruit_CircuitPython_STMPE610

Should I2C support be removed

Open
#23 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
3
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Does anyone use the I2C mode? It is available on the now discontinued and unavailable breakout board but it is not used on any of the tft displays that have the stpme chips built in. They all use SPI.

In addition, the I2C implementation can be flaky and I wonder if it is worthwhile troubleshooting it.

When using the stmpe610 breakout in I2C mode, there are occasional errors
```
>>> import stmpe610_simpletest_i2c
Go Ahead - Touch the Screen - Make My Day!
(1266, 2298, 130)
(1247, 2296, 18)
Traceback (most recent call last):
File "", line 1, in
File "stmpe610_simpletest_i2c.py", line 14, in
File "adafruit_stmpe610.py", line 213, in buffer_empty
File "adafruit_stmpe610.py", line 164, in _read_byte
File "adafruit_stmpe610.py", line 246, in _read_register
OSError: [Errno 5] Input/output error
>>>
```

This was on a GrandCentral M4 running the simpletest in I2C mode.
I have also seen "Error 19 - Unsupported Operations) errors on a QTPY esp32s2

I don't think this is new. I think I saw this in the past but did not open an issue.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing stmpe610_simpletest_i2c.py and the I2C-related paths in adafruit_stmpe610.py, especially _read_byte, _read_register, and buffer_empty. Compare the reported GrandCentral M4 and QT Py ESP32-S2 errors, then determine whether I2C should be removed or troubleshot. Done requires a decided direction and corresponding validation of I2C behavior or removal.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
embedded-iot
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.