Conflict between TWI non blocking and debuggerhttps://devzone.nordicsemi.com/f/nordic-q-a/111827/conflict-between-twi-non-blocking-and-debuggerHi, I am developping a non blocking TWI (I2C) communication, calling this function: The init function of the twi is : Please note that the real code is splitted in more functions, I concatenated it here for better understand, I might haveen-USTelligent Community 13Wed, 05 Jun 2024 09:09:56 GMTRE: Conflict between TWI non blocking and debuggerhttps://devzone.nordicsemi.com/thread/487454?ContentTypeID=1Wed, 05 Jun 2024 09:09:56 GMT137ad170-7792-4731-bb38-c0d22fbe4515:9866c119-2539-488e-99cf-ed2b3c4213e3Diogen23<p>Indeed, I use TWI.</p> <p>This makes sense. Thanks for your answer.</p><div style="clear:both;"></div>RE: Conflict between TWI non blocking and debuggerhttps://devzone.nordicsemi.com/thread/487434?ContentTypeID=1Wed, 05 Jun 2024 08:00:20 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8d4a05e6-60a0-4a83-bb1d-aa1d90f10f95Turbo J<p>If you actually used TWI and not the TWIM peripherial, you cannot send more than one byte with the MCU core blocked by a debugger.</p> <p>The TWIM can do that via EasyDMA, but the TWI needs to be fed by the MCU core.</p><div style="clear:both;"></div>