This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-MSP430FR2476: Setting up I2C where a VL6180X-SATEL TOF sensor is the slave device

Part Number: LP-MSP430FR2476
Other Parts Discussed in Thread: MSP430FR2476

I'm trying to set up an I2C connection where a VL6180X-SATEL is the slave device with the master device being the MSP430FR2476. From what I've read from design documents I believe I want to use the SCL and SDA lines available on the MSP's pins 4.5 and 4.6 and for powering the VL6180X-SATEL (which is labelled as taking in a 2.8V source) I was hoping I could maybe use the 3.3V pin on the MSP. Hopefully at the end I'm trying to utilize the i2c.h library in CCS to write some C code which can allow me to read the time of flight distance sensor on the VL6180X. I'm fairly new to all of this, any and all advice on how to get started with this would be appreciated. I'll attach the design/spec documents for both devices and the pictures are a rough attempt at trying to get these working together (in photos no power is plugged as I was unsure if 3.3V pin to 2.8V connection was safe for the VL6180X-SATEL).

vl6180x-satel user's guide.pdf

MSP430FR2476 User's Guide.pdf

  • Based on DocID027253 (which you attached) Fig 3, there is a regulator (TPS76928) down to 2.8V, so you can supply the board with 3.3V as you planned.

    There do not appear to be any pullups on the Satellite board, so you need to supply them. Per DocID027252 (UM1852) Fig 10, they are supplied by the parent (X-Nucleo-6180XA1) board, pulling up to 3.3V, so evidently that's OK. You might get away with using the MSP430 internal pullups if you don't run the I2C too fast.

    In order to use P4.4/5 for UCB0, you need to set SYSCFG2:USCIB0RMP. [Ref User Guide (SLAU445I) Table 1-31 and data sheet (SLASEO7B) Table 6-11.]

    You didn't mention software. ST offers an API (STSW-IMG003).  I haven't used that, but I've used the analogous packages for the VL53 series. Those are structured so you  just supply an I2C driver with a few "glue" functions. The main catch was that they were large (maybe 45KB of code). I used an FR5994, but if you squeeze a bit it might fit on an FR2476.

  • Hi Andrew,

    Any update about your issue? Do you still need our support?

    Best Regards

    Johnson

**Attention** This is a public forum