• State Resolved
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Subscribers 42 subscribers
  • Views 105 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CC3351: OTP configuration key clarification

Edward Jen
Prodigy 90 points
Part Number: CC3351


Tool/software:

Hello TI,

I have a hopefully quick clarification question regarding the configuration key and checksum for cc33xx-conf.bin.

In the INI Composer, there is a section for CRC_CONF with one subentry for userChecksum.  

In the SimpleLink SDK documentation for the Calibrator Tool and under the OTP Configuration section, there is something called the Configuration Key.  It explains that the CRC checksum is calculated from the Configuration Key and the parameters for the cc33xx-conf.bin.

If I am in the INI Tool of the SimpleLink Wi-Fi Toolbox and have made the changes to the INI settings and need to enter the checksum in CRC_CONF.userChecksum, what am I supposed to do?

I must be misunderstanding what the process is.

Thanks,

Edward

  • +1
    TI__Mastermind 31830 points

    Hi Edward,

    Good question and we need to update the documentation surrounding this topic as the steps have been updated.

    The "conf_key" needs to be uploaded to the INI Composer tool. You can find an example of this conf.key file in C:\ti\simplelink_wifi_toolbox_win_2_5_5\ini-composer\cc33xx_conf_default. First step is to create your own conf.key file.

    Next, upload this conf.key file into INI Composer via Load -> CONF KEY. 

    Now, you can generate the bin or the tar. If you generate the tar, you can then view the exported INI file. Scroll to the bottom of the INI file where you will see 'IniCRC' parameter updated to a non-zero value. Where 'IniCRC' is synonymous with crc_conf.userchecksum.

  • 0 in reply to Sabeeh Khan1
    Expert 1391 points

    Note - this is only relevant if you intend to program the OTP with the configuration key. The key itself, in conf.key, is what you would separately program in OTP during your manufacturing phase. The tools calculate userchecksum based on the value of conf.key, and all should match (OTP key in the radio matches conf.key, and that key value is used by the tools to generate the user checksum).

    You don't ever manually write userchecksum yourself.

    If you aren't going to program the key into radio OTP (which makes the regulatory related parameters tamper resistant), then you can ignore this topic completely.

  • 0 in reply to Sabeeh Khan1
    Prodigy 90 points

    Thanks Sabeeh.  That was helpful!

  • 0 in reply to Dean Ramsier
    Prodigy 90 points

    Thanks for the additional information, Dean.  I appreciate it.