May 15, 2013
09:39 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 15, 2013
09:39 PM
- WICED SDK 2.3.0
- ThreadX/NetX Duo, BCMUSI11
When <WICED module> receive the mass data via <TCP-connection>, sometimes <NetX or BCM43362> hang up.
Here is my test diagram.
[ATTACH=CONFIG]143[/ATTACH]
Here is the test-screenshots.
[ATTACH=CONFIG]144[/ATTACH]
[ATTACH=CONFIG]145[/ATTACH]
After researching the capture file, I guess that the problem it is related with <TCP Window resize stuff>(WICED_TCP_WINDOW_SIZE). But, because I dont have the NetX source, I could not debug it any more.
Thanks in advance.
Steve
Labels
- Labels:
-
TCPIP
- Tags:
- 2.3.0
- advance
- bcmusi11
- capture
- data
- debug
- diagram
- file
- guess
- hang
- hang-up
- mass
- netx
- problem
- problemtcp
- receive
- related
- researching
- source
- steve
- test
- test-screenshots
- threadxnetx
- throughput
- wiced
- wiced_tcp_window_size
4 Replies
Anonymous
Not applicable
May 16, 2013
12:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 16, 2013
12:07 AM
Do you have MCU and/or Wi-Fi powersave enabled?
May 16, 2013
12:36 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 16, 2013
12:36 AM
No, I didnt use <MCU or WiFi Power Save functions>.Anyway, after I changed the TCP_WINDOW_SIZE as below, the <hang-up problem> never happened. //#define WICED_TCP_WINDOW_SIZE (14*1024)#define WICED_TCP_WINDOW_SIZE (2*1024)As I said before, I guess that this problem is related <TCP Window Resize>.Steve K
Anonymous
Not applicable
May 16, 2013
07:44 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 16, 2013
07:44 PM
Cool, so your issue is solved now?
May 22, 2014
10:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 22, 2014
10:28 AM
We have the same issue, except that it always occurs. Solution that has worked for Steve K does not work for us. Any idea, what could be the cause?