Debugging TMS320, Step 1

I maintain the code for a controller based on the TMS320R2811.  My system
uses the boot loader to download the execuable code from a host app, so I
need to know how to set breakpoints after the download is done.  Someone
else, long since gone, did the original development, so I missed that stage
of the development.  So far, I've been able to get by without a debugger,
but those days are over.  I am now trying to figure out how to get started
with simple debugging (breakpoints and reading and setting variables).  I
understand that I can order a USB JTAG cable, but then what?  Where can I
find a good "getting started" guide?  My questions are along the lines of
"how do I tell Code Composer I have the device hooked up?" "How do I set a
breakpoint in code the processor hasn't downloaded yet?"  That sort of
thing.

I'm using CodeComposer 3.3.82.13, freshly updated today.

Radly wrote:
> I maintain the code for a controller based on the TMS320R2811.  My
> system uses the boot loader to download the execuable code from a
> host app, so I need to know how to set breakpoints after the download
> is done.  Someone else, long since gone, did the original
> development, so I missed that stage of the development.  So far, I've
> been able to get by without a debugger, but those days are over.  I
> am now trying to figure out how to get started with simple debugging
> (breakpoints and reading and setting variables).  I understand that I
> can order a USB JTAG cable, but then what?  Where can I find a good
> "getting started" guide?  My questions are along the lines of "how do
> I tell Code Composer I have the device hooked up?" "How do I set a
> breakpoint in code the processor hasn't downloaded yet?"  That sort
> of thing.
>
> I'm using CodeComposer 3.3.82.13, freshly updated today.

You are right about the USB JTAG for the job.  It should interface directly 
with CCS.  I would recommend the 560 series from TI, but it is also made by 
others and may be cheaper.

You can set a breakpoint at any time, so setting it before the code is 
loaded is not a problem.  When the address you have set the breakpoint on is 
reached the code will stop.  The bigger problem may be knowing what those 
addresses are.  The code is presumably linked for where it is loaded, so you 
may be able to do debugging with full source information.

As to telling CCS that the device is hooked up, once you have told CCS that 
you are using the JTAG emulator it will not start until it can talk to the 
JTAG.  If I remember right, the CCS setup utility will be invoked 
automatically if it can not communicate with the device.

Scott

On Mon, 17 Aug 2009 09:56:44 -0600, "Not Really Me"
<scott@validatedQWERTYsoftware.XYZZY.com> wrote in comp.arch.embedded:

> Radly wrote:
> > I maintain the code for a controller based on the TMS320R2811.  My
> > system uses the boot loader to download the execuable code from a
> > host app, so I need to know how to set breakpoints after the download
> > is done.  Someone else, long since gone, did the original
> > development, so I missed that stage of the development.  So far, I've
> > been able to get by without a debugger, but those days are over.  I
> > am now trying to figure out how to get started with simple debugging
> > (breakpoints and reading and setting variables).  I understand that I
> > can order a USB JTAG cable, but then what?  Where can I find a good
> > "getting started" guide?  My questions are along the lines of "how do
> > I tell Code Composer I have the device hooked up?" "How do I set a
> > breakpoint in code the processor hasn't downloaded yet?"  That sort
> > of thing.
> >
> > I'm using CodeComposer 3.3.82.13, freshly updated today.
> 
> You are right about the USB JTAG for the job.  It should interface directly 
> with CCS.  I would recommend the 560 series from TI, but it is also made by 
> others and may be cheaper.
> 
> You can set a breakpoint at any time, so setting it before the code is 
> loaded is not a problem.  When the address you have set the breakpoint on is 
> reached the code will stop.  The bigger problem may be knowing what those 
> addresses are.  The code is presumably linked for where it is loaded, so you 
> may be able to do debugging with full source information.
> 
> As to telling CCS that the device is hooked up, once you have told CCS that 
> you are using the JTAG emulator it will not start until it can talk to the 
> JTAG.  If I remember right, the CCS setup utility will be invoked 
> automatically if it can not communicate with the device.
> 
> Scott

Scott,

Your advice is pretty good, but there is one point where the OP might
save a little money.

