cancel
Showing results for 
Search instead for 
Did you mean: 

STM-Studio Import Variables fails

AlbertoGarlassi
Associate III

Hello, after selecting the .elf file I get hundred of messages of this type:

GDB Cmd [print /x & arm_cfft_sR_f32_len128.pTwiddle] failed

Error: Address of symbol "arm_cfft_sR_f32_len128" is unknown

and similar, all related to CMSIS.

After I ack all of these errors the import restarts with the same errors, only way out is by killing the program via process manager.

All OK when variable addresses taken from .map are inserted, big pain but OK.

What can be done?

I'm aware of STMCubeMonitor, tried it but it looks like it's a joke, or at least not what I need. I just need a scope and a table to read and write variables. AFAIK CubeMonitor does not even have vertical scale adjust, just to mention the first showstopper.

I'm shure that 99% of people share my needs.

BTW STMCubeMonitor could conveniently be replaced with a binding to Python or whatever, then everybody chooses his own gui, framework etc.

20 REPLIES 20
Garnett.Robert
Senior III

You are correct.

 

The Cube Monitor is a hard way to do a simple task and as you pointed out the charts do no have scaling so if you have variables of greatly different magnitudes then it is useless.

I can't believe anyone in ST would use the monitor for debugging realtime systems.

STM Studio isn't perfect, the horizontal scaling is very clunky, but it takes about five minutes to set up and it is ultra reliable when it runs.