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: Designing with CC3220

Part Number: CC3220S
Other Parts Discussed in Thread: AFE4960, CC3301

Hello Team,
We are planning to use CC3220S in one of our applications.
The end product is a medical device (ECG holter monitor).
We need BLE and WiFi functionality in the product. (CC3220S has only WiFi functionality.)
1). Does TI have any MCU like MCU + WiFi + BLE?

2). Also for CC3220S, only a single SPI is available, can I use the pinout for the serial flash (11 - 14) for other peripherals?
3). Or can I use this serial Flash to store the data from a sensor?
The memory size will be above 500MB.

We are using the AFE AFE4960 from TI.
The AFE has a 128 sample FIFO which can store up to 128*32 bits of data.
When the watermark is achieved, we will get a FIFO RDY interrupt from the AFE.
The controller will then wake up from sleep mode and will store those data from the FIFO in the internal RAM of the MCU.
Once the data is in the internal RAM is 4KB (Page Size of the Flash we are using now), those data will be transmitted over SPI to the NAND Flash).
The AFE also uses the SPI interface and the CC3220S has only a single SPI
If the sampling rate of the AFE is taken as 250Hz (125 FIFO water level), we can expect 2 interrupts in a second.
The MCU needs to wake up in 500mS.
Since we only have a single SPI on CC3220S, will this create a bottleneck when using the same SPI for both NAND Flash and AFE?

Our minimum MCU requirements are as follows.
Minimum GPIO - 30 or above
Interfaces - SPI*2 (SPI Clock freq must be above 48M)
UART*2
I2C*2
RAM - 160kB or above
Flash - 500kB or above
Clock Speed - 100MHZ or above
Low Power
Package - Lowest form factor
Architecture - Cortex M4 or M0
Medical device.
The WiFi must support Access Point mode.

  • Hi,

    You can't use the SPI lines towards the host as they are being controlled by the NWP (Network Processor).

    However, you can use the external flash for your storage. check the secure file system (chapter 8) in the programmer's guide. The FS (file system) is implemented by the NWP which enables the MCU application to manage its "user" files.

    I'm not sure how 4K bits every 0.5 sec (even if it is copied twice over the same SPI) can become a bottleneck but if it does you can consider using the external flash instead.

    For Wi-Fi & BLE we have the CC3301 which can be paired with any external MCU (with enough memory).

    br,

    Kobi

  • Hello Kobi,
    Thank you for your quick response.

    If I understand you correctly, the serial flash (on pins 11-14) can be used to store my own sensor data. Since our sensor data is in the order of 500MB, we may need to use a serial flash of 512MB on that port.
    1). Please correct me if I am wrong.
    If that is not the case,
    We may need to use another SPI flash.
    Since only one SPI is available on the CC3220S, we may have to share the same SPI among the AFI and the NAND Flash (SPI Flash).
    The Program flow is as follows.
    i). The AFE gives a FIFO RDY interrupt when the FIFO watermark reaches 125 samples (125*32 bits = 500Byte of data every 500mS)
    ii). Those data are transmitted over SPI to store in the internal RAM of the CC3220S.
    iii). When those data sizes reach the page size (4KB), the data is written to an external Flash through the same SPI (once every 2 seconds)
    iv). The controller will be in sleep mode in all other cases.
    The controller may take some time to get into active mode from wakeup mode.
    The clock may take some time to get stable.
    The Controller should be lessening the data from the AFE even if the data transfer between MCU and external flash.
    Considering all these factors will share the same SPI a bottleneck for data reading from the AFE and data writing to the external Flash.

    If the SPI clock is working at 48MHz, what is the time it will take to transfer 4KB of data?
    We need RAM retention and wakeup from external interrupts during sleep mode.
    What is the best low current we can achieve with these conditions satisfied?
    Ours is a battery-operated device, so the current consumption is very critical.

    Regarding CC3301, the datasheet is not available, and we may need to use another MCU as a master to achieve wireless data communication through CC3301 which may increase the BoM cost.
    Can you please share the datasheet of the CC3301

    Looking forward to hearing from you

  • There should be one serial flash (that is controlled by the NWP). For maintaining the required I'm not sure if the NWP can support files of 500MB. Are you sure that you need so much memory? You can check the requirements and limitations in the https://www.ti.com/lit/pdf/swra613 and the in the programmer's guide (linked before).

    You can add your 500MB on top of the 2-4MB that are required for the device functionality (for service pack storage and OTA support).

    48MHz means max speed of 6MBps. Of course there are protocol overheads and delays between frames but 4KB should be in the order of milliseconds.

    The datasheet of cc3301 should be there in the link i provided.