• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 4 answers
  • Subscribers 41 subscribers
  • Views 1845 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.

CC3220: Smart lock chipset discussion

Dawson Mossman
Prodigy 35 points

Part Number: CC3220

Hi, we are in the process of developing a smart lock spec and I'd like to have a general discussion about our requirements and your recommendations / products that could be a good fit. One of the chips we are looking at is the CC3220 running Amazon RTOS. We also have a need for a camera (lens + chipset) and motion sensor. Would also like to discuss potential for ODM. Thanks. 

  • 0
    Guru 39650 points
    Hi,

    CC3220 is good SoC for your purpose. First thing you need to realise what resolution you need. CC3220 is "small" low-power WiFi SoC and from this reason you cannot use camera with high resolution (1080p, etc.).

    Few examples (designs) for previous generation CC3200, you can take as start-point:
    - www.ti.com/.../TIDC-CC3200-VIDEO
    - processors.wiki.ti.com/.../CC3200_Websock_Camera_Application (example in CC3200 SDK).

    Jan
  • 0 in reply to Hnz
    Prodigy 35 points
    Would this SoC handle a camera with 720p at 30 fps. This would be intermittent use; probably 30sec to 1min bursts several times throughout the day. Could we still use that SoC and have it handle wifi, etc if we also included a dedicated chip for handling the camera, encoding, ...

    Is it possible to setup a call with someone so we could discuss this further?
  • 0 in reply to Dawson Mossman
    TI__Guru* 91206 points

    The CC3200 and CC3220 are being used by commercially available products with both 720p and 1080p resolution video encoders - the previous statement about that (made by Jan) is not correct to this point.

    The CC32xx can be the host of the video encoder and communicates over SPI interface.
    See the reference design Jan pointed to in the first response and think about using OV-798 or similar versus OV-788 for higher resolution.

  • 0 in reply to Dawson Mossman
    Guru 39650 points

    Hi,

    At TIDC-CC3200-VIDEO reference design is used camera with OmniVision OV788 chipset. At this design is used 720p @ 15FPS though OV788 can deal with 720p @ 30 fps. I am not sure if CC3200 (CC3220) is able deal with 30 fps. You should discuss this with TI engineer.

    In this case probably best contact for you can be Josh ( https://e2e.ti.com/members/614 - head of WiFi App Team). Please send him message directly. He can forward your message to proper person. Due to Christmas time can be response time probably longer.

    Update: Yeh, Josh was fastest :)


    Jan

  • 0 in reply to Hnz
    TI__Guru* 91206 points
    the OV788 supports 720p @ 30fps. The communication is over SPI, which at that resolution is only requiring ~2Mbps on an SPI that can handle 20Mbps. 1080p is needing between 4-5Mbps...still no issue for the SPI of the CC3200 or CC3220.
  • 0 in reply to Josh Wyatt
    Prodigy 35 points

    Thank you Josh, I'll look into this further. It sounds like the CC32xx would have no problem also handling a motion sensor and servo motor used to move the lock? What bus would these typically use? Sorry, but I'm a bit new to this stuff. 

    Does TI engage with companies to work on ODM solutions (pcb, etc)? How does that conversation get started?

  • 0 in reply to Dawson Mossman
    TI__Guru* 91206 points
    Dawson -
    Sensor interfaces used are/can be digital or analog (depends on the sensor and how integrated you need that to be) - for example, one configuration i have seen to be popular is the muRata IRSB210ST01, used in conjunction with an LPV802 (op amp) and a TLV3691 Window Comparator, which would feed an interrupt out to a GPIO. One could also feed the output of the op amp into the ADC of the CC3200 or CC3220 to reduce BOM slightly, if needed. If you want something already premade to use as a reference for software development - seeed studio offers several models of PIR sensors which just need power and put out the interrupt signal to do same.

    for the servo motor - we do have GPIOs and PWM peripherals on the MCU which you can leverage - the DRV8833 would be a good choice for the motor driver itself and it can be driven from GPIO, as mentioned.

    you may also want to consider using CapTIvate for your keypad, this offers the ability to do some proximity sensing as well as have robust weather hardened human interface.

    See these TI designs to get some more system details on the discussion points above:
    www.ti.com/.../TIDA-00489
    www.ti.com/.../TIDA-00757
    www.ti.com/.../TIDM-CAPTIVATE-E-LOCK
    www.ti.com/.../TIDM-1004

    Regarding engagement with ODMs - the E2E Forum is a great way to get that started, as you have done. Typically, we expect the company and ODM to either use this Forum for help or if direct involvement by TI is needed for some reason, then we can take it off the Forum and discuss directly what is needed, then leverage our FAEs (for local support, depending on the region and their other work loads) - our level of involvement is something we strive to keep at an appropriate level - meaning - we want to help all the folks we can, but we do need to maintain a healthy balance - hope that makes sense.

    If you need to discuss privately - you can friend request me on this Forum and provide your contact information, background details of the opportunity and we can take it from there.