Hi I am having trouble programming the MSP430G2553 ucontroller on the DAC161S997EVM board. I started to write some code to toggle the LEDs and setup ADC on the uC. I programmed the EVM via the JTAG using a MSP-FET430UIF tool. My project was running along smoothly as gradually started to build up the code, adding feature by feature. I reached a point yesterday where I was ready to start testing the DAC on the EVM. This is programmed via the uC over the SPI comms. I added the code below to setup the SPI comms on the MSP430G2553 on the DACEVM. void SPI_Initialise(void) { P2OUT |= BIT0; P1SEL = BIT5 | BIT6 | BIT7; P1SEL2 = BIT5 | BIT6 | BIT7; UCB0CTL1 = UCSWRST; UCB0CTL0 |= UCCKPH + UCMSB + UCMST + UCSYNC; // 3-pin, 8-bit SPI master UCB0CTL1 |= UCSSEL_2; // SMCLK UCB0BR0 |= 0x02; // /2 UCB0BR1 = 0; // UCB0CTL1 = ~UCSWRST; // **Initialize USCI state machine** } After adding this I downloaded and debugged the code to the uC on the EVM. I am now unable to write any new code to the uC. Everytime I attempt to download the code (IAR) I get the fllowing error Wed Jun 15, 2016 09:32:08: Security Fuse has been blown : (OpenDevice) , Device=MSP430G2xx3, PwLength=0x0 Wed Jun 15, 2016 09:32:09: Fatal error: Could not find device (or device not supported) Session aborted! Now I am fairly new to MSP430's and this is the first time I have used this DAC161S997EVM , but would I be correct in assuming this issue is to do with the fact that the SPI comms lines are shared with the JTAG pins? This makes sense as the code loaded first time (after the addition of the SPI setup) but hasn't been able to communicate since. Are there any other reasons why the security fuse would blow? I was reading that it is usually to do with a timeout issue, which again points to the shared JTAG/SPI lines. I am new to this so please be kind, but I can't understand why the JTAG lines would be shared with SPI lines needed to communicate with the on board DAC? If that is the reason ofc for my issues Any help would be appreciated Dave
↧