Björn Quentin
Björn Quentin
We now have working basic light-sleep and a few more wakeup-sources. I _think_ for remaining features we should have separate issues as needed instead of keeping this issue open forever
I suggest closing this issue and creating new issues as needed for retaining CPU state etc. when we see a need for it. Feel free to re-open if you disagree
Ok maybe it's not a real issue but just "bad luck" on my side. This is the code triggering the problem for me ```rust #![no_std] #![no_main] use defmt_rtt as _;...
Sure - just forgot that 😄 ```toml [package] name = "cp0" version = "0.1.0" edition = "2021" [dependencies] esp-backtrace = { version = "0.14.0", default-features = false, features = [...
One thing which might be worth checking would be the power-supply. Curious about the outcome of this
Regarding getting the IP: it sometimes takes "forever" for me but generally works. Definitely something to look into. Regarding USB connection: You need to use the `phy-enable-usb` feature, see https://github.com/esp-rs/esp-hal/tree/main/esp-wifi#usb-serial-jtag
Any news here?
> @bjoernQ Could the esp-wifi scheduler be replaced by an embassy task instead (as an option)? No, we need a preemptive scheduler for the drivers to work
While I was on it, I looked into ESP32 without any luck. There are quite a few chapters in the ESP32 Errata document and also esp-idf seems to include some...
I also experienced problems with GPIO 1 while others work fine: https://github.com/esp-rs/esp-hal/issues/1207#issuecomment-1971291234