Skip to content
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 Conflict! i2c冲突 (IDFGH-14215) #15012

Open
3 tasks done
likestones opened this issue Dec 10, 2024 · 4 comments
Open
3 tasks done

i2c Conflict! i2c冲突 (IDFGH-14215) #15012

likestones opened this issue Dec 10, 2024 · 4 comments
Labels
Status: Opened Issue is new

Comments

@likestones
Copy link

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.

v5.3.2

Operating System used.

Windows

How did you build your project?

Command line with idf.py

If you are using Windows, please specify command line type.

CMD

What is the expected behavior?

He was supposed to burn and run normally

What is the actual behavior?

Unlimited restart after burning and display through monitor says i2c:COnFLIcT! driver ng is not allowed to be used with this old driver□

Steps to reproduce.

1.idf.py build
2.idf.py flash
3.idf.py monitor

Build or installation Logs.

i2c:COFLIcT! driver ng is not allowed to be used with this old driver□[0m
12:56:25.773]
bort()was calledatP0x420ca4abon core 0
Backtrace: 0x40379eae:0x3foeb100 0x40383e49:0x3foeb1e0 0x4038bab5:0x3fceb200 0x420ea4ab:0x3fceb270 0x420038e3.0x
0x4200395a:0x3fceb2b0 0x40379a4a.0x3fceb2d0 0x403c0941:0x3fcb340 0x403c0037:0x3fceb380 0x40308959:0x3foeb4b0
0x40045001:0x3fceb570 0x40043ab6:0x3fceb6f0 0x40034045:0x3fceb710

More Information.

No response

@likestones likestones added the Type: Bug bugs in IDF label Dec 10, 2024
@github-actions github-actions bot changed the title i2c Conflict! i2c冲突 i2c Conflict! i2c冲突 (IDFGH-14215) Dec 10, 2024
@espressif-bot espressif-bot added the Status: Opened Issue is new label Dec 10, 2024
@suda-morris
Copy link
Collaborator

This error message could happen when you use two components, where component A is constructed based on the legacy i2c driver and component B is constructed based on the new i2c driver. In general, we don't expect the user to use both of them in the same application.

@mythbuster5 mythbuster5 removed the Type: Bug bugs in IDF label Dec 11, 2024
@ammaree
Copy link

ammaree commented Dec 11, 2024

@suda-morris
@mythbuster5

I am having the same problem but with 1 specific device model only, the ESP32-S#-LCD-EV2 board using the latest BSP for this device.

As far as I can recall the BSP (used to?) use some mechanism for auto detecting the I2C driver/module being used. Is it possible that both drivers somehow get linked in here?

@likestones
Copy link
Author

Oh, I found it. I used an audio codec device. You need to close idf.Py menuconifg ->Component config ->Audio Code Device Configuration ->Enable backward compatibility for the I2c driver (force use of the old I2c_driver above v5.3)

@ammaree
Copy link

ammaree commented Dec 11, 2024

Obviously a new setting, either related to latest master IDF or latest BSF.
Disabled same setting, boots now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new
Projects
None yet
Development

No branches or pull requests

5 participants