Dániel Buga

Hacky chip, hacky solutions: if the flashed application bricked the device - by IDK, turning off clocks completely, connecting to the rescue DP is supposed to trigger a reset that...

Let's start by stating that I've tried the obvious: copying config values from esp-idf-svc. Unfortunately, it looks like this issue isn't as easy as a misconfigured softAP.

> TinyCrypt is that basically a no-op thing that makes things compile but break as soon as anything needs crypto? this is essentially what we seem to be experiencing at...

You kinda do (need the matrix), because you can't select two alternate functions for the same pin. I spent more time on this today than I'd like to admit.

probe-rs can not communicate over a USB serial port, you'll need to use espflash for that device I'm afraid. That being said, this is a common enough issue that we...

Don't confuse the chip version with the development board's version. You can see the chip's version info if you run `espflash board-info` (which is, indeed, a bit of a misleadingly...

https://docs.espressif.com/projects/rust/book/getting-started/tooling/probe-rs.html probe-rs requires an external debug probe to work with an ESP32

I'm not convinced my analysis is correct here. While I'm confident that the interrupt handler remains active and that it can wake up the task it's registered to, that wakeup...

I don't think anything should be done with this right now. As long as I can't explain the lockup, nothing is broken except for my logic.

I've deleted the incorrect description. I'm leaving the issue open because the title is correct. Feel free to close in case handling the interrupt can be tolerated.