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.

OMAP4460 Interfacing with CC3000

Other Parts Discussed in Thread: CC3100

I am working on a hardware design of OMAP4460 based WiFi board. I want to interface CC3000, I would be interfacing that CC3000 with the SPI protocol.

Q1) do I need to use SimpleLink API or have to design my own drivers?

Q2) Will CC3000 be sufficient or I have to choose CC3100, which can offload the processing from OMAP4460?

Thanks.

  • Hi Rushi,

    To answer your questions:

    -1- Current kernel releases (both Android & Linux) are for OMAP44xx Reference boards (Blaze, Blaze Tablet & Pandaboard) and they use WiLink, so you will have to do some development to integrate the SimpleLink API in the existing kernels.

    -2- OMAP4460 is powerful enough to use the CC3000, but nevertheless CC3100 is the better choice.

    Best Regards,
    Yordan

  • Hi Yordan, Thanks for the reply.

    -1-If I use CC3000, What can be the level of effort do I need to put to integrate the SimpleLink with the existing kernel, are there any guidelines or source that can help?

    -2- Do I need to put Flash programming device for the CC series on the board? (what my belief is, Once it has to be programmed to get the stream of data through SPI)

    -3- As my point of view, 

    1. CC3000 will just transfer data over SPI without making any changes, the host MCU (which will receive data from CC3000 through SPI) has to take care of interpreting data into useful information. so the computation overhead is on Processor (OMAP4460 in my case).
    2. CC3100 will receive data through WiFi and convert that data into useful information (removing the headers, converting to plain decoded text and vice versa) and then it will sent to host processor through SPI, so computation overhead is totally removed from the host processor.

      1. So the question is, CC3100 will offload the OMAP from the IP/Network processing, all I need is to take care the receiving information through SPI, so if I am not wrong, I need not to integrate Simplelink with existing kernel for C3100, right?

    Best Regards,

    Rushi Gajjar.

  • Hi Rushi Gajjar,

    What I can answer is:

    -1- You will have to start integrating the Simple link from scratch (as I said neither of current omap4 kernel releases has the API integrated). You will not have to develop the driver from scratch, just integrate it in OMAP4 linux kernel. You can use the following links (a search in e2e for CC3000 will return other useful threads) for guidacne:
    http://e2e.ti.com/support/wireless_connectivity/f/851/t/171172.aspx

    http://processors.wiki.ti.com/index.php/CC3000_Host_Driver_Porting_Guide

    http://processors.wiki.ti.com/index.php/CC3000_Host_Programming_Guide

    http://processors.wiki.ti.com/index.php/CC3000_Smart_Config

    http://processors.wiki.ti.com/index.php/CC3000_Patch_Programmer

    http://processors.wiki.ti.com/index.php/CC3000_Release_Notes

    For additional hw info on the CC chips you can always use the SimpleLink™ WiFi - CC3000 Forum http://e2e.ti.com/support/wireless_connectivity/f/851.aspx, as well.

    -2-

    Rushi Gajjar said:
    Do I need to put Flash programming device for the CC series on the board? (what my belief is, Once it has to be programmed to get the stream of data through SPI)

    I think you can get better answer to this question in the SimpleLink™ WiFi - CC3000 Forum: http://e2e.ti.com/support/wireless_connectivity/f/851.aspx . I am not that well familiar with the functionality of the CC devices.

    -3- Your understanding:

    Rushi Gajjar said:
    • So the question is, CC3100 will offload the OMAP from the IP/Network processing, all I need is to take care the receiving information through SPI, so if I am not wrong, I need not to integrate Simplelink with existing kernel for C3100, right?

    is correct.

    That is why I said CC3100 is the better choice, because making omap convert the CC data into useful information will result in additional efforts in the sw porting stage. 

    Best Regards,

    Yordan

  • Thanks Yordan, I have proposed CC3100 for the current iteration, I will update you whatever the issues are.

    I am rectifying the hardware issues regarding the Flash programming of the CC3000/CC3100. Whatever the result comes, I will let you know.

    Best Regards,

    Rushi Gajjar.