TWI Slave and APP_TIMER issues

[AntonHellbe]

Hi,

I'm working on a custom bootloader which does DFU over I2C. As a fail safe mechanism I want to have a timer running that gets reset between each Image data block, so incase we dont get a new image data block in 5-10 seconds (unless we have received the entire image) time the nRF52832 resets itself and goes back to the bootloader and waiting for a complete transfer.

The problems I'm seeing is that the I2C transfers stops working when I try to reset the timer in the I2C interrupt. If I start the timer at boot it runs and reaches its handler for as long as I dont transfer anything over I2C. But as soon as I transfer something it does not hit the handler and the I2C transfers stops.

I'm not quite sure what's happening here as I dont seem to hit any error handlers. Since the timer is not supposed to hit hits handler (if the DFU proccess is successful) they dont run in the same context either. But I have tried changing so that the TWI uses a higher interrupt priority than the APP_TIMER_MODULE, but that does not seem to help.

Here's my TWIS evt handler:

static void twis_event_handler(nrfx_twis_evt_t const * const p_event)
{
    ret_code_t err_code;
    switch(p_event->type)
    {
    case NRFX_TWIS_EVT_READ_REQ:
        if(p_event->data.buf_req)
        {
            err_code = nrfx_twis_tx_prepare(&instance, tx_buff, tx_len);
            NRF_LOG_DEBUG("TX prepare returned err_code: %d", err_code);
        }
        break;
    case NRFX_TWIS_EVT_READ_DONE:
        break;
    case NRFX_TWIS_EVT_READ_ERROR:
        NRF_LOG_DEBUG("I2C read error!")
        break;
    case NRFX_TWIS_EVT_WRITE_REQ:
        if(p_event->data.buf_req)
        {
            err_code = nrfx_twis_rx_prepare(&instance, rx_buff, sizeof(uint8_t) * 128);
            NRF_LOG_DEBUG("RX prepare returned err_code: %d", err_code);
        }
        break;
    case NRFX_TWIS_EVT_WRITE_DONE:
        if (p_event->data.rx_amount > 2)
        {
            NRF_LOG_DEBUG("Received data, DECODING");
            comm_timer_restart();
            handleData(rx_buff, (uint16_t) p_event->data.rx_amount);
        }
        break;
    case NRFX_TWIS_EVT_WRITE_ERROR:
        NRF_LOG_DEBUG("I2C Write error!");
        break;
    case NRFX_TWIS_EVT_GENERAL_ERROR:
        NRF_LOG_DEBUG("I2C Error!");
        break;
    default:
        NRF_LOG_DEBUG("I2C handler default case??");
        break;
    }
}

[Jared]

Hi,

Sorry for the late reply,

I have a couple questions I would like you to answer :) : 

• Which SDK and Softdevice (if you are) version are you using?
• Could you provide a bit more code? I'm specifically interested in the initialization of the Timer and the I2C modules. Could you also share the timer handler, and how you reset the timer? I can make the case private if you prefer it. 
• Where exactly is the code stuck? Have you tried using the debugger and single step through the code?

best regards

Jared

[AntonHellbe]

Also,

Since I'm not using Segger Embedded Studio I'm working on getting the debugging working. I'm having some issues with Ozone. Will update you as soon as I get it to work..

[Jared]

But as soon as I transfer something it does not hit the handler and the I2C transfers stops.

 Could you elaborate on this? My understanding of your project is that you don't want the timer to hit its handler when you transfer as this would cause a reset of the nRF. Instead, you would want to reset the timer after the transfer is complete in the NRFX_TWIS_EVT_WRITE_DONE case.  Is the problem that the I2C transfer doesn't start again after the timer is reset? again, it would be good to know where in the code it stops.

[AntonHellbe]

Hi Jared,

You are correct that I dont want it to hit the timeout handler.

What's happening is that my timer reset is too quick, I stop it quickly and then start it immediately. This does not seem to reset the timer count, causing it to hit the timer timeout handler. And that apparently breaks the I2C transfers. Probably because I will keep trying to restart the timer each time a new I2C message is received.

What I need to solve here is to reset the timer in a manner that ensures that the timer count is reset before I start it again.

Any ideas how I can achieve that?

[Jared]

Hi,

This may be related to the app timer library. SDK 16 has introduced a new and improved version of the library app timer v2. A quick method to check if this is related to the driver is to backport the driver by downloading SDK 16, copy and paste the app_timer2.c and drv_rtc.c instead of app_timer.c to your SDK 15 project see if the problem persists.

regards

Jared