52832 saadc calibration issue

RE: 52832 saadc calibration issue

BEN_HB — Fri, 01 Nov 2019 06:13:14 GMT

Thank you

RE: 52832 saadc calibration issue

Jared — Thu, 31 Oct 2019 13:53:43 GMT

Hi,

It should be ok for S332.

regards

Jared

RE: 52832 saadc calibration issue

BEN_HB — Thu, 31 Oct 2019 10:05:36 GMT

I use S332. Is it also no issue?

RE: 52832 saadc calibration issue

Jared — Thu, 31 Oct 2019 09:28:56 GMT

Hi,

I understand that it might be difficult to move it on your application. If you're using Softdevice S132 then you could move the priority of the SAADC interrupt to 5.

regards
Jared

RE: 52832 saadc calibration issue

BEN_HB — Thu, 31 Oct 2019 07:34:53 GMT

thank you. the calibration func is called from app_timer handler. the timer is called per 30min. and it can't move main thread.

RE: 52832 saadc calibration issue

Jared — Wed, 30 Oct 2019 12:27:53 GMT

Hi,

What context are you calling the calibration task from? Meaning, are you calling it from an interrupt handler or from the main thread? If you are calling it from the interrupt handler, could you try to move it to the main thread?

regards

Jared

RE: 52832 saadc calibration issue

BEN_HB — Wed, 30 Oct 2019 01:24:03 GMT

Thank you. 'you try to change the context that you're calling the function from '<- what is meaning?

I don't know what interrupt conflict with. how do I check?

in code, ant 2 channels, ble , gpiote, saadc, rtc, apptimer is operating...

I didn't change any priority of above function.

while(CaliState){
NRF_LOG_INFO("SAADC is waiting");
NRF_LOG_PROCESS();
}

if it remove this code, the calibration done event is appear little bit later.

the infinite loop is disturb that calibration event done appear?

Is it too fast working to generate saadc event?

thank you so much

RE: 52832 saadc calibration issue

Jared — Tue, 29 Oct 2019 10:16:48 GMT

Hi,

It's generally a good idea to keep all application tasks priority higher then the Softdevice priorities[ 1-5]. For very critical interrupts where low latency is required you can use 2+3 but then you cannot use any SVC. Instead of increasing the interrupt priority I would rather suggest that you try to change the context that you're calling the function from. Which interrupt is the saadc interrupt conflicting with? A softdevice interrupt?

Jared

RE: 52832 saadc calibration issue

BEN_HB — Tue, 29 Oct 2019 08:10:20 GMT

Sorry to late repy. you are right. problem is priority.

I change 6 -> 5. the issue disappered.

i have one more question.

in sdk_config.h

some driver(ex gpiote etc..)

priority 0, 1, 4, 5 is reserved for softdevice.

in saadc there is no sentence.

if i change saadc priority 6 -> 5 , is it no problem?

thank you so much

RE: 52832 saadc calibration issue

Jared — Mon, 21 Oct 2019 11:31:04 GMT

Hi,

Could you share the entire file where you call Calibration_init()? It's important that you don't call the function in interrupt context that has the same or higher interrupt priority.

Jared