T-Beam Supreme blank display on v1.17.0

[crackedatom]

Flashing the companion v1.17.0 firmware yields a blank OLED display. All other functionality seems to work after boot. Performing a full erase has no effect and reverting the firmware to v1.16.0 restores OLED.

Hardware: LilyGo T-Beam Supreme (SX1262)
Vesion: Companion v1.17.0

[Chuck-it]

Rebooting...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x420ba426
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x4bc
load:0x403c9700,len:0xbd8
load:0x403cc700,len:0x2a0c
entry 0x403c98d0
Repeater ID: 7BB689B413636FF8E8EAF248458A8661B9877B6934FE3F8BD32FFF7F9B4EA17C
E (2956) gpio: gpio_set_level(227): GPIO output gpio_num error
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.

Core 1 register dump:
PC : 0x4209e9f3 PS : 0x00060c30 A0 : 0x8209ea39 A1 : 0x3fcebae0
A2 : 0x00000000 A3 : 0x3c0ddfbf A4 : 0x3c0ddfc4 A5 : 0x00000b8c
A6 : 0x3c0ddfbf A7 : 0x3c0de2cf A8 : 0x82064d5e A9 : 0x3fceba40
A10 : 0x00000001 A11 : 0x3c0ddfbf A12 : 0x3c0ddfc4 A13 : 0x3fcebad0
A14 : 0x3fceba80 A15 : 0x0000000c SAR : 0x00000016 EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000 LBEG : 0x400556d5 LEND : 0x400556e5 LCOUNT : 0xfffffff9

Backtrace: 0x4209e9f0:0x3fcebae0 0x4209ea36:0x3fcebb00 0x4209ea5e:0x3fcebb20 0x42018cb9:0x3fcebb40 0x42010dd1:0x3fcebb80 0x42005c31:0x3fcebba0 0x4200622f:0x3fcebbc0 0x42030f96:0x3fcebc50

GPIO Problem in Firmware? level is set to 227, maximum is 39?

[strasharo]

Can confirm this on my end too — T-Beam Supreme (SX1262), Companion/BLE role.

• Flashed T_Beam_S3_Supreme_SX1262_companion_radio_ble-v1.17.0-727fc05-merged.bin via esptool write_flash 0x0: device boots fine (BLE/companion protocol all work), but OLED stays completely blank — no boot logo, no pairing PIN, nothing.
• Reflashed T_Beam_S3_Supreme_SX1262_companion_radio_ble-v1.16.0-07a3ca9-merged.bin on the exact same unit, no other changes: OLED works immediately, shows the BLE pairing PIN as expected.
• Reflashed back to v1.17.0 to match latest: display goes blank again.

So this is clean and reproducible on my hardware too — 100% correlated with the v1.16.0 → v1.17.0 jump on Companion/BLE for this board, nothing else changed between tests. Given PR #2815 (fixing the OLED at the T-Beam Supreme's actual I2C address, 0x3D) landed before the v1.17.0 release, it looks like something in the range between those two tags regressed it again — possibly the display init path only being exercised/tested on the repeater variant (per that PR's test plan) and not companion_radio_ble.

Happy to test any candidate fix/nightly build against this hardware if useful.

[strasharo]

Opened a fix for this: #3153 — tested and confirmed working on the same T-Beam Supreme unit I reproduced the regression on earlier in this thread.