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.

CCS unable to connect to C6678L core

I have a TMDSEVM6678LE board that has been working with the CCS tools.

Starting about a week ago, CCS tools can no longer connect to the core.

In the debug view window, the message is:

"Blackhawk XDS560v2-USB Messzanine Emulator_0 (disconnected:Unknown)
... the above repeated for all 8 cores.
There were other error message appeared on the Console window as well.
Details about my system:
EVM = TMDSEVM6678LE rev. 3A
CCS  Version = 5.2.0.00069 
GEL file version = 2.003

Thanks for helping.

Wing

  • Hi Wing,

    Could you run the XDS560v2 diagnostics and post the results? Blackhawk should provide one that comes with CCS. I'd like for you to test your JTAG integrity outside CCS.

    Thanks

    ki

  • Hi Ki,

    I have used "BH560V2 Config Utility" to test my EVM multiple times. They always pass. I have checked all test options: Reset, Scan Path, Run All, Integrity. All of them passed.

    I have attached the test log file.

    Thanks for your help.

    Regards,

    Wing

    CMD: dtc_conf --version
    Version 5.0.747.0, built May 30 2012 23:43:30
    
    
    CMD: ipconfig
    
    Windows IP Configuration
    
    Ethernet adapter Local Area Connection* 15:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
    Ethernet adapter Local Area Connection:
       Connection-specific DNS Suffix  . : am.mot.com
       Link-local IPv6 Address . . . . . : fe80::b0c0:dac3:87cf:c5%20
       IPv4 Address. . . . . . . . . . . : 10.77.179.132
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 10.77.179.254
    Wireless LAN adapter Wireless Network Connection 3:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : am.mot.com
    Tunnel adapter Local Area Connection* 12:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
    Tunnel adapter Local Area Connection* 16:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
    Tunnel adapter isatap.{03615A4E-5F5B-47FC-ABDB-CA932AD492C7}:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : 
    Tunnel adapter isatap.am.mot.com:
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . : am.mot.com
    
    
    CMD: ping -n 2 10.77.179.255
    RES: Ok
    
    
    CMD: arp -a
    
    Interface: 10.77.179.132 --- 0x14
      Internet Address      Physical Address      Type
      10.77.179.15          00-a0-d1-56-7f-bd     dynamic   
      10.77.179.20          c4-2c-03-0b-d6-35     dynamic   
      10.77.179.56          2c-6b-f5-02-bf-00     dynamic   
      10.77.179.130         f0-de-f1-f1-ca-8a     dynamic   
      10.77.179.139         3c-97-0e-32-f0-16     dynamic   
      10.77.179.159         3c-97-0e-3e-cb-fc     dynamic   
      10.77.179.176         00-1a-a0-17-8a-ab     dynamic   
      10.77.179.252         00-12-f2-96-3d-00     dynamic   
      10.77.179.253         00-12-f2-95-c9-00     dynamic   
      10.77.179.254         02-e0-52-0e-03-66     dynamic   
      10.77.179.255         ff-ff-ff-ff-ff-ff     static    
      224.0.0.22            01-00-5e-00-00-16     static    
      224.0.0.252           01-00-5e-00-00-fc     static    
      239.255.255.250       01-00-5e-7f-ff-fa     static    
      255.255.255.255       ff-ff-ff-ff-ff-ff     static    
    
    LAN: Filter devices...
    LAN: 0 devices found.
    
    
    CMD: dtc_conf get bh560v2u 0 
    
    CMD: dtc_conf get bh560v2u 1 
    USB: 1 device found.
    
    TOTAL: 1 device found.
    
    
    CMD: dtc_conf get bh560v2u 0 
    addrConf=:55756
    addrIo=:55755
    boardRev=2
    dtcName=none
    epkRev=5.0.161.0
    fpgaRev=1.5
    productClass=XDS560V2
    productName=Blackhawk XDS560v2-USB Mezzanine Emulator
    safeMode=false
    serialNum=08:00:28:32:06:08
    swBuildTime=Mar 14 2011 12:02:08
    swRev=5.0.161.0
    time=none
    vendorName=Blackhawk
    
    
    TST: Start...
    
    CMD: dtc_conf get bh560v2u 0 
    TST: PASS
    
    CMD: dbgjtag -d bh560v2u -p 0 -S integrity -Y reset -S pathlength -G range,lowest=9.350000,highest=11.250000 
    
    -----[Perform the standard path-length test on the JTAG IR and DR]-----------
    
    This path-length test uses blocks of 512 32-bit words.
    
    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 6 bits.
    
    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.
    
    -----[Test the source and frequency of the JTAG TCLK]------------------------
    
    The frequency of the JTAG TCLKR input is measured as 10.37MHz.
    
    -----[Perform the scan and frequency double test]----------------------------
    
    This test will use a total of 15 frequencies.
    This test will measure every frequency.
    This test will use blocks of 512 32-bit words.
    This test will be applied just once.
    
      Base         Step          Results (press any key to finish early)
    
      9.000 MHz    125.0 kHz     -  -  -  O  O  O  O  O 
      10.00 MHz    125.0 kHz     O  O  O  O  O  O  O  O 
      11.00 MHz    125.0 kHz     O  O  -  -  -  -  -  - 
    
    The scan and frequency double test has finished.
    
    -----[Perform the Integrity scan-test on the JTAG IR]------------------------
    
    This test will use blocks of 512 32-bit words.
    This test will be applied just once.
    
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    
    The JTAG IR Integrity scan-test has succeeded.
    
    -----[Perform the Integrity scan-test on the JTAG DR]------------------------
    
    This test will use blocks of 512 32-bit words.
    This test will be applied just once.
    
    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.
    
    The JTAG DR Integrity scan-test has succeeded.
    
    RES: dbgjtag -d bh560v2u -p 0 -S integrity -Y reset -S pathlength -G range,lowest=9.350000,highest=11.250000 
    RES: Ok
    

  • Hi Wing,

    Thanks for the attachment. Looks like your JTAG connection is indeed fine.

    One thing to try is update your CCS version to 5.3.0. Hopefully this will help. If it does not, please reproduce the issue and send a debug server log. You need to turn this logging on. You can do it from the CCS Support GUI:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#CCS_Diagnostic_Logs

    Thanks

    ki

  • Hi Ki,

    I have used CCSv5.3.0.00090, turned on the debug server log as suggested , and re-run my project.

    The log file "debugServerLog010313" has been attached.

    I have observed the following that might be helpful:

    * The result of each run is not necessarily consistent. The failure pattern varies ( with the same CCS settings).

    * I was even able to run the project successfully once or twice, but on repeat, it typically failed.

    * I swapped EVMs among my coworkers with various CCS versions. The runs typically failed, with occasional successes.

    Thanks for your help.

    Wing

    2148.DebugServerLog010313.zip

  • Hi wing,

    Thank you for the attachment. However, I only see the Eclipse Logs and Installation Logs. I do not see the debug server logs. You need to explicitly enable the generation of them as mentioned in the wiki article. Could you generate that log and send that to me?

    Thank you

    ki

  • Hi Ki,

    I did turn on the "debug Sever Log", don't know why it is not included. I have tried again today. File is attached.

    I used the "Archive Logs..." button trying to save as a zip file, wasn't able to locate the .zip file. I have used winzip to generate the compress file instead.

    Hope it works. Thanks.

    Wing

    2772.debugServerLog1_010413.zip

  • Thanks. The log was analyzed and there definitely is some emulation failure. The debugger itself seems to be fine.

    Could you try one more thing? Could you clear all target cache files, launch files and also use a new workspace. I just want to see if that will help.

    How to do all this is mentioned below

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#Debugger

    Thanks

    ki

  • Hi Ki,

    I have followed the steps in the link, with a new workspace directory and cleared target cache files.

    The target configuration has been launched a few times, the reaction with the launch was not the same each time.

    Hope this run will provide the information needed to identify the problem.

    Thanks for your help.

    Wing

    debugServerLog011513.zip