<?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>The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/95973/the-soc-nrf5340-i2c-channel-random-failure-with-zephyr</link><description>We are using a few sensors like (IMU, Barometer ) on one of the I2C lines. All the other sensors gets detected but the IMU and Barometer does not get detected even when the CS and SDA SCL are high. The Pull up resistors (internal) does not make the SDA</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Feb 2023 05:33:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/95973/the-soc-nrf5340-i2c-channel-random-failure-with-zephyr" /><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/408730?ContentTypeID=1</link><pubDate>Wed, 08 Feb 2023 05:33:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d58edb6-b608-4f96-b686-8f6f6e788039</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;Hi,Thanks for the help. We could solve the issue. What you said was correct. The Pins were being used by Uart and peripheral.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/408713?ContentTypeID=1</link><pubDate>Tue, 07 Feb 2023 23:34:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f358426a-d139-4beb-9a12-7b7ffb3bfb1d</guid><dc:creator>helsing</dc:creator><description>&lt;p&gt;Hi Vivek,&lt;/p&gt;
&lt;p&gt;Thank you for sharing the files. We are looking into the code and will get back to you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/408173?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2023 07:03:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8f05d78b-6ade-4988-b212-93c9910fdb6e</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/IMU_5F00_Working.zip"&gt;devzone.nordicsemi.com/.../IMU_5F00_Working.zip&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/IMU_5F00_Not_5F00_Working.zip"&gt;devzone.nordicsemi.com/.../IMU_5F00_Not_5F00_Working.zip&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Hi, these are the two sets of codes.&lt;br /&gt;When we load the bluetooth stack the IMU stops getting detected.&amp;nbsp;&lt;br /&gt;the only difference between the two sets are the files&amp;nbsp;&lt;br /&gt;prj.conf and&amp;nbsp;&lt;br /&gt;CMakeLists.txt&lt;br /&gt;&lt;br /&gt;rest all is same.&lt;br /&gt;&lt;br /&gt;Please help us in getting the issue resolved.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/408134?ContentTypeID=1</link><pubDate>Sun, 05 Feb 2023 07:11:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94c93cea-8244-450a-ba60-edc96c425aa3</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;Hi, we have sent two project files to you on your personal mail. difference between workign IMU and the one with Not Working IMU is only two files&amp;nbsp; CMakeList.txt and prf.conf. On starting of BLE, the IMU stops working. Please check the code. Rest is all same.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/407834?ContentTypeID=1</link><pubDate>Thu, 02 Feb 2023 15:21:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fdddd015-4de7-4425-a335-1ab727b39e0d</guid><dc:creator>helsing</dc:creator><description>&lt;p&gt;Hi Vivek, sorry for the delay.&lt;/p&gt;
&lt;p&gt;From Zephyr.dts that you provided it looks like uart0 and i2c1 are both using P0.13.&lt;/p&gt;
&lt;p&gt;Is uart0 in use when Bluetooth is used, perhaps for logging? Try changing the rts-pin of uart0 to something else and see if it helps.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/407002?ContentTypeID=1</link><pubDate>Mon, 30 Jan 2023 07:30:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e1238ca8-4da3-4b26-b8f6-9d450e57cd74</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;Hi, waiting for your response.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406897?ContentTypeID=1</link><pubDate>Fri, 27 Jan 2023 15:19:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:096e73b8-47a5-43cf-b996-ee4e96e231d8</guid><dc:creator>helsing</dc:creator><description>&lt;p&gt;Thank you for the updates I am looking into this and will get back to you over the weekend.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406718?ContentTypeID=1</link><pubDate>Thu, 26 Jan 2023 15:20:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:038d6dd2-82be-4b5a-91d5-69c00e2eae2c</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;Making the P1.00 and P1.01 high using internal resistors does not makes them high.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406706?ContentTypeID=1</link><pubDate>Thu, 26 Jan 2023 14:50:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c2afd5e-038a-4f34-b7a3-1513819474b0</guid><dc:creator>Vivek</dc:creator><description>&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/nrf_5F00_IMU.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;The continuity is good and the components are well placed and connected. This is the connection from nrf5340 to LSM6DSOX&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406705?ContentTypeID=1</link><pubDate>Thu, 26 Jan 2023 14:45:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:646063e5-8728-48ce-bb09-404295ff239e</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We have send the schematics to your personal account. The I2C line where the IMU and Baro are connected are not getting detected. We are sending the circuitry too. The RF is not near this line.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406697?ContentTypeID=1</link><pubDate>Thu, 26 Jan 2023 14:29:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ea0f495a-695d-4f50-a2b2-0f0d57b39928</guid><dc:creator>helsing</dc:creator><description>[quote user="plawat"]However on putting the entire code and activating the BLE, one line (of IMU) stops getting detected.[/quote]
&lt;p&gt;Could you please explain this in more detail? What does it mean that one line of (of IMU) stops getting detected?&lt;/p&gt;
&lt;p&gt;Has the layout of the device been reviewed? Is this line anywhere near the RF path?&lt;/p&gt;
[quote user="plawat"]&lt;p&gt;Can power consumption be an issue?&lt;/p&gt;
&lt;p&gt;We have use TPS63901 that has 400ma limit. Can that be an issue.&lt;/p&gt;[/quote]
&lt;p&gt;What does the power budget for the devices look like? I believe this 400mA should be sufficient. We can have a closer look at this if we are not able to find something else. &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406496?ContentTypeID=1</link><pubDate>Wed, 25 Jan 2023 14:43:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c1458e98-f70a-4429-aa1f-d3dccca24ed5</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;Okay, pl see our last comments too.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406494?ContentTypeID=1</link><pubDate>Wed, 25 Jan 2023 14:40:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c88c28b-584e-4d4d-9e8e-ab6e04dc1f36</guid><dc:creator>helsing</dc:creator><description>&lt;p&gt;Thank you for the file. I will check it out and get back to you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406443?ContentTypeID=1</link><pubDate>Wed, 25 Jan 2023 12:16:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b2fe3944-4318-4d2e-a21f-0a139e8fb3b1</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We put a small code to detect the sensors only and all sensors are getting detected.&lt;/p&gt;
&lt;p&gt;However on putting the entire code and activating the BLE, one line (of IMU) stops getting detected.&lt;/p&gt;
&lt;p&gt;Can power consumption be an issue?&lt;/p&gt;
&lt;p&gt;We have use TPS63901 that has 400ma limit. Can that be an issue.&lt;/p&gt;
&lt;p&gt;The issue of pins 43 and 45 is no more there.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406320?ContentTypeID=1</link><pubDate>Tue, 24 Jan 2023 15:44:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1605715b-2712-450e-9af7-082137cefd1b</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/zephyr.zip"&gt;devzone.nordicsemi.com/.../zephyr.zip&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;dts file&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406288?ContentTypeID=1</link><pubDate>Tue, 24 Jan 2023 14:32:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c95ea35-54e1-42cc-8155-bace52a8e021</guid><dc:creator>helsing</dc:creator><description>&lt;p&gt;How do you specify the pins in your project code?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406275?ContentTypeID=1</link><pubDate>Tue, 24 Jan 2023 14:07:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f9eab56-38e4-4650-9ef5-6ecc8f91dd37</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;We are using P1.00 and P1.01 for the I2C SCL and SDA for the IMU&lt;/p&gt;
&lt;p&gt;the RGB (part D2) is connected to 43,44 and 45 (P1.11, P1.12, P1.13) pins as seen on page two of the pdf attached.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406272?ContentTypeID=1</link><pubDate>Tue, 24 Jan 2023 14:02:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6353f9ba-4adb-4b6e-8244-1c33c59d4cbd</guid><dc:creator>helsing</dc:creator><description>&lt;p&gt;Hi Vivek, &lt;/p&gt;
[quote user=""]However on turning the pins 43 and 45 High, the SCL and SDA becomes high and the IMU and barometer get detected.[/quote]
&lt;p&gt;How do you specify the pins? Would you be able to share the board files, or at least the .dtsi and .dts files?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The SoC nrf5340 I2C channel random failure with Zephyr</title><link>https://devzone.nordicsemi.com/thread/406263?ContentTypeID=1</link><pubDate>Tue, 24 Jan 2023 13:36:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f09999ba-3002-4409-80f8-fc941623ae26</guid><dc:creator>Vivek</dc:creator><description>&lt;p&gt;How to make the pins 32 and 33 high using internal pull ups?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>