Other Parts Discussed in Thread: DP83869, AM2432
Hi,
we are looking at the example enet_lwip_cpsw_am243x-evm_r5fss0-0_freertos_ti-arm-clang in the MCU+ SDK to determine code/data size for the Lwip TCP/IP stack.
Looking at the .map file (attached) we see roughly the following:
|
size |
|
.text |
718,768 |
|
.rodata |
141,632 |
Rom: 860,400 |
.data |
50,176 |
|
.bss |
400,896 |
|
.bss:ENET_DMA_DESC_MEMPOOL |
28,672 |
|
.bss:ENET_DMA_RING_MEMPOOL |
16,384 |
|
.bss:ENET_DMA_PKT_MEMPOOL |
172,032 |
|
.bss:ENET_DMA_OBJ_MEMPOOL |
11,788 |
|
.bss:ENET_DMA_PKT_INFO_MEMPOOL |
0 |
|
.bss:ENET_ICSSG_OCMC_MEM |
0 |
Ram: 679,948 |
Q1) Can we consider the size of Rom and Ram in table is the footprint of Lwip stack? It may include the size of code and data for application as well.
Q2) Can we reduce the size of .bss:ENET_DMA_*? What is the minimum size for those?
Overall we are looking for opportunities to reduce code/data size for the network TCP/IP stack. Have you analyzed this and have maybe already suggestions on where things can be reduced?
Thanks!
--Gunter