The reset signal is not detected on FPGA
Describe the bug I've created a task with k4_frac_N4_tileable_fracff_40nm FPGA architecture and run the autocheck testbench on Modelsim. However, the reset signal does not affect the counter which is my benchmark circuit. It does not matter which state is in, the counter on the FPGA never resets.
Which part of OpenFPGA is buggy [X] VPR [X] FPGA-Verilog
To Reproduce Steps to reproduce the behavior:
- Clone OpenFPGA repository and checkout commit id: 2a43843bd7a7e73f2fdfd9563d34cdb3016d4051
- Create
fracff-testtask withcreate-taskcommand.- Copy the
k4_frac_N4_tileable_fracff_40nmarchitecture file and its annotation file to the task folder.- Copy the counter designs in the
micro-benchmarkfolder to the task folder.- Execute OpenFPGA task.
- See error
Expected behavior I want to benchmark a counter circuit on a FPGA architecture with fracturable flip-flops.
Screenshots
Environment (please complete the following information):
- OS:
- [X] Ubuntu 20.04
- Compiler:
- [X] gcc-9
- Version:
- [X] Current master
Additional context I've uploaded the task folder and my final run below: fracff-test.zip
@yunuseryilmaz18 Please check the usage of
- repack pin constraints https://openfpga.readthedocs.io/en/master/manual/openfpga_shell/openfpga_commands/fpga_bitstream_commands/#cmdoption-design_constraints
- pin constraint file https://openfpga.readthedocs.io/en/master/manual/openfpga_shell/openfpga_commands/fpga_verilog_commands/#cmdoption-pin_constraints_file
I know that openfpga provides a file to describe the pin constraints, but I don't know how openfpga calls this file. Or should I use vpr --place_file place_file_name.place for my purpose?
@narutozxp Please look into this example: https://github.com/lnis-uofu/OpenFPGA/tree/master/openfpga_flow/tasks/basic_tests/constrain_pin_location/config
Thanks a lot, but I can't use pcf2place with openfpga in version 1.1.0 (latest release). Does this feature currently only exist in the beta version?
@narutozxp Yes. This is a new feature that is added recently.
Close for now. If you still have question, please reopen and discuss.
