V4 fails to properly read from RTC after power loss

[terminalvelocity23]

I have a DS3231 RTC module added into my V4 repeater (pins 17 and 18), and after simulating a power loss by cutting the battery power and logging back in the app shows year 2043, but the clock command shows 2/1/2000. After pushing the reset button or issuing a reboot command from CLI time returns to normal. The RTC battery is a brand new 2032 showing healthy 3.3 volts.
My guess is there's something wrong with RTC initialization timing, it isn't initialized yet when the time gets read from it after power loss, so the system gets garbage or default time from it. Maybe it needs a slight delay before the first read to initialize properly, although that's just my guess.

I'm running the latest stable firmware.

[IoTThinks]

Weird to see year 204x recently.

You remove the RTC, sync clock and reset to see if the clock jumps to 204x?

Then test again with RTC.

If yes, then something may be wrong with the code for RTC.

AFAIK, I2C at pin 17, 18 is broken by the OLED in Heltec v4 for MC 1.13.

When OLED is off, all I2C sensors and RTC die with it.

I have put a PR to fix it.

#1569

[terminalvelocity23]

You remove the RTC, sync clock and reset to see if the clock jumps to 204x?

It never did that without the RTC with the same firmware, so I have no reason to believe that unsoldering it suddenly will change this. Removing it isn't trivial.

AFAIK, I2C at pin 17, 18 is broken by the OLED in Heltec v4 for MC 1.13.

When OLED is off, all I2C sensors and RTC die with it.

I have put a PR to fix it.

Thank you, I'll try this.

[terminalvelocity23]

Looks like it's working properly now, no problems detected. No more year 2043 and no time resets.

[IoTThinks]

@terminalvelocity23 What did you do?
Applied the software fix or disassembled the OLED or disassembled the RTC?

[terminalvelocity23]

Applied the software fix or disassembled the OLED or disassembled the RTC?

Applied PR 1569.