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.

Connecting to C6727 PADK with Spectrum Digital XDS10 plus

Other Parts Discussed in Thread: CCSTUDIO

I am having a problem with being able to connect to the C6727 PADK board, can anyone help? I am a complete newbie, I'm afraid

I do as the Lyrtech doc says, and out of the box, the sdconfig program reports "found JTAG length 54, 2 JTAG devices" as expected.

But the documentation says that the firmware doesn't support C672x, so I should uncomment "#EmuFirmware  = sdxds510usb_v10_1.out".

But when I do this, the PC can't even see the emulator. I think this is because the emulator that actually comes with the PADK bundle is the XDS510 PLUS. So instead, I try setting EmuFirmware to sdxds510usbplus_v12.out. Now, the PC can see the emulator again, but still exactly the same results as  before - only two devices (emu and XDS510USB-PLUS). So I don't think it is seeing the processor (I should see it communicating, right?)

What am I doing wrong? I have tried uncommenting the "DevC6000Ulkd=Key_blah" and that makes no difference.

Does anyone know what JTAG settings I should try?

Thanks if anyone knows it, i am really struggling

  • Which version of CCS are you using? Go to Help->About to find the version.

    Which version of Windows are you using?

    Which SD emulator do you have, exactly?

    It is usually best to follow the instructions that come with the board, especially when the emulator comes with the board, too. Can you try going back to the recommendation from the documentation, and after uncommenting the line as directed, save and reboot. The driver connected to the emulator could need to be reloaded into Windows.

  • I am using v3.3.38.2, shipped with the board, Windows XP SP3, XDS510 USB Plus emulator shipped with board

    I think I have followed the instructions to the letter, which is why I am confused? I've tried uncommenting exactly as directed, saving & reboot, then the PC can't connect to the emulator.

    The driver specified in the line being uncommented is "sdxds510usb_v10_1.out", which hasn't been delivered with the board, or with the emulator - so can I get it from somewhere? And also, it seems to refer to the wrong emulator - but everyone who buys this kit must have exactly the same issue, and solved it.

     

     

     

  • It sounds like you have done everything right without success, which of course is why you are trying to get help here. I will help as much as I can, but my PADK did not come with any emulator or software, or at least the TIer who handed it to me did not pass those on to me. I am envious of your XDS510USB Plus because mine is just the XDS510USB, so again I will not be able to prove out any of my suggestions.

    The easiest answer may be going to www.spectrumdigital.com and download the latest emulation drivers. You may have to create an account with them, but this is usually pretty fast. The page with the drivers is http://support.spectrumdigital.com/ccs33/ and it specifically mentions support for your emulator.

    The right answer would be to contact Lyrtech, assuming you bought the PADK from them packaged with the XDS510USB Plus. They should be able to get you running with what they shipped to you.

    When I did a search on my PC, I did not find the exact filename that you mention above, sdxds510usb_v10_1.out, but I found _v9 from 2003 and _v11 from 2008 and 2009. I have a lot of CCS and driver installations on my PC. Since the _v11 file is from Spectrum Digital, I will request that you get the files from them rather than me distributing their files.

  • John,

    First off, make sure you download the latest Spectrum Digital emulation drivers for CCS v3.3 (lazy link here). Like Randy I have only a "regular" XDS510USB but I was able to use these drivers as-is to connect to the PADK.

    After re-reading your original post I am curious if you are actually having trouble connecting to the DSP via CCS or if you are just concerned about the 54-bit IR length which SDConfig returns? If you are failing to connect in CCS then a screencap of the error dialog box might be useful. The IR length should always return 54, so you have nothing to worry about there.

  • Hello both,

    Thanks for the information - I think it may be a specific problem with the drivers of the PLUS

    Downloading the latest drivers does something, but not necessarily improves it - now the error in CCS is

    "Error connecting to target: Error -1072 PTI_ERR_TARG_STATE", whereas before it was "Unknown error -1610"

    Unfortunately I can't do screenshots, because I'm not allowed to connect any dev machine to the internet, or transfer files

    But I think that the "blocking" problem is not within CCS - is there any way within SdConfig whether the emulator (at least) can connect to the C6727 - shouldn't I get some device showing underneath the XDS510USB-PLUS ?

  • John Astrium said:
    But I think that the "blocking" problem is not within CCS - is there any way within SdConfig whether the emulator (at least) can connect to the C6727 - shouldn't I get some device showing underneath the XDS510USB-PLUS ?

    Sorry, I do not quite follow your question here. For reference, I am using an XDS510PP+ right now and this is the result of my scan chain test in SDConfig:

    ** Checking emulator/eZdsp scan connection

    ** Emulator Test **
     $$ EmuProductName=XDS510PP_PLUS
     $$ EmuPortAddr=0x378
     $$ EmuPortMode=SPP8
     $$ ProductId=10
     $$ ProductVersion=02
     ** Emulator Scan Test
       -- Found JTAG IR length of 54
       -- Found 2 JTAG device(s) in the scan chain

    Note that even though it finds the JTAG IR length to equal 54 that this does NOT mean CCS will establish a connection 100% of the time. Sometimes a random condition can prevent the emulator from connecting. Although I am not terribly familiar with the PTI_ERR_TARG_STATE status, if I had to interpret it I would say that the device is in a 'bad state' thus the problem connecting. As such, I would try to force the device to boot into a known good state.

    One quick and easy way to do this is the place the device into an emulation boot mode. This device does not have a boot mode devoted to emulation booting, but UHPI boot is close enough. To place the C672x in a UHPI boot please place JP10 on pins 2-3. This will tell the bootloader that an external host is going to boot the target and the CPU will spin in a while loop waiting for the host to finish. This prevents any application code from running which can effectively "break" the emulation logic.

    Please give this a try and let me know if this helps. In the meantime If you have not already done so I agree with Randy and suggest placing a support ticket in with Spectrum Digital and/or Lyrtech to see if they have already experienced this issue and know how to fix it.

  • From Spectrum Digital Inc. support, editted slightly:

    "Both the XDS510USB and XDS510USB PLUS use the same CCS drivers and in turn use the same CCS configuration.  SDI support tested an XDS510USB PLUS on CCS 3.3, latest SDI CCS 3.3 driver install, and C6727 target.  There was no problem in connecting.

    "Since the user can successfully verify the connection to the target board, they question the CCS Configuration.  Make sure you are using a configuration for the 'XDS510USB Emulator', not the 'XDS510 Emulator'.  They include a configuration with the latest CCS 3.3 driver install that supports the XDS510USB and C672x.  You can filter the configuration search to find 'C67xx' and 'XDS510 USB Emulator'.  The SDI configuration file does not include a GEL file, so it would be a good idea to add the Lyrtech-provided GEL file.

    "Using CCS 3.3, there is no need to modify the SDOPTS.cfg file and change the emulator application/firmware version."

    Do this help point you to a solution?

  • Thanks, this is very helpful to know that they are the same drivers, so I don't have to bother trying to get hold of a non-PLUS just to try. We are now trying a clean install - I wonder whether a previous CCS4 install is confusing it - our other thought is PCI drivers

     

  • I have heard of minor issues with having CCS3 and CCS4 on the same machine, but I have both on mine and have been able to work with either. But to be certain, it is unfortunately a safety measure to uninstall everything from CCS4 and then install the SDI drivers for CCS3. This should not be required, but it eliminates that concern. There have been cases where I would also uninstall CCS3 completely and start from a fresh reboot. After doing that a few times, I keep an InstallationHistory.txt file with the date/time and installation filename for each update; this lets me most easily get back to where I was with all the different emulators and Support Packages I keep.

    It is not clear to me how PCI drivers would affect this, but you have mentioned it as a concern. Could you explain why? Are these PCI drivers for an emulator or for the PC, or what?

  • To add to Randy's post I have some additional comments.

    There was actually a small time gap where the XDS510USB PLUS emulator application support for C6727 under CCS 3.3 was faulty. As such please double-check the configuration as suggested in Randy's earlier post (use the XDS510USB and NOT the XDS510 (ISA) emulator). If that does not work then you can use the attached files to update support on your system. Unzip the attached files into the CCS/Drivers folder - by default this should be C:\CCStudio_v3.3\drivers. Then close down all instances of CCS, cycle power to the emulator (unplug the USB connection and plug it in again), and try CCS again.

    sd510usb_driver_update_403233.zip
  • Thanks all, finally got it working on a clean install - we think that it was more than one thing, as none of these worked individually, but we don't know which things were definitely breaking it.

     Removing the CCS4 . Actively removing the automatically installed driver for the PCI XDS560 emulator. Performing a "Custom" install of CCSv3.3 without changing the defaults. Changing the JTAG TCK to 10 MHz (although it should support much higher). NOT installing the latest updates of CCSv3.3, or the emulator drivers, compared to what was on the disk (hope we don't turn out to need any of these updates later, we'll just have to take it slowly if we do)

    Whew. 

  • I marked your post as the answer even though the answer is likely from pieces of each of the 7 or 8 posts above this one just to show it as answered. In any case I am glad you were able to get this up and running, and I am sorry we could not pinpoint the root cause sooner.