Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Optional reset ports #197

Copy link
Copy link
@mvonbuelow

Description

@mvonbuelow
Issue body actions

Hi all,

I've noticed that most of the HDL modules do not include explicit reset signals. As far as I understand, this follows AMD/Xilinx’s design philosophy to avoid resets where possible and rely on default initialization instead.

However, in our environment this leads to practical issues. Specifically, we have systems where the clock is delivered externally via fiber. If the fiber connection is temporarily removed and reconnected, the clock stops and restarts. After the clock becomes stable again, the design must be properly reset — otherwise, modules may remain in an undefined state.

This is particularly problematic with FIFOs and other stateful components. Without an explicit reset, they may behave unpredictably after clock recovery, and require several cycles to flush or resynchronize before normal operation can resume.

Are there any plans to support optional reset signals, for example, via optional interface ports, to ensure clean reinitialization in such scenarios?

Best,
Maxi

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.