spi_flash and eFuse warning after migration from IDF 4.4 to 5.0

Pixellord
Posts: 5
Joined: Wed Feb 15, 2023 8:58 am

spi_flash and eFuse warning after migration from IDF 4.4 to 5.0

Postby Pixellord » Tue Mar 14, 2023 10:39 am

Hi,

After having migraded IDF from 4.4 to 5.0.1, I have got new warning messages when ESP32-S3-DevKitC boots up and before my own application code starts.

(1) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header
(2) eFuse: calibration efuse version does not match, set default version: 0

Can anyone help me to understand what these two warning messages mean? and how should I fix them?
I could not find any useful infomation from the internet. FYI, I am using ADC in my project. Below I have copied the complete message log.

Thanks!

Code: Select all

I (0) cpu_start: App cpu up.
I (265) cpu_start: Pro cpu start user code
I (265) cpu_start: cpu freq: 160000000 Hz
I (265) cpu_start: Application information:
I (268) cpu_start: Project name:     esp32-io-link-controller
I (274) cpu_start: App version:      c32cc55-dirty
I (280) cpu_start: Compile time:     Mar 14 2023 11:12:10
I (286) cpu_start: ELF file SHA256:  474f5d040f3bb8f1...
I (292) cpu_start: ESP-IDF:          v5.0.1
I (297) cpu_start: Min chip rev:     v0.0
I (301) cpu_start: Max chip rev:     v0.99 
I (306) cpu_start: Chip rev:         v0.1
I (311) heap_init: Initializing. RAM available for dynamic allocation:
I (318) heap_init: At 3FCA1D50 len 000479C0 (286 KiB): D/IRAM
I (324) heap_init: At 3FCE9710 len 00005724 (21 KiB): STACK/DRAM
I (331) heap_init: At 3FCF0000 len 00008000 (32 KiB): DRAM
I (337) heap_init: At 600FE010 len 00001FF0 (7 KiB): RTCRAM
I (345) spi_flash: detected chip: generic
I (348) spi_flash: flash io: dio
[b]W (352) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header.[/b]
W (365) cpu_start: eFuse virtual mode is enabled. If Secure boot or Flash encryption is enabled then it does not provide any security. FOR TESTING ONLY!
[b]W (380) eFuse: calibration efuse version does not match, set default version: 0
W (392) eFuse: calibration efuse version does not match, set default version: 0
W (400) eFuse: calibration efuse version does not match, set default version: 0
W (408) eFuse: calibration efuse version does not match, set default version: 0
W (416) eFuse: calibration efuse version does not match, set default version: 0
W (424) eFuse: calibration efuse version does not match, set default version: 0
W (432) eFuse: calibration efuse version does not match, set default version: 0
W (440) eFuse: calibration efuse version does not match, set default version: 0[/b]
W (448) efuse: Loading virtual efuse blocks from real efuses
I (451) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.

natee.th
Posts: 20
Joined: Fri Feb 10, 2023 5:25 pm

Re: spi_flash and eFuse warning after migration from IDF 4.4 to 5.0

Postby natee.th » Sun May 28, 2023 12:16 pm

(1) spi_flash: Detected size(8192k) larger than the size in the binary image header(2048k). Using the size in the binary image header
that mean your ESP32 has a 8192k flash detect by IDF, Just go to Idf.py menuconfig and setting the flash size correctly.

(2) eFuse: calibration efuse version does not match, set default version: 0
I am also looking for too :D

Who is online

Users browsing this forum: No registered users and 111 guests