| Contents | Index |
| On this page… |
|---|
Additional Configuration Steps to Run Your Executable on a Remote Embedded Linux Target |
After you install the third-party software, configure the coder product to work with Eclipse:
Close Eclipse IDE before you run eclipseidesetup. For more information, see Build Errors.
At the MATLAB command line, enter eclipseidesetup. The coder product opens the "IDE Link: Eclipse Adaptor Setup" dialog box, as shown here on Windows:

Update Executable with the location and file name of the Eclipse application file. For example, C:\eclipse\eclipse.exe.
You can get this value by right-clicking a shortcut for Eclipse and looking at the properties.
Update Workspace with the default location where Eclipse creates and saves new project files. For example, C:\WINNT\Profiles\username\workspace.
To find the current workspace, open Eclipse and select File > Switch Workspace > Other.
In the future, if you change the Eclipse workspace, repeat this configuration procedure.
Do not use workspace paths that contain spaces. If you have a path with spaces, recreate the workspace, and then update the path in Eclipse.
For Port number, enter a valid, unused, IP port number. For example, 5555.
For Site, identify where the coder product uploads and runs the executable file upon completing the build process. Use either of these options:
Choose local to run the executable on your Linux or Windows workstation.
This option requires the Simulink Coder product.
Choose remote to download the executable to a remote target running Linux operating system over a network connection (for example, to connect to an embedded system connection to the Ethernet port on your workstation).
This option requires the Embedded Coder product.
You must perform additional steps to connect to a remote target running Linux. See Additional Configuration Steps to Run Your Executable on a Remote Embedded Linux Target.
To customize the Tool Chain settings, see the Custom GCC/GDB topic.
When you click OK or Apply, the coder product:
Verifies the locations of the Executable and Workspace in the Eclipse Adaptor Setup dialog box.
Verifies that the required third-party software is present.
Installs the coder product plug-ins in the Eclipse plugins folder. For example, in C:\Program Files\eclipse\plugins\.
Saves configuration information to the mwidelink.ini file, located in the Eclipse plugins folder.
To verify that the configuration process is complete, create a handle object for the Eclipse IDE. Enter the following command in MATLAB
IDE_Obj = eclipseide
This command, starts Eclipse IDE if it is not already running, and creates a handle object. For example:
Starting Eclipse(TM) IDE... ECLIPSEIDE Object: Default timeout : 10.00 secs Eclipse folder : C:\eclipse3.4\eclipse Eclipse workspace: C:\WINNT\Profiles\rolfedh\workspace Port number : 5555 Processor site : local
If you are using more recent versions of the GNU tools, you can disregard command-line warnings about using untested versions.
In Eclipse, click the following icon to see the status of the IDE Link plug-in.
![]()
On Linux host systems, you can configure the coder product to download and run an executable on a remote target running Embedded Linux.
During the Configuring Your MathWorks Software to Work with Eclipse process, complete these additional steps:
Set Site to remote. The dialog box displays additional Target Processor and GNU GCC/GDB Commands parameters.
Under Target Processor, enter the values the coder product uses to connect to the target processor over the network:
User login: Supply a user name that has trusted "r-" access to the remote system. The user name must appear in the /etc/hosts.equiv or $HOME/.rhosts files on the remote system.
IP address: Enter the IP address of the remote system. To test the software on your local system instead of the remote system, enter localhost.
Port number: Enter the IP port number for communications between the two systems. For example, 10000.
Download path: Enter the path on the remote system that receives the compiled executable and related files. For example, ./ sends the files to the home folder of the user login.
Under GNU GCC/GDB Commands, enter the tool chain commands and optional arguments the coder product uses to build executable for the target processor.
For example, if you are using the generic GNU tool chain to build an executable for a target processor running Embedded Linux, enter:
Assembler: as
C Compiler: gcc
C Linker: gcc
Archiver: ar
Debugger: gdb
For example, if you are using the MontaVista Linux tool chain to build an executable for an ARM processor running Embedded Linux, enter:
Assembler: arm_v5t_le-as
C Compiler: arm_v5t_le-gcc
C Linker: arm_v5t_le-gcc
Archiver: arm_v5t_le-ar
Debugger: arm_v5t_le-gdb
Click OK to complete the Eclipse Adaptor Setup process.
Also see: Working with Linux Target
![]() | Installing Third-Party Software for Eclipse | Troubleshooting with Eclipse IDE | ![]() |

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |