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: CC3220S and CC3200SF

Part Number: CC3220S

This will be a new product design, I wondering to choose CC3220S or CC3220SF.

CC3220SF has 1MB Flash but more expensive. 

Both MCU should interface with external flash to store the application binary. What is the advantage for the 1MB for CC3220SF?

Regards

Sam

  • Hi Sam,

    With SF variant you can execute bigger code. With S version is your code executed from 256kB RAM. Into this RAM needs to fit your common RAM things like variables, buffers, stack, heap, etc. At SF device can be code executed from internal 1MB XIP flash and you have all 256kB RAM for your variables, buffers...

    External SPI flash chip is mandatory for all CC32xx devices. At the MOD devices is SPI flash integrated inside module already.

    Jan

  • Hi Jan,

    Our application is simple IoT, small amount of data, I like this IC because it is SoC and new IC, it can do analogue measurement and I/O  control. WiFi is only for Cloud connectivity. 

    I have no idea about how much can this 256K RAM do, it should be capable of handling simple Webpage?

    What is the consequence if the 256K is not sufficient? it will crash or just slow? 

    I don't care it slow down for Cloud communication, but not crash.

    Regards

    Sam 

  • Hi Sam,

    Hard to say if there will be enough of memory space for your application at CC3220S. Difference between S and SF device is related to functionally of your code not a WiFi or socket communication. I will suppose that CC3220S will have enough resources for your application but maybe you can reach limits if your application grow due to implementing new features.

    If you will not have enough RAM you will not be able implement more features or it will be needed remove some features.

    For example I use CC3220SF and I have used 312kB from 1MB flash and 187kB from 256kB RAM with this features:

    • measurement from I2C and SPI sensors, evaluating alarm states
    • control LCD display, memory and RTC
    • sending data into Cloud via http/https POST
    • own proprietary communication protocol via USB and TLS
    • datalogging features
    • http/https server with multiple socket capability with HTML5 support
    • sending alarm emails with TLS and STARTTLS support
    • support for Modbus TCP, XML and JSON protocols
    • support for own UDP discovery protocol
    • support for local OTA via webpages

    Jan

  • That is a great example.

    How to check the RAM memory usage via CCS debugger? I can use this to evaluate and choose the right IC.

    Regards

    Sam

  • Hi Sam,

    In case of CCS, you can use Memory allocation tool. This tool show static allocation of memory after compiling. Utilised memory for dynamic allocation from heap at runtime depends on used RTOS. For example for TIRTOS you can use ROV.

    Jan