JTAG link connection to the PADK fails

Stefan Hermanutz

Hello,

We get an error while trying to connect to the PADK with the C6727B@350MHz. This is our own post to the still unresolved problem which I described in the thread of shan.

The situation is as followed. We bought a new PADK from Lyrtech and we can not establish a connection to the board. The system setup and the error is described below.

We had two elder PADKs which work fine in the same setup and which we use in the same way. The boards seems like to be identical. This is the reason why it is strange.

The error message while trying to connect is:

Error connecting to the target:
Error 0x80000200/-1063
Fatal Error during: OCS,
Bad Target Silicon Revision Number
Please check your multi-processor configuration.
The number of devices in the JTAG scan path
must be correct for the silicon revision to be read.
Or, you may have selected the wrong DSP device driver.

The system setup is:

Code Composer Studio:
CCS Version 3.3.82.13 (SR12)
Integrated Development 5.98.0.393
BIOS 5.31.02
Code generation Tools v6.0.8
Board revision (00.00.00)
Target silicon revision (00.00.00)

CCS Setup:
C672x XDS510USB Emulator with sdgo672xUSB.dvr Rev.: 05.29.05
GEL file: padk_350MHz.gel

JTAG Emulator:
Spectrum Digital XDS510 USB PLUS
SD driver package 3.3.30 + Patch (22-Sept-2010)

DSPs of the three PADKs:
/* Work fine */
TMS320C6727BZDH C12-7BA45LW GI
TMS320C6727BZDH C12-83A7IJW GI
/* PADK with JTAG connection problem */
TMS320C6727BZDH C12-05ANOCW GI

Tested with:
Windows 7 and Windows XP
CCS 3.1 and CCS 4.1
different JTAG clocks

Have anyone an approach? We also send a support query to Lyrtech which is in process now.

Kind regards,

Stefan

over 14 years ago

0 JohnS over 14 years ago

TI__Guru**** 162255 points

Stefan,

It seems like something may be wrong with the device. If you run the "test target connection" action from within SDConfig does it give you the same result for all 3 PADKs?

Regards,

John

0 Stefan Hermanutz over 14 years ago in reply to JohnS

Prodigy 160 points

Hello John,

If I run target connection test but all boards show identical outputs unfortunately:

** Checking for a valid emulator/eZdsp
$$ You are connected to:
$$ EmuProductName=XDS510USB
$$ EmuPortAddr=0x510
$$ EmuPortMode=USB
$$ ProductId=510
$$ ProductVersion=86

** Checking emulator/eZdsp scan connection
** Emulator Test **
$$ EmuProductName=XDS510USB
$$ EmuPortAddr=0x510
$$ EmuPortMode=USB
$$ ProductId=510
$$ ProductVersion=86
** Emulator Scan Test
-- Found JTAG IR length of 54
-- Found 2 JTAG device(s) in the scan chain

There is another problem to access the DSP/PADK furthermore. This relates the USB loader. If I try to download an application, described in this reply, it fails while writing to the address of the IRAM. It seems for me there is a relation of the problems.

Regards,

Stefan

0 Stefan Hermanutz over 14 years ago in reply to Stefan Hermanutz

Prodigy 160 points

Hi there,

I close this post!

The service of Lyrtech came to the conclusion that the USB EEPROM is in trouble (This is another problem in addition to the JTAG problem). I do not understand the relation between these problems, but "The PADK must be reprogrammed".

However we gave the PADK back to the seller.

Stefan

0 Stefan Hermanutz over 14 years ago in reply to Stefan Hermanutz

Prodigy 160 points

Hi there,

FYI. Lyrtrech found out and realised that the problems of the PADK are not solved with only a reprogramming of the USB EEPROM. There is also a problem with the FPGA which has to be reprogrammed.

Stefan

0 desouza over 14 years ago in reply to Stefan Hermanutz

TI__Guru**** 171004 points

Stefan,

Thank you for reporting this; it will surely help other developers in the future!

Regards,

Rafael

Code Composer Studio™︎

Code Composer Studio forum

JTAG link connection to the PADK fails