Add support for rp2350 micro-controllers

[KevinOConnor]

This adds support for the new Raspberry Pi RP2350 micro-controllers. This has also been discussed at: https://klipper.discourse.group/t/support-for-rp2350-micro-controllers/19656

Note that the rp2350 has a serious hardware defect (RP2350-E9 errata) and as a result I do not recommend using this chip currently. See the link above for more details.

The code on this PR has a few known limitations (to be addressed in future PRs):

• Only the first 30 GPIOs are supported. Support for the additional GPIOs on the rp2350b has not been added (nor support for ADC in general on the rp2350b).

-Kevin

EDIT: The chipid and reboot into bootloader functionality has also been implemented in this PR.

[thijstriemstra]

In the thread you mention: " Implemented. Regular make flash should now work." Does this also apply to rp2040 or only rp2350?

[KevinOConnor]

The rp2040 already supports make flash. The changes here extend that logic to include rp2350 chips. The rp2040 support is otherwise unchanged.

-Kevin

[github-actions[bot]]

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.