Skip to main content
Associate
June 30, 2025
Solved

Partially disabled conflict is hindering CICD pipeline

  • June 30, 2025
  • 1 reply
  • 524 views

We are having a similar issue as this person here:

https://community.st.com/t5/stm32cubemx-mcus/why-does-the-ioc-file-show-warnings-on-disabled-peripherals/m-p/144500/highlight/true#M5600

One of the responses was that this is just a warning message and is okay.  

But I think this is causing us to have an issue with using a CICD pipeline to handle project generation. 


When I use a build script with project generate I would expect the whole process to be done without interacting with the GUI but an empty warning message actually comes up for me to click 'yes' to before it will go any further. 

 

I tried an .ioc file that I found online to test to see if it would also generate this error and it does not.  

 

I am hoping there is a way to bypass any warnings generated when doing the build using a script. Any help is very appreciated.

Best answer by Souhaib MAZHOUD

Hello @apseftis 

Could you please try to place the line below at the start of the script file:

popupwrapper set

This will prevent the popup from showing.

KR,

Souhaib

 

1 reply

Technical Moderator
July 1, 2025

Hello @apseftis 

Could you please try the description of running STM32CubeMX in command-line mode as stated in UM1718:

"To run STM32CubeMX in command-line mode without UI, use the following command lines:

– On Windows: cd jre\bin\java -jar STM32CubeMX.exe –q 

– On Linux and macOS: ./STM32CubeMX –q"

KR,

Souhaib

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
apseftisAuthor
Associate
July 1, 2025

That’s actually what I’m running with the build script and the dialog still pops up. It will hang until I select yes. 

Update: Well I am actually running: 

java -jar /opt/st/STM32Cube/STM32CubeMX/STM32CubeMX -q build.scr

Because if I run: 

/opt/st/STM32Cube/STM32CubeMX/STM32CubeMX -q build.scr

Then I get stuck at: 

2025-07-01 07:08:08,699 [INFO] ThirdParty:978 - Integrity check success = true
2025-07-01 07:08:08,699 [INFO] IntegrityCheckThread:100 - exiting critical section [integrity check]
2025-07-01 07:08:08,699 [INFO] IntegrityCheckThread:103 - End integrity checks thread

Which may be that warning dialog somehow still getting hung up. 

My build script is: 

config load file.ioc
SetCopyLibrary copy all
SetStructure Advanced
project generate
exit

Souhaib MAZHOUDBest answer
Technical Moderator
July 2, 2025

Hello @apseftis 

Could you please try to place the line below at the start of the script file:

popupwrapper set

This will prevent the popup from showing.

KR,

Souhaib

 

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.