This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Soft device locks the processor for 250 micro seconds

Central : nrf52840
Peripheral: nrf52840
softdevice: s140 5.0.0.2 alpha
ATT_MTU size: 52
Connection event extension: enabled
DLE: ATT_MTU size + 4
Connection Interval: 10ms

I have a data acquisition unit at the peripheral(Tx) which has to be processed for every 40 micro seconds(needs the processor). But the issue is that the processor is locked may be by the soft device as per the documentation on "s132_SDS_v5.0 interrupt model and processor availability "where the processing at the end of a connection event could be of 250micro seconds max. I doubt if this is causing the delay in the samples at the receiver end. When I replace the data acquisition unit with other data values, the link is good. So, I doubt if this locking causing this problem. Looking for an alternate solution.

Thank you, Nivetha

Parents
  • Thanks, Peter, I put it in a better way. At the transmitter, I have a data acquisition element(basically like a sensor unit with amplifiers and ADC, DAC etc.) It will be collecting samples and process it on nrf 52840 which has its Bluetooth stack running. The issue here is the sensor element needs the processor every 40 micro seconds but looks like after every connection event (from the documentation), the soft device will lock the processor for maximum for 250 microseconds. Is my assertion right? Should i set a high priority interrupt or something so that processor will be available to process this sensor element interrupt every 40 micro seconds? The consequence of which I am unable to see the data at the receiver end properly.

Reply
  • Thanks, Peter, I put it in a better way. At the transmitter, I have a data acquisition element(basically like a sensor unit with amplifiers and ADC, DAC etc.) It will be collecting samples and process it on nrf 52840 which has its Bluetooth stack running. The issue here is the sensor element needs the processor every 40 micro seconds but looks like after every connection event (from the documentation), the soft device will lock the processor for maximum for 250 microseconds. Is my assertion right? Should i set a high priority interrupt or something so that processor will be available to process this sensor element interrupt every 40 micro seconds? The consequence of which I am unable to see the data at the receiver end properly.

Children
No Data
Related