MSP430 IAR C/C++ Compiler reference guide - Rice University

The CLIB runtime environmentbreakpoints on certain assembler labels in the application. When code located at thespecial labels is about to be executed, C-SPY will be notified and can perform an action.THE DEBUGGER TERMINAL I/O WINDOWWhen code at the labels ?C_PUTCHAR and ?C_GETCHAR is executed, data will be sent toor read from the debugger window.For the ?C_PUTCHAR routine, one character is taken from the output stream and written.If everything goes well, the character itself is returned, otherwise -1 is returned.When the label ?C_GETCHAR is reached, C-SPY returns the next character in the inputfield. If no input is given, C-SPY waits until the user has typed some input and pressedthe Return key.To make the Terminal I/O window available, the application must be linked with theXLINK option With I/O emulation modules selected. See the MSP430 IAR EmbeddedWorkbench® IDE User Guide.TERMINATIONThe debugger stops executing when it reaches the special label ?C_EXIT.Checking module consistencyFor information about how to check module consistency, see Checking moduleconsistency, page 71.Part 1. Using the compiler81