Forums

problem connecting to DM640 board using CCS

Started by AK April 12, 2006
Hello experts,

I am listing below a problem that I am stuck with for 4-5 days now. Could
you please go through it and give suggestions or lead me to someone in your
contact list who might have experience in related issues?

Our target board is based on the DM640 and we have designed its JTAG
circuitry exactly as in the DM642 EVM.

We are using the 14- pin JTAG connector connected to a XDS510PP parallel
port emulator. When we tried to detect

the JTAG Device using SDConfig Utility, it says:

** Checking for a valid emulator/eZdsp

$$ You are connected to:

$$ EmuProductName=XDS510PP_PLUS

$$ EmuPortAddr=0x378

$$ EmuPortMode=SPP8

$$ ProductId

$$ ProductVersion

** Checking emulator/eZdsp scan connection

** Emulator Test **

$$ EmuProductName=XDS510PP_PLUS

$$ EmuPortAddr=0x378

$$ EmuPortMode=SPP8

$$ ProductId

$$ ProductVersion

** Emulator Scan Test

-- Found JTAG IR length of 38

* Found 1 JTAG device(s) in the scan chain

Furthermore, when we try to run the standard SDConfig Diagnostics, we are
able

To run thousands of test loops without error, both with incremental and user
defined

Test patterns. We have even tried probing the JTAG signals during these
tests, and

They are clean ( no ringing, loading), and exactly match the signals seen
while running

The same tests on a working DM642 EVM we possess.

However, when I try to connect to the target using CCS 3.1 Platinum edition
with the

Custom setup for the XDS510PP emulator and c64XX DSP and a custom GEL file

Containing the details For the DM640 target, we get the follwing error

Error connecting to the target:

Error 0x80000240/-1156 ( Sometimes the error
code is 0x80000260/- 1156)

Fatal Error during: Initialization, OCS,

Invalid data was scanned by the emulation controller.

Verify the board setup to make sure the scan chain is properly

defined.

If the setup is correct, then RESET EMULATOR. This will disconnect each

target from the emulator. The targets should then be power cycled

or hard reset followed by an emureset and reconnect to each target.

Sequence ID: 0

Error Code: -1156

Error Class: 0x80000240

I/O Port = 378

Board Name: DM640 board

Cpu Name: DSP_C64xx

Abort: Close Code Composer Studio.

Retry: Try to connect to the target again.

Cancel: Remain disconnected from the target

Diagnostic: Run diagnostic utility.

Please note that I have tried out all listed versions of C6X drivers from
Spectrum

Digital. I have also tried out both CCS 3.0 & CCS 3.1. Moreover, I have
tried commenting

Out all functions in the GEL file that run OnConnect(). ( eg. Init-emif())

I want to ask two questions:

1. Does the fact that board passes all the SDConfig diagnostics rule

out any hardware or signal integrity issues?

2. Can you possible give me hints to debug this CCS connection?

Any suggestions will be appreciated.

Thanks,

Anand Krishnan
Anand-

When SDConfig (JTAG scan test) works but CCS will not connect, some
typical problems are;

-DSP is being held in Reset; has to be out
of Reset *before* you open CCS

-JTAG signals are marginal; they work fine for simple JTAG
command sequences used by SDConfig, but something goes
wrong (maybe TCK) when CCS is in action

Did you try the xdsprobe.exe utility? This is a more rigorous JTAG test
than SDConfig.

