Using latest esp32-wifi-lib version with esp-idf-v3.1

[davdav]

Hi,

If I checkout esp-idf v3.1, the submodule are aligned to that release (for example esp32-wifi-lib is aligned to commit 1373c2075a9524437cbb4bdfd8576dedb77c68a2).

If I want to upgrade esp32-wifi-lib to a version which should solve some issue, I go into $IDF_PATH/components/esp32/lib folder and I manually checkout a more recent commit (for example the latest commit b9578281990fea536f05d1a6d511c323cedfc50a) with git command

Code: Select all

 git checkout b9578281990fea536f05d1a6d511c323cedfc50a

My question: is it a good idea to do that? In practice, esp-idf v3.1 (in general any release) can work with a different version of esp32-wifi-lib (or esp32-bt-lib)?

Thanks

[ESP_igrr]

No, this is not a good idea. Manually changing submodule versions will result in a version which may easily be broken. Worst case, it will not be immediately obvious that it is broken, and you will only see some occasional weird issues.

If there is some bug that is fixed in master branch but is still present in the release branch, please comment to that effect on the corresponding Github issue (or create new one, if it does not exist). We do monthly bugfix releases and can backport the fix.

[davdav]

If there is some bug that is fixed in master branch but is still present in the release branch, please comment to that effect on the corresponding Github issue (or create new one, if it does not exist). We do monthly bugfix releases and can backport the fix.

Thank you @ESP_igrr. This means I have to test both master and the release version of esp-idf. Being master the "bleed-edge" it could have other issue which I can misunderstand or I'm not able to debug in the same way.

Can I just open an issue on github, asking to espressif dev team to review and possibly porting esp32-wifi-lib and esp32-bt-lib latest bugfix on version v3.1?

Thanks

[ESP_igrr]

In general, we are back porting fixes from master branch to v3.1 at the moment. I'm afraid you would need to be a bit more specific, which issue you are still seeing on the release branch. If you can describe the issue, then of course do open an issue on GitHub.

[davdav]

OK good. Thanks