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.

LP-MSPM0L1306: Identifying a Unique ID For Each Part

Part Number: LP-MSPM0L1306

Dear Support:

I have a customer that because of security reasons, wants to identify a unique number for every MSPM0 device.  From reading through the TRM, there are 3 registers that seem to provide this information: TRACEID, DEVICEID and USERID.  However from reading these registers from 3 different LPs, I'm not making sense out of one I am getting.  For example, from the 3 LPs that I am using, see below:

Device #1:
TRACEID:  0x00000000
DEVICEID: 0x1BB8202F
USERID:     0x80C2DDD3

Device #2:
TRACEID:  0x00000000
DEVICEID: 0x1BB8202F
USERID:     0x80C2BB70

Device #3:
TRACEID:  0x00000221
DEVICEID: 0x1BB8202F
USERID:     0x80C2BB70

From reading through the documentation in the TRM about these registers, it's not clear how these values I am getting map to the bit fields in the registers.  Can you explain what is going on here in more detail and exactly what bit fields uniquely identify a device so that the customer can come up with a value that uniquely identifies a particular device?  In particular, is it the TRACEID and the PART field of the USERID register that uniquely identify a device?  It is not clear what is the meaning of the TRACEID and the VARIANT and PART fields of the USERID register and how these relate.  Can you provide more details here?

Thanks,
Tim

  • Hi Tim,

    Good question. I would think the registers you are reading would provide this information.  Let me check with the product test team.

  • Hi Tim,

    Sorry for the delay.  I'm still trying to track down this information.

  • Hey Dennis:

    Thanks - mainly needing to know what is the meaning of these variable bit fields: TRACEID, VERSION, PARTNUM, PART, VARIANT, etc.  For example, it's not clear what a variant is and how this relates to the TRACEID.  The documentation says that TRACEID should be unique for each device, but that's not what I am seeing.  Just need an better explanation of the bit fields and what they all mean so I can make sense out of what I am reading from the LPs that I have on hand and can relay this to the customer.

    Thanks,
    Tim

  • Got it!  I was given a name of someone on the test team that should be able to help.

  • I have the question but about this and also was thinking the TRACEID would be unique and could be used as a "serial number"

  • Hi John,

    Sorry for the long response time.  From what I'm hearing this is not possible.

    I contacted a different engineer that might be able to help answer the question or provide an alternate solution.  I'm sure this is not the first time a customer has asked this type of question so I'm hoping he can help us.

  • Got my local TI FAE to confirm that the TRACEID is indeed unique to each chip.  I even got one of my engineers to take a peek and confirm and looks like this is true.  Thanks

  • That is not what I am seeing (TRACEID is NOT unique for each chip).  I found that to be the case for several boards I have tested.  Just look at my original post where Device #1 and #2 have the same TRACEID and it is 0 - not much uniqueness about that.  So can we get an explanation what all these fields mean: TRACEID, VERSION, PARTNUM, PART, VARIANT, etc?

    Thanks,
    Tim

  • Hi,

    If what Tim is suggesting is correct, the question then would be "can this location be programmed with the available tools".  I'll bring this up with our tools team.

  • Ok, our SW manager has answered the question:

    The FACTORY region includes 96-bits which can give a unique identity between TRACEID+DEVICEID+USERID.  There could be devices of different families with same TRACEID, but together with the DEVICEID and USERID, it would make it more unique.

    However, it should be noted that this area is non-writable. They could read the contents and use them, but they won’t be able to customize it.

    It could be possible to create a script that serializes the device, but perhaps they could take a look at production programming tools from Elprotronic or PEMicro which already have that capability.

    This is from PEMicro:

  • Hi Tim,

    Our test team is indicating the TRACEID will absolutely be unique for production silicon.  They asked if the ones you were looking at were pre-production units?

  • Hey Dennis:

    I'm pretty sure it was with RevA LPs, but not 100% sure.

    Tim

  • Hi Dennis,

    When you say 'unique for production silicon' is this per device?

    Thanks.

  • Hi Chris,

    According to our Design/Test group:

    USERID and DEVICEID are at least partially documented for the customer in the TRM (see tables below).

    TRACEID is “random” however on pre-production units its not going to be unique (it should be unique on production units, assuming they are units with minorrev = 1 or higher on MSPMOL)

    With respect to “variant” and “part” portion of USERID, this is documented inside of the datasheet

    Based on that, the USERID and DEVICEID end up being “mostly” fixed (will change between orderable part numbers as well as PG revisions), but when mixed in combination with the TRACEID should yield a unique value on production parts.