VDD_SDIO for ESP32 D2WD

[wojc0008]

Thanks for your responses. I'm wondering if the internal 1.8V regulator has enough current for the internal flash? I have a 1.8V switching regulator on my board that I can solder to the VDD_SDIO. Other than that, I'm thinking that it is a software issue with the Windows download tool since I can successfully communicate with the ESP32 every single time and it show the MAC addresses. I have tried several circuit boards and they all do the exact same thing. Any other ideas?

ESP32-D2WD 16Mbit 40MHz DIO.jpg (223.33 KiB) Viewed 12348 times

Espressif engineering support states that the correct settings for the ESP32-D2WD are: Crystal: 40M; SPI SPEED: 40M; SPI MODE: DIO; FLASH SIZE: 16Mbit

I have also tried the SPIAutoSet mode but that did not work either.

ESP32-D2WD 16Mbit 40MHz DIO auto.jpg (233.76 KiB) Viewed 12348 times

Thanks for your help,
Jamie

[rudi ;-)]

Hi Jamie,

first, i understand your problem full -
cause i get this weekend the PCB for soldering and testings also the
Revised Revison ( because the specifications in the technical reference manual contain a fatal error to be able to share the CLK for PSRAM with SPI Flash ) pSRAM custom "wrover" boards from my own,
i can just in time not help you with practical - but theoretical:

note this:
In contrast to many other ESP_ * responses - ESP_igrr does only answere if he knows 100 procent of the knowledge for answering in right way, so you can take this for a combine to further thinking:

One can, for example, connect VDD_SDIO to external 3.3V supply. In this case the internal regulator will be disabled automatically. The only problem with this design is that the flash chip doesn't get automatically powered down before deep sleep, so a shutdown command needs to be sent to it (and then it still draws some sleep current from the external supply).

( you say, you put 1.8V by self to the VDD_SDIO )

if you put "high level" ( 1.8 or 3.3 ) on the VDD_SDIO, the regulator will be disabled,
this can be to say/know, that the pins ( SD_0, SD_1, SD_2, SD_3 also the CLK and CS ) can have other Level -
this question for it, does this be so - is just in time no place answered by the ESP_* and espressif.
this is hard - but it is so.

the next what i can say is, that in last datasheet of esp32 we get new setups on pins:
previor was 12mA --.. now we can set 80mA

this theme, does the VDD_SDIO 1.8V regulator then must set too before, is not clear to me, cause
the CS pins example or the Data Pins have a "must minimal I" for the pins too.
this question for this it, does this be so - is just in time no place answered by ESP_* and espressif too.

this next, Sharing CLK on the technical reference - is just in time no place answered by ESP_* and espressif too. but there are infoshere and there - that we need a separate CLK pin too;
but the level for CLK is without bootstrap over 1.8 V .... cause the things is not clear, does the pins without bootstrap MTDI to high, be then again in the VDD_SDIO Domain

why i name pSRAM here too, cause its the same theme - 1.8V from VDD_SDIO.
and if we take power supply from this regulator ( SPI Flash 1.8, pSRAM 1.8 )
and each get 20..40mA .. it makes sence to put higher the maximum driving cabability from 12mA to 80mA

the last thing was, that GPIO20 was removed now from the VDD_SDIO Domain and there is no answere again on any place - why and for what and so on this so is.

just in time there is a big silence on ESP_* and espressif and we try here and there to clear the questions -
cause we are in production time plan now - and can not start - cause they do wipser only to pycom cause pycom pay for alpha support!

and we get not more answeres cause here and there one or two guys of ESP_* Feel hurt when you take it ( their answeres ) closer under the magnifying glass.

They mean it well - sure sure -
Confronted with opposites that it can not be so, I remain alone with my deep questioning.

"we have to wait" - i think mid june cause pycom then ship the pSRAM modul...

..
..

- we wait this weekend this is my last station -
then again 2 weeks full after the last last promise was spoke that we get the pSRAM things.

@john lee answered last time, they will help after the chin. holidays and need 3 days - we prepair for this weekend next event -
if we can not use the "1.8" theme on D2, pSRAM and other things
then we must stop the project final we started.
it makes no more sense then to hold warm up.

i can't help further more you Jamie - sry - i would realy - but can'T -
i can only say - what the ESP_* sayed in the past and we get from espressif -

sry for my unhelp text to you. perhaps this or that you can need -
hope you have not damaged the regulator or the eMbeddedFlash now.

best wishes
rudi

perhabs there a further infos for you here
edit:
perhabs @WiFive has any idea or further tip to you, the guy is very well detailed knowed and have a good Instincts and can deal with facts very well.

[rudi ;-)]

@Jamie

one thing you can test - cause you have a D2 board ready for testings.

take ESP_ANGUS esptool from github / ESP-IDF
it says, that there is support in it for ESP-D2 - the ESP32 with eMbeddedFlash but i don't believe this ...
It does not take into account the bootstrap and there is also no indication that
we must use the bootstrap! Otherwise the eMbeddedFlash will be destroyed.
Apparently did not know at that time?

