berkay_ has quit [Remote host closed the connection]
bjorkintosh has joined #yosys
famubu[m] has quit [Quit: Idle timeout reached: 172800s]
whitequark[cis]1 has quit [Quit: Bridge terminating on SIGTERM]
_catircservices has quit [Quit: Bridge terminating on SIGTERM]
lofty[m] has quit [Quit: Bridge terminating on SIGTERM]
Semisol[m] has quit [Quit: Bridge terminating on SIGTERM]
_catircservices has joined #yosys
peeps[zen] has joined #yosys
peepsalot has quit [Ping timeout: 248 seconds]
FabM has joined #yosys
FabM has joined #yosys
krispaul has joined #yosys
kristianpaul has quit [Ping timeout: 246 seconds]
_whitelogger has joined #yosys
bjorkintosh has quit [Remote host closed the connection]
bjorkintosh has joined #yosys
bjorkintosh has quit [Changing host]
bjorkintosh has joined #yosys
bjorkintosh has quit [Remote host closed the connection]
bjorkintosh has joined #yosys
bjorkintosh has quit [Changing host]
bjorkintosh has joined #yosys
AdamHorden has quit [Ping timeout: 252 seconds]
bjorkintosh has quit [Remote host closed the connection]
bjorkintosh has joined #yosys
bjorkintosh has joined #yosys
AdamHorden has joined #yosys
mra has joined #yosys
<mra>
hey! just had a bit of a question about best practices involving the ghdl plugin. if i need to be able to instantiate chip-specific primitives that yosys won't infer (plls, for instance), would the "correct" way to do that be to fully elaborate my project with ghdl, then use write_verilog to save everything to a verilog file and then use that for
<mra>
synthesis? it seems a bit messy, but i can't figure out any other way to refer to primitives in vdhl...
lofty[m] has joined #yosys
<lofty[m]>
ghdl has already elaborated the design to yosys; you can use it directly
<mra>
what the hell... could have sworn that i tried that. well, productive waste of a few hours i guess
<mra>
thanks!
<lofty[m]>
I guess it wouldn't work if the GHDL elaboration doesn't match the yosys cell definition, though
<mra>
yeah, but that should be fine as long as i'm careful to correctly match things up. i could also write vhdl wrappers for the primitives that i need for a bit more flexibility, i suppose
<lofty[m]>
what's the chip you're targeting?
<mra>
the ice40. got an icebreaker fpga board recently
<lofty[m]>
that shouldn't be too painful then.
<mra>
unfortunately a new enough version that they don't seem to have posted the pinout or schematics, so there's a bit of trial and error...
<mra>
but other than that it's not so bad
mra has quit [Quit: Client closed]
mra has joined #yosys
<mra>
the only other struggle i've had build-wise is that if i split entities into their own files, which seems like the norm, ghdl seems to require that the files be analysed in dependency order, which makes automating the build a bit annoying, unless i modify my makefile every time i add a new entity
Guest46 has joined #yosys
Guest46 has quit [Client Quit]
mra54 has joined #yosys
mra is now known as Guest5811
mra54 is now known as mra
Guest5811 has quit [Ping timeout: 240 seconds]
bjorkintosh has quit [Quit: "Every day, computers are making people easier to use." David Temkin]
bjorkintosh has joined #yosys
bjorkintosh has quit [Changing host]
bjorkintosh has joined #yosys
mra has quit [Ping timeout: 240 seconds]
FabM has quit [Ping timeout: 248 seconds]
bjorkintosh has quit [Remote host closed the connection]