cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Default CubeMX Settings for NUCLEO-F446RE

Kristof Mulier
Associate III

The target MCU on the NUCLEO-F446RE board receives its clock input directly from the on-board STLink-V2.1 probe (see clock signal MCO in figure below):

KristofMulier_1-1710354070214.png

That's because the crystal X3 is not soldered on the board by default. So, when I launch a new project in CubeMX for this particular board, I would expect to see this reflected in the clock settings:

KristofMulier_2-1710354254259.png

However, I see the following:

KristofMulier_4-1710354329998.png

 

That's weird. The default selection is 'Crystal/Ceramic Resonator' while in fact, no high-speed crystal is soldered on the board.

Is this an error in CubeMX? If so, then the following .ioc file must be fixed:

C:/Program Files/STMicroelectronics/STM32Cube/STM32CubeMX/db/plugins/boardmanager/boards/A42_Nucleo_NUCLEO-F446RE_STM32F446RE_Board_AllConfig.ioc

 

1 ACCEPTED SOLUTION

Accepted Solutions

If you want to have the HSE and LSE disabled on default generated code, Select No on the option "Initialize all peripherals with their default mode?":

STTwo32_0-1710763770549.png

STTwo32_2-1710763795641.png

But If you check Yes, LSE and HSE will be set to Crystal/Ceramic Resonator so you can start directly configuring and using them on your codes:

STTwo32_3-1710763971743.png

Best Regards.

STTwo-32

 

 

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.

View solution in original post

5 REPLIES 5
STTwo-32
ST Employee

Hello @Kristof Mulier 

I will escalate your request to the concerned team for review.

Best Regards.

STTwo-32 

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.

Thank you very much @STTwo-32 

I also noticed that having HSE set to "Crystal/Ceramic Resonator" in CubeMX results in a functional project (the LED blinks on my Nucleo board) - despite the fact that no crystal is soldered. So could it be that choosing either "BYPASS Clock Source" or "Crystal/Ceramic Resonator" doesn't matter after all?

 

Or maybe the board works, but the wrong setting causes the MCU to wear out quickly. I've heard stories that wrong crystal settings can result in a "functional" MCU that dies after one year instead of 10.

 

Kind regards,

Kristof

Hello @Kristof Mulier 

After checking, The default initialization of the HSE is Crystal/Ceramic Resonator but the clock source is configured to PLL_HSI. So, the HSE mode doesn't have any effect on the function. 

Best Regards.

STTwo-32

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.

Thank you @STTwo-32 

However, it's still confusing that the default initialization of the HSE doesn't correspond to the clock source setting. Shouldn't STMicro change the default settings then, such that we're no longer confused?

If you want to have the HSE and LSE disabled on default generated code, Select No on the option "Initialize all peripherals with their default mode?":

STTwo32_0-1710763770549.png

STTwo32_2-1710763795641.png

But If you check Yes, LSE and HSE will be set to Crystal/Ceramic Resonator so you can start directly configuring and using them on your codes:

STTwo32_3-1710763971743.png

Best Regards.

STTwo-32

 

 

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.