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.

TM4C123BH6ZRB: device Markings definition

Part Number: TM4C123BH6ZRB

Hi Champs,

According to customer feedback, they want to know Line4 internal tracking code meaning. Because they found out they got some TM4C123BH6ZRB chip didn't work properly with same program method. They found the difference between work and didn't work IC is Line4 internal tracking code. Please see below picture.

 Could you please help to check what is the meaning for internal tracking code? thanks!  

   

  • Hi Lisa,

      There is also difference in "74C2" vs "71AR" in the marking. I will find out and get back with you.

  • Hi Lisa,
    You can refer to the section A.3 Device Markings in the datasheet for more details. The fourth line will have the form of YMLLLS. The YM indicates the year and month of the manufactured unit. The LLLS is what we call the Lot Trace Code (LTC). With the LTC, we can trace back which wafer fab lot and wafer the die is from.
    So what is the problem you are seeing between the two different units?
  • Hi Charles,

    Customer will write data into EEPROM after power up device They found out EEPROM data isn't right when first time power up. But after they re-program MCU and EEPORM data is right.... However, they use the same factory image and bring up method. There is no problem in another units. The only difference between M4 is date code. That's why they want to know the meaning of date code. Have you ever heard any issue on those specific date code M4 unit ? thanks!
  • Hi Lisa,
    Not that I'm aware of the batch of units with the same LTC having EEprom problem. I don't have these information. Is it true that after reprogram the MCU and EEprom the second time the problem will never occur again? Does the application write new data to the EEprom after each power up? What happens to all the subsequent times(3rd, 4th...Nth) ? Do they see issue? Do they have other units that exhibit similar problem?
  • Have they verified they are not running into any of the EE errata? They're rather extensive in their effects.

    Robert
  • "Unsafe @ any speed!"

    So ***  LIKE  ***

    (Liked is the cleverness of the "tag" - so (beyond) vendor's "pedestrian/sleep-inducing/advertising" tag-ads.)

    Across multiple ARM families (multiple vendors) - such "performance variation tied to lot" (may) indicate that the user operation is, "too close to spec's edge" - (some/greater) guard-banding (often) "cures."