micropython / micropython-esp32

Old port of MicroPython to the ESP32 -- new port is at https://github.com/micropython/micropython
MIT License
669 stars 216 forks source link

Implemented deepsleep, reset_cause and rtc functions memory, string a… #224

Closed smeenka closed 6 years ago

smeenka commented 6 years ago

From sha2017 (https://github.com/SHA2017-badge/micropython-examples-sha2017.git) I merged some stuff back into this repository.

module function status remark
machine reset issue on reboot unhandled exception
machine reset_cause OK
machine deepsleep OK stop processor and wakeup in n milliseconds
machine lightsleep issue on wakeup an exception. See https://github.com/espressif/esp-idf/issues/1024
machine RTC OK fetch RTC module
machine.RTC memory OK read/write one byte to RTC memory
machine.RTC string OK read/write a string to RTC memory
machine.RTC datetime OK read/write the current date tuple
smeenka commented 6 years ago

example usage for rtc.datetime(): import ntptime,time from machine import RTC as rtc t = ntptime.time() tm = time.localtime(t) rtc.datetime(tm)

MrSurly commented 6 years ago

@smeenka Much of SHA2017 deep sleep code was originally from this PR: https://github.com/micropython/micropython-esp32/pull/85, which is still pending.

nubcore commented 6 years ago

I've just tested the rtc functionality, which is looking good and #85 is now closed, anything in particular still holding this up?

MrSurly commented 6 years ago

@nubcore https://github.com/micropython/micropython/pull/3531

nubcore commented 6 years ago

@MrSurly thanks for the info and contribution! Is active developmed for esp32 still micropython-esp32, or did I miss a memo a couple months back and it now is all happening directly in micropython/ports/esp32?

aykevl commented 6 years ago

@nubcore The work continues on the main micropython repo, see https://github.com/micropython/micropython-esp32/issues/233

nickzoic commented 6 years ago

Hi yep, we did a switch over to the main repo now and this repo is really still just here for historical purposes. I'm going to push some changes to the README to clarify this, because while it was discussed at the time, we don't really expect everyone on the internet to watch the state of the project 24/7 :-) I'm making a start on reviewing some of the open PRs today ...

dpgeorge commented 6 years ago

All of this functionality is now merged in the upstream repo.