Upgrading Espressif 32 from 3.3.0 to 3.3.1 broke everything #599
Comments
|
Hi @GeorgeFlorian !
FYI, you can always roll back to the previous version of the platform in your [env:esp32doit-devkit-v1]
platform = espressif32@3.3.0
board = esp32dev
framework = arduino
...
What were the errors exactly?
PlatformIO doesn't touch your configuration files unless you're editing them using the
The PlatformIO build system is sensitive to the version of Python interpreter you're using. For some reason several internal packages were installed for Python 3.9, but from the logs above you're trying to run PlatformIO using Python 3.8. If this what you want, then try to run
Looking at your configuration the only potential change that might have caused the issue comes from #584 . The flash mode is now set according to the value in the board manifest, so please make sure the new value is good for your board. |
I just did this:
I have a strange behavior with Platformio where some libraries that are linked in I have no idea how to get only one library instead of two. If I delete one library from the /libdeps directory it just get's downloaded back on the next build command. On the 3.3.1 version the libraries conflicted with each other.
I think this happened when I was trying to get rid of the doubled libraries by uninstalling them from
I have used the same configuration for the past year or so and I have never had troubles with it: I am using a DevKitV4 with a Wrover-B on it.
This is oblivious to me. |
It's quite hard to guess whether those errors are related without the additional information, but I suppose you managed to get rid of them?
You specified your library dependencies as github repos without any specific labels, so when there are new commits in those repos PlatformIO will pull that changes automatically (and back up previous versions). I'd recommend you to remove the entire
That's true, PlatformIO modify your
Any reason why you used
It might be a good idea to delete the current PlatformIO installation and reinstall everything from scratch. Try deleting the folder |
I have deleted the library links from
I have been doing this all day, they just get downloaded in doubles again.
I had no idea this might happen. I was trying to get rid of the double libraries.
I don't remember why I've been using
|
Please don't do that, just delete the
Good, let's stick to the configuration without this line.
How you're compiling your project then? In first post you even specified the output from the |
|
Bump. I am having this same issue. I updated to see if there was a bugfix for a well-known Wifi bug and it broke my entire vscode/platformio environment. I cannot compile a project that was working before the update to 3.3.1 I get the following error:
Note this is my own project source file, but What is worse is that I cannot revert the changes! I've deleted my pio folder, cleaned the project, restarted VSCode, even manually uninstalled all espidf packages through the platformIO menu but everytime I build I come up with the same error. Below is my platformio.ini config. You can see I am declaring and specifying 3.3.0 but I am still getting the same errors and stuff from 3.3.1. This has halted all my development when I actually find time to code and work on stuff. What is a guaranteed workaround or solution to getting the old version of the framework working? At this rate, I might have to restore to a snapshot in my virtual machine and re-pull from github just to get my development environment back. Seems crazy. |
|
Hi @RoscoeTheDog ! Could you please put together a a minimal example to reproduce the issue? Also, you sure you were using v3.3.0 before the update to 3.3.1? |
|
@valeros It is entirely possible that 3.3.0 is newer than what I'm working with currently and also has problems building. I restored a snapshot of my vm and after checking the versions of what I was previously using, it seems they were older that. The question still stands though: Why is this happening? How has this gone undetected in 3.3.0? Is it with the s2 board only?
|
|
According to the screenshot you used ESP-IDF v4.2.1, so I suppose rolling back to |
I just checked the espidf latest documentation to see if the modules and methods in the older versions of IDF I was using prior are still used in the new one and they are. So why would they fail to build on new versions of idf? It seems like there is likely something else going on here unrelated to IDF compatibility unless I am missing something EDIT: I am not too sure why there was inconsistancy in my build error reports but with a full clean and re-build, I only had 1 error which was that method vTaskList() I mentioned earlier. I guess they must have removed it in the newer version of idf? commenting out this call got me successfully building on the newest version. |
|
@RoscoeTheDog Could you please put together a minimal example to reproduce the issue? |
|
Just FYI after update I have similar issue: After changing to
From qio it works but its very confusing and why does it do that? |
|
Feel free to reopen the issue if the problem persists with the latest version of the |
Configuration
Operating system: Linux Mint
PlatformIO Version (
platformio --version):Description of problem
Upgrading Espressif 32 from 3.3.0 to 3.3.1 broke everything.
I have errors inside libraries where I did not have before.
platformio.ini modified itself after the update.
I have no idea why it says Incompatible above.
Not even the simplest Blink sketch works.
Steps to Reproduce
Actual Results
Expected Results
Whatever the blink project should output.
If problems with PlatformIO Build System:
The content of
platformio.ini:Source file to reproduce issue:
Additional info
I was making some finishes touches on a project when I decided to upgrade from Espressif 32 3.3.0 to 3.3.1 and nothing worked since.
Also, on that project, the platformio.ini file modified itself after the update.
FROM:
TO:
The text was updated successfully, but these errors were encountered: