stm32c5: initial commit adding stm32c5 support to stm32h5 driver. #2242

emeb commented 2026年04月29日 00:18:26 +02:00

This PR adds support for the STM32C53x/54x/55x/56x/59x/5Ax series devices to the STM32H5 driver.

Your checklist for this pull request

• I've read the Code of Conduct
• I've read the guidelines for contributing to this repository
• It builds for hardware native (see Building the firmware)
• It builds as BMDA (see Building the BMDA)
• I've tested it to the best of my ability
• My commit messages provide a useful short description of what the commits do

Closing issues

<!-- Filling this template is mandatory --> ## This PR adds support for the STM32C53x/54x/55x/56x/59x/5Ax series devices to the STM32H5 driver. <!-- * The only new feature is a new stm32c5_probe() function which builds the appropriate RAM and Flash maps for the newly supported devices, as well as ID and revision reporting. --> ## Your checklist for this pull request * [x] I've read the [Code of Conduct](https://codeberg.org/blackmagic-debug/blackmagic/src/CODE_OF_CONDUCT.md) * [x] I've read the [guidelines for contributing](https://codeberg.org/blackmagic-debug/blackmagic/src/CONTRIBUTING.md) to this repository * [x] It builds for hardware native (see [Building the firmware](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-the-firmware)) * [x] It builds as BMDA (see [Building the BMDA](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-black-magic-debug-app)) * [x] I've tested it to the best of my ability * [x] My commit messages provide a useful short description of what the commits do ## Closing issues <!-- put "fixes #XXXX" here to auto-close the issue(s) that your PR fixes (if any). -->

emeb commented 2026年04月29日 00:22:29 +02:00

Whoops - I guess I kinda mangled the markdown for this PR. Details are that I just add a new stm32c5_probe() function which builds the proper RAM and Flash maps as per the memory layout info in RM0522 section 2.2.2. The flash controller in the C5 family appears to be sufficiently similar to that in the H5 devices that I didn't need to make any changes to the rest of the driver. I've tested this on the only C542 device that I have and it is able to load code correctly. Other C5xx devices should work but haven't been tested yet.

Whoops - I guess I kinda mangled the markdown for this PR. Details are that I just add a new stm32c5_probe() function which builds the proper RAM and Flash maps as per the memory layout info in RM0522 section 2.2.2. The flash controller in the C5 family appears to be sufficiently similar to that in the H5 devices that I didn't need to make any changes to the rest of the driver. I've tested this on the only C542 device that I have and it is able to load code correctly. Other C5xx devices *should* work but haven't been tested yet.

emeb commented 2026年04月29日 00:39:17 +02:00

Thanks for the review. I'll fix those issues (was wondering about the capitalization & int8_t vs bool stuff).

Thanks for the review. I'll fix those issues (was wondering about the capitalization & int8_t vs bool stuff).

emeb commented 2026年04月29日 00:47:44 +02:00

All three issues have been corrected. Code has been tested on the bench and now reports proper STM32C5 name during connection.

All three issues have been corrected. Code has been tested on the bench and now reports proper STM32C5 name during connection.