OpenOCD package update and STM32 ecosystem

1

since more than 3 years the openocd does’t get any updates, but the readme say its the xPack version of openocd. the xPack version has get some updates in the last three years which also fix some issues with the ststm32 platform see GitHub-PR887. I think it’s cumbersome that every user should manually update the binaries.

I’ve start a discussion with the maintainer of the xPack package, but we both need some advice which way we should go.

I understand that a package from platformio team looks better, but why this effort? Why not help the maintainer to do this job?
I hope that somebody of the core team will help me with the outdated packages. It would be nice if the source for every package were in the GitHub-Orga visible (easy findable). Because tool-ldscripts-ststm32 is outdated too.

And another point is the STM32 platform as a whole: there is a lot of stuff available from ST itself, for which all that would be required is a ‘package.json’ file and a workflow for publication. Has anyone asked ST to do this?

2

The current OpenOCD package used in the ststm32 platform and others is published by PlatformIO staff. Sure, a user can submit the latest OpenOCD packages to the PlatformIO registry, but if the platforms don’t use it, they’re not good. I would expect the PlatformIO staff to regularly keep up with new package versions and PRs for new board support which in turn needs new package versions. I agree that 3 year old OpenOCD is not the best look.

The last time it was done it was via https://github.com/platformio/platform-ststm32/issues/683.

I’ve opened https://github.com/platformio/platform-ststm32/issues/906 in regards to this.