4
\$\begingroup\$

I have done many Arm embedded design projects in gcc using Maxim chips. Every few years I attempt to download STM tools to see if STM stuff is working yet. (Five years ago I got some tools working but the SWD interface on STM chips was unresponsive. At the time I was happy to switch to Maxim as a result. Now there are supposedly some new MCUs out and I want to see for myself if this is real, or just more vaporware and/or impossibly steep learning curves.)

Today I downloaded the STM32CubeIDE from here. I used the Debian version for Ubuntu as recommended in UM2563 (the STM32CubeIDE installation guide). Then I did

./st-stm32cubeide_1.18.0_24413_20250227_1633_amd64.deb_bundle.sh

It claims to have succeeded:

: N: Download is performed unsandboxed as root as file '/root/stm32/makeself_dir_XiCZzS/libtinfo5_6.4-2_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) STM32CubeIDE installed successfully

Note the sentence "STM32CubeIDE installed successfully". Now, according to this site, I am next supposed to Launch the software. With no hints about how to do that.

I am not getting any autocompletes for st-, stm, or STM. Has anyone gotten this software working? What is the secret?

\$\endgroup\$
4
  • \$\begingroup\$ I have installed it many times under different Linuxes and it has always worked and the program start menus have CubeIDE icon. Also I have used it for well over five years under multiple OSes so I can't share what your rant is about really. And how to install CubeIDE in Ubuntu and how to run it isn't exactly an electrical engineering problem. If you have problems installing and running CubeIDE, perhaps ask on ST forums. \$\endgroup\$ Commented Apr 6 at 20:18
  • \$\begingroup\$ @Justme That's great that it just worked for you. I could be wrong, but according to STM's website, either CubeIDE or Keil (or non-free software) is required to get their examples working. In my experience the vendor examples are a basic aspect of getting a microcontroller working. Of course once we figure out how to compile it in gcc, we can ditch the bloated IDEs. But they are a necessary first step in my experience. So the vendors are in fact making a basic electrical engineering problem (of getting working firmware examples) into a software problem. Sorry that it stretches topicality. \$\endgroup\$ Commented Apr 6 at 22:15
  • \$\begingroup\$ Why would you need to use these IDEs to get the examples working? Why not just learn from them and redo them to use GCC right from the start? At the end of the day there are two distinct processes, building the executable and uploading it to the target. You can tackle both of them separately. \$\endgroup\$ Commented Apr 7 at 6:04
  • \$\begingroup\$ @the busybee In my experience, it is easier to start with a working example. If we just took the code from github and put it in GCC, software tends to be too fragile, and something doesn't work, and there is not enough documentation to quickly identify what's wrong. There can be all kinds of issues, like the linker silently omitting some startup code, missing switches, etc. Not that we couldn't work through all that, but starting with a working example is faster overall. And that means using frustrating IDEs at the beginning. I wish it were easier but this is my observation of how things work. \$\endgroup\$ Commented May 4 at 18:52

1 Answer 1

Reset to default
4
\$\begingroup\$

The script appears to put the program in /opt/st. Run it by typing the following command.

/opt/st/stm32cubeide_1.18.0/stm32cubeide

(replacing 1.18.0 by the version you installed, if necessary)

\$\endgroup\$
2
  • 2
    \$\begingroup\$ Thanks for updating \$\endgroup\$ Commented Apr 7 at 5:32
  • \$\begingroup\$ I'd point out that if you don't want to type the full path every time, you can add /opt/st/stm32cubeide_1.18.0 to $PATH variable. \$\endgroup\$ Commented Apr 7 at 10:23

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.