CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.8.6 2016-08-22T02:24:49+00:00 2016-08-22T02:24:49+00:00 Damien George damien.p.george@gmail.com 2016-08-22T02:24:49+00:00 urn:sha1:d2d9dfcd40caafa99177ca36bd3e3faf52ee05b3 TIM3 is no longer special, or at least does not have special IRQ settings. 2016-08-22T02:18:04+00:00 Dave Hylands dhylands@gmail.com 2016-08-19T03:47:49+00:00 urn:sha1:c6983e3ce0bb9708afabb9fb7cbdf54ba46fb594 It turns out that TIM1 and TIM8 have their own Capture/Compare interrupt vector. For all of the other timers, the capture/compare interrupt vector is the same as the update vector. So we need to add handlers for these vectors and enable them when using capture/compare callbacks. During testing of this, I also found that passing a channel callback into the channel constructor would not enable interrupts properly. I tested using: ``` >>> pyb.Timer(1, freq=4).channel(1, pyb.Timer.OC_TOGGLE, callback=lambda t: print('.', end='')) ``` I tested the above with channels 1, 4, and 8 2016-04-17T11:16:13+00:00 Tobias Badertscher python@baerospace.ch 2016-03-22T16:07:43+00:00 urn:sha1:31f5dc065a6feb3205495f8b096aec9ebb0ccc5d 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. 2016-01-29T22:31:56+00:00 Damien George damien.p.george@gmail.com 2016-01-29T22:31:56+00:00 urn:sha1:ea89b80ff4f842b010f9f8ec3280675f81bc6bc5 TIM3 is no longer used by USB CDC for triggering outgoing data, so we can now make it available to the user. PWM fading on LED(4) is now gone, but will be reinstated in a new way. 2016-01-29T15:21:43+00:00 Damien George damien.p.george@gmail.com 2016-01-09T21:59:15+00:00 urn:sha1:d3631339176b768ce1ffdc535223385245ff906b Previous to this patch the USB CDC driver used TIM3 to trigger the sending of outgoing data over USB serial. This patch changes the behaviour so that the USB SOF interrupt is used to trigger the processing of the sending. This reduces latency and increases bandwidth of outgoing data. Thanks to Martin Fischer, aka @hoihu, for the idea and initial prototype. See PR #1713. 2016-01-11T00:49:27+00:00 Damien George damien.p.george@gmail.com 2016-01-03T15:55:55+00:00 urn:sha1:5b3f0b7f39bd67cc9182993c288f09f67a0890df The first argument to the type.make_new method is naturally a uPy type, and all uses of this argument cast it directly to a pointer to a type structure. So it makes sense to just have it a pointer to a type from the very beginning (and a const pointer at that). This patch makes such a change, and removes all unnecessary casting to/from mp_obj_t. 2015-12-09T17:39:34+00:00 Damien George damien.p.george@gmail.com 2015-12-09T17:39:34+00:00 urn:sha1:f54a96d6a20df998eb70a5cffe63f5ea885595c8 This way mp_float_t can be changed to, eg, double. 2015-12-04T14:07:15+00:00 Damien George damien.p.george@gmail.com 2015-12-04T14:07:15+00:00 urn:sha1:66b96822fb33863fde5ce13a6bdeb99a404575dc This is a hack to free up TIM3 so that it can be used by the user. Instead we use the PVD irq to call the USB VCP polling function, and trigger it from SysTick (so SysTick itself does not do any processing). The feature is enabled for pyboard lite only, since it lacks timers. 2015-11-24T16:18:07+00:00 Damien George damien.p.george@gmail.com 2015-11-24T16:18:07+00:00 urn:sha1:e99e6c883d70eda894aba124c8ee0495dc90c350 Using SysTick to do the counting and dispatch of the flash storage idle handler is more efficient than requiring a dedicated hardware timer. No new counter is needed, just the existing uwTick variable. The processing is not actually done in the SysTick IRQ, it is deferred to the flash IRQ (which runs at lower priority).