PADK with XDS510 USB emulator

Hi Randy,

       As you mentioned in the previous post i have tried all the possibilities and from the above post you can find the detailed information about my problem, And my CCS version is 

CCS v 3.3.38.2

Integrated Development 5.98.0.219

Code generation Tools v4.1.3

Board revision (00.00.00)

Target silicon revision (00.00.00)

I have downloaded the XDS 510 emulator driver from Spectrum Digital site.

Hi ,

        Could any one reply for my post, Its 7 days old but not even a single reply for my post, Kindly help me to fix this issue....

Hello,

shan said:

CCS v 3.3.38.2

This version of CCS 3.3 is very old. Could you upgrade your CCS install to the latest CCS 3.3 service release (SR12)?

Thanks

ki

Hello,

we have the same problem with the JTAG connection to a new bought PADK with the XDS510 USB PLUS and a problem to use the USB connection.

We use the SR12 of CCS3.3 with

CCS Version 3.3.82.13
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)

and the error message while trying 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.

We have two other PADKs and there occur no problems while connecting with the same PC in the same way.

Another problem is the USB interface on the PADK. In the device manager the PADK appears with Vendor ID 0x04B4 and PID 0x8613. But the driver (ltpadk_usb.inf) uses Vendor ID 0x1420 and PID 0x9641 (firmware not loaded) or PID 0x1641 (real or 2nd stage driver). The two other Boards work fine with correct IDs.

I know a third department who bought new boards with the same problems. So, has the hardware changed in an important way? Are there some updates of drivers?

Kind regards

Stefan

Hi,

here is an update.

I tested the JTAG connection with CCS 4.1 and the XDS510 USB PLUS but the problem still exists. The behaviour while connecting and the error message is the same. The two elder PADKs work fine but I can not connect to the new one.

Regards

Stefan

Stefan,

Based on the emulator error message you sent, it looks like that two things are contributing for this:

- Lyrtech updated the PADK with a new device revision (maybe C6727B);

- Either CCS debugger or Spectrum Digital's emulation drivers do not recognize this device revision;

Unfortunately I don't have a new PADK and, just like you, the old PADK works just fine with the XDS510USB from Spectrum Digital. 

Therefore I suggest you to contact Lyrtech and ask what changed in the new board revision (this will also help with the USB interface issue you mentioned before). I would ask Spectrum Digital to see what may be needed to support the C6727B (if Lyrtech confirms they are using this device revision on their boards).

In the meantime I will check if there is any limitation in the CCS debugger and/or drivers.

Hope this helps,

Rafael

Hi Rafael,

Thanks for your answer.

All of our DSPs are C6727B at 350MHz unfortunately . The Part # and Details of the DSPs are as followed:

/* Work fine */
TMS320C6727BZDH C12-7BA45LW GI
TMS320C6727BZDH C12-83A7IJW GI
/* DSP on PADK with JTAG Connection problem */
TMS320C6727BZDH C12-05ANOCW GI

This is the reason why it is amazing. The hardware seems to be the same but it does not work. Therefore I assume the general support of the C6727B by the emulator is given.

I contacted Lyrtech but still waiting for answer. I agree that the USB is a Lyrtech problem and hope they can solve it. If I get an answer I inform you especially about their statement to the JTAG problem.

Do you have additional idea?

Kind regards

Stefan

Stefan,

Indeed it seems the emulator support is ok. Therefore one additional suggestion is (maybe) a somewhat flaky PCB routing that is causing data to be invalidated during JTAG communications. Can you try to reduce the speed of the JTAG clock as shown in questions 4.1. and 4.2 of the Spectrum Digital's support page?

http://support.spectrumdigital.com/guides/JTAG_Emulator_guide/

I don't recall seeing a bad device ID caused by this, but I surely have seen issues caused by high JTAG speeds.

Hope this helps,

Rafael

Hi Stefan,

I am also still struggling  with this, Even i didnt get any response from LYRTECH, Have you tried with USB, Weather it works for you, For me When I select that ltpadk_usb.inf file it shows that (The specified location does not contain ant information about your Hardware), and if you get any answers please let me know

regards,

Hello shan,

For the installation of the USB driver I tested a workaround with a modified ltpadk_usb.inf.

The buggy USB device of the PADK does not match with the Vendor ID of the Lyrtech driver which I described in a reply above. However the installation of the device driver take place in two steps. In a first step a firmware is downloading to the USB controller. Then the controller get another Vendor ID and PID and initialise a second register process.

So replace the IDs of the device of the first boot step with the IDs from the information of the device manager. Then the basic firmware is loaded and the device is register in the second step with the IDs from Lyrtech which is used by the driver and the Lyrtech applications.

These lines are chanced in the ltpadk_usb.inf by me:

