<sf-slack>
<jake.mercer> Am I on the right track with this? Or am I missing something? `make run` is able to complete without any DRC violations or other errors. The blurb associated with the A_INPUT attribute is: ""DIRECT" Selects the input to the A port between parallel input ("DIRECT") or the cascaded input from the previous slice ("CASCADE")." I have assumed "DIRECT" is 0 and "CASCADE" is 1 in generate.py, is there any way to know
<sf-slack>
for sure?
freeemint has quit [Ping timeout: 245 seconds]
_whitelogger has joined #symbiflow
Vonter has quit [Ping timeout: 240 seconds]
Vonter has joined #symbiflow
OmniMancer has joined #symbiflow
_whitelogger has joined #symbiflow
citypw has quit [Ping timeout: 240 seconds]
<sf-slack>
<mkurc> @jake.mercer The truth is that you can't be 100% sure that the parameter you are changing is correlated with a bit in the bitstream. In your case Vivado may not enable the CASCADE frature if you don't connect the other DSP cell in the cascade chain.
Bertl is now known as Bertl_zZ
citypw has joined #symbiflow
freeemint has joined #symbiflow
<sf-slack>
<jake.mercer> Gotcha, so it's mostly a case of try it in various configurations/nets and see what works
<mithro>
jake.mercer: While you waiting for the fuzzers to run, you could start working on a sim model
<sf-slack>
<jake.mercer> Where are they in the tree? Is there an example I can look at?
freeemint has quit [Remote host closed the connection]
freeemint has joined #symbiflow
freeemint has quit [Ping timeout: 245 seconds]
freeemint has joined #symbiflow
emily has quit [Remote host closed the connection]
emily has joined #symbiflow
<daveshah>
jake.mercer: There's a DSP48E1 model in Yosys that I was working on that might be useful