Why does TWIM driver execute SUSPEND when NO_SPURIOUS_STOP is specified?

RE: Why does TWIM driver execute SUSPEND when NO_SPURIOUS_STOP is specified?

loquat — Wed, 11 Feb 2026 23:20:39 GMT

Thanks.

RE: Why does TWIM driver execute SUSPEND when NO_SPURIOUS_STOP is specified?

Priyanka — Thu, 05 Feb 2026 09:26:29 GMT

Hi,

There is a following sentence in the product specification:

Note: The TWI master does not stop by itself when the entire RAM buffer has been sent, or when an error occurs. The STOP task must be issued, through the use of a local or PPI shortcut, or in software as part of the error handler.

and the nrfx_twim implementation has chosen the local shortcut approach.

-Priyanka

RE: Why does TWIM driver execute SUSPEND when NO_SPURIOUS_STOP is specified?

loquat — Fri, 30 Jan 2026 14:50:43 GMT

Thanks.

How is that different from specifying the LASTTX_STOP shortcut?

RE: Why does TWIM driver execute SUSPEND when NO_SPURIOUS_STOP is specified?

Priyanka — Thu, 29 Jan 2026 14:29:07 GMT

If no shortcuts are specified, obviously a STOP condition will be initiated. And hence we prefer setting a SUSPEND, because this prevents an immediate STOP condition.

If a STOP is initiated, then after the first transmission, the master will have to give up the bus and START again, and in the meantime if some other device gains bus control, then we will have to wait until we get control again, in order to START the next TX.

-Priyanka

RE: Why does TWIM driver execute SUSPEND when NO_SPURIOUS_STOP is specified?

loquat — Wed, 28 Jan 2026 14:50:04 GMT

Thanks.

What happens if all shortcuts are not specified?
Wouldn't that also result in a STOP condition?
I'd like to know why it is necessary to set it to SUSPEND instead of not specifying all shortcuts.

RE: Why does TWIM driver execute SUSPEND when NO_SPURIOUS_STOP is specified?

Priyanka — Wed, 28 Jan 2026 09:57:26 GMT

Hi,

NRF_TWIM_SHORT_LASTTX_SUSPEND_MASK is like a shortcut which connects the LASTTX to the SUSPEND task in the hardware. So what basically happens is that, after the LASTTX event, instead of a STOP condition (which forces the TX to release the bus), a SUSPEND is instead given, so that the bus need not be released yet, as there will be a new TX that's going to happen. You could say that it's like the repeated START condition in a usual TWI scenario.

So when you use the NRFX_TWIM_XFER_TXTX, the NRF_TWIM_SHORT_LASTTX_SUSPEND_MASK is also enabled so that there is no interruption between the first TX and the next, i.e. a STOP condition is not enabled for smoother transactions.

-Priyanka