Reply by Graeme Parker●December 13, 20002000-12-13
Normally using CCSetup produces no problems. You don't really need to
go
through the compjtag & board.dat route. If you only have 4 C60s then it
doesn't matter which order they are listed, when all you are trying to do
is
get CC running. Do you have any C67s in your chain?
> -----Original Message-----
> From: Phil Alder [SMTP:]
> Sent: Tuesday, December 12, 2000 2:31 PM
> To:
> Subject: Re: [c6x] Debugging four TMS320C6201
>
> Graeme Parker wrote:
>
> > Hi Thomas
> >
> > There are a lot of things to investigate:
> >
> > 1) does your JTAG hardware/driver support multiple processors?
> > 2) Can you target the processors individually?
> > 3) I know that TI suggest signal buffering, but have you tried
without
> this?
> > 4) Have TI made any comments?
> >
> > I know of people in the UK who could assist you (we're probably
not the
> best
> > match to your requirements!). If you would like some details, then
drop
> me a
> > line.
> >
> > Best of luck.
> >
> > Graeme.
>
> Thomas,
>
> please find some further comments on CCS multi-processor debugging:
> {
> With the C:\ti\cc\bin\compjtag.exe utility, it is possible to generate a
> board *.dat-file from
> text based board configuration files (*.cfg) - CCS uses the *.dat-file
to
> configure and init
> the JTAG chain. Normally, the *.dat is stored in the subdirectory
> C:\ti\cc\bin\BrdDat\.
> Upon exitting CC Setup, the CompJTAG utility is run and creates the
*.dat
> file used
> as a board definition file by selecting the option to "specify
custom
> board data file" from within
> CC_Setup. This is also explained in the Code ComposerStudio Setup Help
> Utility.
> The CCS users guide can be downloaded from
>
> Please notice that the order of the JTAG components listed in the *.cfg
> files or in the CCS setup
> utility
> is the opposite order of the physical connection (e.g. the device
> connected to TDO of the emulator
> header needs to be the first device in the list). A board config *.CFG
> file for a PCB board with
> three JTAG components (e.g. a DSP and 2 CPLDs) in the following scan
> chain:
>
> Emulator
TDI=>TDI-DSP-TDO=>TDI-CPLD1-TDO=>TDI-CPLD2-TDO=>Emulator TDO
>
> should therefore look like as follows:
>
> "CPLD2" BYPASS05
> "CPLD1" BYPASS05
> "DSP" TI320C5xx
>
> If you run COMPJTAG then you get a new BOARD.DAT file but some Code
> Composer versions
> may still not start without error messages. This problem can be solved
by
> using small caps letters
> when defining the processor names (dsp instead of DSP) in the Code
> Composer Setup:
>
> "cpld2" BYPASS05
> "cpld1" BYPASS05
> "dsp" TI320C5xx
>
> An example of an *.dat file can be found under C:\ti\c6000\evm6x\lib
>
> Good luck,
> Phil
> --
> ---------------------------
> Phil Alder
> Field Application Engineer
> DSPecialists GmbH
> Germany www.DSPecialists.de
> ---------------------------
> DSPecialists Making the Impossible Work !
>
>
> To Join: Send an email to
>
> To Post: Send an email to
>
> To Leave: Send an email to
>
> Archives: http://www.egroups.com/group/c6x
>
> Other Groups: http://www.dsprelated.com
>
Reply by Phil Alder●December 12, 20002000-12-12
Graeme Parker wrote:
> Hi Thomas
>
> There are a lot of things to investigate:
>
> 1) does your JTAG hardware/driver support multiple processors?
> 2) Can you target the processors individually?
> 3) I know that TI suggest signal buffering, but have you tried without
this?
> 4) Have TI made any comments?
>
> I know of people in the UK who could assist you (we're probably not
the best
> match to your requirements!). If you would like some details, then drop me
a
> line.
>
> Best of luck.
>
> Graeme.
Thomas,
please find some further comments on CCS multi-processor debugging:
{
With the C:\ti\cc\bin\compjtag.exe utility, it is possible to generate a
board
*.dat-file from
text based board configuration files (*.cfg) - CCS uses the *.dat-file to
configure and init
the JTAG chain. Normally, the *.dat is stored in the subdirectory
C:\ti\cc\bin\BrdDat\.
Upon exitting CC Setup, the CompJTAG utility is run and creates the *.dat
file
used
as a board definition file by selecting the option to "specify custom board
data
file" from within
CC_Setup. This is also explained in the Code ComposerStudio Setup Help
Utility.
The CCS users guide can be downloaded from
Please notice that the order of the JTAG components listed in the *.cfg files
or
in the CCS setup
utility
is the opposite order of the physical connection (e.g. the device connected
to
TDO of the emulator
header needs to be the first device in the list). A board config *.CFG file
for
a PCB board with
three JTAG components (e.g. a DSP and 2 CPLDs) in the following scan chain:
If you run COMPJTAG then you get a new BOARD.DAT file but some Code Composer
versions
may still not start without error messages. This problem can be solved by
using
small caps letters
when defining the processor names (dsp instead of DSP) in the Code Composer
Setup:
"cpld2" BYPASS05
"cpld1" BYPASS05
"dsp" TI320C5xx
An example of an *.dat file can be found under C:\ti\c6000\evm6x\lib
Good luck,
Phil
--
---------------------------
Phil Alder
Field Application Engineer
DSPecialists GmbH
Germany www.DSPecialists.de
---------------------------
DSPecialists Making the Impossible Work !
Reply by Graeme Parker●December 12, 20002000-12-12
Hi Thomas
There are a lot of things to investigate:
1) does your JTAG hardware/driver support multiple processors?
2) Can you target the processors individually?
3) I know that TI suggest signal buffering, but have you tried without this?
4) Have TI made any comments?
I know of people in the UK who could assist you (we're probably not the
best
match to your requirements!). If you would like some details, then drop me a
line.
Best of luck.
Graeme.
-----Original Message-----
From: Thomas Schwere [mailto:]
Sent: 11 December 2000 10:39
To:
Subject: [c6x] Debugging four TMS320C6201
Hi all
We developped a board with four C6201 in the JTAG chain and want to
debug them with the XDS510 Emulator and Code Composer Studio Debug Tools
1.20. The DSPs are the only devices in the JTAG chain. The Emulator is
connected as in the TI application note SPRA439, figure 5 with signal
buffering.
In the CCS Setup we define four DSPs, but when we start CCS, the error
message "Can't initilaze target dsp..." appears. All the other
settings
are correct, because with only one DSP in the chain it works properly.
Does anybody have experience with this stuff or did encountered similar
problems?
Thanks in advance.
Thomas
--
//\\\\
| ~ ~ |
( O O )
___________________________________oOOo______( )_____oOOo_______
Reply by Thomas Schwere●December 11, 20002000-12-11
Hi all
We developped a board with four C6201 in the JTAG chain and want to
debug them with the XDS510 Emulator and Code Composer Studio Debug Tools
1.20. The DSPs are the only devices in the JTAG chain. The Emulator is
connected as in the TI application note SPRA439, figure 5 with signal
buffering.
In the CCS Setup we define four DSPs, but when we start CCS, the error
message "Can't initilaze target dsp..." appears. All the other
settings
are correct, because with only one DSP in the chain it works properly.
Does anybody have experience with this stuff or did encountered similar
problems?
Thanks in advance.
Thomas
--
//\\\\
| ~ ~ |
( O O )
___________________________________oOOo______( )_____oOOo_______