hwclock issue pcf8523 (slackwareaarch64-current RPi 4)

eduardr · 05-03-2023, 12:46 PM

Used the standard slackwareaarch64-current image to set up an RPi4. No SARPI.

This Slackware installer hardcodes the ds1307 clock module, which is not installed in my RPi. Instead I have the pcf8523.

After quite some digging around I extracted the initrd contents (initrd-armv8-6.1.27), and made changes to it to reference pcf8523 instead, and the correct module loads now but hwclock still fails to get data from the module. On a previous installation I used SARPI and that worked great with this same module, once I enabled the appropriate line in /boot/config.txt

File "load_kernel_modules.scr/platform/aarch64/bcm2711"

Code:

...
MOD_RTC="rtc-pcf8523"
...
echo pcf8523 0x68 > /sys/class/i2c-adapter/i2c-1/new_device
...

File "bcm2837"

Code:

MOD_RTC="rtc-pcf8523"

Code:

[root@rpi1a ~]# dmesg|grep -i rtc
[Thu Jan  1 02:00:14 1970] rtc-pcf8523 1-0068: registered as rtc0
[Thu Jan  1 02:00:14 1970] rtc-pcf8523 1-0068: hctosys: unable to read the hardware clock
[Thu Jan  1 02:00:19 1970] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4])
[Thu Jan  1 02:00:19 1970] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4])
[Thu Jan  1 02:00:19 1970] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4])
[Thu Jan  1 02:00:19 1970] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4])

[root@rpi1a ~]# hwclock
hwclock: ioctl(RTC_RD_TIME) to /dev/rtc0 to read the time failed: Invalid argument

[root@rpi1a ~]# ls -al /dev/rtc*
lrwxrwxrwx 1 root root      4 Jan  1 02:00 /dev/rtc -> rtc0
crw-r--r-- 1 root root 251, 0 Jan  1 02:00 /dev/rtc0

[root@rpi1a ~]# lsmod|grep rtc
rtc_pcf8523            16384  0

Thanks for any hints!

drmozes · 05-05-2023, 06:05 AM

Try using the Device Tree Overlays.
I did not succeed in making DTO work for the ds1307 which is why it's still set up from the OS InitRD, but if anybody does make it work with DTO, let me know as that's the preferred route for this stuff.

eduardr · 05-05-2023, 07:26 AM

Thanks Stuart, I'll look into dto and try to get my clocks working (pcf8523 and RasClock pcf212x) - don't have any clocks working yet in my new installs. Worked fine on SARPI in the past but I'm not using SARPI currently.

drmozes · 05-05-2023, 09:19 AM

Quote:

Originally Posted by eduardr

Thanks Stuart, I'll look into dto and try to get my clocks working (pcf8523 and RasClock pcf212x) - don't have any clocks working yet in my new installs. Worked fine on SARPI in the past but I'm not using SARPI currently.

Interesting. I wonder if it's that the mainline Kernel is missing support.

If you like I can build a proper set of Slackware Kernel packages from the RPi Kernel fork of Linux 6.1.27 and put them online. You can upgradepkg to them from Slackware, and roll back to the proper packages if you want.

I've also just made a change to kernel.SlackBuild to make it easier to store the resulting packages in an alternate directory, so if anybody does want to provide such packages to the community it's even easier than before. I'll update the Kernel build doc once I push out the updates.

drmozes · 05-05-2023, 11:35 AM

I've uploaded the kernel and kernel-modules packages which is all that's required. If you or anybody fancies using them, have fun ;-)

Caveat - I haven't tested these.

I've updated the custom Kernel document as well so that the packages can be created outside of the Slackware tree.

eduardr · 05-07-2023, 02:40 PM

Thank you very much Stewart. It looks like I was able to get the RasClock at least to work (pcf2129, uses the pcf2127 module) using the manual approach by writing to address 51 instead of 68. Now I need to replace the CR1220 battery on it and make sure it works by making this change in the initrd. If it fails and I can't get dto to work either, will try the kernel fork approach as well.