Re: [lwip-users] Porting 2.1.2 to Atmel Studio 7... dirent.h?

2019-02-08 Thread goldsimon
Am 8. Februar 2019 20:18:23 MEZ schrieb Stephen Cowell : > >On 2/7/2019 11:39 PM, goldsimon wrote: >> Am 8. Februar 2019 00:27:58 MEZ schrieb Stephen Cowell >> : >> ... > >> > Does everyone have to go through and edit >> >the >> >header file includes to reflect the new structure?  I can't see

Re: [lwip-users] Porting 2.1.2 to Atmel Studio 7... dirent.h?

2019-02-08 Thread Stephen Cowell
On 2/7/2019 11:39 PM, goldsimon wrote: Am 8. Februar 2019 00:27:58 MEZ schrieb Stephen Cowell : ... > Does everyone have to go through and edit >the >header file includes to reflect the new structure?  I can't see why >this >is not fixed in the release. That should not be required. Can you

Re: [lwip-users] Porting 2.1.2 to Atmel Studio 7... dirent.h?

2019-02-08 Thread Dave Nadler
Hi Steve - While not exactly your challenge, I recently had to update an LwIP 2.x to the latest, on an ST project (easier change than from 1.x). I've attached my notes below; perhaps they will help, Best Regards, Dave ST distributes a lwip 2.x version which is not up-to-date and cleverly has

Re: [lwip-users] retransmission in lwip2.0

2019-02-08 Thread Sergio R. Caprile
What I see is that the slave seems to respond but its response is not in the capture. This means that the frame is not getting there, it is getting lost somewhere in between. If the slave is an lwIP device, then it is quite likely your driver+port are losing frames. Vague questions usually get

[lwip-users] TCP snd_queuelen issue (Jasper)

2019-02-08 Thread Jasper Verschueren
Hi Simon, I don't think they directly influence snd_queuelen but they do influence the function where this assert is triggered. I thought maybe bug #51447 could have something to do with it because it influences the while loop around the assert (TCP_SEQ_LEQ). I thought maybe bug #48839