Re-enable softdevice

RE: Re-enable softdevice

Hung Bui — Thu, 09 Feb 2017 14:02:12 GMT

Please post when you have it. According to our example experimental_ble_app_gzll (in multiprotocol folder) where we switch between Gazel (similar to ESB) and BLE we do need to disable all the interrupt including the RADIO_IRQn, before we switch back to BLE. I think it makes sense to update the nrf_esb_disable() to disable RadioIRQn. I will check with the developer.

RE: Re-enable softdevice

jrowe — Wed, 08 Feb 2017 21:04:58 GMT

It will probably be a few days before I have time to set up a clean example than runs on the developement boards (not my own hardware), but I will do so when I can. Perhaps the problem is that I am initializing the soft device first, disabling it when I want to use ESB, and then re-initializing it when I am done with ESB. I am using version 11.0.0 of the sdk and the s132 softdevice, but I tried it with version 12.0.0 well and had the same problem.

I did make one other change to the nrf_esb.h file so that I could use the app_timer module. see this link.

I will post thins kind of stuff as a comment in the future.

RE: Re-enable softdevice

Hung Bui — Wed, 08 Feb 2017 13:13:46 GMT

@jrowe : I tried to init esb and then disable it then call sd_softdevice_enable but it works fine in my case. Could you state which SDK version you used ? And better if you can provide an example that can demonstrate the issue. Also please create a new case or put it as a comment when you have similar issue, not as an answer to the question.

RE: Re-enable softdevice

Roger Clark — Fri, 03 Feb 2017 21:42:38 GMT

Sounds like a bug that should be reported to Nordic (if you have to modify the SDK)

I think there is a thread that Nordic created to report bugs in SDK 12

RE: Re-enable softdevice

jrowe — Fri, 03 Feb 2017 18:27:35 GMT

I had exactly the same problem: when trying to re-enable my softdevice after running ESB the sd_softdevice_enable() function would return with the "NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION" error code.

The solution that worked for me was to disable the RADIO_IRQn interrupt in the nrf_esb_disable() function inside of the nrf_esb.c file.

My modified nrf_esb_disable() function looks like this.

uint32_t nrf_esb_disable(void)
{
    m_nrf_esb_mainstate = NRF_ESB_STATE_DISABLE;

    /* Disable RADIO first. */
    NRF_RADIO->INTENCLR        = 0xFFFFFFFF;
    NRF_RADIO->EVENTS_DISABLED = 0;
    NRF_RADIO->TASKS_DISABLE   = 1;
    while (NRF_RADIO->EVENTS_DISABLED == 0) ;
    
    // Clear PPI
    NRF_PPI->CHENCLR = (1 << NRF_ESB_PPI_TIMER_START) |
                       (1 << NRF_ESB_PPI_TIMER_STOP)  |
                       (1 << NRF_ESB_PPI_RX_TIMEOUT)  |
                       (1 << NRF_ESB_PPI_TX_START);

    m_nrf_esb_mainstate = NRF_ESB_STATE_IDLE;

    reset_fifos();

    memset(m_rx_pipe_info, 0, sizeof(m_rx_pipe_info));
    memset(m_pids, 0, sizeof(m_pids));

    // Disable the radio
    NVIC_DisableIRQ(ESB_EVT_IRQ);
    NRF_RADIO->SHORTS = RADIO_SHORTS_READY_START_Enabled << RADIO_SHORTS_READY_START_Pos |
                        RADIO_SHORTS_END_DISABLE_Enabled << RADIO_SHORTS_END_DISABLE_Pos;

    // EDIT JBR: return origional priorities - turns out to be unnecessary.
    NVIC_SetPriority(RADIO_IRQn, s_radio_irq_initial_priority);
    NVIC_SetPriority(ESB_EVT_IRQ, s_esb_irq_initial_priority);
    // EDIT JBR: disable the radio interrupt! this is the one that fixes it
    NVIC_DisableIRQ(RADIO_IRQn);

    return NRF_SUCCESS;
}

I also reset the priorities for the interrupts back to the values that they were at before the nrf_esb_init() function changed them, but that proved to be unnecessary.

RE: Re-enable softdevice

Hung Bui — Mon, 17 Aug 2015 12:54:07 GMT

@LKH: You can get the priority level by using NVIC_GetPriority or sd_nvic_GetPriority() when softdevice is enabled. Make sure you don't use interrupt priority level 0 or 2 in your application when starting softdevice.

I would suggest you to test by not enabling any other interrupt /code when disable and enable the softdevice. (follow what we did in ble_app_gzll). And then gradually add your code in and see when the issue happens.

RE: Re-enable softdevice

LKH — Sat, 15 Aug 2015 13:11:48 GMT

Hi. I used ble_conn_params_stop() and softdevice_handler_sd_disable(), as in ble_app_gzll. I didn't check the return values of sd_softdevice_enable() in the ble_app_gzll yet.

And, ble_app_evt_wait() function returns 0x02 that means soft device is not enabled. (devzone.nordicsemi.com/.../) If the softdevice is already enabled, why the function ble_app_wait_evt() returns 0x02?

So I think the error code 0x00001001 means "enabled interrupt has an illegal priority level". How can I check priority level of enabled interrupts?

RE: Re-enable softdevice

Hung Bui — Fri, 14 Aug 2015 12:11:42 GMT

Hi,

Error code 0x00001001 means "NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION SoftDeviceinterrupt is already enabled". See the description of sd_softdevice_enable.

Have you made sure you have disabled it before you enable it again ?

When you testing with our ble_app_gzll do you have the same issue ?

RE: Re-enable softdevice

LKH — Fri, 14 Aug 2015 03:15:50 GMT

I am using ble_app_gzll for my refernce example, but the problem does not solved.