Wednesday, 2019-07-24

*** tpb has joined #yosys00:00
*** X-Scale has joined #yosys00:25
*** kmehall has quit IRC00:45
*** kmehall has joined #yosys00:46
*** MoeIcenowy has quit IRC00:47
*** MoeIcenowy has joined #yosys00:52
*** PyroPeter has quit IRC02:26
*** PyroPeter has joined #yosys02:39
*** _whitelogger has quit IRC02:48
*** _whitelogger has joined #yosys02:50
*** chipb_ is now known as chipb03:26
*** AlexDaniel has joined #yosys03:44
*** citypw has joined #yosys03:55
*** rohitksingh_work has joined #yosys04:46
*** emeb has quit IRC04:50
*** dys has joined #yosys04:58
*** Jybz has joined #yosys05:42
*** proteusguy has joined #yosys05:54
*** futarisIRCcloud has quit IRC06:29
*** m4ssi has joined #yosys07:19
*** emeb_mac has quit IRC07:24
*** citypw has quit IRC08:02
*** citypw has joined #yosys08:19
*** AlexDaniel has quit IRC08:38
*** futarisIRCcloud has joined #yosys08:55
*** Jybz has quit IRC10:12
*** jryans has quit IRC10:17
*** nrossi has quit IRC10:17
*** Wolf480pl has quit IRC10:20
*** Wolf480pl has joined #yosys10:22
*** somlo has quit IRC10:36
*** pepijndevos_ has quit IRC10:55
*** jryans has joined #yosys11:00
*** futarisIRCcloud has quit IRC11:34
*** pepijndevos has joined #yosys11:37
*** nrossi has joined #yosys11:46
*** cr1901_modern has quit IRC11:52
*** proteusguy has quit IRC12:06
*** rrika has quit IRC12:35
*** rrika has joined #yosys12:37
pepijndevosHow does the extract pass work with parameters?12:51
pepijndevos-ignore_parameters Do not use parameters when matching cells.12:53
pepijndevosSo what does it do to "use parameters"?12:53
pepijndevosIt seems extract is also extremely picky about using for example 1 or 8'b113:01
*** rohitksingh_work has quit IRC14:38
*** proteusguy has joined #yosys14:55
*** maikmerten has joined #yosys15:08
*** rohitksingh has joined #yosys15:09
pepijndevosDoes a techmap "inherit" the parameters of the thing it replaces?15:16
*** cr1901_modern has joined #yosys15:39
*** emeb has joined #yosys15:42
pepijndevosAre there any magic rules for when a techmap matches or not? Mine does not, for some reason.15:57
*** rohitksingh has quit IRC15:58
pepijndevosERROR: (ASSERT MODE) No matching template cell for type \$counter16 found.16:06
*** rohitksingh has joined #yosys16:11
ZirconiumX[16:07:31]  pepijndevos: Does a techmap "inherit" the parameters of the thing it replaces?16:15
ZirconiumXIf you use a _TECHMAP_REPLACE_ I think so16:16
ZirconiumX[16:48:29]  pepijndevos: Are there any magic rules for when a techmap matches or not? Mine does not, for some reason.16:16
ZirconiumXEither the module is named the same as the cell you're trying to replace, or you have (* techmap_replace = "target_cell" *) above it, and _TECHMAP_FAIL_ is zero16:17
ZirconiumXThat's when it matches16:17
pepijndevosZirconiumX, it's the dollar signs... If I'm trying to act cool and put dollar signs in my counter like a real techmap it fails16:22
pepijndevosIf I just extract and techmap without the dollars it breaks. I think I'm not escaping stuff enough/too much16:23
ZirconiumXThe documentation says techmap -assert errors out if a cell name doesn't end with an underscore16:24
ZirconiumXIf you called your cell $counter16, that'll error because it does not end with an underscore16:24
pepijndevoshttps://github.com/YosysHQ/yosys/blob/master/passes/techmap/techmap.cc#L413 i think it means it'll ignore anything with an underscore if I read the code correctly16:25
tpbTitle: yosys/techmap.cc at master · YosysHQ/yosys · GitHub (at github.com)16:25
ZirconiumXCorrect16:25
ZirconiumXConversely since your cell does not end in an underscore, it's an error16:25
pepijndevosYea, but if I just put an underscore it'll not error and still not replace, I think it's purely that it never asserts on underscored things.16:27
pepijndevosSo if I call my extracted cell counter16 and the techmap on counter16 all is good, but if I call my extraction $counter16 or \$counter16 or whatever, nothing works.16:28
pepijndevosOr even $_COUNTER16_ or anything else that I've tried.16:29
pepijndevosSo I'm not understanding anything about the naming convention and escaping. Like, I've seen \$thing and \\$thing and $thing in various places16:29
pepijndevosI guess I don't really care about the dollar thing, except counter8 seems so common it might come up in normal code, so I thought I'd stick with what seems to be a convention for dollar signs for cells.16:30
pepijndevosShould I just call it 74xx_counter and be done with it?16:31
*** m4ssi has quit IRC16:34
*** citypw has quit IRC16:41
pepijndevosCool, techmap kinda works, simulation super broken.16:52
*** Thorn has quit IRC17:21
pepijndevosit's working! Kinda??17:28
*** proteusguy has quit IRC17:32
ZirconiumXpepijndevos: so when are you shipping a PicoSoC to me?17:32
ZirconiumX:^)17:32
*** AlexDaniel has joined #yosys17:35
*** Jybz has joined #yosys17:42
pepijndevosZirconiumX, hopefully near the end of the holiday :^)17:50
ZirconiumXI think the multiplier would be painful17:50
pepijndevosThe pwmled is now 7 chips17:50
ZirconiumXBecause of counter recognition?17:50
pepijndevosYes17:51
pepijndevosBut it's extremely picky, so you pretty much have to want to use it.17:51
pepijndevosOriginally I wanted to use an up/down counter, but it seems 74161 is pretty much the only thing that's still on sale.17:51
*** rohitksingh has quit IRC17:52
ZirconiumXI don't think you can meaningfully reduce that benchmark any further17:52
pepijndevosWith an up/down counter you could make a sweeeet stack pointer, but at least maybe this is somewhat useful as an instruction pointer.17:52
pepijndevosThere is a sexy sexy 8-bit up/down counter IC, but I don't think it's sold anywhere.17:53
ZirconiumXWhich model?17:53
pepijndevos74x86717:54
ZirconiumXpepijndevos: have you seen the 74x4040?17:59
pepijndevoseh, yea... can't remember the details18:00
pepijndevos12 bits is a bit... odd, no preset, no up/down. So it could be a lot more efficient in some cases, and less useful in others.18:02
pepijndevosRight now I have to specifically extract counter8, counter16 etc. and counter12 seems... not very common.18:03
ZirconiumXMmm18:03
pepijndevosSo for example, if I want to use it as an instruction counter, I need preset for jumps18:05
*** rohitksingh has joined #yosys18:05
pepijndevosAlthough I'm not even convinced what I'm doing now will work for that...18:06
pepijndevosWell, lemme push and you can have a look at it.18:06
GenTooManthe 74hc191 still is produced?18:08
ZirconiumXTrue, and Farnell sell it18:11
ZirconiumXGenTooMan: though we prefer DIP over SOIC for this18:11
GenTooManZirconiumX Nexperia and TI still make the DIP version as far as I know.18:12
sorearkinda surprised you’re not just using quad nands etc18:12
ZirconiumXTI are the one who sell DIPs for Farnell, and it's on back-order18:12
ZirconiumXsorear: We're crazy not stupid18:12
GenTooManat least you are not making it with transistors.18:15
pepijndevos74x191 is actually a nice one maybe? Not really in AC or DIP but... it counts down.18:19
GenTooManthe reason I bothered pointing it out.18:19
*** Thorn has joined #yosys18:24
pepijndevoschange.org petition: TI makes the whole 74xx series18:30
pepijndevossorear, part of me wants to do NOR and recreate the Apollo Guidance Computer18:31
daveshahWhy need a change.org petition when you have MPWs?18:31
pepijndevosdaveshah, what's MPW?18:32
daveshahMulti project wafer18:32
daveshahRelatively cheap way of making custom silicon18:32
pepijndevosAre you suggesting I make an ASIC instead (boring), or produce my own 74xx chips (omg)?18:33
pepijndevosAny idea what it costs to do that kind of stuff?18:33
daveshahLatter18:33
daveshahProbably a few thousand euros minimum18:34
pepijndevosOkay, scrap the change.org, on to kickstarter hehe18:34
GenTooManthen your biggest issue would become buffering and someone to package the chips. a single 8 inch wafer can get you quite a few parts I suspect.18:35
daveshahEuropractice 700nm, probably fine for any 7400, 300€/mm2, 5mm2 min18:36
daveshahFor 30 samples, excluding packaging18:36
ZirconiumXThat's a bit pricey, but would be funny18:37
ZirconiumXOn the other hand, why not just fabricate a PicoSoC directly?18:37
pepijndevosThat's what these Raven people did, no?18:38
pepijndevosOr why not both?18:38
daveshahThat's already been done18:38
daveshahIndeed18:38
ZirconiumXpepijndevos: I'm going to disappoint you greatly18:39
ZirconiumX"In my experience writing counter + 1 and counter + 1'b1 already causes a mismatch"18:39
ZirconiumXBecause 1'b1 is 1-bit, and 1 is 32-bit18:39
pepijndevosI know, but yosys optimizes the useless bits away18:40
ZirconiumXSure, but they're semantically different and the compiler obviously has to keep semantics18:40
pepijndevosI guess...18:41
daveshahopt and wreduce should deal with the difference though18:41
pepijndevosIt just makes the counter extraction not very flexible.18:41
ZirconiumXI'm reasonably sure Yosys turns, say, 4'b1 (i.e. 4'b0001) to 4'bxxx118:41
ZirconiumXBut don't quote me on that18:42
daveshahUnlikely18:42
pepijndevosdaveshah, if I put my extract pass *after* wreduce it doesn't match.18:42
daveshahWhat does the netlist look like after wreduce (`dump` and `show` are helpful)?18:43
daveshahYou might want to use a wreduce'd counter (e.g. saved as il) as the needle in this case18:43
pepijndevosThat might be a good one...18:44
daveshahAfter wreduce and clean, this produces three identical adders (A_WIDTH 4, B_WIDTH 1, Y_WIDTH 4, B connected to 1'b1)18:46
daveshahhttps://www.irccloud.com/pastebin/sKl9bVGj/18:46
tpbTitle: Snippet | IRCCloud (at www.irccloud.com)18:46
pepijndevosdoes opt do clean or are these different things?18:49
daveshahopt does clean too (I didn't use opt for this test as it would actually merge all three adders)18:50
pepijndevosyay that works18:53
pepijndevosNow I wonder if it gets used in *any* of the other benchmarks...18:53
pepijndevosThe answer is no18:54
*** qu1j0t3 has joined #yosys19:30
*** rohitksingh has quit IRC19:50
*** maikmerten has quit IRC20:22
*** matt` has joined #yosys21:30
*** Jybz has quit IRC21:32
matt`hello! i'm having some trouble understanding a yosys error message: "found error in internal cell" where it's complaining about cell $_DFF_PP1. I'm experiencing this when running `synth_xilinx`; `read_verilog` works fine (although I do get a warning about tri-state logic from the same file triggering the error message). Is there a possibility this error means I'm using a tristate representation not supported by yosys? What does that21:42
matt`error mean generally? That yosys isn't able to map the RTL to the available Xilinx cells?21:42
matt`i'm running the current git master version btw21:43
*** qu1j0t3 has left #yosys21:44
daveshahmatt`: I don't think this would be related to a  tristate issue21:47
daveshahA "found error in internal cell" is a Yosys bug21:47
daveshahIf your design isn't confidential, creating a Yosys issue would be helpful21:48
matt`daveshah: i'll try to get this down to a minimal example and raise the issue. Thanks for the help! By the way, what does it mean that tri-state has limited support? is there somewhere in the documentation that says what is and isn't supported in that regard?21:49
daveshahIf it helps pinpoint the issue, a `$_DFF_PP1_` is the Yosys internal type for a single-bit D flipflop with an asynchronous set and rising edge clock21:50
daveshahIn practice I don't think it's so much that only a subset of tristate functionality is supported, as that tristate has a lot of different possibilities and not everything has been tested21:51
daveshahThis is particularly the case for the Xilinx flow which isn't so well used for designs with this kind of stuff21:52
matt`gotcha. thanks again21:54
*** dys has quit IRC23:53

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!