• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 40 subscribers
  • Views 441 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-LAUNCHXL: Uniflash flashing error

KHODIDAS DOMADIYA
Prodigy 20 points
Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH, CC3220S, CC3220SF

Hi Ti,

Using uniflash

I am programming binary image in device, on 99% it is giving error 

Operation failed: fs_programming error: ret: -10301, ex_err: 2595 - FS_FILE_UNVALID_FILE_SIZE

jumper settings are checked ok, device gets detected, so cable and power are ok. created binary was already programmed earlier and not changed then after. just loading different application binary. 

I have two devices, and on both it is showing same error.

please help.

  • 0
    TI__Mastermind 40965 points

    Hi Khodidas,

    That specific error looks like it is returned from the network processor if for some reason the NWP is unable to detemine the max size of a file that it is able to create. It is as if the flash is not formatted correctly. However, Uniflash will always perform a flash format prior to programming.

    Since you mention that you were previously able to program the CC3220 with a different binary, what differences are there between the old binary and your new binary? Have you confirmed that both binaries are meant for the CC3220S, and not for the CC3220SF?

    Edit: There is also some debug information that you can look through here:

    https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/t/732447

    In particular, do you have files that are too large in size?


    Regards,
    Michael

  • 0 in reply to Michael Reymond
    Prodigy 20 points
    Thank you for your support
    Finally, I have tried the same thing with another PC. and works, hence it was issue with my PC.