Skip to main content

IAR Embedded Workbench for Arm 9.70.x

Terminal I/O window

In this section:

What do you want to do?

YellowStripe.png

The Terminal I/O window is available from the View menu.

fib_tio_FF93_04.png

Use this window to enter input to your application, and display output from it.

To use this window, you must:

  • Link your application with the option Semihosted or IAR breakpoint.

    C-SPY will then direct stdin, stdout and stderr to this window. If the Terminal I/O window is closed, C-SPY will open it automatically when input is required, but not for output.

The following possibilities for using Terminal I/O in real time apply:

Device

Description

Cortex-M

The stdout of your application is routed via SWO. See SWO Configuration dialog box, specifically the ITM Stimulus Port option.

Arm7/Arm9, including Armxxx-S, and when using the C-SPY J-Link/J-Trace driver

DCC can be used for Terminal I/O output by adding the file arm\src\debugger\dcc\DCC_Write.c to your project. DCC_write.c overrides the library function write. Functions such as printf can then be used to output text to the Terminal I/O window.

In this case, you can disable semihosting which means that the breakpoint it uses is freed for other purposes. To disable semihosting, choose General Options>Library Configuration>Library low-level interface implementation>None.

Table 17. Terminal I/O in real time 


Requirements

Can be used with all C-SPY debugger drivers and debug probes.

Toolbar
Input

Type the text that you want to input to your application.

Ctrl codes

Opens a menu for input of special characters, such as EOF (end of file) and NUL.

EditSettingsButtonEnabled.png

Opens the IDE Options dialog box where you can set options for terminal I/O. For information about the options available in this dialog box, see Terminal I/O optionsTerminal I/O options.

SavetoLogButton_01.png

Opens the Terminal I/O Log File dialog box, where you can configure and toggle logging on/off, see Terminal I/O Log File dialog box.