Difference between revisions of "IAR Workbench"
m (→I=AR DLIB=) |
m (→Use of printf() and scanf()) |
||
| Line 10: | Line 10: | ||
===Use of printf() and scanf()=== | ===Use of printf() and scanf()=== | ||
| − | *[[MSP430F5529/UART console]] - Simple implementation of low-level functions | + | In order to use '''printf()''' and '''scanf()''' the low level functions '''__read()''' and '''__write()''' must be implemented in the project enabling writing and reading to STDOUT/STDERR and STDIN. |
| + | *[[MSP430F5529/UART console]] - Simple implementation of low-level functions '''__read()''' and '''__write()''' | ||
[[Category:MSP430]] | [[Category:MSP430]] | ||
Revision as of 07:24, 8 December 2022
IAR DLIB
The runtime library uses a set of low-level functions—which are referred to as the DLIB low-level I/O interface—to communicate with the target system. Most of the low-level functions have no implementation.
To use some of the DLIB high-level functions, the project must implement some of the low-level functions. For example __read() and __write() in order to use for example printf() and scanf()
IAR has skeleton implementations examples in the IAR Workbench installation files. ON my PC they are in: C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.5\430\src\lib\dlib
Use of printf() and scanf()
In order to use printf() and scanf() the low level functions __read() and __write() must be implemented in the project enabling writing and reading to STDOUT/STDERR and STDIN.
- MSP430F5529/UART console - Simple implementation of low-level functions __read() and __write()