STM32CubeMonitor 1.4.0 CPU critical performance issue

[acv_atr]

Hello everyone.

I'm trying to work with STM32CubeMonitor to implement an industrial machine Life Test JIG using 12 ST-LINK v2 probes connected to STM32 microcontrollers by SWD protocol, but I'm facing very strange and anoying issues.

This post will focus only on CPU critical allocation on V1.4.0.

When acq node is started (only after receive start acquisition order) the process allocate 100% of one CPU core.

As shown on the picture below, I'm using at the moment and for development purposes, only two ST-LINK probes, that's why "only" two cores are at 100% allocation.

 

This does not occurs on STM32CubeMonitor V1.3.0

 

According to V1.4.0 release notes the multiple probe acquisitions was improved.

 

Windows 10 pro has the same behaviour on V1.3.0 and V1.4.0

Ubuntu 20.04 Desktop has also been tested and verified.

All installation recomendations defined at wiki have been meet.

Question: Is this CPU allocation expected/known and it's a true improvment relative to v1.3.0?

[acv_atr]

Hello @Richard.Chvr​ .

Any news from dev team or next stm32cubemonitor release?

Thank you for your support and attention.

[acv_atr]

Hi Mr. @Richard.Chvr​ 

Have you already avalilble some news or solutions from dev team?

Thanks for your attention.

Best regards

[Richard.Chvr]

Hi,

In next release 1.5.0, it will will possible to get 2 different modes, either to optimize acquisition frequency or CPU workload depending on a user setting.

Coming soon...

[stephane.legargeant]

Hello

Problem should be fixed in version 1.5.0: For frequency lower than 10Hz, the thread will give back the free time to the CPU, and the CPU usage will decrease.

Please let us know if it is good for you.

Best regards

Stephane