suspect-devices/circuitpython/shared-bindings/time/__init__.h, branch 5.3.x CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=5.3.x 2020-02-07T15:02:50+00:00 improve time.monotonic_ns() accuracy from ms to us 2020-02-07T15:02:50+00:00 Dan Halbert halbert@halwitz.org 2020-02-07T15:02:50+00:00 urn:sha1:857d8ab40a6e4ef7d0cc78f481511070c1af15e3 Add rtc module 2018-04-16T10:49:10+00:00 Noralf Trønnes noralf@tronnes.org 2018-04-07T13:00:13+00:00 urn:sha1:8d1719f190f249ebb0e53c4f42a81d7fc16f4e00 Add an rtc module that provides a singleton RTC class with - a datetime property to set and get time if the board supports it. - a calbration property to adjust the clock. There's also an rtc.set_time_source() method to override this RTC object using pure python. The time module gets 3 methods: - time.time() - time.localtime() - time.mktime() The rtc timesource is used to provide time to the time module. lib/timeutils is used for time conversions and thus only supports dates after 2000. Initial merge of micropython v1.9.2 into circuitpython 2.0.0 (in development) master. 2017-08-26T02:17:07+00:00 Dan Halbert halbert@halwitz.org 2017-08-26T02:17:07+00:00 urn:sha1:ef61b5ecb59e9b4e37e3e3c023c62d583c23eb16 cpx build compiles and loads and works in repl; test suite not run yet esp8266 not tested yet This introduces an alternative hardware API called nativeio structured around different functions that are typically accelerated by native hardware. Its not meant to reflect the structure of the hardware. 2016-11-21T22:11:52+00:00 Scott Shawcroft scott@chickadee.tech 2016-11-03T22:50:59+00:00 urn:sha1:ccbb5e84f980e252f7380d96fcc5c417a8a64523 Docs are here: http://tannewt-micropython.readthedocs.io/en/microcontroller/ It differs from upstream's machine in the following ways: * Python API is identical across ports due to code structure. (Lives in shared-bindings) * Focuses on abstracting common functionality (AnalogIn) and not representing structure (ADC). * Documentation lives with code making it easy to ensure they match. * Pin is split into references (board.D13 and microcontroller.pin.PA17) and functionality (DigitalInOut). * All nativeio classes claim underlying hardware resources when inited on construction, support Context Managers (aka with statements) and have deinit methods which release the claimed hardware. * All constructors take pin references rather than peripheral ids. Its up to the implementation to find hardware or throw and exception.