RE: execution profiling

paul — Wed, 24 Apr 2019 05:15:17 GMT

hi Edvin,

In trying to resolve this I simplified the code down. The for loop is not timer/interrupt driven - just normal flow of execution. It should enter the third if statement every 20ms unless something that is timer/interrupt driven is taking a long time. The flex_debugdata call simply writes that value - lastTime_ - startTime to a characteristic for debug purposes. It should be 20. However at steady state it is 37 - 38 hence the 17 to 18 ms lost.

I finally found where this extra time was going. Seems I had a couple of SDH logs enabled. With these switched off, the measurement timing comes back to 51.2hz or ~20ms

Thanks for your help

Paul

RE: execution profiling

Edvin — Tue, 23 Apr 2019 14:20:55 GMT

Hello Paul,

It is a bit difficult to say without knowing what you do inside your flex_DebugData(), and what other tasks your application is doing. Is there any more relevant information you can share?

[quote user=""]While in the loop there are a steady stream of writes to a service characteristic. [/quote]

Where are you sending data over BLE?

Without knowing anything about your application, from a power consumption point of view, it doesn't look like you ever let your chip go to sleep. I don't know whether this is a concern for you.

Best regards,

Edvin