RE: ncs1.5.0 and nrf5340 board ,GPIOE interrupt every 4ms ECG data ready, but 30ms can read one time

Simon — Mon, 26 Jul 2021 13:41:38 GMT

It's a little hard to know exactly what's causing this without being able debug your application and without having access to the ADS129 sensor. I assume there are some other threads running in the background causing the delay. The thread aware debugging feature that comes with Ozone may help you figure out the cause: Thread aware debugging with nRF Connect SDK

I created a simple sample where I triggered a timer every 4ms and woke up a custom thread using a semaphore. I then toggled a GPIO (as well as using LOG_INF()) in the custom thread to see if ran every 4ms, and it did indeed:

Can you test out the same sample in NCS v1.6.0 using nrf5340dk_nrf5340_cpuapp? First with the timer, and then you swap it out the timer with the sensor interrupt.

devzone.nordicsemi.com/.../semaphore_5F00_timing.zip

Is there a reason you're logging all the data? Logging every 4ms corresponds to 250 logs each second. By the way, I don't think it should affect the timing since it has a very low priority.