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.

AM623: external otp efuse magic word

Part Number: AM623


Tool/software:

Hi, TI expert! 

I have a development environment for am6234, with our own evaluation board.

The software SDK version is PROCESSOR-SDK-LINUX-RT-AM62X-08.06.00.42.

From the image below, it can be seen that otp mmr 31 has 2 bytes used to store magic words.


May I ask which magic words are defined in addition to 0xEBC8 that ROM can recognize? What are the enumeration values for magic words and from which document are they from?

The image is from the following link:

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1235880/faq-how-to-update-ids-usb-pcie-pid-vid-mac-id-by-programming-extended-otp-on-am6x

Regards,

Li

 

  • Hello Li,

    The assigned expert is currently out of office. Please expect responses in few business days.

    Regards,

    Vaibhav

  • Hello,

    That is the only magic word defined. The usage is described below (quoted from the FAQ)

    Upon SoC RESET, ROM reads extended OTP array from the end to determine if various device IDs (USB VID/PID, PCIe VID/PID, MAC ID) are programmed into the extended OTP efuse. If the extended OTP data matches the ID update magic word then ROM will process the values from the extended OTP efuse, and updates these values into control MMRs (See TRM for control MMRs for USB, PCIe, MAC ID).

    Regards,

    Prashant

  • Hello,
    “That is the only magic word defined”,Where can I find this sentence in the official document? My client doubts the authority of this statement.

    Regards,

    Li

     

  • Hello,

    The magic word is mentioned in the OTP Keywriter user guide. The ROM reads the Extended OTP MMRs for only one purpose of identifying if the programmed values are to be interpreted as device IDs & so there is only one magic word defined.

    Regards,

    Prashant