TWI timeout - SDK11

RE: TWI timeout - SDK11

Susheel Nuguru — Sun, 11 Mar 2018 11:42:24 GMT

seems like a good solution. The whole point of open source is to add/modify features to your liking, which you did :)

RE: TWI timeout - SDK11

oneguy — Fri, 09 Mar 2018 07:15:43 GMT

We ended up doing this (using embOS):

- in your read/write function ----------------------------------------

if (nrf_drv_spi_transfer (&mSpi, setup, 3, NULL, 0) != NRF_SUCCESS)
{
nrf_gpio_pin_set (PIN_FRAM_CS);
return (NRF_ERROR_INTERNAL);
}

if (! transferCompleted (DEVICE_TIMEOUT))
{
nrf_gpio_pin_set (PIN_FRAM_CS);
return (NRF_ERROR_TIMEOUT);
}

- here is yout transferCompleted function -------------------------------

static bool transferCompleted (int ms)
{
bool tc = (OS_EVENT_WaitTimed (&mTCevent, ms) == 0);

return (tc); /* Return true to indicate successful transfer */
}

- here is what the respective interrupt service routine does ----------

static void onTransferComplete (nrf_drv_spi_evt_t const * p_event, void * p_context)
{
OS_EVENT_Set (&mTCevent); /* All bytes transferred */
/* --> signal main thread */
} /* (see transferCompleted ()) */

RE: TWI timeout - SDK11

Susheel Nuguru — Thu, 08 Mar 2018 07:45:30 GMT

so this problem is solved in the later SDK?

RE: TWI timeout - SDK11

oneguy — Wed, 28 Feb 2018 15:42:19 GMT

No, but in the mean time we have switched to a later SDK. Is seems to include code to guard against timeouts.

RE: TWI timeout - SDK11

AndrewJ — Fri, 23 Feb 2018 03:31:38 GMT

I'm experiencing hanging in the exact spot as the OP. Was a solution ever found to this problem?

RE: TWI timeout - SDK11

oneguy — Tue, 30 Aug 2016 12:05:24 GMT

Thank you for your reply AlexV.

If I choose Option 2 (non-blocking) which function do I use to cancel the pending write?

RE: TWI timeout - SDK11

Alex — Tue, 30 Aug 2016 11:21:09 GMT

Simplest solution is to modify your current blocking functions but remember that if you update SDK you have to modify it again unless you create your own functions based on Nordic implementation. Non-blocking in your case is more safe for future but need to spend time now to implement it. I would not wait for option (3)

RE: TWI timeout - SDK11

laurent — Mon, 29 Aug 2016 14:47:36 GMT

Hi, I can advise you to try making a simple read sequence first following the good sample (which works well): devzone.nordicsemi.com/.../ This is helpful to check the communication beetween nRF and a twi slave. laurent