-
Notifications
You must be signed in to change notification settings - Fork 0
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
WiFiWebClient sketch from Mbed WiFi library does not connect to AP with Pico and ESP-Host #1
Comments
default SPI in Mbed Core uses pins 16, 18, 19 for Pico. |
right sorry.
|
Sure, I did:
As well as the header file:
|
the C3 version of the firmware uses 30 MHz SPI. I wonder that with Pico Core it worked without |
Adding
I wonder why the ESPHost-EMAC does not apply RESET ( ESPHOST_RESET=9 ) to the ESP32-C3 every time the sketch boots up, like the Pico Core does. |
did you restart the IDE after changing boards.local.txt? reset is done by the ESPHost library so that should be the same |
I use
I wonder if the Mbed Core uses the same PinName-to-GPIO mapping as the Pico Core does... |
for Pico in Mbed Core pins mapping is simple. pins 0 to 29 are p0 to p29. last time I wired the Pico to C3 I didn't test with Mbed Core only with the Pico Core so now I wired them together again. I will test it tomorrow. |
I guessed that by noticing "can work" words in the statement below:
|
that is because Nano RP2040 has ESP32 on board and the other two require to wire an ESP32 to them |
I tested it and it works. Maybe Mbed Core or the WiFi library has some problem with your WiFi? Is it WPA? |
Board: Raspberry Pico
Core: ArduinoCore-Mbed 4.1.1
Sketch: WiFiWebClient
I can see numerous messages in a loop:
When I monitor UART messages from ESP-C3 Host - the log is empty.
My boards,local.txt file contains the following:
This issue happens with ESPHost-EMAC and Arduino-Mbed Core only.
The same hardware works fine with ESPHost driver integrated into Arduino PRP2040 Core developed by Earle Philhower (3.8.0).
boards,local.txt file for Earle's Core contains the following:
When I monitor UART messages from ESP-C3 Host connected to the Pico with Earle's Core - I can see regular boot log messages and connection session.
The text was updated successfully, but these errors were encountered: