• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 100 subscribers
  • Views 746 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: Device Naming Convention clarification

Pierluigi Passaro
Prodigy 120 points
Part Number: AM625

Dear Ti Support,

according section 10.1.2 of the SoC datasheet, there are 2 fields named "Functional Safety" and "Security".

Can you please add details about the features related to these 2 fields ?

Also how these fields match with the section and their impact to section 3.3.1.2 of the "Processor SDK Linux for AM62x v08.06.00.42" ?

Thanks

Best Regards

Pier

  • 0
    TI__Genius 9430 points

    Pier,

    What information are you needing? For functional safety, the G in the OPN will indicate Non FuSa where an F indicates it is FuSa enabled.

    For security, a 'G' will indicate non secure, or general purpose. Any other value will indicate that the device is secure and will need to have the steps followed in the linked migration guide.

    Thanks,

    Chris

  • 0 in reply to Christopher Roberts
    Prodigy 120 points

    Hi Cristopher,

    I was actually trying to understand which HW features are included in "Functional Safety" and which are included in "Security".

    Just as reference:

    • can a non Functional Safety SoC support Security ?
    • can a non Secure SoC support Funtional Safety ?
    • which are the expected value of these flags for GP / HS-FS / HS-SE SoCs ?

    Thanks

    Best Regards

    Pier

  • 0 in reply to Pierluigi Passaro
    TI__Mastermind 28035 points

    Pier 

    I am working to get you an answer on the Safety features. 

    For your other questions:
    Security devices support encryption keys that allow the boot image to be encrypted.

    Pierluigi Passaro said:
    can a non Functional Safety SoC support Security ?

    Yes, that configuration is available in the ALW package. 

    Pierluigi Passaro said:
    can a non Secure SoC support Funtional Safety ?

    This combination is not offered 

    Pierluigi Passaro said:
    which are the expected value of these flags for GP / HS-FS / HS-SE SoCs ?

    From the datasheet:

    G = GP
    Other = HS-FS (Field Securable)

    HS-SE (Security Enforced) is a HS-FS HS-FS device with programmed keys 

      Paul 

  • 0 in reply to PaulM
    TI__Mastermind 28035 points

    Previous post edited to correct details. 

  • +1 in reply to PaulM
    TI__Mastermind 28035 points

    Pier

    Following up on the remaining question. 

    The part capabilities are the same but distinctly identified as a functional safety device. The functional safety devices are part of a safety enabling system which includes the device, software, and documentation. 

    --Paul