@oe1cxw This might be a stupid q, but in yosys how did you get ahold of SiliconBlue's primitive library (in Verilog form)?
-
-
Replying to @cr1901
You mean techlibs/ice40/cells_sim.v? I just wrote that myself.
1 reply 0 retweets 0 likes -
Replying to @oe1cxw
Yes. And is that the file used to infer primitives when my Verilog code is parsed?
2 replies 0 retweets 0 likes -
(Context: I'm trying to get yosys to infer a pullup on IceStick's GPIO and instantiating an SB_IO seems to be doing nothing :(...)
1 reply 0 retweets 0 likes -
Replying to @cr1901
instantiating the SB_IO (and setting PULLUP=1) should do the trick.
1 reply 0 retweets 0 likes -
Replying to @oe1cxw
Fixed (kinda... now it's always high)... I forgot to add a clock signal, since inputs are registered by default.
1 reply 0 retweets 0 likes -
Replying to @cr1901
You should always at least specify PIN_TYPE when instantiating SB_IO. Don't rely on defaults.
1 reply 0 retweets 1 like -
Replying to @oe1cxw
Are defaults prone to changing (I'm not questioning your judgment. I'm changing it now. Just wondering)? >>
1 reply 0 retweets 0 likes -
In general, I try not to mess with settings I don't need to change :P. I'm known for crashing things when I sneeze wrong.
1 reply 0 retweets 0 likes -
Replying to @cr1901
If you instantiate SB_IO, and don't know what PIN_TYPE does, then you are doing it wrong. 1/
2 replies 0 retweets 0 likes
Refer to the ice40 technology lib manual for details on all the primitive parameters: http://www.latticesemi.com/~/media/LatticeSemi/Documents/TechnicalBriefs/SBTICETechnologyLibrary201504.pdf … 2/2
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.