• State Resolved
  • Locked Locked
  • Replies 24 replies
  • Answers 2 answers
  • Subscribers 23 subscribers
  • Views 8946 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.

CC Debugger not being recognized by Windows

Vivek Ravi
Prodigy 240 points
Other Parts Discussed in Thread: CC-DEBUGGER

Hey guys,

I am trying to use the CC debugger to program a few demo applications to the CC2540DK-MINI using the RF flash programmer and I am having some very frustrating issues that I'm hoping somebody can help me with.

I followed the instructions on the getting starting guide that was provided with the development kit. I first downloaded and installed the smart FT flash programmer and smart RF studio.( I read in the user manual for the CC debugger that the USB driver is automatically downloaded when any one of these tools are installed).

Now when I connect the CC Debugger to the PC I get an error from windows stating  that the USB device not recognized.  Specifically the error says that "One of the USB devices attached to this computer has malfunctioned".  It says windows has stopped the device because it has detected problems( code 43).

 I downloaded the Cebal – CCxxxx Development Tools USB Driver for Windows x86 and x64” which is a standalone installer including only the device driver and manually tried to update the drivers but it says that "the best drive for software is installed and up to date".

I tried connecting the debugger to the USB dongle and the keyfob and I know it connects to both targets because there's a green light on the debugger. So the debugger recognizes the targets but the PC doesn't recognize the debugger. 

Has anybody faced this issue? I would really appreciate any help regarding this. I am using 64 bit windows 7.

regards,

