Closed duanearnett closed 4 years ago
I would check signal integrity on the SDIO signals and the reset pin. Then I'd check that the power supply is solid to the ESP module. It can pull significant current on startup.
Then make sure it's a 'real' ESP-12F and not a knockoff with different flash configuration or different mapping of the flash castellations.
I did shorten the jumpers to the ESP-12F but it did not improve. I'm going to put the chip on a better protoboard and hope that improves the signal integrity. Thank you for the response!
New chip (from Waveshare) and new proto board. dmesg
gives me the following:
esp_sdio_init power up OK
sip_rx first read err -84 12
resetting event timeout
esp_init_all failed -110
first error exit
Trying to listen to the serial interface but just getting gibberish when I reload the driver, no matter the baudrate I select. This is on a waveshare compute module board with bank 0 GPIO which I confirmed raspi-gpio was reporting the right functionality for the GPIO. Using 33ohm resistors on the transmission lines but not pulling anything else down or up? I've come across varying sources saying they needed pull-ups on reset or IO15. Once schematic I found had 200ohm resistors for the transmission lines? Not sure if this helps someone with more experience pinpoint my issue, but thanks for the help!
Wanted to do another follow-up and say this was most likely because of the CMIO board I was using. A custom printed module, with the same wiring runs perfectly. Thanks @al177 for all your work and helping through everyone's issues.
Running
sudo rmmod esp8089
and I get two flashes on the ESP-12f and the following indmesg
:This is on a new RPI CM3+ module via headers on an IO Board. Any troubleshooting steps on why the firmware fails to load? I will try another module later but don't want to bin this one if its a software issue.