RTC not setting with 24-11 disc update

I’ve tried the prior version of PlingBoot & yesterday’s (24th Nov) with the 21st & 25th Nov ROMs.

Any combo with an earlier PlingBoot works fine but yesterday’s leaves the clock set at 2nd Jan 1970. Clicking ‘Try’ in the Time & date config gives ‘Sync success’ yet that isn’t reflected in setting the clock.

I don’t have a clock battery & the above is from power on. It’s a BB -xm Rev C.

OK on the batteryless Pi from a cold start with OS5.21 (25-Nov-13) and !Boot 24Nov13. The NetTime module is now 0.42 and the RTC module is dormant.

I’ll try integrating the new !Boot again tomorrow. It’s usually easy to know what one’s added but perhaps I missed removing something. Else I’ll try a virgin !Boot.

Oh, well. Couldn’t wait so tried a virgin copy of !Boot with only networking configured. Same symptoms. RTC is 0.1 in ROM & active, NetTime is 0.42. ‘Try’ still gives ‘Sync success’ without resetting the clock.

On the other hand the situation is not quite so good on the Iyonix. This has !Boot of 24th Nov and can softload OS5.21 of 25th Nov. There is a battery backed real time clock so it might not be immediately obvious if something was wrong. The test is to mis-set the clock manually and see if “Set from the network” works, in OS5.21 the clock is left at the wrong time whereas in OS5.20 it does reset to the current time. The NetTime module is 0.42 in both cases, it is in !System, and it is the same !Boot in both cases. The relevant difference between OS5.20 and OS5.21(25 Nov 13) might be that OS5.20 has RTCAdjust 0.10 in ROM but it is dormant, OS5.21 has the new RTC module 0.01 and it is active. Unplugging the RTC module gets internet time working again in OS5.21.

The Raspberry Pi does pass that test, but the RTC module is dormant.

I can confirm the same issues with my -Xm, which does not have a battery backup, and 24/11 disc image.

Unplugging the RTC module restores the time setting via the NetTime module however if you have “Switch DST automatically” set then the clock is 1hr out. Unticking this and leaving DST active sets the time correctly for now.

It sounds like the large adjustment (1970→2013) isn’t working for some reason when applied by NetTime. In that situation, could you say what the “last protocol” used was as reported by

*NetTime_Status

SYS"RTC_Adjust",0,-&20,360000,3<<24

This is from the Iyonix, OS5.21 (25-Nov-13). The test is just to set the hours back a bit, the real time clock does work there is no fall back to the default start year.

*NetTime_Status
Current time:    Tuesday, 26 November 2013 05:14:41.89
Status:          Sleeping
Last server:     pool.ntp.org
Last protocol:   SNTP
Poll interval:   30 minutes
*BASIc
ARM BBC BASIC V version 1.55 (C) Acorn 1989

Starting with 651516 bytes free

>SYS "RTC_Adjust",0,-&20,360000,3<<24
>QUIT
*NETTime_kick
*NetTime_Status
Current time:    Friday, 15 June 2057 13:10:16.21
Status:          Sleeping
Last server:     pool.ntp.org
Last protocol:   SNTP
Poll interval:   30 minutes
*unplug RTC
*NetTime_Kick
*NetTime_Status
Current time:    Friday, 15 June 2057 13:11:15.74
Status:          Sleeping
Last adjustment: 9 seconds ago
Last delta:      1374375124.100059 seconds fast
Last server:     pool.ntp.org
Last protocol:   SNTP
Poll interval:   30 minutes
*

Seems OK here now, with NetTime 0.43, 25th Nov ROM. Great!

Seems OK on the Iyonix too, !Boot and ROM dated 28 Nov 13. Many thanks.