V

  • 0
    Guru 31280 points

    Hi,

    Have you tried to connect it to another PC (with, let's say, win XP on it)?

    One more thing, do you have additional CC debugger, or a smartRF05EB?

  • 0 in reply to Igor Sherer
    Prodigy 240 points

    Hey,

    Thank you for getting back to me.

    Yes, I tried it on three other machines.. One desktop with windows 7(32 bit), one desktop with xp and one laptop with xp on it. All four devices give me the same error.

  • 0 in reply to Vivek Ravi
    Guru 31280 points

    Ok,

    Do you have additional CC debugger, or a smartRF05EB?

  • 0 in reply to Igor Sherer
    Prodigy 240 points

    No, I don't! Do you think it is a problem with the debugger? Will I need to update the firmware or something along those lines? The debugger recognizes the target which is good, but the PC does not recognize the debugger.  Well it does, but says it's malfunctioning. 

    V

  • 0 in reply to Vivek Ravi
    Guru 31280 points

    And despite the fact it's being recognized as malfunctioning, can you still use smartRF flash studio and read

    IEEE address of, let's say, the keyfob?

    You can update the firmware, if of course the CC debugger recognized by smartRF flash programmer.

    You can even try to do something more complicated, like flushing a bootloader and then updating the firmware,

    though for this you'll need another CC debugger or a smartRF05EB.

    To be honest with you, I think you got a broken CC debugger, you can follow its schematics and try to trace

    the problem, also you can return it back from where you bought it and ask for a new, free one.

  • 0 in reply to Igor Sherer
    Prodigy 240 points

    No it's not being recognized by the smartRF flash programmer or smartRF studio. If it did, I would update firmware. I have a feeling the debugger is broken too, but I thought  maybe someone from TI or on the forum has dealt with a similar problem? 

    Ok, I just spoke with one of my colleagues and he told me he's worked with this particular debugger on his laptop before so we connected the debugger to his laptop( His laptop has RF flash programmer and smartRF studio installed) and it works fine. ( We are not getting the USB not recognized error). Now, this is very strange and I have no idea what is happening. The laptop that it works on is windows 7(64 bit). Could it be a windows update that's messing with the drivers? 

  • 0 in reply to Vivek Ravi
    Guru 31280 points

    I don't think so, since you have tried on several PCs and a laptop with different OS on each one.

    You can install the last version of smartRF flash programmer on your colleague's PC and try to update

    the firmware of CC debugger, then try to reinstall the driver on you PC (cebal64)

  • 0 in reply to Igor Sherer
    Prodigy 240 points

    Thank you so much for answering my questions.

    Apparently the debugger has the latest firmware so there is no update required. Is there a specific way in which the rf programmer or smartRF studio needs to be installed? From all the manuals it seems pretty straight forward. I really have no idea what the problem could be. It's tempting to assume that the debugger is faulty but the fact that it works on the one systems seems to suggest that it could be an installation issue. The laptop that it works on has RFstudio 1.6.1 and the latest one available on the TI website is 1.9.1.

  • 0 in reply to Vivek Ravi
    Guru 31280 points

    Vivek Ravi said:
    TI website is 1.9.1.

    No way, the latest version is SmartRF Flash Programmer 1.12.4 (Rev. P)

    Download it and install, update me on your progress.

  • 0 in reply to Igor Sherer
    Prodigy 240 points

    I installed the latest smartRF programmer on my computer and it doesn't work. Same problem. My colleague is hesitant to install the latest version on his  computer(the one that works) because we don't have the exe file of the version of the programmer that's currently installed. So we don't want to mess with the one system it's working on.

    Do you know we can revert back to the older version if it doesn't work and if the older versions are still available online?

    Thank you so much for your response.

    regards

    V

  • 0 in reply to Vivek Ravi
    Guru 31280 points

    Odd, very odd.

    Usually TI doesn't gives to download older versions of such software tools, however you can as them if

    the have this particular version, I think the can give an access.

    Here's a link to ver 1.10, it works on winXP and win7 (64Bit). Uninstall any version of smartRF flash programmer

    currently installed on your PC, also remove any cebal drivers. Only then install ver1.10.

    good luck :)

  • 0 in reply to Igor Sherer
    Prodigy 240 points

    I tried installing the older version as well and it's the same error. Thank you for your help and advice. Can somebody from TI maybe take a look at this post and let me know  what they think the problem could be?

    regards,

    V

  • 0 in reply to Vivek Ravi
    TI__Expert 4470 points

    Hi,

    It sounds like either a broken CC Debugger or a driver problem. Does the CC debugger show up in the device manager on your pc, and if yes how?

    Maybe you could try to install latest version of SmartRF Studio, and then manually 'update driver' from the device manager and point it to the drivers folder that gets installed with SmartRF Studio (under C:\Program Files\Texas Instruments\SmartRF Tools\Drivers\cebal)

    Regards,

    Bjørn

  • 0 in reply to Bjørn
    Prodigy 240 points

    Hey,

    Thank you so much for your response. 

    When I connect the debugger to the PC it says, USB device not recognized. Specifically, "One of the devices attached to this computer has malfunctioned. (Windows problem code 43)"

    Yes, I did install the latest version of the smartRF studio and the smartRF flash programmer and manually tried to update the driver but it gives me the same error.

    I want to believe that it's a faulty debugger but as mentioned in my previous post, it works fine on one laptop, but four other pc's don't recognize it. 

    Is it possible for a broken debugger to work fine on one laptop but not work on anything else?

  • 0 in reply to Vivek Ravi
    TI__Genius 12900 points

    On the computer where the CC debugger is working:

    - What driver version does the CC debugger use? (Device Manager > Right click on the CC debugger and select properties. Version is listed under the Driver tab)

    - What operating system are you running (32bit / 64 bit)

    What are the differences between the working pc and the non-working ones (OS, driver version, SmartRF software versions)?

    Br,
    ABO 

  • 0 in reply to TIABO
    Prodigy 240 points

    Hello,

    Here are the specifications of the OS and software for the computer on which CC Debugger is working:

    Driver Version: 2.50.0.0 (11/01/2010)

    OS: Windows 7(version 6.1) 64 bit

    smartRF studio version: 1.6.1

    On the computers that cc debugger that does not work on:

    Driver version: Every time I connect the debugger to any other machine I get a windows error saying USB device not recognized."Windows has stopped because it has reported problem 43". When I look at driver details it says that it has installed a Microsoft driver(version: 6.1.7601.17586) by default. So I uninstall this and manually update the driver to the cebal drivers that are on the system but when I do it says, device driver software not successfully installed. please consult hardware manufacturer.  I have no idea what to do beyond this point.

    OS: we've tried installing it on windows 7(64 bit) and windows xp. No success.

    smartRF studio: version 1.9.1(latest)

    I hope this information can help you in giving me some insight into this problem.

    We are stuck trying to find out why this is working on one machine and isn't working on others. And the TI distributor that we bought the debugger from does not have it in stock right now so we can't even get a new one. 

    regards,

    V

  • 0 in reply to Vivek Ravi
    TI__Genius 12900 points

    Hi Vivek,

    Looking through the post, it does sound like a hardware issue, some kind of short circuit maybe, that causes a too high current consumption or e.g. poor D+/D- signalling.

    Br,
    ABO 

  • 0 in reply to TIABO
    Prodigy 240 points

    Thank you for your help! 

  • 0 in reply to TIABO
    Prodigy 10 points

    Hello guys,

    I got the same symptoms as described by Vivek Ravi. CC Debugger was working on some PCs/Laptops and not working on others.

    TIABO, you are right there is a hardware issue. At least in my case. The problem was in TPS79333 (U3) which had 4.5 V on its OUT port instead of 3.3 V. We replaced the TPS79333 and CC Debugger is now working just fine. Windows (XP x86, 7 x64) is now recognizing it without a problem.

    Best Regards,

    Al Darmonski

  • 0 in reply to Alexander Darmonski
    Prodigy 20 points

    I also had a similar problem as described (but I only have one computer to test on).  After a couple of faithful years, one day my CC Debugger stopped showing up, and Windows (7, 64 bit) gave a "Device Malfunctioned" message.  I opened up the debugger, and found the main voltage regulator U3 to be getting very hot.  The output of U3 was only 1.7V when connected to USB, instead of the 3.3V expected from the device.  With U3 in circuit (and powered off), I measured ~17 ohms to ground.  Oh no! Something has shorted!  I removed U3, and fortunately the short was in the regulator device itself.  With U3 off the board, I still measured 17 ohms between pins 2 and 5, while the board VDD to ground measured >100kOhm. 

    I didn't have a TPS79333, but I did have an ADP150AUJZ-3.0 laying around. These parts have the same pinout (SOT-23-5 regulator), even if my part was only a 3.0V device instead of 3.3V. Since my target runs at 3.0V, I thought I would give it a try. Sure enough, after replacing the regulator the CC-Debugger works fine once again.  

    The CC-Debugger was just sitting in a box since the previous use last week, I'm not sure what damaged the regulator.  Maybe surge currents when plugging it in?  I will say thanks to TI for providing schematics even for the Debugger, so many vendors don't think this sort of thing is important, but I would have lost a couple of days waiting for a new one without the schematic (and this post!).

  • 0 in reply to JustinM
    TI__Genius 12900 points

    Good to hear you solved your issue, and thanks for the feedback!

    Br,
    ABO 

  • 0
    Prodigy 50 points

    Hey!

    I am facing a similar problem.I am trying to use the CC debugger to program a few demo applications to the CC2540DK-MINI using the RF flash programmer.

    When I connect the CC Debugger to the PC I get an error from windows stating  that the USB device not recognized.  Specifically the error says that "One of the USB devices attached to this computer has malfunctioned".  It says windows has stopped the device because it has detected problems( code 43).

    I tried to resurrect it according to the steps given in CC debugger user guide but all failed. Now its blinking a red continuous light while the PC still shows it to unrecognized USB device.

    Has anybody faced this issue? I would really appreciate any help regarding this. I am using 32 bit windows XP.

  • 0 in reply to Mansimran Benipal
    TI__Genius 12900 points

    Hi,

    Can you be specific of where the resurrecting of the CC Debugger went wrong? And, explain the setup you used?

    Br,
    ABO 

  • 0 in reply to TIABO
    Prodigy 190 points

    I had similar problems with the cc debugger not showing up right because of a broken vreg.  I found a workaround by connecting it thru a usb hub where it is working in spite of having 4.8vdd on a uc that is rated for 3.6vdd max.