MSP432 Launchpad at US$4.32...

[Fred27]

Energia takes everything that is awful about Arduino and applies it to the MSP430, etc. I suggest you don't use it if you have any self respect or if you have any interest in useful features like JTAG debugging, breakpoints or EnergyTrace power profiling.

Of course that's just my opinion. Try Energia and CCS then make up your own mind.

[suicidaleggroll]

It looks like the chips are now in production.  No stock yet at distributors, but they now have listings for them and show the status as "on order", and you can buy the chips and get samples from TI (currently in stock).  It also looks like TI has now released msp432-gcc to go along with their msp430-gcc open source compiler, which makes me very happy.

[dannyf]

last time I checked, TI had yet to implement the "#pragma vector" directive for t he MSP432 family of chips.

As such, you will have to manually edit the start-up file to insert your ISRs.

I would not do any work on the chip until that has been resolved.

[suicidaleggroll]

The msp432-gcc examples have all of the ISRs pre-set in the startup file, all you have to do is write the ISR in your program and enable it in NVIC.

http://www.ti.com/lit/zip/slac698

[Macbeth]

last time I checked, TI had yet to implement the "#pragma vector" directive for t he MSP432 family of chips.

As such, you will have to manually edit the start-up file to insert your ISRs.

I would not do any work on the chip until that has been resolved.

OMG! I have a couple of these MSP432's, but it sounds like you have found a major show stopper! Good on you, I wish moar people would come out and shame TI because of major shit like this. 

[dannyf]

The sad thing is that the weak attribute is actually supported by ti arm compiler, itself a derivative of GCC.

You can pretty much implement your own programmable isr by declaring the as weak in the start up file and the code compiles just fine.

Why ti decided to release a half ass compiler, and didn't provide a quick update, as shown in the porting guide, is beyond me.

[rsjsouza]

But there is a simple solution provided by TI in this case so it isn't a big deal.

Yes, just edit the startup_msp432p401r_gcc.c file and you are good.

[andyturk]

last time I checked, TI had yet to implement the "#pragma vector" directive for t he MSP432 family of chips.

As such, you will have to manually edit the start-up file to insert your ISRs.

I would not do any work on the chip until that has been resolved.

MSP432 is a Cortex-M core and you can write ISRs and set up your vector table in straight C.

[rsjsouza]

last time I checked, TI had yet to implement the "#pragma vector" directive for t he MSP432 family of chips.

As such, you will have to manually edit the start-up file to insert your ISRs.

I would not do any work on the chip until that has been resolved.

Get on with times and get your devices straight.

- MSP432 uses the ARM GCC compiler from https://launchpad.net/gcc-arm-embedded
- MSP430 uses a GCC porting that started to support the pragma in 2012, as mentioned below:
http://stackoverflow.com/questions/15500826/how-to-declare-an-interrupt-handler-isr-in-mspgcc

[Cervisia]

Please note that "mspgcc" is a now-outdated fork of gcc; the last release was in 2012.

MSP430 support was also added to the 'real' gcc.
The "msp430-gcc" package on TI's website is just the official gcc, configured to cross-compile with the MSP430 as target.

"#pragma vector" was supported by mspgcc, but is not available in gcc.
(There's nothing that TI can do about this, except creating their own fork of gcc. But that would not make sense because they already make their own compiler.)

All of TI's current MSP430 example code uses the correct compiler-specific #ifdeffery when declaring interrupt vectors.

(And none of this applies to the MSP432; as already mentioned, it's just an ARM.)

[dannyf]

"And none of this applies to the MSP432"

That's the saddest part: a big selling point for 432 is its peripheral comparability with 430.

So it is a little bit too much to require manual editing of start up files when porting one one to another.

[suicidaleggroll]

I could have sworn I already said above that you don't have to edit the startup file...

I just wrote a simple msp432 program for testing last night that used the timer interrupt for a programmable delay.  The result looks almost identical to the MSP430.  The register setup looks basically the same, the ISR looks only slightly different, and it has an extra NVIC call, that's about it.  No editing of the startup file, no "#pragma vector" syntax in either one.

Maybe you had to edit the startup file previously, but it was still pre-release silicon with pre-release software support.  If you don't want to deal with pre-release "problems" then wait until the device has moved to active production.

[dannyf]

Updated my compiler to 15.12 LTS and the interrupts worked beautifully - as I had used the same vector names so my code compiled and ran as expected.

I'm a happy camper.

BTW: TI should have updated the porting guide.