SAADC with softdevice cann't work

[liu]

Hi,

Now, i want to use SAADC with softdevice of SDK15.0 to make a beacon program.

I migrate SAADC example in nRF5_SDK_15.0.0_a53641a\examples\peripheral to beacon with softdevice. My cpu is NRF52810. Of course, i change timer from timer0 to timer1.

Now ,i compile it no error,but i cann't run these codes:

#define SAMPLES_IN_BUFFER 1
volatile uint8_t state = 1;

const nrf_drv_timer_t TIMER_LED = NRF_DRV_TIMER_INSTANCE(1);
static nrf_saadc_value_t m_buffer_pool[2][SAMPLES_IN_BUFFER];
static nrf_ppi_channel_t m_ppi_channel;
static uint32_t m_adc_evt_counter;

in main function:
saadc_init();   //cann't run;
saadc_sampling_event_init();   //cann't run;
saadc_sampling_event_enable();   //cann't run;

 

[Einar Thorsrud]

Hi,

Please elaborate on what actually happens when you write "can't run". Also, please look at this example (ble_app_beacon_saadc_sdk_15.2.zip) which I just adapted for this thread. It combines the SKD beacon example application with the SAADC example.

[liu]

Hi,

Einar.

Thanks.

Now, i add some printf to show where the progarm stop.

It shows program stop at saadc_sampling_event_init(), in it we can find:

the result shows the code 

    err_code = nrf_drv_ppi_channel_alloc(&m_ppi_channel);

cann't run through.

we can find this result  by sscom32:

 

[Einar Thorsrud]

Can you debug to see what happens when "the program stops"? Using a debugger you should be able to see what is happening. What is the state of the CPU etc. when it seems like it is stopped? What happens within nrfx_ppi_channel_alloc()?