Skip to main content
Ildar Mulyukov
Ildar Mulyukov
Associate
February 17, 2017
Question

CubeMX hangs on ''Clock Configuration'' tab hanging the whole system

  • February 17, 2017
  • 9 replies
  • 3816 views
Posted on February 17, 2017 at 04:44

Hi! I'm using Linux x86_64 with OpenJDK 64-Bit Server VM (build 25.71-b15, mixed mode). The versions affected: 4.19.0, 4.18.0

When I start STM32CubeMX and create a project, everything is fine. But if I click the 'Clock Configuration' tab, the whole X11 session freezes.

Please drop me any idea how to get more info: traces, debug, anything?

#cubemx
This topic has been closed for replies.

9 replies

I
Imen.D
Technical Moderator
February 17, 2017
Posted on February 17, 2017 at 09:03

Hi,

Can you please share the .ioc file and the STM32CubeMX.log file you find under your user directory in the .stm32cubemx folder.

Thanks

Imen

"When your question is answered, please close this topic by clicking ""Accept as Solution"".ThanksImen"
Ildar Mulyukov
Ildar MulyukovAuthor
Associate
February 17, 2017
Posted on February 17, 2017 at 17:11

No input ioc: New Project. Then choose any MCU. Then click the 'Clock Configuration' tab

http://pastebin.ru/g8XI36m3

.
Juergen Rothbaecher
Juergen Rothbaecher
Visitor II
February 26, 2018
Posted on February 26, 2018 at 13:16

 ,

 ,

I don't know if this would preserve the error but you could try save the project before changing to 'Clock Configuration' and paste the complete content of the file for the experts here.

see also my problem

 ,
Ildar Mulyukov
Ildar MulyukovAuthor
Associate
February 17, 2017
Posted on February 17, 2017 at 17:19

Also (as I got developers' attention): in Linux CubeMX creates excessive folders: $HOME/.stm32cubeMX AND $HOME/.stm32cubemx .

And if we could avoid $HOME/STM32Cube in $HOME that'd be very good (XDG says it should be in 

$XDG_DATA_HOME
, which is e.g. 
$HOME
/.local/share)

I
Imen.D
Technical Moderator
February 17, 2017
Posted on February 17, 2017 at 19:26

Hi, 

I will share your feedback internally for more investigation and we will come back to you as soon as possible.

Imen

"When your question is answered, please close this topic by clicking ""Accept as Solution"".ThanksImen"
Sirma Siang
Sirma Siang
ST Employee
February 22, 2017
Posted on February 22, 2017 at 16:58

Hello Ildar,

The log file link is somehow not accessible.

Could you upload it in your post ?

Kind regards

Sirma

Ildar Mulyukov
Ildar MulyukovAuthor
Associate
February 23, 2017
Posted on February 23, 2017 at 10:32

Hi!

The log file is perfectly available. But per your request I repost the log:

http://pastebin.com/JcRc0b1g

 

I don't see how I can upload the log in this forum, sorry.

Sirma Siang
Sirma Siang
ST Employee
February 28, 2017
Posted on February 28, 2017 at 12:39

Hello Ildar,

Thanks for the log.

They looks correct.

I did the experiment by installing Ubuntu16.04 64b distribution.

I have installed openjdk-8-jdk (which seems to be the same version as yours).

    'java -version' returns

     openjdk version '1.8.0_121'

     OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)

     OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode)

Then I have installed CubeMX 4.19.

When I open a new project, and goes under the clock config tab, it does not hang my system.

Are you working on an Ubuntu ?

If not, could you indicate on which distribution you are working ?

Have you tried to use VisualVM to spy java virtual machine activities ?

When your system hang, are you stll able to access another system console ?

Kind regards

Sirma

Rob.Riggs
Rob.Riggs
Senior
March 1, 2017
Posted on March 01, 2017 at 03:01

FWIW, I use Linux (Fedora versions, currently 24) and have never had this problem.  This seems distribution specific.  I do agree about putting the STM32Cube folder under 

$XDG_DATA_HOME. 

Ildar Mulyukov
Ildar MulyukovAuthor
Associate
March 1, 2017
Posted on March 01, 2017 at 07:54

Anyway I made a new log with sending SIGQUIT to Java VM. Hope it'll help.

________________

Attachments :

cubemx.log.zip : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006Hys3&d=%2Fa%2F0X0000000bDO%2FcnZMLHqHOH88pd1XX4qV7D1PCBR8TSUt.tGM1nULac0&asPdf=false
AvaTar
AvaTar
Senior III
March 1, 2017
Posted on March 01, 2017 at 09:11

