We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
We are using MDK V5.26.2.0 with STM32F429 running at 168MHz. We have set up Event Recording which is working well with DWT Cycle Counter, except for the timestamps and deltas calculated in view Event Recorder & Statistics.
According to EventBuffer, the difference for a StartA/StopA event is 5252 cylces and in the Event Statistics view it is displayed as 525,20us (as if the wrong frequency is used for calculation, 10MHz instead of 168MHz).
We already verified, that the frequency in EventStatus.ts_freq is set correctly to 168000000.
best regards, Gregor
Just found out, that the Debug -> Trace -> Core Clock is used as frequency for time calculation, which of course is per default not the same as used in the project!
This should be mentioned in documentation or corrected in uVision!
>> or corrected in uVision! uVision doesn't know what speed you're running the processor at, that's why there's a dialog item for you to put it in.
@Westonsupermare Pier: You are wrong! As you can read in my first post about this issue, EventRecorder stores the SystemCoreClock in structure EventStatus.ts_freq! So therefor uVision does quiet well know the speed of the processor.