My Rpi4 / Rock 9.3 boots up with the date set to Aug 21, 2023. It doesn’t take long for chronyd to set the clock but in the meantime logs are using the wrong date.
I bought an Adafruit PCF8523 RTC that just pops on the GPIO bus. Unfortunately, all of the docs/tutorials I can find for this clock assume that the Pi4 is running raspian and to use raspi-config to enable the i2c bus.
I guess the trick is going to be figuring out what values the 6 pins used by the RTC module need to be set.
So far I haven’t seen any low level info covering this. What I am finding is “import these python3 modules and set the time”.
What I see in reality is that those python scripts don’t even see the RTC module on the GPIO bus so that’s why I asked about enabling that bus as raspi-config would do. I do have a 3B+ still on Ubuntu so maybe I can take a peek at that and glean some information.
Unfortunately, that’s all the farther I’ve gotten. The rpm mentioned in the reddit thread adds sections to /boot/config.txt like this:
# Start managed by rpi4-i2c-userspace rpm
dtparam=i2c_arm=on
i2c-bcm2708
# End managed by rpi4-i2c-userspace rpm
# Start managed by rpi4-i2c-userspace-i2c1 rpm
dtparam=i2c1=on
# End managed by rpi4-i2c-userspace-i2c1 rpm
Rebooting to enable that does nothing that I can see. i2cdetect -y 1 still shows a 68 instead of a UU to show that the clock is working.
hwclock finds no clock:
jross@rpi4:~$ sudo hwclock --verbose -r
hwclock from util-linux 2.37.4
System Time: 1705006319.086912
Trying to open: /dev/rtc0
Trying to open: /dev/rtc
Trying to open: /dev/misc/rtc
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
So I’m stopped for now unless someone has a clue by four to help me out