rp2: Don't reset RTC over RP2350 reset or deepsleep. · micropython/micropython@eb1611d · GitHub

micropython / micropython Public

• Notifications You must be signed in to change notification settings
• Fork 9k
• Star 22.1k

• Code
• Issues 1.2k
• Pull requests 372
• Discussions
• Actions
• Projects
• Wiki
• Security and quality
• Insights

Additional navigation options

Commit eb1611d

Browse filesBrowse the repository at this point in the historyBrowse files

projectgus

authored and

dpgeorge

committed

rp2: Don't reset RTC over RP2350 reset or deepsleep.

machine.RTC will now keep its value after machine.reset() or machine.deepsleep(). Only changes behaviour on RP2350. On RP2040 the AON timer is never running at this point, but it may be possible to keep it on by changing mp_machine_reset(). This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>

1 parent f217a31 commit eb1611d
Copy full SHA for eb1611d

1 file changed

+6-4Lines changed: 6 additions & 4 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• ports/rp2
  • main.c

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎ports/rp2/main.c‎

Copy file name to clipboardExpand all lines: ports/rp2/main.c

+6-4Lines changed: 6 additions & 4 deletions

Original file line number	Diff line number	Diff line change
@@ -138,10 +138,12 @@ int main(int argc, char **argv) {
138	138	mp_thread_init();
139	139	#endif
140	140
141		- // Start and initialise the RTC
142		- struct timespec ts = { 0, 0 };
143		- ts.tv_sec = timeutils_seconds_since_epoch(2021, 1, 1, 0, 0, 0);
144		- aon_timer_start(&ts);
	141	+ if (!aon_timer_is_running()) {
	142	+ // Start and initialise the RTC if not already running
	143	+ struct timespec ts = { 0, 0 };
	144	+ ts.tv_sec = timeutils_seconds_since_epoch(2021, 1, 1, 0, 0, 0);
	145	+ aon_timer_start(&ts);
	146	+ }
145	147	mp_hal_time_ns_set_from_rtc();
146	148
147	149	// Initialise stack extents and GC heap.

0 commit comments

Comments

0 (0)