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: what's the bare minimum that the security client should do on bootup ?

Part Number: AM625
Other Parts Discussed in Thread: SK-AM62

Hi TI experts,

I'm writing bare metal code on sk-am62, there's a whole driver on the TI SCI Client. Still, I was wondering what's the bare minimum interaction that needs to be done with the security core (I guess system firmware) through the client API at boot time for typical use. By typical use, I mean just providing power and a clock for selected modules and making sure they operate. I do not need to worry about any power management or resource management or low power mode or any other security or resource/power management stuff. 

Please help me in the right direction.

Best,

Seyed (Amir) 

  • Hello Seyed, 

    I am looking at your queries.

    You may expect a reply in one or two days.

    Regards,

    S.Anil.

  • Hello Seyed,

    In AM62X, DM operations will be done by the R5F core, and security operations will be performed by the M4F core.

    In booting time, the boot application will send requests to the DM core for clock, power, and reset, and other than this, any other security control is done by the M4F core.

    Now, you can please reframe your questions, and really, I am not able to understand what you are expecting.

     

    May I know why you wanted to install DM (R5F) firmware on Baremetal instead of RTOS?

    Your R5F application needs to be implemented in Baremetal ?

    Regards,

    S.Anil.