Linux debug in CCSv5

Please provide the version numbers for the CCS you are using.  Windows or Linux version?

You should be able to enable all items in the capabilities dialog.

Which EZSDK / DVSDK and version and MPU device are you working with

Regards,

Michael

Michael,

         I am using Code composer studio  Version: 5.1.0.09000  on Windows XP environment.

I am not able find  below items in the capabilities dialog

1.CDT-Debug-c/c++ Development Tools
2.CDT DSF-GDB - GDB Debugging
3.CDT-DSF Debug Services Framework

I am not able to understand your 3rd question           "Which EZSDK / DVSDK and version and MPU device are you working with"

I am working on OMAPL138

Is there any EZSDK or DVSDK available for windows ?   

I am not having any EZSDK or DVSDK  on windows. 

For OMAP-L138 there are several software development kits

for Linux, WinCE, SYSBIOS (for DSP) and Starterware (if not using an O/S)

http://www.ti.com/product/omap-l138#toolssoftware

Just enable all items in the CCS Capabilities dialog.

When you create a new debug configuration use the "C/C++ Remote Application" type.

In Debug Configurations on Main tab, click "Select Other" to open the Select Preferred Launcher dialog.

Check "Use configuration specific settings".

Choose "GDB(DSF) manual remote debugging launcher" if you will transfer executable to target manually and start gdbserver manually in a console window.

Choose "GDB(DSF) automatic remote debugging launcher" if you will use a Remote System Explorer SSH connection to do those steps automatically.

Regards,

Michael T

Thanks Michael,

         1.Target board is Zoom (OMAPL138B),
 The snapshot of gdbserver running on  target ( Viewed through Hyper terminal)  is given below

root@hawkboard:/# cd media/sda1/gdb\ needs/
root@hawkboard:/media/sda1/gdb needs# cp gdbserver /usr/bin/
root@hawkboard:/media/sda1/gdb needs# cp libthread_db* /lib/
root@hawkboard:/media/sda1/gdb needs# gdbserver 10.1.5.92:1000 Firrst
Process Firrst created; pid = 1187
Listening on port 1000

2.CCS Version: 5.1.0.09000 on windows

I followed your steps as mentioned above . I am unable to debug,.

when i given debug am getting following error:

For GDB(DSF) Automatic Remote Debugging Launcher, In progress bar -> it stays Launching:Configuring GDB
Error in final launch sequence
Failed to execute MI command:
-target-select remote LOCALHOST:1000
Error message from debugger back end:
LOCALHOST:1000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
LOCALHOST:1000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

For GDB(DSF) Manual Remote Debugging Launcher, In progress bar -> it stays Launching:Configuring GDB
Error in final launch sequence
Failed to execute MI command:
-target-select remote LOCALHOST:1000
Error message from debugger back end:
LOCALHOST:1000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
LOCALHOST:1000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

for some times,
Error in final launch sequence
Failed to execute MI command:
-exec-run
Error message from debugger back end:
Don't know how to run.  Try "help target".
Don't know how to run.  Try "help target".


For Standard Remote Create Proces Launcher
Target selection failed.
LOCALHOST:1000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
LOCALHOST:1000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
LOCALHOST:1000: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

In run mode debug, (select Window -> Preferences -> General -> Capabilities)" still I didn't get,
1.CDT-Debug-c/c++ Development Tools
2.CDT DSF-GDB - GDB Debugging
3.CDT-DSF Debug Services Framework
but I have CDT GDB Debugging option as enabled

Kindly help me.

The debug configuration should have the IP address of the target board (not the linux host)

and must have the same port number (1000 in your case).

Try this

gdbserver :1000 /usr/bin/<executable-name>

Regards,

Michael T

Hello Michael,

we both are working together here for this. still we are facing the same problem. Kindly help me on this regard.

I've followed your instructions,

@ Host (windows)side, communicating to target via hyper terminal

#cp libthread_db* /lib/

#cp gdbserver /usr/bin/

#cp Firrst /usr/bin

#gdbserver :1000 /usr/bin/Firrst

Process /usr/bin/Firrst created; pid = 1190

Listening on port 1000

-------------------------------------------------------------------------------------------------------------------

@ Host (windows) side, On CCSv5

Debug Configuration -> c/c++ Remote Appl - >

main->

+Disabled auto build

+GDB(DSF)Automatic Remote Debugging Launcher

Debugger->

GDB debugger -> copied the path "codesourcery\sourcery G++ Lite\bin\arm-none-linux-gnueabi-gdb.exe"

GDB command file -> .gdbinit

Gdbserver setting ->

Gdbserver name: 10.1.5.115, Port number : 1000

Result @ CCSv5  By hitting Debug button:

Kindly help me........

Hi Michael,

I am also having same issue.

I have enabled all items CCS capabilities dialog.

But still i could not find GDB(BSF) remote system process launcher.

Is there any other setting to be done.

Sanket