I have been working with ala42's STM32F4 library
I have also been working with ST Micro's libraries and examples. It is not possible to mix ala42's interrupt vector names with the ST's libraries, and vice versa.
I have changed all of the interrupt vector names in ala42's code so that they all match the ones ST Micro use in their libraries and projects.
This allows me to successfully compile, link and run ST Micro's own STM32F4 peripheral library, and some of their projects. For example I have their IO_toggle and MEMS 3D-accelerometer demo working on my STM32F4Discovery.
The interrupt names are straightforward to find from the ST Micro's STM32F4 documentation without looking at the source code. The names follow a simple rule.
This is such a pervasive change to ala42's code that I feel I should ask for feedback. I am especially asking ala42.
I also thought folks working with ala42's library may have written their own code which uses the existing vector-names in ala42's library.
So I have written an 'ed' script which will edit source code, and change the interrupt vector names 'automatically'.
Folks can apply this technique to their source. That would bring us to a set of sources which share the same interrupt vector names. That would allow us to mix and merge our source code, which I feel is very important.
Will my 'ed' script be adequate for anyone working on the source who has a lot of code which uses those interrupt names? Specifically, is there anyone working on the source, who would need to change a lot of interrupt vector names, who don't have 'ed' (i.e. more than 10 minutes of hand editing and testing)?
I think there is huge advantages in using the same vector names as ST. We get all of their projects to run on STM32F4-based boards and can use their projects to test boards and electronics. Their code may be ugly, but I'll take ugly and mostly-works over most alternatives :-)
My goal is to ensure we can use an STM32F4 libmaple-style/wiring-style library at the same time, in the same program (sketch) as ST's code.
The same technology (ed) I use to change ala42's interrupt-vector names can be used to change them to something else, so I don't think there is much of a problem.
What objections are there to me pushing all of my vector-name changes, into the ala42-based openstm32sw/stm32f4 github repo?
I will also push my ed-script too so folks can bring their source in-line.
I will wait until Friday before pushing to give folks time to think and respond.