-
Notifications
You must be signed in to change notification settings - Fork 7.6k
I2C not communicating with slave device #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have HTU21 here, no clue if it's DF though... will try the code above, but please share the rest of it so I can test both sensors here. |
I'm looking deeper into it and can see other issues also |
I've done what I can in my latest commit. From all of the devices that I tested, only that device and AM2320 do not respond. I tested IMUs, barometers, oled and 1602 screens, RTC and some more. All showed in scan. |
My testing result: BMP085, BMP180, SSD1306 OLED can be found by scanning i2c |
please try the latest commit! it should be all good now :) |
I'm unable to find my PCF8563, but was able to find some old DS1307, even though it gave me a weird reading, and printed out it found a dozen devices when I was searching for the DS1307. I'm going to test other i2c devices this evening. |
testing today: the sensors have 10K pullups on SDA/SCL |
this get's more and more interesting :D |
yeah i will bring home a salae logic over the holiday and see if i can see what is up |
wait for data to be latched and increase timeout in attempt to fix clock stretch issues Connected issues: http://esp32.com/viewtopic.php?f=19&t=632&p=2832#p2801 #81 #53 #11
try the latest commit please :) |
@ladyada is there any way that you can prepare a pack of the most used i2c/spi devices/sensors that I can purchase from you? Having the most common devices to test could greatly help to improve libraries. I have PayPal that I can use to pay. |
many many things have been fixed in I2C. I'm closing this issue now, if someone still has problems, feel free to reopen |
oof apologies i didnt see your reply - i did just retest with a wide variety of i2c sensors and all are working now. once i have more than one ESP32 feather ill get you a kit! |
Thanks :) That would be great! |
Can anyone give me some instruction on using a DS3231 with a nodeMCU-32S (pins and library to use) ? |
Add missing '!' to shebang line in some bash scripts
wait for data to be latched and increase timeout in attempt to fix clock stretch issues Connected issues: http://esp32.com/viewtopic.php?f=19&t=632&p=2832#p2801 espressif/arduino-esp32#81 espressif/arduino-esp32#53 espressif/arduino-esp32#11
wait for data to be latched and increase timeout in attempt to fix clock stretch issues Connected issues: http://esp32.com/viewtopic.php?f=19&t=632&p=2832#p2801 espressif/arduino-esp32#81 espressif/arduino-esp32#53 espressif/arduino-esp32#11
I tried an HTU21DF (temperature and humidity) and a BMP180 (barometric pressure) but the drivers do not get past the first I2C transmission. Both sensors work on an ESP8266.
The first thing the HTU21DF driver does is send a RESET command like this. Writing to this register forces the sensor to factory defaults.
This is what it looks like on an Uno.
Here is what happens on my ESP32. If other people have I2C working, the problem must be in my setup or ESP32.
Since there is a NAK, the driver aborts the rest of the transmission.
I am trying various changes to esp32-hal-i2c.c but have not made any progress.
The text was updated successfully, but these errors were encountered: