Installing framework on ESP32 s2 wemos S2mini

[mackyb27]

I'm frustrated with wemos S2mini, not sure what is going on. It works in Arduino IDE and uplaoding sketches, but nanoff has issues. It seems the communication is slow, it detects the chip, downloads image but then dies on backup creation due to the timeout. And this takes several minutes. Is there any catch to this board or was anyone able to use it? Spec wise it is a very good board, even has 2mb PSRAM, cheap too.

kind regards, martin

[alberk8]

Try to add the --masserase to the nanoff command, that should skip the backup.

[josesimoes]

Hi @mackyb27!

I haven't played with that board, so here's my general guidance for S2.
You can skip the backup part by adding --nobackupconfig that will make the update process very quick.

Usually with S2 you have to put the board in bootloader mode, do the flashing with nanoff and then reset to get it back to operation. I suppose you've been doing that.

[mackyb27]

Thx all for all suggestions however thebresultbis the same and there seems to be some other issue. Not sure how to approach this. It nanoff takes forever to determine the chip. Arduino IDE has no problems once it enters boot mode. However if it is not in boot mode than it is not visible on USB in ports. As it not there at all. V pon., 31. mar. 2025, 12:58 je oseba José Simões ***@***.***> napisala:

…

Hi @mackyb27 <https://github.com/mackyb27>! I haven't played with that board, so here's my general guidance for S2. You can skip the backup part by adding --nobackupconfig that will make the update process very quick. Usually with S2 you have to put the board in bootloader mode, do the flashing with nanoff and then reset to get it back to operation. I suppose you've been doing that. — Reply to this email directly, view it on GitHub <#1620 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB7ERPQQ3TK3W546PV2643T2XENWXAVCNFSM6AAAAAB2DYGBWGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRXGUYTQMY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mackyb27]

Forgot to attach the output: nanoff --target ESP32_S2_USB --serialport COM5 --update --masserase .NET nanoFramework Firmware Flasher v2.5.126+716b21797a Copyright (C) 2019 .NET Foundation and nanoFramework project contributors Reading details from chip...OK Connected to: ESP32-S2 (ESP32-S2FNR2 (revision v0.0)) Features WiFi, Embedded Flash 4MB, Embedded PSRAM 2MB, ADC and temperature sensor calibration in BLK2 of efuse V2 Flash size 4MB unknown from ST (manufacturer 0x32 device 0x16406) PSRAM: undetermined Crystal 40MHz MAC 84:FC:E6:C5:74:5E Extracting ESP32_S2_USB-1.12.4.38.zip...OK Updating to 1.12.4.38 Erasing flash...Error E4000: Error executing esptool command. (esptool.py v4.8.1 Serial port COM5 A fatal error occurred: Could not open COM5, the port is busy or doesn't exist. (Cannot configure port, something went wrong. Original message: OSError(22, 'The semaphore timeout period has expired.', None, 121)) V V pon., 31. mar. 2025 ob 15:55 je oseba Martin Butina < ***@***.***> napisala:

…

Thx all for all suggestions however thebresultbis the same and there seems to be some other issue. Not sure how to approach this. It nanoff takes forever to determine the chip. Arduino IDE has no problems once it enters boot mode. However if it is not in boot mode than it is not visible on USB in ports. As it not there at all. V pon., 31. mar. 2025, 12:58 je oseba José Simões < ***@***.***> napisala: > Hi @mackyb27 <https://github.com/mackyb27>! > > I haven't played with that board, so here's my general guidance for S2. > You can skip the backup part by adding --nobackupconfig that will make > the update process very quick. > > Usually with S2 you have to put the board in bootloader mode, do the > flashing with nanoff and then reset to get it back to operation. I suppose > you've been doing that. > > — > Reply to this email directly, view it on GitHub > <#1620 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB7ERPQQ3TK3W546PV2643T2XENWXAVCNFSM6AAAAAB2DYGBWGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRXGUYTQMY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >