Migration to SD functions

[Ck]

I have to update my non soft device source code to SD because now I will use Radio.

My question is if it is necessary to rewrite all functions which are in SD API. Like:

NVIC_SetPriority(ADC_IRQn, APP_IRQ_PRIORITY_LOW);
NVIC_ClearPendingIRQ(ADC_IRQn);
NVIC_EnableIRQ(ADC_IRQn);
NRF_POWER->SYSTEMOFF = 1;	
NRF_CLOCK->TASKS_HFCLKSTART = 1;
NRF_RTC1->EVENTS_COMPARE[0] = 0;
__WFI();
__WFE();
and similiar

I'm assume that SD alternate function has just some assert to control if I'm passing right arguments or so. So if I'm sure I didn't use any resources against SD, is it necessary to use strictly only SD functions?

[Nikita]

You can see in S110_SoftDevice_Specification_v1 3.pdf there is a list of peripherals used by softdevice in "Table 23 Peripheral protection and usage by SoftDevice".

Any direct access to the protected resources while softdevice is enabled will generate hard fault by softdevice, so you must use softdevice calls to access to this resources.

[Ck]

I'm not using any peripheral used by SD, but I'm using IRQ handlers for non restrictred or blocked peripherals (I hope at least this is OK), various power modes and HF clock start/stop (so here I have to use alternate SD funcs). BTW sd_app_evt_wait() is waiting for event or irq, what about if I want strictly wait for irq as it is done by __WFI()?

[Nikita]

but I'm using IRQ handlers for non restrictred or blocked peripherals (I hope at least this is OK)

Yes, it's ok, you only need to use sd_nvic_* instead of NVIC_*.

BTW sd_app_evt_wait() is waiting for event or irq, what about if I want strictly wait for irq as it is done by __WFI()?

There is no way to do it, softdevice has only this one function for both irq and events together. Softdevice handles both irq and events and after softdevice handles them first then softdevice will send software interrupt to the application.

[Ck]

I search for enum NRF_SOC_EVTS and that means that by sd_app_evt_wait() system go sleep and wake up at ANY generated event or interrupt, but sd_evt_get(p_evt_id) can get only those events in enum NRF_SOC_EVTS, right? So for non SD events I still can use own flags set in appropriate IRQ handler to know that particular event has occured.

[Nikita]

Yes, for example, you want to send some data through UART and you send first byte by writing

NRF_UART0->TXD = data[0]; 

and then go to low-power mode with sd_app_evt_wait() then you will return from sd_app_evt_wait() when UART will send data and generate TXDRDY event so you can handle it like this:

// Enter main loop.
for (;;)
{
    if (NRF_UART0->EVENTS_TXDRDY == 1)
    {
        NRF_UART0->EVENTS_TXDRDY = 0;
        NRF_UART0->TXD = data[next_byte]; 
        ...
    }
    sd_app_evt_wait();
}

[Ck]

Great. Now I'm not sure only with __SEV(); Can I use this instruction withih SD enabled? I'm using this in IRQ handler after event_flag is set to avoid race condition.