-
Notifications
You must be signed in to change notification settings - Fork 105
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
能否更新I2C驱动? (BSP-551) #391
Comments
@espressif2022 thank for the response, but not sure I understand. Will I2C v2 driver functionality be added to all the devboard BSP's? -or- Will I2C v2 driver functionality be added specifically to the ESP32-S3-BOX-3 BSP, as this issue requests? |
Hello @ammaree, |
Hi @espzav Thanks for the response, and sorry to bother again, but just trying to get clarity on specifics. Our order of priority would be:
We understand and accept that your priorities might be different but would really appreciate if you can: Thanks in advance, the info will help a lot. |
With this change we also must upgrade to IDF v5.4, because esp32-camera supports Driver-NG only from v5.4 onwards. Relates to #391
With this change we also must upgrade to IDF v5.4, because esp32-camera supports Driver-NG only from v5.4 onwards. Relates to #391
With this change we also must upgrade to IDF v5.4, because esp32-camera supports Driver-NG only from v5.4 onwards. Relates to #391
With this change we also must upgrade to IDF v5.4, because esp32-camera supports Driver-NG only from v5.4 onwards. Relates to #391
Update
|
Has the ESP32-S3-LCD-EV-BOARD been updated to support I2C version 2? |
Not yet, it is the next one on our list |
Related area
Driver
Hardware specification
ESP32-S3-BOX-3
Is your feature request related to a problem?
我在 ESP-ADF 中使用 BSP 中的 ESO-BOX-3,其中的 I2C 都使用的都是旧的驱动,包括示例也是,能否更新新的I2C驱动?
Describe the solution you'd like
在 ESP-ADF 中调用初始化接口函数
Describe alternatives you've considered
No response
Additional context
No response
I have checked existing list of Feature requests and the Contribution Guide
The text was updated successfully, but these errors were encountered: