cr1901 has quit [Read error: Connection reset by peer]
dormito has quit [Ping timeout: 256 seconds]
<lambda>
holy mother of issue notifications
dormito has joined #yosys
<mwk>
yup
<mwk>
we figured we may try to enable the github discussions thing since so many issues are actually questions
<mwk>
this involved a little issue tracker sweep
Guest4464 has joined #yosys
Guest4464 has quit [Client Quit]
gsmecher has joined #yosys
emeb_mac has joined #yosys
emeb has joined #yosys
cr1901 has joined #yosys
oldtopman has quit [Ping timeout: 240 seconds]
emeb_mac has quit [Quit: Leaving.]
FabM has quit [Quit: Leaving]
GenTooMan has quit [Ping timeout: 245 seconds]
GenTooMan has joined #yosys
scientes has joined #yosys
<scientes>
Are there any cycle-accurate FPGA simulators?
<scientes>
I want something like single-stepping gdb
<scientes>
just to get a better feel of these things
<scientes>
(obviously something small like a ice40)
<agg>
often you'd simulate your logic using a logic simulator, something like verilator, icarus verilog, modelsim, cxxrtl (built in to yosys), and often then use some tool to view the simulation results (like gtkwave)
<agg>
depending on what you need, you can simulate just your logic, or the result of synthesising it into FPGA elements, and include simulation models of the FPGA hardware like block memories, DSP units, etc
<scientes>
<agg> depending on what you need, you can simulate just your logic, or the result of synthesising it into FPGA elements, and include simulation models of the FPGA hardware like block memories, DSP units, etc
<scientes>
yeah, the ice40 is small enough you could simulate the whole thing
<agg>
if you're asking about simulating a physical specific ice40 chip and bitstream, not sure if such a thing really exists beyond wrapping the simulators I mentioned
<agg>
what are you trying to get a feel of exactly?
<scientes>
low-level synthesis
<agg>
you can dump the synthesis as verilog and simulate it with models of each primitive, the same way you'd simulate logic
<scientes>
like using codeexplorer
<agg>
and can include the timing information if you need to model that too, with some simulators, assuming you have that information
<agg>
but it seems like an unusual thing to go about doing, i feel like the objective is usually to simulate your design, not your fpga
emeb_mac has joined #yosys
<agg>
(there are other physical simulation tools for asics I guess to cover things like antenna rules and power distro, I don't really know anything about them)
<sorear>
a fpga is an analog device, "cycle accurate" will always involve compromises
<scientes>
sorear, ahhh
<scientes>
its clocked so it appears a digital device only