DST and Panda ROM 23/10/17
Doug Webb (190) 1129 posts |
Hi, I’ve got an issue with DST since the clock changes on my Pandaboard with a CJE RTC board. The “Switch DST automatically” option is ticked the configuration tool but the clock is 1hr off what it should be. Resyncing the clock shows successfully but does not change the time back 1hr. If I manually take off the option and then reset it on it does make the change. Equally if set the option to off and load and run !Organizer then it will change the clock time to the correct value. If I put the option on for DST in the configuration tool and load and run !Organizer then it will not reflect the correct DST time. I have a CJE Micro RTC board install but taking that off doesn’t make any diference to the behaviour. I know the DST tool has been subject to a lot of discussions but can’t see any mention of this issue. |
Doug Webb (190) 1129 posts |
Hi again As an update to this I fired up my Iyonix and it too has the same behaviour with TOM build 16th Oct 17. So I tried older versions as per below: 20th Aug 17 HV softload – DST time is correct CVS doesn’t show anything obvious to a lay person like myself but as it effects two different system types and works/not works between two ROM build dates then I suspect it is an issue with some chnage put in that isn’t working as it should. If I can find other builds I’ll test but in the meantime it is narrowed down to a 12 day period of CVS activity. |
Frederick Bambrough (1372) 817 posts |
Same here with BB -xM and 30th Oct ROM. Deleting & selecting ‘Switch DST automatically’ works here too. Re-boot re-introduces the error. Setting DST off manually survives re-boot. |
Doug Webb (190) 1129 posts |
So I’ve found some more ROM builds I saved for my Pandaboard but nothing more for the Iyonix but I think I’m safe in saying this is a generic issue rather than machine specific. Anyway the results of the tests are as below: 8th Sept 17 ROM HV – DST time correct Only 3 changes in CVS so at least it should be simple for someone to track down the issue :-) |
Steve Pampling (1551) 7921 posts |
Iām safe in saying this is a generic issue rather than machine specific. Very much generic – it affects the IOMD HAL version when used on RPCEmu. 2017-09-08 works with time shown correct There’s more than a couple of change entries for September 9th, most seem to be labelled as keyboard related. |
Martin Avison (27) 1417 posts |
I have this problem on a RPi1 with RTC board, using ROM 1/10/2017. I also have an RPi3, and do not have the problem… with an identical cloned SD card… but I have not yet fitted a RTC card. My next moves will be to swap the RTC over when I get chance to open the cases up. |
David Pitt (3386) 1248 posts |
To get my Titanium to do GMT I have reverted to the ROM of 08Sep17. |
Martin Avison (27) 1417 posts |
I have a Pi1B and a Pi3, both running 5.23H 1/10/2017 with 18/2/2017 firmware from cloned SD cards. I also have two different CJE RTC modules – an old one with 3 black chips, and a new one with only two. I have spent some time trying various combinations, all with an Internet connection, and my conclusions are: Note that I always powered off and re-booted before checking this. Without this I could manage to avoid having DST set sometimes, which was confusing. I think this bug can be avoided for the moment by simply un-selecting I am aware that this bug also affects other types of machine, not using the CJE RTC module, but perhaps it is caused by the presence of any RTC? |
Chris Evans (457) 1614 posts |
RTC chips have no sense of DST/BST the bug I deduce was introduced 9.9.2017 in i2cutils Only one line (1168) seems to be have changed: |
Steve Pampling (1551) 7921 posts |
I was going to say “is that used in the IOMD port”, but I see it’s a CMOS code block so yeah, everywhere. |
Martin Avison (27) 1417 posts |
David seems to have Titanium problems (see above). |
Martin Avison (27) 1417 posts |
Bug ticket #441 raised. |
Frederick Bambrough (1372) 817 posts |
Resolved on my BB -xM with today’s (13/11/17) ROM update. |