CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=esp-extra-scripts 2016-05-13T10:01:21+00:00 2016-05-13T10:01:21+00:00 Damien George damien.p.george@gmail.com 2016-05-13T10:01:21+00:00 urn:sha1:1dc2862a837a08c6aa96fb369657be21043015ad This allows PYBv3 to use PWM for LED(1) and LED(2). 2016-03-07T11:28:36+00:00 Pavol Rusnak stick@gk2.sk 2016-02-03T16:45:38+00:00 urn:sha1:ce3beb1672a890726902988c4e9184ec6cf3e902 To make it easier to spot differences. 2016-02-06T13:07:01+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-02-06T12:48:58+00:00 urn:sha1:97a0846af906cde677742bff810fb7965c38fbb7 To allow to reuse stmhal/diskio for ports which don't have flash but have other storage devices. 2016-01-29T22:44:43+00:00 Damien George damien.p.george@gmail.com 2016-01-29T22:44:43+00:00 urn:sha1:a8a4b01af6501ff7ab61b251fc30fcf8a286f8d1 USB CDC no longer needs TIM3 (which was originally used for LED(4) PWM) and so TIM3 has been freed for general purpose use by the user. Hence LED(4) lost its PWM capabilities. This patch reinstates the PWM capabilities using a semi-generic piece of code which allows to configure a timer and PWM channel to use for any LED. But the PWM capability is only configured if the LED is set to an intensity between 1 and 254 (ie only when needed). In that case the relevant timer is configured for PWM. It's up to the user to make sure the timers are not used if PWM is active. This patch also makes sure that PWM LEDs are turned off using standard GPIO when calling led.off() or led.intensity(0), instead of just setting the PWM counter to zero. 2015-12-12T15:02:02+00:00 Damien George damien.p.george@gmail.com 2015-12-12T15:02:02+00:00 urn:sha1:f7c4f9a64048bcbeaf36be8590b352bbef72aa08 Previously, SPI was configured by a board defining MICROPY_HW_ENABLE_SPIx to 0 or 1. Now, the board should define MICROPY_HW_SPIx_SCK, MISO, MOSI and NSS. This makes it the same as how I2C is configured. 2015-12-09T09:56:36+00:00 neilh10 neilh20@wLLw.net 2015-12-08T22:02:34+00:00 urn:sha1:1be0fde45c8d84eaf04851af96f06aad8171b2b2 This is refactoring to enable support for the two USB PHYs available on some STM32F4 processors to be used at the same time. The F405/7 & F429 have two USB PHYs, others such as the F411 only have one PHY. This has been tested separately on a pyb10 (USB_FS PHY) and F429DISC (USB_HS PHY) to be able to invoke a REPL/USB. I have modified a PYBV10 to support two PHYs. The long term objective is to support a 2nd USB PHY to be brought up as a USB HOST, and possibly a single USB PHY to be OTG. 2015-11-23T23:23:07+00:00 T S tsp@esg-workstation.com 2015-11-07T11:03:12+00:00 urn:sha1:86aa16bea61da8a8d156a7a928902a0bf4c85b73 If RTC is already running at boot then it's left alone. Otherwise, RTC is started at boot but startup function returns straight away. RTC startup is then finished the first time it is used. Fallback to LSI if LSE fails to start in a certain time. Also included: MICROPY_HW_CLK_LAST_FREQ hold pyb.freq() parameters in RTC backup reg MICROPY_HW_RTC_USE_US option to present datetime sub-seconds in microseconds MICROPY_HW_RTC_USE_CALOUT option to enable RTC calibration output CLK_LAST_FREQ and RTC_USE_CALOUT are enabled for PYBv1.0. 2015-10-29T22:40:42+00:00 Damien George damien.p.george@gmail.com 2015-10-29T22:40:42+00:00 urn:sha1:6f70283909a718ca4eab4efcdd1a2d74939c7193 2015-08-07T07:54:14+00:00 Dave Hylands dhylands@gmail.com 2015-08-06T07:03:45+00:00 urn:sha1:872f9af6aed49fa088d89152b983506285e1d34b This needs to land afte #1407 lands, since #1407 is where the CMSIS_MCU was defined. 2015-08-07T07:46:43+00:00 Dave Hylands dhylands@gmail.com 2015-08-02T17:42:09+00:00 urn:sha1:be66a9ecf60eac18e08eda7bddf4b3481459c9f2 This causes unnecessary constants to no longer be generated. Some constants (like UART_BRR) are different between the F4 and F7