ESP32 Forum

500ma@3.3V power supply are you sure? According to the post you think that the chip d2wd always reset is due to the power supply can provide enough current? But the hardware book don't say that the esp32 d2wd need so much power and current.Although it's peak current when it work for wifi.I doubt the if the esp32 d2wd @500ma can be said ultra low power chip ?

We met two chip are always reset reset and reset. If the d2wd chip is wrong or bug?

500ma@3.3V power supply are you sure? According to the post you think that the chip d2wd always reset is due to the power supply can provide enough current? But the hardware book don't say that the esp32 d2wd need so much power and current.Although it's peak current when it work for wifi.I doubt the if the esp32 d2wd @500ma can be said ultra low power chip ?

Now it is always reset reset and reset

Do you have any other good suggestion for this issue? 500ma is so crazy that unbeleavable.

We met two chip are always reset reset and reset. If the d2wd chip is wrong or bug?

perhabs you forget onetime bootstrap pulled up for intern regulator 1.8V
then there is a rest risiko to damage the eMbeddedFlash

Which power supply do you suggest for the d2wd?

which consum you have measuring in the line from your supply to the SoC 3.3 power?

FYI:
my labor supply is on 3.3V and 5 Ampere

the limit for the SoC is set by Resistor ( 4 Ohm ) in the line and i can get max 825mA then for testings.

i do generally not play with cheap Regulator that only bring 240mA or 250mA or 330mA and so on and
they promisse 0.5 A or 1.5 A and so on.

pull the Ampere full from your labor supply and limit the consum by Resistor to your board
make a professional measuring in the line on it and then test again.

i think you have the equicment what you need for

No, the ROM boot log looks fine, and flash itself seems to be okay — 2nd stage bootloader is loaded into RAM; however it doesn't run further.
I recommend sending you firmware binaries to Espressif support for a test on a known good D2WD board, maybe there is a problem with your compiled binary (e.g. sdkconfig settings could be wrong).

No, the ROM boot log looks fine

Side question: what does SPIWP:0xee indicate since wp is not part of spi efuse config?

There is no efuse space reserved for WP, so ROM bootloader reads it from the binary image header. 0xee means "don't configure WP". 2nd stage bootloader itself is loaded in DIO mode, and then it enables QIO.

There is no efuse space reserved for WP, so ROM bootloader reads it from the binary image header. 0xee means "don't configure WP". 2nd stage bootloader itself is loaded in DIO mode, and then it enables QIO.

Thanks. Where are the pin drive strength settings read from?
Edit: nvm also header