ESP32-D0WD Design Issue.
ESP32-D0WD Design Issue.
Please find below the Schematic of the ESP32-D0WD SOIC based design.
I am able to detect chip as well as all technical parameters of ESP32 when I try to flash a code over chip but after that, I think Flash does not respond and it fails and got some error.
I use W25Q16JVZPIQ flash (it's 16Mb / 2MB)
Also, I am able to erase the flash, and the command working fine.
Also, there is a small bit of communication done between ESP32 and Flash than its Fail as per log of command.
May I know what is the issue??
Hello, world example code we try to flash and I think that 2MB flash is enough and Good with ESP32.
We try a lot but were not able to figure out the issue Maybe ESP32 does not enter into boot mode but I am not sure so please help me to solve this issue.
Thanks,
AB.
I am able to detect chip as well as all technical parameters of ESP32 when I try to flash a code over chip but after that, I think Flash does not respond and it fails and got some error.
I use W25Q16JVZPIQ flash (it's 16Mb / 2MB)
Also, I am able to erase the flash, and the command working fine.
Also, there is a small bit of communication done between ESP32 and Flash than its Fail as per log of command.
May I know what is the issue??
Hello, world example code we try to flash and I think that 2MB flash is enough and Good with ESP32.
We try a lot but were not able to figure out the issue Maybe ESP32 does not enter into boot mode but I am not sure so please help me to solve this issue.
Thanks,
AB.
- Attachments
-
- Command Log
- 001.PNG (77.81 KiB) Viewed 15496 times
-
- Connection
- 002.PNG (69.19 KiB) Viewed 15496 times
Re: ESP32-D0WD Design Issue.
Try slower bad rate, stronger power supply, or use esptool.py --trace option
Re: ESP32-D0WD Design Issue.
Hi,
I have tried to read the flash Id using the command "esptool.py --trace flash_id" and I see it reads 0xFF which i think is wrong.
What could be the next step to the test board??
I have tried to read the flash Id using the command "esptool.py --trace flash_id" and I see it reads 0xFF which i think is wrong.
Meanwhile, I also verified that the chip enter successfully in to bootloader mode here is the log.TRACE +0.025 Read 1 bytes: c0
TRACE +0.000 Read 11 bytes: 01090200000000000000c0
TRACE +0.007 Received full packet: 01090200000000000000
Manufacturer: ff
Device: ffff
Detected flash size: Unknown
Hard resetting via RTS pin...
What could be a possible issue with external flash looks like I am not detecting the flash?--- idf_monitor on \\.\COM11 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jul 29 2019 12:21:46
rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download
What could be the next step to the test board??
- Attachments
-
- Logfile
- 002.PNG (32.65 KiB) Viewed 15429 times
-
- Logfile 001
- 001.PNG (83.31 KiB) Viewed 15429 times
Re: ESP32-D0WD Design Issue.
Hey, May I know what is the issue??
-
- Posts: 9764
- Joined: Thu Nov 26, 2015 4:08 am
Re: ESP32-D0WD Design Issue.
Your schematic looks OK to me; are you sure your board itself matches the schematic (as in: no solder bridges, badly soldered joints etc)? Do you have multiple boards to test this on?
Re: ESP32-D0WD Design Issue.
Yes, PCB board Connections and Routing are the same as in the image of the Schematic.
We have 4 PCBA boards and all of the boards have the same issue.
Thanks,
AB.
We have 4 PCBA boards and all of the boards have the same issue.
Thanks,
AB.
-
- Posts: 9764
- Joined: Thu Nov 26, 2015 4:08 am
Re: ESP32-D0WD Design Issue.
Any chance that MTDI is pulled low on startup? If that's the case, the ESP32 probably won't be able to talk to the flash either. You can check that by looking at the voltage over C18; that should be 3.3V and not 1.8V.
Re: ESP32-D0WD Design Issue.
Pulled *high*, pulled low is default. The answer is probably no becauseESP_Sprite wrote: ↑Mon Aug 23, 2021 10:44 amAny chance that MTDI is pulled low on startup? If that's the case, the ESP32 probably won't be able to talk to the flash either. You can check that by looking at the voltage over C18; that should be 3.3V and not 1.8V.
Code: Select all
boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
-
- Posts: 9764
- Joined: Thu Nov 26, 2015 4:08 am
Re: ESP32-D0WD Design Issue.
Whoops, you're right ws high vs low. I saw the boot string but till wanted to ask as there's not much else going on that can explain this.
Re: ESP32-D0WD Design Issue.
I have the same problem with ESP32-D0WD-V3. Using it with MX25R3235FM2IH0 which is 1.65V ~ 3.6V so I can use power it both using 3.3V or 1.8V (doesn't work either way). I also tried soldering GD25LQ32DSIGR instead (and using it with 1.8V of course) - also didn't work.
Enclosed is my schematic.
This is what I'm getting when trying to flash_id:
This when I try to write_flash:
And this is what it prints on the serial when powered:
I have 3 PCBs - all show same issue.
All 3 have ESP and flash soldered in reflow so there's no cold joints etc.
Any ideas what might be wrong?
Cheers!
Enclosed is my schematic.
This is what I'm getting when trying to flash_id:
Code: Select all
esptool.py v3.1
Serial port COM14
Connecting........_
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:dd:57:93:78:98
Uploading stub...
Running stub...
Stub running...
Manufacturer: ff
Device: ffff
Detected flash size: Unknown
Hard resetting via RTS pin...
Code: Select all
esptool.py v3.1
Serial port COM14
Connecting........_
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:dd:57:93:78:98
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
Flash will be erased from 0x0000e000 to 0x0000ffff...
Compressed 8192 bytes to 47...
A fatal error occurred: Timed out waiting for packet content
Code: Select all
ets Jul 29 2019 12:21:46
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
ets Jul 29 2019 12:21:46
rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
invalid header: 0xffffffff
All 3 have ESP and flash soldered in reflow so there's no cold joints etc.
Any ideas what might be wrong?
Cheers!
- Attachments
-
- schematic.png (139.06 KiB) Viewed 15017 times
Who is online
Users browsing this forum: Bing [Bot] and 166 guests