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.

SMARTRFTM-STUDIO: CCDebugger will not connect via USB due to driver issues

Part Number: SMARTRFTM-STUDIO
Other Parts Discussed in Thread: CC1101

I am attempting to connect a CCDebugger to a PC with Windows 7 Pro on it.  However, the CCDebugger entry in the Device Manager always shows the error with the yellow exclamation point over the icon.  No matter what I do to try to install/reinstall the drivers I get the same message saying "Windows found driver software for your device but encountered an error while attempting to install it.  One of the installers for this device cannot perform the installation at this time."

I have run through the driver installations as stated in the User's Guide and Design Note 304.  None of this helps.  I have tried to use drivers installed with the SmartRF studio, then i uninstalled it and attempted to install the drivers separately.  None of this worked.

Any help would be greatly appreciated.

  • Try to use the driver downloaded from www.ti.com/.../swrc212a.zip
  • I had already tried that one along with a few others that I found on the TI site.  I was finally able to solve the problem through some sequence of reboots, driver uninstalls and reinstalls.  I'm not sure of the exact sequence that finally did it, but it appears that they have been installed.

    I still have a problem with the board not talking to the CCDebugger.  That should be a different issue.  I have checked all of the connections to the board, and the board is functioning.  Is there a special load I need to put into the board to get the CCDebugger to work with it?

    Any suggestions would be appreciated.

  • What do you mean “you still have a problem with the board not talking to the CCDebugger“? What’s the board do you mean here?
  • I have a development board connected to the CCDebugger hardware using the recommended connections in the User's Guide. I am using a CC1101, so I have GND, VDD, DC, DD, CSn, SCLK, MOSI and MISO connected. Now that I have the driver installed correctly I should be able to see a green LED when everything is connected. It's still red.
  • CC1101 is a transceiver and I suppose the connection between CC Debugger and CC1101 is SPI interface which you can refer to www.ti.com/.../swru197h.pdf . After connection, I suppose you can use SmartRF Studio to control CC1101.
  • Is the DUT powered from the debugger? In either case, have you connected pin 2 to the relevant supply?
  • Yes, I agree I should be able to control the board. However, I have it hooked up exactly like the diagram shown in Figure 10. I double-checked our connections using a meter.

    I power the device from an external battery pack, but the VDD is connected back to the CCDebugger as shown in the User's Guide.

    Is there an order to the connection process? I don't see a button or menu choice to connect. Should I assume that it automatically connects when everything is powered and connected correctly?
  • If you have connected everything correctly it should only be to press the reset button on the debugger and the light should go from red to green.

    Which development board are you referring to?

    I have done this myself a fair number of times and the common issues are:
    - The signals are not connected correctly (looking at wrong pin, mixing wires, soldering etc)
    - Pin 2 is incorrect.
    - The SPI lines are driven by a second MCU on the board
  • After I put the SPI master into reset it fixed the problem.

    The documentation is not entirely correct.  In order to control the board from SmartRF you do not need all of the connections in the diagram from the documentation.  The DD and DC signals are not needed.  Only SPI, VDD and GND are needed.

    Thanks for your help.

  • I believe the DD and DC are needed if you want to use SmartRF Studio to send and receive packets with your board.
  • Hi,

    Clarification on Glenn's comment above:

    When CC Debugger talks to a CCxxxx SoC, the DD and DC lines are required for data communication.

    When CC Debugger talks to a CCxxxx transceiver, the SPI lines are required for data communication.

    Br,
    TIABO