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.8 Attaching to HSM Core With TRACE32

After successfully executing and unlocking JTAG access for the HSM with the TRACE32 script “J721S2_secure_unlock.cmm”, it is now possible to attach and load HSM symbolic information within TRACE32 for debugging purposes. Please navigate to the following folder location ~/t32/cmm-ti/cmm-dra/cmm-tda4v_j721s2/x_gel_to_cmm/ and edit the following script parameters located in the “_J721S2_m4.cmm” script in order to attach to the HSM (Cortex M4F).

GUID-20240212-SS0I-TZ9K-2P5T-QVZTXKFZBV08-low.png Figure 2-9 TRACE32 – HSM Attach Script

After modifying “_J721S2_m4.cmm” script and saving the file, please once again click on the “Do” button in order to execute the script in TRACE32. Finally, you should now be attached to the HSM and able to view debugging windows in TRACE32 as depicted in the Figure 2-10.

GUID-20240212-SS0I-JWL5-ZTMW-S7G2GWPQHX4K-low.png Figure 2-10 TRACE32 – HSM Debugging