• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 39 subscribers
  • Views 545 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.

CC3200: CC3220

Neeraj Sallh
Intellectual 685 points
Part Number: CC3200
Other Parts Discussed in Thread: CC3120, CC3100

Fact 1:

In case we want to use an external Host then CC3120 will be used.

Fact 2:

The host driver has to be ported to the external Host for configuring/initializing CC3120.

Now the question:

If despite the elegant solution mentioned in Fact 1 above, one still wants to implement a solution where an external Host is linked up with CC3220 (instead of the more apt CC3120), i.e. CC3220 is the peripheral, then:

  1. Will there be an API that straightaway enables the external Host to configure/initialize the CC3220 device (on the same lines as mentioned in Fact 2 above)?
  2. Or because we know that the CM4 of CC3220 is the host for the "Wi-Fi + NWP" part of CC3220, we will have to go via CC3220 and do the following:
    1. The command given from external host is interpreted by CM4 first.
    2. Then the CM4 uses the API available to itself as the host of "Wi-Fi + NWP" part for configuration of the "Wi-Fi + NWP" part.

  • 0
    TI__Expert 8255 points

    Hi Neeraj,

    I'm not sure if I fully understand the implementation above--but I think you are suggesting using an additional external MCU with the CC3220 device--which already contains an M4 application MCU + NWP. Is that correct, and can you help me understand why this setup?

  • 0 in reply to Austin Tanner
    Intellectual 685 points

    Hi Austin,

    After discussion with my team we want to rephrase the query as follows:

    CC3220 will be passing the data between the external host processor and the Wi-Fi interface.  

    We want to use CC3220 for providing us the Wi-Fi functionality mainly.  No peripherals (camera, audio serial port etc.) are supposed to be attached to CC3220.  The peripherals will be connected to the external host processor and it will only pass the data onto CC3220 for transmission/reception over Wi-Fi/Radio.  Thus the external host will be shouldering the burden of peripherals and passing data to CC3220.  CC3220 will only be carrying data and doing some Wi-Fi related activity that the NWP is not offloading onto itself.

    We believe this way we will have the host driver running on CC3220 and save memory/processing power on the external Host processor.  

    Our questions are:

    1. Will this be significant saving?  How much is the impact of the host driver on the host MCU in terms of memory/processing power?  Lets assume that the complete (Full) set of APIs is used as against the other two possibilities of Tiny and Customized set of APIs.
    2. Is there a framework available in CC3220 for such handling of data?  Or we would need to implement code to provide this functionality?
    3. Is it possible to configure CC3220 itself as an AP/STA/P2P node, its transmit power etc. directly from the external Host Processor?  Or we will have to implement it such that the CC3220 interprets the commands from external host and carries out the necessary configuration?

     

  • 0 in reply to Neeraj Sallh
    TI__Expert 8255 points

    Hi Neeraj,

    If you intend to use an external host processor and would like to have access to Wi-Fi functionality, then I'd recommend using the CC3120 device as this is a network processor without a host MCU.  If you'd like to have an integrated host MCU and an network processor the CC3220 is a great choice.

    Regarding your questions:

    1. I'm referencing the CC3100 datasheet and found that it mentions the host driver footprint is less than 7KB of code memory and 700 B of RAM for TCP client application.
    2. The host driver is included in our SDK releases and can be used in your application.
    3. Please reference the programmer's guide for information on configuring the device in AP/STA/P2P mode, etc.