• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 1335 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.

CC2652P: CC2652P Overconsumption problem

Mauro Hernan Castro
Prodigy 175 points
Part Number: CC2652P
Other Parts Discussed in Thread: LAUNCHXL-CC1352P, CC1352P

Hi!

6 months ago using TI LAUNCHXL-CC1352P design reference, we implement a CC2652P Zigbee transceiver on our IOT product. We have manufacture about 4 thousand units of it.

Last week, one of our client notify us about high temperature on the equipment, specifically in the area where the zigbee transceiver is located.

Checking all the units produced, I could see that between 10-15% of the units, there was an over consumption of 160-170 ma. If we take into account that the total consumption of the equipment in stand-by is 150 mA, we are talking about the equipment with problems doubling the normal consumption, very serious. This comsumtion is registered on the 12V power supply. 

Investigating the equipment with overconsumption, I was able to verify that the problem is being generated in the Zigbee transceiver. (when we disable the module, or keep it reset, the overconsumption dissapear).

I couldn't find any problem in the PCB layout, nor in the component assembly. Perform the change of the IC CC2652P in 2 units with problems, and after the change they stopped presenting overconsumption.

Hardware Schematic

Firmware

The code that we are programming on the IC is the "znp_CC1352p_2_LAUNCHXL_tirtos_CCS" that comes with the CCS, we implment the configurations that you recommend on a previous thread for CC2652P

Let me know the additional information that I can provide.

Mauro.

  • 0
    TI__Mastermind 37805 points

    Hi Mauro,

    It sounds like you might need a more formal design review from us. Can you follow the instructions on the page I have linked below so we can get more information and help you debug this please.

    https://www.ti.com/tool/SIMPLELINK-2-4GHZ-DESIGN-REVIEWS 

  • 0 in reply to Nathan Block
    Prodigy 175 points

    Hi Nathan,

    Thanks for your answer. I want to add info that we are getting from the test that we are running. We disable the Internal DCDC by hardware or firmware and the overconsumption disappear. 

    Firmware

    Hardware

    Removing L11

  • 0 in reply to Mauro Hernan Castro
    TI__Mastermind 37805 points

    Hi Mauro,

    Thank you for the information, let me also ask you an additional question:

    Are you able to take one of the chips that's displaying the high current draw, re-solder it onto a PCB that was displaying the normal current draw, and see if you get the same high current? This will help us identify whether the problem is on the IC or the board. Typically higher than usual currents are a result of parts not being soldered correctly. 

  • 0 in reply to Nathan Block
    Prodigy 175 points

    Hi Nathan,

    Yes, on Monday I did the test you are mentioning. I started with 2 boards, one with overconsumption and another that worked correctly. Previously, the performance of both transceivers  was checked. Then I proceeded to the exchange of the CC2652P ICs. Once the change was finished I turned on both boards, and the overconsumption problem was transferred along with the IC. That is, the problem went from one board to another.

    Thanks!!

    Regards,

    MHC

    Hardware Engineer

  • 0 in reply to Mauro Hernan Castro
    TI__Mastermind 37805 points

    The next thing we'd suggest is an X-ray of a bad board looking into the IC. We want to see if there is significant voiding of the IC soldered to the board. The IPC standard is <30% voiding. Let's take this offline though, as it's likely going to be a more in-depth discussion.

    I'm talking to some experts internally about your issue, and we'd like to get more information about your schematic/layout...etc. Can you follow the instructions in that design review link above please so we can do that. We'll continue to communicate through that channel and get your issue to the right people.

  • 0 in reply to Nathan Block
    Prodigy 175 points

    Hi Nathan, 

    Yesterday I request the Formal Design Review. We don't have the equipment to perform the last test that you request. I will ask my PCB/PCBA supplier if they can perform that. If it's possible, I would like to leave this thread open, I don't think this was solved at all.

    Thanks!

    Regards.

    Mauro

  • 0 in reply to Mauro Hernan Castro
    TI__Mastermind 37805 points

    Thank you for filling out the review - I can now see it in our internal system. I'm happy to leave the thread open, but I'll be corresponding with you over the design review channel. My team and I will be reviewing the materials you've sent and will get back to you shortly.

  • 0 in reply to Nathan Block
    Prodigy 175 points

    Hi Nathan,

    I Notice on the CC2652P errata document that there is some issue with the DCDC converter. 

    This behaviour isn't the problem that we are having, just caught my attention, because it is the same module that we are having problems with.

    BR,
    Mauro
  • 0 in reply to Mauro Hernan Castro
    TI__Mastermind 37805 points

    Hi Mauro,

    Thank you for submitting the materials. I plan on reviewing them in greater detail this week, one thing that did catch my eye early on was that the inductor listed in the BOM you've connected to the DCDC converter is 6.8 nH, whereas the value we specify in the design guide (page 11) is 6.8 uH. While I don't yet have an explanation for why this is only a problem for the 10-15% of your devices, I do wonder what would happen if you changed it to the 6.8 uH value in the spec. Could you take a faulty board and try changing out the inductor for a larger one? I'm not sure if this would completely solve your issue, but I think it's worth investigating.

    Best,

    Nate

  • 0 in reply to Nathan Block
    Prodigy 175 points

    Hi Nathan,

    Yesterday I make the replacement of the inductor on two troubled boards, and the overconsumption dissapear. Apparently the wrong inductor, causes a malfunction of the internal DCDC converter of the CC2652P generating an over consumption.

    Likewise, if possible, I would like you to complete the formal review, in case any other recommendation or design modification arises.

    Thank you!

    Regards,

    Mauro