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.

CC3220SF-LAUNCHXL: CC3220SF-LAUNCHXL & Uniflash 6.2.0.3059 unable to flash Energia binary

Genius 12695 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH, ENERGIA, CC3220SF, CC3220S,

Hello Team,

I read several comments on e2e regarding "how to flash an Energia binary with Uniflash" and I tried them all without success.

I used CCS Cloud, imported the Energia Sketch "blink", run it successfully on the launchpad. Then I downloaded the blink.bin and opened Uniflash.

In the simple view I browsed to the blink.bin in the MCU Img field and I also entered the path to the latest service pack. Then "Burn", then "Program Image",

During programming all seems to work without any errors but the application does not work. I only can flash the OOB binary...SOP is in position 1.

Thanks for your help and best regards,

Hans

  • Hi Hans,

    I don't use Energia with CC3220SF, but I can explain reason of issues. I am not sure if this issue persist, but it is likely that this bug is still opened.

    Issue is that binary generated by Energia is linked into RAM for SF devices. But ROM bootloader at CC3220SF devices expects that code is linked into XIP flash. And this is reason why binary file generated by Energia cannot flash by Uniflash. There is a few ways how overcome this issue:

    Jan

  • Hello Dan,

    thanks for fast reply! I flashed the bootloader successfully (got the same error message: "Unable to get size...") 

    Then I tried to add the energia.bin under user files in advanced mode as shown below. I also tried to to put the energia.bin under root without success.

    Would it be possible to get some instructions, please? 

    Will flashing work for CC3220S Launchpad without these problems?

    Thanks in advance and Best Regards,

    Hans

  • Hi Hans,

    You need to upload energia.bin into /energia.bin not into /sys/energia.bin and bootlaoder file as /sys/mcuflashimg.bin.

    Yes, you can use CC3220S Launchpad with Energia and Uniflash without any issues.

    Jan

  • Hello Jan,

    thanks so much for your support! It looks like flashing works. 

    Are the properties correct?

    Thanks again,

    Hans

  • Hi,

    Yes, this looks OK. Are you able execute your example uploaded by Uniflash?

    Jan

  • Hi, so far I did not succeed in getting my application on the launchpad running.

    Any ideas are appreciated, I am an analog person ;-)

    Thanks and Best Regards, 

    Hans

  • Hi Hans,

    Hard to say what is wrong at your case. Maybe you can start from the beginning...

    • create new Uniflash project for CC3220SF-LAUNCHXL. Make sure that development mode is used.
    • at simple mode MCU image (use my bootloader file) and insert Service Pack from CC32xx SDK as well (insert .bin file from simplelink_cc32xx_sdk_5_10_00_02\tools\cc32xx_tools\servicepack-cc3x20\sp_3.19.0.1_2.7.0.0_2.2.0.7.bin)
    • burn image into LaunchPad
    • connect to the UART from LaunchPad at 115200Bd and check that error message is shown, if so continue
    • generate binary file from Energia example (in Energia select CC3220S device)
    • switch Uniflash to advanced mode and upload .bin file generated by Energia as energia.bin
    • burn image into LaunchPad and check if your example works, if you will have still issue, upload here your .bin file generated by Energia and I will check them

    Jan

  • Hello Jan,

    now it works! New for me was the fact that I have to compile for an CC3220S and not CC3220SF! Thanks a lot! Some observations:

    I tried some examples with Energia and flashed them successfully according your recent instructions. But when I used my own application it ran only partly (established network connection and connected to mqtt server but did not publish).

    I used exactly the same code in CCS Cloud, compiled it for CC3220S and flashed it with Uniflash and this worked. Both binaries had the same size.

    I cannot explain what went wrong but I don't care anymore :-)

    Thanks again and best regards,

    Hans