The 28xxx leaves out some of the fancy debug features of some of the
other TI DSP families, so there is no real gain in paying more for a
560 series JTAG debugger over a 510 class device.

-- 
Jack Klein http://JK-Technology.Com
FAQs for
news:comp.lang.c http://c-faq.com/
news:comp.lang.c++ http://www.parashift.com/c++-faq-lite/
news:alt.comp.lang.learn.c-c++
http://www.club.cc.cmu.edu/~ajo/docs/FAQ-acllc.html 

On Aug 18, 4:43=A0am, Jack Klein <jackkl...@spamcop.net> wrote:
> On Mon, 17 Aug 2009 09:56:44 -0600, "Not Really Me"
> <sc...@validatedQWERTYsoftware.XYZZY.com> wrote in comp.arch.embedded:
>
>
>
> > Radly wrote:
> > > I maintain the code for a controller based on the TMS320R2811. =A0My
> > > system uses the boot loader to download the execuable code from a
> > > host app, so I need to know how to set breakpoints after the download
> > > is done. =A0Someone else, long since gone, did the original
> > > development, so I missed that stage of the development. =A0So far, I'=
ve
> > > been able to get by without a debugger, but those days are over. =A0I
> > > am now trying to figure out how to get started with simple debugging
> > > (breakpoints and reading and setting variables). =A0I understand that=
 I
> > > can order a USB JTAG cable, but then what? =A0Where can I find a good
> > > "getting started" guide? =A0My questions are along the lines of "how =
do
> > > I tell Code Composer I have the device hooked up?" "How do I set a
> > > breakpoint in code the processor hasn't downloaded yet?" =A0That sort
> > > of thing.
>
> > > I'm using CodeComposer 3.3.82.13, freshly updated today.
>
> > You are right about the USB JTAG for the job. =A0It should interface di=
rectly
> > with CCS. =A0I would recommend the 560 series from TI, but it is also m=
ade by
> > others and may be cheaper.
>
> > You can set a breakpoint at any time, so setting it before the code is
> > loaded is not a problem. =A0When the address you have set the breakpoin=
t on is
> > reached the code will stop. =A0The bigger problem may be knowing what t=
hose
> > addresses are. =A0The code is presumably linked for where it is loaded,=
 so you
> > may be able to do debugging with full source information.
>
> > As to telling CCS that the device is hooked up, once you have told CCS =
that
> > you are using the JTAG emulator it will not start until it can talk to =
the
> > JTAG. =A0If I remember right, the CCS setup utility will be invoked
> > automatically if it can not communicate with the device.
>
> > Scott
>
> Scott,
>
> Your advice is pretty good, but there is one point where the OP might
> save a little money.
>
> The 28xxx leaves out some of the fancy debug features of some of the
> other TI DSP families, so there is no real gain in paying more for a
> 560 series JTAG debugger over a 510 class device.
>
> --
> Jack Kleinhttp://JK-Technology.Com
> FAQs for
> news:comp.lang.chttp://c-faq.com/
> news:comp.lang.c++http://www.parashift.com/c++-faq-lite/
> news:alt.comp.lang.learn.c-c++http://www.club.cc.cmu.edu/~ajo/docs/FAQ-ac=
llc.html

I agree with Jack, the 560 series is an overkill for C28xx devices.

Regarding the breakpoints, I would like to remind you that there are
two kinds:
Hardware breakpoints which are basically program counter comparators
and you can set only two of them and
Software breakpoints which are basically assembly "ESTOP0"
instruction. You can set any number of them, but only in RAM, and they
can be overwritten by the CPU. Therefore SW breakpoints must be set
after the code was loaded. You were warned.

Once you are connected to the CPU you should load symbols from the
compiler generated .out file so that CCS can link the source files
(.c, .asm) with program counter in order to have the ability to step
through the code, not only through disassembly

Good Luck

Mitja

