STM32N6570-DK HSE Input Frequency

[mhd0425]

Hello,

 

I am currently evaluating the STM32N6570-DK and am seeking clarification regarding a discrepancy I’ve encountered.

 

I can confirm that there is a 48MHz crystal on board for the HSE. However, the default CubeMX projects generated by the board selector, as well as other example projects I have reviewed, all configure the input frequency to 24MHz.

 

Could you please clarify what the correct input frequency for the HSE should be on this discovery kit?

 

Thank you for your assistance.

[Simon V.]

Hello,

Can you please share which projects please ? I performed a quick check on template project for example and HSE frequency was 48MHz.

Please note from product reference manual HSE peripheral has an optional DIV2 output.

Regards,

Simon

[TDK]

A default project created on the board for me shows 24 MHz, not 48 MHz. Maybe templates are correct, maybe not. The result is still wrong.

 

[Andrew Neil]

What do the board User Manual and Schematics say ?

[mfgkw]

The schematics tells 48 MHz: https://www.st.com/resource/en/schematic_pack/mb1939-n6570-c02-schematic.pdf

 

(In doubt I would use what is printed on the crystal on my board...)

[mhd0425]

@Simon V. The projects are from Infineon AIROC https://github.com/Infineon/AIROC-Wi-Fi-Bluetooth-STM32 but also when I generate a project from board selector. CubeMX 6.16.1 and MPU package for STM32N6 Series version 1.3.0.

I checked the crystal under a microscope. It is labeled 48MHz.

@TDK That is what I see too.

[mhd0425]

I believe this confirms the HSE DIV2 path. However, this might also be incorrect considering the HSE input frequency is actually 48MHz.

 

Could you please review this and let me know your thoughts?

 

Best regards,

 

Mark

[Simon V.]

Hi,

 

I confirm that default template for both N6 DK and N6 Nucleo are wrongly generated using a base frequency for HSE=24MHz. I forward this update request to CubeMx internal team for correction.

Thanks for your input relative to this typo.

Regards,

Simon

[mhd0425]

Thank you very much.

 

-Mark