13.07.2015 Views

TASKING VX-toolset for ARM User Guide

TASKING VX-toolset for ARM User Guide

TASKING VX-toolset for ARM User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>TASKING</strong> <strong>VX</strong>-<strong>toolset</strong> <strong>for</strong> <strong>ARM</strong> <strong>User</strong> <strong>Guide</strong>11.4.3. File System Simulation (FSS) ViewDescriptionThe File System Simulation (FSS) view is automatically opened when the target requests FSS input orgenerates FSS output. The virtual terminal that the FSS view represents, follows the VT100 standard. Ifyou right-click in the view area of the FSS view, a menu is presented which gives access to someself-explanatory functions.VT100 characteristicsThe queens example demonstrates some of the VT100 features. (You can find the queens example inthe \examples directory from where you can import it into your workspace.)Per debugging session, you can have more than one FSS view, each of which is associated with a positiveinteger. By default, the view "FSS #1" is associated with the standard streams stdin, stdout, stderrand stdaux. Other views can be accessed by opening a file named "terminal window ", asshown in the example below.FILE * f3 = fopen("terminal window 3", "rw");fprintf(f3, "Hello, window 3.\n");fclose(f3);You can set the initial working directory of the target application in the Debug configuration dialog (seealso Section 11.2, Creating a Customized Debug Configuration):1. On the Debugger tab, select the Miscellaneous sub-tab.2. In the FSS root directory field, specify the FSS root directory.The FSS implementation is designed to work without user intervention. Nevertheless, there are someaspects that you need to be aware of.First, the interaction between the C library code (in the files dbg*.c and dbg*.h; see Section 13.2.5,dbg.h) and the debugger takes place via a breakpoint, which incidentally is not shown in the Breakpointsview. Depending on the situation this may be a hardware breakpoint, which may be in short supply.Secondly, proper operation requires certain code in the C library to have debug in<strong>for</strong>mation. This debugin<strong>for</strong>mation should normally be present but might get lost when this in<strong>for</strong>mation is stripped later in thedevelopment process.11.4.4. Disassembly ViewThe Disassembly view shows target memory disassembled into instructions and / or data. If possible, theassociated C / C++ source code is shown as well. The Address field shows the address of the currentselected line of code.To view the contents of a specific memory location, type the address in the Address field. If the addressis invalid, the field turns red.278

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!