<?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>VL53L3X interfacing problem with nrf52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/110169/vl53l3x-interfacing-problem-with-nrf52832</link><description>Hii , I am interfacing VL53L3X sensor with the nrf52832 , and using its given liberary which is in zephyr for VL53L0X , as I think it should we work with also my sensor VL53L3x , I use the given liberary and connect my device and check on the logic analyser</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 18 Apr 2024 13:10:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/110169/vl53l3x-interfacing-problem-with-nrf52832" /><item><title>RE: VL53L3X interfacing problem with nrf52832</title><link>https://devzone.nordicsemi.com/thread/479452?ContentTypeID=1</link><pubDate>Thu, 18 Apr 2024 13:10:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:41565233-7160-4a1b-8b09-75b2dbea06bc</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;I am not sure of the issue. Could you share your whole file? I will go through it. There is a developer academy course on &lt;a href="https://devzone.nordicsemi.com/support-private/support/325206/I%20am%20not%20sure%20of%20the%20issue.%20Could%20you%20share%20your%20whole%20file?%20I%20will%20go%20through%20it.%20There%20is%20a%20developer%20academy%20course%20on%20I2C%20communication;%20please%20make%20sure%20you%20have%20followed%20every%20step%20mentioned.%20As%20an%20example,%20you%20can%20go%20through%20the%20exercise%20section."&gt;I2C communication&lt;/a&gt;; please make sure you have followed every step mentioned. As an example, you can go through&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-6-serial-com-i2c/topic/exercise-1-6-2/"&gt; the exercise section&lt;/a&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;Kind Regards,&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;Abhijith&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VL53L3X interfacing problem with nrf52832</title><link>https://devzone.nordicsemi.com/thread/478900?ContentTypeID=1</link><pubDate>Tue, 16 Apr 2024 09:03:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ee80734d-0e97-4289-89e0-e2ed3b7eadf9</guid><dc:creator>Ashleo</dc:creator><description>&lt;p&gt;hello,&lt;/p&gt;
&lt;p&gt;Yes I used&amp;nbsp;&lt;span&gt;CONFIG_VL53L1X in my prj already.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;and I&amp;nbsp; use this 0x29 address in overlay to make i2c communication ,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;both address 0x52 and 0x29 show (sensor: device not ready.)&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VL53L3X interfacing problem with nrf52832</title><link>https://devzone.nordicsemi.com/thread/478871?ContentTypeID=1</link><pubDate>Tue, 16 Apr 2024 07:19:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a7961ae3-a775-49f9-b136-79d083b5ea17</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Could you try enabling the configuration CONFIG_VL53L1X inside the prj.config?&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The address&amp;nbsp;&lt;/span&gt;&lt;code dir="ltr"&gt;0x52&lt;/code&gt;&lt;span&gt;&amp;nbsp;is an 8-bit address, and when converted to a 7-bit address (used on the I2C bus during communication), it becomes&amp;nbsp;&lt;/span&gt;&lt;code dir="ltr"&gt;0x29&lt;/code&gt;&lt;span&gt;. This is done by right-shifting the address by one bit&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt; (&lt;/span&gt;&lt;code dir="ltr"&gt;0x52 &amp;gt;&amp;gt; 1 = 0x29&lt;/code&gt;&lt;span&gt;). This is why you&amp;#39;re seeing&amp;nbsp;&lt;/span&gt;&lt;code dir="ltr"&gt;0x29&lt;/code&gt;&lt;span&gt;&amp;nbsp;when you use an I2C scanner or a logic analyzer, and why you need to use&amp;nbsp;&lt;/span&gt;&lt;code dir="ltr"&gt;0x29&lt;/code&gt;&lt;span&gt;&amp;nbsp;in your code.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kind Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Abhijith&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VL53L3X interfacing problem with nrf52832</title><link>https://devzone.nordicsemi.com/thread/478656?ContentTypeID=1</link><pubDate>Mon, 15 Apr 2024 05:30:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47e8f71c-c3e8-4c7e-a8d8-39dfeb4634ae</guid><dc:creator>Ashleo</dc:creator><description>&lt;p&gt;Hii,&lt;/p&gt;
&lt;p&gt;Is anyone get the solution for this problem, To interfacing the VL53L3X with nrf52832&lt;span&gt;&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;Ashleo&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VL53L3X interfacing problem with nrf52832</title><link>https://devzone.nordicsemi.com/thread/478613?ContentTypeID=1</link><pubDate>Sat, 13 Apr 2024 05:25:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f3a079f-2788-4f2c-9de3-bcb56b5924f5</guid><dc:creator>Ashleo</dc:creator><description>&lt;p&gt;&lt;span style="font-size:inherit;"&gt;I had use address for this sensor is 0x29 , while in the given address in the dataseat is 0x52, Here is the reason for this , when i use the 0x52 address and use logic analyser its show nothing, and when i used 0x29 its show the graph . after that I used i2c scanner on arduino for this sensor the result was also 0x29, thats why I am using this address.&amp;nbsp;&lt;/span&gt;&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/Screenshot-2024_2D00_04_2D00_13-104853.png" /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: VL53L3X interfacing problem with nrf52832</title><link>https://devzone.nordicsemi.com/thread/478558?ContentTypeID=1</link><pubDate>Fri, 12 Apr 2024 12:55:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7d387192-cff4-42b8-ac9c-38af5a6709af</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;In the overlay you provided, the device address for the &lt;code&gt;vl53l0x&lt;/code&gt; sensor is set to &lt;code&gt;0x29&lt;/code&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Please make sure that the device address specified in your code matches this address. If your sensor has a different address, you will need to update it.&lt;/p&gt;
&lt;p&gt;The device not ready message can be because of a connection issue or the sensor not being powered properly.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind Regards,&lt;/p&gt;
&lt;p&gt;Abhijith&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>