Code Composer Studio for TI OMAP 35xx

2010-10-07 Thread Elvis Dowson
Hi,
Is there a version of CCS that will run on linux and work for the TI 
OMAP 35xx?  I primarily want to do target based debugging of the linux-omap 
kernel, using an Eclipse or similar IDE type front end with kgdb.

Best regards,

Elvis Dowson

--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Code Composer Studio for TI OMAP 35xx

2010-10-07 Thread Elvis Dowson
On Oct 7, 2010, at 7:19 PM, Elvis Dowson wrote:

 Hi,
Is there a version of CCS that will run on linux and work for the TI 
 OMAP 35xx?  I primarily want to do target based debugging of the linux-omap 
 kernel, using an Eclipse or similar IDE type front end with kgdb.

BTW, I downloaded CCS4, but it only runs on windows. 

http://focus.ti.com/docs/toolsw/folders/print/ccstudio.html

I don't want to use windows for linux kernel debugging :-) I came across a wiki 
that was under construction that hinted at a CCS5 that runs on Linux. 

Is it possible to try that out?

Elvis Dowson
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Code Composer Studio for TI OMAP 35xx

2010-10-07 Thread Mark Grosen

On 10/7/2010 8:22 AM, Elvis Dowson wrote:

On Oct 7, 2010, at 7:19 PM, Elvis Dowson wrote:


Hi,
Is there a version of CCS that will run on linux and work for the TI 
OMAP 35xx?  I primarily want to do target based debugging of the linux-omap 
kernel, using an Eclipse or similar IDE type front end with kgdb.


BTW, I downloaded CCS4, but it only runs on windows.

http://focus.ti.com/docs/toolsw/folders/print/ccstudio.html

I don't want to use windows for linux kernel debugging :-) I came across a wiki 
that was under construction that hinted at a CCS5 that runs on Linux.

Is it possible to try that out?


You can get the Linux version of CCS here:
http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

A wiki article on using JTAG to debug Linux kernel is here:
http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5

Note that you really do not need the TI CCS version of Eclipse to use 
kgdb - you could just grab the generic version from eclipse.org


Mark


--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Code Composer Studio for TI OMAP 35xx

2010-10-07 Thread Elvis Dowson
Hi Mark,

On Oct 7, 2010, at 10:20 PM, Mark Grosen wrote:
 
 A wiki article on using JTAG to debug Linux kernel is here:
 http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5
 
 Note that you really do not need the TI CCS version of Eclipse to use kgdb - 
 you could just grab the generic version from eclipse.org

Thanks for the reply. I'm having trouble connecting to the target via the 
serial console, I get a bunch of error messages when attempt to connect to kgdb 
first via a command line. (It didn't work from standard Eclipse IDE, and that 
doesn't give much info,  but the command line does, thought CCS might have some 
better support for this, but guess I have to resolve the command line 
connectivity issues first before using the IDE.) 

Here is what I've done.

I have the following u-boot environment variables set, for the console and 
mmcargs bootargs

# setenv console ttyS2,115200n8
# setenv mmcargs 'setenv bootargs console=${console} vram=12M omapfb.vram=0:4M 
omapfb.mode=dvi:${dvimode} omapdss.def_disp=${defaultdisplay} 
root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init kgdboc=${console} 
kgdbwait'

Testing it quickly with kermit gives the expected response

console [ttyS2] enabled
kgdb: Registered I/O driver kgdboc.
kgdb: Waiting for connection from remote gdb...

I have on the target board, ttys2, the TI OMAP 3503 serial port configured as 
the debug console. and the board that I have has an FTDI to USB converter.

This when connected to the host appears as /dev/ttyUSB0

I then log in as root, after closing all previous sessions, power on the target 
hardware (Gumstix Overo Earth TI OMAP 3503 based platform), and then type the 
following commands, but get a bunch or error messages. 


# su
# cd /tool/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel

# arm-angstrom-linux-gnueabi-gdb
GNU gdb (GDB) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as --host=x86_64-linux 
--target=arm-angstrom-linux-gnueabi.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
(gdb) file vmlinux
Reading symbols from 
/tool/overo-oe/tmp/staging/overo-angstrom-linux-gnueabi/kernel/vmlinux...done.
(gdb) set remotebaud 115200
(gdb) set debug remote 1
(gdb) set debug serial 1
(gdb) target remote /dev/ttyS0

Remote debugging using /dev/ttyS0
Sending packet: $qSupported#37...[
r Timeout: 2 seconds]Sending packet: $qSupported#37...[Timeout: 2 
seconds]Sending packet: $qSupported#37...[Timeout: 2 seconds]Sending packet: 
$qSupported#37...[Timeout: 2 seconds][Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
Ignoring packet error, continuing...
Packet qSupported (supported-packets) is supported
warning: unrecognized item timeout in qSupported response
Sending packet: $Hg0#df...[Timeout: 2 seconds]Sending packet: 
$Hg0#df...[Timeout: 2 seconds]Sending packet: $Hg0#df...[Timeout: 2 
seconds]Sending packet: $Hg0#df...[Timeout: 2 seconds][Timeout: 2 
seconds]Timed out.
[Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
Ignoring packet error, continuing...
Sending packet: $?#3f...[Timeout: 2 seconds]Sending packet: 
$?#3f...[Timeout: 2 seconds]Sending packet: $?#3f...[Timeout: 2 
seconds]Sending packet: $?#3f...[Timeout: 2 seconds][Timeout: 2 
seconds]Timed out.
[Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
Ignoring packet error, continuing...
Sending packet: $Hc-1#09...[Timeout: 2 seconds]Sending packet: 
$Hc-1#09...[Timeout: 2 seconds]Sending packet: $Hc-1#09...[Timeout: 2 
seconds]Sending packet: $Hc-1#09...[Timeout: 2 seconds][Timeout: 2 
seconds]Timed out.
[Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
Ignoring packet error, continuing...
Sending packet: $qC#b4...[Timeout: 2 seconds]Sending packet: 
$qC#b4...[Timeout: 2 seconds]Sending packet: $qC#b4...[Timeout: 2 
seconds]Sending packet: $qC#b4...[Timeout: 2 seconds][Timeout: 2 
seconds]Timed out.
[Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
Ignoring packet error, continuing...
Sending packet: $qAttached#8f...[Timeout: 2 seconds]Sending packet: 
$qAttached#8f...[Timeout: 2 seconds]Sending packet: 
$qAttached#8f...[Timeout: 2 seconds]Sending packet: 
$qAttached#8f...[Timeout: 2 seconds][Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed out.
Ignoring packet error, continuing...
Packet qAttached (query-attached) is supported
Sending packet: $qOffsets#4b...[Timeout: 2 seconds]Sending packet: 
$qOffsets#4b...[Timeout: 2 seconds]Sending packet: $qOffsets#4b...[Timeout: 
2 seconds]Sending packet: $qOffsets#4b...[Timeout: 2 seconds][Timeout: 2 
seconds]Timed out.
[Timeout: 2 seconds]Timed out.
[Timeout: 2 seconds]Timed