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.2.1 PROCESSOR-SDK-RTOS

In order to build the SCI Client Board Configuration within the PROCESSOR-SDK-RTOS please navigate to the <pdk_path>/packages/ti/build/ directory and open a command prompt. Next, the following make command should be executed in order to independently build the SCI Client Board Configurations:

make sciclient_boardcfg_hs BOARD=j721s2_evm CORE=mcu1_0 OS=linux

The make command above will compile, encrypt, and sign the SCI Client Security Board Configuration with the default MEK and MPK development keys located in the PROCESSOR-SDK-RTOS. The final output from this build command will be a C array located within <pdk_path>/packages/ti/drv/sciclient/soc/V4/ directory.