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.

CC1110-CC1111: CC Debugger fails to connect to CC1110

Part Number: CC1110-CC1111
Other Parts Discussed in Thread: CC-DEBUGGER

Hello! I am opening this issue to ask for support with the CC1110 what we are using in a custom layout/custom firmware application. We use the CC-Debugger to load our own bootloader onto this board, and then we flash our application via UART. Recently one of our boards stopped interacting with the debugger. The debugger light glows red, and the debugger is known to be good and running the latest firmware, as it interacts fine with other boards. The problem board still runs our firmware and accepts a new application over UART, just does not accept a new bootloader from the debugger. In the past this board had no issue with interacting with the debugger. To our knowledge, there has been no physical or electrical damage done to the board in question. The board also features ESD protection diodes on the debugger lines and has only been handled in an ESD safe environment (mat/strap). Is there anything which could be causing this behavior? With the chip shortage, we are not very inclined to just write off the board and replace the CC1110 with the new one, unless we know that we can prevent this from happening in the future.

Altium project: gitlab.com/.../poc-transciever

Good connection logic analyzer capture - known good board:

Bad connection logic analyzer capture - problem board:

Reset line works fine - button presses on reset are observed on logic analyzer:

The voltage levels on the relevant pins have been measured and found to be correct.

  • Are you not able to detect the CC1110, or are you detecting the board, but are not able to program it?

    If you have several identical boards, and one is not being detected by the debugger, I would assume that the problem is HW related.

    If the board is detected, but you are not able to program it, could it be that Flash has been write protected?

    To determine if it is a HW problem, you could simply take one good board and one bad board, and swap the CC1110's to see if the problem follows the board itself or the device.

    Siri

  • Thank you. Based on your description, it seems like this is a device problem. I am certain that if we swapped chips, it would work. With the CC1110 in short supply, I just wanted to see if anything could cause the debugger interface on the CC1110 damage before I use up a good chip to revive the board again.