CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.2.x 2021-03-15T13:57:36+00:00 2021-03-15T13:57:36+00:00 microDev 70126934+microDev1@users.noreply.github.com 2021-03-15T13:57:36+00:00 urn:sha1:a52eb88031620a81521b937f2a0651dbac2bb350 2021-03-12T02:02:07+00:00 Dan Halbert halbert@halwitz.org 2021-03-12T02:02:07+00:00 urn:sha1:fa34b8a40475724a7072ba85b05415c607915b19 2020-10-26T21:44:38+00:00 Christian Walther cwalther@gmx.ch 2020-10-24T15:50:11+00:00 urn:sha1:99a3750a2cfd1da8cdd266ca9a0367f0c3a54092 After calling board.SPI().deinit(), calling board.SPI() again would return the unusable deinited object and there was no way of getting it back into an initialized state until the end of the session. 2020-10-26T21:44:38+00:00 Christian Walther cwalther@gmx.ch 2020-10-24T15:23:17+00:00 urn:sha1:f4f80e07ca3dc2f5a93484e5342540837a94a505 Fixes #3581. Pins were marked as never_reset by common_hal_displayio_fourwire_construct() and common_hal_sharpdisplay_framebuffer_construct(), but these marks were never removed, so at the end of a session after displayio.release_displays(), {spi|i2c}_singleton would be set to NULL but the pins would not be reset. In the next session, board.SPI() and board.I2C() were unable to reconstruct the object because the pins were still in use. For symmetry with creation of the singleton, add deinitialization before setting it to NULL in reset_board_busses(). This makes the pins resettable, so that reset_port(), moved behind it, then resets them. 2020-10-26T21:44:38+00:00 Christian Walther cwalther@gmx.ch 2020-10-24T15:13:10+00:00 urn:sha1:1117edae63df7b66f1575980bf54d6836f9a8aa8 At the end of a session that called displayio.release_displays() (and did not initialize a new display), a board.I2C() bus that was previously used by a display would wrongly be considered still in use. While I can’t think of any unrecoverable problem this would cause in the next session, it violates the assumption that a soft reboot resets everything not needed by displays, potentially leading to confusion. By itself, this change does not fix the problem yet - rather, it introduces the same issue as in #3581 for SPI. This needs to be solved in the same way for I2C and SPI. 2020-09-30T19:57:39+00:00 Scott Shawcroft scott@tannewt.org 2020-09-29T20:04:39+00:00 urn:sha1:a739d314f1a9f5fee6517eb425a2c691969fd7f7 Also fix two bugs: * Crash when resetting board.SPI when it hasn't been inited. * Reading back the output value is always false. Fixes #3353 2020-09-25T18:07:22+00:00 Scott Shawcroft scott@tannewt.org 2020-09-25T18:07:22+00:00 urn:sha1:b9d68bc5a6b7b63f52da6c7034d379d6de51be7e Greater that 100khz is technically out of the original spec. Background here: https://github.com/adafruit/Adafruit_CircuitPython_CLUE/issues/36 2020-09-11T15:54:46+00:00 root siehputz@gmail.com 2020-09-11T15:54:46+00:00 urn:sha1:870326b2218e24a20f40c8ee72f3ec27d0f3813b 2020-09-09T15:36:55+00:00 root siehputz@gmail.com 2020-09-09T15:36:55+00:00 urn:sha1:59165cabbe1c27260678c4e252465b11e1cf8c0e 2020-09-09T14:32:25+00:00 root siehputz@gmail.com 2020-09-09T14:32:25+00:00 urn:sha1:24a18c63f9d3990661cc58888896faba9c8fad50