ESP32 IDF v5.0 Support

[MJU20]

Is there a way of letting us know when the V5 issues between FC10 and the IDF are solved (or at least stable?).

It's been a long while since there was a mailing, maybe if the V5 of the ESP IDF is stable?

[MJU20]

Any advance to report?

[chipfryer27]

Hi

Today, forgetting that the machine I'm using runs v5.0, I tried compiling a chart without success. It wouldn't connect to my SSID and it did take me longer than I care to admit to realise where the problem lay

However although the issue is documented elsewhere in this thread, I did discover something new to report. I added in a UART to send out "info" to my PC as the chart progressed, and whilst this did work it wasn't without issue. I'd set the UART to run at 9600 Baud but irrespective of what it's set at, it "defaults" to 115200.

Not seen that reported yet so thought I'd inform.

Regards

[chipfryer27]

Hi

Again, just for info, it looks like the I2C is problematic in v5. I documented an isue with an I2C OLED display in an earlier post, but an I2C sensor seems problematic too, so maybe it's the I2C?

Regards

[medelec35]

I have 5.1 installed and I2C LCD Backpack is working for me on the ESP32 C3 and Wroom.
With regard to UART, it's working for me with different Baud rates.
Was that with channel 1 or channel 2?
What is the sensor that is not working?

[chipfryer27]

Hi

BH1750, and it's also not working on an ESP32-Lolin compiled with v4.x Just sent a bug report re such.

Regards

[BenR]

Hello,

The UART stuck at a fixed baud of 115200 on the ESP32 has now been replicated. It seems to be a specific problem with IDF version 5.0.

The problem is fixed in IDF v5.1.

To move to IDF version 5.1 please do the following.

First click the Start menu and type in ESP, click the ESP-IDF Command Prompt shortcut that appears.

Type the following commands into the command promt window and press enter after each line, note each step may take a few minutes to complete.

Code: Select all

git fetch
git checkout release/v5.1
git pull
git submodule update -f --init --recursive
install.bat
python tools/idf_tools.py uninstall
python tools/idf_tools.py install-python-env

You may need to restart your computer at this point. You will also need to delete the current build files which are located in a folder next to your Flowcode project file with the same name. Just delete or rename the folder.

Now try compiling again using the Flowcode Build -> Compile to chip.

Let us know how you get on.

[chipfryer27]

Hi

Thanks for the update, I'll try later when I'm on a machine running v5 and will let you know how I get on.

Regards

[chipfryer27]

Hi

Not so good with progress.

First command failed due to "dubious ownership in repository" so I added the recommended exception.

That then allowed line 1 to run.
Line 2 failed as I'm informed that "release/v5.1 did not match any files known to git"

Regards

[medelec35]

Hello
Git can literally be a git!
Ben's method when working is way much quicker so it's a shame it does not work 100% of the time.
Here are my steps to upgrade/downgrade that have worked 100% of the time for me.
1. Right-click the Windows icon and select Apps and Features & enter idf within the search box and select uninstall.
2. Delete the idf and idf-tools folders that were created when first installing idf v4
3. Run the esp-idf-tools-setup-2.3.exe (ESP32 Toolchain) that you would of downloaded from here
Install as per instructions found here
I would recommend selecting release/v5.1 (release branch) version
Select to keep the existing Python and Git.
Don't go away from the PC while installing as there will be a point where admin elevation is required.
After installing it's important to restart PC otherwise compile errors could occur.
You should be good to go now.