Björn Quentin

False alarm caused by unintendedly enabling ps-max-modem in that branch (but proves that using modem sleep makes getting the IP address harder)

I don't see anything I can do at least (or anything we can do by changing code at all) - I spent almost a day trying out multiple scenarios -...

Maybe the HAL could check the reset reset-reason during start-up and initialize that memory region if needed (and not touching it otherwise) 🤔

I'd say option 3 probably results in the best developer-experience. Some interrupts are enabled by the second stage bootloader but very early we disable all known interrupts - if any...

> Maybe `persistent`? > > I was thinking of an option to allow reducing the list of reset reasons that skip initialization. Perhaps `#[ram(…, persistent)]` to use the default list...

I don't think `save-image` (by default) writes anything but the firmware image. e.g. we use it in the "OTA example" (which is not over-the-air actually): https://github.com/esp-rs/esp-hal/blob/99042a7d60388580459eab6fe0d10e2f89d6ab6c/examples/src/bin/ota_update.rs#L10 There is a command...

Mind posting some more details (e.g. exact steps to reproduce, the errors you see)? I will close this for now - feel free to re-open with more details

I like the idea of runtime binding of interrupt handlers as suggested here: https://github.com/esp-rs/esp-hal/pull/1047#issuecomment-1864602855 I had a brief look at our code and I think it won't add much more...

Basically, had a similar thing in mind (minus the type-state). > Most likely this will be done through the constructor of peripheral drivers. And in case of non-async we probably...

I wanted to start working on the real implementation of this after the next HAL release (I certainly can start behind the curtain earlier). Good thing is we don't need...