TDA4VE-Q1: Flash the Linux image

Part Number: TDA4VE-Q1

Hi Team,

I am currently working on enabling the HSM (Hardware Security Module) on the TDA4VEN / TDA4AEN Jacinto™ Processors.

Could you please share the following:

  • Linux image package
  • U-Boot package
  • HSM/TIFS firmware package
  • Any relevant SDK or security package required for HSM enablement
  • Documentation or references for secure boot and HSM integration

Additionally, I would appreciate guidance on the flashing process, including:

  • Overall boot and security flow
  • Sequence for flashing SBL, TIFS/HSM firmware, U-Boot, and Linux images
  • Which core/subsystem executes the HSM firmware
  • IPC mechanism between application cores (A53/R5F) and HSM
  • Any dependencies, configuration steps, or prerequisites for enabling HSM functionality

Please share the relevant package links and documentation when available.

Thanks & Regards,
Naveenaasre S

  • Hi Naveenaasre,

    These are entry level query and you can find answers for these query on the sdk documentation.

    I would also recommend you to go through TRM to get more understanding on the device offering.

    Note: TI does not provide HSM stack as part of default SDK and development of this should be own by customer or may use any 3P stack like vector HSM.

    Regards
    Diwakar

  • Hi  

    1. In what scenarios 3rdparty/Customer HSM is needed? (why isn't TIFS sufficient)

    2. Can the application-specific keys be stored and managed by TIFS?

    3. Can we have the  Secure boot authentication routed via HSM?

    Regards,

    Naveenaa

  • Hi Naveenaa ,

    1. In what scenarios 3rdparty/Customer HSM is needed? (why isn't TIFS sufficient)

    TIFS is TI foundational security firmware and provided services to support secure boot , run time firewall configuration etc. These are the list of ssecurity features supported by TIFS https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/index.html#secure-management.

    For any advance security feature we need t go with HSM stack.

    2. Can the application-specific keys be stored and managed by TIFS?

    Apart from root trust keys , TIFS does support keyring feature  which is used for importing additional set of asymmetric keys and using these newly imported key for authenticating different component.

    Do check out if this feature suits your requirement.

    3. Can we have the  Secure boot authentication routed via HSM?

    ROM and TIFS will rely of active root trust keys fused on to the device for secure boot. So boot loader certificate and TIFS outer cert will get authenticated against active root trust keys. 

    Once the HSM booted you can authenticated the rest of the component with the service provided by HSM if needed.

    Regards
    Diwakar

  • Hi  

    1. If TIFS supports customer-provided keys, can customer keys be stored and managed directly by TIFS without using a dedicated HSM?

    2. Are there any limitations on the number, type, or storage capacity of keys supported by TIFS?

    3. Assuming TIFS supports customer-provided keys, can TIFS Runtime Services be used for security features such as SecOC and Secure Diagnostics?

    4. If an HSM firmware is executed on the M4_1 core, will TIFS be responsible for booting and initializing the HSM firmware?

    5. Currently, the SBL is loaded/triggered by TIFS. If an HSM solution is introduced, what is the recommended approach to prevent or modify the TIFS-to-SBL boot handoff mechanism?

    Regards

    Naveena