Closed Aadhithya33 closed 2 months ago
@Aadhithya33 The warning from Yosys does get handled in OpenLane. If you look in the log file, you will find the following:
Warning: Driver-driver conflict for \BR_EN between cell $procdff$2377.Q and constant 1'0 in iiitb_rv32i: Resolved using constant.
Warning: Driver-driver conflict for \REG[6] [31] between cell $procdff$2337.Q and constant 1'0 in iiitb_rv32i: Resolved using constant.
Warning: Driver-driver conflict for \REG[6] [30] between cell $procdff$2337.Q and constant 1'0 in iiitb_rv32i: Resolved using constant.
However, OpenLane consider this behavior dangerous, captures the original multiple conflicting drivers warning from Yosys and throws an error. This behavior is controlled by the variable QUIT_ON_SYNTH_CHECKS
@kareefardi Thank you for the reply. Is it okay to do this "set ::env(QUIT_ON_SYNTH_CHECKS) 0" ? Can i ignore these warnings and proceed to PnR stage?
@Aadhithya33 I think you should try to fix the errors/warnings in your RTL first.
@kareefardi okay thank you
Description
When i synthesized this verilog code in yosys, it was successful.But when i ran it in openlane i got an warning (Multiple conflicting driver). Even i got the same warning when i synthesized using yosys but it was resolved by yosys. But in openlane it did not.
Expected Behavior
Ideally multiple conflicting driver should be resolved but i am getting an warning/error .
Environment report
Reproduction material
iiitb_rv32i.zip
Relevant log output