I think you are just in time. I had the intention to remove all the non-ARM stuff bit by bit during a couple of next upcoming releases.
The new 2.0 is also going more and more in the direction of an ARM only-tool because of the tight coupling with EBlink.
The question is, is it worth to keep the non-ARM mcu's or should we keep that as a 1.11 version feature?
I don't have a clue how many users there are, I didn't used MSP430 for more than a decade to be honest. The reason why it is there is because somewhere in 2010/2011 I had one small project with MSP430.
BTW
Attached compiler plugin with MSP430 (I had the sources still in git).
But the questions remains, how long do we need to support this (and other non-ARM) mcu.
The new 2.0 is also going more and more in the direction of an ARM only-tool because of the tight coupling with EBlink.
The question is, is it worth to keep the non-ARM mcu's or should we keep that as a 1.11 version feature?
I don't have a clue how many users there are, I didn't used MSP430 for more than a decade to be honest. The reason why it is there is because somewhere in 2010/2011 I had one small project with MSP430.
BTW
Attached compiler plugin with MSP430 (I had the sources still in git).
But the questions remains, how long do we need to support this (and other non-ARM) mcu.