m5stack ToF vl53l0x unit will stop scanning I2C devices
-
When m5stack ToF sensor is connected to Gray Core, i2c_scanner could not find/detect internal Mpu9250
The scanning is stopping at :
"I2C device found at address 0x29 !"
If we will connect GYVL53L0X module from other supplier, we will get correct scanning results:
"I2C device found at address 0x29 !"
"I2C device found at address 0x68 !" -
@vvs551
Hey, Here's my result. My Gray Core works well.
https://github.com/tackelua/I2C_Scanner/blob/master/I2C_Scanner.ino
-
@watson without any chance for me
With ToF unit connected:
With disconnected ToF unit:
What is 0x75 in your listing?
-
@vvs551
0x75 is the address of IP5306 IC. Because this IC is customized. It is designed to communicate with M5Core through IIC. -
@watson Did you mean battery extension?
I have not 0x75 when scan I2C -
@vvs551
Hey, IP5306 was built in M5Core board without battery extension.How about M5Core running with I2C_Scanner.ino without any unit?
IP5306 was built in M5Core Fire, so the terminal will display two I2C addresses: 0x68(MPU9250), 0x75(IP5306).
IP5306 was built in M5Core Basic, so the terminal will display one I2C address: 0x75(IP5306).
-
@vvs551
What's the hardware version of your basic core? -
-
@watson there is scanning just 0x68 without any units/
You can see this listing in previous post -
@vvs551 Could you make a picture of the TOF PCB? The schematics are not yet available
I have a hypothesis on all this I2C issuses.But before just to exclude software bugs, please check to use the latest ESP32 Arduino core, at least V1.0.1 https://github.com/espressif/arduino-esp32/releases including all the recent I2C fixes.
-
@playthegame thank you for help!
I updated esp32-arduino with this link - nothing happens
The same result - just 0x68 in I2C scanner listing(