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

Branch : Quicklogic : Crash while running analysis on the attached design using logic cell macro #1588

Open
rakeshm75 opened this issue Jul 13, 2020 · 4 comments
Assignees

Comments

@rakeshm75
Copy link

Get following error when running the attached design (using logic cell macro):

Writing Implementation Netlist: top_post_synthesis.v
Writing Implementation Netlist: top_post_synthesis.blif
Writing Implementation SDF : top_post_synthesis.sdf
make[3]: *** [quicklogic/pp3/tests/quicklogic_testsuite/test_logic_cell/test_logic_cell-ql-chandalar/ql-s3-ql-eos-s3-virt-ql-eos-s3-wlcsp/analysis.log] Error 134
make[2]: *** [quicklogic/pp3/tests/quicklogic_testsuite/test_logic_cell/CMakeFiles/test_logic_cell-ql-chandalar_analysis.dir/all] Error 2
make[1]: *** [quicklogic/pp3/tests/quicklogic_testsuite/test_logic_cell/CMakeFiles/test_logic_cell-ql-chandalar_analysis.dir/rule] Error 2
make: *** [quicklogic/pp3/tests/quicklogic_testsuite/test_logic_cell/CMakeFiles/test_logic_cell-ql-chandalar_analysis.dir/rule] Error 2

counter_8bit.zip

@rakeshm75
Copy link
Author

Added one more test case

test_logic_cell.zip

@mkurc-ant
Copy link
Collaborator

Looks like a VPR segfautl. Will check that.

@mkurc-ant mkurc-ant self-assigned this Jul 14, 2020
@mkurc-ant
Copy link
Collaborator

I've identified the issue. It appears that i has already been fixed in upstream VPR (as of aa042b61c4). I'll go through the procedure of integration upstream VPR into symbiflow. Once that is done a new conda package with the updated VPR will be uploaded with the issue fixed.

@mkurc-ant
Copy link
Collaborator

@rakeshm75 @tpagarani If you cherry pick the following commits from the upstream VTR into your fork then the issue should be solved: 0f1c496 and 197d65a.

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

2 participants