CCS/MSP432P401R: Handling UART IV on MSP432 as on MSP430

Nathan Vander Wilt

Part Number: MSP432P401R

Tool/software: Code Composer Studio

I'm porting some code from the MSP430 to the MSP432 and having trouble with tons of constants being missing. What would be the idiomatic way to port the following code for the MSP432?

switch(__even_in_range(UCA0IV, USCI_UART_UCTXCPTIFG)) {
    case USCI_NONE:
        break;
    case USCI_UART_UCRXIFG:
        // … handle RX …
        break;
    case USCI_UART_UCTXIFG:
        // … handle TX …
        break;
    case USCI_UART_UCSTTIFG:
        break;
 // …etc.

It seems that only the constants for IFG flags are available, e.g. EUSCI_A_IFG_TXIFG which expands to 0x2 rather than the 0x4 obtained via USCI_UART_UCTXIFG.

Was I using the wrong headers/constants to begin with in MSP430? Or did use of the IV get deprecated? Why did those constants go away and what should I use in their stead?

over 4 years ago

0 Bruce McKenney47378 over 4 years ago

Guru 90830 points

There used to be a header file "msp432p401r_classic.h" which provided the MSP430-ish names. It's still there in CCS v8.3, but I don't have v9 or v10.

The general move (Examples and such) has been to ARM's CMSIS convention. In that, you would reference something like USCI_A0->IV;

0 Nathan Vander Wilt over 4 years ago in reply to Bruce McKenney47378

Intellectual 340 points

Thanks, yeah we noticed the _classic header but are more interested in updating things. Ideally if there is a way intended for usage across both MSP platforms, but not eager to embrace anything deprecated to do so.

With the USCI_A0->IV convention, what constants should I compare the values to? Is the practice now just to hardcode numbers like "case 0x4:"? That doesn't seem like a very good style especially when TI used to provide constants like USCI_UART_UCTXIFG instead.

Can anyone provide an example of my original code ported in "best practice" style? It's still bothering me that, if the IV register is still intended to be used, why there are no longer corresponding constants provided [except in "classic" which sounds like something to be avoided in new code].

0 Bruce McKenney47378 over 4 years ago in reply to Nathan Vander Wilt

Guru 90830 points

Hm. I don't see names for the IV values defined in msp432p401r.h. But I also don't see your symbols defined in msp430xxx.h either (sample size 2). I do see (for the MSP430) symbols of the form UCIV__UCTXIFG.

In the MSP430 code, where do you go if you right-click on one of those names and "Go To Definition"?

[Edit: Curious -- I don't see these symbols in fr5994.h nor fr2311.h, but I do see them in fr2433.h. I'm sure there's a good reason, but I don't know it.]

0 Nathan Vander Wilt over 4 years ago in reply to Bruce McKenney47378

Intellectual 340 points

Yeah, in my code I simply `#include <msp430.h>`. On the old dev board, the symbol ends up resolving within the file ccs_base/msp430/include/msp430fr6989.h

I wonder if the inconsistencies are just ongoing shift's in TI's strategy and recommendations? I had been using the <msp430.h> header but also aware of a presumedly newer <msp.h> one. And now also read today (in the SimpleLink migration guide) that:

> Even if you are not currently using MSP432Ware and/or TI-provided libraries, note that, device header files will not be deployed via the IDE in the future. Hence installing and using the SDK is crucial to keep your software projects updated and using the correct version of the device header files.

[emphasis mine]

0 Gary Gao over 4 years ago in reply to Nathan Vander Wilt

TI__Mastermind 35155 points

Please refer to the application note that migrating from MSP430 to MSP432 devices

https://www.ti.com/lit/an/slaa656d/slaa656d.pdf?ts=1597673163158&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FMSP432P4011%253FkeyMatch%253DMSP432P401%2526tisearch%253DSearch-EN-everything%2526usecase%253DGPN

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

CCS/MSP432P401R: Handling UART IV on MSP432 as on MSP430