Yes, I have seen these in other contexts. To my understanding, it indicates a problem between the debug probe and the target. It could be the cable or some noise on the connection line.
What helped on my case was using a different debug probe, e.g. J-Link or P&E.