• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 900 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/LAUNCHXL-F28069M: Target Configuration - Device not listed

Urvi Ahluwlaia
Prodigy 10 points

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: UNIFLASH, CCSTUDIO

Tool/software: Code Composer Studio

Dear team,

I am trying to Configure Lanchpad F28069M using CCS v6.2.0, but the devise is not listed in the drop down. Kindly let me know how to proceed. On checking the connection using 'Test Connection' the following error occurs: 

Execute the command:

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

[Result]


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

C:\Users\Divya\AppData\Local\TEXASI~1\CCS\
ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.

An already open status was returned 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 '-110' (0xffffff92).
The title is 'SC_ERR_OCS_ALREADY_OPEN'.

The explanation is:
This utility opened the controller but found it already in use.
You must exit other debuggers and utilities that access the
controller because this utility must be the only client.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

Thanks,

Urvi

  • 0
    TI__Guru**** 171729 points
    Urvi,

    The error message indicates there is something else already using the XDS100v2 ports. Do you have a running debug session already or other utilty such as Uniflash or a serial terminal program (Teraterm, Putty, etc.) running on your host PC?

    I would also close the current instance of CCS and check if there are any other processes named ccstudio.exe in the Windows Task Manager. If you experienced a software crash/collapse, there is a slight chance the process of the previous run is zombie and should be terminated manually.

    Hope this helps,
    Rafael