NodeMCU-32S need burn firmware if the connection is disconnected and reconnected.

[alaj]

Board: NodeMCU-32S
uPyCraft version: 0.30, 1.1
Situation: connect the board with computer, and use uPyCraft to burn firmware(esp32). Then I can download and run program. But if I click disconnect button on uPyCraft and then click connect button again, it pop the dialog and ask me to burn firmware again. Every time I reconnect, I need to reburn firmware again. Is my operation wrong?

[jhlucky]

Upy comes with the latest firmware verision of ESP8266, 0721(note: you can check it throgh os.uname()). It will prompts upgrade if your version of the firmware of esp8266 lower than 0721. If you don't want to upgrade your firmware, you can set to ignore fireware upgrading at Tools->Preferences->config.

[White-Goblin]

I have the same issue. It is able to connect the first time without problems, but after disconnecting, I get prompted to burn firmware again. Changing the preferences does not fix the issue. This is for an esp32.

[alaj]

I set upy to ignore upgrading firmware. Still not working.

[SilvesterHsu]

I find that the connection may have time_out strategy. The connection time starts counting from the boot of my esp. If the time spending on the main programme is longer than a specific time, it would fail during connecting.

[smith-scot]

I have a similar issue; however I only notice the problem after I have connected the wifi. I can connect serially several times with no problems noticed. It is only after I have an active WiFi connection that I have the problem, and even after uPyCraft requests to burn firmware, I can go to another serial program (MobaXterm) and connect to the ESP32. There doesn't seem to be anything wrong with the ESP32. Any thoughts?

[SilvesterHsu]

@smith-scot I guess this will be related to the ESP runtime. If you use the wifi connection example provided by Micropython, you will find a process waiting for a wifi connection.

while not sta_if.isconnected():
    pass

This will wait for the router DHCP to assign an IP address, however this may exceed the IDE's timeout.

I use a MacBook, but the experience of this software on the mac is not very good, you can try the Windows version. And the version on Github seems to be slower to update, they have the same project on gitee, and the v1.1 version is released.

[smith-scot]

@SilvesterHsu I have been doing some additional testing, and the problem seems to be corrected when I skip the connect() function. I will need to perform some test so see if I can prevent this, but like you stated, the problem seems to be associated with a failure to sign into the Wifi network. I am currently using v1.1, I don't an option to increase the IDE's timeout. Does this option exist?

[SilvesterHsu]

@smith-scot Sorry, I didn't find that the timeout is optional. It is estimated that this is related to how the software is connected.
In addition, I also use ESPlorer frequently, which seems to be software developed by the Russians. ESPlorer does not have a timeout problem, it can load the program quite smoothly, and also provides the RTS button. It was always a pleasant time to develop on ESPlorer. However, the only problem is the file uploading bug.
The original author of ESPlorer seems to have stopped updating the software. Uploading the file sometimes fails, but Josverl modified the upload function and his version will be much more stable.

[chrissyast]

I am finding this same issue on uPyCraft v1.1, I changed CheckFirmware to no check but still get the prompt for firmware every time. Just wondering if any of you found any solutions since the last post? I don't see where is the connect() function that @smith-scot mentions.

I guess I will try ESPlorer and see how it works.

[larslundh]

I have a similar issue; however I only notice the problem after I have connected the wifi. I can connect serially several times with no problems noticed. It is only after I have an active WiFi connection that I have the problem, and even after uPyCraft requests to burn firmware, I can go to another serial program (MobaXterm) and connect to the ESP32. There doesn't seem to be anything wrong with the ESP32. Any thoughts?

---

Hello, I just want to Second that I have identical issue.
Just like you said, Serical communication works fine (as well as Webrepl if the micro is loading the wifi code from micropython.org) to add:
my suggestion is to delete the wifi code from your micro via Serial or Webrepl
control + C to stop it doing stuff, if its locked then...

import os
os.remove("main.py")
GG try re-connect (hopefully you put the wifi code there...)

[Aschhoff]

On Windows use my Tool:
https://github.com/Aschhoff/ESP-Autostart-Changer