Vitis Unified platform build fails when top-level lwip_debug=true

[digitalnumeric]

In the platform, trying to turn on lwip debug print statements for sub-systems (e.g., socket, udp, etc.) results in nothing is printed.

If I try to turn on the top-level lwip debug the platform build fails.

Is there a work around to turn on lwip debugging in Vitis Unified?

[anirudha1977]

Hi,
We will check and get back.

[VenkateshOdela]

@digitalnumeric , the sub-system socket or udp level debug messages are shown when top-level lwip_debug is enabled.

could you please help us with build failure log your facing when lwip_debug is enabled?

[digitalnumeric]

Attached are screenshots with the top-level lwip debug set to false and true. With it set to false the build succeeds. Setting it to true the platform build fails. I also attached the text from the Vitis Unified Output Window.


platform_build_output_error.txt

[digitalnumeric]

Update. I found the following fix and applied it to lwip213
lwip220 : fix lwip debug options in cmake
1fee17e

0001-applied-fix-to-allow-selection-of-SocketAPI-with-Fre.patch

However, the platform is still failing to build. One error I see in the logs is that the tool cannot find xil_printf. Vitis logs attached.
2024-10-07_ide.log
2024-10-07_ide_verbose.log
2024-10-07_vitis.log

Is there a workaround for any of the errors in the log files so we can turn on lwip debugging and have the platform successfully build?

BTW: We are still on Vitis Unified 2023.2 because we found 2024.1 much too unstable. We were unable to build the same project (or even simple projects) and after fighting with it for 2 days had to give up. I posted about this on the forums and informed our FAE. We are going to have to wait until 2024.2 comes out before trying again.

[VenkateshOdela]

Thanks for logs. let me go through and try to reproduce the issue and find the workaround. we will update you.

[venodela]

Hi @digitalnumeric

As per the Vitis log, we resolved the build failure issue caused by the NETIF_DEBUG macro in the 2024.2 release.
@anirudha1977 @HariniKatakamX

[digitalnumeric]

Sounds good. Unfortunately due to other issues with 2024.2 we are unable to use it.

[anirudha1977]

Hi,
Sorry to know about it. We will try our best to ensure that 2024.2 is usable.
These issues that you are referring to, are these already mentioned in this thread?

If so, we will go oved them once again and see what we can do.

[digitalnumeric]

I just added the issues this morning. Please see these:
Vitis 2024.2 is missing CMake definition for __FILENAME__ used in xil_assert.h in some cases
#326
Vitis 2024.2: CMake Policy CMP0010 is not set: Bad variable reference syntax is an error.
#327
Vitis 2024.2: Fails to complete build, hangs
#328