Problem working with PlatformIO build

[saspol]

Hello,
after compile with this platformio.ini and uploading have such errors on boot:

`ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, 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:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8`

Maybe some building option missed? Please give me advice. Others esp32-cam projects i tried dont have this issue.

[easytarget]

flash read err, 1000
AAh Google!
https://github.com/espressif/esptool/wiki/ESP32-Boot-Mode-Selection#early-flash-read-error
There is no magic option to set to fix this, the most likely explanation is that the board is brown-outing during boot (given how sensitive most ESP-CAM boards are to power issues). Try flashing a simple 'blink' sketch via platformio and see if that works.

Alternatively your platformio setup may be corrupted. For me the bootloader is added by ~/.platformio/packages/framework-arduinoespressif32/tools/platformio-build.py line 181 where the block:

        ("0x1000", join(FRAMEWORK_DIR, "tools", "sdk", "bin", "bootloader_${BOARD_FLASH_MODE}_${__get_board_f_flash(__env__)}.bin")),
        ("0x8000", join(env.subst("$BUILD_DIR"), "partitions.bin")),
        ("0xe000", join(FRAMEWORK_DIR, "tools", "partitions", "boot_app0.bin"))

puts the bootloader at address 0x1000. Maybe you have been reconfiguring or this is otherwise corrupted?

I cant properly debug this for you I'm afraid, it's a generic error that seems to affect people occasionally and has no single cause or solution.

Plus I only really support the Arduino IDE, platformio is a nice-to-have but not my default environment, but, to double-check I just re-uploaded via platformio and saw this:

[owen@hobbes esp32-cam-webserver]$ pio run -t upload
Processing esp32dev (platform: espressif32; board: esp32dev; framework: arduino)
-------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32dev.html
PLATFORM: Espressif 32 (3.3.2) > Espressif ESP32 Dev Module
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (esp-prog) External (esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES: 
 - framework-arduinoespressif32 3.10006.210326 (1.0.6) 
 - tool-esptoolpy 1.30100.210531 (3.1.0) 
 - tool-mkspiffs 2.230.0 (2.30) 
 - toolchain-xtensa32 2.50200.97 (5.2.0)
Converting esp32-cam-webserver.ino
LDF: Library Dependency Finder -> http://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 28 compatible libraries
Scanning dependencies...
Dependency Graph
|-- <WiFi> 1.0
|-- <ArduinoOTA> 1.0
|   |-- <Update> 1.0
|   |-- <WiFi> 1.0
|   |-- <ESPmDNS> 1.0
|   |   |-- <WiFi> 1.0
|-- <DNSServer> 1.1.0
|   |-- <WiFi> 1.0
|-- <FS> 1.0
|-- <SPIFFS> 1.0
|   |-- <FS> 1.0
Building in release mode
Compiling .pio/build/esp32dev/src/esp32-cam-webserver.ino.cpp.o
Linking .pio/build/esp32dev/firmware.elf
Retrieving maximum program size .pio/build/esp32dev/firmware.elf
Checking size .pio/build/esp32dev/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM:   [==        ]  18.2% (used 59792 bytes from 327680 bytes)
Flash: [======    ]  56.6% (used 1112742 bytes from 1966080 bytes)
Building .pio/build/esp32dev/firmware.bin
esptool.py v3.1
Merged 1 ELF section
Configuring upload protocol...
AVAILABLE: esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port...

Auto-detected: /dev/ttyUSB0
Uploading .pio/build/esp32dev/firmware.bin
esptool.py v3.1
Serial port /dev/ttyUSB0
Connecting.....
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 3c:71:bf:f8:28:30
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x0011ffff...
Compressed 17104 bytes to 11191...
Writing at 0x00001000... (100 %)
Wrote 17104 bytes (11191 compressed) at 0x00001000 in 0.5 seconds (effective 252.1 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 129...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.1 seconds (effective 387.5 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 510.9 kbit/s)...
Hash of data verified.
Compressed 1112848 bytes to 583958...
Writing at 0x00010000... (2 %)
Writing at 0x000272ae... (5 %)
Etc..
Writing at 0x00110353... (94 %)
Writing at 0x001161d0... (97 %)
Writing at 0x0011bb26... (100 %)
Wrote 1112848 bytes (583958 compressed) at 0x00010000 in 14.2 seconds (effective 627.3 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
================= [SUCCESS] Took 33.83 seconds =========================

After which the esp-cam boots and works properly.

What do you see? In particular, do you see:

Writing at 0x00001000... (100 %)
Wrote 17104 bytes (11191 compressed) at 0x00001000 in ...

...this is where the bootloader is being uploaded to address 0x1000, If you don't see this, or see a different address in use then you have a configuration or corruption problem with your platformio environment.
If you do see it, but the error persists on reboot, you probably have a corrupt flash chip or soft-fuse issues.

[easytarget]

NB Converting to a discussion since I want to leave this info visible, I imagin others may encounter it, but don't want open-ended issues clogging up the system.