• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 39 subscribers
  • Views 336 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.

CC3220S: SLImageCreator.exe image program Error FS_ILLEGAL_SIGNATURE

Johan Carlberg
Prodigy 30 points
Part Number: CC3220S
Other Parts Discussed in Thread: CC3220R, UNIFLASH

Hi

Have mounted a CC3220S on a PCB where we normaly use CC3220R.
Using the same .sli file. Programming CC3220R works fine but with CC3220S i get FS_ILLEGAL_SIGNATURE.
Can anyone tell me why/what wrong.

/Johan


C:\>SLImageCreator.exe image program --file programming.sli --port COM8
INFO:root:COM PORT COM8
INFO:slbootloader.slbootloader:Connecting to device
INFO:slbootloader.slbootloader:--- Please power off the device ---
Press ENTER to continue
INFO:slbootloader.slbootloader:Power off
INFO:slbootloader.slbootloader:Set break signal
INFO:slbootloader.slbootloader:--- Please power on the device ---
INFO:slbootloader.slbootloader:Power on
INFO:slbootloader.slbootloader:Clear break signal
INFO:slbootloader.slbootloader:Connection succeeded
INFO:slbootloader.slbootloader:Received storage list
INFO:root:Patching RAM...
Preparing...: 100% (10532/10532)INFO:root:Patching SFLASH...
Image Programming: 99% (282624/282688)INFO:slbootloader.slbootloader:Received error : error number = -10363 , extended error = 2633
Traceback (most recent call last):
File "<string>", line 5266, in <module>
File "<string>", line 5262, in main
File "<string>", line 5232, in cmdline
File "<string>", line 4115, in command_image_program
File "<string>", line 2788, in program_image_from_sli
File "<string>", line 2946, in program_image
File "W:\slbootloader\slbootloader.py", line 793, in fs_programming
slbootloader.slbootloader.BootLoaderError:
Error: SLImageCreator.exe: fs_programming error: ret: -10363, ex_err: 2633 - FS_ILLEGAL_SIGNATURE
SLImageCreator returned -1

  • 0
    TI__Guru 64525 points

    Hi,

    If the SLI was created for cc3220R which is non secured part, you would probably need to recreate the SLI for CC3220S part.

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 30 points

    That's what I thought too...
    But in CCS, both Device in common.syscfg and project properties "Variant and core:" is set to CC3220S.
    It's always been that way.
    Building .SLI and programming and the CC3220 using Uniflash has worked!
    (There no option to even select CC3220R in Uniflash (only S or SF) . New Config->Choose your device...)

    Seems strange, it should be that CC3220 programming fails and not CC3220S!?

    If i run dslite to check device. i get the same result for both MCUs

    C:\ti\uniflash_7.0.0>dslite.bat --mode cc32xx device info --port COM8

    Result
    CC3220
    Device Info :
    Type : CC3220
    Secure : False
    MAC : 50:f1:4a:d7:5b:f3
    PROG MAC : None
    HW Version : 0x31

    CC3220S
    Device Info :
    Type : CC3220
    Secure : True
    MAC : e0:ff:f1:2b:26:56
    PROG MAC : None
    HW Version : 0x31

  • 0 in reply to Johan Carlberg
    TI__Guru 64525 points

    Hi,

    I was referring to Uniflash in the first place.

    So it does work when you are working with Uniflash and not with CCS, is that it?

    The printouts show different data that matches the connected device ,either secured or non-secured. Why do you say you get the same result?

    It may be that syscfg does not work for CC3220R and only to secured parts but Uniflash should supprt it (you can pick CC3220R or CC3220S).

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 30 points

    Hi

    sorry for the confusion. Just trying to clarify that all settings are CC3220S(CCS and Uniflash).
    So no It does not work with CCS or Uniflash.  

    You are correct about the "Secure:" part. I expected the "Type:" to be different.

    So the error "- FS_ILLEGAL_SIGNATURE" should not be due to selected "Device Type" in Uniflash. Since it is set to CC3220S..!?
    So I guess something in the "Trusted Root-Certificat...." is not right..

  • 0 in reply to Johan Carlberg
    TI__Guru 64525 points

    now you got me even more confused.

    I need some clarifications:

    1. The result of getting the device type seems to be OK. Why do you say you get the same result? It is not the device type that needs to be different but the Secure part.

      Result
      CC3220
      Device Info :
      Type : CC3220
      Secure : False
      MAC : 50:f1:4a:d7:5b:f3
      PROG MAC : None
      HW Version : 0x31

      CC3220S
      Device Info :
      Type : CC3220
      Secure : True
      MAC : e0:ff:f1:2b:26:56
      PROG MAC : None
      HW Version : 0x31

    2. You said earlier: "Building .SLI and programming and the CC3220 using Uniflash has worked!". I understood that with Uniflash it worked when CC3220S is soldered.
    3. You said: "There no option to even select CC3220R in Uniflash (only S or SF)". But there is, see capture from my side.

    So starting clean with Uniflash and choosing CC3220S as the device works? can you try?

    Shlomi