Twi sensor interrupt driven example?

RE: Twi sensor interrupt driven example?

Jørgen Holmefjord — Thu, 10 Jan 2019 14:07:15 GMT

The softdevice will always have highest priority, and will preempt the TWI driver. The TWI driver does not support timeouts, and there is no function to stop a transfer (and to be honest, I have never heard about this being an issue). The TWI protocol will report an error if a command is not ACK'ed. The TWI slave will send a NACK to stop the transfer when it is done sending data.

You can implement a timer that trigger the STOP task manually if you need timeouts, using the TWI HAL function nrf_twi_task_trigger (NRF_TWI_Type *p_reg, nrf_twi_task_t task).

RE: Twi sensor interrupt driven example?

Luke.L — Wed, 09 Jan 2019 13:57:43 GMT

Thanks for the reply. One of my concerns is the blocking event handling may interrupt ble connections? Or would it not? And what would be the best practice for TWI timeouts?

RE: Twi sensor interrupt driven example?

Jørgen Holmefjord — Wed, 09 Jan 2019 12:12:17 GMT

Hi,

The TWI Sensor example in the SDK is interrupt driven. The example do have a blocking while loop that ensures that a transfer is completed before starting a new one, but this you will not be able to avoid anyway. If this example does not meet your requirements, you should include some details about your application and what your requirements are.

Best regards,
Jørgen