Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: T-Beam Supreme - Display stays black #2519

Closed
Tom9876 opened this issue May 26, 2023 · 4 comments
Closed

[Bug]: T-Beam Supreme - Display stays black #2519

Tom9876 opened this issue May 26, 2023 · 4 comments

Comments

@Tom9876
Copy link

Tom9876 commented May 26, 2023

Category

Display not working - stays black

Hardware

LilyGO T-Beam Supreme U-blox MAX-M10S

Firmware Version

2.1.11.5ec624d

Description

The OLED Display (SH1106 - I2C connected to SDA:1017 / SCL:1018) stays black
Using SoftRF the display works fine
I re-flashed several times (also with the "core-board" disconnected from the "body", using CLI ((“./device-install.sh -f firmware-tbeam-s3-core-2.1.11.5ec624d.bin”) and the web-interface.
Watching the log I noticed a 2 minute pause after "Scanning for i2c devices on port 1". When the "core-board" is disconnected from the "body" there is no pause.
Also setting the display manually to SH1106 does not cure the problem.

Relevant log output

Scanning for i2c devices...
DEBUG | ??:??:?? 2 Scanning for i2c devices on port 2
DEBUG | ??:??:?? 3 I2C device found at address 0x34
INFO  | ??:??:?? 3 axp192/axp2101 PMU found
DEBUG | ??:??:?? 3 I2C device found at address 0x51
INFO  | ??:??:?? 3 PCF8563 RTC found
DEBUG | ??:??:?? 4 Scanning for i2c devices on port 1
INFO  | ??:??:?? 130 2 I2C devices found

@garthvh
Copy link
Member

garthvh commented May 26, 2023

@lewisxhe We are receiving some reports of screen issues with the new Tbeam Supreme

@geeksville
Copy link
Member

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/new-lilygo-t-beam-supreme-product/7474/27

@lewisxhe
Copy link
Contributor

A fix has been submitted #2520

@caveman99
Copy link
Member

merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants