Yup, dead easy: Firstly, enable the below config option. This means that, if you do not explicitly mark the new img as OK, it will automatically roll back upon the next boot. CONFIG_BOOTLOADER_APP_ROLLBACK_ENABLE Then check to see if your img is pending verification: esp_ota_img_states_t imgState; e...

Hmm, that sounds identical to what I am experiencing in STA mode. I have just tested AP mode, and I am experiencing similar things to STA mode. It is much more reliable in AP mode, but I am still getting a long block every 30 or so requests. I have tested this on Chrome, Edge and Firefox. So not qui...

Connection:close does not help. Still getting multiple second response times on 700 bytes of text, generated on the fly. I can request the data, and there is no indication within the HTTPD server that a request has been made, until a couple of seconds pass and it serves up the data, which is why I t...

I am not sure that the filesystem is the whole story. I agree spiffs is significantly slower than FAT, but I still believe that requests are getting stopped somewhere way before the webserver. I have some JSON pages generated entirely on the fly, with no mention of a filesystem. It sometimes still t...

Did you get any further with this? I am experiencing similar issues. It seems that any requests get "stuck" in the IP stack for a long time before making it to the web server handler. It might take 5 seconds before the server responds. What in the IP stack would cause it to hold on to a request for ...

Hi Guys, I have NDIR_LAMP_TIMER set up with a 125ms period. This fires a GPIO. I need to sample an ADC exactly 50ms after the NDIR_LAMP_TIMER ticks. NDIR_LAMP_TIMER auto reloads NDIR_SAMPLE_TIMER does not. Currently I have the following ISR: void IRAM_ATTR timer_group0_isr(void *para) { timer_intr_t...

Okay. Sounds like it may be fixed, although it would be nice to know the root mechanism as to why devices in noisy environments get bricked.

The immunity thing may be a red herring, but worth looking out for.

Can you share what you did differently between revisions in regards to GND coupling?

Sam

No worries. Yeah, it does seem far fetched, but weirder things have happened. If power consumption isn't an issue, you could easily lower it. Okay, that makes sense. To clarify, the second batch of devices never overwrite their bootloader? Or they don't have any noise issues? Have you put the device...

You need a pull up on IO0 I believe.
Also, are you toggling the reset line?

Workflow should be:
Pull IO0 Low
Reset chip (or cycle power)
Release IO0
Initiate Download
cycle power when complete

Done!

Could it be that 360k isnt aggressive enough of a pull down? One thing worth trying might be disabling the bootstrapping pins and forcing the flash voltage through the efuse, and then see if you get a failure? I dont know how long you have to run these before they typically fail. You mentioned that ...