Hi Stephen,
Unfortunately I'm not using Atmel Studio. Anyway, one thing that comes
to my mind is that maybe at some point (e.g. in your ftpd code) there is
a call to tcp_abort() from a TCP callback that does not return ERR_ABRT
(see the tcp_abort() description). Not sure if this could cause
Dear Sergio,
GMAC is Atmel stuff, of course.
It seems to me that in the Atmel application note, deduction of MEM_SIZE
meaning is wrong.
So if someone aware of lwIP memory internals can confirm it, we can tell
Atmel to correct that app note... before using it for improving lwIP
documentation
There is no reference to 'GMAC' in the whole lwip tree.
That seems to be Atmel stuff and you should ask them
--
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
>On 20/03/2015 17:56, Sylvain Rochet wrote:
>They even do perfect documentation (perfect documentation is almost
>always the case with Atmel) about lwIP[1], way better than our own lwIP
>documentation, and which really prove they have a deep understanding of
>lwIP internals.
>We really
Hi Bill,
On Wed, Oct 14, 2015 at 03:08:07PM +, Bill Auerbach wrote:
> On 20/03/2015 17:56, Sylvain Rochet wrote:
> >
> > They even do perfect documentation (perfect documentation is almost
> > always the case with Atmel) about lwIP[1], way better than our own
> > lwIP documentation, and
Hi Stephen,
On Wed, Oct 14, 2015 at 09:13:59AM -0500, Stephen Cowell wrote:
> Hey Enrico,
> I'm using GNU toolchain/compiler, supplied with Atmel Studio 6.1.
> Since I've added the code I've had no other problems; I really don't
> have much time to research this, what with other pressures at
Well, I'm by no means even close to an expert, but afaik that certainly
depends on how you configure lwip.
PBUF_RAM is a single consecutive chunk of RAM for a pbuf, taken from the
heap.
PBUF_POOL is a pbuf which is itself a chain of pbufs, which are chunks
of RAM taken from the pool.
Allocation
Hi Stephen,
Maybe your workaround is not a safe way to overcome the problem: at that
point the pcb chain is already corrupted (and probably unrecoverable?).
What compiler/toolchain are you using?
Enrico
On 13/10/2015 11:48, Sylvain Rochet wrote:
Hi Stephen,
On Tue, Oct 13, 2015 at
On 20/03/2015 17:56, Sylvain Rochet wrote:
They even do perfect documentation (perfect documentation is almost
always the case with Atmel) about lwIP[1], way better than our own lwIP
documentation, and which really prove they have a deep understanding of
lwIP internals.
We really should ask
Hey Enrico,
I'm using GNU toolchain/compiler, supplied with Atmel Studio 6.1.
Since I've added the code I've had no other problems; I really don't
have much time to research this, what with other pressures at work.
It seems the issue is not unknown... sometimes the pdb ends up pointing
to
10 matches
Mail list logo
