RMOS3-GNU V3.0 is a further development of the new development platform for RMOS3 based on the GNU development tools and the integrated graphical development environment Eclipse. Apart from support for the current versions of Eclipse and CDT, the following functions are offered in combination with RMOS3:

Terminal plug-in (new)

The terminal plug-in creates a view in the Eclipse IDE that makes it possible to operate one or more target systems via TELNET. This view is available during program development as well as during the debug phase. The view can assign a suitable, freely selectable name for easier identification of the respective target system.

In addition to operating the RMOS3 system, the developer is also able to watch the messages from the RMOS3 applications, without the need to switch to other Telnet programs.

Profiling plug-in (new)

The profiling plug-in allows the user to investigate the load distribution and the task activity on the target system. The plug-in comprises the two views "Load Distribution" and "Task Activity".

Load Distribution

The "Load Distribution" view shows the percentage loading on the individual processor cores, as well as the percentage loading of the overall system per task, during one measurement.

The loading on the CPU with one or two processor cores is shown in the left-hand part of the view with the help of bars. There is one bar per processor core for "Task" load, "S-State" interrupt load and "Idle Time". On the right-hand side, the load distribution for all tasks is shown in tabular form. The display can be sorted according to a column, by clicking the column header.

The developer can use the "Load Distribution" display to gain an overview of the loading of the overall system and can sort the tasks to discover large consumers of computing time.

Task Activity

The "Task Activity" view displays the individual RMOS3 calls with a time stamp and the interrupts that are performed during a measurement.

To analyze specific results, the data can be sorted, filtered and saved after measuring. The developer therefore has a convenient tool for analyzing the timing of events on the target system.

RMOS3 simulation

RMOS3 simulation allows RMOS3 programs to be pretested on the development PC with Windows using Eclipse. You can, therefore, work independently of the target hardware and start developing your automation solution early, and implement and test hardware-independent parts of your application.

Remote launcher plug-in (extended)

The remote launcher configuration can be used to transfer a generated application to the target system at the click of a button and to start it. Outputs from the program that is integrated in the Eclipse IDE are then displayed in the console.

The remote launcher also allows an application to be debugged on the target system both in Privilege Level 0 and in Privilege Level 3 without the need to manually transfer the application to the target system and start the debug server.

FTP plug-in

The FTP plug-in included in the delivery package enables the created application to be downloaded from the Eclipse IDE to the target system. Switchover to additional FTP clients is no longer necessary. Downloading is performed at the click of a button.

RMOS3 project type

The project plug-in "Executable (GNU on RMOS)" as well as "Static Library (GNU on RMOS)" makes it easy to create new projects in the Eclipse IDE by presetting parameters. When the project is created, the required configuration "Release", "Debug" and/or "Simulation" can be selected. All the necessary compiler, linker and debugger settings have already been made and you can start creating and testing the program immediately.

Code completion

Code completion is offered in Eclipse IDE for the RMOS, CRUN and CLI functions. This support can be extended by reinstalling additional RMOS3 products (e.g. BSP SIMATIC IPC V3.0, RMOS3 TCP/IP V2.3).

To use code completion, you simply type the first characters of the required function and press "CTRL+SPACE". A selection box is then displayed containing a list of all functions that start with these letters. The type of return parameter and the parameters complete with their data are also displayed.

When you select a function, it will be inserted at the current cursor position. The cursor waits at the first parameter or void function behind the closing bracket. For functions with several parameters, use the "TAB" button to jump from one parameter to the next.

Error messages from the compiler caused by typing mistakes can therefore be prevented and the expected parameter types can be immediately recognized, so there is no need to refer to the documentation.

RMOS3 help function

A help function is also available in German for the RMOS3 calls, the CRUN calls and the CLI calls. This support can be extended by reinstalling additional RMOS3 products (e.g. BSP SIMATIC IPC V3.0, RMOS3 TCP/IP V2.3).

You open the help either via the Help menu of Eclipse or by pressing the "F1" key after positioning the cursor on the required function call. You receive a detailed description of the call with additional links to related function calls that is similar to the description of function calls in the RMOS3 reference manuals.

Debugger

The debugger integrated into Eclipse offers convenient functions for testing your application in simulation mode on your development computer and via the Ethernet coupling to the RMOS3 target system.

The connection to the RMOS3 target system is built up via the GNU debug server which can be used under RMOS3 V3.40 as well as under RMOS3 V3.50:

• Quick and easy starting of the GNU debug server:
  The GNU debug server on the RMOS3 target system can also be started without specifying the IP address and port number. The IP address of the RMOS3 computer on which the GDB server is started is used here as the IP address. The default port number used is 8200.
• Debugging of executing applications:
  It is possible at any time to connect the main task of the application as well as the child tasks created by the main task using the option "Attach" and to debug them. There is no need for time-consuming adjustment of the behavior of the application under the control of the debugger.
• Source code display for general protection errors:
  It is also possible to connect to an application in which an exception has occurred. After connecting to the GNU debug server, the destination in the source text is then shown in which an exception has occurred.