ESP32 Forum

Downloaded V3 rc1 and installed, following Release notes.
Even simple hello application gives attached.
Confusing is SPI Flash Size with 2MB, I'm pretty sure to have 4MB
BTW, this time, I'm sure to have flash correct bootloader.bin

ets Jun 8 2016 00:22:57

rst:0x1 (POWERON_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:4
load:0x3fff0018,len:4
load:0x3fff001c,len:5704
load:0x40078000,len:0
ho 12 tail 0 room 4
load:0x40078000,len:13804
entry 0x40079030
I (83) boot: Detected ESP32
I (33) boot: ESP-IDF v3.1-dev-37-ga7a8619 2nd stage bootloader
I (34) boot: compile time 18:12:06
I (34) boot: Enabling RNG early entropy source...
I (39) boot: SPI Speed : 20MHz
I (43) boot: SPI Mode : DIO
I (47) boot: SPI Flash Size : 2MB
E (51) flash_parts: partition 0 invalid magic number 0x40a9
E (58) boot: Failed to verify partition table
E (63) boot: load partition table error!
user code done

Did you flash correct partition table? Are you using make flash command?

I flashed and overwrote all of the memory with zero.
With or without overwriting, same problem.
Tested with 2 different boards.
Tested the same with older ESP-IDF and everything runs fine.

jumjum123 wrote:I flashed and overwrote all of the memory with zero.
With or without overwriting, same problem.
Tested with 2 different boards.
Tested the same with older ESP-IDF and everything runs fine.

have you tried? if this wont help, try

jumjum123 wrote: E (51) flash_parts: partition 0 invalid magic number 0x40a9

This error can imply bootloader.bin is too big, and has overwritten the partition table. Although esptool.py should detect this and error out if both were flashed at the same time (ie with "make flash").

Any chance you could please zip up your "build" directory for hello world and post it somewhere for us to take a look?

Angus

@esp_angus
Please see here http://jumspruino.jumware.com/problems/ ... -World.zip
And this is the way, how I flash http://jumspruino.jumware.com/problems/ ... -World.PNG
There is one change in sdk_config for size of flash to 4mb
Anyway, 2mb or 4mb, problem is the same.
Hope, you can help me

Hmmmmm, looks like I found problematic code.
Removed call to
- vddsdio_configure
- flash_gpio_configure
from main in bootloader_start.c
and it works

update:
problem is somewhere in flash_gpio_configure
no problem if this call is commented out

2nd update:
just recognized warning that my toolchain is too old
Therefore googled for actual one and found this https://esp-idf.readthedocs.io/en/v2.0/linux-setup.html
In there is a note V3 rc1 with a link, but link is dead
Anyway, just download from link found here https://esp-idf.readthedocs.io/en/v3.0- ... setup.html
Will install and check again

3rd update tested with new toolchain and get same problem as before.
So its not a problem of toolchain.
checked with 3 different devkits (watterott, www.doit.am and one of the first from 2016), same problem for all

Does it happen at 40mhz too?

Can confirm setting 20MHz flash speed is the problem here, in the flash_gpio_configure() function. We will have a fix ASAP.

In the mean time, the development boards you mention should work (with better performance) with 40MHz flash speed.

@ESP_Angus why is the default to use gpio matrix now instead of mux?