• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 313 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.

CC2652R: What is the best practice for MCU Serialization in product line?

user5908057
Prodigy 60 points
Part Number: CC2652R
  1. MAC address is a kind of unique ID, but for some reason it's not enough for our purpose 
  2. Found that MSP Gang can do serialization for MSP430 chip, but not for SimpleLink MCUs. 
  3. in TI files, it is said there is Device identity: Unique and immutable die ID and Bluetooth address. Is there any API to read this "die ID"?  http://www.ti.com/lit/ml/swpb016a/swpb016a.pdf
  4. The only idea left is: modifying hex file before flashing. Is there something like "best practice" on this?
    1. e.g. which page to choose?
    2. how to prevent these fields been modified after production?
    3. will there be potential impact on OAD image checksum calculation?