Secure JTAG

Hi Rob,

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 ?
>> Secure booting is considered as whole.

Please note, from 0x202BFFFF to 0x28240000 is reserved memory space. Since you are trying to read data from the RESERVED Memory location, it is not accessible.

Also, please refer "Figure 5. ADSP-SC58x/ADSP-2158x Memory Map" in the below linked datasheet of ADSP-SC58x/ADSP-2158x.
www.analog.com/.../ADSP-SC582_583_584_587_589_ADSP-21583_584_587.pdf

Is there any documentation about how to use cldp to program the OTP ?
>> Please refer in below CCES help:
CrossCore® Embedded Studio 2.11.0 > Integrated Development Environment > Working with Bootable and Non-bootable Files > Device Programmer > Device Programmer Command Line > Device Programmer Command-Line Switches

Please note that once the part is locked, it can only be accessed via JTAG with the emulation key.

Regards
Divya.P

Hi Divya,

Thanks for your response.

The datasheet only mentioned OTP once..

One Time Programmable Memory (OTP) The processors feature 7 kB of one time programmable (OTP) memory which is memory-map accessible. This memory contains space for programmable unique keys and supports secure boot and secure operation. 

But doesn't mention it in the memory map, hence my question.

Any ideas why the EE note example code doesn't seem to work on an SC589 ? That's my main concern at the moment as I'm unable to proceed in my evaluation of security options. 

Thanks

Rob

Hi Divya, 

I'm using the Program_OTP project from here 

http://www.analog.com/media/en/technical-documentation/application-notes/EE-366.zip

Here are the steps I followed..

1) imported the keygen & Program_OTP projects into cces (2.8.3)

2) Delete all the pre-build artefacts in the keygen project & build project to create new keys

3) Fix out of date python scripts to work with Python 3

 bin2inc.py : 

     Bytes.append(ord(b))  >> Bytes.append(b)
     if args.mode is 'c': >> if args.mode == 'c':

genRandKey.py

 print "File %s exists, will not overwrite" % f >> print ("File %s exists, will not overwrite" , f)

Makefile
   PYTHON: - change to path to Pythong 3.10

4) Build keygen project to generate a new set of keys

5) There are no example projects for the SC589, so I created a new cces project Program_OTP_Sharc (for Cores 0 & 1)
    - remove addins from Core0 & 1 projects except heap add in for core 0 

    - delete Program_OTP_Sharc_Core1.h & .c auto generated files

    - add new linked file to the Core 1 project (PROJECT_LOC/../Program_OTP/src/Program_OTP.c)

    - add include path to C++ preprocessor settings ("${workspace_loc:/keygen}")

    - enable call to setupBlp() in main() and comment out all references to lock_part() 

          - one in setupBlp()

          - one in main()

    - Set custom linker script for Core0 project to run from L2

          C:\Analog Devices\CrossCore Embedded Studio 2.9.3\ARM\arm-none-eabi\arm-none-eabi\lib\ldscripts\adsp-sc589-l2.ld

  - Add while(1); to end of arm main()

  - configure heap to 4KB. Configure all stacks to 1KB so that project fits in L2

6) Setup launch config for Core 0 & 1 projects (using standard EzKit preloads)

7) Set custom board to No Boot mode

8) Launch debug project, continue the ARM core and start stepping through code in sharc core 1

    - Step into SetupBlp

         - Step into program_authentication_key()

                run to line in the disas windows to step over adi_rom_otp_pgm - note that R0=1 (success)

                run to line to step over validate_pgm - note R0 = 0 (fail) 

                continue and observe output...

Programming auth key:
Qx: a2 6a ff 68 f8 d0 ab c0 03 03 f9 98 60 b1 7d 02 89 be b1 a3 9a 26 a0 d4 18 de 9c 08
Qy: 5e 2d ba 86 50 56 89 3b 2b c8 25 71 f1 1b 04 4b 05 d5 41 3d 84 bf 09 c9 0e 1e b7 df

failed to program authentication key
Reading auth key:
Qx: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Qy: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

I've tried this on several boards. I know the boards haven't been locked, because I accidentally locked one (forgot to comment out lock_part() and the behaviour is different for a locked part - the adi_rom_opt_pgm call fails if the part has been locked.

To confirm, I haven't got as far as generating a secure boot image yet, I was just trying to verify the process of securing a processor. 

Kind Regards

Rob

Hi Rob,

We have OTP program example for ADSP-SC589 from EE366v02 notes. Also, we suspect you may face error when trying to import the ADSP-SC589 Program_OTP in CCES.

Please note that, Typically a project will use a number of relative paths in its configuration that may become invalid once the project has been moved. These are files that do not exist within the directory structure of the project, and are instead linked into the project from relative paths

In order to recover the "file not found error", use the linked resources path, please follow the below steps.

1. Open project properties > Resources > Linked Resources
2. Select the "Linked Resources" tab which is next to Path Variables.
3. Select the to be changed to relative location under 'Resource name' and click 'Edit'.
4. Select the source file/folder to be link and click OK.

Please find the attached screenshot for reference.OTP.zip

Could you please try to use the default key available in Keygen project without creating new keys and let us know whether you are able to read the authentication key properly.  And confirm whether the issue occurs only in generating new key's. Please share us the screenshot of the console.

If still facing issue in example project, can you please share us your modified project along with keys you have used.

Regards,
Divya.P