• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 80 subscribers
  • Views 510 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

NMI example for Rev 1.4 board.

Paul Maxwell
Prodigy 70 points

Hello all,

I cannot get the NMI example code to work properly. It will not except A RST line going low as an interrupt. It never goes to the ISR. I'm wondering if it is the Rev 1.4 board. Just curious, because this is a new board, TI has not even put the Rev 1.4 schematic in their web page yet.

Can anyone give me some suggestion on how to go about debugging this. I used the program named msp430g2xx1_nmi.c example program.

Thanks,

Paul

  • 0
    Prodigy 70 points

    Hello All,

    Update!

    Programming the chip works. I disconnected the USB from the Launchpad board, then reconnected it. The NMI (RST) (S1) now works. It's just that it wont breakpoint in the ISR (interuprt vector). I can breakpoint in the main routine.

    Paul

  • 0 in reply to Paul Maxwell
    Expert 2840 points

    Interrupt Vector is an address that is read when interrupt happens. MCU does not execute this location (at least in regular conditions) but read the address and jumps to the address. This is wht the breakpont in this location does not catch and hold your microcontroller.

    When you forgot about setting vector for enabled interrupt you can expect redirection to 0xFFFE and execution the values fetched from this location. It this unusual circumstances the vector is executed and breakpoint will work. Please remember that this is a result of error - missing interrupt vector.

    Regards,
    Piotr Romaniuk, Ph.D.
    ELESOFTROM

  • 0 in reply to Paul Maxwell
    Guru 17650 points

    Hi Paul,

    you're using Spy-Bi-Wire debugging on your LaunchPad, right? So, one of the Spy-Bi-Wire signal is RESET --> you can't debug the NMI when your debugger (Emulator part of the LaunchPad) has control over the Reset signal!

    Use the debugger option "Release JTAG On Go" that can be selected from the IDE drop-down menu. This prevents the debugger from accessing the MSP430 while the application is running. Note that in this mode, a manual halt is required to see if a breakpoint was hit.

    Rgds
    aBUGSworstnightmare

**Attention** This is a public forum