Hello @aezero

just to be clear, with your setup, the firmware update always fails, correct?

• Does your code have tasks (other than the mandatory loop())?
• Is your power source stable?

Thanks
Felix

Hello @BennoB

have you tried to run the example without modification, e.g. connecting to mqtt.m5stack.com as a test? Does that work?

Thanks
Felix

Hello @aezero

hmm, not sure why your sketch is taking longer (unless the firmware is bigger).

I think if you want to decouple the flash from the download process you'd need to look into examples using SPIFFS. However in my opinion this is kind of redundant as SPIFFS is in flash as well. So the download would go into SPIFFS first and then copy from flash to flash. (Unless I am missing something.)

When I check with tcpdump on my server I see it reading multiple small chunks over the period of the download (about 37s). In other words I don't think there is a buffer on the way or in the modem in my case.

Are you using the default modem.restart();? I found it can take quite some time for the modem to be ready after that. Plus the modem sometimes sends some unsolicited messages (e.g. +CPIN: READY, SMS DONE, PB DONE) as well which I think might interfere with the download.

You could try using modem.init(); instead and / or add some sort of delay / check if the modem is ready or not. I've added the following line modem.testAT(30000); before String modemInfo = modem.getModemInfo(); which helped the download when using a SIM7600G.

BTW: from what I can tell my setup uses CGNAT IP starts with 10.x.x.x.

Thanks
Felix

P.S. github example updated

Hello @RIDDSprojects

is your M5Stack running the latest UiFlow firmware (v1.10.9)? You can install it with M5Burner v3.0.

Thanks
Felix

Hello @btrex

not sure I understand why the LAN module removes port B. Do you mean the LAN module uses the GPIOs normally used for port B?

Anyways, if you are using an M5Core2 device this module might help.

And for an M5Stack device the bus module might be helpful as it exposes all pins.

Thanks
Felix

Hello @LishengKKK

cool. I am happy to hear you got it working. Thank you for reporting back.

Thanks
Felix

Hello @kilnageer

you are welcome. Thank you for reporting back. I am happy to read that it worked for you.

Same to you!

Thanks
Felix

Hello @kilnageer

when the code is downloaded to the device and is run in app mode, WiFi might no longer be connected. Try adding below blocks to your program to ensure WiFi is connected.

Thanks
Felix

Hello @aezero

the linked example works for me. It is using TinyGSM library which supports multiple modems. I've tested it with a SIM7080 modem and CAT-M1.

Thanks
Felix

Hello @teastain

Wire.begin() used to always initialize an I2C master, but in recent ESP32 Arduino framework versions an ESP32 can also be setup as I2C slave. But instead of creating a new function like Wire.beginSlave() it has been decided to overload the already existing begin() function so it can be used to initialize an I2C master or a slave.

The compiler / linker decides from the argument types which begin function to call. The I2C master begin function is defined like this:

bool begin(int sda, int scl, uint32_t frequency=0);

And the I2C slave begin function is defined like this:

bool begin(uint8_t slaveAddr, int sda, int scl, uint32_t frequency);

Now if you call Wire.begin(SDA, SCK) and SDA and SCK are defined as uint8_t the I2C slave begin is called (instead of the intended I2C master begin) since the argument types match better.

Thanks
Felix

P.S.: my original advise to typecast the arguments to (int) was useless as numbers are already defined as int.