2022-05-16 08:15 AM
Hi,
I want to understand fundamentally how the STM32CubeMonitor is able to monitor my memory and the tradeoffs of using such software.
Is there some documentation on the topic? I can't find anything.
How does the atomicity work? Is the core stopped while the st-link is reading memory? Are you using special ARM cortex-m instructions?
Thanks,
Gabriel
EDIT: if needed, I'm using the STM32CubeMonitor v1.4.0
Solved! Go to Solution.
2022-05-16 08:22 AM
The core doesnt look to me to be stopped while the stlink is reading memory, i am able to run motor control algoritms and very fast softpwm syntetizers while using cubemonitor without any spurious spike.
It is my understanding the SWD peripheral accesses the AHB bus independently so if your application makes intensive use of the AHB bus you might notice something.
https://www.cnblogs.com/shangdawei/p/4753040.html
2022-05-16 08:22 AM
The core doesnt look to me to be stopped while the stlink is reading memory, i am able to run motor control algoritms and very fast softpwm syntetizers while using cubemonitor without any spurious spike.
It is my understanding the SWD peripheral accesses the AHB bus independently so if your application makes intensive use of the AHB bus you might notice something.
https://www.cnblogs.com/shangdawei/p/4753040.html
2022-05-17 08:15 AM
Interesting @Javier Muñoz, I'm gonna take a look at the AHB bus.