Skip to main content
mickminn
mickminn
Associate II
July 25, 2019
Question

Why does STM32CubeMX show a conflict between CRS_SYNC and DEBUG?

  • July 25, 2019
  • 0 replies
  • 1160 views

Hello,

I am starting a project using STM32CubeMX v5.3.0 and looking at using the STM32H745ZI. If I set up the following options:

  • RCC Low Speed Clock (LSE) to "Crystal/Ceramic Resonator"
  • RCC CRS SYNC to "CRS SYNC Source LSE"
  • DEBUG Debug to "JTAG (5-pins)" - to match the device power on state

then I get a yellow exclamation warning on RCC and CRS SYNC is highlighted with the warning "CRS SYNC conflict with DEBUG Debug JTAG (5 pins) or/and USB Should be enabled".

Can I ignore this warning? I would have thought in this configuration, with CRS SYNC being sourced from LSE that I do not need the CRS SYNC pin which is shared with JTDO and no warning should be issued. Even with CRS SYNC disabled (although I do not see how that is achieved from the reference manual) the warning is still shown.

Or does STM32CubeMX just bundle up all the possible warnings, errors and remedies and display them, even if you have settings that would not cause the conflict? I can see in the CRS SYNC drop down that using the GPIO is invalid, but I've also tried enabling USB FS and HS and the warning message about enabling USB still persists.

Thanks.

This topic has been closed for replies.
Terms & ConditionsAccessibility statement