SAADC with softdevice cann't work

RE: SAADC with softdevice cann't work

Einar Thorsrud — Fri, 26 Oct 2018 10:17:12 GMT

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()?

RE: SAADC with softdevice cann't work

liu — Fri, 26 Oct 2018 02:16:37 GMT

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:

RE: SAADC with softdevice cann't work

Einar Thorsrud — Thu, 25 Oct 2018 11:23:33 GMT

Hi,

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

RE: SAADC with softdevice cann't work

liu — Thu, 25 Oct 2018 08:47:40 GMT

I use timer1 or timer2,but it cann't work also;

saadc_init(); //cann't run through this code;

saadc_sampling_event_init();

saadc_sampling_event_enable();