fko-kuptec

I am not sure, whether the API was changed or I just misread something. But the `GenericClockController` does **not** consume the `MCLK` at construction. Therefore, it is possible to set...

I already tested it with the `unbounded` feature enabled, since I also assumed this to be the root cause. No luck, however. My last test today was with this configuration:...

Interesting... I cannot reproduce the issue in my minimal example. My best guess would be, that this is a compiler bug again. I've seen them before in my firmware with...

A short update for today: I finally can reproduce the issue with my minimal example. It happens with both `edge-executor` and `async-executor`, but only if the PSRAM is enabled, which...

I am running the tests on ESP32-S3 :)

Finally, you can find the reproduction of the bug in [this repo](https://github.com/fko-kuptec/edge-executor-bug). The README includes instructions, information on what works and what doesn't, and a few stack traces. I have...

> One thing I noticed (still shooting in the dark) is that you are running both async-executor and edge-executor on top of the single-future executor of esp_idf_hal::task::block_on. Have you tried...

Note, though, that I am also running my own executor with the ESP-IDF `block_on()`, which seems to work. Therefore, I don't think thats the root cause.

Oh, and regarding RISC-V: Unfortunately, we don't have any normal ESP32 RISC-V devkits here. The only thing we have is the brand new P4 evaluation kit, but that's a different...

Thank you for taking a look :) > I'm not able to reproduce your crashes without psram so far, but honestly I did not try hard enough. Without PSRAM I...