On 17 =D0=90=D0=B2=D0=B3, 14:27, "Radly" <da...@daryllee.com> wrote:
> I maintain the code for a controller based on the TMS320R2811. =C2=A0My s=
ystem
> uses the boot loader to download the execuable code from a host app, so I
> need to know how to set breakpoints after the download is done. =C2=A0Som=
eone
> else, long since gone, did the original development, so I missed that sta=
ge
> of the development. =C2=A0So far, I've been able to get by without a debu=
gger,
> but those days are over. =C2=A0I am now trying to figure out how to get s=
tarted
> with simple debugging (breakpoints and reading and setting variables). =
=C2=A0I
> understand that I can order a USB JTAG cable, but then what? =C2=A0Where =
can I
> find a good "getting started" guide? =C2=A0My questions are along the lin=
es of
> "how do I tell Code Composer I have the device hooked up?" "How do I set =
a
> breakpoint in code the processor hasn't downloaded yet?" =C2=A0That sort =
of
> thing.
>
> I'm using CodeComposer 3.3.82.13, freshly updated today.

please check http://www.olimex.com/dev/tms320-jtag-usb.html it may be
what you want, low cost (EUR 55) programming and debugging tool for
TMS320 family
a bit slower than the other expensive USB JTAGs but does same step,
breakpoints etc

Best regards
Tsvetan Usunov
Olimex ltd
---------
Development and prototype boards, programmers, debuggers for ARM, AVR,
MSP430, MAXQ2000 and PIC at http://www.olimex.com/dev
Fast PCB prototypes in 3-5 working days for EUR 30 at http://www.olimex.com=
/pcb

Jack Klein wrote:
> On Mon, 17 Aug 2009 09:56:44 -0600, "Not Really Me"
> <scott@validatedQWERTYsoftware.XYZZY.com> wrote in comp.arch.embedded:
>
>> Radly wrote:
>>> I maintain the code for a controller based on the TMS320R2811.  My
>>> system uses the boot loader to download the execuable code from a
>>> host app, so I need to know how to set breakpoints after the
>>> download is done.  Someone else, long since gone, did the original
>>> development, so I missed that stage of the development.  So far,
>>> I've been able to get by without a debugger, but those days are
>>> over.  I am now trying to figure out how to get started with simple
>>> debugging (breakpoints and reading and setting variables).  I
>>> understand that I can order a USB JTAG cable, but then what?  Where
>>> can I find a good "getting started" guide?  My questions are along
>>> the lines of "how do I tell Code Composer I have the device hooked
>>> up?" "How do I set a breakpoint in code the processor hasn't
>>> downloaded yet?"  That sort of thing.
>>>
>>> I'm using CodeComposer 3.3.82.13, freshly updated today.
>>
>> You are right about the USB JTAG for the job.  It should interface
>> directly with CCS.  I would recommend the 560 series from TI, but it
>> is also made by others and may be cheaper.
>>
>> You can set a breakpoint at any time, so setting it before the code
>> is loaded is not a problem.  When the address you have set the
>> breakpoint on is reached the code will stop.  The bigger problem may
>> be knowing what those addresses are.  The code is presumably linked
>> for where it is loaded, so you may be able to do debugging with full
>> source information.
>>
>> As to telling CCS that the device is hooked up, once you have told
>> CCS that you are using the JTAG emulator it will not start until it
>> can talk to the JTAG.  If I remember right, the CCS setup utility
>> will be invoked automatically if it can not communicate with the
>> device.
>>
>> Scott
>
> Scott,
>
> Your advice is pretty good, but there is one point where the OP might
> save a little money.
>
> The 28xxx leaves out some of the fancy debug features of some of the
> other TI DSP families, so there is no real gain in paying more for a
> 560 series JTAG debugger over a 510 class device.

Good to know, thanks.  I haven't used the 28xxx family, but many of the 
others.

Scott

