I'm trying to do this update on windows:

>EasyLoader_M5StickV_v5.1.2.exe

But I get a window like this, while the S in a box flashes on the display:

[32m[INFO] COM Port Selected Manually:  COM7 
[INFO] Default baudrate is 115200 , later it may be changed to the value you set. 
[INFO] Trying to Enter the ISP Mode... 
._._._._._._._._._._._._._._._._._._._._

And then eventually "Failed" in the popup. I only get the one baudrate in the dialog, so I can't try to go slower. Any ideas on how I can make this go?

@m5stack I was using the version that comes up when you click "FirmwareBurner" in M5Flow on the PC. My version of M5Flow is 1.0.9.3: The M5burner that comes up doesn't appear to have a version.
Do you mean the beta version at the link? I don't know if you update the version that shows up in File Explorer properties, but both the version of M5Burner that I downloaded in March and the one I downloaded today claim version 1.0.0.0, and the M5Burner.exe versions are byte-for-byte identical.

I have noticed that, when the burner starts up (either independently, or through uiflow), it points to Esp32Cam-Nopsram-v1.0.1, and the Device is Esp32Camera.

When I click on e.g. UIFlow-v1.5.2, the Device remains Esp32Camera:

I found out by accident that it actually does burn the Esp32Camera firmware, because that firmware doesn't support WiFi, and neither did my image. The fix/workaround is to click on the firmware (e.g. UIFlow-v1.5.2) again, and then the device switches to M5Stack Core.

Caveat burner! :)

Poking around a bit:

wifiCfg.deviceCfg.get_wifi()
['fbi covert AP', 'letmein']

wifiCfg.deviceCfg.wifi_read_from_flash()
['not the cia', 'really']

This actually sort of makes sense in that I used not the cia with m5burner, but I called doConnect once with 'fbi covert AP` hard-coded.

Reflashing back to 1.4.5, I see that it is not the same:

>>> wifiCfg.deviceCfg.wifi_read_from_flash()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute deviceCfg'

>>> wifiCfg.wifi_read_from_flash()
['not the cia', 'really']

Ugh.

1.5.2 is the same as 1.5.1 though.

I want to access the pre-existing WiFi config from micropython, the one you setup with M5burner.

On 1.4.5, on the M5StickC, the SSID + password are stored in apps/config.json. This is cool, as I don't have to hard-code it into my apps.

On 1.5.1, on the Core/Gray, there does not appear to be any equivalent file, yet it still knows the information. How do I access it?

I tried wifi_history = machine.nvs_getstr("history") from WifiCfg.py, but machine doesn't have nvs_getstr().

Is there any way to get this now? I really don't want to go back to hard-coding!

As I'm not doing recursion explicitly, there must be something going on behind the scenes. Or I've got an error! Or maybe event-driven isn't clean and somehow keeps calling itself.

I decided to go to a polling loop instead and it seems to work a lot better.

Sometimes I get a stack dump almost immediately on starting the network, so maybe I'm skating close to the edge.

Connected. Network config: ('192.168.6.109', '255.255.255.0', '192.168.6.1', '192.168.6.1')
***ERROR*** A stack overflow in task mp_thread has been detected.
abort() was called at PC 0x400899a8 on core 1

ELF file SHA256: 0000000000000000000000000000000000000000000000000000000000000000

Backtrace: 0x400896a7:0x3ffb9160 0x40089991:0x3ffb9180 0x400899a8:0x3ffb91a0 0x4009220a:0x3ffb91c0 0x40093f98:0x3ffb91e0 0x40093f4e:0x3ffb91cc

I am getting:

  File "flowlib/hw/mpu6050.py", line 145, in acceleration
RuntimeError: maximum recursion depth exceeded

I'm using the timer and button events, and that may contribute, but how do I debug this? What is the maximum recursion depth, and can I display the current depth?