Add cr10 smart cr fdm config

[RENOPS]

Description

This adds a configuration file for the Creality CR-10 Smart with CR-FDM-v2.5.S1 -100 mainboard variant.

Why this configuration is needed

The existing CR-10 Smart examples in the config directory (printer-creality-cr10-smart-*.cfg) do not work with this specific CR-FDM-v2.5.S1 mainboard variant. This configuration is based on reverse-engineered pin analysis and confirmed working setup.

Hardware Details

• Main board: STM32F103RET6 microcontroller
• Secondary strain gauge board: STM32F030F4P6 + NX711 load cell ADC
• Connections: 2x7 pin (14-pin) and 2x8 pin (16-pin) headers to main board
• Configuration: Uses physical Z endstop instead of strain gauge probe for reliability

Pin Mappings Verified

• Steppers: PA4/PA5 (X), PC6/PC7 (Y), PC0/PC1 (Z), PA1/PA0 (E)
• Endstops: PC4 (X), PC5 (Y), PB2 (Z-physical)
• Heaters: PB13 (Bed), PB14 (Hotend)
• Thermistors: PB0 (Bed), PB1 (Hotend)
• Fans/Outputs: PB15 (Part fan), PC13 (Lights), PA0 (Power)
• Sensors: PA7 (Filament sensor)

Testing

This configuration has been tested and confirmed working with the CR-10 Smart CR-FDM v2.5.S1 hardware.

[github-actions]

Thank you for your contribution to Klipper. Unfortunately, a reviewer has not assigned themselves to this GitHub Pull Request. All Pull Requests are reviewed before merging, and a reviewer will need to volunteer. Further information is available at: https://www.klipper3d.org/CONTRIBUTING.html

There are some steps that you can take now:

1. Perform a self-review of your Pull Request by following the steps at: https://www.klipper3d.org/CONTRIBUTING.html#what-to-expect-in-a-review
   If you have completed a self-review, be sure to state the results of that self-review explicitly in the Pull Request comments. A reviewer is more likely to participate if the bulk of a review has already been completed.
2. Consider opening a topic on the Klipper Discourse server to discuss this work. The Discourse server is a good place to discuss development ideas and to engage users interested in testing. Reviewers are more likely to prioritize Pull Requests with an active community of users.
3. Consider helping out reviewers by reviewing other Klipper Pull Requests. Taking the time to perform a careful and detailed review of others work is appreciated. Regular contributors are more likely to prioritize the contributions of other regular contributors.

Unfortunately, if a reviewer does not assign themselves to this GitHub Pull Request then it will be automatically closed. If this happens, then it is a good idea to move further discussion to the Klipper Discourse server. Reviewers can reach out on that forum to let you know if they are interested and when they are available.

Best regards,
~ Your friendly GitIssueBot

PS: I'm just an automated script, not a human being.