Well, that's one to remember.:)
On 15 January 2014 16:44, skeezix <[email protected]> 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? I.e
> # Interrupt on what, does it auto clear etc.
>
> uuuugh; any way to stop this?
>
> clive just sent a post:
>
> https://my.st.com/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Flat.aspx?RootFolder=/public/STe2ecommunities/mcu/Lists/cortex_mx_stm32/Problem%20with%20DMA-USART%20Rx%20on%20STM32F407VG&FolderCTID=0x01200200770978C69A1141439FE559EB459D7580009C4E14902C3CDE46A77F0FFD06506F5B¤tviews=148
>
> Reading that, it just sounds like an internal race condition that
> ther eis basicly nothing you can do about, except adding some NOPs or
> _something_ in the handler. If the handler is 'too trivial', there'll be
> timing issues and you get spurious callback.. what I'm seeing likely.
>
> So .. make sure your interupt handlers do something slightly
> heavier than a feather.
>
> Damn, thats not a fun resolution to multiple days of banging
> head on data sheets :(
>
> jeff
>
> --
> If everyone would put barbecue sauce on their food, there would be no war.
>
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
libopencm3-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libopencm3-devel
