CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=4.0.0-beta.0 2019-01-20T00:45:35+00:00 2019-01-20T00:45:35+00:00 Dan Halbert halbert@halwitz.org 2019-01-20T00:45:35+00:00 urn:sha1:28cfd8a5135a1e420b56d693cef20fc1a4721081 2019-01-15T01:29:19+00:00 Scott Shawcroft scott@tannewt.org 2019-01-15T01:26:36+00:00 urn:sha1:747f2cfe267628fda8487c533ce7a5ab10a9388f Also, swap make_news to accept a kwarg map and refine param checking. Fixes #1237 2018-12-04T20:05:39+00:00 Dan Halbert halbert@halwitz.org 2018-12-04T20:05:39+00:00 urn:sha1:63cd9209f17c6807e96e5011c5dca9862d67da58 2018-12-03T17:04:32+00:00 Dan Halbert halbert@halwitz.org 2018-12-03T16:00:35+00:00 urn:sha1:80db2cec99ca5c995a0302b1d6d00ad77cfcd736 2018-09-18T19:38:12+00:00 Dan Halbert halbert@halwitz.org 2018-09-18T19:38:12+00:00 urn:sha1:bc510e714f4fde7af949c525ced5c8a4db53bce0 2018-09-12T21:19:43+00:00 Dan Halbert halbert@halwitz.org 2018-09-12T21:19:43+00:00 urn:sha1:6a046f55c449da59cf4641ef4cf34c6b1b63da44 2018-08-09T00:21:57+00:00 Jeff Epler jepler@gmail.com 2018-07-31T01:49:20+00:00 urn:sha1:e1b4e9b7c7cdd7a022a5ab113b68c8fa6be2c74d Particularly when they have buffers that are written via IRQ or DMA, UART objects do not relocate gracefully. If such an object is relocated to the long-lived pool after its original creation, the IRQ or DMA will write to an unexpected location within the Python heap, leading to a variety of symptoms. The most frequent symptom is inability to read from the UART. Consider the particular case of atmel-samd: usart_uart_obj_t contains a usart_async_descriptor contains a _usart_async_device. In _sercom_init_irq_param the address of this contained _usart_async_device is assigned to a global array sercom_to_sercom_dev which is later used from the interrupt context _sercom_usart_interrupt_handler to store the received data in the right ring buffer. When the UART object is relocated to the long-lived heap, there's no mechanism to re-point these internal pointers, so instead take the cowardly way and allocate the UART object as long-lived. Happily, almost all UART objects are likely to be long-lived, so this is unlikely to have a negative effect on memory usage or heap fragmentation. Closes: #1056 2018-08-07T21:58:57+00:00 Scott Shawcroft scott@tannewt.org 2018-07-31T23:53:54+00:00 urn:sha1:933add6cd833bb6ba6682ad2b6eb478871415ff5 2018-02-21T22:18:49+00:00 Dan Halbert halbert@halwitz.org 2018-02-21T21:30:26+00:00 urn:sha1:9b4477e1dc088d18127838310b828514cb33edea 1. UART: ported to ASF4. Allow rx-only and tx-only. Add .baudrate r/w property. 2. Make NeoPixel timing deterministic by turning off caches during NeoPixel writes. 3. Incorporate asf4 updates: a. async USART driver b. bringing Atmel START configuration closer to what we use c. Clock initialization order now specified by CIRCUITPY_GCLK_INIT_1ST and _LAST. 4. supervisor/port.c: Move commented-out clock-test pin setting to correct location. 2017-10-03T19:07:17+00:00 Dan Halbert halbert@halwitz.org 2017-10-03T00:49:40+00:00 urn:sha1:c478c10923b9085b2abe135470e968029aaf2fdb Fixes #278, #277, #276, #275.