I2C Failure After Launching HTTP Client Task (IDFGH-14322)

[kevinkfci]

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.

General issue report

Everything operates as designed and expected until a command is issued to activate the HTTP client task and download a file from the AWS cloud. I encountered a similar issue when testing OTA examples with the HTTP client.
Once the HTTP client is launched, it begins to interfere with the I2C portion of the code, producing the following error. Even after stopping the HTTP client task, the error messages persist on the console port and do not stop.
At this stage, I am confident that the HTTP client is the source of the problem. I have divided the code into smaller sections, integrated them into my project, and tested each part. The issue consistently occurs as soon as the HTTP client is called. I am not sure what I have missed or if there is any HTTP client patch I have overlooked. I have tried different task approaches, such as changing task priority, but none of them have helped.

I am using ESP-IDF version 4.4.5 and cannot use the latest code due to compatibility constraints.
please help!!!

I have attached the following files for reference:
bootuplog.txt
sdkconfig.txt
errormessage.txt
http_mp3_pwm.zip

[mythbuster5]

The error message is i2c driver not installed?

[kevinkfci]

I suspect the HTTP client is overwriting a memory section used by the I2C driver. I have several tasks utilizing I2C, and they work fine as long as the HTTP client-related task is not running. However, when I trigger the HTTP client task, error messages begin appearing, regardless of whether a file is being downloaded from AWS Cloud or not.

[mythbuster5]

I see your code but seems not very helpful. Maybe a minimum reproducable project (including app_main) interface would be helpful for debugging. Perhaps it's not an I2C issue seems.

[kevinkfci]

I try to put something together based on a dev-board. currently, it is ruing on our board.

[nileshkale123]

Hello @kevinkfci ,

Is this issue still occurring? If not, could you please share the steps you took to resolve it?

If the issue persists, feel free to reach out with a concise, reproducible example so we can assist you further in debugging.

[kevinkfci]

yes, it is still there, I have not found any solution yet.