AM623: Question on OTP Keywriter for Yocto build

Part Number: AM623
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hi,

I am currently working on creating the OTP keywriter for AM62x. I’ve successfully built the AM62x keywriter using the MCU+SDK and OTP Keywriter tools, and I’ve also managed to program the key into the fuse and boot up successfully.

As a common team, we build our images using Yocto. To streamline the build process for both the images and the keywriter—especially for our partners—I would like to integrate the keywriter into the Yocto build. This would eliminate the need for them to manually install the required tools and build the keywriter themselves.

I’ve looked through some forums and understand that the OTP keywriter currently works only with the MCU+SDK.
OTP Keywriter build workflow - Processors forum - Processors - TI E2E support forums

Here are the questions:

  1. Is it possible to integrate or install the required tools (AM62x MCU+SDK, SysConfig, TI ARM CLANG) MCU+SDK in our Yocto build. If yes, how can I integrate these tools during the Yocto build?
  2. May I know why is the OTP keywriter tool not supported in Yocto build environment? Is it due to security concerns? Understanding this would help me explain to the team why building the keywriter with Yocto might not be feasible.
  3. As mentioned in the OTP Keywriter build workflow above, I would like to clarify: Is it acceptable to store the installed Keywriter tool in a private Git repository, especially if we’ve made modifications to adapt it for our custom board?

Thanks.

  • Hello,

    Is it possible to integrate or install the required tools (AM62x MCU+SDK, SysConfig, TI ARM CLANG) MCU+SDK in our Yocto build. If yes, how can I integrate these tools during the Yocto build?

    We do not have the Yocto support for these tools so we can not confirm the feasibility of integrating these in Yocto.

    May I know why is the OTP keywriter tool not supported in Yocto build environment? Is it due to security concerns? Understanding this would help me explain to the team why building the keywriter with Yocto might not be feasible.

    The keywriter package is built on top of the MCU+ SDK which does not have Yocto support so the keywriter inherits that as well.

    As mentioned in the OTP Keywriter build workflow above, I would like to clarify: Is it acceptable to store the installed Keywriter tool in a private Git repository, especially if we’ve made modifications to adapt it for our custom board?

    It is okay to modify the keywriter source code for the custom board. Please refer to the LICENSE for more details.

    Regards,

    Prashant

  • Hi  ,
    Thanks for the quick response.
    I will figure out if I able to install these tools in our Yocto build.

    I couldn't find the LICENSE in the OTP Keywriter tool. Is the LICENSE same as TI MCU+SDK? Do you have the reference link for the LICENSE?

    Thanks.

    Regards,

    Ooi, Yoong Chean

  • I couldn't find the LICENSE in the OTP Keywriter tool. Is the LICENSE same as TI MCU+SDK? Do you have the reference link for the LICENSE?

    You should get the LICENSE while installing the keywriter package.

  • Thanks, I able to get the LICENSE during the installation.