<?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>How to modify the timing at TWIM write/read sequence?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/107673/how-to-modify-the-timing-at-twim-write-read-sequence</link><description>Hi 
 Below is from nrf9160 data sheet TWIM section. 
 
 Using this sequence to a sensor device, we found sometimes the data read was incorrect. The sensor vendor said the root cause was the delay time 
 below was too short for their device to respond</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 24 Jan 2024 09:39:17 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/107673/how-to-modify-the-timing-at-twim-write-read-sequence" /><item><title>RE: How to modify the timing at TWIM write/read sequence?</title><link>https://devzone.nordicsemi.com/thread/465738?ContentTypeID=1</link><pubDate>Wed, 24 Jan 2024 09:39:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:44202b32-f599-48ef-b105-93861373e5b1</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Jeff,&lt;/p&gt;
&lt;p&gt;I see. Did the sensor vendor say more about what caused problems for the sensor? An alternative could be to split up the sequence in several transactions and add a delay in software (with a k_sleep()) between them to ensure they are long enough, if that is indeed what casues the problem for the sensor.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to modify the timing at TWIM write/read sequence?</title><link>https://devzone.nordicsemi.com/thread/465699?ContentTypeID=1</link><pubDate>Wed, 24 Jan 2024 01:38:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba242a48-1dff-4ac5-a3b0-df9e5b808b1e</guid><dc:creator>Jeffery</dc:creator><description>&lt;p&gt;Hi Einar&lt;/p&gt;
&lt;p&gt;Thanks. I2C frequency was the lowest(100K). The result was same.&lt;/p&gt;
&lt;p&gt;Jeff&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to modify the timing at TWIM write/read sequence?</title><link>https://devzone.nordicsemi.com/thread/465555?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2024 12:34:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8e727577-c35e-43f4-bc24-5c6311d83f29</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It seems like the sensor id doing some clocke stretching, so this time (before the snesor answers) is dictatedby the sensor, and not the nRF. If it needs a longer pause before answering, why does it not just stretch the clock longer? If this is the problem, then it seems like the sensor is behaving strangely.&lt;/p&gt;
&lt;p&gt;Can you try to work around it by using a lower I2C frequency?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to modify the timing at TWIM write/read sequence?</title><link>https://devzone.nordicsemi.com/thread/465506?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2024 09:23:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f2437e39-a798-4e1e-9ae7-393ace8b499d</guid><dc:creator>Jeffery</dc:creator><description>&lt;p&gt;Sorry. I posted same waveforms 3 times.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>