cancel
Showing results for 
Search instead for 
Did you mean: 

STM32F4 OSC Problem

Scarlet
Associate III

Hi everyone

I'm currently using the NUCLEO-F429ZI development board. I'm planning to create a PCB using the STM32F429ZIT6, but I've encountered some questions during the planning stage.

  1. According to the datasheet, HSE_OSC is specified to provide 8MHz, and CubeIDE also indicates "Input Freq HSE = 8MHz." However, on the NUCLEO-F429ZI development board, the JFVNY 25.000 oscillator supplies 25MHz. I have verified that the SPI clock indeed derives from multiplying and dividing an 8MHz source, but when I measure the JFVNY 25.000 oscillator on the development board, it does indeed supply 25MHz. Why are these two frequencies inconsistent, or am I misunderstanding something?
  2. Referring to the Clock tree and considering, if not using the RTC section, is it possible to omit providing the external LSE_OSE?
20 REPLIES 20

JFVNY is not mentioned in the document, it is the packaged font on the development board.

Yes, X3 is the HSE OSC.

Although I'm not entirely sure about the meaning of 'not provided,' I should be able to design with HSE 8MHz.

Thank you.


I should be able to design with HSE 8MHz.

Yes without Constraints/Issues. And as I said, use PLL to reach your system frequency target.

You can use CubeMx that helps you to find your target frequencies:

SofLit_0-1713367985802.png

 

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.

@Scarlet wrote:

Yes, X3 is the HSE OSC.


No, it's not the oscillator; it's just the crystal - ie, the resonant element for the oscillator.

 


@Scarlet wrote:

Although I'm not entirely sure about the meaning of 'not provided,


It means it isn't fitted to the board:

AndrewNeil_0-1713373246614.png

 


@Scarlet wrote:

I should be able to design with HSE 8MHz.


With X3 not fitted, you won't be using HSE at all - you'll be bypassing it, and using the 8MHz clock signal from the ST-Link.


@Scarlet wrote:


So I can use STLink to program the microcontroller without providing an external oscillator externally?

However, the MCU requires an HSE of 8MHz for execution. Right?


The MCU doesn't require HSE at all.

HSE is just one of the many potential clock sources.

The default for the board is to bypass the HSE, and use the 8MHz clock signal provided by the ST-Link

AndrewNeil_0-1713373664335.png

 

My current understanding is that there is no X3 OSC on the development board, and the 8MHz is currently provided by the STLink. Right!?

Yes. By default X3 is not populated, for external clock source STLink MCO is an alternative.

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.

@Scarlet wrote:

My current understanding is that there is no X3 OSC on the development board, and the 8MHz is currently provided by the STLink. Right!?


Again, X3 is just a crystal - it's not an oscillator:

  • The oscillator is within the STM32 - so that is always present;
  • The crystal needs to be provided externally - it is not present on the NUCLEO-F429ZI board.

https://www.avrfreaks.net/s/topic/a5C3l000000UYYQEA4/t146620?comment=P-1401006

 


@Scarlet wrote:

 the 8MHz is currently provided by the STLink. Right!?


Yes.



Again, X3 is just a crystal - it's not an oscillator:

Okay, I will research the differences between the two.

Thanks.


@Scarlet wrote:


Okay, I will research the differences between the two.


Unfortunately, the link in that AVRFreaks post that I referenced seems to be broken.

But here is a description of what's inside a Crystal Oscillator:

https://www.avrfreaks.net/s/topic/a5C3l000000UcE1EAK/t160729

As you can see, an oscillator is a complete active electronic circuit:

 

AndrewNeil_1-1713513145485.png

It contains a crystal plus  all the active circuitry necessary to make it oscillate and give a nice, clean digital clock signal as output.

 

The crystal itself is just a passive component:

 

AndrewNeil_3-1713513282266.png

it requires extra active electronic circuitry to make it oscillate.

In the case of a microcontroller, the oscillator  circuitry is usually inside the microcontroller chip (eg, the HSE within the STM32) - so you just need to provide the crystal externally.

 

Update:

From an article from SiTime describing the difference between a crystal oscillator (XO) and just a crystal (XTAL):

AndrewNeil_1-1730305596522.png

 

https://www.sitime.com/company/newsroom/articles/do-you-know-when-use-crystal-or-oscillator-wrong-answer-can-cost-you

 

#CrystalVsOscillator #OscillatorVsCrystal