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

Trouble connecting with new CCDebugger hardware

Glenn Monroe
Intellectual 330 points
Other Parts Discussed in Thread: CC1101

I have been testing some of our units that use a CC1101 using a CCDebugger that we have had for a while.  Everything works well.  However, I ordered two more CCDebuggers , and neither of them work to connect to our hardware.  The CCDebugger is recognized, but the CC1101 conected to it is not.  The LED remains red.  Is there some sort of update that I need to do to the firmware in order to get them to work?  If it had only been one I might be inclined to blame it on bad debugger HW, but since it's both I'm guessing it's something else.

  • 0
    TI__Guru** 106705 points
    Hi Glenn,

    There has not been any changes to the CCDebugger for a long time. Any chance you could hook an oscilloscope or logic analyzer to the debug signals?

    Regards,
    Fredrik
  • 0 in reply to Fredrik K
    Intellectual 330 points
    Can you give me an idea of what I should be looking for? I am hesitant to start debugging a TI device without any definite instruction.
  • 0 in reply to Glenn Monroe
    TI__Guru** 106705 points
    Since you have both working and not working debuggers you could compare what happens immediately after pressing the reset button on the debugger. If the resulting waveforms on DD and DC are not similar, there is most likely an issue with the debugger.
  • 0 in reply to Fredrik K
    Intellectual 330 points
    I don't have DC and DD connected in most of my boards. However, the board I am testing with does have both of those signals connected. Needless to say, they are not the problem if the boards without them work fine with the older CCDebugger.
  • 0 in reply to Glenn Monroe
    Intellectual 330 points
    I probed around with an oscilloscope. The DC and DD never do anything anyway. The SPI lines are move when the reset on the CCDebugger is released. This is true for both the working and non-working CCDebugger. I did notice that the non-working debugger does not appear to hold the CS line. When I release the reset it pulses a couple times then goes back low. The working one pulses a couple of times then holds the CS high until the next time I reset it.

    This gets us back to the question of firmware. How can I get the firmware version from the CCDebugger? The CCDebugger boards are the same revision and I am using exactly the same hardware for my product. The only thing left that I can think of is the firmware.
  • 0 in reply to Glenn Monroe
    TI__Guru** 106705 points
    You are of course right about the DC/DD, I though you were using a SoC. Anyway, looking at the SPI signals would be the equivalent and it is interesting that you observe differences.

    In Flash Programmer you can see the firmware version of the debugger (EB firmware rev). You can also update the FW if you want to by changing to "Program Evaluation Board" in the top drop down menu.
  • 0 in reply to Fredrik K
    Intellectual 330 points

    I found the firmware version.  Turns out it was right there on the screen the whole time in the bottom of the window.

    The working debugger has the following information:

    USB Device ID:  0170

    Firmware Rev:  0044

    The non-working debugger has the following:

    USB Device ID:  0890

    Firmware Rev:  0025

    Now the question is how do I uprev to 0044 on the non-working boards.

  • 0 in reply to Glenn Monroe
    Intellectual 330 points
    Nevermind. I solved my own problem. Updating the firmware is done by double-clicking on the CCDebugger listed in the "List of Connected Devices" at the bottom of the SmartRF window. This successfully updated both of my non-working boards to the same firmware as the working board. They both now work.
  • 0 in reply to Glenn Monroe
    TI__Guru** 106705 points
    Hi Glenn,

    Good to hear that the problem is resolved.

    Cheers,
    Fredrik