In order to standardize and simplify the process of customers providing binary, TI can provide the CRP Script Tools. Currently this tool reference tar only support TDA4VM, more device need chose your SDK path to generate the binary signed. The running logic of this CRP script is shown in Figure 3-2.

After set up the environment for generate the binary, TI will provide a reference environment tar (base on TDA4VM SDK8.6), customer only need enter the KEY_FILE path (this means the customer needs to be able to access the private key), Device UID, and the output path, the tool will help sign and generate all the binaries for TI CRP need. Include the override.bin, SBL/SPL Certificate binary, and the DMSC Certificate binary. The tool can choose that other binaries except tiboot3.bin and tifs.bin or sysfw.itb need to be signed or not. And for the difference sign process of the HS device and HS-Prime device, tool can also handle this.

Use this tool to generate all the files that need to be signed in the CRP process at one time, and modify the parameters to configure the number of files generated by the tool, and the tool is still being improved. The specific steps to use the tool are as follows:

1. Download and extract the j7_crp_tool.zip tar to your ubuntu PC.
2. Go to the path of this tool installed, and execute the script tool use the command: ./j7_crp_spl_tool.sh.
3. Enter your private key path: KEY_FILE path, the tool provide the TI dummy key in this tool for example as below: {cwd}/j7_crp_spl_too_for_reference/core-secdev-k3/keys/custMpk.pem.
4. You need to enter the device type (hs/hsp). The tool will check to see whether the key file exists and exit immediately if it does not exists.
5. You need enter the Device UID and the output path for the signed binaries.
6. You can find the all binaries generated by this tool in the output path, and you need to pack them into one file (tar) and send to TI contact window.