• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Answers 4 answers
  • Subscribers 41 subscribers
  • Views 594 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC3120BOOST: Simplelink host driver for CC3120BOOST

PaulLee
Prodigy 170 points
Part Number: CC3120BOOST
Other Parts Discussed in Thread: CC3120, CC3135, CC3100, CC3200

Hi,

I got CC3120BOOST board for WPA_ENT service.
My host MCU is STmciro MCU.
I don't want to modify CC3120 internal F/W at all.

But, I cannot find host driver to port to stm32F MCU.
If I want to use AT command, do I have to update CC3120BOOST F/W?

BR
Paul

  • 0
    Prodigy 170 points

    In swra704.pdf, 2.1

     In the SimpleLink Wi-Fi CC32xx SDK, this porting layer is implemented for ***** the on-chip ARM M4 application microcontroller ****. The porting layer distributed in the and SimpleLink SDK Wi-Fi Plugin is implemented ***** for other microcontrollers in the SimpleLink platform family *****.

    1. "SimpleLink Wi-Fi CC32xx SDK" is for application running on CC3120 on-chip ARM core?

    2. What "SimpleLink platform family." means? 

    What package do I have to port to stm32 MCU?

    BR
    Paul

  • 0 in reply to PaulLee
    TI__Guru 63006 points

    See the porting guide to STM32 (https://www.ti.com/lit/pdf/SWRA704).

    AT command was developed as an MCU application on CC32xx (i.e. the MCU device and not the CC31xx NWP only) to provide access to external host over UART. The application in this case is a proxy the transfer AT Commands to SL (NWP) API and vice versa.

  • 0 in reply to Kobi Leibovitch
    Prodigy 170 points

    I understand about AT command, I need CC32XX....

    My question is from reading swra704...
    I have to port SimpleLink SDK Wi-Fi Plugin to stm32... right?

    BR
    Paul

  • 0 in reply to PaulLee
    TI__Guru 63006 points

    if you are using CC31xx (i.e. not through the AT-Commands) - Then the you'll need to port the driver according to the instructions in swra704.

  • 0 in reply to Kobi Leibovitch
    Prodigy 170 points

    Hi,

    I'm porting WiFi plugin to stm32 now.
    I do not use OS, non-OS.

    In case of non-OS, do I have to port "2.5 OS Abstraction: FreeRTOS part" in swra704?
    Sone source in simplelink_sdk_wifi_plugin_4_20_00_10 use OS abstraction object.
    I do not define SL_PLATFORM_MULTI_THREADED.

    And I ask again, do I have to port "simplelink_sdk_wifi_plugin_4_20_00_10" only? no need cc32xx_SDK?

    BR
    Paul

  • 0 in reply to PaulLee
    TI__Guru 63006 points

    You can look at the simplelink driver build configuration for "norots" (and on the nortos example from the plugin). I believe there are other differences in the pre-defined symbols.

    If you point to the exact code that causes the issues - I should be able to help.

    I would recommend that once you understand the porting steps you would replace the driver with the one from CC32xx SDK 7.10 which is the latest one (the porting itself should be mostly the same as the 4.20 release).

  • 0 in reply to Kobi Leibovitch
    Prodigy 170 points

    Hi,
    In C:\ti\simplelink_sdk_wifi_plugin_4_20_00_10\examples\nortos\MSP_EXP432P4111\demos\trigger_mode/main_nonrtos.c

    The mainThread () is called. But mainThread ()  API is not in simplelink_sdk_wifi_plugin_4_20_00_10.
    mainThread API is defined in ti\simplelink_cc32xx_sdk_7_10_00_13
    Do I have to port ti\simplelink_cc32xx_sdk_7_10_00_13 also with simplelink_sdk_wifi_plugin_4_20_00_10?
    It is hard to port to MCU not from you.

    BR
    Paul
  • 0 in reply to PaulLee
    TI__Guru 63006 points

    mainThread is defined in "trigger_mode.c" (in c:/ti/simplelink_sdk_wifi_plugin_4_20_00_10/examples/nortos/MSP_EXP432P4111/demos/trigger_mode/trigger_mode.c).

  • 0 in reply to Kobi Leibovitch
    Prodigy 170 points

    Sorry.

    My editor always link rtos mainThread Disappointed
    So, I missed it.

    ---- 
    In the example,  nortos trigger_mode.c call "ClockP_setTimeout".

    And, ClockP_setTimeout () is defined in ClockPTimer_nortos.c

    ClockPTimer_nortos.c includes "timerP.h"
    But "timerP.h" is included in "C:\ti\simplelink_cc32xx_sdk_7_10_00_13\kernel\freertos\dpl" folder.

    I don't use RTOS.

    Do I have to port step by step like this?

    BR
    Paul 

  • 0 in reply to PaulLee
    TI__Guru 63006 points

    I think you shouldn't try to port the dpl part (such as ClockP...). This was not designed for this,

    Instead you should provide STM32-NORTOS implementation to the services as listed in simplelink/user.h: e.g. sl_SyncObjWait,

    sl_LockObjLock

    You can use the DPL sources as a reference.

  • 0 in reply to Kobi Leibovitch
    Prodigy 170 points

    Hi,

    My host MCU use UART interface instead of SPI to CC3120 module.
    First response received from device is ba,dc,cd,ab,08,00,14,00

    I checked this data by a tool.

    Device to host  sync word is AB CD DC BA according to user's guide.

    High low nibble is swaped.
    Is it right?

    BR
    Paul

  • 0 in reply to PaulLee
    TI__Guru 63006 points

    Are you reading the response byte by byte (from memory or from the SPI) or as a 32B word?

    BTW. not related to the issue - I just saw that you are using the CC3120 for WPA_ENT. Are you aware if the CC3120 limitations? It only supports TLS1.0 for the EAP connections. It typically makes an issue as most enterprise networks requires TLS1.2 today. 

  • 0 in reply to Kobi Leibovitch
    Prodigy 170 points

    Hi,

    I use UART for interface CC3120.
    STM32 UART DMA driver is set to byte transfer. And I I read byte to byte from memory.

    ------

    Yes, right. I select this CC3120 module for WPA_ENT.
    Thanks you for information about TLS version you support today.
    When will you support TLS1.2?

    --------

    Anyway I am monitoring on the line MCU and CC3120.

    This is the capture image on the physical  UART line from CC3120 module by using terminal program.

     
    BR
    Paul

  • +1 in reply to PaulLee
    TI__Guru 63006 points

    yes, the monitored data seems ok.

    CC3120 will not be able to support TLS1.2 (it is a ROM device and it is limited by the patches memory).

  • 0 in reply to Kobi Leibovitch
    Prodigy 170 points

    Hi,

    CC3220 can support TLS1.2?
    BR
    Paul

  • +1 in reply to PaulLee
    Guru 78435 points

    Hi Paul,

    None of CC31xx or CC32xx device (CC3100, CC3120, CC3135, CC3200, CC3220, CC3235) supports TLS 1.2 for EAP security.

    Jan