Skip to content

Why does PLL define a COMPENSATION value when that is not used? #2341

New issue
New issue
Open
Open
Why does PLL define a COMPENSATION value when that is not used?#2341
@nelsobe

Description

@nelsobe
nelsobe
opened on Dec 7, 2021 · edited by nelsobe
Contributor

The techmapper for xc7 https://github.com/SymbiFlow/symbiflow-arch-defs/blob/master/xc/xc7/techmap/cells_map.v defines a default value for COMPENSATION in the PLL advanced module even though it is never used. Should that be removed? Or, is the techmapper incomplete?

@mkurc-ant and @acomodi - can you comment?

Activity

mkurc-ant

mkurc-ant commented on Dec 8, 2021

@mkurc-ant
mkurc-ant
on Dec 8, 2021 · edited by unfurl-links
Collaborator

@nelsobe Hmm, The problem with PLL is that it is not clear which features related to COMPENSATION settings should be emitted for each available choice. As with MMCM there is no one-to-one relation between them.

Currently there are those features in the prjxray database: https://github.com/SymbiFlow/prjxray-db/blob/cd41f08a8a4d2a60053750a0fe10623b1e2e35da/artix7/segbits_cmt_top_r_upper_t.db#L56-L59

I think that to get compensation working we would need to do more "minitests" against vendor tools to identify the correct behavior.

GitHub
Project X-Ray Database: XC7 Series. Contribute to SymbiFlow/prjxray-db development by creating an account on GitHub.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @nelsobe@mkurc-ant

        Issue actions
          Why does PLL define a COMPENSATION value when that is not used? · Issue #2341 · f4pga/f4pga-arch-defs