nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

Hakon — Thu, 01 Jun 2023 09:02:52 GMT

[quote user="sunilhalvi"]Now, If I want to change slave address of 'vl53l1xdev1'(a i2c_dt_spec object), I should post a question in ST community?[/quote]

Yes, you can try that. I can't promise that they will know the solution, but you should still try.

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

sunil kumar — Wed, 31 May 2023 13:01:06 GMT

Hi Hakon,

I am little confused here, I have declared new node in .overlay file like shown below

  &i2c2{
      vl53l1x: vl53l1x@30{
            compatible = "st,vl53l1x";
            reg = < 0x30 >;
            label = "MYSENSOR2";        
            int-gpios= <&gpio0 13 (GPIO_ACTIVE_HIGH)>;        
        };  
    }

And, I have declared a variable like shown below

const struct device *const Vl53l1xdev1 = DEVICE_DT_GET(DT_NODELABEL(vl53l1x));

Now, If I want to change slave address of 'vl53l1xdev1'(a i2c_dt_spec object), I should post a question in ST community?

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

Hakon — Wed, 31 May 2023 12:14:48 GMT

This is not a driver provided by Nordic. It is a device driver developed and maintained by the ST software team. The driver has just been ported to Zephyr, which is part of NCS. You will most likely get an answer to your question if you contact the ST community.

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

sunil kumar — Wed, 31 May 2023 11:00:53 GMT

Hi Hakon

Could you please reply to my queries as early as possible. If you can just confirm if nRF connect SDK and VL53L1X driver is capable of changing I2C slave address during run time will be very helpful.

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

sunil kumar — Tue, 30 May 2023 11:59:38 GMT

I have VL53L1X sensor driver that I got from Nordic's git repo. My question is, how to change the slave address of the vl53l1x sensor during the run and continue communicating with it with the new slave address?

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

Hakon — Tue, 30 May 2023 11:43:41 GMT

[quote user="sunilhalvi"]I use VL53L1X sensor driver provided Nordic semiconductor.[/quote]

Nordic has not implemented this driver. Have you tried asking the STM community about this?

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

sunil kumar — Tue, 23 May 2023 16:45:53 GMT

I use VL53L1X sensor driver provided Nordic semiconductor. This driver has a source file called vl53l1x.c. In this source file, a function is defined for initializing sensor here is its signature

int vl53l1x_init(const struct device *dev)

The 'dev' parameter in above function is used for I2C communication with sensor. It holds the slave address that we define in .overlay file. I am referring to this structure object. I need to change the slave address of vl53l1x sensor during runtime and update the same in this object. Or, is there a way vl53l1x driver updates the slave address during run time.

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

Hakon — Tue, 23 May 2023 15:39:14 GMT

Hello,

[quote user=""]Now, we are looking for an API function for our nRF9160 to update the slave address in the I2C handler. [/quote]

which "I2C handler" are you referring to? Are you talking about the nrfx driver?

RE: nrf9160 working with nRF Connect SDK 2.3.0. Need to change slave address of VL53L1X sensor

Amanda Hsieh — Fri, 19 May 2023 15:24:49 GMT

Hi,

We are short-staffed this week due to Public Holidays in Norway. We will be back on Monday 22nd and hope to be able to answer all incoming requests within a couple of days, depending on the backlog. I am sorry for the inconvenience.

Best regards,
Amanda H.