There is a comment in mem.c:
/** If you want to relocate the heap to external memory, simply define
* LWIP_RAM_HEAP_POINTER as a void-pointer to that location.
* If so, make sure the memory at that location is big enough (see below on
* how that space is calculated). */
#ifndef
It's much safer to integrate this with linker script (for example
with attributes on gcc). Casting number to pointer does not
guarantee that other variable will no be placed in the same area (by
linker or other Dev using such tricks). Happy debugging when it
happens :)
Yes.
However, in this
Just to continue with off-topic :)
AFAIK all solution are toolchain specific, for GCC we use:
#define MEMORY_EXSRAM1_ORIGIN 0x6000
#define MEMORY_EXSRAM1_LENGTH 4194304 /* 4M */
#define MEMORY_EXSRAM1_ATTRIBUTE __attribute__((section(.exsram1)))
And in linker script:
.exsram1 (NOLOAD) :
{
Hello
This depends in your linker, but probably it's done with the __bss() command.
Kind regards
Michael
Am 20. August 2015 17:01:46 MESZ, schrieb jo.van.montfo...@telenet.be:
Hi,
I like the lwip memory managent but HOW to point ram_heap to external
memory?
Kr,Jo
Hi,
I like the lwip memory managent but HOW to point ram_heap to external memory?
Kr,Jo
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users
Mason wrote:
I'm not sure how to do this within the pbuf infrastructure?
Normally, for a DMA-enabled MAC, you would just pre-allocate 120
PBUF_POOL pbufs (each 1536 bytes big) and pass the payload pointer to
the DMA engine. By substracting the difference between 'struct pbuf' and
its member
Hello,
I'm trying to port lwip 1.4.0 to STMicro's OS21/OS+ operating system.
I've coded the required sys_arch.c
I'm now working on the Ethernet interface code.
On my platform, reads (rx) and writes (tx) are asynchronous.
Here's how the driver works for reads:
I register a packet-handling
