• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 40 subscribers
  • Views 738 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTOS/CC3220SF-LAUNCHXL: Trying to program with .hex file

Jonathan Martin
Intellectual 620 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH, CC3220SF

Tool/software: TI-RTOS

I have used older uniflash version but am having issues with the new version 4.

I would like to just take a .hex file and load it onto the chip. 

  • 0
    TI__Guru* 91206 points
    Jonathan -
    the CC3220SF has security built into the device, which simply means you need to follow a process to sign the image before attempting to load it.
    the Uniflash with Image Creator is the tool to use which can sign it for you, if the certificate chain is loaded as described here:
    www.ti.com/.../swru461a.pdf and also in other detail, here: www.ti.com/.../swru469b.pdf

    Please also note that the tool was recently updated, so do visit: processors.wiki.ti.com/.../Category:CCS_UniFlash
  • 0 in reply to Josh Wyatt
    Intellectual 620 points

    ok I have tried the dummy version. It is able to load the image. When my image boots it is suppose to write certs needed to run. Its how AWS SDK was set up. Those do not seem to be working..


    ERROR: runAWSClient L#288
    Error(-24) connecting to a17q59ygxtqaej.iot.us-west-2.amazonaws.com:8883


    Subscribing...


    network disconnect error

    ERROR: runAWSClient L#306
    Error subscribing (-13)

    I tried other ways to get it loaded but none worked. I also found this in another example but not sure exactly how to follow it...

    5.7.1.1 Host Application for the CC3220SF Device The CC3220SF application requires adding 20 bytes of SHA to the beginning of the host file. The SHA is the result of a hash algorithm, which is calculated on the host file content. The file signature is calculated on the host file content, including the SHA. The creation steps are as follows: 1. Add SHA to the beginning of the file (host_final). 2. Calculate the host signature (signature of the host_final file). The ImageCreator offers two methods of adding the host application: • The application file, including the SHA, is created by the user and the file signature. The input is the host_final and the signature of the host_final. • The host_file, without the SHA, is set by the user: 1. The ImageCreator calculates the SHA and the host_final. 2. The file signature of the host_final file is calculated by the ImageCreator, using the private key in DER format as an input.

  • 0 in reply to Jonathan Martin
    TI__Guru* 91206 points
    Jonathan -
    Please then see Quick Start guide for the AWS IoT Plugin:
    dev.ti.com/.../

    and similar from AWS website: docs.aws.amazon.com/.../getting_started_ti.html - specifically the section where you configure your AWS IoT Credentials and include them in your code before signing into the AWS IoT Console and subscribing.
  • 0 in reply to Josh Wyatt
    Intellectual 620 points

    I used the quick start guide to get going. It only shows howto load code with CCS but that only loads it to ram. If i reset chip I have to reload firmware. 

    That other link doesn't show anything new either. 

    I have root_ca, cert, and private cert key.

    I can make .pem or .der files with them but have not found a way to use them. The dummy example can not really be modified for my purpose or at least it doesnt look like it can