Difference between revisions of "IAR Workbench"
m (→Use of printf() and scanf()) |
m |
||
| Line 2: | Line 2: | ||
The runtime library uses a set of low-level functions—which are referred to as the 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 | low-level I/O interface—to communicate with the target system. Most of the low-level | ||
| − | functions have no implementation. | + | functions have no implementation. See IAR manual '''C/C++ Compiler User Guide''' |
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()''' | 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()''' | ||
Latest revision as of 07:27, 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. See IAR manual C/C++ Compiler User Guide
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()