Possible bugs in extension v1.0.3
Posted: Wed May 05, 2021 8:34 am
I am not posting under the issues/bugs forum because I am not whether these are bugs or I am doing something wrong.
The thing is that I only started getting these issue after the v1.0.3 extension update. The previous extension version was no issue.
Latest version of vscode
Windows 10 (64 bit)
esp v4.2
extension 1.0.3
python 3.9
1.
Using the lightning bolt icon to compile/flash/monitor does not copy spiffs folder for copying FLASH IN PROJECT
If I use the lightning bolt for projects that contain files to write into spiffs partition at flssh time, the spiffs fails to mount and then fails to find files. Note: If I use spiffs without flashing to chip (ie. write, read, delete file etc) then that works ok.
If I open esp-idf terminal and type manually "idf.py flash monitor" then the files do get flashed ok and project runs ok.
2. If I attempt to to a full-clean after using the cog icon to launch sdk config gui , I get a lock error relating to "rmdir" (even if I discard and close the config window). If I now exit vscode and re-start then I can do full-clean.
The thing is that I only started getting these issue after the v1.0.3 extension update. The previous extension version was no issue.
Latest version of vscode
Windows 10 (64 bit)
esp v4.2
extension 1.0.3
python 3.9
1.
Using the lightning bolt icon to compile/flash/monitor does not copy spiffs folder for copying FLASH IN PROJECT
If I use the lightning bolt for projects that contain files to write into spiffs partition at flssh time, the spiffs fails to mount and then fails to find files. Note: If I use spiffs without flashing to chip (ie. write, read, delete file etc) then that works ok.
If I open esp-idf terminal and type manually "idf.py flash monitor" then the files do get flashed ok and project runs ok.
2. If I attempt to to a full-clean after using the cog icon to launch sdk config gui , I get a lock error relating to "rmdir" (even if I discard and close the config window). If I now exit vscode and re-start then I can do full-clean.