LAUNCHXL-CC3235SF: Can't reset code by pressing the reset button

Hello Rock,

There is probably a problem with the code the customer is running. What are they trying to do?

Jesu 

Hi Jesu,

The customer found that using Uniflash 5.2 download .bin that compiled by IAR to LAUNCHXL-CC3235S is normal, but they want to use CC3235SF.

They guess below is the reason, but they don't know how to resolve it.

So could you please give some suggestions?

Thanks a lot!

Hello Rock,

I'm not sure what reason you're insinuating here. Could you verify their project in IAR is correcty building? There should be a .bin file that gets generated. This is the mcu image that should be used to program the device in Uniflash. Also verify the project is for the CC3235SF and not the CC3235S.

Jesu

Hello Rock,

In response to your direct query:

According to swru469f  6.11.1. for CC32xxSF devices, 20 bytes sha1 digest been needed to add to host file. But in Uniflash 5.2.0, after we add the host.bin file in simple mode, we found a 32 bytes sha256 digest added automatically. even when we use CLI to add the mcu file, the 32 bytes sha256 also added automatically. when we add the 20 bytes sha1 by using openssl, we have no method to add the .bin file into the project without the 32 bytes sha256.
       This 32 bytes sha256 digest cause my CC3235SF LAUNCHXL not able to reboot according to the swru469f 6.11.1.
My CC3235S LAUNCHXL works well in same operation. 
      Could you provide more information about this bug and how to solve the problem with some method?

CC3220 devices use SHA1 to verify the MCU image. CC3235 uses SHA2 by default so the behavior you’re seeing is expected. I'm still not sure what problem you are experiencing. Could you describe in detail what the exact problem is? What is the customer trying to accomplish?

Jesu

Are you sure CC3235SF using SHA2?

I use the uniflash demo project of OOB (example from SDK), it works well with my CC3235SF LAUNCHXL, and I check the file mcuflashimg.bin, it is SHA1.

I have test same project with my CC3235S LANUCHXL, it works well. But it not for my CC3235SF LAUNCHXL. I am sure I have change the device between CC3235SF and CC3235S with different LAUNCHXL, So I think the problem is SHA2 or SHA1. 

I am using Uniflash 5.2. FreeRTOS with IAR.

I have test same project( IAR PROJECT, NOT UNIFLASH PROJECT, COPY FROM OOB. I USE THE BIN FILE TO CREATE UNIFLASH PROJECT BY MYSELF.) with my CC3235S LANUCHXL, it works well. But it not for my CC3235SF LAUNCHXL. I am sure I have change the device between CC3235SF and CC3235S with different LAUNCHXL, So I think the problem is SHA2 or SHA1.

Are you flashing the SF version of the OOB project to the SF device? Keep in mind all projects in the SDK have a CC32XXS version and a CC32XXSF version. So even if you change the Uniflash project to S or SF device binary images are specific to the type of device you're using. Please confirm.

Jesu

Yes, I flash with SF version OOB to SF version LAUNCHXL. 

c:\ti\simplelink_cc32xx_sdk_3_30_01_02\examples\rtos\CC3235SF_LAUNCHXL\demos\out_of_box\uniflash\cc32235sf_out_of_box_freertos.zip

By import this uniflash project, I get the file mcuflashimg.bin, and find it is with 20 bytes SHA1. 

But when I create a uniflash project by myself and add my own bin file. then get the mcuflashimg.bin file out of the project. I find it with 32 bytes SHA2.

SHA1 works well and SHA2 failed. 

Yes. CC3235 devices are supposed to use SHA2. 

How are you checking whether the signature is SHA1 or SHA2? Please share. 

I cannot reproduce this behavior. I imported the out_of_box\uniflash\cc32235sf_out_of_box_freertos.zip project and flash it and it is working. 

Could you provide detailed steps to reproduce the failure you're seeing?

Jesu

I check the Uniflash OOB project, it is SHA2, you are right.

When importing the Uniflash OOB project from SDK, It is working. I am here same with you.

But if I import the IAR project from the SDK, and make my own bin file. Then I create a new Uniflash project and add this new bin and service pack file in Simple mode. Then I program it into 3235SF LAUNCHXL, It can not run when reset. But for 3235S LAUNCHXL, it works when reset.( Of course i have change settings for different device.)

If I use IAR to download the project when 3235SF is in development mode, it works well, so I think it not because of code. Something must be wrong in my Uniflash project. But I don't know why?

I repeat my process:

1. for CC3235S

    import CC3235S IAR project in to my 3235S folder. -> build it to get a bin -> New a project in Uniflash -> add the bin file and service pack file in simple mode   -> burn into CC3235S LAUNCHXL -> open Tera Term of the COM port -> Press reset button on LAUNCHXL -> Tera Term get information

2. for CC3235SF

    import CC3235SF IAR project in to my 3235SF folder. -> build it to get a bin -> New a project in Uniflash -> add the bin file and service pack file in simple mode   -> burn into CC3235SF LAUNCHXL -> open Tera Term of the COM port -> Press reset button on LAUNCHXL -> Tera Term DO NOT get information

Thanks for providing these steps. I will test tomorrow by building out of box project in IAR and flashing the bin to an SF using Uniflash to see if I get the same behavior. I will get back to you.

Jesu