Hi Thomas,
On Wed, Mar 06, 2013 at 06:43:15AM -0800, ThomasJ wrote:
> Hi
>
> Just an idea... and would it work?
>
> If I keep my TX task and RX task.
> I then make make sure the TXTask does not use the netconn_write while the
> RXTask is in the netconn_recv call.
> Would that be ok or must the n
Hi
Just an idea... and would it work?
If I keep my TX task and RX task.
I then make make sure the TXTask does not use the netconn_write while the
RXTask is in the netconn_recv call.
Would that be ok or must the net connection be handle only by the same task?
Thomas
--
View this message in con
Hi Thomas,
On Wed, Mar 06, 2013 at 03:03:55AM -0800, ThomasJ wrote:
>
> or is it better to use a semaphore around the netconn_recv and
> netconn_write, so no write can be done during receiving and no receive
> during wrie?
>
> How does you handle it?
This is exactly the same from the lwIP point
Hi Sylvian
Just to be clear.
So I do have todo something like with a small receive timeout for the
netconn:
CombinedTXAndRXTask()
{
// Do connections handlign
WaitForLink();
xNetConn = netconn_new(NETCONN_TCP);
netconn_connect ( xNetConn, &remote_ip, sPortNumber );
Hi Thomas,
On Wed, Mar 06, 2013 at 01:14:57AM -0800, ThomasJ wrote:
>
> Could it be the fact I'm using netconn_write in one task and netconn_recv in
> another? Would it help using them in the same task? (First check for
> received data and then send data if any to send?)
Yes, this is the issue,
Hi
In my current system I do have a TXTask or sending data to the server and a
RXTask for receiving data from the server. They use the netconn API..
I do have some problems getting the stack to run smoothly. It is just a
matter of time (many hours) until the netconn API/stack stops working. I
sti
