Re: CETK -> RTC Latency/Resolution (high priority)

Don't really sure that I have any RTC related bug
since the test result is "PASSED". However
I can see a zillion calls to the OEMGetRealTime
routine and system looks frozen during the test
since I think there are some "dead loops" like
the following one inside the

timerabstraction.cpp -> getLatencyAndResolutionOnce(...)

.....

/* loop until we get an error or the time changes */
while (((bGetTickReturnVal = (*timer->getTick)(ullStartTime)) == TRUE) &&
(ullStartTime == ullEndTime))
{
}

.....

Have no ideas by now, I'll try Your suggestion with a custom application.
Thanks.


"Steve Maillet (eMVP)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:#r2vGRATFHA.3344@xxxxxxxxxxxxxxxxxxxxxxx
> We have run that test. Although there are problems with it on numerous
CPUs,
> I haven't seen that particular set of symptoms. You could try extracting
the
> test code (it's pretty simple) into a separate application and step
through
> it to see what is happening. Most likely there is a bug in your OAL code
> causing this [But not necessarily!]
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>


.