• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 475 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/66AK2H12: Cannot access xds560 emulator

Tim Cooper1
Intellectual 980 points
Part Number: 66AK2H12


Tool/software: Code Composer Studio

CCS 8.1.00011, K2H12 processor.  I have an eval board (with the JTAG emulator as part of the board): works fine.

I also have a production board and an xds560 usb pod.

Yesterday, I had CCS 7.3 and updated some of the software components.  As a result of this, CCS could no longer initialize the 560 pod.  I removed CCS, and installed 8.1.0.00011.  Same behavior: I cannot access the 560 pod.

The pod and card work fine, as demonstrated by another PC with an older CCS.

The results from the emulator test window are shown below.  How do I recover from this?

[Start: Blackhawk XDS560v2-USB System Trace Emulator_0]
 
Execute the command:
 
%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
 
[Result]
 
 
-----[Print the board config pathname(s)]------------------------------------
 
C:\Users\TIMCOO~1\AppData\Local\TEXASI~1\
    CCS\ti\1\0\BrdDat\testBoard.dat
 
-----[Print the reset-command software log-file]-----------------------------
 
This utility has selected a 560/2xx-class product.
This utility will load the program 'bh560v2u.out'.
E_RPCENV_IO_ERROR(-6) No connection: emulator was not found
Download failed for file C:\ti\ccsv8\ccs_base\common\uscif\xds560v2.out
 
An error occurred while soft opening the controller.
 
-----[An error has occurred and this utility has aborted]--------------------
 
This error is generated by TI's USCIF driver or utilities.
 
The value is '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.
 
The explanation is:
An attempt to access the debug probe via USCIF ECOM has failed.
 
[End: Blackhawk XDS560v2-USB System Trace Emulator_0]
  • 0
    TI__Guru**** 161600 points
    Hi Tim,

    Did you reinstall or did you upgrade the CCS from 7.3 to 8.1? I suggest you try reinstalling the CCS and doing a fresh installation.

    Backup your modified source code. Uninstall the current CCS8.1 version, then delete the whole ~/ti folder and do a fresh installation of CCS.

    If the above doesn't work, try updating the Emulator firmware from another PC (you said the board works with another PC).

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Intellectual 980 points
    Let me clarify: I removed (un-installed) CCS 7.x and installed 8.1, and I still cannot access the pod (so, yes, a fresh installation).

    When you suggest updating the emulator firmware from another PC, can you be more specific? I understand there is firmware in the pod (which should not be the issue since the pod works with the other PCs); there is firmware that is part of CCS, and there are drivers provided by the vendor that are bundled with CCS. Can you be more specific?
  • 0 in reply to Tim Cooper1
    Intellectual 980 points

    I just un-installed CCS. Then I moved ti to ti_old, and installed CCS 8.1. Same issue.

    Same question: when you suggest "updating the emulator firmware", can you please be more specific?

    Thanks

    More:  after taking a few hours with field support at blackhawk and also with IT, we were able to get the emulator to work.   Backing up ti, moving it, and re-installing ccsv8 did not work.  The pc got into this mode when I selected updating various components under the the CCS help window.  Updating components was recommended as a potential resolution for another problem.  In retrospect upgrading was probably not needed. 

    No one (Blackhawk, TI, or the IT support) can explain why accessing the pod worked three days ago but was, all of the sudden, flagged by the PC with a bad signature. Reinstalling CCS and reinstalling the driver did not work.  IT took several actions and turned off some security features (features that have not changed for months) to get the driver to work.

    It is very inconvenient to reinstall CCS, esp with all of the supporting tools and packages needed to support this processor in the middle of a project.  I am curious:  have others had this problem? Also, why the TI tools are such that this is required, esp since many E2E posts recommend using the latest version of tools?  I now have the latest version of CCS,and am re-installing supporting tools and packages.  Even if CCSv8 is more robust, my tool set is now out of sync with the tool set used by others on the development team. 

    Thanks for your help and responses.

    Regards,

    Tim