• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 53 subscribers
  • Views 1625 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.

Original question:

connect to the XDS110 failed

CCS/CC2642R: XDS110 debug and programming problems CCS 9.1

Ron Sloat
Prodigy 60 points
Part Number: CC2642R
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hi all,

I'm trying to debug and program a CC2642 chip, and I have purchased an XDS110 debug probe. My problem lies in the debug probe and CCS 9.1.

Upon installing all of the software, my debug probe never was recognized in Windows 7. It came up as an "XDS110 Probe" but could not find drivers. I found out where the drivers were installed, and forced a driver install. However, I can only select either the "Debug" or "Data" .inf's, not both. When it installs, I get a device titled either "XDS110 Class Data Port" or "XDS110 Class Debug Port" under "Texas Instruments Debug Probes". Nothing shows up in the "Ports" category related the the device like other forum posts show.

Getting a .hex file from CCS, I can use the probe with Uniflash to flash the code to the device. However, in CCS 9.1 I cannot get it to either debug or flash, and just gives me an "Error -6311" connection problem. 

Has anybody had a similar experience? I can't get both the Data and Debug ports up, is that my problem? I seem to have hit the limits of my knowledge and ability on getting this to work. Thanks for any light you can shed on this problem.

Ron

  • 0
    TI__Guru**** 171044 points

    Ron,

    Certainly the device driver install is a problem. Interestingly there is a somewhat similar report that was just submitted to e2e: basically the auxiliary UART ports cannot be properly instantiated, but the Debug and Data ports are ok. 

    https://e2e.ti.com/support/tools/ccs/f/81/t/830969 

    Please check the details on the related thread. I suspect you already did all this from your description.  

    Since the Debug port is functional, you shoudl be able to connect to the device. Error -6311 is related to a change in the TCLK parameter of JTAG. Please check : 

    https://e2e.ti.com/support/tools/ccs/f/81/t/821584 

    Hope this helps,

    Rafael 

  • 0 in reply to desouza
    Prodigy 60 points

    Yeah, I tried that already. Unfortunately, since only one device shows up on my computer, I can only attempt to uninstall and reinstall that single Data or Debug driver. Doesn't seem to affect anything else, and I have yet to see anything regarding the ports.

    I've attempted to remove all of my USB drivers to see if starting over would help, but have had no luck. One thing I noticed is that when I plug in the XDS110, if I go to Devices and Printers, an unspecified device called "XDS110 (02.03.00.18) Probe with CMSIS-DAP" shows up.

    I'm completely stuck now. I'm going to find another computer to plug this into to see if I can salvage this.

  • 0 in reply to desouza
    Prodigy 60 points

    Well, if it wasn't my computer before, maybe it is now. All of this uninstalling USB hubs and ports and screwing around has killed the USB ports on my docking station, and now two unknown devices pop up that are likely USB hubs or such. Cannot for the life of me get drivers installed, and on my laptop USB ports I still only can see one USB device when the XDS110 is plugged in. 

    Are there any known problems with Windows 7? This seems like such a stupid problem, and if Windows can't see it, it's gotta be buried deep.

  • 0 in reply to Ron Sloat
    TI__Guru**** 171044 points

    Hi,

    I am sorry to hear about the issues you are having. At this point I am wondering about the following scenarios:

    - The fact you can't enumerate the XDS110 Debug Probe anymore may be tied to the fact Windows exhausted these entries on the Device Manager with the successive retries. If you open the Device Manager and go to menu View --> Show hidden devices, can you erase the greyed out entries of both classes? 

    - After doing that, I would connect the Launchpad and see which entries were enumerated. If you are still not seeing the Serial Ports but see the Texas Instruments Debug Probe ports, try to re-flash the debug probe as shown in section Updating the XDS110 Firmware of the page below: 

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

    - If that fails, please copy and paste the output of the xdsdfu utility. I would then suspect there is something more critical with the Launchpad HW. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 60 points

    I think by removing my USB hubs to try to "reset" my USB, it must have removed those entries, because I see no ports whatsoever. And I've used ports for bluetooth serial links, arduino, etc.

    Flashing the bootloader gives me very little feedback that it worked, but the xdsdfu gives me:

    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 Probe with CMSIS-DAP
    Version: 3.0.0.2
    Manufacturer: Texas Instruments
    Serial Num: 00000000
    Mode: Runtime
    Configuration: Standard

    Found 1 device.

    But that's it. Still just that one device that I can install either the Debug or Data port on, and it seems to just do the same thing. 

    One thing that I noticed (which might be from the clock speed issue) is that when uploading with Uniflash 5.0.0, it works fine. I upgraded to Uniflash 5.1.0 to match CCS 9.1 (because of the bootloader) and I noticed that I get that 6311 error which can't write the register. Setup is exactly the same, just the firmware and Uniflash/CCS. Of course, I'm still missing those auxiliary ports and such, so it's clearly not my only problem. For what it's worth.

    I'm upgrading to Windows 10 tonight. Will update on port progress then.

  • 0 in reply to Ron Sloat
    TI__Guru**** 171044 points

    Hi,

    I am still baffled by the absence of the serial ports. 

    Ron Sloat said:
    One thing that I noticed (which might be from the clock speed issue) is that when uploading with Uniflash 5.0.0, it works fine. I upgraded to Uniflash 5.1.0 to match CCS 9.1 (because of the bootloader) and I noticed that I get that 6311 error which can't write the register.

    PRSC Error 6311 is usually due to a cJTAG and JTAG mismatch. Your target configuration probably is set to 4-wire JTAG (IEEE1149.1) while the target wants to communcate in cJTAG (IEEE1149.7). This is reported in the Debugging JTAG page below (search for the error number):

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

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 60 points

    Hi Rafael,

    Good news. I updated to Windows 10, and viola, the probe comes up with the serial ports and all seems well. Why there was a problem to begin with I have no idea. Now the biggest issue is that PRSC Error 6311, which goes away if I just hit retry a bunch of times. I tried to read the pages you linked to, but I couldn't find any information on correcting the JTAG configuration. When I open up the config file in CCS, I don't see any options besides changing the debug probe, which is correctly set to the XDS110. 

    Would you be able to point me in the direction of the fix for this? Does it have anything to do with the clock frequency problem brought up earlier?

  • 0 in reply to Ron Sloat
    Prodigy 60 points

    Actually, I found it finally in the advanced settings. I changed the speed down a bit and set it to 4 wire JTAG. I think this clears everything up! Thanks so much!

  • 0 in reply to Ron Sloat
    TI__Guru**** 171044 points

    Ron,

    Thanks for reporting back the outcome of your scenario; this will certainly help other developers in the future. 

    For me this launchpad seems to works well with 5.5MHz instead of the default 8.5MHz. 

    The OS serial ports remains a mystery. I will be on the lookout for any other reports. 

    Regards,

    Rafael