clifford changed the topic of #yosys to: Yosys Open SYnthesis Suite: http://www.clifford.at/yosys/ -- Channel Logs: https://irclog.whitequark.org/yosys
m_w_ has quit [Ping timeout: 260 seconds]
srk has quit [Quit: ZNC - http://znc.in]
srk has joined #yosys
cemerick has quit [Ping timeout: 240 seconds]
emeb has quit [Quit: Leaving.]
proteus-guy has joined #yosys
xrexeon has joined #yosys
<promach> ZipCPU: what do you mean by "n8" ?
<awygle> promach: it's an abbreviation of "night" or "good night"
proteus-guy has quit [Remote host closed the connection]
dys has quit [Ping timeout: 240 seconds]
xrexeon has quit [Remote host closed the connection]
digshadow has quit [Ping timeout: 276 seconds]
m_w_ has joined #yosys
AlexDaniel has quit [Ping timeout: 256 seconds]
leviathan has joined #yosys
leviathan has quit [Read error: Connection reset by peer]
leviathan has joined #yosys
digshadow has joined #yosys
pie_ has quit [Read error: Connection reset by peer]
pie__ has joined #yosys
proteus-guy has joined #yosys
proteus-guy has quit [Ping timeout: 264 seconds]
leviathan has quit [Remote host closed the connection]
m_w_ has quit [Ping timeout: 240 seconds]
pie__ has quit [Ping timeout: 240 seconds]
seldridge has quit [Ping timeout: 264 seconds]
mjo-uk has quit [*.net *.split]
Marex has quit [*.net *.split]
_florent_ has quit [*.net *.split]
jophish has quit [*.net *.split]
jophish has joined #yosys
_florent_ has joined #yosys
Marex has joined #yosys
FabM has joined #yosys
FabM is now known as FabM_Cave
bluesceada has quit [Ping timeout: 276 seconds]
nrossi has quit [Ping timeout: 276 seconds]
kerel_ has quit [Ping timeout: 276 seconds]
nrossi has joined #yosys
kerel has joined #yosys
bluesceada has joined #yosys
dys has joined #yosys
dys has quit [Ping timeout: 260 seconds]
mjo-uk has joined #yosys
GuzTech has joined #yosys
cemerick has joined #yosys
proteus-guy has joined #yosys
proteus-guy has quit [Max SendQ exceeded]
proteus-guy has joined #yosys
proteus-guy has quit [Remote host closed the connection]
proteus-guy has joined #yosys
proteus-guy has quit [Ping timeout: 256 seconds]
goosenphil has joined #yosys
goosenphil has quit [Quit: goosenphil]
proteus-guy has joined #yosys
proteus-guy has quit [Ping timeout: 263 seconds]
oldtopman has quit [Ping timeout: 276 seconds]
oldtopman has joined #yosys
m_w_ has joined #yosys
pie__ has joined #yosys
m_w_ has quit [Ping timeout: 268 seconds]
pie__ has quit [Ping timeout: 256 seconds]
eduardo__ has joined #yosys
eduardo_ has quit [Ping timeout: 240 seconds]
pie__ has joined #yosys
leviathan has joined #yosys
leviathan has quit [Read error: Connection reset by peer]
leviathan has joined #yosys
<ZipCPU> promach: Do you want to see how I handled that portion of the test within my own UART receiver?
<ZipCPU> It's a work in progress, but maybe this will give you an idea: https://github.com/ZipCPU/wbuart32/blob/dev/rtl/rxuartlite.v#L531-L562
<tpb> Title: wbuart32/rxuartlite.v at dev · ZipCPU/wbuart32 · GitHub (at github.com)
quigonjinn has quit [Ping timeout: 264 seconds]
quigonjinn has joined #yosys
promach__ has joined #yosys
jophish_ has joined #yosys
<promach__> ZipCPU: are you there ?
<ZipCPU> Yo
proteus-guy has joined #yosys
<ZipCPU> I'm here promach__
AlexDaniel has joined #yosys
quigonjinn has quit [Read error: Connection reset by peer]
quigonjinn has joined #yosys
xrexeon has joined #yosys
<promach__> ZipCPU: what is wrong with "no driver" issue for my generate loop ?
<tpb> Title: test_UART.v · GitHub (at gist.github.com)
<promach__> Warning: Wire test_UART.\Tx_shift_g_index is used but has no driver.
<promach__> ZipCPU
xrexeon has quit [Ping timeout: 276 seconds]
<promach__> Warning: Identifier `\Tx_shift_g_index' is implicitly declared at ../rtl/test_UART.v:149.
pie__ has quit [Ping timeout: 248 seconds]
xrexeon has joined #yosys
<daveshah> promach__: I think you meant to type Tx_shift_**re**g_index
<ZipCPU> promach__: Surely you can see that the identifier is named in error, and can see what it should've been?
<promach__> it is a genvar and it is driven by the for loop
<ZipCPU> Did you see my note where I posted the code I have to accomplish the same check?
<promach__> your note ??
<ZipCPU> "promach: Do you want to see how I handled that portion of the test within my own UART receiver?"
<ZipCPU> "It's a work in progress, but maybe this will give you an idea: https://github.com/ZipCPU/wbuart32/blob/dev/rtl/rxuartlite.v#L531-L562"
<tpb> Title: wbuart32/rxuartlite.v at dev · ZipCPU/wbuart32 · GitHub (at github.com)
<promach__> ZipCPU: that is a lot of magic number
<ZipCPU> Yeah, well ... it works if the clocks are identical, that should count for something.
<ZipCPU> promach__: Let me know if you need an explanation of any of those "magic numbers"
<promach__> daveshah: do you have any idea why I am having that "no driver" issue ?
<promach__> ZipCPU: let me focus on solving that "no driver" issue
<ZipCPU> promach__: The "no driver" issue is simple.
<ZipCPU> It basically means you have an item in your design for which nothing is setting its value.
<ZipCPU> It's a common enough error. As I understand, the reason why you have this issue is because you have a typo in the code you are working with.
<ZipCPU> To find or fix this error, search on the identifier it says has no driver.
<ZipCPU> Then notice that the identifier has nothing assigning a value to it, and you'll see the problem.
<promach__> ZipCPU: that is not a typo issue
<ZipCPU> Even better, place a `default_nettype none at the top of your file. This will help you avoid typo's as well, by not assuming a variable when there shouldn't be one.
<ZipCPU> promach__: Post your code, then. These things are really easy to find.
<promach__> ZipCPU: found it !!
<ZipCPU> Do tell.
<promach__> it is really typo issue
<promach__> I am sorry
<ZipCPU> "<promach__> ZipCPU: that is not a typo issue" <==== :P
<promach__> I am sorry, I am not careful enough
<ZipCPU> lol
<ZipCPU> "Have no fear: programming isn't actually debugging 100% of the time. There's some time set aside for creating new bugs." -- Kelly Vaughn, on twitter
<ZipCPU> Software development process: 0. I can't fix this, 1. Crisis of confidence, 2. Questions career, 3. Questions life, 4. Oh, it was a typo, cool. :P
<ZipCPU> 99 little bugs in the code, 99 little bugs, take one down, patch it around, 127 little bugs in the code ... ;)
<promach__> yeah
kristianpaul has quit [Quit: Lost terminal]
pie_ has joined #yosys
m_w_ has joined #yosys
mattvenn_ has quit [Remote host closed the connection]
jophish_ has quit [Ping timeout: 268 seconds]
seldridge has joined #yosys
xrexeon has quit [Ping timeout: 240 seconds]
_whitelogger has joined #yosys
<awygle> I found that true for a long time, then I started hitting *real* bugs but it took me forever to find them, and now I'm pretty good at sorting "I am misusing this library" and "this is a compiler bug" into different buckets
<awygle> Someday I might even figure out how to fix them in a timely manner... :-P
matt___ has joined #yosys
matt___ is now known as mattvenn
promach__ has quit [Ping timeout: 276 seconds]
leviathan has quit [Ping timeout: 260 seconds]
leviathan has joined #yosys
pie_ has quit [Ping timeout: 276 seconds]
m_w_ has quit [Quit: Leaving]
pie_ has joined #yosys
m_w has joined #yosys
proteus-guy has quit [Ping timeout: 276 seconds]
Nazara has quit [Remote host closed the connection]
GuzTech has quit [Quit: Leaving]
ravenexp has quit [Quit: WeeChat 2.0.1]
ravenexp has joined #yosys
xrexeon has joined #yosys
xrexeon has quit [Remote host closed the connection]
dys has joined #yosys
kristianpaul has quit [Quit: Lost terminal]
FabM_Cave has quit [Quit: ChatZilla 0.9.93 [Firefox 52.7.2/20180316222652]]
digshadow has quit [Ping timeout: 256 seconds]
kristianpaul has joined #yosys
gnufan has quit [Ping timeout: 264 seconds]
gnufan has joined #yosys
seldridge has quit [Ping timeout: 256 seconds]
seldridge has joined #yosys
<pie_> found this single thing on youtube about the reduceron https://www.youtube.com/watch?v=0wT5pobsIaM
<pie_> audio seems kind of horrible
leviathan has quit [Remote host closed the connection]
<pie_> transparencies tho omg xD
<philtor> pie_, what's the context?
<philtor> pie_, for reduceron?
<pie_> just some short discusion on it yesterday i think
<pie_> dont know how it came up
<philtor> lots of graph-reduction going on in the deep learning space
<philtor> I also see in the "up next" videos this talk here from StrangeLoop: https://www.youtube.com/watch?v=GawiQQCn3bk
<philtor> "An Introduction to Combinator Compilers and Graph Reduction Machines"
<pie_> yeah thats also in the search list
<pie_> i mean maybe just read the papers or something i dunno
* pie_ 's efficiency is not very good
<philtor> pie_, are you doing any work in this space? (Graph Reduction)
<pie_> no
bpye has quit [Remote host closed the connection]
dys has quit [Ping timeout: 240 seconds]
digshadow has joined #yosys
cemerick has quit [Ping timeout: 264 seconds]
dys has joined #yosys
digshadow has quit [Ping timeout: 240 seconds]
vinnyp has joined #yosys
vinnyp has left #yosys [#yosys]
seldridge has quit [Quit: WeeChat 1.4]
seldridge has joined #yosys
promach__ has joined #yosys
m_w has quit [Quit: leaving]
digshadow has joined #yosys
digshadow has quit [Ping timeout: 260 seconds]
m_w has joined #yosys
digshadow has joined #yosys
tpb has quit [Remote host closed the connection]
tpb has joined #yosys