how to avoid softdevice interrupts during i2c read operation

[microembedded]

hi, i am reading mpu6050 with nrf51822. every now and then the data got corrupt because of softDevice interrupts. if i don't use Softdevice the it runs perfectly but when i use softdevice(S130) it give me some corrupt data and at times it got stuck at some point. how can i avoid this.

[endnode]

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.)

[microembedded]

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.

[Daniel Wang]

try to increase the TWI_DEFAULT_CONFIG_IRQ_PRIORITY

[endnode]

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