You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add AP (Access Point) mode support to the ESP32::WiFi class in picoruby-esp32, so that PicoRuby code on R2P2-ESP32 can start a Wi-Fi access point in addition to the existing station mode.
Background
On the RP2040 / Pico W side, an equivalent change is being introduced for CYW43:
Implement the AP-mode bindings on top of ESP-IDF's Wi-Fi APIs (esp_wifi_set_mode(WIFI_MODE_AP) etc.).
Keep the first step minimal: bringing up / tearing down the AP. Higher-level concerns (DHCP server tuning, IP configuration helpers, etc.) can be follow-ups.
Add a minimal example and note current limitations, mirroring the structure of PR #400.
Summary
Add AP (Access Point) mode support to the
ESP32::WiFiclass in picoruby-esp32, so that PicoRuby code on R2P2-ESP32 can start a Wi-Fi access point in addition to the existing station mode.Background
On the RP2040 / Pico W side, an equivalent change is being introduced for CYW43:
That PR adds the following Ruby APIs:
CYW43.enable_ap_mode(ssid, password, auth = CYW43::Auth::WPA2_AES_PSK) -> boolCYW43.disable_ap_mode() -> boolWe want
ESP32::WiFito expose a comparable AP mode API so that AP mode is available across both RP2040 and ESP32 targets.Proposed API
Modeled after picoruby/picoruby#400, on the
ESP32::WiFiclass:ESP32::WiFi.enable_ap_mode(ssid, password, auth = <ESP32 default WPA2>) -> boolESP32::WiFi.disable_ap_mode() -> boolThe exact constant name(s) for the auth mode should match existing
ESP32::WiFiconventions.Approach
esp_wifi_set_mode(WIFI_MODE_AP)etc.).Example (target usage)
References