This application note describes how to use Eclipse for building and debugging applications for Emcraft Cortex-M BSPs.
1. Installing Eclipse IDE
Download and install a Linux version Eclipse IDE to the Linux host.
The latest version of Eclipse IDE for C/C++ Developers can be found here:
https://www.eclipse.org/downloads/eclipse-packages/
2. Creating a Project in Eclipse
Perform the following steps to create a single file project in Eclipse.
Start Eclipse and select a workspace directory, different from the directory where your source file is located.
To create an empty project, open File -> New -> C/C++ Project, select ะก Managed Build and click Next.
In C Project window enter the name of the project, for example,
c-example
, select Empty Project -> Cross GCC and click Finish.On this step you are prompted to choose build configurations. Click Next to proceed with the default settings.
In the Cross GCC Command window, enter
arm-buildroot-uclinuxfdpiceabi-
in the Cross compiler prefix box and/usr/local/arm-buildroot-uclinuxfdpiceabi_sdk-buildroot/bin
in Cross compiler path, click Finish.To add the source file to the project, open File -> Import. In the Import window select General -> File System, click Next.
Navigate to the directory where the source file is located (
/home/sasha/work
in the example below). Select the directory in the left window.Click Finish to complete.
3. Building the Project
To build the project, press Ctrl-B.
4. Debugging the Project on the Target
On the host filesystem, the executable binaries are located in the Debug
subfolder of the Eclipse workspace directory:
% $ ls -1 eclipse-workspace/c-example/Debug/ app.d app.o c-example makefile sources.mk subdir.mk $
In the directory above, c-example
is the binary for Cortex-M target.
For remote debugging, you need to deploy the c-example
binary to the target. This can be done in several ways:
Using
scp
orsftp
to copy the binary to the target;Using NFS share configured on the host and mounting this share from the target.
We will demonstrate the second method. Suppose we have the Eclipse workspace directory (for example, /srv/homes/eclipse-workspace/
) exported as NFS share. Let's modify the Linux project to auto-mount this directory via NFS. Add the following lines to etc/rc
and rebuild the project:
% cd projects/rootfs % vi etc/rc ... sleep 2 mount -o nolock 192.168.0.103:/srv/homes/eclipse-workspace/ /mnt/nfs ...
After loading the project to the target, you should have your Eclipse workspace directory mounted as /mnt/nfs
:
/ # df Filesystem 1K-blocks Used Available Use% Mounted on 192.168.0.103:/srv/homes/eclipse-workspace/ 488645632 124968960 338781184 27% /mnt/nfs / # ls -la /mnt/nfs/c-example/Debug/ drwxrwxr-x 2 1005 1005 4096 Jun 11 2024 . drwxrwxr-x 4 1005 1005 4096 Jun 11 2024 .. -rw-rw-r-- 1 1005 1005 16 Jun 11 2024 app.d -rw-rw-r-- 1 1005 1005 52048 Jun 11 2024 app.o -rwxrwxr-x 1 1005 1005 41680 Jun 11 2024 c-example -rw-rw-r-- 1 1005 1005 1360 Jun 11 2024 makefile -rw-rw-r-- 1 1005 1005 402 Jun 11 2024 sources.mk -rw-rw-r-- 1 1005 1005 752 Jun 11 2024 subdir.mk / #
Now, we need to add Debug Configuration to the Eclipse project:
Open Run -> Debug Configurations -> C/C++ Remote Applications:
Create a new configuration in C/C++ Remote Application by clicking + in the upper left part of the dialogue:
In the Main tab, change Using GDB Automatic Remote Debugging Launcher: click to Select other... and choose Manual Remote Debugging Launcher:
Now, switch to the Debugger tab and change gdb to arm-buildroot-uclinuxfdpiceabi-gdb pointing out a full path to it:
Select the Connection tab and enter an IP address of you target, and
gdbserver
connection port:Click Apply (don't click Debug yet!).
5. Debugging on the Target
Now, we are ready to debug on the target. In the target console window, start gdbserver with you application using the port number your specified above:
/ # gdbserver :1234 /mnt/nfs/c-example/Debug/c-example Process /mnt/nfs/c-example/Debug/c-example created; pid = 134 Listening on port 1234
Back to the Eclipse, click Debug. You will be asked to switch to the Debug Perspective window, accept it:
When started under remote debugger, the program automatically stops at the main() function.
Now you can execute you program with steps, put breakpoints, and examine variables: