On Wed, 15 Jan 2014, Donald E Haselwood wrote:
# the bus to stall until the previous operation (the write to clear the
# flag) has completed.
#
# For example,
# void SPI2_IRQHandler(void)
# {
# volatile unsigned int dummy;
# ... some code...
# SPI2_CR2 &= ~SPI_CR2_RXNEIE;// Tur
Jeff,
I only skimmed the previous posts so maybe I've missed a nuance, but the
way to avoid tail-chaining is just before the ISR 'return' re-read the
register that was written to clear the interrupt flag. The read causes
the bus to stall until the previous operation (the write to clear the
flag)
Hi
I've knocked up some boilerplate docs for the flash programming modules
in the STM32 families, without changing any code. Once that is merged
I'd like to fiddle the code a bit, mainly to de-duplicate the F0/F1/L1
modules which seem to have a fair bit in common.
Just a couple of points needi
Well the timing of the CPU clock affects the timing of the AHB and APB
clocks but they aren't 1 for 1. One of the things that has bitten me a
couple times is that APB1 and APB2 have different clocks and setting
baud rates for USARTS on them needs to know which clock to use.
On Wed, Jan 15, 2014 at
Take a look at the TILM4F launchpad too. It runs at 80MHz and has floating
point also.
On 15 January 2014 17:53, skeezix wrote:
> On Wed, 15 Jan 2014, Frank Duignan wrote:
>
> # There are a number of options available to Tim2 - A good read of the
> reference guide is required. Alternatively,
On Wed, 15 Jan 2014, Frank Duignan wrote:
# There are a number of options available to Tim2 - A good read of the
reference guide is required. Alternatively, if you just want a periodic
interrupt why not use systick - it is
# much simpler (doesn't even require ack'ing the irq)
For the pr
Well, that's one to remember.:)
On 15 January 2014 16:44, skeezix wrote:
> On Wed, 15 Jan 2014, Frank Duignan wrote:
>
> # More likely the interrupt is tail-chaining (re-entering immediately) and
> this is happening so quickly that the port has no time to react. What mode
> is the timer set to
There are a number of options available to Tim2 - A good read of the
reference guide is required. Alternatively, if you just want a periodic
interrupt why not use systick - it is much simpler (doesn't even require
ack'ing the irq)
f.
On 15 January 2014 16:24, skeezix wrote:
> On Wed, 15 Jan 201
On Wed, 15 Jan 2014, Frank Duignan wrote:
# More likely the interrupt is tail-chaining (re-entering immediately) and this
is happening so quickly that the port has no time to react. What mode is the
timer set to? I.e
# Interrupt on what, does it auto clear etc.
gh; any way to stop
On Wed, 15 Jan 2014, Frank Duignan wrote:
# More likely the interrupt is tail-chaining (re-entering immediately) and this
is happening so quickly that the port has no time to react. What mode is the
timer set to? I.e
# Interrupt on what, does it auto clear etc.
The entirety of the timer set u
More likely the interrupt is tail-chaining (re-entering immediately) and
this is happening so quickly that the port has no time to react. What mode
is the timer set to? I.e Interrupt on what, does it auto clear etc.
f.
On 15 January 2014 15:49, skeezix wrote:
> On Wed, 15 Jan 2014, skeezix wr
On Wed, 15 Jan 2014, skeezix wrote:
# Continuing the hunt ..
Newest finding..
If I twiddle the isr function around a bit, and make it _last
longer_, everything is peachy. Of note:
void tim2_isr ( void ) {
TIM_SR(TIM2) &= ~TIM_SR_UIF; /* Clear interrrupt flag. */
uns
On 01/15/14 00:48, skeezix wrote:
> Sorry to have taken over the mailing list, but it seemed quiet,
> thought I'd liven it up. Is this in fact an appropriate topic for the
> mailing list here, or should I take it elsewhere?
>
I think this thread is perfect for this list, much more interest
13 matches
Mail list logo
