TI-Davinci Development Series 5 CCS5.2 Remote Application Debugging Using gdbserver

Go to the blog post "TI-Davinci Development Series 4 CCS5.2 online debugging of ARM and DSP programs using XDS560v2"
Remote Application debugging with gdbserver (gdbsever porting see Introduction to successfully porting gdbserver and gdbserver in ubuntu10.04 (for CCSV5.2 remote debugging of ARM CORTEX-A8 Program)

/*************************************** **************************************** **************************************** *******************/

Original file. The original source of the article must be indicated by a hyperlink during reprinting: http://blog.csdn.net/gqb_driver/article/details/18034377,the Author: gqb666
/*************************************** **************************************** **************************************** *******************/
1. Create a GCCProject in CCS5.2

When you use gdbserver to debug the target board application, you must create a GCC Project in CCS5.2 and copy the build execution program to the target board for execution. The process of creating a GCCProject in CCS5.2 is as follows:

Click Project> New Project> C/C ++> C Project and click Next.

Name the Project. Set Projecttype to Cross-Compile Project, and Toolchains to CrZ release? Http://www.bkjia.com/kf/ware/vc/ "target =" _ blank "class =" keylink "> vc3MgR0NDo6y147v3TmV4dKGjIDwvcD4KPHA + ICA8aW1nIHNyYz0 =" http://www.bkjia.com/uploadfile/Collfiles/20140110/2014011009024256.jpg "alt =" \ ">

Select the cross-compiler and enter Tool command prefix according to the actual situation. In this project, arm-none-linux-gnueabi is used, and the corresponding Tool Command path is: /usr/local/arm/arm-2009q1/bin. Click Next.

By default, click Finish.

In this way, a new project is created on the project management interface. You can right-click the project name, select Add files, or create a helloworld. c file by yourself. Then, right-click the build project and the following occurs:

2. Configure and perform remote debugging

Run-> DebugConfiguration, select C/C ++ Remote Application, click New launch configuration, and name it gcc_test.

On the Main tab, click SelectOther... Select GDB (DSF) Manual Remote Degugging Launcher. Click OK.

Go to the Debug tab and find the GDB compiled when porting gdbserver In the gdb debugger column. Note that the gbdserver must come from the same version as the gdb here, for example, gdb is installed in the/home/ss/develop_environment/gdb7.1/bin/directory on my machine. Select the default value for the GDB command file.

On the Debug Connection tab, enter the IP address of the target board and a custom port number. Click Apply and CloseDebug to configure other options by default.

Run gdbserver 10.2.7.96: 10000 gcc_test on the target board. gcc_test is compiled by the host machine CCS5.2 and copied to the target board. 10.2.7.96 is the host machine IP address, and 10000 is the port we specified in CCS5.2. After execution, Listeningon port 10000 is displayed, indicating a normal connection wait.

On the host, click gcc_test Debug.

Then, go to the remote debugging interface. It can be seen that the source code is debugged in CCS5.2, and the output information is on the gdbserver side. After debugging is complete, remember to click the stop debugging button in CCS5.2 Debug mode, as shown in the red box in, because a debugsession cannot be stopped on gdbserver.