Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
LAWBear opened this issue Nov 24, 2021 · 5 comments

Comments

@LAWBear
Copy link

LAWBear commented Nov 24, 2021

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
Copy link
Member

anecdata commented Nov 24, 2021

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
Copy link

@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
Copy link
Member

anecdata commented Dec 5, 2021

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
Copy link
Author

LAWBear commented Dec 6, 2021

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

@dhalbert
Copy link
Contributor

dhalbert commented Jun 6, 2022

Closing as possibly resolved, please reopen if not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants