• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 56 subscribers
  • Views 385 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.

CC2530: How long the code can be saved after the chip is burned and then reflow

Cherry Zhou
Mastermind 22235 points

Part Number: CC2530

Hi team,

Here's an issue from the customer may need your help:

The CC2530 chip is burned before reflow. The product is rigorously tested before it leaves the factory and is no problem. After about two years, 20 percent of the chips cannot work when they were powered up.

They've done the following test: verify the hardware first, each voltage output is good, and the chip is powered properly. And then reburn the abnormal product code and return it all to normal.

The customer suspect this issue is related to the missing code of the chip. Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Mastermind 38575 points

    Hi Cherry,

    Three questions for you to help us diagnose the problem:

    1. Can you clarify the issue? Are you saying that when they take chips that are not working, reflash the original code onto them and power them back up then they start working again?

    2. What is abnormal about the product code?

    3. What missing code are you referring to here?

    Best,

    Nate

  • 0 in reply to Nathan Block
    TI__Mastermind 22235 points

    Hi Nate,

    Thanks for your help.

    Nathan Block said:
    1. Can you clarify the issue? Are you saying that when they take chips that are not working, reflash the original code onto them and power them back up then they start working again?

    Yes, after reflash the original code, it can go to work again.

    Nathan Block said:
    2. What is abnormal about the product code?

    It cannot be read again because the lock was applied during the burn. It can only be determined through the external pin that the code segment is missing. After reburn, it's good. And they have also verify the peripheral circuit is ok. So it should be an internal code missing issue.

    Nathan Block said:
    3. What missing code are you referring to here?

    The missing code in code memory area inside the CC2530 chip.

    Also, the possibility of the error occurring is a little bit large, and the situation is basically same. 

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Guru**** 223927 points

    Hi Cherry,

    What is the customer's application, does it ever write to flash memory during operation, and is the device ever susceptible to low power conditions or ESD?  I'm attempting to determine whether abnormal voltages could cause corrupt flash memory writes.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Mastermind 22235 points

    Hello Ryan,

    Ryan Brown1 said:
    What is the customer's application,

    Wireless control panel switches.

    Ryan Brown1 said:
    does it ever write to flash memory during operation

    It cannot operate.

    Ryan Brown1 said:
    and is the device ever susceptible to low power conditions or ESD? 

    There are no low power requirements, the supply output current capability is 1 A, and the voltage output is 3.3 V.

    Ryan Brown1 said:
    I'm attempting to determine whether abnormal voltages could cause corrupt flash memory writes.

    And may I know is there anything new for this question?

    Also, if the application layer does not write a value to a specific flash address, does the abnormal voltage cause a flash write to the wrong value?

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Guru**** 223927 points

    Cherry,

    I meant to pose my question as such: Does their application purposely write to flash memory using operations like HAlFlashWrite?  Flash writing at voltages lower than 2.2 V could be susceptible to corruption.  You mentioned a wireless application, is this a proprietary radio or are they using a stack provided by TI.  If so, what type and which version?  Are they able to replicate the issue without locking the device and thus more closely debug the issue and observe its memory changes?

    Regards,
    Ryan