async timer panic about esp-idf-hal HOT 7 CLOSED

expected? No, We currently have lots of moving parts with embassy support, there were recently some atomic changes introduces, that also changed inside our crates and also in embassy, this is potentially an outfall here.

This behavior is completely normal and expected, as per above.

tanks for pointing it out, because of all the atomics stuff these days, they magically grab my attention currently making me blindsided 🥲

from esp-idf-hal.

can you please specify what esp32 you are using specifically? a normal esp32 running on xtensa? Also please clarify what version of the toolchain you are using with rustc --version

from esp-idf-hal.

can you please specify what esp32 you are using specifically? a normal esp32 running on xtensa? Also please clarify what version of the toolchain you are using with rustc --version

rustc 1.75.0-nightly (edf0b1db0 2023-11-10)

[build]
target = "riscv32imc-esp-espidf"

[target.riscv32imc-esp-espidf]
linker = "ldproxy"
# runner = "espflash --monitor" # Select this runner for espflash v1.x.x
runner = "espflash flash --monitor" # Select this runner for espflash v2.x.x
rustflags = ["--cfg", "espidf_time64", "-C", "default-linker-libraries"]

[unstable]
build-std = ["std", "panic_abort"]

[env]
MCU="esp32c3"
# Note: this variable is not used by the pio builder (`cargo build --features pio`)
ESP_IDF_VERSION = "v5.1.1"

from esp-idf-hal.

If I use esp_idf_hal::task::block_on instead of embassy_futures::block_on, it will not panic. Is it expected?

from esp-idf-hal.

expected? No,
We currently have lots of moving parts with embassy support, there were recently some atomic changes introduces, that also changed inside our crates and also in embassy, this is potentially an outfall here.

Before recently the most tested way was to use the edge-executor as a base to run async code, but now we should be in a good position to allow other runners including bigger ones like tokio, with the advent of the possibility to notify waker from ISR context.

@ivmarkov seeing __atomic_compare_exchange_4 in his crash ( we are here running against the riscv_imc target), could this related to the recent changes @Dirbaio made in embassy to help the no_std guys back on track?

from esp-idf-hal.

This is not a panic - look at the top of the stack trace and google "esp idf twdt". And NO you should not be using embassy_futures::block_on. Read the comment above that function as to what it is doing, and that would hopefully explain why the task watchdog is triggering.

from esp-idf-hal.

expected? No, We currently have lots of moving parts with embassy support, there were recently some atomic changes introduces, that also changed inside our crates and also in embassy, this is potentially an outfall here.

This behavior is completely normal and expected, as per above.

from esp-idf-hal.