2020-09-18 10:45 PM
I have just installed STM32CubeMonitor as an alternative to STM32Studio since I am no longer using Windows. I have been a happy user of STM32Studio but have been frustrated with the lack of Linux support, so I was excited to see that STM32CubeMonitor supported Linux.
Unfortunately my first experience with it did not meet my expectations.
Finally I would also like to ask about why both the Probe Out and Probe In is needed when you only want to do acquisition (input). Why is the Probe Out needed?
Best regards
Thomas Jespersen
Solved! Go to Solution.
2020-11-23 12:11 AM
@Thomas Jespersen
Hello Thomas
In version 1.0.0, the parsing of c++ classes in the elf file was not supported and classes were skipped. But if the address is known, it can be added manually in the variable to monitor.
In 1.1.0, the class variables which have static address in the elf file are listed.
Best regards
Stephane
2020-09-21 12:26 AM
Hello Thomas
I don't see the picture with the ELF parser stuck. Nevertheless, are you using version V1.1.0 ? We have done some fix, it may solve the issue.
For the acquisition speed, with a Ubuntu 18.04.5 and board Nucleo-F411RE and version 1.1.0, I have around 800 points per seconds. So I am surprised that you have only 10Hz. May be there is a display issue with your computer ? Can you try to record the data in the processing node (log all values) and check if you have samples in the file ?
For the Probe In and Probe Out, we need both because the Probe Out send the configuration and the request to the probe, while the Probe In receives the results.
In node-RED many nodes works in pair (serial in/out, web socket, http). We tried to have similar design.
Thanks
Stephane
2020-09-22 06:04 PM
Yes, I am using V1.1.0. I have tried to attach the image again.
2020-09-23 12:18 AM
Hello Thomas.
It seems there is something blocking the elf parser in your elf. What is the size of the file ?
Is it possible to share the elf with me ? (you can send me a private message)
Best regards
Stephane
2020-10-07 07:15 AM
It seems that problem is only present in version 1.1.0 of STM32CubeMonitor.
By installing version 1.0.0 I am able to load the ELF file successfully.
PS. I am using C++ in my embedded project. Maybe this plays a role when loading?
2020-10-07 08:43 AM
Hello Thomas.
The support of some c++ symbols has been added in V1.1.0, so it may generate an issue during the parser. In V1.0.0, these symbols were skipped. .
Stephane
2020-10-12 02:27 AM
Hello
We have identified an issue : The tool fails to parse the c++ classes which have references to themselves.
As c++ classes is a new feature of V1.1.0, it is possible to use the version 1.0.0 as a workaround if you face this issue.
Stephane
2020-11-20 08:19 PM
Does this mean that C++ is not supported in V1.0.0?
2020-11-23 12:11 AM
@Thomas Jespersen
Hello Thomas
In version 1.0.0, the parsing of c++ classes in the elf file was not supported and classes were skipped. But if the address is known, it can be added manually in the variable to monitor.
In 1.1.0, the class variables which have static address in the elf file are listed.
Best regards
Stephane