--
Has recibido este mensaje porque estás suscrito al grupo "FPGAwars: explorando el lado libre" de Grupos de Google.
Para cancelar la suscripción a este grupo y dejar de recibir sus mensajes, envía un correo electrónico a fpga-wars-explorando-el...@googlegroups.com.
Para ver este debate, visita https://groups.google.com/d/msgid/fpga-wars-explorando-el-lado-libre/ba580b28-a30a-440b-bf28-be26834c6522n%40googlegroups.com.
Hi Joaquin,
Thanks a lot for testing the tool and for your feedback, I really appreciate it!
About the testbench: you actually don’t need to modify it too much to validate your design. In most cases, you only need to change the stimuli in this section:
That’s where you define the input signals for your design.
For clocked circuits, just make sure you have an input named clk (lowercase) and connect your clock to that signal. Icestudio automatically adds this to the testbench:
Also, designs like a simple LED blink are not the best candidates for simulation. Since the on/off timing is usually very long (many clock cycles), you would need a huge number of simulation steps, which makes the simulation slow and not very practical. For this kind of design, simulation is usually less useful unless you reduce the counter values just for testing.
And about Icestudio overwriting the -tb file when rebuilding: that’s a very good point. I’m actually working on that now, since preventing users from losing their testbench changes is definitely important.
Thanks again for the great feedback!