Secure JTAG

Question

Hi, 
 Is it possible to program just a secure key for the JTAG or does enabling secure jtag also mandate that a secure boot stream is required ? 
 I've tried to experiment with an old board with the code based on the Program_OTP util in the EE-366 notes, but after programming the key & then reading it back to verify, it always comes back as zeros. It seems to program fine and I can see the key being programmed is valid. 
 /* call the api */ if(!adi_rom_otp_pgm(&data)) { return false; } 
 /* verify the data was written */ return VALIDATE(secure_emu_key); 
 where 
 #define VALIDATE(otpkey) validate_pgm(otpcmd_##otpkey,*key,ROM_OTP_SZ_##otpkey) 
 
 I've read that the OTP regions is memory mapped, I eventually found the address in an apt file as 
 { 0x24000000u, 0x240FFFFFu, ADI_MMU_RW_UNCACHED }, /* 1MB OTP Space */ 
 but I can't view that address in a cces memory window - should I be able to ? 
 Is there any documentation about how to use cldp to program the OTP ?

Rob Belcham · Accepted Answer

Hi Divya, yes thanks : tools support were able to provide a fix for the BLw images which I'll post here for anyone else having trouble.. Use aesKey parameter instead of using aesWrapKey under configureBlw() in SecureBoot_OpenPart.c from "uint8_t * aesWrap = (uint8_t *)&pBootConfig->aesWrapKey;" to "uint8_t * aes = (uint8_t *)&pBootConfig->aesKey;" whole function for reference void configureBlw(ADI_ROM_BOOT_CONFIG* pBootConfig) { uint8_t * pKey = (uint8_t *)&pBootConfig->publicKey; uint8_t * aes = (uint8_t *)&pBootConfig->aesKey; uint8_t i; for(i=0; i<56; i++) { pKey[i] = secure_boot_public_key[i]; } for(i=0; i<16; i++) { aes[i] = wrapper_key[i]; } })