Chris Reed

What type(s) of probe(s) are you using? That could narrow down the possibilities.

Very interesting, I'm surprised it leaks with no probe attached. That's very helpful.

I can reproduce it on macOS 10.15 with one CMSIS-DAPv1 (hidapi), one CMSIS-DAPv2 (libusb), and an STLinkV2-1 (libusb). It doesn't seem to leak when no probes are attached. I need...

Hi @j4cbo, yeah, that's a tricky one without a completely right answer. I think it depends on what you're debugging—ultimately it's something you need to configure. In almost all cases...

Good point. Thanks for complaining about it! 😄

This is a known issue with the STM32F7 series. This series (and the H7 series) requires some special handling to recover from low power modes that other STM32 device don't....

Hi @martinpriestley, yeah, unfortunately the structure of the J-Link low level API doesn't really make it possible to do fast memory transfers. There is already a method in pyocd to...

I hadn't even thought of checking the J-Link docs for command strings. The `CORESIGHT_SetIndexAHBAPToUse` and APB variant commands certainly look like they might work. We'll have to see how they...

> That seems to be by Cortex family. Being based on the Cortex family raises a potential issue. The J-Link DLL requires you to pass in the device name. Right...

Going to pause this one. More work is needed. A `KeyboardInterrupt` could still be raised from within (for instance) the CMSIS-DAP internal packet management code, which can break the sequencing...