MSP430F149: Disassembler keeps getting suck in the an infinite loop

Hello Beau,

I suspect that the problem is that if there is too much data getting initialized, this startup code can take too long to run and the WDT times out before you ever reach main to be able to disable it.

See this FAQ entry as well: http://processors.wiki.ti.com/index.php/MSP430_FAQ#WDT_fires_during_C_startup_code

You should be able to solve this issue by either declaring some variables or arrays as __no_init, or by customizing the __low_level_init() function to stop the watchdog timer. __low_level_init() is called before the variables are initialized so it will solve the problem even if you do have a large amount of data that needs to get initialized in the cstartup code. You can find more info on __low_level_init() in the IAR compiler guide as well.

Run time Issue with MSP430FR6989 while trying to run / debug source code

Regards,

James

Hey James,

I did try that with the following code segment:

int __low_level_init(void)
{
HOLD_WATCHDOG(); //used to prevent debug timeout
return (1);
}

Unfortunately the problem seems to continue.

Additionally, I have been seeing that when enough time passes, the code will eventually reach to the beginning of the main function ( I set a break point at the beginning of the code). When I hit continue, the program will run and then lose connection with the following error:

Communication Error.
Check if hardware is connected.
Check if debug protocol (SBW or 4-wire) is connected