how to avoid softdevice interrupts during i2c read operation

RE: how to avoid softdevice interrupts during i2c read operation

endnode — Thu, 11 May 2017 07:13:55 GMT

Also are you sure you use proper DMA enabled driver from SDK?

RE: how to avoid softdevice interrupts during i2c read operation

Daniel Wang — Wed, 10 May 2017 16:47:38 GMT

try to increase the TWI_DEFAULT_CONFIG_IRQ_PRIORITY

RE: how to avoid softdevice interrupts during i2c read operation

microembedded — Wed, 10 May 2017 16:38:45 GMT

i am using I2C as master. the reading i get are mostly correct lets say 5 incorrect readings in 100 readings. in very unusual case it got stuck during reading I2C. if i don't use S130 then it works perfectly well. so i am guessing the application interrupts are causing it.

RE: how to avoid softdevice interrupts during i2c read operation

endnode — Wed, 10 May 2017 11:48:38 GMT

If you use I2C (TWI) slave on nRF51 during BLE connection with Nordic stack (SD) then I'm afraid you have a problem. In our case it leaded to redoing HW architecture because it was simply impossible to achieve reliable communication during heavy BLE processing (connection event). I2C (TWI) Master should be OK on nRF51 because it has DMA (since rev 2 or 3 I believe), similar to SPI (should work both Master and Slave). So if you experience problems when nRF51 is Master then are you sure you started from proper SDK example?

(Another way could be to use non-Nordic BLE stack but I would not go there, most of open-source promising projects focus on nRF52 now.)