Can't flash ESP8266. Error: Module for path is not found
See original GitHub issueI cannot flash my ESP8266 board. I have ESP-07 module (not WEMOS D1 mini nor WEMOS D1 mini Pro). I successfully flash it with other IDEs - Arduino and esptool.py.
When I edit Run/Debug Configuration and select my USB/UART converter, it throw an error - Error: Module for path is not found
, see screenshot. Maybe it is because I have external usb/uart converter. I have latest Pycharm and Micropython plugin and Ubuntu 16.04 lts
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Can't flash ESP8266. Error: Module for path is not found #41
I cannot flash my ESP8266 board. I have ESP-07 module (not WEMOS D1 mini nor WEMOS D1 mini Pro). I successfully flash it...
Read more >ESP8266 Troubleshooting Guide - Random Nerd Tutorials
The ESP8266 has a few common issues when you are trying to flash a new firmware, uploading a script or during normal usage...
Read more >How to resolve “Board generic (platform esp8266, package ...
Restart Arduino IDE, go to Tools > Board: > Boards Manager and install the esp8266 / Arduino package again. Select ESP8266 module and...
Read more >How to Flash or Program ESP8266 AT Firmware by ... - YouTube
During flashing AT Firmware into ESP8266 module, it may encounter problem which unable to access AT mode after flashing successfully.
Read more >Update the Firmware in Your ESP8266 Wi-Fi Module - Projects
Press and hold the Reset button, and then press and hold the Flash button. Release the Reset button, and then release the Flash...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No problem @vlasovskikh, glad to help out as long as I am doing that and not confusing things 😃
I’ll take a look at the README.md update that you are reviewing and see if I can do something to make the setup steps a little clearer. Possibly just the high level overview steps as I outlined earlier in this thread will be enough.
@tarakanov - It was my understanding that when you create frozen modules or bytecode you are actually ‘baking’ these modules into a new ‘custom’ micropython firmware image which is then put on the board in a repeat of Step 1. There is no cycle of steps 4 and 5 because you have to rebuild the complete micropython firmware image from the full source with the appropriate toolchain in order to freeze the modules and include them in the image for loading on the device.