RTC oddity: has anyone seen this?
Posted: Fri Jan 20, 2017 10:55 am
I have a project which uses the Pyboard's low power modes and an RTC backup battery. The situation I'm about to describe convinced me there was an intermittent fault with my hardware so I built a new set. I've now seen it on the new set too. The hardware of both sets is properly constructed with a PCB. I'm unsure what triggers it: it doesn't occur in unattended operation but only when I'm making changes to the system. The symptoms are as follows.
The REPL works fine but the RTC is at the initial value set by the firmware. If I try to set it with rtc.datetime((8-tuple)) the function takes a second or two to return and the RTC is unchanged. The only solution is to do a complete power down including disconnecting the RTC backup battery. rtc.datetime((8-tuple)) then works and returns immediately.
On today's appearance of the fault it occurred after making a minor hardware change with the board powered down and the backup battery in place. No code changes were made.
I can work round this and I'm not expecting a fix: I'm just puzzled as to the cause and wondered if anyone else had encountered it.
The REPL works fine but the RTC is at the initial value set by the firmware. If I try to set it with rtc.datetime((8-tuple)) the function takes a second or two to return and the RTC is unchanged. The only solution is to do a complete power down including disconnecting the RTC backup battery. rtc.datetime((8-tuple)) then works and returns immediately.
On today's appearance of the fault it occurred after making a minor hardware change with the board powered down and the backup battery in place. No code changes were made.
I can work round this and I'm not expecting a fix: I'm just puzzled as to the cause and wondered if anyone else had encountered it.