This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Which XDS510 driver do I install for CCS?

Other Parts Discussed in Thread: TMS320VC5506

Hello,

Due to budgetary constraints, my client purchased an XDS510 USB 2 device on eBay.  It came with no documentation other than a CD-R with several conflicting files.  I was able to get this XDS510 working last year with our custom board on a borrowed PC running CCS3, but I did not take notes on which driver was successful, and now I do not have access to that machine any more.  We're now trying out CCSv4 with the XDS100 on our own Window XP machine, but I find it slow and buggy, and would like to try the XDS510 again, with CCS3 and CCSv4, if possible.

Can anyone help me identify this XDS510 hardware?

The USB VendorID is 0x0B1E "Electronic Warfare Assoc., Inc. (EWA)", the ProductID is 6, and the Device Version Number is 2.0.0 (0x0200)

The circuit board says "TI DSP Emulator" XDS510-usb2.0 KG0901-12Y180K and has chips including ACT8990, Cypress CY7C68013A-100AXC, Lattice B832KK08 and a 24 MHz crystal, among other parts.

My problem is that I can't seem to figure out which drivers to install, since there are about 3 different drivers on the CD-R.  If I knew for sure who made this hardware, and which driver was appropriate, then I'd probably be able to get it working.  Last year, I struggled with strange error messages and was working with an unproven TMS320 board of my own design, but eventually got it working.  If only I had realized that I would of course forget which driver and settings worked, then I would have taken careful notes.

P.S.  Another issue is that I "improved" our TMS320VC5506 board by adding pull-ups on the JTAG header, so I cannot even be certain that I didn't make things worse.  Obviously, narrowing down the possibilities by removing variables is going to be key.  I still have the old boards, though, if that turns out to be the issue.

  • This product sounds like it could be a a cloned XDS510. Many of the products on ebay are clones of legitamate XDS vendors.

    You should contact your vendor and get updated drivers. They should also be able to help you through setup/configuration.

     

  • Thanks for the reply.  I was afraid this might be a clone.  Seeing the TI logo on a box that doesn't come from TI is a bad sign (unless all of the third-party emulators have the TI logo).

    There is no vendor, though, since this was basically an individual to individual eBay purchase.  I'll try to find out whether the seller is still available on eBay (and speaks English or we can find a translator).  Much of the documentation was in Chinese, but otherwise looks identical to TI documentation.

    If only the price difference were not a couple of orders of magnitude more, then this cloning would be less of an issue.  Usually, cloned hardware - especially open hardware (see Microchip PICkit) - is only about $5 cheaper from the clones than from companies that are mainstream.  Sorry for the rant.  I'll see what I can find out from the source.

  • Brian Willoughby said:
    The USB VendorID is 0x0B1E "Electronic Warfare Assoc., Inc. (EWA)"

    I think that is Blackhawk. That is what my Virtual Machine sees it as when I connect my Blackhawk emulator to it.

  • Thanks Brian. We've been working to get prices down, and XDS100 is one of the ways. Though not that fast, we have tried to make sure XDS100 is very stable, so I would like to understand what kind of instability you are seeing.

  • As for CCSv4 with XDS100 problems, I often get into a situation where the debugger or whatever the connection is to the XDS100 freezes or crashes the JVM.

    If I start CCSv4 fresh, power up my board, and connect with the debugger, I'm basically 100% guaranteed to be able to download and run my firmware.

    However, if I need to pause, recompile, download the new firmware and run, there's a high probability that CCS will crash or freeze.  The more times I repeat the cycle, the more likely it is to wedge.  If I disconnect, power-cycle my board, then reconnect for firmware download and execution, then it seems to help a little, slightly reducing the chances of a problem.  Even with power-cycling, I still eventually get a freeze or crash.

    When I say 'crash' - I mean that the JVM dies and XP asks if I want to report the crash to Microsoft.  I'm running the latest CCSv4 version.

    When I say 'freeze' - I mean that most of Eclipse seems to be running fine, except that it waits on the debugger/XDS100 connection indefinitely.  Sometimes I can clear this by removing the USB cable from the XDS100, which causes the wait to terminate with an error.  But that is not always a solution, either.

    With CCS3 and XDS510, I had none of these problems.  Technically, my board at that time was missing one or two pull-ups, which I have added on the revised board.  I hope that adding the recommended pull-ups did not actually cause any problems.  The XDS100 sure seems to work the first time, so I assume there are no electrical problems with my board's JTAG interface.

  • Did You try with the original BlackHawk drivers this product? It seem that the VID, PID,REV  are the same:

    ; Blackhawk USB 2.0 JTAG Emulator, rev 2.0 before and after ReNumeration
    %bh2ldrFX2.DeviceDesc% = bh2ldrFX2.Dev, USB\VID_0B1E&PID_0006&REV_0200
    %bh2usbFX2.DeviceDesc% = bh2usb.Dev, USB\VID_0B1E&PID_8006&REV_0200

    I do not think that chinese people did anything else that a perfect copy of a well know emulator...

    Please let me know the result, I am very interested.

    You can mail directly to gsmtransfer at gmail.com too. Thanks!

  • Seems to be working with DBGJTAG.EXE (now I just need to get the license upgraded from Free XDS100 to Demo).

    DBGJTAG.EXE shows the following (I excerpted just the interesting lines):

    This utility has selected an XDS510 class product.

    This utility will operate on port address '0'.

    The emulator adaptor is name 'bhjtag.dll'.

    The emulator adaptor is titled 'A block-mode adapter for Blackhawk USB emulators'.

    The emulator adaptor is version '33.0.0.0'.

    The controller has a version number of '1' (0x0001).

    The controller has an insertion length of '16' (0x0010).

    The local memory has a word capacity of '262144' (0x040000).

     

    The controller type is the production TBC (74ACT8990).

    The software is configured to use only TBC features.

    The software is configured for slower clock operation.

  • Aniway, If you can configure it under CCS4 please let me know. Maybe you have to rename some driver files and use in that way or create some configuration files, I have no idea. But it would be nice, to all us learn how to migrate some older third party hardwares to CCS4...

    Good luck!

  • Yes, I had to quit and restart CCS4 several times to "downgrade" the license from the permanent free XDS100 to the time-limited evaluation, but eventually a dialog appeared from the Blackhawk driver.  I have been able to successfully run my firmware (which, by the way, I could also do in CCS3 with this same JTAG emulator).

    Again, I have no idea whether this is "genuine but used" or "clone" hardware.  I guess it's not genuine, though, since it doesn't say Blackhawk anywhere on the milled aluminum case, nor does it match current photos of Blackhawk products, which appear to have plastic casings.  That's what I get for purchasing on eBay, but I saved our product from an additional $1,370 in expenses!  Our budget is so tight that we also skipped the C55x Evaluation board, but that worked out well because my first board designs worked with the JTAG header and basically cost less than the EVM.