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

Problems while programming CC1110F32 using CC debugger

FORBIX SEMICON
Prodigy 100 points

Hello,


1. We are facing similar problems where nearly 5% of 1K units of CC1110F32 (~45-50 every month) are not getting detected by the CC debugger.  It shows Red LED glow.  Rest of the times Green is proper.  Programming wires are ~10-15cm.  Initially we assumed this is a soldering malfunction, but now we realize this is a chip malfunction.  The CHIP ID read from the RED LED (at CC debugger) is different from the GREEN LED glowing ones.  We do not repair the faulty module but just destroy them.  We incur loss in our production for such malfunctions.  Is there a way, in which these parts can be repaired?

2. Recently, we have started seeing another problem, where CC debugger shows GREEN glow on LED properly but then when we try open RF Studio, a error window pops up that says - USB connection failure to the chip.  We do not know what is the reason for such a failure.

We do not want to share our PCB design artwork & component values on this public forum.  Will you be needing it for proposing us the solution for such a failure?  We have custom tweaked the RF cap & inductance tracks to get the max performance out of the chip.

Your help is really appreciated?

 


Design Engineer 

FORBIX SEMICON
www.forbixsemicon.org

  • 0
    Guru 31280 points

    Hi,

     

    It happens even if you trying this with another CC debugger?

  • 0 in reply to Igor Sherer
    Prodigy 100 points

    We are not sure, as we have used (& continue to use) only 1 unit till now.  We will order another one for sure, if you suggest so.  

    But wondering what can be the problem? Same PCB, same quality , same tracks - some CC1110 parts fails (rest passes).  Anything that comes to your mind right away?


    - Design Team

  • 0 in reply to FORBIX SEMICON
    Guru 31280 points

    Well, nothing much, as per your description the faulty PCBs came from the same assembly

    set as the working ones.

    Can you run several tests on the faulty PCB (and compare it with a good one):

    1. Supply voltage on all the AVDD and DVDD. Make sure you are measuring voltage
      on cc1110 pins, not the tracks (cold soldering happens).
    2. Debugging interface (CC1110 side)
    3. What is the voltage level on DCOUPL pin? is it 1.8V?
  • 0 in reply to FORBIX SEMICON
    Prodigy 100 points

    Another point which we want to bring up for your information:

    We have developed another system (with CC1110F32 master and FTDI232 + USB) which we use to program module CC1110F32 (slave).  The master CC1110 is 1st time programmed using CC debugger & then this master unit generates appropriate signals (as instructed via USB/RS232) for programming slave CC1110 (via the 5 pins).  All slaves are our production parts. Therefore, we are happy working with 1 CC debugger.

    So when a particular module (slave CC1110) shows LED RED on CC debugger, it also shows FAIL in write & verification of slave CC1110 using our custom programmer.  This made us come to the conclusion that the slave CC1110 parts are bad.  Is our assumption true?

  • 0 in reply to FORBIX SEMICON
    Guru 31280 points

    It can be the part or the PCB, at this point all options should be included.

    However, it is very unlikely that so much devices are faulty.

    It means that TI don't perform quality checks (impossible if you ask me)

    1 faulty device out of 1M working devices sounds way better then 50 faulty out of 1K,

    don't you think?

     

    By the way, this is actually proves that the CC Debugger working properly.

  • 0 in reply to Igor Sherer
    Prodigy 100 points

    Sounds logical.  We would revisit your points 1 & 3.  Point 2, we do not understand, what you meant.  We are off for next few days.  I'll get back to this same letter thread on our observations.  Thanks a lot for reading and replying us.

  • 0 in reply to FORBIX SEMICON
    Guru 31280 points

    You are right, point 2 should be explained in more detailed way.

    By debugging interface I mean those 5 signals needed for 

    flushing the flash or debugging cc1110. What I suggest is actually

    to check whether the signals on these pins are as should be by

    the spec. Especially check if there any interferences on these pins

    that can change the logic and thus making the flushing process 

    impossible to make.

  • 0 in reply to Igor Sherer
    Prodigy 100 points

    I understand your point very well.  We were just avoiding/postponing the painful process of debug till now.  But looks like - no pain no gain.  We will get back.

  • 0 in reply to FORBIX SEMICON
    Prodigy 100 points


    Hello,

    We are back with all our test results.

    1. Most of the failing chips were because of dry soldering or short points.  Either AVDD was not connected or some places 56K was grounded etc.  For the correct ones RBAIS is1.8V & DCOUPL  is 1.2V.  We have rectified a good amount of them.

    2. Still there remains a bunch of other modules, which are passing (1) above but still showing a RED LED on CC debugger.  These units continue to fail in our custom programmer too.

    Anyway, thanks a lot for your help.

    We will get back to you incase we have more questions.


    Design Team,

    FORBIX SEMICON