Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0

[Stefan Parvu]

Testing the new clock for 5hrs downtime. No go. This is driving me nuts.
Something is very odd here, but not sure what. It works fine for short 
periods of time, but then somehow for longer periods of time nope (>1-2hrs)

$ kldstat
Id Refs Address                Size Name
 1    9 0xffff000000000000  13d1480 kernel
 3    1 0xffff000001415000    40ea8 nxprtc.ko
 4    1 0xffff000053600000    41000 tmpfs.ko
 5    1 0xffff000053641000    31000 mac_ntpd.ko

$ dmesg | grep nxp
nxprtc0: <NXP PCF2129 RTC> at addr 0xa2 on iicbus0
nxprtc0: WARNING: RTC battery failed; time is invalid
nxprtc0: registered as a time-of-day clock, resolution 0.015625s
nxprtc0: RTC clock not running


Stefan Parvu
sparvu at kronometrix.org



> On 19 Jul 2019, at 12.40, Stefan Parvu <sparvu at kronometrix.org> wrote:
> 
>> The time couldn't have been correct from the RTC if it said the clock
>> was not running -- the driver says that instead of returning a time to
>> the kernel.  Ntpd must have already set the time before you checked it.
> 
> Thats correct. Tests were done incorrectly. The power cable was not removed
> the board still had power. 
> 
> I have repected fresh all tests. Now, very strange everything is fine. I cant explain
> what has happened except:
> 
> * kldunload / load nxprtc 
> 
> * creating a new hints file 
> 
> * removing and re-inserting the battery 
> 
> I have powered off the board for 2hrs and the time functions correctly. I will soon
> setup another RBPI board and re-test all over with the new ko module. 
> 
> Stefan
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"