<?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>I2C frequency  in NCS V3.2.0 nrf52833</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127918/i2c-frequency-in-ncs-v3-2-0-nrf52833</link><description>The device tree configuration rate is inconsistent with the actual rate.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 29 Apr 2026 22:12:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127918/i2c-frequency-in-ncs-v3-2-0-nrf52833" /><item><title>RE: I2C frequency  in NCS V3.2.0 nrf52833</title><link>https://devzone.nordicsemi.com/thread/565706?ContentTypeID=1</link><pubDate>Wed, 29 Apr 2026 22:12:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:79e9d2bd-f1fd-4437-9ee4-0e39bac8f2e5</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;One issue which can cause slower than expected clock rates with i2c is the nRF52833 mistakenly thinking the i2c slave is requesting clock stretching; this can occur by using too-soft drive levels on SCL and SDA (S0D1) particularly at 400kHz. Fix - advisable in any case for i2c at 400kHz - by forcing high-drive (H0D1) and ensuring the pull-up resistance to VDD is low enough, perhaps 4k7 or less. If the i2c slave is on a single bus and never requests a clock stretch, H0H1 can be used.&lt;/p&gt;
&lt;p&gt;The trace waveforms captured are very misleading as they are on a digital logic analyser; using an oscilloscope would show that SCL in particular is very soggy with a slow rise- and fall-time; it is this slow rise &amp;amp; fall which makes the nRF52833 think the clock is being externally held low for a time (which is interpreted as a clock stretch) and sharpening up those clock edges can provide a solution. The longer the i2c SCL connection the worse the problem due to parasitic capacitance.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;/* 重新定义 i2c0_default 和 i2c0_sleep 以覆盖默认引脚 */
&amp;amp;pinctrl {
	/* 覆盖默认的 i2c0_default */
	i2c0_default: i2c0_default {
		group1 {
			psels = &amp;lt;NRF_PSEL(TWIM_SDA, 0, 17)&amp;gt;,    /* P0.26 SDA */
					&amp;lt;NRF_PSEL(TWIM_SCL, 0, 15)&amp;gt;;    /* P0.27 SCL */
			nordic,drive-mode = &amp;lt;NRF_DRIVE_H0D1&amp;gt;;  // &amp;lt;== add something like this
		};
	};

	/* 覆盖默认的 i2c0_sleep */
	i2c0_sleep: i2c0_sleep {
		group1 {
			psels = &amp;lt;NRF_PSEL(TWIM_SDA, 0, 17)&amp;gt;,
					&amp;lt;NRF_PSEL(TWIM_SCL, 0, 15)&amp;gt;;
			nordic,drive-mode = &amp;lt;NRF_DRIVE_H0D1&amp;gt;;  // &amp;lt;== add something like this
			low-power-enable;
		};
	};
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Worth checking with a debugger that zephyr stuff doesn&amp;#39;t defeat this high-drive setting, and if using 10k pull-ups reduce that to 4k7 or less ..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C frequency  in NCS V3.2.0 nrf52833</title><link>https://devzone.nordicsemi.com/thread/565647?ContentTypeID=1</link><pubDate>Wed, 29 Apr 2026 02:08:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:774c26b6-faac-46ce-ad2c-078506d2679d</guid><dc:creator>mjguo</dc:creator><description>&lt;p&gt;you can download code:&amp;nbsp;&lt;a href="https://github.com/gmj22362/ncs_example.git"&gt;github.com/.../ncs_example.git&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C frequency  in NCS V3.2.0 nrf52833</title><link>https://devzone.nordicsemi.com/thread/565600?ContentTypeID=1</link><pubDate>Tue, 28 Apr 2026 08:13:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:81751550-e215-4bd4-8afe-8f909db49c30</guid><dc:creator>Priyanka</dc:creator><description>&lt;p&gt;You could maybe attach your code (do let me know in case I need to make the case private for this) and I can take a look at it.&lt;/p&gt;
&lt;p&gt;-Priyanka&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C frequency  in NCS V3.2.0 nrf52833</title><link>https://devzone.nordicsemi.com/thread/565599?ContentTypeID=1</link><pubDate>Tue, 28 Apr 2026 08:12:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f049f4f6-f6b2-470f-8104-8a4f3176152e</guid><dc:creator>Priyanka</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;Could you check in you application code, whether you are maybe using the&amp;nbsp;I2C_BITRATE_STANDARD or whether some snippet in the code is actually calling the standard rate ?&lt;/p&gt;
&lt;p&gt;This can override the dts setting.&lt;/p&gt;
&lt;p&gt;-Priyanka&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C frequency  in NCS V3.2.0 nrf52833</title><link>https://devzone.nordicsemi.com/thread/565486?ContentTypeID=1</link><pubDate>Sat, 25 Apr 2026 04:11:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2fd23768-c40a-4560-80a9-cf16b0742635</guid><dc:creator>mjguo</dc:creator><description>&lt;p&gt;This is the waveform I captured.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/image_2D00_2026_2D00_4_2D00_25_5F00_12_2D00_2_2D00_1.png" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>