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: 
Highlighted
Visitor loldaa
Visitor
1,895 Views
Registered: ‎12-05-2017

2017.4 Sdaccel Ubuntu16.03 XOCC Options --kernel_frequency problem

Jump to solution

Hi, everyone

 

I want to lower my kernel frequency below 300MHZ, since some time if your kernel run too fast they will give you a integration error like following

 

===>The following messages were generated while Compiling (bitstream) opencl binary: kernel Log file: .... :
ERROR: [vpl-1] design did not meet timing, auto frequency scaling failed because an unscalable system clock did not meet the target frequency. Please try specifying a clock frequency lower than 500 using the '--kernel_frequency' switch for the next compilation
ERROR: [vpl 60-704] Integration error, problem implementing dynamic region, route_design ERROR

ERROR: [vpl 60-806] Fail to finish platform linker
ERROR: [XOCC 60-626] Kernel link failed to complete
ERROR: [XOCC 60-703] Failed to finish linking

 

Then I edit the xocc options by parameter "--kernel_frequency  200", but the hls report did not change anything

 

Is it a bug, or I do something wrong?

 

By the way, I can change the uncertainty by edit xocc option 

"--xp prop:solution.kernel_compiler_margin=<Frequency Percentage>"

This really success.

 

 

 

 

0 Kudos
1 Solution

Accepted Solutions
Moderator
Moderator
1,072 Views
Registered: ‎11-04-2010

Re: 2017.4 Sdaccel Ubuntu16.03 XOCC Options --kernel_frequency problem

Jump to solution

The exact reason is in the accepted solution of the new thread:

https://forums.xilinx.com/t5/SDAccel/sdx2017-4-XOCC-kernel-compiler-cannot-set-kernel-frequency/td-p/894185

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

View solution in original post

0 Kudos
5 Replies
Moderator
Moderator
1,853 Views
Registered: ‎03-27-2012

Re: 2017.4 Sdaccel Ubuntu16.03 XOCC Options --kernel_frequency problem

Jump to solution

Hi,

 

Are you using RTL kernel? If so please try with:
xocc --kernel_frequency "0:200"

-------------------------------------------------------------------------
Don’t forget to reply, kudo, and accept as solution.
-------------------------------------------------------------------------
0 Kudos
Xilinx Employee
Xilinx Employee
1,841 Views
Registered: ‎06-17-2008

Re: 2017.4 Sdaccel Ubuntu16.03 XOCC Options --kernel_frequency problem

Jump to solution

It will not affect the HLS result but it should be able to be reflected in the final Vivado timing result.

0 Kudos
Visitor loldaa
Visitor
1,833 Views
Registered: ‎12-05-2017

Re: 2017.4 Sdaccel Ubuntu16.03 XOCC Options --kernel_frequency problem

Jump to solution

Thanks seans and yunl. 

 

Yes,  I found it in the log file says it change the clock frequency at last time. I miss the message in the console.

 

The command of  "--xp prop:solution.kernel_compiler_margincan" can reflect in the hls report, so I think "kernel_frequency" will do the same thing.

 

Clearly, I misunderstanding this.

 

0 Kudos
Visitor yunzhehi
Visitor
1,114 Views
Registered: ‎07-18-2018

Re: 2017.4 Sdaccel Ubuntu16.03 XOCC Options --kernel_frequency problem

Jump to solution

just confused, does the "--kernel_frequency" not working in XOCC kernel compiler or it worked but not show in the log?

0 Kudos
Moderator
Moderator
1,073 Views
Registered: ‎11-04-2010

Re: 2017.4 Sdaccel Ubuntu16.03 XOCC Options --kernel_frequency problem

Jump to solution

The exact reason is in the accepted solution of the new thread:

https://forums.xilinx.com/t5/SDAccel/sdx2017-4-XOCC-kernel-compiler-cannot-set-kernel-frequency/td-p/894185

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

View solution in original post

0 Kudos