Unable to Perform Silent Installation of TrueSTUDIO v9.3.0

[Martin42]

Hello,

I'm trying to silently install Atollic TrueSTUDIO for STM32 v9.3.0 for use in a CI/CD pipeline.

I'm launching the installer from a .bat file using the following command:

Atollic_TrueSTUDIO_for_STM32_windows_x86_v9.3.0_20190212-0734.exe /S /D=C:\Tools\TrueSTUDIO

Were:
/S = Silent installation (commonly used with NSIS-based installers)
/D= = Destination path for installation

The installation does not run in silent mode – the graphical installer still appears. There are no error messages, but also no indication that a background installation is taking place.

Does the TrueSTUDIO installer support silent installation at all?
Setup Details:
TrueSTUDIO Version: 9.3.0 (Build 20190212-0734)
Platform: Windows 11
Installer Filename: Atollic_TrueSTUDIO_for_STM32_windows_x86_v9.3.0_20190212-0734.exe

Any insights or suggestions would be greatly appreciated – thanks in advance!

Martin

 

 

[Peter BENSCH]

Silent install is an option with NSIS, not a standard. However, I would like to point out that Atollic Truestudio has Not been Recommended for New Developments (NRND) for a very long time. Due to the outdated database of supported MCUs alone, the constantly updated STM32CubeIDE should be used instead.

Regards
/Peter

[Martin42]

Hi Peter,

Thanks for your response – and yes, I'm aware that Atollic TrueSTUDIO is not recommended for new designs and no longer recommended for new developments. In this particular case, however, we're maintaining a legacy toolchain for an existing setup, and for that reason, TrueSTUDIO is still required.

That's why I'm specifically interested in whether a silent installation is possible with the provided Windows .exe installer – even though it's an older setup.

 

Best regards,
Martin

[Martin42]

Hi everyone,

just a quick update in case anyone faces a similar challenge:
I manually installed TrueSTUDIO once, then simply zipped the installation directory and now use that archive in our CI/CD environment.
Of course, it's not a "clean" solution, but for our legacy use case, it works reliably.

Maybe this pragmatic approach will help someone else as well.

Best regards,
Martin