• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 55 subscribers
  • Views 500 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.

Compiler: I use CC3235SF to do a stress test based on TCP sending and receiving data, it will freeze

user6484902
Prodigy 100 points


Tool/software: TI C/C++ Compiler

As mentioned in the title, connect to the AP and create a TCP connection,

One computer uses the serial port assistant to send an AT command AT+Send = 0,0,100,111 every 100ms, which controls the wifi module client to send 100 bytes each time, and the other computer acts as a TCP server to receive it with the network debugging assistant, the distance is three to four About meters, I finally found that it was stuck when it was sent 573,524 times, and the serial port did not respond to the command, so the server could not receive the data.

Another wifi module was also tested synchronously and sent an AT command AT+Send = 0,0,500,111 at an interval of 50ms, and finally found that it was stuck when it was sent about 254,058 times.
This is a very serious problem. I don't know what is wrong with the at_commands routine, wifi module, and hardware circuit?

  • 0
    Guru 80445 points

    Hi,

    You should to use JTAG and determine what is going on. AT command example is only code running at application processor. Code of AT command example you have available at SDK and you can change this code or debug them if you need.

    btw ... what SDK and ServicePack do you use?

    Jan

  • 0 in reply to Jan D
    Prodigy 100 points

    I thought that using the command example to do such a test would not get stuck and only lose packets, but the result was out of my expectation, using the newer SDK and 4.8 SP

  • 0 in reply to user6484902
    Guru 80445 points

    Hi,

    As I said. You should use JTAG and determine what is going on at code.

    Jan

  • 0 in reply to Jan D
    Prodigy 100 points

    Hi,

    I was wondering why there was a problem with the official AT_command demo program to do this stress test. Has TI ever done a similar test for this demo？

  • 0 in reply to user6484902
    Guru 80445 points

    Hi,

    I am not able answer question what exact tests was done at AT_command demo with CC3235. Please wait for answer from TI.

    If I am not wrong TI used network_terminal example for throughput measurement. Maybe you can test with this example.

    Jan

  • 0 in reply to Jan D
    TI__Mastermind 22935 points

    Hello,

    We do not stress test with AT command demo like you are doing. Could you explain to us your setup and what is going on after the failure? I understand you interface our device to a computer via UART. I'm guessing you have some computer program calling AT+send every 100ms. 

    Have you tried analyzing air logs or debugging the device once the failure occurs via JTAG? I can't think of any reason why this failure would happen. I don't have enough information right now to help further. 

    Jesu