-Jeff
> I am listing below a problem that I am stuck with for 4-5 days now. Could
> you please go through it and give suggestions or lead me to someone in
> your
> contact list who might have experience in related issues?
> Our target board is based on the DM640 and we have designed its JTAG
> circuitry exactly as in the DM642 EVM.
>
> We are using the 14- pin JTAG connector connected to a XDS510PP parallel
> port emulator. When we tried to detect
>
> the JTAG Device using SDConfig Utility, it says:
>
> ** Checking for a valid emulator/eZdsp
>
> $$ You are connected to:
>
> $$ EmuProductName=XDS510PP_PLUS
>
> $$ EmuPortAddr=0x378
>
> $$ EmuPortMode=SPP8
>
> $$ ProductId
>
> $$ ProductVersion
>
> ** Checking emulator/eZdsp scan connection
>
> ** Emulator Test **
>
> $$ EmuProductName=XDS510PP_PLUS
>
> $$ EmuPortAddr=0x378
>
> $$ EmuPortMode=SPP8
>
> $$ ProductId
>
> $$ ProductVersion
>
> ** Emulator Scan Test
>
> -- Found JTAG IR length of 38
>
> * Found 1 JTAG device(s) in the scan chain
>
> Furthermore, when we try to run the standard SDConfig Diagnostics, we are
> able
>
> To run thousands of test loops without error, both with incremental and
> user
> defined
>
> Test patterns. We have even tried probing the JTAG signals during these
> tests, and
>
> They are clean ( no ringing, loading), and exactly match the signals seen
> while running
>
> The same tests on a working DM642 EVM we possess.
> However, when I try to connect to the target using CCS 3.1 Platinum
> edition with the
>
> Custom setup for the XDS510PP emulator and c64XX DSP and a custom GEL
> file
>
> Containing the details For the DM640 target, we get the follwing error
>
> Error connecting to the target:
>
> Error 0x80000240/-1156 ( Sometimes the error
> code is 0x80000260/- 1156)
>
> Fatal Error during: Initialization, OCS,
>
> Invalid data was scanned by the emulation controller.
>
> Verify the board setup to make sure the scan chain is properly
> defined.
>
> If the setup is correct, then RESET EMULATOR. This will disconnect each
> target from the emulator. The targets should then be power cycled
> or hard reset followed by an emureset and reconnect to each target.
> Sequence ID: 0
> Error Code: -1156
> Error Class: 0x80000240
>
> I/O Port = 378
> Board Name: DM640 board
> Cpu Name: DSP_C64xx
>
> Abort: Close Code Composer Studio.
> Retry: Try to connect to the target again.
> Cancel: Remain disconnected from the target
> Diagnostic: Run diagnostic utility.
>
> Please note that I have tried out all listed versions of C6X drivers from
> Spectrum
>
> Digital. I have also tried out both CCS 3.0 & CCS 3.1. Moreover, I have
> tried commenting
>
> Out all functions in the GEL file that run OnConnect(). ( eg.
> Init-emif())
>
> I want to ask two questions:
>
> 1. Does the fact that board passes all the SDConfig diagnostics rule
>
> out any hardware or signal integrity issues?
>
> 2. Can you possible give me hints to debug this CCS connection?
>
> Any suggestions will be appreciated.
>
> Thanks,
>
> Anand Krishnan
Dear Everyone,

Thanks to Jeff for the suggestions.

My connection problem was traced back to a surprising assembly mistake. Due
to not populating a component, the PLL_VDD pin on the DM640 that powers the
PLL circuitry was not getting power. This means that though the DSP was
seeing the 33MHz signal from my oscillator, it was not seeing the 400MHz
clock inside. Despite this, all emulator diagnostics ( sending & receiving
data) were working and the scan chain was being correctly detected.

I guess the JTAG circuitry is clocked entirely from the external clock and
Was hence working OK but CCS connect probably requires the chip to access
its internal memory or something.

Anyway, it had me stumped for 5 days & I don't know whether to laugh or cry
now that it's traced to something so trivial:-)

Thanks!
Anand
-----Original Message-----
From: c... [mailto:c...] On Behalf Of Jeff
Brower
Sent: Wednesday, April 12, 2006 8:54 PM
To: Anand Krishnan
Cc: c...
Subject: Re: [c6x] problem connecting to DM640 board using CCS

Anand-

When SDConfig (JTAG scan test) works but CCS will not connect, some
typical problems are;

-DSP is being held in Reset; has to be out
of Reset *before* you open CCS

-JTAG signals are marginal; they work fine for simple JTAG
command sequences used by SDConfig, but something goes
wrong (maybe TCK) when CCS is in action

Did you try the xdsprobe.exe utility? This is a more rigorous JTAG test
than SDConfig.

