• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 78 subscribers
  • Views 1261 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

warning #10374-D: Interrupt vector "NMI" does not have an interrupt handler routine.

vinayak13
Intellectual 625 points
Other Parts Discussed in Thread: MSP430G2553

Hi,

I have simple UART code.

8468.Lab4.c
Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
/*
* main.c
*/
#include "msp430g2553.h"
void main(void)
{
WDTCTL = WDTPW + WDTHOLD; // Stop WDT
BCSCTL1 = CALBC1_1MHZ; // Set DCO
DCOCTL = CALDCO_1MHZ;
P1SEL = BIT1 + BIT2 ; // P1.1 = RXD, P1.2=TXD
P1SEL2 = BIT1 + BIT2 ; // P1.1 = RXD, P1.2=TXD
UCA0CTL1 |= UCSSEL_2; // SMCLK
UCA0BR0 = 104; // 1MHz 9600
UCA0BR1 = 0; // 1MHz 9600
UCA0MCTL = UCBRS0; // Modulation UCBRSx = 1
UCA0CTL1 &= ~UCSWRST; // **Initialize USCI state machine**
IE2 |= UCA0RXIE; // Enable USCI_A0 RX interrupt
__bis_SR_register(LPM0_bits + GIE); // Enter LPM0, interrupts enabled
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

After compiling I get binary file. But I get following warnigns. Kindly help me to remove these warnings

"../lnk_msp430g2553.cmd", line 79: warning #10374-D: Interrupt vector "PORT1"
   does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 80: warning #10374-D: Interrupt vector "PORT2"
   does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 82: warning #10374-D: Interrupt vector "ADC10"
   does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 83: warning #10374-D: Interrupt vector
   "USCIAB0TX" does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 85: warning #10374-D: Interrupt vector
   "TIMER0_A1" does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 86: warning #10374-D: Interrupt vector
   "TIMER0_A0" does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 87: warning #10374-D: Interrupt vector "WDT"
   does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 88: warning #10374-D: Interrupt vector
   "COMPARATORA" does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 89: warning #10374-D: Interrupt vector
   "TIMER1_A1" does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 90: warning #10374-D: Interrupt vector
   "TIMER1_A0" does not have an interrupt handler routine.
"../lnk_msp430g2553.cmd", line 91: warning #10374-D: Interrupt vector "NMI"
   does not have an interrupt handler routine.
'Finished building target: UART.out'

Regards,

VInayak

  • 0
    Guru 58965 points

    I think the compiler is overreaching.

    I think it is not smart enough to check whether you enabled the possible interrupts or not, and  blindly warn you that you do not have all the interrupt vectors assuming that you had enabled all of them.

    If you so wish, you can add all those useless interrupt vectors to keep the compiler quiet. This does no harm, but is not useful either.

  • 0 in reply to old_cow_yellow
    Guru 58965 points

    Actually, it was the linker, not the compiler. My mistake.

  • 0 in reply to old_cow_yellow
    Guru 16361 points

    What toolchain are you using?

    Version 4.3 of TI's compiler - as found in CCSv6 - supports the following construction:

    #pragma vector=unused_interrupts
interrupt void user_trap_function(void)
{
    // code for handling all interrupts that do not have specific ISRs
}

    (quoted from the MSP430 Optimizing C/C++ Compiler v4.3 User's Guide)

    By default it uses a trap ISR implemented in the RTS library (isr_trap.asm). This implementation just contains an infinite loop that forces the CPU into LPM0 on each iteration.

    I replace this trap ISR with one that also uses _op_code(0x4343), which is roughly equivalent to "__asm { INT 3 }" (from x86 architecture). This addition means that triggering any undefined interrupts causes the debugger to break, as long as software breakpoints are enabled.

  • 0
    Guru 23000 points

    This happens when you change something to your project, don’t ask me what but I know this happens sometimes. The warnings are not critical and can be ignored or you make some changes to your linker command file “lnk_msp430g2553.cmd” found near the bottom in the project explorer. Under Sections comment-out (//… or /* … */) all the references to unused vectors.

**Attention** This is a public forum