<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]]