-Jeff
> I am listing below a problem that I am stuck with for 4-5 days now. Could
> you please go through it and give suggestions or lead me to someone in
> your
> contact list who might have experience in related issues?
> Our target board is based on the DM640 and we have designed its JTAG
> circuitry exactly as in the DM642 EVM.
>
> We are using the 14- pin JTAG connector connected to a XDS510PP parallel
> port emulator. When we tried to detect
>
> the JTAG Device using SDConfig Utility, it says:
>
> ** Checking for a valid emulator/eZdsp
>
> $$ You are connected to:
>
> $$ EmuProductName=XDS510PP_PLUS
>
> $$ EmuPortAddr=0x378
>
> $$ EmuPortMode=SPP8
>
> $$ ProductId
>
> $$ ProductVersion
>
> ** Checking emulator/eZdsp scan connection
>
> ** Emulator Test **
>
> $$ EmuProductName=XDS510PP_PLUS
>
> $$ EmuPortAddr=0x378
>
> $$ EmuPortMode=SPP8
>
> $$ ProductId
>
> $$ ProductVersion
>
> ** Emulator Scan Test
>
> -- Found JTAG IR length of 38
>
> * Found 1 JTAG device(s) in the scan chain
>
> Furthermore, when we try to run the standard SDConfig Diagnostics, we are
> able
>
> To run thousands of test loops without error, both with incremental and
> user
> defined
>
> Test patterns. We have even tried probing the JTAG signals during these
> tests, and
>
> They are clean ( no ringing, loading), and exactly match the signals seen
> while running
>
> The same tests on a working DM642 EVM we possess.
> However, when I try to connect to the target using CCS 3.1 Platinum
> edition with the
>
> Custom setup for the XDS510PP emulator and c64XX DSP and a custom GEL
> file
>
> Containing the details For the DM640 target, we get the follwing error
>
> Error connecting to the target:
>
> Error 0x80000240/-1156 ( Sometimes the error
> code is 0x80000260/- 1156)
>
> Fatal Error during: Initialization, OCS,
>
> Invalid data was scanned by the emulation controller.
>
> Verify the board setup to make sure the scan chain is properly
> defined.
>
> If the setup is correct, then RESET EMULATOR. This will disconnect each
> target from the emulator. The targets should then be power cycled
> or hard reset followed by an emureset and reconnect to each target.
> Sequence ID: 0
> Error Code: -1156
> Error Class: 0x80000240
>
> I/O Port = 378
> Board Name: DM640 board
> Cpu Name: DSP_C64xx
>
> Abort: Close Code Composer Studio.
> Retry: Try to connect to the target again.
> Cancel: Remain disconnected from the target
> Diagnostic: Run diagnostic utility.
>
> Please note that I have tried out all listed versions of C6X drivers from
> Spectrum
>
> Digital. I have also tried out both CCS 3.0 & CCS 3.1. Moreover, I have
> tried commenting
>
> Out all functions in the GEL file that run OnConnect(). ( eg.
> Init-emif())
>
> I want to ask two questions:
>
> 1. Does the fact that board passes all the SDConfig diagnostics rule
>
> out any hardware or signal integrity issues?
>
> 2. Can you possible give me hints to debug this CCS connection?
>
> Any suggestions will be appreciated.
>
> Thanks,
>
> Anand Krishnan
Anand,

I apologize for the earlier post. I was reading my
email while on a phone call and did not see your group
post. Good work.

mikedunn

--- AK wrote:

