[BUG] "One or more timer conflict detected" when trying to compile using mks_robin_nano35_stm32

[th0m4sek]

Bug Description

`Marlin/src/HAL/STM32/timers.cpp:281:41: error: static assertion failed: One or more timer conflict detected
  281 | static_assert(verify_no_duplicate_timers(), "One or more timer conflict detected");
      |               ~~~~~~~~~~~~~~~~~~~~~~~~~~^~`

same configuration working fine when compiling with mks_robin_nano35
using tmc2209 with uarts connected to one pin.

Configuration Files

Marlinconf.zip

Steps to Reproduce

compile attached files

Expected behavior:

posibility to compile with mks_robin_nano35

Actual behavior:

[th0m4sek]

Solution from #19905

#if defined(ARDUINO_ARCH_STM32) && !defined(STM32GENERIC)
  // Variant default conflicts with Servo timer
  #define TEMP_TIMER 5
#endif

worked for my MKS Robin Nano V1.2
Maybe this should be merged?

[rhapsodyv]

@sjasonsmith we can merge it? or it's just a temporary hack?

[sjasonsmith]

I would like to try to find a more flexible way to solve it. As more boards move to the STM32 HAL this will continue to be a problem, and it would be nice to not have to manually define the timer for each board. Not every board should use the same timers for this, due to other conflicts.

[sjasonsmith]

I've updated the provided configs to reproduce the problem using the current state of bugfix-2.0.x.
I tried to preserve all the original settings, but no promises. My goal is just to reproduce the compilation issue.
Configuration.zip

[th0m4sek]

updated conf on current bugfix is acting as before - can be compiled with mks_robin_nano but not with mks_robin_nano_stm32

[sjasonsmith]

Sorry, I wasn't suggesting that I've fixed it, I just updated them to provide failing configs that work with the current bugfix.

I think I have a more flexible solution semi-ready, but I haven't yet tried it with any hardware. I'm about to post it as a Draft pull request to see if it passes our build tests, and to solicit feedback.

[th0m4sek]

i was not sure what you wanted to communicate but i wanted to show that i'm ready to help at least with testing ;)

[sjasonsmith]

@th0m4sek I appreciate the willingness to help. I just posted that draft. I'll tag you again when it is ready for you to try out. I'd like to test it with some of my own hardware first.

[sjasonsmith]

This conflict should now be resolved, along with several other boards with similar issues.
I'm closing this, but please let us know if you continue to see issues with the latest changes from bugfix-2.0.x.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.