Skip to main content
Markus GIRDLAND
ST Employee
May 15, 2019
Question

Features and known issues in STM32CubeIDE

  • May 15, 2019
  • 24 replies
  • 10958 views

Dear community,

Edit: This thread was initially made to clear up some confusion about what functionality STM32CubeIDE was intended to have. As the tool has now been released for a while I believe that is has become more clear. However, having easy access to the known problems and limitations is still very helpful so I will keep this thread pinned.

Although, to spare myself from having to continuously update this thread I will simply link to the release note where this information is available:

The release note can be found here (RN0114).

This topic has been closed for replies.

24 replies

EMitu
Associate III
August 12, 2019

I found another bug. The path "Window->Preferences->Run/Debug->C/C++ Embedded Aplication->Serial Wire Viewer" doesn't exist. Right path "Windows->Preferences->STM32Cube->Serial Wire Viewer'0690X0000098QyyQAE.jpg0690X0000098Qz3QAE.jpg

Gabriel Staples
Associate
August 14, 2019
matheusmbar
Associate
August 14, 2019
mute

*Matheus Marques Barbosa*
Tesla DeLorean
Guru
August 14, 2019

Still getting reports of project import function failing to build with Java NULL pointer errors.

x-cube-spn2 SW4STM32 project imported into CubeIDE

An internal error occurred during: "Build Project".

java.lang.NullPointerException

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
mattias norlander
ST Employee
August 15, 2019

The original .cproject file contains dynamic variables which are not expanded. Apparently SW4STM32 can cope with these. CubeIDE cannot. Will discuss the issue internally with relevant teams. Thanks for reporting!

koincidencia
Visitor II
August 15, 2019

I don't know where is the best place to add my bug report, but it is really annoying. With CubeIDE version v1.0.2 on a windows10 machine when I change some peripheral settings in the CubeMX plugin and regenerate the project the source location and include path settings are reverted back to default (both in Basic and Advanced folder structure settings). This is very annoying if your custom code is in a separate folder.

mattias norlander
ST Employee
August 16, 2019

Thanks! Confirmed regression. Will look into this for next release.

XChen.19
Visitor II
August 16, 2019

Hi, I have encountered two problems when using STM32CUBEIDE.

  1. Project configurations would be totally lost when regenerating the source file from .ioc file.
  2. In regenerating the source file from .ioc file, the error box "create startup failure: cannot copy script template" would pop out sometimes.

mattias norlander
ST Employee
August 16, 2019

Confirmed. Same thing as reported by szabolcs.vereb1 above. Very annoying. Will look into it. Also considering how to improve our automatic validation test suites for the future.

A big challenge is that since MX and Eclipse are based on different GUI frameworks. There is no single UI test tool that can interact and test both tools. Hence we use different UI test tools for the MX and IDE. This makes it difficult to run test campaigns that exercises real development cycles using both tools in iterations.

paul vertebny
Visitor II
August 30, 2019

Hi,

the error box "create startup failure: cannot copy script template" will pop out because some file becomes marked read-only. For me it is the startup_stm32xxxxx.s file. I clear the read-only flag but a little while later this file becomes read-only again. I suppose the CubeMX plug-in does it.

About the big challenge. If some plug-in functionality such as files generating isn't tightly coupled with GUI, there should be no (big) problem to automate tests of such functionality independent of GUI kind. ;)

Paolo Andreuzza
Associate III
August 28, 2019
mattias norlander
ST Employee
September 5, 2019

Thanks, will be fixed in the next version.

DSukh.5
Visitor II
September 1, 2019

In CubeMX 5.3/CubeIde 1.0.2 on windows 10 it always hangs/freezes on generating user code

Vincent Grennerat
Associate
September 5, 2019

How is it possible that ST dares to put online an official video ( https://www.youtube.com/watch?v=eumKLXNlM0U ) showing the RUN button in the toolbar and at 2'11" showing the RUN function in the drop-down menu whereas this functionality is not available in the released version of the IDE !

I have lost several hours trying to mess with running configurations in order to get the RUN button like in the video, before eventually finding the info in the release notes.

I can't even understand why in the first place STM32CubeIDE was released without this major functionality.

mattias norlander
ST Employee
September 5, 2019

Run configurations/External Tool configurations was not implemented properly in time for Mass-market release. Therefore these options were simply disabled since they would generate more headaches (support-wise) then benefit. It is unfortunate that the video referred to above, had to be made with a nightly build before release which clearly differs from 1.0.0 Mass-market release build.

There are many different teams involved to develop the ever-growing Cube ecosystem. We do our best to stay agile and honor customer requests while at the same time trying to stay internally in sync and aligned with all team. Quite a challenge. The video issue is probably a good example of that challenge.

The Run/External tools configuration is on the to-do list to be re-introduce, but compared to other more pressing bug fixes and feature requests I would say that the priority is not high as of right now. Sorry for the inconvenience!

Paolo Andreuzza
Associate III
September 5, 2019

Mattias,

what you say is understandable, and the effort that ST puts into carrying out the project is commendable.

To keep users informed about the planning of new features (for example the RUN function), it would be useful for the entire user community to know the product development roadmap, this, not to set constraints, but to share experiences.

scherbakoff.dima
Visitor II
September 12, 2019

I am trying to blink LED of my old STM32VLDISCOVERY board using brand new STM32CubeIDE under Linux. My Linux us Linux Mint 19.2, based on Ubuntu 18.04. The latter support is declared by ST.

What does not work:

1) Debugging

2) There is no download/flash/run button (according to Release Note it is not implemented)

How to reproduce:

1) Create new project for board STM32VLDISCOVERY

2) Try to debug

3) Get following errors:

https://www.dropbox.com/s/rpsel3tqy70kaoa/STM32_1.png?dl=0

https://www.dropbox.com/s/sdnto14jo526qkz/STM32_2.png?dl=0

https://www.dropbox.com/s/qy8pcwk8hybmn18/STM32_3.png?dl=0

I have not succeeded in flashing yet, because any configuration does not work.

How can I flash STM32 via ST-LINK/V1 under Linux?

Thanks in advance.

UPD1: Replaced images with Dropbox links, due to they loss from community.st.com

mattias norlander
ST Employee
September 12, 2019

The ST-LINK V1 is not supported by CubeIDE. This board embeds the V1. And it is the only or one of very few with this version of ST-LINK. Unfortunately no plans of implementing support for ST-LINK V1.

Maybe you can flash your application with ST-LINK Utility. You may then be able to just connect and debug with ST-LINK V1 in CubeIDE. But this is not something we test and validate. Just a possible way forward for you to try...