cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
LichengGuo-UCLA
Visitor
Visitor
494 Views
Registered: ‎02-19-2021

[Urgent] Vitis Cannot Run Cosim in Debug Mode with Vivado-HLS-generated XO

Jump to solution

Hello guys,

I'm having difficulty getting the waveform when running Vitis cosim.

 

I'm using Vivado HLS (2019.2) to generate the XO object, then invokes v++ to compile the XO object with hw_emu target. I have added the -g option in v++.

v++ will report this warning: "WARNING: [v++ 60-1455] Debuggable symbols are not generated successfully, clean up ..."

When I run the cosim, it is reported that "non-of the module is compiled in debug mode", so I cannot get the waveform. It just finishes with no waveform file left.

I need to use Vivado HLS to pack the XO because I need to modify the RTL a little bit before feeding them into Vitis.

 

How can I make it right? 

Thanks a lot for your help.

 

Best,

Licheng

0 Kudos
1 Solution

Accepted Solutions
LichengGuo-UCLA
Visitor
Visitor
338 Views
Registered: ‎02-19-2021

 @randyh mentioned that we need to add "config_debug -enable" in the script. That solves the problem. Thanks a lot guys!

View solution in original post

0 Kudos
5 Replies
wenchen
Moderator
Moderator
413 Views
Registered: ‎05-27-2018

Hi @LichengGuo-UCLA 

The 2019.2 Vivado HLS version is not a mature tool for generating xo files. Have you ever tried to update to the Vitis HLS 2020.2 version?

Wen

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.


**~ Got a minute? Answer our Vitis HLS survey here! ~**


-------------------------------------------------------------------------
如果提供的信息能解决您的问题,请标记为“接受为解决方案”。
如果您认为帖子有帮助,请点击“奖励”。谢谢!
-------------------------------------------------------------------------------------------------
0 Kudos
LichengGuo-UCLA
Visitor
Visitor
410 Views
Registered: ‎02-19-2021

Hi @wenchen ,

Thanks for your reply.

I have tried Vitis HLS 2020.2. However, it does not work either

-Licheng

0 Kudos
wenchen
Moderator
Moderator
395 Views
Registered: ‎05-27-2018

Hi @LichengGuo-UCLA 

You said “ invokes v++ to compile the XO object with hw_emu target” which means you run the emulation in the Vitis tool and try to get a co-sim waveform right?

Please run the HLS kernel CO-sim directly in the Vitis HLS and if you cannot get the co-sim passed with waveform, there would be some bugs in your testbench or the kernel code.

Wen

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.


**~ Got a minute? Answer our Vitis HLS survey here! ~**


-------------------------------------------------------------------------
如果提供的信息能解决您的问题,请标记为“接受为解决方案”。
如果您认为帖子有帮助,请点击“奖励”。谢谢!
-------------------------------------------------------------------------------------------------
0 Kudos
LichengGuo-UCLA
Visitor
Visitor
389 Views
Registered: ‎02-19-2021

Hi @wenchen ,

However, In many cases, the host executable provided to me is only for the Vitis hw_emu flow, and I do not have the one for HLS cosim.

This is a clear bug of Vivado HLS/ Vitis HLS. I wonder if you can report it to the HLS team?

Thanks for your help!

-Licheng

 

0 Kudos
LichengGuo-UCLA
Visitor
Visitor
339 Views
Registered: ‎02-19-2021

 @randyh mentioned that we need to add "config_debug -enable" in the script. That solves the problem. Thanks a lot guys!

View solution in original post

0 Kudos