Post Go back to editing

external flash can be operated when JTAG has been locked

Category: Software
Product Number: ADSP-21565
Software Version: 2.12.0

Hello Support Team Guys,

We follow the link of "Emulation Key Disable - Q&A - ADSP-2156x - EngineerZone" for JTAG locking. Regarding the JTAG key protection of ADSP-21565, we hereby feedback our test and verification results, and have 2 questions that require your company’s response.

Regarding the issue of JTAG key protection for the ADSP21565, here is the feedback on the test verification results from our side:

  1. According to the previous document "EmulationKeyDisable - Copy.zip," the current test results indicate that JTAG can be locked, and debugging via JTAG is indeed prevented.
  2. However, even with JTAG locked, it is still possible to program the corresponding external Flash of the ADSP21565 via JTAG.
  3. The method described in the "EmulationKeyDisable - Copy.zip" file for unlocking the JTAG interface by importing an XML file has not been successfully implemented by our team so far.

 

two questions:

  1. We are currently puzzled because the JTAG key protection function for the ADSP21565 has not been successfully implemented. Is our approach incorrect, or does the ADSP21565 DSP chip itself not yet support this feature?
  2. please clarify whether the ADSP21565 DSP can indeed implement JTAG key protection—specifically, whether JTAG can be locked to prevent programming the corresponding external Flash data via JTAG after locking, while still allowing unlocking via a key.

Thanks & Best regards,

xiangzhi wu

xiangzhi wu

Parents Reply
  • Hi,
    Could you please provide more information on below points,
    1.Have you generated the ECDSA-224 key pair using the CCES signtool (genkeypair command), and confirmed that both the public and private keys were created successfully in DER format?
    2.Was the application loader file (.ldr) generated using the elfloader tool with the correct processor type (ADSP-21565) and boot configuration (SPI, width, boot code)?
    3.Did you convert the loader file into a secure boot stream (e.g., BLp format) using adi_signtool with the correct private key, hash configuration, and attributes?
    4.How was the secure boot stream programmed into the storage device, and did you follow the CLDP flashing procedure described in the below commands for ADSP-2156x BSP?
    For reference, please refer the below CLDP command,
    "C:\analog\cces\3.0.1\adi_signtool.exe" -proc ADSP-21569 -add-sbh-hash-256 sign -type BLp -attribute 0x80000003=256 -prikey keypair.bin -infile application.ldr -outfile application_BLp.ldr
    5.Which method was used to program the security keys into OTP memory (CLDP or ROM-based OTP APIs), and was the programming verified before relying on the boot kernel to decrypt the secure boot stream during boot?
    6.If not already referred,  test the Secure_Openpart example code first before writing to OTP memory. Please find the below FAQ link,
    Regards,
    Nandini C
Children
No Data

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.