Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add techmap for BUFGMUX #1419

Merged
merged 2 commits into from
Dec 14, 2020
Merged

Add techmap for BUFGMUX #1419

merged 2 commits into from
Dec 14, 2020

Conversation

rw1nkler
Copy link
Contributor

This commit adds techmap for BUFGMUX.
The implementation is based on the [Xilinx documentation]

@probot-autolabeler probot-autolabeler bot added the lang-verilog Issue uses (or requires) Verilog language. label Apr 14, 2020
Copy link
Contributor

@litghost litghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a test for this techmap:

  • Add a test circuit
  • Test it in hardware
  • Have a add_vivado_target and make sure the diff test is green

@rw1nkler rw1nkler mentioned this pull request May 5, 2020
@rw1nkler rw1nkler force-pushed the bufgmux_techmap branch 2 times, most recently from 057bc5d to f7f43e8 Compare May 12, 2020 14:42
@rw1nkler rw1nkler changed the title Add techmap for BUFGMUX [DNM] Add techmap for BUFGMUX May 12, 2020
@rw1nkler
Copy link
Contributor Author

rw1nkler commented May 12, 2020

For the Nexys Video board test produces the same error as for OpenTitan design #1442 (comment). I will investigate why this error occurs.

@rw1nkler rw1nkler mentioned this pull request Jun 16, 2020
@rw1nkler rw1nkler changed the title [DNM] Add techmap for BUFGMUX Add techmap for BUFGMUX Jul 28, 2020
Copy link
Contributor

@litghost litghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, merge if green and if tested in hardware

Copy link
Contributor

@litghost litghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CI is red

@rw1nkler
Copy link
Contributor Author

Yeah, I thought that we have already merged new db - #1619
Can we merge that? @litghost

@litghost
Copy link
Contributor

Can you simply incorporate the submodule bump in this PR, and that will test that the new prjxray-db solves your issue?

@rw1nkler
Copy link
Contributor Author

rw1nkler commented Nov 10, 2020

@litghost I believe that those CI failures are not related to this PR.

  • Xilinx Series 7 - Vendor Tools Tests fails due to no space left on the device error
Traceback (most recent call last):
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7-vendor/xc/common/utils/prjxray_import_tile_capacity.py", line 90, in <module>
    main()
  File "/tmpfs/src/github/symbiflow-arch-defs-presubmit-xc7-vendor/xc/common/utils/prjxray_import_tile_capacity.py", line 86, in main
    f.write(tile_str)
OSError: [Errno 28] No space left on device
  • VtR + SymbiFlow Architecture Definitions fails on no possible path error in the buttons_basys3_full test:
Cannot route from BLK-TL-RIOPAD_M[0].IOI_ILOGIC0_O[0] (RR node: 1484735 type: SOURCE location: (114,109) class: 53 capacity: 1 fan-in: 0 fan-out: 1) to BLK-TL-RIOPAD_S[0].IOI_OLOGIC1_D1[0] (RR node: 1392164 type: SINK location: (114,67) class: 26 capacity: 1 fan-in: 1 fan-out: 0) -- no possible path
Failed to route connection from 'sw[15]' to '$iopadmap$top.led_15.t_inv' for net '$abc$1667$iopadmap$led[15]' (#16)

Could this be related to #1711?

Signed-off-by: Robert Winkler <rwinkler@antmicro.com>
Signed-off-by: Robert Winkler <rwinkler@antmicro.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lang-verilog Issue uses (or requires) Verilog language. third-party
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants