esp-wifi 0.3.0 does not compile for ESP32-C3, it depends on portable-atomic, and that doesnt build for RiscV about esp-wifi-sys HOT 5 CLOSED

I was able to fix the atomic error thanks to taiki-e/portable-atomic#148, however no i get this when compiling esp-wifi 0.3.0

error[E0432]: unresolved import crate::hal::interrupt
--> /Users/admin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-wifi-0.3.0/src/preempt/preempt_riscv.rs:3:17
|
3 | use crate::hal::interrupt::TrapFrame;
| ^^^^^^^^^ could not find interrupt in hal

error[E0432]: unresolved imports crate::hal::interrupt, crate::hal::macros::interrupt
--> /Users/admin/.cargo/registry/src/index.crates.io-6f17d22bba15001f/esp-wifi-0.3.0/src/timer/timer_esp32c3.rs:5:11
|
5 | hal::{interrupt, macros::interrupt, peripherals::Interrupt},
| ^^^^^^^^^ ^^^^^^^^^^^^^^^^^ no interrupt in the root
| |
| no interrupt in the root

from esp-wifi-sys.

esp-wifi releases are tied to esp-hal releases - they need to match! e.g. for 0.3.0 the C3 hal is 0.15.0: https://crates.io/crates/esp-wifi/0.3.0/dependencies

additionally the way how atomics are handled in esp-hal changed at some point in time - for later HAL versions atomic emulation was removed so you need to remove this: https://github.com/makepaddev/rc_radio/blob/a04fd8eec7278f7d924d11488b25bf384c249050/.cargo/config.toml#L13-L27

from esp-wifi-sys.

That message about the esp32s3 is coming from ROM code, which is burned into flash at the factory - this means you have an esp32s3 board, not a esp32c3 board. Try flashing the example targetting the esp32s3.

from esp-wifi-sys.

Sorry im mistaken, i had an S3 board plugged in, nevermind.

from esp-wifi-sys.

Alright it works! I have a working example. Thanks. Closing.

from esp-wifi-sys.