CC3235MODASF: STA disconnect

Mauro Fantina

Genius 3800 points

Part Number: CC3235MODASF
Other Parts Discussed in Thread: LAUNCHCC3235MOD

Hello I'm developing

a firmware on LAUNCHCC3235MOD.

The firmware Configure SimpleLink as P2P-CLIENT and then act as TCP server:

it listens on 50002 port and accept connection.

The software on PC (the TCP client) sends a packet with a progressive byte (0,1,2,...) at position 0,

the Simple Link receives this packet, print the progressive byte on UART and the answers to PC a new packet

with the same progressive byte at position 0.

This simple test exchanges a lot of packets correctly but at a certain point Application processor receives SL_WLAN_EVENT_P2P_DISCONNECT from NWP and I loose connection.

over 5 years ago

0 Kobi Leibovitch over 5 years ago

TI__Guru 63006 points

Hi Mauro,

Disconnection can happen. There are various reasons for that.

You can read the reason code (received within the event info) and you can try to re-connect.

If re-connection happens before the TCP Keep-Alive time expires, the TCP connection may still be functional.

Br,

Kobi

0 Mauro Fantina over 5 years ago in reply to Kobi Leibovitch

Genius 3800 points

ok... but

1. I'm reading SWRU455J-February 2017-Revised February 2020 page 75: Events and Errors for SL_WLAN_EVENT_P2P_DISCONNECT and I don't find Reason Code Table

2. If I reconnect I obtain different SimpleLink IPv4 address from previous address

0 Jan D over 5 years ago in reply to Mauro Fantina

Guru 79905 points

Hi,

Please see wlan.h file.

Jan

0 Mauro Fantina over 5 years ago in reply to Jan D

Genius 3800 points

OK... but If a reconnect I obtain new IPv4 address for my SimpleLink (configured as Client) and new IPv4 address for my PC (configured as GroupOwner)

0 Mauro Fantina over 5 years ago in reply to Kobi Leibovitch

Genius 3800 points

But FAST mode in the Connection Policies could resolve me this problem ?

0 Kobi Leibovitch over 5 years ago in reply to Mauro Fantina

TI__Guru 63006 points

The fast is not expected to make a difference. It just prevents the scan before the connection.

In your case it seems that the DHCP server on the GO device is not optimized (if it really changes the ip addresses each time). Typically the a station will try to use the same IP address it used before and the DHCP server will approve it if there are no conflicts. It seems that in this P2P session this is not the case.

Please check the reason code so you can try to avoid the disconnection.

Br,

Kobi

0 Mauro Fantina over 5 years ago in reply to Kobi Leibovitch

Genius 3800 points

For DHCP server on the GO device that change IP address it could more probably that I was wrong ...
when I return to work in two weeks I'll do some tests.

0 Mauro Fantina over 5 years ago in reply to Kobi Leibovitch

Genius 3800 points

So could be a good idea to disable KeepAlive both on PC and SimpleLink side ?

0 Kobi Leibovitch over 5 years ago in reply to Mauro Fantina

TI__Guru 63006 points

What kind of keep alive? for what layer/protocol?

I don't think that disabling a keep-alive is the solution for this.

Wi-Fi

Wi-Fi forum

CC3235MODASF: STA disconnect