rust-esp32-std-demo | A demo STD binary crate

Install the Rust Espressif compiler toolchain and the Espressif LLVM Clang toolchain This is necessary, because support for the Xtensa architecture (ESP32 / ESP32-S2 / ESP32-S3) is not upstreamed in LLVM yet
Switch to the esp toolchain from the pre-built binaries: rustup default esp NOTE For ESP32-C3 - which runs a RiscV32 chip - you can just use the stock nightly Rust compiler, and a recent, stock Clang (as in Clang 11+) (You can do this by issuing rustup install nightly and then rustup default nightly instead of installing/building the Rust & Clang ESP forks and switching to their esp toolchain as advised above)
If using the custom Espressif Clang, make sure that you DON'T have a system Clang installed as well, because even if you have the Espressif one first on your $PATH, Bindgen will still pick the system one A workaround that does not require uninstalling the system Clang is to do export LIBCLANG_PATH=<path to the Espressif Clang lib directory> prior to continuing the build process
cargo install ldproxy
Clone this repo: git clone https://github.com/ivmarkov/rust-esp32-std-demo
Enter it: cd rust-esp32-std-demo
Export two environment variables that would contain the SSID & password of your wireless network: export RUST_ESP32_STD_DEMO_WIFI_SSID=<ssid> export RUST_ESP32_STD_DEMO_WIFI_PASS=<ssid>
To configure the demo for your particular board, please uncomment the relevant Rust target for your board and comment the others. Alternatively, just append the --target <target> flag to all cargo build lines below.
Build: cargo build or cargo build --release If you would like to see the async networking in action, use the following build command instead: export ESP_IDF_VERSION=master; cargo build --features native (Only if you happen to have a TTGO T-Display board): Add ttgo to the --features build flags above (as in cargo build --features ttgo) to be greeted with a Hello Rust! message on the board's LED screen (Only if you happen to have an ESP32-S2-Kaluga-1 board): Add kaluga to the --features build flags above (as in cargo build --features kaluga) to be greeted with a Hello Rust! message on the board's LED screen (Only if you happen to have a Heltec LoRa 32 board): Add heltec to the --features build flags above (as in cargo build --features heltec) to be greeted with a Hello Rust! message on the board's LED screen (Only if you happen to have an ESP32-S3-USB-OTG): Build with native and the ESP-IDF master branch and add esp32s3_usb_otg to the --features build flags above (as in export ESP_IDF_VERSION=master; cargo build --features native,esp32s3_usb_otg) to be greeted with a Hello Rust! message on the board's LED screen (Only if you happen to have an Ethernet-to-SPI board based on the W5500 chip): Build with native and the ESP-IDF master branch and add w5500 to the --features build flags above (as in export ESP_IDF_VERSION=master; cargo build --features native,w5500) to have Ethernet connectivity as part of the demo Note that other Ethernet-to-SPI boards might work just fine as well, but you'll have to change the chip from SpiEthDriver::W5500 to whatever chip your SPI board is using, in the demo code itself. (Only if you happen to have an ESP32 board with an onboard IP101 LAN chip and/or a stock ESP32 board connected to an IP101 Ethernet board via RMII): Build with native and the ESP-IDF master branch and add ip101 to the --features build flags above (as in export ESP_IDF_VERSION=master; cargo build --features native,ip101) to have Ethernet connectivity as part of the demo Note that other RMII Ethernet boards might work just fine as well, but you'll have to change the chip from RmiiEthDriver::IP101 to whatever chip your board is using, in the demo code itself.
(Only if you happen to have an ESP32-S2 board and can connect a LED to GPIO Pin 04 and GND): Try accessing http://<dhcp-ip-of-the-board>>/ulp once build is flashed on the MCU