lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] LWIP 1.4.1 uploading problem


From: Sergio R. Caprile
Subject: Re: [lwip-users] LWIP 1.4.1 uploading problem
Date: Mon, 1 Aug 2016 10:05:49 -0300
User-agent: Mozilla/5.0 (Windows NT 6.1; rv:45.0) Gecko/20100101 Thunderbird/45.2.0

Let me do a bit of a disection here.
ST is a vendor who is taking code from lwIP.
You are using ST code, which for some pieces may be lwIP, for others may be vendor modified code. There is your code, ST code, and lwIP code. There is some sort of POST in the form of some cgi functions in the browser in the contrib tree in 1.4.1. The browser calls user functions, user functions are not part of the browser, they are either ST code or your code. lwIP is an open source project and people who help on this list is mostly volunteering. Even if there is the possibility that the problem is on lwIP code, you are the one who is having the problem, and if you expect someone to help you, you should start by explaining what you are doing with the stack; and that means posting code, capturing traffic, giving extended descriptions, and having good manners. I don't know the ST libraries, maybe someone else does, I won't search them; you can wait for someone else to kick in if you please, however.
My advice to you is:
diff against the official lwIP distribution to check for vendor modifications identify and understand what is your code: the callback functions that are called when the browser POSTs. If some of that is ST's, that is not lwIP, is ST. verify your code against the recommendations in the docs. If you are unsure, you can post your code and someone will surely comment about it. capture the traffic and analyze what happens at the point where it stops working. You can post it, many of us appreciate it. define in clear terms what happens when the upload stops. Is your callback function not called anymore ? What do you see on the wire ? What do the debugging and statistics log tell you ? Do you run out of memory buffers maybe ? Are you properly freeing pbufs?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]