Dario Nieuwenhuis

This issue is unrelated to the vscode debugger pointer loop issues. This one is something much lower-level, related to the SWD protocol: doing an SWD register write can fault, which...

Unfortunately I've never been able to repro this. I don't know what I did to cause it either! :( #1123 removes one possible case of recursion, but the one I...

the recursion here is "write random reg -> FAULT -> write ABORT to handle the fault -> FAULT -> write ABORT to handle the fault -> FAULT ...", unrelated to...

LGTM other than that typo

For jlink it's indeed a misleading error message, since multidrop is completely unimplemented. It's not supposed to work, it should say so to the user. Cmsis-dap probes like DAP42 and...

I'm seeing the same error message with using a stm32f401 blackpill with the WeAct CMSIS-DAP firmware to debug a stm32f411 blackpill. No idea if it's related. https://gist.github.com/Dirbaio/cc7608b2b2d4f24579159d1089e616d2

double-buffering writes to the second buffer while the algo is flashing the first buffer. I guess while it's flashing the bus is busy so the ram writes to the second...

nrf52 and nrf53 have the same issue. The issue is not WFI. nRF's debug keeps working across WFI. (they honor the DP CDBGPWRUPREQ, unlike stm32 >_>) The issue is while...

the firmware resetting itself (with `SCB::sys_reset()`) works fine. It fails when you hold RST low (for example by pressing the reset button)

I think this is actually 2 separate bugs: - probe-rs-debugger not switching RTT to BlockIfFull, so if you print too fast the buffer fills up, which corrupts the defmt stream....