max/embassy
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Modern embedded framework, using Rust and async.
101 Commits 67 Branches 32 Tags 16 MiB
Rust 98.9%
Shell 0.9%
Python 0.2%
33cbc22236
Go to file
Dario Nieuwenhuis 33cbc22236
Merge pull request #39 from kbleeke/pio 
Use PIO for SPI communication in Pico W example
2023-03-21 19:56:57 +01:00
.vscode vscode: recommend extensions, disable toml formatting, update. 2023-03-19 22:36:18 +01:00
examples/rpi-pico-w replace inspect() with direct calls to trace!() after awaiting 2023-03-21 19:39:41 +01:00
firmware Obtain the firmware blobs from the user instead of hardcoding magic flash addrs. 2022-07-17 00:33:30 +02:00
src replace inspect() with direct calls to trace!() after awaiting 2023-03-21 19:39:41 +01:00
.gitignore Obtain the firmware blobs from the user instead of hardcoding magic flash addrs. 2022-07-17 00:33:30 +02:00
Cargo.toml remove use of embedded-hal SPI traits. Instead just call our bus trait directly and push responsibility for implementing CS on the trait implementor 2023-03-21 19:15:54 +01:00
LICENSE-APACHE Add LICENSEs 2022-07-11 22:53:57 +02:00
LICENSE-MIT Add LICENSEs 2022-07-11 22:53:57 +02:00
README.md Get wifi credentials from envvars in example. 2022-07-21 23:50:40 +02:00
rust-toolchain.toml even faster pio speed are possible 2023-03-19 17:00:45 +01:00
rustfmt.toml 🌈 2022-07-10 19:45:26 +02:00

README.md

cyw43

WIP driver for the CYW43439 wifi chip, used in the Raspberry Pi Pico W. Implementation based on Infineon/wifi-host-driver.

Current status

Working:

  • Station mode (joining an AP).
  • Sending and receiving Ethernet frames.
  • Using the default MAC address.
  • embassy-net integration.

TODO:

  • AP mode (creating an AP)
  • GPIO support (used for the Pico W LED)
  • Scanning
  • Setting a custom MAC address.
  • RP2040 PIO driver for the nonstandard half-duplex SPI used in the Pico W. Probably porting this. (Currently bitbanging is used).
  • Using the IRQ pin instead of polling the bus.
  • Bus sleep (unclear what the benefit is. Is it needed for IRQs? or is it just power consumption optimization?)

Running the example

  • cargo install probe-run
  • cd examples/rpi-pico-w
  • WIFI_NETWORK=MyWifiNetwork WIFI_PASSWORD=MyWifiPassword cargo run --release

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

The 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.

License

This work is licensed under either of

at your option.