Have you tried with Oracle Java instead of OpenJDK ?

CubeMX wouldn't be the first quasi-commercial application to fail with the latter.

I guess ST doesn't validate Cube against every possible Linux distribution / Java engine combination.

Ildar Mulyukov
Ildar MulyukovAuthor
Associate
March 1, 2017
Posted on March 01, 2017 at 09:39

I guess ST doesn't validate Cube against every possible Linux distribution / Java engine combination.

I didn't expect anything like that. And I don't blame ST for this non-working combination. I just humbly asked for help for my particular situation.

And hope that either I get enough info to bugreport to my distro OR help find a pitfall in CubeMX that causes that.

Sirma Siang
Sirma Siang
ST Employee
July 6, 2017
Posted on July 06, 2017 at 11:38

Hello Ildar,

It is quite difficult to understand what could go wrong in your config.

I do not beleave that the java VM could be the cause of your graphic hang.

And every config I can test, works well in my side.

I would like to dig into the presence of the win-apps directory in your system.

I feel you are running cube like a windows application using wine, or... ?

CubeMX can run as a Linux native application.

Have you tried to 

download the installation zip and run 'java -jar <path/SetupSTM32CubeMX-xxx.exe', then select a local path (the exe here is just a file container) ?

Kind regards

Sirma

Juergen Rothbaecher
Juergen Rothbaecher
Visitor II
February 26, 2018
Posted on February 26, 2018 at 13:04

I had a similar issue on windows (CubeMX 4.24.0), where a project didnt open anymore. Just for fun I edited the .ioc file manually and deleted all lines starting with 'RCC.'. Then I could open the project again.

Here some context information of my 'corrupt' .ioc file.

PCC.MCU=STM32L051K(6-8)Ux

PCC.PartNumber=STM32L051K8Ux

PCC.Seq0=0

PCC.Series=STM32L0

PCC.Temperature=25

PCC.Vdd=null

PinOutPanel.RotationAngle=0

RCC.AHBFreq_Value=8000000

RCC.APB1Freq_Value=8000000

RCC.APB1TimFreq_Value=8000000

RCC.APB2Freq_Value=2097000

RCC.APB2TimFreq_Value=2097000

RCC.CECFreq_Value=32786.88524590164

RCC.FCLKCortexFreq_Value=8000000

RCC.FamilyName=M

RCC.HCLKFreq_Value=8000000

RCC.HSI16_VALUE=16000000

RCC.HSICECFreq_Value=32786.88524590164

RCC.HSI_VALUE=16000000

RCC.I2C1Freq_Value=2097000

RCC.I2SFreq_Value=8000000

RCC.IPParameters=AHBFreq_Value,APB1Freq_Value,APB1TimFreq_Value,APB2Freq_Value,APB2TimFreq_Value,CECFreq_Value,FCLKCortexFreq_Value,FamilyName,HCLKFreq_Value,HSI16_VALUE,HSICECFreq_Value,HSI_VALUE,I2C1Freq_Value,I2SFreq_Value,LPTIMFreq_Value,LSE_VALUE,LSI_VALUE,MCOFreq_Value,MSI_VALUE,PLLCLKFreq_Value,PLLMCOFreq_Value,PLLMUL,PWRFreq_Value,RTCFreq_Value,SYSCLKFreq_VALUE,TIMFreq_Value,TimSysFreq_Value,USART1Freq_Value,USART2Freq_Value,VCOOutput2Freq_Value,VCOOutputFreq_Value,WatchDogFreq_Value

RCC.LPTIMFreq_Value=2097000

RCC.LSE_VALUE=32768

RCC.LSI_VALUE=37000

RCC.MCOFreq_Value=8000000

RCC.MSI_VALUE=2097000

RCC.PLLCLKFreq_Value=32000000

RCC.PLLMCOFreq_Value=16000000

RCC.PLLMUL=RCC_PLL_MUL8

RCC.PWRFreq_Value=2097000

RCC.RTCFreq_Value=37000

RCC.SYSCLKFreq_VALUE=8000000

RCC.TIMFreq_Value=2097000

RCC.TimSysFreq_Value=8000000

RCC.USART1Freq_Value=8000000

RCC.USART2Freq_Value=2097000

RCC.VCOOutput2Freq_Value=4000000

RCC.VCOOutputFreq_Value=48000000

RCC.WatchDogFreq_Value=37000
Terms & ConditionsAccessibility statement