You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to upload a new firmware to the board wcc tries to connect to the internet to get the description of the boards. So I can not use wcc on some machines with firewalls. The same applies if no internet connection exits.
It would help if i can set a local file for the boards configurations.
It would also help to specify more options for the internet connection (proxy, other protocols).
The text was updated successfully, but these errors were encountered:
I tried different tools but it does not work.
If I use the ESP32 Flash Download Tool, where can I find the images for a particular board (in this case M5STACK)?
you could easily create a custom "offline" version of wcc.
That version would use pre-downloaded local files instead of grabbing them from the servers.
You would need to provide
the file board.json in source file board.go around line 923 and 988
the file esptool.zip matching your OS in the source file download.go around line 99
the file firmware.zip matching your ESP32 device in the source file download.go around line 140
a lastcommit file matching the new firmware's commit-id in the source file main.go around line 368
If you can implement a clean solution that is 100% compatible to the current wcc and add a parameter, e.g. ' -offline ' to this standard wcc then you could even create a PR so that the functionality would be maintained for you in this project in the future.
When I try to upload a new firmware to the board wcc tries to connect to the internet to get the description of the boards. So I can not use wcc on some machines with firewalls. The same applies if no internet connection exits.
It would help if i can set a local file for the boards configurations.
It would also help to specify more options for the internet connection (proxy, other protocols).
The text was updated successfully, but these errors were encountered: