• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 1387 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.

MSP430F5510: Shelf Life of ICs

Atul Bhakay
Genius 3205 points
Part Number: MSP430F5510


Dear Sir,

We have just received a bulk order of one of our product which is using MSP430F5510IRGZT. As per our records, around 200 ICs are available with us. But when we try to use them in the product, the microcontroller seems to misbehave. During various troubleshooting, we checked the label and found that the ICs have been packed on date 03/05/14. We have purchased them in 2015 from Texas Instrument's authorized distributor.

 

Request you to please let us know whether the issue can be because of older ICs? If yes, please let us know what is the shelf life of the IC in question

Regards

Atul Bhakay

  • 0
    Guru 26200 points
    Hello Atul,

    misbehave? What do mean?

    MSPs, when working with silicon temperatures below 80-90 degC, us I remember, should work for 10+ years.
  • 0 in reply to Tomasz Kocon
    TI__Expert 5490 points

    Hi Atul,

    the packaging of the MSP430 are rated at MSL Level 3. The MSL level are specified in JEDEC J-STD-020E (may need to register it is free). This MSL level is mainly used for production as humidity can get into the device package and damage the device during soldering.

    Your error description is rather general. Can you please specify what is failing?

    Can you please let us know the marking on the package of the failing devices and the devices which are working?

    Best regards,

    Andre

  • 0 in reply to Andre Frantzke
    Genius 3205 points
    Dear Sir,
    Given below is the reply to your question on this subject matter
    "Your error description is rather general. Can you please specify what is failing? "
    In most of the cases the microcontroller is unable to give 3.3V regulated output. Instead, it gives random output voltage below 3V say 2.7V or 2.2V or something even below that. We even tried to solder only the microcontroller and only other required components on multiple boards and in that case also we got the same issue for almost 60% of of the total boards soldered. Remaining 40% worked normally. FYI, all the boards are from same lot and microcontrollers are also from the same lot.

    "Can you please let us know the marking on the package of the failing devices and the devices which are working? "
    Presently we have only one functional board and multiple boards having problem. Following is the chip marking found on one functional as well as three non-functional chips.

    1. Functional Microcontroller
    MSP430
    F5510
    TI 42K D
    DD48 G4

    2. Non-functional Microcontroller 1
    MSP430
    F5510
    TI42K E
    CE2J G4

    3. Non-functional Microcontroller 2
    MP430
    F5510
    TI 37K D
    AY38 G4

    4. Non-functional Microcontroller 3
    MP430
    F5510
    TI42K E
    CE58 G4
  • 0 in reply to Atul Bhakay
    TI__Expert 5490 points
    Hi,

    thanks for sending the markings. It seems you are using revision D and E. In both revision there is a known issue. Please check the USB9 issue and workaround in the errata document (www.ti.com/lit/slaz301).

    Another thing you should check is the current consumption on VUSB. If it is higher then the allowed maximum (12mA) then the voltage may no reach the correct level.

    Best regards,
    Andre
  • 0 in reply to Andre Frantzke
    Genius 3205 points
    Dear Sir,
    Thanks for your quick response.

    We have checked the USB9 issue along with the workaround in the errata document, but we feel it does not apply in our case. The document says that the "VBUS detection may fail". However in our case, the VBUS is always getting detected and we are also getting some voltage as LDO output on VUSB pin. The only issue we are facing is that instead of giving 3.3V output, LDO gives output voltage between 1.2 V to 2.7 V. In addition, we are not even able to program the microcontroller in absence of proper voltage. So unable to test the workaround of clearing the USBPWRCTL register in order to let it retry the detection of VBUS voltage.

    At present, we have soldered only the microcontroller and adjacent capacitors. The 3.3V LDO output is only connected to the microcontroller power input line. As per datasheet, the maximum current consumption of microcontroller shall be 6.5 mA which is way below the LDO current supply limit of 12 mA. However we are trying to measure actual current which may take some time as we will have to remove some tracks on board. We shall update you soon with actual current consumption.

    Meanwhile, request you to please let us know in case you feel there can be any other issue.

    Regards
    Atul Bhakay
  • 0 in reply to Atul Bhakay
    TI__Genius 14165 points
    Atul,

    Andre's input for USB9 is valid please refer to the workaround section for bus powered systems.

    However, if the integrated 3.3-V USB LDO (the output of the VUSB pin) is used to power
    the device's DVCC pin, as in many bus-powered applications, and if the rare bandgap
    error occurs, the CPU fails to power up, because the USB LDO fails to operate. The
    problem might be resolved by cycling power to the VBUS pin; for example, if the end
    user responds to the failure by unplugging and replugging the USB cable. The bandgap
    failure is also known to occur more often with slow DVCC ramps > 200 ms; for example,
    when there is excessive capacitance on the DVCC pin, in excess of what the USB
    specification allows. However, the only sure way to prevent the problem from occurring
    in the first place is to avoid making DVCC power reliant on VUSB.

    Can you please try to cycle the power faster maybe removing some caps on your board and checking the LDO output again?

    The other thing is regarding soldering! If you opened the package the humidity label most probably was not blue anymore but red correct. This means your normally need to bake the parts before soldering to prevent any delamination issues inside the package. The problem can be that humidity inside the package expands quickly if solder heat is applied rapidly.

    Best regards,
    Dietmar
  • 0 in reply to Dietmar Walther
    TI__Expert 5490 points
    Hi Atul,

    do you have further questions? If not, please select "Resolved" for the post that solved your issue so this thread can be closed out.
    Thanks a lot!

    Best regards,
    Andre
  • 0 in reply to Andre Frantzke
    TI__Expert 5490 points
    Hi,

    I suppose that you were able to move on with your application as you didn't reply anymore, so I'll close this post.
    Please feel free to comment again if you look for further assistance, it will re-open the thread.

    Best regards,
    Andre
  • 0 in reply to Andre Frantzke
    Genius 3205 points
    Hi,
    As per our communication, we thought to disconnect VUSB pin from input voltage pins (DVCC and AVCC) in order to check whether the voltage is getting dropped due to excess current or due to some other reason. During troubleshooting, we found that even if VUSB pin is disconnected from all other pins, the voltage we received over VUSB was same as earlier i.e. 1.5 V in this specific case. We then checked voltage on the input voltage pins (DVCC and AVCC) and shocked to found that they are also giving 1.5 V, even though they are physically disconnected from VUSB pin.

    This points us to believe that the exposure of chips to humidity has permanently damaged them because of higher soldering temperature. However, to confirm the same, we will have to bake remaining ICs and then check if all of them are working as desired
    Hope that we are on the right path
    Regards
    Atul Bhakay
  • 0 in reply to Atul Bhakay
    Genius 3205 points
    Hi, Kindly do not close this thread yet.
    Regards
    Atul
  • 0 in reply to Atul Bhakay
    TI__Expert 5490 points

    Hi Atul,

    I'm closing this thread. Please use the "Ask a related question" button to refer to this thread.

    Best regards,
    Andre

  • 0 in reply to Andre Frantzke
    TI__Expert 5490 points
    Hi Atul,

    what further information do you need?

    Thanks,
    Andre

**Attention** This is a public forum