UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
1,472 Views
Registered: ‎03-03-2017

Displayport Rx example project debug xdbg_printf

Jump to solution

Hi,

   I am working with a DisplayPort Rx example design on KC705 using Vivado/SDK 2017.4 and would like to debug plugging in a custom build Dp source and would like to see the xdbg_printf statements be printed to the terminal.

   I see there is an xdebug.h in the BSP/mblaze/include directory, but how do I properly enable so that the xdbg_printf will print to the UART?

   I tried manually copying the file into my project directory and defining DEBUG at the top and when I compile the project I get the following error:

 

sdk_error.png

 

   Any directions on how to get this working is appreciated.

 

Thanks.

Tim

0 Kudos
1 Solution

Accepted Solutions
Moderator
Moderator
1,700 Views
Registered: ‎11-09-2015

Re: Displayport Rx example project debug xdbg_printf

Jump to solution

Hi @tim_severance,

 

The steps to enable the debug are mentioned in the PG233.

 

Check Software Debug section from p109.

 

Besically you should use the option -DDEBUG in the BSP settings.

 

Regards,

 


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
6 Replies
Moderator
Moderator
1,701 Views
Registered: ‎11-09-2015

Re: Displayport Rx example project debug xdbg_printf

Jump to solution

Hi @tim_severance,

 

The steps to enable the debug are mentioned in the PG233.

 

Check Software Debug section from p109.

 

Besically you should use the option -DDEBUG in the BSP settings.

 

Regards,

 


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
1,418 Views
Registered: ‎03-03-2017

Re: Displayport Rx example project debug xdbg_printf

Jump to solution

Thanks @florentw,

   I wasn't aware of that.

Tim

0 Kudos
Visitor sandyhelton
Visitor
942 Views
Registered: ‎01-15-2018

Re: Displayport Rx example project debug xdbg_printf

Jump to solution

Hi,

I am running into the same issue with 2018.2. I get the same issue with the xdebug.h file when compiling. I did't make any change in the example project, but still get the xdebug.h invalid operands error message. I reviewed PG233 dated 12/2018 and added the -DDEBUG flag to the bsp extra_compiler_flags, but that did not fix the core issue. Any help would be appreciated.

Capture.PNG

0 Kudos
Highlighted
Moderator
Moderator
916 Views
Registered: ‎11-09-2015

Re: Displayport Rx example project debug xdbg_printf

Jump to solution

HI @sandyhelton,

You should not set #define DEBUG 1 directly in the code but only use the option -DDEBUG.

Are you getting this issue inside the Displayport driver?

 


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
Visitor sandyhelton
Visitor
900 Views
Registered: ‎01-15-2018

Re: Displayport Rx example project debug xdbg_printf

Jump to solution

I am using the file provided by Xilinx without modification. The example design targeted to a KC705 does not compile as delivered by Xilinx. I did as you suggested and it does compile now.

0 Kudos
Visitor sandyhelton
Visitor
888 Views
Registered: ‎01-15-2018

Re: Displayport Rx example project debug xdbg_printf

Jump to solution

I decided to try the build on a Windows machine prior to seeing the solution. On the PC, the problem did not occur. I found that the xdebug.h file in the bsp was being compiled prior to the top level xdebug.h file. When that occurs, the top level XDEBUG define is already set, so the top level file is bypassed. 

It would seem that either these two files should be equivalent or that the top level file should be fixed as you describe and the top level file should be read first.

0 Kudos