read the Advanced Options too - there is SPI and HSPI possible

and the part Custom Pins


test this simple example: esptool.py flash_id

cause you do not sure know - how your setup must be.. ( let us say this in this example )
and the esptool have the support for ESP32 with eMbeddedFlash
then the tool must be read the info .. automode.
.. test it and please write your test result .. does the esptool support D2 or not..
this test i would do if the boards comes on friday here to me for the weekend event.

the esptool itself is here
and in the ESP-IDF as recursive Part



thank you!
best wishes
rudi

[rudi ;-)]

@jamie
here a test on an ESP32-D0WD

with esptool v2.0-beta2

v2.0.png (19.29 KiB) Viewed 12339 times

with esptool v2.0-beta3 ( the latest )

v2.0-beta3.png (25.28 KiB) Viewed 12339 times

test it with your D2
and be sure, you pulled up the MTDI for VDD_SDIO 1.8V !

Am already very excited what comes out.
Please post it


best wishes
rudi

[rudi ;-)]

@jamie

and last but not least, if you not familary with esptool on console
and if you use example eclipse,

- make a new target entry with "flash_id"
- edit the project makefile and make a new target
write the commands in new line and use one tab ( not space )

( example on D0 )

eclipse_make_file.png (79.34 KiB) Viewed 12334 times

best wishes
rudi

now we wait your response

[enitalp]

Hi,

the hardware is now in my hands too (i'm the software guy, and jamie the hardware guy).

So the flash_id in eclipse gave me

Code: Select all

10:00:58 **** Build of configuration Default for project Imagine Bracelet ****
make flash_id 
hello word
esptool.py v2.0-beta1
Connecting.....
Detecting chip type... ESP32
Uploading stub...
Running stub...
Stub running...
Manufacturer: ff
Device: ffff
Hard resetting...

10:01:01 Build Finished (took 3s.317ms)

and for the instant flashing from eclipse (windows) fail too.

[enitalp]

Code: Select all

Flashing binaries to serial port /dev/COM8 (app at offset 0x10000)...
esptool.py v2.0-beta1
Connecting....
Uploading stub...
Running stub...
Stub running...
Attaching SPI flash...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Flash params set to 0x0220
Compressed 9488 bytes to 5745...

A fatal error occurred: Timed out waiting for packet content
make: *** [/c/ESP32-IDK-SDK/esp-idf/components/esptool_py/Makefile.projbuild:53: flash] Error 2

Changing my flash settings

Update did change the CONFIG_ESPTOOLPY_FLASHSIZE_DETECT=n to remove warning, and set it up to 2mb.
Still no luck. trying to switch to not compressed...

Yup no luck there.

Code: Select all

Flashing binaries to serial port /dev/COM8 (app at offset 0x10000)...
esptool.py v2.0-beta1
Connecting........
Uploading stub...
Running stub...
Stub running...
Attaching SPI flash...
Configuring flash size...
Flash params set to 0x0210

A fatal error occurred: Timed out waiting for packet content
make: *** [/c/ESP32-IDK-SDK/esp-idf/components/esptool_py/Makefile.projbuild:53: flash] Error 2

Upgrading my tools

[rudi ;-)]

@ivan @jeroen @angus
do we need a special bootstrap pin( ESP-D2WD ) for "flashing" the eMbeddedFlash and later then for "booting" from it?
best wishes
rudi
https://github.com/espressif/esptool/issues/205

[rudi ;-)]

Code: Select all

Flashing binaries to serial port /dev/COM8 (app at offset 0x10000)...
esptool.py v2.0-beta1
Connecting....
Uploading stub...
Running stub...
Stub running...
Attaching SPI flash...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Flash params set to 0x0220
Compressed 9488 bytes to 5745...

A fatal error occurred: Timed out waiting for packet content
make: *** [/c/ESP32-IDK-SDK/esp-idf/components/esptool_py/Makefile.projbuild:53: flash] Error 2

Changing my flash settings

Update did change the CONFIG_ESPTOOLPY_FLASHSIZE_DETECT=n to remove warning, and set it up to 2mb.
Still no luck. trying to switch to not compressed...

Yup no luck there.

Code: Select all

Flashing binaries to serial port /dev/COM8 (app at offset 0x10000)...
esptool.py v2.0-beta1
Connecting........
Uploading stub...
Running stub...
Stub running...
Attaching SPI flash...
Configuring flash size...
Flash params set to 0x0210

A fatal error occurred: Timed out waiting for packet content
make: *** [/c/ESP32-IDK-SDK/esp-idf/components/esptool_py/Makefile.projbuild:53: flash] Error 2

Upgrading my tools

yes use 2MB and do not compress - how you go on?

[ESP_igrr]

esptool.py v2.0-beta1

That seems to be a fairly dated version of esptool (and hence the IDF). Support for D2WD was added to IDF in commit 6630877 (around first week of April). If your version of IDF is older than that, you will need to update it (including git submodule update to update esptool).