Original question:
TM4C1294NCPDT: LWIP 1.4.1 Multiple Connections Eventually Results in Corrupted PCB List
I have the same problem mentioned in the post of this link, I was wondering if a solution has already been found for this
Hi Simion,
Looks like Ralph in the other post has suggested increasing the stack and heap sizes and ask you to experiment with the number of concurrent connections until the corruption occurs. However, looks like it didn't solve your problem.
I want to check with you how you increase the stack and heap sizes. Below is an example. In the CCS linker option you will change the stack and heap sizes. And in the linker command file you will also update the stack pointer to align with the size of the stack you allocate. For example, if you allocate 512 bytes of stack, you will have 512 changed in both the CCS and the linker command file. Just double checking. Most likely it is already done properly from your size. If this is the case, the issue may be deep inside the LwIP stack.
I don't know what LwIP support has any recommendation in this regard as we really don't have the expertise with the LwIP if the problem is deep inside the stacks which is beyond our knowledge. With that said, I try to do Google search and come across some reported issues and perhaps you can go through them and follow up with the LwIP support forum. I simply search for "LwIP 1.4.1 PCB list corruption" using Google search. I wonder if it is worthwhile for you to migrate to a higher version of the LwIP if the problem is specific to 1.4.1. This task will be on your own though as we have no plan to migrate to another LwIP version.
Please note that today is a US national holiday. Response will be delayed.
