You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing the companion firmware v1.15.0 on a Lilygo T-Beam Supreme ESP32-S3 V3.0 the display stays dark.
The device came originally with Meshtastic preinstalled. It showed the Meshtastic information on its OLED display. Installing MeshCore Companion Bluetooth from https://flasher.meshcore.io/lilygo-t-beam-supreme-sx1262/ seemed to work, but the OLED display stays dark after rebooting.
change bool SH1106Display::begin() similar to the proposal in Display Fix for different versions of TBeam Supreme #2591, but extending bool SH1106Display::i2c_probe(TwoWire &wire, uint8_t addr) to probe for a SH1106 at the probed address instead.
remove DISPLAY_ADDRESS completely. This will also affect the code of wio-tracker-l1.
change void TBeamBoard::scanDevices(TwoWire *w) to add the additional address for debugging.
The best solution seems to check if at 0x3C is a SH1106 and try 0x3D, if it is not.
Please advise me, if I should just add another variant (e.g. lilygo_tbeam_supreme_SX1262_v3).
Problem description
After installing the companion firmware v1.15.0 on a Lilygo T-Beam Supreme ESP32-S3 V3.0 the display stays dark.
The device came originally with Meshtastic preinstalled. It showed the Meshtastic information on its OLED display. Installing MeshCore Companion Bluetooth from https://flasher.meshcore.io/lilygo-t-beam-supreme-sx1262/ seemed to work, but the OLED display stays dark after rebooting.
Analysis
Lilygo's documentation at https://github.com/Xinyuan-LilyGO/LilyGo-LoRa-Series/blob/master/docs/en/t_beam_supreme/t_beam_supreme_hw.md states that the OLED has a another I2C address (0x3D instead of 0x3C), if the device has a MAG sensor QMC6310N at 0x3C.
Proposed solution
Extend the code to include 0x3D as I2C address.
bool SH1106Display::begin()similar to the proposal in Display Fix for different versions of TBeam Supreme #2591, but extendingbool SH1106Display::i2c_probe(TwoWire &wire, uint8_t addr)to probe for a SH1106 at the probed address instead.DISPLAY_ADDRESScompletely. This will also affect the code of wio-tracker-l1.void TBeamBoard::scanDevices(TwoWire *w)to add the additional address for debugging.The best solution seems to check if at 0x3C is a SH1106 and try 0x3D, if it is not.
Please advise me, if I should just add another variant (e.g. lilygo_tbeam_supreme_SX1262_v3).