@david95 I'm using Mac and can get the M5StickCplus working nicely. But cannot get the Core2 to connect over the serial port. I have had issues with the USB-C and power on some ESP devices. You might play with different cables, such as USB-A to USB-C vs straight UCB-C.

Having been successful for months with the OTA updates with all my ESP devices, all of a sudden the loop in the library Updater.cpp is failing (found via printouts).

file: ~/Library/Arduino15/packages/m5stack/hardware/esp32/2.0.4/libraries/Update/src/Updater.cpp

I successfully retrieve a 'bin' file from a web location (over http) and then get to the update loop.

Then the following never gets all the bits:

 size_t written = Update.writeStream(_client);

Inside the while loop of writeStream, there is a call:

toRead = data.readBytes(_buffer + _bufferLen, bytesToRead).

While sometimes reading 4096 bytes, eventually this returns 0 and after a number of times (300 in code) it quits with an UPDATE_ERROR_STREAM (#6) error. Sometimes it return 0 but after a couple tries works.

Anyone have any ideas on what might be the issue? Why would the readBytes in general not work?

Is this readBytes grabbing bits from the internet or from the binary already downloaded?

thanks.

I just received the beautiful M5 Core2 unit and was trying to get the factory test to upload. Unfortunately I get an error I see in other posts.

Chip is ESP32-D0WDQ6-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
WARNING: Detected crystal freq 41.01MHz is quite different to normalized freq 40MHz. Unsupported crystal in use?
Crystal is 40MHz
MAC: 78:21:84:93:38:58
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out)
A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out)

I can upload to all the other M5 devices and ESP-32. This occurs on my Mac with the M1 chip, but also with an older Mac.

I've tried the USB-C to USB-C as well as USB-A to USB-C. No difference.

I just received my Unit V2 and was wondering the same about running MQTT. Doing some digging on the chip and I found they already include the mosquito broker, and it works right out of the box.

I also got the wpa_supplicant to connect this device to an ssid of my network. Now the device can just startup without the serial wire.

Has anyone connected the existing server.py code to MQTT or other interfaces?

Is the best approach just to modify the server.py code to start performing the additional operations, like publishing the JSON data over MQTT?

thanks.

I received the M5 unitV2 and with an up to date firmware, the "Code Detector" feature of the camera isn't working as defined. Basically the camera display isn't showing the found QR codes. But I found the internal file "server_log.txt" is printing out that it finds them.

But the error reported is (with example QR = "http://qr.com")
[line:311] - WARNING: pipe_result_rx_queue full, discard: b'{"code":[{"prob":0.943542421,"x":335,"y":125,"w":90,"h":96,"type":"http://qr.com,"content":""}],"num":1,"running":"Code Detector"}'

I'm new to this forum and didn't know where else to report this information.

Also, does anyone have pointers to startup an MQTT client?

thanks.