Bruce
Wed May 14 10:09:45 PDT 2008
You should check the BSP and your application to see if there is anywhere
else that is writing to either OSMR0 or OSCR. Writing either could cause
this.
--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
EuroTech Inc.
www.EuroTech.com
"Chris Tacke, eMVP" <ctacke.at.opennetcf.dot.com> wrote in message
news:%23aOUghdtIHA.5580@TK2MSFTNGP04.phx.gbl...
> The 19 minute timing is very, very indicative of a clock/register rollover
> relation, at it take about 19 minutes to roll a 32-bit register that is
> incrementing once a milliseconds. So you at least have a clue as to what
> type of thing to look for. The fact that it doesn't stop dead, but slows
> down indicates it's probably not the bug Bruce (and probably everyone
> else) thought, but instead something else tangentially related to a
> clock - meaning much more difficult to find. I hope you got BSP support
> from the vendor, as I'd certainly push this back on them as a bug. Happy
> hunting.
>
>
> --
>
> Chris Tacke, Embedded MVP
> OpenNETCF Consulting
> Giving back to the embedded community
>
http://community.OpenNETCF.com
>
>
> "Martin" <Martin@discussions.microsoft.com> wrote in message
> news:84F5F589-DC67-4B2B-8B58-0A71864D1BB0@microsoft.com...
>> Hallo Bruce,
>>
>> -stubbing OALCPUIdle {} and OEMIdle {} had no positive effect.
>> -adding INTERRUPTS_OFF(); ..... INTERRUPTS_ON(); in ARMTimerISR
>> had no positive effect.
>> -I encountered a FREEZE: -with the mouse I could open more windows, but
>> slower and slower til nothing happend anymore...and after about 20minutes
>> all
>> recovered.
>> -> there must be another hanger which affects not all tasks....
>>
>> regards: Martin
>
>