Unknown revision number from PIDR2 in ROM table

Hi, 

nRF5340_PS_v1.0.pdf has multiple PIDR2 values to denote engineering versions of the chip. This seems to have been removed in subsequent product specifications, and now has a single value of 0x0000001C (is that rev 1 ?). However, I got my hands on a chip whose PIDR2 value has 0x0000006C and that does not match any specification (1.0 to 1.2). PS 1.0 has upto 5C for EngD . Could you help identify what 6C maps to?

Parents
  • Hello,

    If your chip isn't an engineering version you can look away from this register. 

    I don't know what 6C maps to, but it is not something that you need to worry about. 

    Best regards,

    Edvin

  • If your chip isn't an engineering version

    That is what I am trying to figure out in software without looking at the the markings on the chip, and is the primary reason I'm interested in knowing what 6c corresponds to, given it doesn't feature in any PS. Hence, I cannot look away from this register.

  • Sorry. I haven't found any registers that can differ the latest engineering sample from the production chip (which to be fair is the same chip). 

    I understand that you want to do this check, but in reality, it is not a common use case to do this in production, as the engineering samples are not to be used in production.

    If there exists some hidden register I don't know about that could actually say whether or not it is an engineering sample, I wouldn't be able to provide any more information than what is in the Product Specificaton. If you really need that information, you would have to sign an NDA to disclose this. 

    However our R&D team responded to my question with something like "customers shouldn't really do these checks themselves. We do the checks in the MDK (part of the SDK) to decide what erratas/anomalies to apply and which to not apply. You shouldn't have to worry about it. 

    If there is an issue that you encounter, then please let us know, and perhaps we can come up with a solution for it.

    PS: We are short staffed due to Christmas Holidays from now until the beginning of January. I will be out of office from tomorrow. If this is an urgent issue, please create a new ticket (you can point to this one for background information). If you reply to this ticket, I will look into it in the beginning of January.

    Best regards,

    Edvin

Reply
  • Sorry. I haven't found any registers that can differ the latest engineering sample from the production chip (which to be fair is the same chip). 

    I understand that you want to do this check, but in reality, it is not a common use case to do this in production, as the engineering samples are not to be used in production.

    If there exists some hidden register I don't know about that could actually say whether or not it is an engineering sample, I wouldn't be able to provide any more information than what is in the Product Specificaton. If you really need that information, you would have to sign an NDA to disclose this. 

    However our R&D team responded to my question with something like "customers shouldn't really do these checks themselves. We do the checks in the MDK (part of the SDK) to decide what erratas/anomalies to apply and which to not apply. You shouldn't have to worry about it. 

    If there is an issue that you encounter, then please let us know, and perhaps we can come up with a solution for it.

    PS: We are short staffed due to Christmas Holidays from now until the beginning of January. I will be out of office from tomorrow. If this is an urgent issue, please create a new ticket (you can point to this one for background information). If you reply to this ticket, I will look into it in the beginning of January.

    Best regards,

    Edvin

Children
No Data
Related