CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.2.0-beta.2 2021-01-26T13:37:05+00:00 2021-01-26T13:37:05+00:00 Dan Halbert halbert@halwitz.org 2021-01-26T13:37:05+00:00 urn:sha1:da6869dbd5366c0f3d186b32a2b058585b0c5192 2021-01-26T03:40:31+00:00 Dan Halbert halbert@halwitz.org 2021-01-26T03:40:31+00:00 urn:sha1:a9f339b4619a55cf5748124180e43afca32d8fb7 2021-01-25T04:10:20+00:00 Dan Halbert halbert@halwitz.org 2021-01-25T03:49:28+00:00 urn:sha1:69869e1439a1ebad383b75b28e7e88f21ccab732 2021-01-21T18:18:04+00:00 Scott Shawcroft scott@tannewt.org 2021-01-21T18:18:04+00:00 urn:sha1:b7a63dc4980808e5f9716c1851a015ae65a16eb7 2021-01-21T03:16:56+00:00 Scott Shawcroft scott@tannewt.org 2021-01-21T00:47:18+00:00 urn:sha1:733094aead6e84b42da54655b2b0a5d0dbd1a503 The RP2040 is new microcontroller from Raspberry Pi that features two Cortex M0s and eight PIO state machines that are good for crunching lots of data. It has 264k RAM and a built in UF2 bootloader too. Datasheet: https://pico.raspberrypi.org/files/rp2040_datasheet.pdf 2021-01-05T19:19:11+00:00 iot49 49917707+iot49@users.noreply.github.com 2021-01-05T19:19:11+00:00 urn:sha1:1a82555803ab66bdb608508fccbcc9acc9bac657 2020-12-17T19:04:56+00:00 microDev 70126934+microDev1@users.noreply.github.com 2020-12-17T19:04:56+00:00 urn:sha1:4863413bc9aa3104f2c983efa43bf3afa028b80b 2020-12-11T23:55:46+00:00 microDev 70126934+microDev1@users.noreply.github.com 2020-12-11T23:55:46+00:00 urn:sha1:37ee5e683deb26ee691090d4f51b0ade4fa9b61c 2020-12-11T19:10:30+00:00 Scott Shawcroft scott@adafruit.com 2020-12-11T19:10:30+00:00 urn:sha1:344d3c59cba516aac28f6c7db4189d80b2bfb49d 2020-12-08T18:52:25+00:00 Scott Shawcroft scott@tannewt.org 2020-12-03T02:05:29+00:00 urn:sha1:40118bcf57f026fd6a58733501c759a9ba87e835 This changes lots of files to unify `board.h` across ports. It adds `board_deinit` when CIRCUITPY_ALARM is set. `main.c` uses it to deinit the board before deep sleeping (even when pretending.) Deep sleep is now a two step process for the port. First, the port should prepare to deep sleep based on the given alarms. It should set alarms for both deep and pretend sleep. In particular, the pretend versions should be set immediately so that we don't miss an alarm as we shutdown. These alarms should also wake from `port_idle_until_interrupt` which is used when pretending to deep sleep. Second, when real deep sleeping, `alarm_enter_deep_sleep` is called. The port should set any alarms it didn't during prepare based on data it saved internally during prepare. ESP32-S2 sleep is a bit reorganized to locate more logic with TimeAlarm. This will help it scale to more alarm types. Fixes #3786