I have been having trouble with modules appearing to “lock up”. I have traced the problem to an errant build (or brand new modules) presenting the setup dialog prompt at startup, and my app on the other CPU sending data during this time, putting the module into the menu. In trying to fix this, I managed to hose a few modules, so I need to recover them with the short pins/TFTP method.
So, I’m trying to rebuild my app to remove the dialog, and in the process ESP prompts me to install updates, and I do. I also build a new FTP server sample project to use for the TFTP program to get a base install that should be close to what’s in a brand new module.
I power up with the pins shorted, the TFTPD32 program shows the module connect and download the image.bin of the FTP sample, and I release the short and wait for the module to reboot. So far, so good, this all works as expected.
However, when the module reboots and I connect via FTP and try to send the image.bin of my app (or any other app, including old versions), I get an FTP error.
For example, using the Windows command line FTP:
Connected to 126.96.36.199.
220 NET+OS 7.4.2 FTP server ready.
User (188.8.131.52:(none)): root
331 User root OK, send password.
230 Password OK.
200 Type set to I.
ftp> put image.bin
200 PORT command Ok.
425 Unable to open data connection, network error
There is probably 20 seconds of delay between the 200 line and the 425 line.
What could be the problem here? DigiESP is up to date on 7.4 as of yesterday.