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.1.2 PROCESSOR-SDK-LINUX

In the PROCESSOR-SDK-LINUX version 9.0 or less you can find the security board configuration file under <linux sdk>/k3-image-gen-xxxx.xx/soc/<soc_name>/evm/sec-cfg.c.

GUID-20240212-SS0I-HT4Q-MKTB-W1HB3PGMDJR8-low.png Figure 2-2 (SPL < 9.0 SDK) Secure Debug Structure – Example Configuration

In PROCESSOR-SDK-LINUX version 9.0 or greater the security board configuration file can be find under <u-boot-xxxx.xx+x>/board/ti/<soc_name>/sec-cfg.yaml.

GUID-20240212-SS0I-3DD5-WMZC-9FCKC014WJCD-low.png Figure 2-3 (SPL 9.0+ SDK ) Secure Debug Structure – Example Configuration