Please keep updating the STM32_open_pin_data repo with new families (as of now, STM32C5xx)

[waclawek.jan]

I've noticed, that the new STM32C5xx family is not present in the STM32_open_pin_data repo.

I know why (MX2 vs MX), but ST, please, keep updating this repo with the new families' data. It's a valuable database for third party tools used to allocate pins in various STM32 designs.

Thanks,

JW

[christophe_M]

The STM32_open_pin_data repo is only a subset of MX1. We retrieve inside only STM32 families supported in MX1.

For MX2 we have a datacentric approach and information related to peripherals, pinout, clock are available directly in the C5xx Dfp pack in some json files.

[waclawek.jan]

Yes, that's the status quo. 

And my request is, please include to the STM32 open pin repo also the families which are otherwise not supported in MX1.

As an alternative, please provide xml files with the same format as the others, for those not supported families, as a separate repo.

The reason for this request is, that since it's provided as a separate repo, it's not only MX1 which uses it, but also third party solutions (and also there are people who manually retrieve and review the xml files).

Thanks,

JW

[christophe_M · Accepted solution]

As explained it is not planned to add xml files into STM32 open pin repo for series not supported in MX1.

The same info are now in the json files of packs delivered and compatible with MX2. 

The dfp C5xx is delivered publicly in this repo :

https://github.com/STMicroelectronics/stm32c5xx-dfp/tree/main/Descriptors 

All packs for C5 are available here : https://github.com/STMicroelectronics/STM32Cube_MCU_Overall_Offer/blob/master/STM32Cube_STM32C5.md 

Third party solutions should use now json files instead of xml for new series like C5.

CMO

[waclawek.jan]

That's a pity, then.

It questions ST's ability to commit to any scheme providing this sort of information in long term.

In other words, it's not that unlikely the jsons will be dropped for whatever else will be in fashion within a couple of years, when MX3 will come.

> Third party solutions should use now json files instead of xml for new series like C5.

AFAIK, ST has no plans to migrate existing series to the "new" format, either.

JW

[waclawek.jan]

Thanks for the links, though.

A json-to-xml converter appears to be a simple affair.

JW