Bricked ESP32?

AppdigEng
Posts: 13
Joined: Thu Feb 08, 2018 8:50 pm

Bricked ESP32?

Postby AppdigEng » Mon Nov 04, 2019 12:02 pm

I have somehow managed to brick my ESP32.

I have tried loading versions 0.10, 1.0, 1.1, 1.1.1, 1.1.2, and 1.2 of the command set be no matter the version, this is what happens
at boot.
  1. ets Jun  8 2016 00:22:57
  2.  
  3. rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
  4. configsip: 0, SPIWP:0xee
  5. clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
  6. mode:QIO, clock div:2
  7. load:0x3fff0018,len:4
  8. load:0x0348a033,len:55133211
I erased the flash between reloading the at files.
I can download the arduino core and it works fine but anytime I come back to at command set it get the above boot loop.
Is there anyway to recover?

WiFive
Posts: 3529
Joined: Tue Dec 01, 2015 7:35 am

Re: Bricked ESP32?

Postby WiFive » Mon Nov 04, 2019 12:48 pm

Make sure you are flashing the proper binaries to the proper addresses. How are you doing it?

AppdigEng
Posts: 13
Joined: Thu Feb 08, 2018 8:50 pm

Re: Bricked ESP32?

Postby AppdigEng » Mon Nov 04, 2019 1:58 pm

I'm sure the address are correct, I've use the same setup before.

And now it has happened on a second unit.
This occurred after I attempted to downgrade from V1.2.0.0 to V1.1.0.0 using the OTA function
I used the command AT+CIUPDATE=0,"V1.1.0.0" and it did finish with the final response of +CIUPUDATE:4,
but now it is unusable with the AT Command Set

AppdigEng
Posts: 13
Joined: Thu Feb 08, 2018 8:50 pm

Re: Bricked ESP32?

Postby AppdigEng » Mon Nov 04, 2019 2:28 pm

***** SOLVED ******

My flash programmer had SPI mode set to QIO instead of DIO

Who is online

Users browsing this forum: aliarifat794 and 57 guests