Open lyusupov opened 7 months ago
default SPI in Mbed Core uses pins 16, 18, 19 for Pico.
right sorry. did you do this from README?
In WiFi.cpp add this line at the end of the file.
arduino::WiFiClass WiFi(WiFiInterface::get_default_instance());
Sure, I did:
$ tail -10 libraries/WiFi/src/WiFi.cpp
arduino::WiFiClass WiFi(WiFiInterface::get_default_instance());
#endif
// every specialization library should declare its own WiFI object: eg
//
// static ESP8266Interface wifi_if(PD_8, PD_9);
// arduino::WiFiClass WiFi(&wifi_if);
arduino::WiFiClass WiFi(WiFiInterface::get_default_instance());
As well as the header file:
#if 1 // defined(COMPONENT_4343W_FS)
#include "WhdSoftAPInterface.h"
#endif
the C3 version of the firmware uses 30 MHz SPI. I wonder that with Pico Core it worked without -DESPHOSTSPI_MHZ=30
Adding -DESPHOSTSPI_MHZ=30
to boards,local.txt file gives no positive effect to me.
$ tail -2 ~/.arduino15/packages/arduino/hardware/mbed_rp2040/4.1.1/boards.local.txt
pico.build.extra_flags=-DESPHOST_RESET=9 -DESPHOST_HANDSHAKE=7 -DESPHOST_DATA_READY=6 -DESPHOST_CS=17 -DESPHOSTSPI=SPI -DESPHOSTSPI_MHZ=30
I wonder why the ESPHost-EMAC does not apply RESET _( ESPHOSTRESET=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
did you restart the IDE after changing boards.local.txt?
I use arduino-cli.
It senses all the dependencies and makes a complete rebuild when necessary.
It did the complete sketch rebuild after boards.local.txt update as well.
reset is done by the ESPHost library so that should be the same
I wonder if the Mbed Core uses the same PinName-to-GPIO mapping as the Pico Core does... If it does not - it may cause a lot of troubles.
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.
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:
Works with Nano RP2040 Connect and can work with Nano 33 BLE and Raspberry PI Pico with esp32 wired on SPI.
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.