Frequently Asked Questions
9)It is possible to mix assembler and C programs within the Workbench. Refer to the Assembler Language Interface chapter of the C/C++ Compiler Reference Guide from IAR.
10)The Workbench can produce an object file in Texas Instruments .TXT format.
.TXT format.
11)The example programs giving in the Kickstart documentation (i.e., Demo, Tutor, etc.) are not correct. The programs will work only in the simulator. However, the programs will not function correctly on an actual device because the Watchdog mechanism is active. The programs need to be modified to disable the Watchdog mechanism. Disable the Watchdog mechanism with the
12)Access to MPY using an
13)Constant definitions (#define) used within the .h files are effectively “reserved”, and include, for example, C, Z, N, and V. Do not create program variables with these names.
14)The CSTARTUP that is implicitly linked with all C applications does not disable the Watchdog timer. Use WDT = WDTPW + WDTHOLD; to explicitly disable the Watchdog. This statement is best placed in the __low_level_init() function that gets executed before main().
If the Watchdog timer is not disabled and the Watchdog triggers and resets the device during CSTARTUP, the source screen will go blank as
int __low_level_init(void)
{
/* Insert your
WDTCTL = WDTPW + WDTHOLD; // Stop Watchdog timer
/*==================================*/
/* Choose | if | segment | initialization */ | |||
/* should | be | done or | not. | */ | ||
/* | Return: 0 | to | omit | seg_init | */ | |
/* |
| 1 | to | run seg_init | */ |
/*==================================*/ return (1);
}
15)Compiler optimization can remove unused variables and/or statements that have no effect, and can effect debugging.