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

CC3135MOD: Does CC3135MOD support AT command?

Poh Kok Keng
Genius 5112 points
Part Number: CC3135MOD
Other Parts Discussed in Thread: CC3220S, CC3220SF, , CC3135, CC3235SF

Dear Expert,

According to SWEU534D https://www.ti.com/lit/ug/swru534d/swru534d.pdf 

It only mentioned this is supported in CC3200R, CC3220S, CC3220SF.

Can i know is CC3135MOD also can support AT command as well? 

Best regards,
Felix

  • 0
    TI__Intellectual 1600 points

    Hello Felix,

    The CC3135MOD cannot support AT commands because that device is a Wi-Fi network processor only device, and will need another MCU running the Wi-Fi host driver for operation. Communication with CC3135 is done via TI proprietary protocol. Translation from sl_ function calls to TI proprietary protocol is done via SimpleLink (host) driver. SimpleLink driver is available in C code and need to be executed at your MCU (host).

    If you want to use AT commands, you need to select CC3235 and run at this MCU TI firmware which translates sl_ API calls to AT commands. 

    Regards,

    Jonathan 

  • 0 in reply to Jonathan Cohen
    Genius 5112 points

    hi Jonathan,

    Can i check if the customer already have an external MCU in their design, are they able to move this AT protocol to this external MCU to run? does TI share the source code for this AT implementation? 

    Best Regards,
    Felix

  • 0 in reply to Poh Kok Keng
    Guru 73255 points

    Hi Felix,

    Source code is available inside CC32xx SDK (example at_commands - examples\rtos\CC3235SF_LAUNCHXL\demos\at_commands\ and libraries inside \source\ti\net\atcmd\). You customer can port this code to their own MCU without any restrictions. But porting of code will require some effort. How much depends on experiences with CC31xx/CC32xx devices.

    First step of porting is to port host driver (code which translate sl_ API calls to SPI communication) - see SWRU455 chapter 19. After that can be ported slnet layer and AT command library.

    Jan