DAC161S997EVM

Hi David!

I had a look into the schematics - unfortunately the EVM uses 4-wire JTAG instead of 2-wire SBW for communication with the MSP430G2553. This can cause problems because the JTAG pins are shared with other functions on this board. When I look at your source code, I can see that you configure P1.4 which is also a JTAG signal. This could cause erroneous behaviour.

Could you try the following:

#include "msp430g2553.h"
#incldue <stdint.h>

void delay( uint32_t delay );

void main( void )
{
  WDTCTL = (WDTPW | WDTHOLD);

  P1DIR |= 0x08;

  while( 1 )
  {
    P1OUT ^= 0x08;
    delay( 250000 );
  }
}

void delay( uint32_t delay )
{
  volatile uint32_t counter;

  for( counter = 0; counter < delay; counter++ );
}

Does this cause D3 to blink?

It would be more useful to use SBW for communication here. If you can do a small hack to the connections, do the following (connector J2 on the EVM):

• Connect pin 4 of the EVM to pin 4 of the FET
• Connect pin 9 of the EVM to pin 9 of the FET
• Connect pin 11 of the EVM to pin 1 of the FET
• Connect pin 8 of the EVM to pin 7 of the FET

The board must be powered externally by connecting the loop terminals. Then you can use all pins of the MSP430 while debugging your application, otherwise the communication to the DAC161S997 is disturbed as well.

Dennis