• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1561 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/TMS320F28377S: -2083 Error code with Xds560v2 since upgrade CCS from CCS9.0.1.00004_win64 to CCS9.1.0.00010_win64

A GIR
Genius 3615 points
Part Number: TMS320F28377S
Other Parts Discussed in Thread: CCSTUDIO, TMDSEMU560V2STM-U

Tool/software: Code Composer Studio

Hello

I'm using CCS everyday on a borad with F28377S. I'm using the Xds560v2.

Since last monday, I upgrade CCS and pass from  CCS9.0.1.00004_win64 to CCS9.1.0.00010_win64.

But now, As soon as CCS was closed one time, the next use of CCS lead to the error -2083 when I try to connect to the target.

I tried all say in this post:

https://e2e.ti.com/support/tools/ccs/f/81/t/640080?tisearch=e2e-sitesearch&keymatch=2083

But nothng work.

The only way I found is to uninstall CCS and re install. After that, Xds560v2 work again, but only until the next Close/Open CCS!!… :-(

I'm downgrading to the v9.0.1 until a solution was found! .

Thank for your help.

  • 0
    Genius 3615 points

    Note:

    I Upgrade by download the Offline installer.

    Today, after re installed the 9.0.1, the Update notification inform me the update of:

    CCSv9 Service release Windows v 9.1.0.00010

    And also the Debug Server Flash (windows) v9.1.0.1672.

    Is the update of Debug Server with the CCS v9.1.0 will work?

  • 0 in reply to A GIR
    Genius 3615 points

    In fact, problem occurs also on v9.0.1. Then the problem appears in the same time I update the CCS to v9.1.0 but there is no correlation.

    What can I do to resolve my problem?

  • 0 in reply to A GIR
    TI__Guru**** 170244 points

    Hi,

    Error -2083 is a problem between the host and the Debug Probe, and can be caused by a nubmer of factors described in the Debugging JTAG page below (just search for th error number):

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html 

    Given you seem to have a reproducible behaviour where running CCS once causes the probe to become incommunicable, I suspect there may be a lingering process that is hijacking it and preventing any subsequent connections. 

    After you connect once, can you close CCS and look for ccstudio.exe processes running in the Task Manager? They may be locking up the probe. If youare using a Spectrum Digital Probe, there is also another process called sd560v2u_server.exe

    Also, can you try to run the probe utility (either Bh560v2Config or Sd560v2Cnfg v5) and see what it reports back? It may help shed some light on the issue. 

    Unfortunately I can't reproduce this issue here in both my Windows 7 and Windows 10 (1809). Also, historically I was unable to reproduce this without a clear explanation of conflicting processes or debug probes. 

    The CCS versions 9.0.1.00004 and 9.1.0.00010 feature the same Blackhawk Emulators component (9.0.0.001) but with different TI Emulators component (8.1.0.00012 and 8.2.0.00004 respectively). However, both worked fine here. 

    I am connecting to a F28377D experimenter kit using the 14-pin adapter. 

    I will try to think about additional scenarios and report back. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Genius 3615 points

    Hello,

    PLease find the report when I made "TestConnection" via the Target connection configuration into CCS:

    [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\Arnaud\AppData\Local\TEXASI~1\CCS\
    ccs901\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 'bh560v2u.out'.
Outfile creation failed for infile C:\ti\ccs901\ccs\ccs_base\common\uscif\uscifv2.out
Load of file C:\ti\ccs901\ccs\ccs_base\common\uscif\uscifv2.out failed

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]

    Bellow the test done with the Blackhaw installated tool (Shortcut on the desktop named bh560v2ConfigUtility linked to C:\ti\ccs910\ccs\ccs_base\common\uscif\Bh560v2Config.jar:

    I get the same message:

    Thank

  • 0 in reply to A GIR
    TI__Guru**** 170244 points

    Hi,

    Thanks for sending the screenshots - the last one partially matches my TMDSEMU560V2STM-U Debug Probe:

    The utility in both our cases is properly detecting and reading the configuration infiormation of the probe.

    The dbgjtag command, however, is different. In your setup this command is failing on both CCS and the Bh560v2Config Utility, which is quite odd given the utiltiy is able to properly communicate with the probe. This error is described in the reference I sent before and is usually related to physical or device driver issues between the probe and the host - clearly not the case here. 

    In my setup above, you can see the dbgjtag goes past beyond the point you are getting it (the full console output is shown in the attached file). 

    With this, I can't really tell what may be happening. Are you running this on a native or a Virtual Machine? Which version of Operating System are you running? Do you recall any Windows updates recently applied? 

    Regards,

    Rafael

    Bh560v2Config_20190823160743.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    CMD: dtc_conf --version
    Version 8.2.0.00004, built Jun 3 2019 15:19:28
    LAN: Not selected to search.
    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.573.0
    fpgaRev=1.54
    productClass=XDS560V2
    productName=Blackhawk USB560v2 System Trace Emulator
    safeMode=false
    serialNum=00:00:00:04:34:73
    swBuildTime=Apr 19 2012 14:09:25
    swRev=5.0.573.0
    time=none
    vendorName=Blackhawk
    standbyEnable=false
    standbyMinutes=20
    CMD: dbgjtag -X emulator,driver=bh560v2u,ioport=0 -S integrity -Y reset -S pathlength -G range,lowest=9.350000,highest=11.250000
    Loaded FPGA Image: C:\CCSv9_1_0\ccs\ccs_base\common\uscif\dtc_top.jbc
    -----[Perform the standard path-length test on the JTAG IR and DR]-----------
    This path-length test uses blocks of 64 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 64 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 64 32-bit words.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to desouza
    Genius 3615 points

    hello

    I'm using Windows 10. I havn't virtual machine, only native operating system. I not remember changed anything on my computer. I'm gone to the vacation, I when I'm back, It propose me to  update from 9.0.1 to 9.1.0. Then I done. Since, problem occurs. It is why the title of this post indicate the problem come with the upgrade CCS.

    But now, I test with the old version v9.0.1 and it is the same.

  • 0 in reply to A GIR
    Genius 3615 points

    Hello,

    Any other idea?

    It is very blocant for me to remove and then re install every day CCS!

    :-(

  • 0 in reply to A GIR
    TI__Guru**** 170244 points

    Hi,

    Unfortunately I have no idea what may be going on in your system, as I don't have a previously reported issue like that.

    It could be either a problem between the OS and the debug probe's device drivers or between the OS and CCS. If possible, can you try on a different host? Or perhaps restart the system after you close CCS? This may be evidence the CCS process may be lingering and locking the Debug Probe. 

    Also, instead of re-installing CCS, when you plug the Debug Probe in the system can you try to uninstall and re-install the device drivers only? For that you need to go to Control Panel --> Device Manager --> right-click on the Blackhawk USB560v2 --> Uninstall Device --> and check the box Delete the driver software for this device. 

    This would be the closest scenario to a full reinstall - from the standpoint of the Debug Probe's perspective, of course. 

    Another theory is to check the antivirus or firewall to see if they are somehow blacklisting or quarantining any of the CCS components. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Genius 3615 points

    Hello

    I try again this morning, and then it run again! :-)

    The only change since last week, until I remember is the Windows update to the new version (1903)...

    I can't say if there a link With my problem..

    I will back agin here if the problem back again..

    Thank

  • 0 in reply to A GIR
    TI__Guru**** 170244 points

    Hi,

    Thanks for reporting back the outcome of your scenario. What was the previous version running? 

    I have everything running fine here on my Windows 10 host running version 1809. Prior to CCSv9, I was running version 1803. I also have a 1903 version that works fine as well.  

    At any rate, thanks again for reporting back the outcome of this issue. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Genius 3615 points

    I not remember the previous Windows version.

    I'm septic on the fact the new upgrade change my problem... But ...