Re: [lwip-users] Assistance Required: Errors in lwiplib.c and Related Files After Upgrading LWIP from 1.4.1 to 2.2.0

[Timothy Martin]

Hi Scott,

Yes, we have updated both the headers and the source files in the includes directory when upgrading LWIP from version 1.4.1 to 2.2.0.

Best,
Timothy

Sent with Proton Mail secure email.

On Wednesday, January 10th, 2024 at 11:24 AM, Scott Miller <scott@argentdata.com> wrote:

I'll start with the obvious question - when you say you updated the headers, do you mean you updated ONLY the headers or did you also update all of the library files as well?

Scott

On 1/9/2024 4:39 PM, Timothy Martin via lwip-users wrote:

Dear LWIP Community,

I am Timothy, currently working on a project involving LWIP. I recently updated the LWIP headers from version 1.4.1 to 2.2.0 and have encountered multiple errors that I'm struggling to resolve. These errors are primarily in lwiplib.c and related files, and I would greatly appreciate any guidance or advice you can provide.

Here are the details of the issues I'm facing:

• Error #137 in lwiplib.c (Path: /NetworkModule/utils):

  • Struct "ip_addr" has no field "addr" at lines 739, 740, 741, 745, 746, 747, 1174, 1198, 1245, 1246, and 1247.

• Error #137 in .ccsproject (External Location: C:\ti5\third_party\lwip-1.4.1\src\core):

  • Struct "udp_pcb" has no field "lwip_recv" at line 404 (File: udp.c).
  • Struct "tcp_pcb" has no field "lwip_recv" at lines 501, 541, 1568, and 1581 (File: tcp.c).
  • Struct "tcp_pcb_listen" has no field "lwip_accept" at lines 956 and 667 (File: tcp_in.c).

• Error #56-D and #29 in .ccsproject (External Location: C:\ti5\third_party\lwip-1.4.1\src\core):

  • Too many arguments in invocation of macro "recv" at line 404 (File: udp.c).
  • Expected an _expression_ at line 1428 (File: tcp.c).
  • Too few arguments in invocation of macro "poll" at line 1428 (File: tcp.c).

I have attempted to troubleshoot these issues by reviewing the documentation and searching for similar problems faced by others, but I haven't found a clear solution yet.

Any help or pointers on how to address these errors would be immensely helpful. I am especially interested in understanding if these are known issues when upgrading from LWIP 1.4.1 to 2.2.0, and if there are any specific changes or considerations I should be aware of.

Thank you in advance for your time and assistance. Your expertise and advice are invaluable to me and others facing similar challenges.

Best,
Timothy

_______________________________________________
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-users