We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

Karl Ylvisaker — Wed, 20 Oct 2021 09:43:09 GMT

Hello again,

[quote user="ShubMane"]How to enable the multiple writes as well as multiple reads in the TWI.[/quote]

By this, do you mean multiple reads or writes without a stop condition in between?
If so, please see my mention of the SUSPEND flag in my previous comment.

[quote user="ShubMane"]if possible please send the example for multiple writes as well as multiple read.[/quote]

Unfortunately I do not have any example that demonstrate the use of the SUSPEND flag, but you could try it out by modifying the TWI sensor example, for instance.
If you intend to do this, you will have to change the TWI0_USE_EASY_DMA define to 0, so that the example uses the TWI driver (that has the SUSPEND option) rather than the TWIM driver (that does not have the SUSPEND option) behind the scenes.

Best regards,
Karl

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Wed, 20 Oct 2021 09:30:38 GMT

Hello Karl,

How to enable the multiple writes as well as multiple reads in the TWI.

if possible please send the example for multiple writes as well as multiple read.

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

Karl Ylvisaker — Thu, 23 Sep 2021 10:28:32 GMT

Hello again,

[quote user="ShubMane"]we had an interface with the hts221 with vl53l1x on TWI bus. hts221 is workingly fine but vl53l1x is not working fine.[/quote]

Are you saying that you connected the HTS221 in the exact same way as you have tried connecting the VL53l1X, and was able to communicate with it as expected?

[quote user="ShubMane"]because all the external sensor drivers provided in SDK having the register's address length is 8 bit.[/quote]

All TWI addresses are 7 bit, with the 8th bit of the byte indicating whether it is a read or a write command for the 7 bit address. Sometimes, this is concatinated into a single address, such as WHO_AM_I_READ or similar. All TWI addresses are 7 bit as per the specification.

[quote user="ShubMane"]For resolving the issue, can we have some options like multiple read or write???[/quote]

Sure, you can do multiple reads or writes in the same transaction if you would like (no STOP between reads, for example). You can do this by using the nrfx_twi_xfer with the SUSPEND flag.

I repeat myself because it would be very helpful to know for the continued debugging of this case:

[quote user="Karl Ylvisaker"]

Karl Ylvisaker said:
Which pins are you using for this on the nRF52832?

Exactly which pins on the nRF device are you trying to use for your TWI peripheral? Your drawing does not include this information.

Karl Ylvisaker said:
Do you have access to a logic analyzer, so we could take a look at what might be happening on the lines?

[/quote]

Please take a moment to answer these questions.

Best regards,
Karl

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Thu, 23 Sep 2021 07:10:44 GMT

Hello Karl,

For resolving the issue, can we have some options like multiple read or write???

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Thu, 23 Sep 2021 06:32:46 GMT

Hello Karl,

In the above, I am talking about the internal register's address length of the sensors for reading and writing in them. and not about the slave address.

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Thu, 23 Sep 2021 06:25:37 GMT

Hello Karl,

Suspecting that we had been found the issue regarding the I2C communication of the vl53l1x.

please refer to the image. (I2C) the frame format of VL53L1x.

Address length size is about to be 16 bit with the separation of the MSB[15:8] and LSB[7:0]. so we have seen the TWI driver regarding that, files are "nrf_drv_twi.h" and "nrf_drv_twi.c" files. so in the TWI driver, only 8 bits of data were allowed to be passed within them

might be this is an issue that happens for the I2C communication. because we had even checked all the external sensor drivers that are provided in the SDK for example HTS221 the address length size is 8 bit.

we had an interface with the hts221 with vl53l1x on TWI bus. hts221 is workingly fine but vl53l1x is not working fine.

The nrfx TWI driver was also enabled even we had that also checked.

please check for the issue and let us know. please refer to the I2C frame format of VL53L1X.

because all the external sensor drivers provided in SDK having the register's address length is 8 bit.

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

Karl Ylvisaker — Tue, 21 Sep 2021 12:14:32 GMT

Hello again, Shubham

Thank you for providing the drivers.
As mentioned I do not expect this to stem from a logical error in the officially supplied drivers, but it could stem from a mismatch in configuration. In your diagram you are using external pullup resistors. The nrfx TWI driver enables internal pullups by default. Have you disabled the internal pullups, since you are using external ones?
Please see these questions from my previous comment:

[quote user="ShubMane"]4. Please refer to the attached diagram. same connection configurations are working with ESP32.[/quote][quote user="Karl Ylvisaker"]Which pins are you using for this on the nRF52832?[/quote]

Exactly which pins on the nRF device are you trying to use for your TWI peripheral? Your drawing does not include this information.

[quote user="Karl Ylvisaker"]Do you have access to a logic analyzer, so we could take a look at what might be happening on the lines?[/quote]

Please answer these questions so we may proceed with the debugging of your issue.

Best regards,
Karl

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Tue, 21 Sep 2021 05:49:43 GMT

Hello Karl,

1. When we are going to interfacing the TOF sensor(VL53L1X) with ESP32. It is working absolutely fine with the ESP32 platform with Arduino IDE. I am attaching the library of the TOF sensor which is working on ESP32.

devzone.nordicsemi.com/.../VL53L1X.h devzone.nordicsemi.com/.../VL53L1X.cpp

2. It's giving the problem with the nRF52832 platform here I am attaching the library file of the TOF sensor given by the manufacturer (STMicroelectronics).

devzone.nordicsemi.com/.../vl53l1_5F00_platform.h devzone.nordicsemi.com/.../vl53l1_5F00_platform_5F00_log.h

devzone.nordicsemi.com/.../vl53l1_5F00_platform_5F00_user_5F00_config.h devzone.nordicsemi.com/.../vl53l1_5F00_platform_5F00_user_5F00_data.h

devzone.nordicsemi.com/.../vl53l1_5F00_platform_5F00_user_5F00_defines.h devzone.nordicsemi.com/.../vl53l1_5F00_types.h

3. Resistor value is from R1-R4 is 20k.

4. Please refer to the attached diagram. same connection configurations are working with ESP32.

5. Please refer to the attached library and help us with the TWI communication with the TOF sensor (VL53L1X).

Best regards,

Shubham

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Fri, 17 Sep 2021 11:46:45 GMT

Hello Karl,

1. Here is the detail for the hardware connection (nRF52832 -> VL53L1X).

2. According to me, there is nothing that goes wrong with the hardware connection

3. We had studied the datasheet of the VL53L1X.

4. Even there is no driver available in the SDK for this sensor. Can u provide the driver of this???

5. Please refer the image.

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

Karl Ylvisaker — Fri, 17 Sep 2021 11:19:50 GMT

Thank you for providing the drawing.
Which pins are you using for this on the nRF52832?
The TWI driver by default enables external pullups. Have you disabled these? How much resistance is the resistors R1-R4?
Could you also confirm whether or not you are working with a nRF52 DK?

[quote user="ShubMane"]2. According to me, there is nothing that goes wrong with the hardware connection[/quote]

Do you have access to a logic analyzer, so we could take a look at what might be happening on the lines?

[quote user="ShubMane"]4. Even there is no driver available in the SDK for this sensor. Can u provide the driver of this???[/quote]

Unfortunately we do not provide drivers for all third party sensors in our SDK, but if you have an existing driver written in C it should not require too much work to port it to the nRF52832.

Best regards,
Karl

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Fri, 17 Sep 2021 11:06:57 GMT

Hello Karl,

1. Here is the detail for the hardware connection (nRF52832 -> VL53L1X).

2. According to me, there is nothing that goes wrong with the hardware connection

3. We had studied the datasheet of the VL53L1X.

4. Even there is no driver available in the SDK for this sensor. Can u provide the driver of this???

5. Please refer the image.

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

Karl Ylvisaker — Fri, 17 Sep 2021 09:10:23 GMT

Hello again,

[quote user="ShubMane"]

1. I had tried with "Twi scanner code" but the slave device address was not found.

2. even I had again checked the hardware connections for it.

[/quote]

That is strange. Could you detail how you connected the nRF to the TWI slave? Which pins on the nRF is connected to which pins on the slave device, and how is the slave device powered? Could you also elaborate on how you have initialized the TWI - what configuration are you using?

[quote user="ShubMane"]3. for chacking the hardware connection We had tried to with ESP32 platform "I2C scanner code".[/quote]

How was your connections between the ESP32 and the TWI slave? What TWI configuration did you use on your ESP32 when you successfully found the device?

[quote user="ShubMane"]5. Is VL53L1X is compatible with NRF52832??? because even in basic TWI scanner code the device is not found [/quote]

No, as long as they both follow the TWI protocol there is no notion of compatibility, since none of the devices actually know what is on the other side of the connection - all they need to know is what will be coming in on the TWI pins, and what to do with that information.

Looking forward to resolving this issue together.

Best regards,
Karl

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

ShubMane — Fri, 17 Sep 2021 07:48:41 GMT

hello Karl,

1. I had tried with "Twi scanner code" but the slave device address was not found.

2. even I had again checked the hardware connections for it.

3. for chacking the hardware connection We had tried to with ESP32 platform "I2C scanner code".

4. on the ESP32 platform the slave address was found.

5. Is VL53L1X is compatible with NRF52832??? because even in basic TWI scanner code the device is not found

RE: We are trying to interface the VL53L1X with nrf52832. but "slave address = 0x52" is not getting reflected in the address register of TWI0.

Karl Ylvisaker — Tue, 14 Sep 2021 13:25:42 GMT

Hello,

You should first try to run the TWI Scanner example from the SDK to verify that your hardware connections is correct. The example will scan through all devices on the TWI bus and report any found devices in the log. If all your hardware connections are correct and the TWI Slave is operating as intended it will be found here.

Please also make sure that you have DEBUG defined in your preprocessor defines, like shown in the included image.

This will make a detailed error message be output by your logger in the case that a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.

Are you using the TWI or TWIM driver in your application? It would be helpful to see the section of the code where you are using the TWI peripheral.

For future reference, please use the Insert -> Code option when sharing code here on DevZone.

On another note it seems that you are getting a lot of non-zero error codes in your log - what are these, and where do they originate?

Best regards,
Karl