• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 190 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Compilation problem after modifying key_writer of AM62x secure version (Secure Boot)

Louis_Vertiv
Intellectual 260 points
Part Number: AM625
Other Parts Discussed in Thread: SYSCONFIG

Hi, 

    I configured MCU_GPIO0 according to the following configuration example.syscfg, and reported the above error. This is your standard code. Why did such an error occur?

  • 0
    Intellectual 260 points

    Hi, 

      The following is the part I changed:

  • 0 in reply to Louis_Vertiv
    TI__Guru 56971 points

    Hi,

    It looks like you are manually editing the Sysconfig file which is not recommended. Please use the Sysconfig GUI to add & configure any modules.

    For now, the following declaration in the Sysconfig file should resolve the error

    Fullscreen
    1
    gpio1.useMcuDomainPeripherals = true;
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 260 points

    Hi, Shivhare:

        Thank you very much. There was a problem with my previous understanding, so I changed the file directly. The Sysconfig GUI version used was different. Your reply made me enlightened.

        Currently, on our board, I use key_writer's tiboot3.bin, which can already control GPIO and light up the LED, proving that I can control VPP for key_writer program.

        Currently, there is a very difficult problem. Our safe version only has 2 templates, so if the key_writer is programmed incorrectly, the templates are likely to become bricks.

        I would like to consult with you to see if there is any good way to debug this part. It means programming, which means that the programming error can be recovered, or the programming fails. It can be proved through the serial port that there is no problem with programming.