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

CC1110-CC1111: CC Debugger firmware rev killing device?

Luka Bosnjakovic
Prodigy 40 points
Part Number: CC1110-CC1111


Hello

We have device that has CC1110 and we are programing it with CC Debugger. The problem is that in some case (we don't know all variables) device starts to draw more current that it has to draw. We manage to find out that when device draws to much current pin P1_7 is not functional and we suspect that P1_7 is burned or latched up and current consumption is over that pin. When current drawn is normal pin p1_7 is operational. 

P1_7 is connected to CC Debugger so we suspect that this is main cause of this problem. Further we found out that when we used CC Debugger with FW rev 0025 problem was occuer less times than when we updated CC Debugger to newest rev (0044). I tried to find rev 0025 but this is nightmare because TI provides only lastest FW versions and revisions. Can anyone give me FW rev 0025 to try to verify that FW rev has connections with this P1_7 problem?

We are making devices with worker wired to ground so ESD shouldn't be cause.

Any ideas are welcome.

Thank you,

Luka

  • 0
    TI__Genius 12900 points

    Attaching CC debugger firmware version 0025 for you to try out.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/156/cebal_5F00_fw_5F00_srf05dbg_2D00_0025.hex

  • 0 in reply to TIABO
    Prodigy 40 points

    Thank you for response. We will try and I'll inform you about result.

    Has anyone have indications why would P1_7 burn out. It is always P1_7, that is very odd

    Luka

  • 0 in reply to Luka Bosnjakovic
    TI__Guru**** 317180 points
    I'm not aware of any issue with CCDebugger. Do you have more than one so you can test if you get the same behavior with a different one? It could be that the CCDebugger has been through a ESD event that makes it behave a bit strange.

    Have you tried to flash a different type of board to check if it's something with the hardware design on your board that causes this issue.
  • 0 in reply to TER
    Prodigy 40 points
    We have 3 CC Debuggers and this is happening with all three.

    I downgrade fw on CC Debugger, changed laptop with another laptop and when programming we first connect device GND with CC Debuggers GND than connect debuggers connector for programming and result is that on about 100 devices we all devices are ok (P1_7 problem weren't present). So we think we solve problem but still we are not sure what is the main cause (because we changed 3 factors).

    We have 5 devices with CC1110 and this problem were occure on all range of devices, but all of them were made by same people so we can not say that they didn't make mistake. But I think they didn't because we had about 5-10% devices with P1_7 issue
  • 0 in reply to Luka Bosnjakovic
    TI__Genius 12900 points

    What pin on the CC Debugger is your CC1110 P1_7 connected to?

  • 0 in reply to TIABO
    Prodigy 40 points
    First it was connected to pin 10 on CC Debugger, but when problem was present we remove connection with it, so now P1_7 is not connected with CC Debugger and problem is less present (after restoreing old rev). It looks like it depends on chip series too, because we have pannels without problem (one chip serie) and pannels with problem present in minimum scale (serie different than previous)