VL53L5CX-SATEL connect to Pixhawk

-

This sensor has one of the worst documentation on the internet. It took me too long to start I2C communication with it so I decided to write the notes here.

My initial goal was to write a driver for PX4 Autopilot, so here are my findings.

I2C address
The address 0x52 mentioned in VL53L5CX documentation is the one shifted to the left. So the real address is actually 0x29.

i2cdetect PX4
If you going to use the i2cdetect application from PX4 you will not be able to read any address because VL53L5CX doesn't respond with the ACK for some reason that I didn't investigate.

Connecting the wires
To connect wires you need to connect AVDD and PWREN to 5V.

VL53L5CX PX4

 

The board has a 3.3V voltage regulator that turns 5V to 3.3V. You can reuse it to connect it to the EVK_IOVDD pin, so you don't need to wire an extra pin and it is very useful for a PX4 I2C standard connector.

VL53L5CX-SATEL schematic


With this setup, you will be able to connect VL53L5CX to Pixhawk without the need for a 3.3V wire.



If this saves you some time you can thank me by buying me a coffee.

Buy Me A Coffee



Comments

Post a Comment

Popular posts from this blog

AUTOSAR and CRC calculation

-
Image
If you find yourself reading AUTOSAR document Specification of CRC Routines you are probably looking for a solution on how to implement it in your code. This is short instruction without explaining how CRC works. It includes working CRC code with examples from the mentioned documentation. Explanation of CRC8 CRC 8 it means, the polynomial of CRC is 8 bit long.  Explaining chapter 7.2.1: CRC result width - it is the return value, it says it is 8 bits long Polynomial - this value is used to calculate CRC. In this case, it is 0x1D Initial value - CRC calculation start with this value. It is usually all F's or zeros.  Input data reflection - it says if the data which you want to do CRC need to be reflected or not. Example of data reflection: hex: 0x73 or binary: 1110011, reflected value is: 1100111 or hex 0x67 Result data reflected - same as input data, but the only result is reflected XOR value - result value need to be XOR-ed with this value before...
Read more

Flashing/debugging/running code at external memory in the memory-mapped mode

-
Image
  STM32 microcontrollers have special capabilities running code directly from external flash. To make it possible STM32 made a special set of instructions called memory-mapped mode where the microcontroller is reading instructions from the external flash. Since to read data from an external flash can take some time there is QSPI protocol witch basically four wires used as SPI MISO (Master Input Slave Output) to make throughput 4x time faster than classical SPI.   Figure 1 - Illustration of STM32H750 connected to W25Q128JV 
Read more

Debugging EK-TM4C123GXL with Visual Studio Code on Linux

-
Image
If you have TM4C123G LaunchPad Evaluation Kit and you like Visual Studio Code here is how to setup debugging on this board. This is the tutorial how to do that on clean Ubuntu 16.04 LTS. ARM GCC Compiler Setup Download the latest GCC cross compiler for the ARM from here:  https://launchpad.net/gcc-arm-embedded/+download In the time of writing this text, the last one is    gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 Run this commands in Linux console. wget https://launchpad.net/gcc-arm-embedded/5.0/5-2016-q3-update/+download/gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 tar -jxf gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 rm gcc-arm-none-eabi-5_4-2016q3-20160926-linux.tar.bz2 exportline="export PATH=$HOME/gcc-arm-none-eabi-5_4-2016q3/bin:\$PATH" echo $exportline >> ~/.profile source ~/.profile sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install libc6:i386 lib32ncurses5 Without i386 architecture ...
Read more