Simon,
I did use a debugger and that is how I found that it is from within recvfrom ...
As I am only a user and not the developer of LwIP I am asking for tips on how
to catch
the problem. I am not familiar with the low level internals of LwIP so that is
difficult to
find the cause.
I am
Hi Sergio,
Embedded Linux uses lots of RAM and is much more complicated from FreeRTOS.
Even is we eventually will add external RAM, say 16-32M or more I still prefer
the
FreeRTOS [] .
As for all the apss that are running in the device its a a must, system
requirements.
I am sure that
Hi Sergio,
Long time :-) ...
Yes I am aware of what you wrote. Inside the recvfrom function this is actually
what the
function is doing... copying in parts from the chained buffers until it gets
all the data it
needs.
LwIP has sufficient RAM (22K) and PCB's (80) so it should be ok ?
As long as you have the memory and CPU resources, you can have an RTOS
and as many threads as you can, with all the apps you need. lwIP main
core and RAW API apps will run on a thread, other apps with their
netconn/socket APIs on their respective threads.
The point is... do you actually
It is not a matter of possible/impossible, but how much are you willing
to thrive to do it.
Unless you do it yourself from the RFCs, you'll work with already made
parts, which most probably have been written for a socket(-like) API,
most probably on a non event-driven way.
You'll find some
A pbuf can be a single one or a chain of them, and your app gets what
the rx driver got, so most likely you can't tell in advance and have to
be prepared to just deal with it.
If you can spare the memory, you can copy to a buffer and be happy. But
if you can't spare it, there are pbuf_
Noam Weissman wrote:
> I get a read error inside lwip_recvfrom function.
> [..]
> If anyone has any ideas on what more to check or test please respond.
1: Get an idea of the error (if recvfrom returns -1, what's the corrent errno?)
2: Get a debugger and try to find out why recvfrom returns an
Hi Jan,
As a continuation to our previous correspondence we had so far.
Just to remind you all, I have an STM32F427 (192+64 K RAM) running FreeRTOS 9
LwIP 2.01 and mbedTLS 2.xx (do not remember) ... All of the 64K is dedicated for
compiler heap, actually for SSL as all other memory usage is