> Dear Everyone,
>
> Thanks to Jeff for the suggestions.
>
> My connection problem was traced back to a
> surprising assembly mistake. Due
> to not populating a component, the PLL_VDD pin on
> the DM640 that powers the
> PLL circuitry was not getting power. This means that
> though the DSP was
> seeing the 33MHz signal from my oscillator, it was
> not seeing the 400MHz
> clock inside. Despite this, all emulator diagnostics
> ( sending & receiving
> data) were working and the scan chain was being
> correctly detected.
>
> I guess the JTAG circuitry is clocked entirely from
> the external clock and
> Was hence working OK but CCS connect probably
> requires the chip to access
> its internal memory or something.
>
> Anyway, it had me stumped for 5 days & I don't know
> whether to laugh or cry
> now that it's traced to something so trivial:-)
>
> Thanks!
> Anand
> -----Original Message-----
> From: c...
> [mailto:c...] On Behalf Of Jeff
> Brower
> Sent: Wednesday, April 12, 2006 8:54 PM
> To: Anand Krishnan
> Cc: c...
> Subject: Re: [c6x] problem connecting to DM640 board
> using CCS
>
> Anand-
>
> When SDConfig (JTAG scan test) works but CCS will
> not connect, some
> typical problems are;
>
> -DSP is being held in Reset; has to be out
> of Reset *before* you open CCS
>
> -JTAG signals are marginal; they work fine for
> simple JTAG
> command sequences used by SDConfig, but something
> goes
> wrong (maybe TCK) when CCS is in action
>
> Did you try the xdsprobe.exe utility? This is a
> more rigorous JTAG test
> than SDConfig.
>
> -Jeff
> > I am listing below a problem that I am stuck with
> for 4-5 days now. Could
> > you please go through it and give suggestions or
> lead me to someone in
> > your
> > contact list who might have experience in related
> issues?
> >
> >
> > Our target board is based on the DM640 and we have
> designed its JTAG
> > circuitry exactly as in the DM642 EVM.
> >
> > We are using the 14- pin JTAG connector connected
> to a XDS510PP parallel
> > port emulator. When we tried to detect
> >
> > the JTAG Device using SDConfig Utility, it says:
> >
> > ** Checking for a valid emulator/eZdsp
> >
> >
> >
> > $$ You are connected to:
> >
> > $$ EmuProductName=XDS510PP_PLUS
> >
> > $$ EmuPortAddr=0x378
> >
> > $$ EmuPortMode=SPP8
> >
> > $$ ProductId
> >
> > $$ ProductVersion
> >
> > ** Checking emulator/eZdsp scan connection
> >
> >
> >
> > ** Emulator Test **
> >
> >
> >
> > $$ EmuProductName=XDS510PP_PLUS
> >
> > $$ EmuPortAddr=0x378
> >
> > $$ EmuPortMode=SPP8
> >
> > $$ ProductId
> >
> > $$ ProductVersion
> >
> > ** Emulator Scan Test
> >
> > -- Found JTAG IR length of 38
> >
> > * Found 1 JTAG device(s) in the scan chain
> >
> > Furthermore, when we try to run the standard
> SDConfig Diagnostics, we are
> > able
> >
> > To run thousands of test loops without error, both
> with incremental and
> > user
> > defined
> >
> > Test patterns. We have even tried probing the JTAG
> signals during these
> > tests, and
> >
> > They are clean ( no ringing, loading), and exactly
> match the signals seen
> > while running
> >
> > The same tests on a working DM642 EVM we possess.
> >
> >
> > However, when I try to connect to the target using
> CCS 3.1 Platinum
> > edition with the
> >
> > Custom setup for the XDS510PP emulator and c64XX
> DSP and a custom GEL
> > file
> >
> > Containing the details For the DM640 target, we
> get the follwing error
> >
> > Error connecting to the target:
> >
> > Error 0x80000240/-1156
> ( Sometimes the error
> > code is 0x80000260/- 1156)
> >
> > Fatal Error during: Initialization, OCS,
> >
> > Invalid data was scanned by the emulation
> controller.
> >
> > Verify the board setup to make sure the scan chain
> is properly
> > defined.
> >
> > If the setup is correct, then RESET EMULATOR.
> This will disconnect each
> > target from the emulator. The targets should then
> be power cycled
> > or hard reset followed by an emureset and
> reconnect to each target.
> >
> >
> > Sequence ID: 0
> > Error Code: -1156
> > Error Class: 0x80000240
> >
> > I/O Port = 378
> > Board Name: DM640 board
> > Cpu Name: DSP_C64xx
> >
> > Abort: Close Code Composer Studio.
> > Retry: Try to connect to the target
> again.
> > Cancel: Remain disconnected from the
> target
> > Diagnostic: Run diagnostic utility.
> >
> > Please note that I have tried out all listed
> versions of C6X drivers from
> > Spectrum
> >
> > Digital. I have also tried out both CCS 3.0 & CCS
> 3.1. Moreover, I have
> > tried commenting
> >
> > Out all functions in the GEL file that run
> OnConnect(). ( eg.
>
=== message truncated ==