board unresponsive after main.py file activation.
Posted: Mon May 11, 2020 11:10 am
Hi all.
I have an adafruit feather HUZZAH and I'm trying to use micropython for the first time. There seemed to be an issue that I can flash micropython on to the board and everything seems to work fine. I'll then use mpfshell to put the main.py file that just set some of the pins and flashes an LED ten times. Upon the reset the board is activated and the code run but nothing is accessible. mpfshell is no longer responsive, I tried using picocom to access the repl and that doesn't work either. Rebooting or power cycling simply re-runs the the main.py but I can't access or replace it the main.py anymore. The only way to get it functioning again is to esptool erase flash it and then reupload the firmware however the same problem is still in place where as soon as the board is run with a main.py the board is no longer responsive.
I'm using a MacBook and the screen is also unresponsive after the first run. I also tried using an older version of the esp8266 firmware but with the same outcome so I'm not sure what I'm doing wrong or what I should try next.
I have an adafruit feather HUZZAH and I'm trying to use micropython for the first time. There seemed to be an issue that I can flash micropython on to the board and everything seems to work fine. I'll then use mpfshell to put the main.py file that just set some of the pins and flashes an LED ten times. Upon the reset the board is activated and the code run but nothing is accessible. mpfshell is no longer responsive, I tried using picocom to access the repl and that doesn't work either. Rebooting or power cycling simply re-runs the the main.py but I can't access or replace it the main.py anymore. The only way to get it functioning again is to esptool erase flash it and then reupload the firmware however the same problem is still in place where as soon as the board is run with a main.py the board is no longer responsive.
I'm using a MacBook and the screen is also unresponsive after the first run. I also tried using an older version of the esp8266 firmware but with the same outcome so I'm not sure what I'm doing wrong or what I should try next.