4 releases (breaking)

0.3.0 Jan 6, 2025
0.2.0 Aug 5, 2024
0.1.0 Jan 11, 2024
0.0.0 Mar 7, 2023

#2213 in Embedded development

Download history 141/week @ 2024-12-21 119/week @ 2024-12-28 299/week @ 2025-01-04 420/week @ 2025-01-11 406/week @ 2025-01-18 282/week @ 2025-01-25 403/week @ 2025-02-01 1328/week @ 2025-02-08 808/week @ 2025-02-15 615/week @ 2025-02-22 828/week @ 2025-03-01 415/week @ 2025-03-08 922/week @ 2025-03-15 653/week @ 2025-03-22 587/week @ 2025-03-29 350/week @ 2025-04-05

2,572 downloads per month
Used in cyw43-pio

MIT/Apache

555KB
11K SLoC

cyw43

Rust driver for the CYW43439 wifi+bluetooth chip. Implementation based on Infineon/wifi-host-driver.

Works on the following boards:

  • Raspberry Pi Pico W (RP2040)
  • Raspberry Pi Pico 2 W (RP2350A)
  • Pimoroni Pico Plus 2 W (RP2350B)
  • Any board with Raspberry Pi RM2 radio module.
  • Any board with the CYW43439 chip, and possibly others if the protocol is similar enough.

Features

Working:

  • WiFi support
    • Station mode (joining an AP).
    • AP mode (creating an AP)
    • Scanning
    • Sending and receiving Ethernet frames.
    • Using the default MAC address.
    • embassy-net integration.
    • RP2040 PIO driver for the nonstandard half-duplex SPI used in the Pico W.
    • Using IRQ for device events, no busy polling.
    • GPIO support (for LED on the Pico W).
  • Bluetooth support
    • Bluetooth Classic + LE HCI commands.
    • Concurrent operation with WiFi.
    • Implements the bt-hci controller traits.
    • Works with the TrouBLE bluetooth LE stack. Check its repo for examples using cyw43.

Running the WiFi examples

  • Install probe-rs following the instructions at https://probe.rs.
  • cd examples/rp

Example 1: Scan the wifi stations

  • cargo run --release --bin wifi_scan

Example 2: Create an access point (IP and credentials in the code)

  • cargo run --release --bin wifi_ap_tcp_server

Example 3: Connect to an existing network and create a server

  • cargo run --release --bin wifi_tcp_server

After a few seconds, you should see that DHCP picks up an IP address like this

11.944489 DEBUG Acquired IP configuration:
11.944517 DEBUG    IP address:      192.168.0.250/24
11.944620 DEBUG    Default gateway: 192.168.0.33
11.944722 DEBUG    DNS server 0:    192.168.0.33

This example implements a TCP echo server on port 1234. You can try connecting to it with:

nc 192.168.0.250 1234

Send it some data, you should see it echoed back and printed in the firmware's logs.

Dependencies

~2.2–3MB
~56K SLoC