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

Daisho USB design failing #271

Open
acomodi opened this issue Nov 17, 2020 · 5 comments
Open

Daisho USB design failing #271

acomodi opened this issue Nov 17, 2020 · 5 comments

Comments

@acomodi
Copy link
Contributor

acomodi commented Nov 17, 2020

With the latest database from conda, the daisho-usb3 design fails in symbiflow with the following error:

prjxray.fasm_assembler.FasmInconsistentBits: FASM line "CMT_TOP_R_UPPER_T_X8Y200.PLL_CLK_FREQ_BB1_NS_ACTIVE" wanted to set bit (156, 74, 1) but was cleared by FASM line "CMT_TOP_R_UPPER_T_X8Y200.CMT_TOP_R_UPPER_T_PLLE2_CLKIN2.CMT_TOP_R_UPPER_T_PLLE2_CLK_IN2_INT"
Makefile:43: recipe for target 'top.bit' failed
acomodi added a commit to antmicro/fpga-tool-perf that referenced this issue Nov 17, 2020
Until chipsalliance#271 is fixed

Signed-off-by: Alessandro Comodi <acomodi@antmicro.com>
@litghost
Copy link
Contributor

This is likely a bug in the PLL pip fuzzer. The MMCM pip fuzzer does a better job of decoupling the bits. @mkurc-ant is this something you can help with?

@mkurc-ant
Copy link
Collaborator

I can take a look at that. Besides that some PLL PIPs are missing in the issue: f4pga/f4pga-arch-defs#1750. So anyways PLL PIP fuzzer is worth revisiting.

@mkurc-ant
Copy link
Collaborator

@acomodi This is weird. These two FASM features do not even refer to the same segbits. Can you point me out to the design?

@acomodi
Copy link
Contributor Author

acomodi commented Nov 24, 2020

@mkurc-ant This is the top level.

You can run that with the following, prior to having set up the toolperf environment:

./fpgaperf.py --toolchain vpr --board nexys-video --project daisho-usb3

@mkurc-ant
Copy link
Collaborator

Ok I've found the issue. These features conflict for segbits_cmt_top_r_upper_t but not for segbits_cmt_top_l_upper_t.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants