ESP32 Forum

Posted: **Sat Jan 16, 2021 4:15 am**

During the boot sequence of my ESP32-DEVKITM-1 I see "The system cannot find the file specified" errors for files that have nothing to do with the current project flashed to the device. The device continues and successfully runs the hello_world example app.

The path given for the missing file is from a project previously loaded on the board. The file does exist on the computer's hard drive.

What did I do wrong to cause this?
How do I correct this issue?

Code: Select all

ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:6956
load:0x40078000,len:13072
xtensa-esp32-elf-addr2line -pfiaC -e c:\users\dg\source\repos\esp32\blink\blink\build\udp_server.elf 0x40078000: [WinError 2] The system cannot find the file specified
load:0x40080400,len:3896
xtensa-esp32-elf-addr2line -pfiaC -e c:\users\dg\source\repos\esp32\blink\blink\build\udp_server.elf 0x40080400: [WinError 2] The system cannot find the file specified
entry 0x40080688
xtensa-esp32-elf-addr2line -pfiaC -e c:\users\dg\source\repos\esp32\blink\blink\build\udp_server.elf 0x40080688: [WinError 2] The system cannot find the file specified
I (30) boot: ESP-IDF v4.1-dirty 2nd stage bootloader
I (30) boot: compile time 21:12:40
I (30) boot: chip revision: 3
I (33) boot_comm: chip revision: 3, min. bootloader chip revision: 0
I (40) boot.esp32: SPI Speed      : 40MHz
I (45) boot.esp32: SPI Mode       : DIO
I (49) boot.esp32: SPI Flash Size : 4MB
I (54) boot: Enabling RNG early entropy source...
I (59) boot: Partition Table:
I (63) boot: ## Label            Usage          Type ST Offset   Length
I (70) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (78) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (85) boot:  2 factory          factory app      00 00 00010000 00100000
I (93) boot: End of partition table
I (97) boot_comm: chip revision: 3, min. application chip revision: 0
I (104) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x04c58 ( 19544) map
I (120) esp_image: segment 1: paddr=0x00014c80 vaddr=0x3ffb0000 size=0x0194c (  6476) load
I (124) esp_image: segment 2: paddr=0x000165d4 vaddr=0x40080000 size=0x00404 (  1028) load
xtensa-esp32-elf-addr2line -pfiaC -e c:\users\dg\source\repos\esp32\blink\blink\build\udp_server.elf 0x40080000: [WinError 2] The system cannot find the file specified
I (131) esp_image: segment 3: paddr=0x000169e0 vaddr=0x40080404 size=0x08b80 ( 35712) load
xtensa-esp32-elf-addr2line -pfiaC -e c:\users\dg\source\repos\esp32\blink\blink\build\udp_server.elf 0x40080404: [WinError 2] The system cannot find the file specified
I (155) esp_image: segment 4: paddr=0x0001f568 vaddr=0x00000000 size=0x00ab0 (  2736)
I (156) esp_image: segment 5: paddr=0x00020020 vaddr=0x400d0020 size=0x12a14 ( 76308) map
xtensa-esp32-elf-addr2line -pfiaC -e c:\users\dg\source\repos\esp32\blink\blink\build\udp_server.elf 0x400d0020: [WinError 2] The system cannot find the file specified
I (195) boot: Loaded app from partition at offset 0x10000
I (196) boot: Disabling RNG early entropy source...
I (196) cpu_start: Pro cpu up.
I (200) cpu_start: Application information:
I (204) cpu_start: Project name:     hello-world
I (210) cpu_start: App version:      1
I (214) cpu_start: Compile time:     Jan 15 2021 21:09:42
I (220) cpu_start: ELF file SHA256:  bfc1edfe4da46a32...
I (226) cpu_start: ESP-IDF:          v4.1-dirty
I (231) cpu_start: Single core mode
I (236) heap_init: Initializing. RAM available for dynamic allocation:
I (243) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (249) heap_init: At 3FFB2068 len 0002DF98 (183 KiB): DRAM
I (255) heap_init: At 3FFE0440 len 0001FBC0 (126 KiB): D/IRAM
I (262) heap_init: At 40078000 len 00008000 (32 KiB): IRAM
I (268) heap_init: At 40088F84 len 0001707C (92 KiB): IRAM
I (274) cpu_start: Pro cpu start user code
I (291) spi_flash: detected chip: generic
I (292) spi_flash: flash io: dio
I (292) cpu_start: Starting scheduler on PRO CPU.
Hello world!
This is ESP32 chip with 1 CPU cores, WiFi/BT/BLE, silicon revision 3, 4MB embedded flash
Restarting in 10 seconds...

Posted: **Sun Jan 17, 2021 1:45 pm**

These lines are generated by 'esp.py monitor', which runs on your local PC. When you use that and something appears in the serial stream that looks like a RAM address, that program helpfully tries to tell you what symbol the address maps to. Here it fails as the project was moved or something. Those lines are not from the ESP32 itself, and your program itself is working fine.

Posted: **Thu Jan 21, 2021 3:40 am**

Thank you for the reply ESP_Sprite. After your post I found the documentation on the auto address decoding. Now I know it is harmless, but I also know how to suppress the warnings.

IDF Monitor - Automatic Address Decoding Documentation

ESP32 Forum

Missing Files Reported During Boot Process

Missing Files Reported During Boot Process

Re: Missing Files Reported During Boot Process

Re: Missing Files Reported During Boot Process