<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TWI - Sending arbitrary combinations of RX/TX without generating a TWI stop condition</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/101573/twi---sending-arbitrary-combinations-of-rx-tx-without-generating-a-twi-stop-condition</link><description>Hi, 
 We are using the nrf-twim driver for i2c/twi communication in our project. We are using the Azotech IQS7222B chip for touch buttons in our product and have run in to issues with the TWI driver. 
 The IQS7222B has a RDY pin that is active low. It</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 06 Jul 2023 14:24:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/101573/twi---sending-arbitrary-combinations-of-rx-tx-without-generating-a-twi-stop-condition" /><item><title>RE: TWI - Sending arbitrary combinations of RX/TX without generating a TWI stop condition</title><link>https://devzone.nordicsemi.com/thread/435027?ContentTypeID=1</link><pubDate>Thu, 06 Jul 2023 14:24:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:256ce11e-9fe2-465a-a302-aa9dd7549673</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Enabling a TX after RX after TX transfer in the TWIM peripheral requires the&amp;nbsp;&lt;span&gt;LASTRX_SUSPEND&amp;nbsp;&lt;a title="SHORTS" href="https://infocenter.nordicsemi.com/topic/ps_nrf52840/twim.html?cp=5_0_0_5_30_6_12#register.SHORTS"&gt;SHORT&lt;/a&gt;&amp;nbsp;feature, which was not published at the time of the driver implementations. It have since this been published and can be used for applications requiring this feature, but support for this have not been implemented in the drivers. This is not a very common use-case for TWI/I2C devices, and this is likely why it has not been added to the drivers.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;You could either implement a custom driver for supporting this, or use your alternative workaround for your slave device.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;br /&gt;Jørgen&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>