NUCLEO-U5A5ZJ-Q default configuration

[RobinG44]

Hello,

I am currently trying to setup a blink example on NUCLEO-U5A5ZJ-Q and I have a bug using the default configuration from current CubeMX version (6.18.1).
The generated binary ends up in an Error Handler in the SystemClock_Config function. The default clock configuration generated is the following:
 

I have noticed that a similar issue has been notified in 

I have tried to use the bypasses mentioned in the previous post (setting the HSE source to 16 MHz, changing the SYSCLK Mux source, etc.) without success. Particularly, I am not able to find the setting allowing me to set HSE to “Crystal/Ceramic Resonator” in my CubeMX version.

Thanks in advance for helping me resolve this setup issue,

Best regards,
Robin

[AScha.3]

Hi,

set crystal:

..and clock tree :  pll 1P  to 16 M !

because usb needs it:

+

on nucleo U5A5  the clock is coming from the st-link , in first version (?), so 8Mhz , + “bypass” is correct setting.

Look, what is really on your board : if the 16M crystal is there, then 16M + “crystal..” is correct, maybe necent version, then clock tree:

and can use it for USB also:

 

[RobinG44]

​@AScha.3 

Thank you very much for your quick answer
 

Setting this configuration did solve the issue with the HSE input frequency set to 16 Mhz as mentionned in the previous post. Following clock configuration is working on my side if anyone else encounters the problem:
 

 

Just a question remains, why isn’t this the default setup for this board since the setup currently provided doesn’t work?

Thanks again for the support,

Best regards,

Robin

[AScha.3]

..see my post again, i edit...for 16M crystal;

+

>why isn’t this the default setup for this board 

Perhaps STM wants to raise the bar a little…    :)

 

joking...maybe there was a first version with 8M and they forgot to change the default.

[RobinG44]

Sorry ​@AScha.3, I didn’t even read the entire post. When I saw where was the source clock config, I tried right away ;) ! Your comment should be taken as reference for newly users of this board who are having such issues

Yes, maybe a new version of this board was released with a new clock configuration and this was not updated yet in CubeMX… Hope the update will come soon
 

Hope this ticket will help other people and thanks again ​@AScha.3 for your valuable returns