• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 599 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.

AM625: RemoteProc and OTP

C.S
Prodigy 50 points

Part Number: AM625

Hi,

I want to run otp functions in r5 core by using RemoteProc.  Is there any limitation for this application?  

B.R.

  • 0
    TI__Guru* 90111 points

    Hello,

    The OTP Keywriter is a ROM bootable application & so it can't be booted using Remoteproc. Also, the OTP Keywriter for it's functionality requires a special TIFS which comes with the OTP Keywriter package itself. This TIFS is different from the usual TIFS delivered with SDKs and are not interchangeable.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Prodigy 50 points

    Hello Prashant

    As a secont option , I want to add OTP Keywriting functionality to tiboot3.bin and when it boots, directly it will run otp keywriting. As you mentioned TIFSs are different, If so, it doesn't seem like it's possible to do it this way, right?

    Is there any other option adding otp key writing functionality in bootloader?  

    B.R.

  • +1 in reply to C.S
    TI__Guru* 90111 points

    Hello,

    C.S said:
    If so, it doesn't seem like it's possible to do it this way, right?

    Yes, it is not possible due to the different TIFS binaries for OTP Keywriter and the usual bootloaders.

    May I know why you want to integrate OTP Keywriter functionality into the bootloaders. The OTP Keywriter is a separate package and should be treated that way only. Also, the OTP Keywriter is a sensitive procedure so it is best to not keep anything unrelated in the OTP Keywriter to avoid any unwanted issues popping up.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Prodigy 50 points

    Hello

    We do not want to use boot models other than emmc, this pushes us to look for alternative options. 
    If it was possible to write OTP keys with commands sent from the command line, it would be very helpful in terms of ease of use.


  • 0 in reply to C.S
    TI__Guru* 90111 points

    Hello,

    Have you evaluated the Options A/B & C suggested in the "AM62x_HS_Key_Programming_Flashing_v2" presentation. The option A/B is particularly suited for eMMC. You can keep the primary boot modes to eMMC while the backup boot modes can be UART, USB DFU or anything. Then, the OTP Keywriting and flashing of the customer signed images can be done over backup boot media.

    Regards,

    Prashant 

  • 0 in reply to Prashant Shivhare
    Prodigy 50 points

    I will check it again, as far as I remember , if there is a customer signed image in emmc then it is not goes to backup boot mode UART for otp key programming bootloader. I tried this on am64-sk hs EVM board. 

  • 0 in reply to C.S
    TI__Guru* 90111 points
    C.S said:
    if there is a customer signed image in emmc then it is not goes to backup boot mode UART

    If the image is valid then yes the ROM will not fallback to UART boot mode. The option A/B is more suited for production where it is the case that the eMMC will be blank so on the very first boot the ROM will not be able to boot from eMMC thus fallbacks to the backup boot media.

  • 0 in reply to Prashant Shivhare
    Prodigy 50 points

    Hi Prashant 

    I try to implement "Booting From Primary media (Option C)" , I prepare a flash image which has otp keywriter (signed with TI keys) @primary boot offset(0x0), and other bootloader which signed with customer keys located at 0x400000 offset. In this option next boot after otp keywriting, boot will fail at 0x0 offset and  device will jump to 0x400000 for booting  right ? 

  • +1 in reply to C.S
    TI__Guru* 90111 points

    Hi C.S,

    C.S said:
    In this option next boot after otp keywriting, boot will fail at 0x0 offset and  device will jump to 0x400000 for booting  right ? 

    The redundant boot is not supported for eMMC boot partitions. It's only supported for eMMC UDA partition. So, if you are using eMMC UDA, then yes on next boot after OTP Keywriting, ROM fails to boot from 0x0 and fallbacks to the redundant boot offset 0x400000.

    Regards,

    Prashant