<?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>TWIS read with repeated start</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/70752/twis-read-with-repeated-start</link><description>Hi all, 
 I have a problem with nRF52840 acting as TWI slave. I&amp;#39;m using TWIS. Typical scenario is: 
 1. Master writes request and ends transaction using stop condition. 
 2. Master starts read transaction, read some bytes, NAK last byte and perform repeated</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 22 Jan 2021 14:51:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/70752/twis-read-with-repeated-start" /><item><title>RE: TWIS read with repeated start</title><link>https://devzone.nordicsemi.com/thread/290793?ContentTypeID=1</link><pubDate>Fri, 22 Jan 2021 14:51:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a3e320e-6acf-4a3d-a5ff-b6c28d884c62</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This is due to the&amp;nbsp;&lt;span&gt;The RXD.AMOUNT register only being updated after every transaction has ended. A transaction is then interpreted&amp;nbsp;as after the STOP signal has been received&amp;nbsp;from the Master. Which means that you do have to split it into multiple transaction if you want to use the RXD.AMOUNT with repeated start.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;regards&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Jared&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>