"Olimex" <tsvetanusunov@gmail.com> schreef in bericht
news:1527ff5d-4ae7-4221-b254-33c93a69ffc9@k30g2000yqf.googlegroups.com...
On 17 ???, 14:27, "Radly" <da...@daryllee.com> wrote:
> I maintain the code for a controller based on the TMS320R2811. My system
> uses the boot loader to download the execuable code from a host app, so I
> need to know how to set breakpoints after the download is done. Someone
> else, long since gone, did the original development, so I missed that
stage
> of the development. So far, I've been able to get by without a debugger,
> but those days are over. I am now trying to figure out how to get started
> with simple debugging (breakpoints and reading and setting variables). I
> understand that I can order a USB JTAG cable, but then what? Where can I
> find a good "getting started" guide? My questions are along the lines of
> "how do I tell Code Composer I have the device hooked up?" "How do I set a
> breakpoint in code the processor hasn't downloaded yet?" That sort of
> thing.
>
> I'm using CodeComposer 3.3.82.13, freshly updated today.

please check http://www.olimex.com/dev/tms320-jtag-usb.html it may be
what you want, low cost (EUR 55) programming and debugging tool for
TMS320 family
a bit slower than the other expensive USB JTAGs but does same step,
breakpoints etc

Will this device also work for the DaVinci DSP's (TMS320DM642)?

Antoon

>
>"Olimex" <tsvetanusunov@gmail.com> schreef in bericht
>news:1527ff5d-4ae7-4221-b254-33c93a69ffc9@k30g2000yqf.googlegroups.com...
>On 17 ???, 14:27, "Radly" <da...@daryllee.com> wrote:
>> I maintain the code for a controller based on the TMS320R2811. My
system
>> uses the boot loader to download the execuable code from a host app, so
I
>> need to know how to set breakpoints after the download is done.
Someone
>> else, long since gone, did the original development, so I missed that
>stage
>> of the development. So far, I've been able to get by without a
debugger,
>> but those days are over. I am now trying to figure out how to get
started
>> with simple debugging (breakpoints and reading and setting variables).
I
>> understand that I can order a USB JTAG cable, but then what? Where can
I
>> find a good "getting started" guide? My questions are along the lines
of
>> "how do I tell Code Composer I have the device hooked up?" "How do I
set a
>> breakpoint in code the processor hasn't downloaded yet?" That sort of
>> thing.
>>
>> I'm using CodeComposer 3.3.82.13, freshly updated today.
>
>please check http://www.olimex.com/dev/tms320-jtag-usb.html it may be
>what you want, low cost (EUR 55) programming and debugging tool for
>TMS320 family
>a bit slower than the other expensive USB JTAGs but does same step,
>breakpoints etc
>
>Will this device also work for the DaVinci DSP's (TMS320DM642)?
>
>Antoon
>

You have all been most helpful.  Now as soon as my hardware guy sends me
the development unit with the JTAG adapter in place, I have something to go
on!  Thanks again.

Olimex wrote:

> On 17 &#1040;&#1074;&#1075;, 14:27, "Radly" <da...@daryllee.com> wrote:
>> I maintain the code for a controller based on the TMS320R2811.  My system
>> uses the boot loader to download the execuable code from a host app, so I
>> need to know how to set breakpoints after the download is done.  Someone
>> else, long since gone, did the original development, so I missed that
>> stage of the development.  So far, I've been able to get by without a
>> debugger, but those days are over.  I am now trying to figure out how to
>> get started with simple debugging (breakpoints and reading and setting
>> variables).  I understand that I can order a USB JTAG cable, but then
>> what?  Where can I find a good "getting started" guide?  My questions are
>> along the lines of "how do I tell Code Composer I have the device hooked
>> up?" "How do I set a breakpoint in code the processor hasn't downloaded
>> yet?"  That sort of thing.
>>
>> I'm using CodeComposer 3.3.82.13, freshly updated today.
> 
> please check http://www.olimex.com/dev/tms320-jtag-usb.html it may be
> what you want, low cost (EUR 55) programming and debugging tool for
> TMS320 family
> a bit slower than the other expensive USB JTAGs but does same step,
> breakpoints etc
> 
> Best regards
> Tsvetan Usunov
> Olimex ltd
> ---------
> Development and prototype boards, programmers, debuggers for ARM, AVR,
> MSP430, MAXQ2000 and PIC at http://www.olimex.com/dev
> Fast PCB prototypes in 3-5 working days for EUR 30 at
> http://www.olimex.com/pcb

What's wrong with the Alternator signal that provides the "Ignition light" 
switching?

Paul E. Bennett