<Myrl-saki>
This one has a smaller diagnostic $flatten\furv.$0$memwr$\r$furv.v:125$106_EN[31:0]$135
<Myrl-saki>
I'm not so sure what a "feedback arc" means.
<Myrl-saki>
FWIW, doing splitnets fixes this.
<Myrl-saki>
Ah, I can just splitnets on the modules that have this problem, and thne flatten.
<Myrl-saki>
Ah, seems like `share -force` gets it.
srk has quit [Remote host closed the connection]
srk has joined #yosys
<Myrl-saki>
Well, turns out it disappears because it removes the store lol
citypw has joined #yosys
FabM has joined #yosys
FabM has joined #yosys
GenTooMan has quit [Ping timeout: 260 seconds]
notgull has quit [Ping timeout: 255 seconds]
notgull has joined #yosys
GenTooMan has joined #yosys
schaeg has joined #yosys
schaeg has quit [Ping timeout: 264 seconds]
sauce has joined #yosys
arogora has joined #yosys
killjoy has quit [Ping timeout: 255 seconds]
arogora is now known as killjoy
killjoy has quit [Changing host]
killjoy has joined #yosys
bjorkintosh has quit [Quit: Leaving]
bjorkintosh has joined #yosys
bjorkintosh has quit [Changing host]
bjorkintosh has joined #yosys
gordonDrogon has quit [Ping timeout: 248 seconds]
gordonDrogon has joined #yosys
GenTooMan has quit [Ping timeout: 272 seconds]
gordonDrogon has quit [Ping timeout: 255 seconds]
gordonDrogon has joined #yosys
GenTooMan has joined #yosys
GenTooMan has quit [Ping timeout: 260 seconds]
citypw has quit [Ping timeout: 252 seconds]
<Myrl-saki>
jix: Hi, sorry. How exactly do I load the module afetr blackboxing it?
<Myrl-saki>
Is this on nextpnr or on yosys?
<Myrl-saki>
ERROR: Unable to place cell 'rom', no BELs remaining to implement cell type 'rom'
<jix>
Myrl-saki: you load the module into a separate design (see `help design`) and then run techmap with that design as cell library (`help techmap`)
<Myrl-saki>
Thanks. :)
<jix>
I can elaborate later, but I'm about to leave
<Myrl-saki>
Good enough for me. ^^ I just needed a hint.
<jix>
Might also be able to just read_verilog the rom.v after synth but I haven't tried that and that gives you less control over what passes to run on that module independent from the rest of the design
<Myrl-saki>
Ah! I found a
<Myrl-saki>
Yes!
<Myrl-saki>
That's exactly what I did. :D
<Myrl-saki>
Well kind of. I did it directly before synth, but after all my optimization passes.
<Myrl-saki>
Thanks, seems like I got it.
<Myrl-saki>
Wild, removing the ROM makes yosys infer block RAM (it says SPX9?). Computers never cease to amaze me. That aside, I think I got it working! :)
<lofty>
Myrl-saki: that's a rather peculiar synthesis script
<Myrl-saki>
I decided to just flatten and opt, and that produces way smaller than whatever I wrote. : X
<Myrl-saki>
3700 vs 4300
<Myrl-saki>
Though, 4300 vs 4700 if I opt without flatten.
<Myrl-saki>
With that said, there's probably :tm: bugs in my code, because my core is not responding to UART lol
<Myrl-saki>
So that could account for the missing LUTs.
<Myrl-saki>
But yeah, so I had an idea of how I wanted the compilation to look in mind, that's why I am compiling each module with their own specific settings.
<jix>
Myrl-saki: Without `-force` it shouldn't break things.
<Myrl-saki>
How about -aggressive?
<jix>
Myrl-saki: If it does what it says in the help message that shouldn't be able to break things, but it's been a while since I looked at share's source code and I haven't done much with it