search

adafruit / Adafruit_CircuitPython_ESP32SPI

ESP32 as wifi with SPI interface
MIT License
103 stars 75 forks source link

Feather M4 Express not connecting with Air Lift ESP32 Coprocessor after update to NINA_W102-1.7.4 #144

Closed LAWBear closed 2 years ago

LAWBear commented 2 years ago

Purchased Feather M4 Express to allow use of Air Lift ESP32 Coprocessor breakout board via SPI. Previous test with original Air Lift firmware using Feather M0 Adalogger were successful using WIFINA examples.

Following detailed instructions, I updated firmware on Air Lift using SerialPassThru on new Feather M4 Express, and reflashed Air Lift with NINAW102-1.7.4 as clear instructions provided: Capture The above output assumed success of the update as instructed, however EXTENSIVE testing of various CircuitPython examples from Python 7 bundles all fail with similar errors (timed out waiting for SPI char) as follows: ESP32 SPI webclient test Traceback (most recent call last): File "code.py", line 50, in File "/lib/adafruit_esp32spi/adafruit_esp32spi.py", line 335, in status File "/lib/adafruit_esp32spi/adafruit_esp32spi.py", line 325, in _send_command_get_response File "/lib/adafruit_esp32spi/adafruit_esp32spi.py", line 292, in _wait_response_cmd File "/lib/adafruit_esp32spi/adafruit_esp32spi.py", line 271, in _wait_spi_char RuntimeError: Timed out waiting for SPI char

I am desperate for a kind wizard to advise my errors and lead to my hope of implementing the BLE capabilities of the Feather M4 Express with Air Lift ESP32 Coprocessor breakout board.

anecdata commented 2 years ago

Should work, I have an identical configuration, but I think this is more of a support question than a library issue. Can you post about it on the Adafruit Discord #help-with-CircuitPython, (or if not that then in the Adafruit support forums)? Be specific about the exact hardware, CircuitPython version, library bundle date, photo of wiring, etc.

JayToltTech commented 2 years ago

@LAWBear I have an identical configuration and I had your problem until I flashed to W102-1.7.4 which fixed the problem.

My suspicion would be that your flash didn't work as expected. I had to flash a few times to get it right, though I don't think I saw a 'false positive' where it said it flashed but didn't like seems to be in your case.

anecdata commented 2 years ago

And just to be squeaky-clean about it, you can use the erase_flash option before the flashing step.

I'd triple-check solders and wiring from M4-to-Airlift too, especially if this is not the FeatherWing. I can't tell you how many times I've thought for sure the wiring was correct and solid, and then found something wrong, even in the breadboard or the power sourcing.

Though not necessarily the recommended procedure, you can also try skipping the passthrough and use esptool directly in many cases if you have a separate serial-to-USB converter, but this process introduces its own variables into the mix.

LAWBear commented 2 years ago

Many thanks to the wizards, I will implement all checks and suggestions soonest.

dhalbert commented 2 years ago

Closing as possibly resolved, please reopen if not.