search

Xilinx / embeddedsw

Xilinx Embedded Software (embeddedsw) Development
Other
959 stars 1.07k forks source link

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

Open digitalnumeric opened 1 month ago

digitalnumeric commented 1 month ago

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 commented 1 month ago

Hi, We will check and get back.

VenkateshOdela commented 1 month ago

@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 commented 1 month ago

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. BSP_lwip_debug_off BSP_lwip_debug_on platform_build_output_error.txt

digitalnumeric commented 1 month ago

Update. I found the following fix and applied it to lwip213 lwip220 : fix lwip debug options in cmake https://github.com/Xilinx/embeddedsw/commit/1fee17e71664a082382099049295bfb9abdc0426

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 commented 1 month ago

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