On 18.09.2018 09:53, Andy Pont wrote:
[..]
I tried to follow this code but couldn’t find some of the defines. It
turns out this project hasn’t been updated and is still running v1.4.x
code!
Ok, that's not good news. You'll find many bugs fixed in the last 6 years!
Looking through the .map
Simon wrote...
Yes. Just follow the defines:
LWIP_MALLOC_MEMPOOL() -> LWIP_MEMPOOL() -> LWIP_MEMPOOL_DECLARE() ->
memp.h lint 95 (git head) instantiates the memory via
LWIP_DECLARE_MEMORY_ALIGNED()
The plot thickens…
I tried to follow this code but couldn’t find some of the defines. It
tu
On 17.09.2018 22:20, Andy Pont wrote:
That macro allocates pools of X elements with Y bytes each.
It allocates (14 * 75) + (6 * 225) + (1 * 525) + (3 * 1540) bytes
plus a little offset for administration, so roughly 7,5 kB.
Is that memory being allocated by the linker in either the .data or
.bs
That macro allocates pools of X elements with Y bytes each.
It allocates (14 * 75) + (6 * 225) + (1 * 525) + (3 * 1540) bytes plus
a little offset for administration, so roughly 7,5 kB.
Is that memory being allocated by the linker in either the .data or .bss
sections or is it pulled from the hea
On 17.09.2018 18:10, Andy Pont wrote:
Hello,
I’m trying to figure out the memory settings being used by a project
that I have inherited. The lwipopts.h file contains:
#define MEM_USE_POOLS1
#define MEMP_USE_CUSTOM_POOLS1
#define MEM_USE_POOLS_TRY_BIGGER_POOL1
I think this means that it allo
Hello,
I’m trying to figure out the memory settings being used by a project
that I have inherited. The lwipopts.h file contains:
#define MEM_USE_POOLS1
#define MEMP_USE_CUSTOM_POOLS1
#define MEM_USE_POOLS_TRY_BIGGER_POOL1
I think this means that it allocates the memory that is defined in
lw
