>> BTW combining semihosting with interrupts is not a good practice anyway. >> Except some basic tests the interrupts are unusable due >> to giant latencies caused by debug halts.
> Hmmm... Can you be more specific on this? What halts do you mean? I > definitely do not set any breakpoints in my tests, and I expect the > interrupts to run at full speed. I presume that the breakpoints used to implement semihosting (e.g. 0xBEAB for Cortex-M7) do actually cause the target to go into debug halt for a period of time even if they're subsequently automatically resumed as part of the semihosting mechanism? And it is those periods in debug halt mode (which will necessarily be "long" in terms of target execution time/cycles?) that Tomas is referring to as being intrusive to program execution on the target?
