Apr 21, 2013
10:37 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 21, 2013
10:37 AM
[WICED-SDK-2.2.1]
The NX_TIMEOUT() macro produces an overflow when used with WICED_NEVER_TIMEOUT.
This happens for instance when wiced_tcp_receive() is invoked with WICED_NEVER_TIMEOUT with unexpected results.
-Marco G.
Labels
- Labels:
-
SPI
4 Replies
Anonymous
Not applicable
Apr 22, 2013
08:03 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Apr 22, 2013
08:03 AM
Good find marcoeg,I believe the following definition of NX_TIMEOUT() should solve the problem:#define NX_TIMEOUT(timeout_ms) ((timeout_ms != WICED_NEVER_TIMEOUT) ? (timeout_ms * SYSTICK_FREQUENCY / 1000) : WICED_NEVER_TIMEOUT )
May 26, 2013
12:38 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 26, 2013
12:38 PM
Since the SDK comes without source code for NetX, how can I insure that the correct definition is used? I noticed that it is part of a Wiced layer, but just deleting the library in the build/[app]/Libraries directory, it doesnt seem enough.Can anyone suggest a workaround? Thanks,-Marco G.
Anonymous
Not applicable
May 27, 2013
05:11 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
May 27, 2013
05:11 PM
The NX_TIMEOUT() is only used in the NetX/NetX_Duo tcpip.c file which is built into the Wiced_NetX_Interface library.Running "make clean" followed by a build of your application should ensure that the new definition of NX_TIMEOUT() is used.What, specifically, is the error you are seeing?
Anonymous
Not applicable
Jun 15, 2015
02:54 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jun 15, 2015
02:54 PM
Discussion is being locked. If you have any follow-up, please start a new discussion.