lwip is not an adequate replacement for xilnet in all cases. First, lwip requires some form of OS kernel and timers, while xilnet can be used in stand-alone applications. As a result, xilnet is more suitable for smaller projects where code space is a constraint. However, reading the license for the code, it appears that you can keep using it even though it is deprecated, you will just need to turn it into a user library.
I'm working on several projects on ML boards where we simply don't have enough code space left for lwip and xilkernel, so this is the approach we are taking.
Sure, that is a valid approach. However, you might also want to check the RAW mode of lwIP. It does not require a kernel, and it should be small. However you have to rewrite your app using the RAW API.
The benefit is ofcourse that you get the improvements/bug fixes in lwIP. RAW mode is also significantly better performing (close to 100 Mbps TCP throughput w/ xps_ll_temac).
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.