Scott Mabin

So I believe the issue above is a bit of a red-herring and can be resolved quite easily by increasing the failure_retry count in esp_wifi_connect. The other issue happens when...

So I could reproduce this esp-idf, it's most likely my crappy isp router not responding to subsequent scans, switching to a high-quality router and it works flawlessly. It's a shame...

This hal does not currently have a driver for the i2s peripheral.

This is a good idea! We've recently had a PR for the `esp-idf-hal` crate adding this. PR's welcome for this crate too :).

Hi @lily-mara, sorry for the delay! Interesting! I think you're the first person to get `esp32_hal` and `rust-esp32-std-hello` to work nicely! I don't think @schphil had such luck in #64....

~~Works for me:~~ Ignore that, was running the wrong example `cargo +esp-dev espflash --tool cargo --chip esp32 --speed 460800 --example mem --features alloc /dev/ttyUSB0` Are you enabling the `external-ram` feature?...

Scratch what I said above, not working for me either!

Hmm it will be quite awkward, but just about doable I think. One of the idf developers replied to me about the wifi libs [on reddit](https://www.reddit.com/r/rust/comments/d23yl1/rust_on_the_esp32/ezvrh7z/?context=3) that explains a little...

Essentially we need to reimplement this file https://github.com/espressif/esp-idf/blob/master/components/esp32/esp_adapter.c , but it's not quite that straight forward as implementing requires: - [ ] NVS driver - [x] Allocation, not sure how...

Oh excellent! I started something similar, but will now put my efforts into esp-rs/esp32-wifi!