Page 1 of 1

ESP32-C Device stuck in a boot loop: SHA-256 comparison failed

Posted: Sat Jan 15, 2022 12:20 am
by bstolk
My ESP32-C was working previously, but after hooking up GPIO9/8 to try I2C, I think I somehow corrupted it?

Now it is stuck in this boot loop.

I tried reset, and power-cycle, to no avail:

Code: Select all

ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xd (SPI_FAST_FLASH_BOOT)
Saved PC:0x403d0f88
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x420
load:0x403ce000,len:0x90c
load:0x403d0000,len:0x236c
SHA-256 comparison failed:
Calculated: ccb0d00bac7e84e1d90a12e4f75f4ab6c5f7e71bb209afd5819c4c9557a6db71
Expected: c9cf160580940ec7801c73b16423824e72ad12055c732e83ce66332240af42a7
Attempting to boot anyway...
entry 0x403ce000
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xd (SPI_FAST_FLASH_BOOT)
Saved PC:0x403d0f88
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x420
load:0x403ce000,len:0x90c
load:0x403d0000,len:0x236c
SHA-256 comparison failed:
Calculated: ccb0d00bac7e84e1d90a12e4f75f4ab6c5f7e71bb209afd5819c4c9557a6db71
Expected: c9cf160580940ec7801c73b16423824e72ad12055c732e83ce66332240af42a7
Attempting to boot anyway...
entry 0x403ce000
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xd (SPI_FAST_FLASH_BOOT)
Saved PC:0x403d0f88
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd6100,len:0x420
load:0x403ce000,len:0x90c
load:0x403d0000,len:0x236c
SHA-256 comparison failed:
Calculated: ccb0d00bac7e84e1d90a12e4f75f4ab6c5f7e71bb209afd5819c4c9557a6db71
Expected: c9cf160580940ec7801c73b16423824e72ad12055c732e83ce66332240af42a7
Attempting to boot anyway...
entry 0x403ce000
ESP-ROM:esp32c3-api1-20210207
Build:Feb  7 2021
rst:0x3 (RTC_SW_SYS_RST),boot:0xd (SPI_FAST_FLASH_BOOT)
Saved PC:0x403d0f88
SPIWP:0xee
...

Re: ESP32-C Device stuck in a boot loop: SHA-256 comparison failed

Posted: Thu Feb 24, 2022 9:04 pm
by GregP72
Change the pins for I2C.

Re: ESP32-C Device stuck in a boot loop: SHA-256 comparison failed

Posted: Fri Feb 25, 2022 10:17 am
by felmue
Hi @bstolk

afaik GPIO6 to GPIO11 are normally used for flash. So yes, like @GregP72 already wrote, use different GPIOs for I2C.

Thanks
Felix

Re: ESP32-C Device stuck in a boot loop: SHA-256 comparison failed

Posted: Fri Feb 25, 2022 7:28 pm
by lbernstone
On the esp32-c3, gpio8 is the pin to disable logging, and gpio9 is the programming pin. While not forbidden, these will be difficult to use with an i2c device, since you cannot guarantee their state during initialization. I suspect in this case, there are errors being generated, but you don't see them since gpio8 is disabling logging on boot. Note that pulling both 8 and 9 low during boot will generate errors.

Re: ESP32-C Device stuck in a boot loop: SHA-256 comparison failed

Posted: Thu Mar 24, 2022 1:00 am
by bstolk
felmue wrote:
Fri Feb 25, 2022 10:17 am
Hi @bstolk

afaik GPIO6 to GPIO11 are normally used for flash. So yes, like @GregP72 already wrote, use different GPIOs for I2C.

Thanks
Felix
I am confused... I am not supposed to use GPIO6, GPIO7, GPIO8, GPIO9, GPIO10 and GPIO11 for anything?

Doesn't that severely hamper the usefulness of this board?

Or just not use if for i2c?

Re: ESP32-C Device stuck in a boot loop: SHA-256 comparison failed

Posted: Fri Mar 25, 2022 7:35 am
by felmue
Hi @bstolk

which ESP32 MCU are you using exactly?

My comment regarding GPIO6 to GPIO11 only applies to the ESP32. ESP32C3 is different, see comment from @lbernstone.

Sorry for the confusion.

Thanks
Felix