• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 602 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: CCS9 Windows 10 and SEED XDS560v2 incompatibility ?

Arthur Cartier
Intellectual 410 points


Tool/software: Code Composer Studio

Hello,

We are trying to update our work environment from Windows 7 Code Composer studio 6.2 to Windows 10 code composer studio 9.2 .

But it seams that on the new environement CCS cannot contact the XDS560v2 over Ethernet. The "Test Connection" give the following result :

[Start: SEED XDS560V2 LAN Emulator_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\ew\AppData\Local\TEXASI~1\CCS\ccs920\
    0\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 'seed560v2e.out'.
E_RPCENV_IO_ERROR(-6) No connection: Load of seed560v2e_io.dll failed
Download failed for file C:\ti\ccs920\ccs\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: SEED XDS560V2 LAN Emulator_0]

No setting has changed since from the old environment.
The seed560v2e_io.dll is in the same folder as dbgjtag.exe and the folder is in the path.

Do you have an idea what could be the issue ?

Best Regards

Arthur CARTIER

  • 0
    TI__Guru**** 171254 points

    Arthur,

    I am able to connect to my Blackhawk BH560v2STM Debug Probe over the network, thus ruling anything inherently wrong with CCSv9.2 itself.

    Given that error -250 is caused by communications failure between the Debug Probe and the host, there is a very high probability that something on the network or on the network interfaces of the host computer are causing this. 

    Obviously that rules out any possible incompatibilty between the SEED drivers and CCSv9.2, but for that information you would have to contact them directly - we don't support SEED Debug Probes. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 410 points

    Hello Rafael,

    Thank you for your fast answer.

    The first error that shows up is "E_RPCENV_IO_ERROR(-6) No connection: Load of seed560v2e_io.dll failed".

    But even if there was a file named seed560v2e_io.dll in the folder "C:\ti\ccs920\ccs\ccs_base\common\uscif\" the correct dll file is named sd560v2e_io.dll (only the later one is mentioned in the manifest from SEED). So I copied the sd560v2e_io.dll and renamed it seed560v2e_io.dll (erasing the former one). And now it's working.

    Best regards

    Arthur

  • 0 in reply to Arthur Cartier
    TI__Guru**** 171254 points

    Arthur,

    Thanks for reporting back your findings. The sd560v2e_io.dll is installed with the Spectrum Digital Debug Probe support, thus I am a bit surprised that SEED would work with the same .dll without modifications.

    At any rate, it is an interesting conclusion.

    Regards,

    Rafael