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 Recognized After Firmware Upgrade

I have the latest version of SmartRF Flash Programmer, and two new CC Debuggers out of the box.  When I plug in the CC Debugger to USB, SmartRF tells me it needs to updgrade the firmware, not unexpected.  I change "What do you want to program?" to Program Evaluation Board, the EB Application (USB) tab says:

EB ID 4427, Chip type NA, EB firmware ID 05CC, EB firmware rev 0027 (note this is what it says now after flashing)  The Flash image is:

C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Flash Programmer\bin\..\..\Firmware\CC Debugger\cebal_fw_srf05dbg.hex

The box nder Perform Actions says it completed successfully. HOWEVER, when I change What do you want to program? to "Program CCxxxx SoC...", it does not recognize the CC debugger any more.  The SOC box is blank.  I get the correct beeps from the PCB when I plug and unplug the CC debugger, and I can go back to program evaluation board and it sees it, but it's never recognized for programming.  I tried my second CC Debugger, and got the exact same issues and result.

Can anyone suggest how to get this to work?  The LED on the CCD just stays red, even after I plug in the target board and processor.

  • As long as the LED on the debugger is red, it will not appear in the flash programmer tool when you have selected to "Program CCxxxx SoC...". The LED has to be green, meaning that it has successfully detected the target device. 

    What device is connected to the debugger? Have you followed the CC Debugger User's Guide (www.ti.com/lit/swru197) instructions for proper target connection?

  • hi 

    I have the same problem. Can you help me out?

  • So you tried to update the firmware on the debugger, but now it is no longer detected by the PC?

    In the flash programmer tool, can you select "Program Evaluation Board" and the "EB Application (USB)" tab? Is the debugger listed there? Is the LED on the debugger red or some other color?

    Have you tried out the troubleshooting hints in the CC Debugger User's Guide (www.ti.com/lit/swru197)? 

  • I dont have EB. But when I run the smart rf flash programmer, it was showing, an old version of firmware is running, update. then i went to the EB tab in the smart rf and did the update. I have no idea where is it updated, is it on the cc debugger? now cc debugger is not recognised at all, neither by the smart rf flash programmer, nor by smart rf studio.

  • the debugger is not listed in any of the tabs of the smart rf flash programmer. and the led is not lit at all.

    I cannot follow the steps for ressuructing the cc debugger, since i dont have another cc debugger or smartrfEB.

  • What's the color of the LED on the debugger?

    Can you see if the debugger is listed in Windows Device Manager? Look for "Cebal controlled devices", as shown in figure 2 in the debugger user's guide.

  • I read the CC debugger user guide. This section talks about what I did.

    8.2 Updating the firmware manually in SmartRF Flash Programmer
    You can also update the firmware manually using SmartRF Flash Programmer. You can use this
    method if you like to have full control of the firmware image to be programmed on the controller of the
    debugger (i.e. programming custom firmware or old firmware revisions).

    1. Start SmartRF Flash Programmer and select the tab called “EB application (USB)”. This tab
    will let you program compatible firmware on the CC Debugger (or evaluation boards) via the
    USB interface (i.e. no external programming device required).
    2. Disconnect the debugger from any target board, and connect it to the PC via the USB cable.
    The debugger will appear in the list of connected devices. Chip type will be listed as N/A.
    3. Select the flash image you want to program on the debugger. Normally, you would select:
    C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Firmware\CC
    Debugger\cebal_fw_srf05dbg.hex1

    4. Select the action “Erase, program and verify”
    5. Click the “Perform actions” buttons. The programming procedure will start. Note that this will
    take several seconds.
    6. The CC Debugger will reappear in the list of connected devices, now showing the new
    firmware revision in the device list.
    7. Done!

    I did not do this manually. I got an alert saying, update firmware and I did so. What went wrong?

  • The led is not lit at all. I cannot see the debugger listed in the device manger also. I tried installing the cebal driver again, even then the cc debugger is not listed.

  • Not sure what went wrong in your case, but the firmware update obviously failed. It should still be possible to resurrect your debugger, even without having another debugger or EB.

    Try out the forced boot recovery mode described in section 8.3 of the User's Guide. Short circuit the two pins and power up the debugger. Does the LED blink?

  • I tried the forced boot recovery as well. the led is still not lit. 

  • So the LED did not start to blink when you plugged in the USB cable while these two pins were connected together?

  • yeah. led did not blink when i connected those pins and plugged the USB.

  • So now what should I do? Is resurrecting the CC debugger the only method left? 

  • See private message.

  • I have the same problem. I tried all aproachs follow the methods in CC debug user guide step by step. but the red LED still solid on. anything else I can do?

  • Have you tried to connect it to a know good system, e.g. a kit from TI?

    Do you have another debugger or a SmartRF05EB you can use to reprogram the assumed broken debugger?

  • I figure out where the problem is. I have to connect the dongle or keyfob into debuger. the LED then turns to green. if you just connect the debug into computer but no device on it, it will always solid red. but in manual, it doesn't mention it (or emphasize it). Hope others have the same problem notice this.

    anyways thanks for the quick response from TI!