This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2538: ZigBee SEP 1.1 flashing of Encryption and Certificate Key Data

Part Number: CC2538
Other Parts Discussed in Thread: Z-STACK

CC2538 based ZigBee In Home display to connect to electric meter.   Smart Energy 1.1 using   Z-Stack Energy,   Smart RF Flash Programmer 2     XDS110 tool

Want to make sure we put the Certicom Certificate in the correct place using the correct format.

Based on MAC 00124B0011F76543   (From Certicom  Test Certificate generator )  we got:

CA Pub Key:

0200fde8a7f3d1084224962a4e7c54e69ac3f04da6b8

Device Implicit Cert:

020446d5556644272cff3045854fc67fc779d81387e300124b0011f765435445535453454341df060655af082494dfdf

Private Key Reconstruction Data:

0297fcdf23998361995d08aa5da1e8f42ed4501837

Device Public Key:

03013df8b56d32b1fba18832bf65b1cf42aa97926e38

We are making a .txt   text file like this:

IEEE Address: 00124B0011F76543   

CA Pub Key: 0200fde8a7f3d1084224962a4e7c54e69ac3f04da6b8   

Device Implicit Cert: 020446d5556644272cff3045854fc67fc779d81387e300124b0011f765435445535453454341df060655af082494dfdf  

Device Private Key: 0297fcdf23998361995d08aa5da1e8f42ed4501837000000   

Device Public Key: 03013df8b56d32b1fba18832bf65b1cf42aa97926e380000

Using the "Image Overides" section of the Flasher under Encryption Key Data, we have specified the .txt file name and address 0x27ff6c Picture below.

This correct?

Thanks

  • Update and we think we found the issue.  Appears that there are two fundamental problems with using the Image Override  to write the Encryption Key Data to Flash.

    PROBLEM 1: Address Mapping.

    From file hal_board_cfg.h.  we know where the keys should be

    When we run the .txt file  in the SmartRF Programmer we get the following.  Note that two keys from the file and the IEEE MAC are put in the wrong place.  Although this configuration file calls for padding, the Programmer does not account for this. 

     


     

    PROBLEM 2: WRONG  KEY PROGRAMMED

    Although the TI documents say "Note that the Device Public Key is not used as part of the input into the Certicom library but is provided for completeness "      that key is actually the one programmed in.  The most important one, the CA public key  is NOT programmed in at all. 

     

    TI please comment.  

    Thanks

     

     

     

     

     

  • Think we coded around the two issues by changing the text file format.   TI  please confirm.

  • Hi Daniel, 

    We are looking into this, meanwhile, please see the section 3.3 in the document "Z-Stack Energy Sample Application User’s Guide" which describes how to program the cert data. This document is available at /documents/ under the Z-Stack Energy install.

    I don’t think the padding is required as the document doesnt call for it. The document however mentions

    Note: The data for the device implicit cert should be on one line (i.e. no carriage return separations should be included).

     

  • Thanks for the note. We are very familiar with that document. We believe that the routine for programming the certificate into CC2538 (from the .txt file) built into Smart RF Flash Program 2 Ver 1.7.5 is where the problem is. It does not put two of the keys and the IEEE Mac in the right place and and it does not install the critical CA Public key from the text file. We coded around it and have it working now with a CC2538 ESP and our CC2538 set up as a display.
  • Suyash:

    Any further information? Our device is connecting fine to a production electric meter (with a Certicom test certificate) at the ZigBee layer but failing at the Certicom steps.

    Thanks,

    Dan