freeRTOS - Reduce BLE thread blocking time

[Dave_couling]

Hi,

I'm currently running a BLE thread which is sample the SAADC at 100hz. I'm also sending out notifications with the ADC values at 100Hz.

On a separate thread I'm running a sensor state machine, polling an accelerometer also at 100hz.

I'm finding (with the use of a local watchdog) that the Sensor Thread is often blocked for more than 50msec at a time, but the BLE thread. So I'm losing large chunks of Sensor Data.

I'm sampling 3 channels on the SAADC with no Oversampling @ 20usec acq time. I didn't really think this would block the Sensor thread, but it appears so. Is there any ways I can reduce the up-time of the BLE thread to allow for more processing time for the Sensors?

FYI, BLE thread priority is 5, Sensor thread is 4. Making them the same priority didn't really help.

[Susheel Nuguru]

I do not think BLE thread should take upto 50ms , but the softdevice could take if you doing some flash activity. Based on the description you gave it is hard to say, what is blocking your sensor thread. Maybe more code or adding your project here might help. 50ms is very large blocking time if there is no flash activity. Maybe you can use SEgger SystemView to get more data which task is blocking what. www.segger.com/.../

some helpful link mcuoneclipse.com/.../