; Models section:
[LYT.Lyrtech_PADK_USB]
%LYT.ltpadk.drv.Desc%=ltpadk.drv, USB\VID_1420&PID_1641 ; Lyrtech, PADK
;%LYT.ltpadk.ldr.Desc%=ltpadk.ldr, USB\VID_1420&PID_9641 ; firmware not loaded, 0xC0 type EEPROM
%LYT.ltpadk.ldr.Desc%=ltpadk.ldr, USB\VID_04B4&PID_8613 ; generic cypress chip IDs at EEPROM errors

The IDs are from the device details:

The modified ltpadk_usb.inf you have to use in addition to the *.sys is:

; ltpadk_usb.inf
;
; Lyrtech PADK
;
; Driver Installation for WIN98/WIN2000
;
; LYRtech Inc., mar/17/2005
;


[Version]
Signature="$CHICAGO$"
ClassGUID={36fc9e60-c465-11cf-8056-444553540000}
Class=USB
Provider=%LYT%
DriverVer=03/17/2005,1.0.00.1   ; mm/dd/yyyy,x.y.v.z

; Manufacturer section:
[Manufacturer]
%LYT%=LYT.Lyrtech_PADK_USB

; Models section:
[LYT.Lyrtech_PADK_USB]
%LYT.ltpadk.drv.Desc%=ltpadk.drv, USB\VID_1420&PID_1641 ; Lyrtech, PADK
;%LYT.ltpadk.ldr.Desc%=ltpadk.ldr, USB\VID_1420&PID_9641 ; firmware not loaded, 0xC0 type EEPROM
%LYT.ltpadk.ldr.Desc%=ltpadk.ldr, USB\VID_04B4&PID_8613 ; generic cypress chip IDs at EEPROM errors


; DDInstall section:
[ltpadk.drv]
CopyFiles=ltpadk.drv.Files.Sys, ltpadk.Files.Inf
AddReg=ltpadk.AddReg

[ltpadk.ldr]
CopyFiles=ltpadk.ldr.Files.Sys, ltpadk.Files.Inf
AddReg=ltpadk.AddReg

[DestinationDirs]
ltpadk.drv.Files.Sys = 12	; drivers
ltpadk.ldr.Files.Sys = 12	; drivers
ltpadk.Files.Inf = 17	   ; INF

[ltpadk.drv.Services]
Addservice = ltpadk, 0x00000002, ltpadk.drv.AddService

[ltpadk.ldr.Services]
Addservice = ltpadkLdr, 0x00000002, ltpadk.ldr.AddService

[ltpadk.drv.AddService]
DisplayName    = %LYT.ltpadk.drv.Desc%
ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
StartType      = 2                  ; SERVICE_AUTO_START
ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
ServiceBinary  = %12%\ltpadk_usb.sys
LoadOrderGroup = Base

[ltpadk.ldr.AddService]
DisplayName    = %LYT.ltpadk.ldr.Desc%
ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER
StartType      = 2                  ; SERVICE_AUTO_START
ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL
ServiceBinary  = %12%\ltpadk_usbldr.sys
LoadOrderGroup = Base

[ltpadk.AddReg]
;???
;HKR,,DevLoader,,*ntkern
;HKR,,NTMPDriver,,stcrusb.sys

[ltpadk.drv.Files.Sys]
ltpadk_usb.sys

[ltpadk.ldr.Files.Sys]
ltpadk_usbldr.sys

[ltpadk.Files.Inf]
; do not copy...MSA ltpadk_usb.inf

;---------------------------------------------------------------;

[Strings]
LYT="LYRtech Inc."
; Localizable string:
LYT.ltpadk.drv.Desc="Lyrtech PADK - USB"
LYT.ltpadk.ldr.Desc="Lyrtech PADK - USB Firmware Loader, 0xC0 type EEPROM"

I installed the buggy board with this driver but I did not test it with applications from Lyrtech.

Hope this is usefull,

Stefan

Update 2011-02-09:

This post is marked as 'This question is answered'. So I wrote a new post,  http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/92608/321917.aspx#321917, becaurse the problem ist still unresolved.

Hi shan,

I tested the buggy PADK with the modified driver and the Lyrtech USB loader. It does not work togehter!

If I am downloading a DSP application the progress stops and fails. It fails not while connecting to USB but loading the app. to the DSP. Take a look to the screenshot above. The address where the progress stops is 0x10001C00 for most of the applications. The beginning of the IRAM. For a few applications the address is varying e.g. PollingUsbLpback.out from the usbbenchmark at address 0x10005BC0.

However the (modified) USB driver should work. The UsbFreeRxTxConsole.exe of the host starts, create pipes and submit a few date till the buffer of the USB controller is full.

So, there is still a problem with the DSP chip while loading by USB in addition to the JTAG problem.

Regards,

Stefan

Just FYI for others...

Indeed there seems to be an issue with the newer PADK boards. Check the last post from Stefan on the forum thread below:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/92608.aspx

Regards,

Rafael