Cannot start a debug session for one XDS110 debug probe if another debugger instance for another XDS110 exists that is connected to another core

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Medium
    • Code Composer Studio Debugger
    • CCBT-3671
    • Hide
      https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1642880/ccstudio-debugging-two-mcus-with-two-xds110
      Show
      https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1642880/ccstudio-debugging-two-mcus-with-two-xds110
    • CCS_20.3.0
    • Generic
    • Hide
      The workaround is to launch both debug instances first before connecting to any core. Once both instances have been launched, it is possible to connect to cores for both targets.

      Another workaround is to disable the "Detect Probe On Launch" option in the General Settings.
      Show
      The workaround is to launch both debug instances first before connecting to any core. Once both instances have been launched, it is possible to connect to cores for both targets. Another workaround is to disable the "Detect Probe On Launch" option in the General Settings.

      In environments where there are multiple XDS110 debug probes connected to the machine, it should be possible to launch multiple debugger instances for each probe as long as workspaces are not shared between the CCS/debugger instances. However, there are cases where a debug launch will fail with a LIBUSB_ERROR_ACCESS error. This can happen if there is already a running XDS110 debug instance where a target connect with the core in already establish.

      The workaround is to launch both debug instances first before connecting to any core. Once both instances have been launched, it is possible to connect to cores for both targets.

      It has been determined that the root cause is with auto-detect. Hence this issue only impacts multiple auto-detectable debug probes like XDS110. Hence there is no issue with an environment with one XDS110 and one XDS100.

      Another workaround is to disable the "Detect Probe On Launch" option in the General Settings.

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Connection: Intermediate to External PROD System
                EXTSYNC-6027 - Cannot start a debug session for on...
                SYNCHRONIZED
                • Last Sync Date: