Hi all!
I am using a Black Magic Probe to debug an STM32 microcontroller that also shares an I2C bus with a few sensors (like MPU6050 and BME280). 
Debugging generally works fine; but when I pause execution / step through code while the MCU is reading from I2C; I sometimes notice garbled signals / ghost traffic on the bus when monitored with a logic analyzer. 
I suspect it has something to do with the MCU being halted mid-transaction while the I2C peripheral is active. 
However, I’ve also noticed that just having the BMP connected to the target board via SWD sometimes introduces subtle noise on the lines, even without active debugging.
I have tried lowering the debug clock and isolating power rails; but the issue persists intermittently.
Has anyone else seen similar I2C instability / noise behavior when using the Black Magic Probe in embedded systems where debugging & I2C share close ground/trace space? I checked Home · blackmagic-debug/blackmagic Wiki · GitHub with Selenium Training related to this and found it quite informative.
I would appreciate any advice on decoupling strategies, firmware safeguards / alternate debug wiring layouts.
Thank you !