SPRUJC1 April   2024

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
    1. 1.1 Unlocking JTAG With Jacinto7 Security Enabled Devices
  5. 2Steps to Unlock JTAG for HSM Core With TRACE32
    1. 2.1 Modifying the SCI Client Default Security Board Configuration
      1. 2.1.1 PROCESSOR-SDK-RTOS
      2. 2.1.2 PROCESSOR-SDK-LINUX
    2. 2.2 Building the SCI Client Security Board Configuration
      1. 2.2.1 PROCESSOR-SDK-RTOS
      2. 2.2.2 PROCESSOR-SDK-LINUX
    3. 2.3 Modifying the Secondary Bootloader’s x509 Certificate
      1. 2.3.1 Windows Build Environment
      2. 2.3.2 Ubuntu Build Environment
    4. 2.4 Building the Secondary Bootloader
    5. 2.5 Verifying Secondary Bootloader and TIFS is Executing
    6. 2.6 Creating a Downloadable x509 Certificate With a Debug Extension
    7. 2.7 Execution of TRACE32 Unlock Script
    8. 2.8 Attaching to HSM Core With TRACE32

2.5 Verifying Secondary Bootloader and TIFS is Executing

Since the ROM Loader is not capable of unlocking JTAG for the HSM it is necessary to confirm the SBL is successfully booting and the TI Foundational Secure (TIFS) firmware is running. In order to validate this, copy or flash the newly built SBL image and TIFS binary to your non-volatile boot media. Next, connect to the MCU UART port on your board, power on the device, and verify with a terminal window that TIFS is running successfully (see Figure 2-6).

GUID-20240212-SS0I-MW5Q-RDH2-9DXPFJKKNQNC-low.png Figure 2-6 Verifying SBL and TIFS Boot