Forum Discussion

ost's avatar
ost
Icon for New Contributor rankNew Contributor
3 years ago
Solved

Global hls_singlepump?

I want to avoid any 2x clock interface to my HLS code, and I wonder if there is a way to do this globablly for a component. Regards
Compilation
  • BoonBengT_Altera's avatar
    BoonBengT_Altera
    3 years ago

    Hi @ost,


    Noted with thanks for the explanation and your patients, after some discussion alignment, unfortunately yes you are right. Short answer to global method of hls_singlepump are not possible at the moment for post compilation.

    Please do let us know if there is anything else we can clarify with.


    Regards

    BB


BoonBengT_Altera's avatar
BoonBengT_Altera
Icon for Moderator rankModerator
3 years ago

Hi @ost


Thank you for posting in Intel community forum, hope all is well and apologies for the delayed in response.

Can you provide more insight on what you mean by 2x clock?

Per my understanding there are limitation where HLS component function cannot be used as namespaces.

However perhaps you can try wrapping the component function as global wrapper, which allow member function to call it.

Hope that clarify.


Best Wishes

BB


ost's avatar
ost
Icon for New Contributor rankNew Contributor
3 years ago
@BoonBengT_Altera wrote:

Can you provide more insight on what you mean by 2x clock?

I assumed this is a known thing for HLS users. The compiler will try to maximize memory performance and one of it's tools are "doublepumping", meaning it will use the 2x clock domain and your component instance will have both clk and clk2x as input pins. You can use the keyword "hls_singlepump" on each array that you define to prevent this, but this may lead to other problems since you don't know at processing time if the array is becoming a register or a memory array. I want a global way of preventing this to happen.