• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 475 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.

CCS/CC3220S-LAUNCHXL: CC3220S automatically become AP

Siqi Zhang
Intellectual 280 points
Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: CC3220S, UNIFLASH

Tool/software: Code Composer Studio

Using official routines, serial_wifi_CC3220S_LAUNCHXL_tirtos_ccs,CC3220S, as STA, automatically finds a fixed AP connection. If no target is found after 6 seconds, you can manually select an AP connection by sending AT instructions through the serial port.

Experimental results: The first debugging, the results and instructions are consistent, but the second debugging found a running program, CC3220S automatically become AP, why? What are you going to do?

I tried factory reset and reset on the parameter configuration page, but it was unsuccessful.

I really need help. Thank you very much.

  • 0
    TI__Mastermind 40965 points
    Hi,

    Running the serial_wifi example from the latest SDK v.3.10.00.04, I cannot replicate what you're seeing.
    In my testing, the program starts up in STA mode, and will try to connect to a saved profile. If there is no profile, then it will wait for input in the form of an at+wlanconnect command or a at+wlanprofileadd command. This behavior is consistent across resets and debug sessions.

    While the program will not deliberately set the device into AP mode without the user sending an AT command to do so, it is possible that another program that ran before launching the serial_wifi example set the device into AP mode. Do you have another program flashed onto the CC3220? By default, the device comes with the out_of_box demo program, which does make use of AP mode. You can try reflashing the CC3220 without an MCU image, or with the serial_wifi binary to prevent the out of box program from running. The simplest way to do so would be to import the Uniflash project provided with the local_ota example. To do so, follow the instructions at the SimpleLink Academy module from "Importing and Opening a Project":dev.ti.com/.../node
    Then, import the project at /examples/rtos/CC3220S_LAUNCHXL/demos/local_ota/uniflash/cc3220s_local_ota_tirtos.zip.

    Try flashing that image to your CC3220S launchpad and seeing if you get the correct behavior.

    Regards,
    Michael
  • 0 in reply to Michael Reymond
    Intellectual 280 points
    Thanks for your help. Write a new program through UniFlash, flush out the default program, and debug it online. The result is correct.
    But I am still very confused, let me explain my operation in detail: the first debugging, did not find AP, use AT command input AP (my phone), but I input AT command format wrong:\\<AT+WlanConnect = vivoX9,,open,,,,(correct: \\\\<AT+WlanConnect = vivoX9,,open,,,,The mistake was discovered only today)
    Because there is a private affair out of the middle did not continue to operate behind. Later began to debug the second time, found click debug it directly into the AP automatically, don't know is which operation caused this phenomenon, although I don't have to write program into the Flash, but I am online debugging, he should not directly in the memory to run on my program, rather than directly to the Flash on the default program run the program into memory, I wonder if you have any comment on this phenomenon?
  • 0 in reply to Siqi Zhang
    TI__Mastermind 40965 points

    Hi,

    When you run your program from the debugger, it will not be copied to flash, only to the RAM of the device. Thus, when you reset the device it will clear your program from RAM and execute whatever code was programmed to flash. If you have programmed the device with a blank program like I mentioned, then you shouldn't have anything execute when you reset the device and let it free run from flash.

    Unless you are using the wlanprofileadd command, your device should not connecting to an AP automatically after starting the serial_wifi example. If it is connecting automatically, this indicates that a Wi-Fi profile was added to the device. This can be done through a variety of methods:

    • Using the  \\<at+wlanprofileadd= command
    • Using the CC3220 web interface to add a profile through the online config pages
    • Running another program that automatically writes a profile to the CC3220 during runtime

    Have you double-checked to ensure that you are not adding a profile at some point between debug sessions?

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Intellectual 280 points
    I have something to do recently, so I'm really sorry for replying you so late. Thank you very much for your help. I did use \\<at+wlanprofileadd= command in debugging
  • 0 in reply to Siqi Zhang
    TI__Mastermind 40965 points
    Hi,

    If you use the at+wlanprofileadd command, then the behavior you are getting is expected. at+wlanprofileadd is designed to persistently add Wi-Fi connection details to the CC3220, and have it connect automatically to it when the device is in range of that network.

    See section 4.3 of the NWP programmers' guide for more details:
    ti.com/lit/swru455h

    Let me know if you need more clarification, or have further questions on the issue you are seeing.

    Regards,
    Michael
  • 0 in reply to Michael Reymond
    Intellectual 280 points


    Thank you very much for your answer.

    I am sorry for replying you so long and I have no more questions about the at+wlanprofileadd command, thanks for the detailed link.

    And may I ask if  UART can receive data of variable length?I want to use UART DMA to receive a frame of data, and when a frame ends, I send it out.