*** tpb has joined #yosys | 00:00 | |
*** emeb has quit IRC | 00:15 | |
*** emeb_mac has quit IRC | 00:15 | |
*** emeb_mac has joined #yosys | 00:18 | |
*** Noname_Matt has joined #yosys | 00:21 | |
*** Noname_Matt has joined #yosys | 00:25 | |
Noname_Matt | test. | 00:26 |
---|---|---|
mwk | toast. | 00:29 |
*** GenTooMan has quit IRC | 00:53 | |
*** GenTooMan has joined #yosys | 00:55 | |
*** matthuszagh has joined #yosys | 02:17 | |
matthuszagh | hello. i'm having some trouble getting yosys to find verilog include files via a tcl script. I must be doing something obviously wrong but I can't pinpoint it. If I write the read_verilog line as 'read_verilog -sv -I/path... top.v' it works fine, but if I place the same string in an environment variable and read it out with $::env(INCLUDES) yosys emits an error saying it can't open the include file. I've checked that tcl gets the | 02:27 |
matthuszagh | variable with puts $::env(INCLUDES) and it matches what I expect | 02:27 |
matthuszagh | happy to post the actual scripts and output if that helps | 02:29 |
*** PyroPeter has quit IRC | 02:47 | |
*** PyroPeter has joined #yosys | 03:01 | |
Noname_Matt | matthuszagh How are you calling yosys with the includes? | 03:03 |
Noname_Matt | I ran into a (sort of) glitch in TCL like this | 03:04 |
Noname_Matt | if you read it in like | 03:04 |
Noname_Matt | set my_var "item1 item2 item3" | 03:04 |
Noname_Matt | then call it like | 03:04 |
Noname_Matt | exec "yosys" $my_var | 03:05 |
Noname_Matt | you may get this problem as the three items are passed as one item with spaces in it | 03:05 |
Noname_Matt | this is not a system() call. it's directly calling the exec() system call | 03:05 |
Noname_Matt | the workaround is to do | 03:05 |
Noname_Matt | eval exec "yosys" $my_var | 03:06 |
Noname_Matt | which adds an extra level of evaluation which breaks apart the list | 03:06 |
Noname_Matt | be careful about attacker controlled variable contents though, as this is adding an extra iteration of evaluation after all | 03:07 |
matthuszagh | Noname_Matt: the way I call it is a bit different. I have a makefile with an export command at the top, then variable definitions then just yosys path/to/script.tcl | 03:08 |
matthuszagh | i'm trying to come up with a minimal example that introduces, but so far it's working there... | 03:08 |
matthuszagh | s/introduces/reproduces/ | 03:08 |
*** gatin00b has joined #yosys | 03:09 | |
Noname_Matt | ah, ok. I'm not familiar with yosys' internal TCL interfaces and interpreter | 03:09 |
matthuszagh | thanks anyway! | 03:09 |
Noname_Matt | though I have plenty of experience with synopsys' :P | 03:10 |
Noname_Matt | need to learn more about yosys and the icestorm flow | 03:10 |
Noname_Matt | I've only done some small proof of concept stuff so far | 03:10 |
matthuszagh | ah was just about to ask if there's a way around the tcl usage (i.e. get a enviro variable from a yosys script) but i guess then you probably wouldn't know | 03:11 |
*** shapr has left #yosys | 03:33 | |
Noname_Matt | can you do something like | 03:40 |
Noname_Matt | yosys --includes $includes | 03:41 |
*** Noname_Matt has quit IRC | 03:41 | |
*** Noname_Matt has joined #yosys | 03:43 | |
*** Guest4992 has joined #yosys | 03:45 | |
Guest4992 | argh. battery picked that exact instant to die | 03:46 |
*** Guest4992 is now known as Noname_MAtt | 03:46 | |
*** Noname_MAtt is now known as Noname_Matt | 03:46 | |
matthuszagh | Noname_Matt: that doesn't appear to work either | 03:46 |
Noname_Matt | It probably wouldn't. I was making up the command line option. | 03:46 |
Noname_Matt | My point was rather can you have the calling makefile derefeence the variable? | 03:47 |
Noname_Matt | dereference* | 03:47 |
matthuszagh | oh yeak ok i see. unfortunately i don't think yosys has an include flag like that | 03:48 |
matthuszagh | just via yosys -p | 03:48 |
matthuszagh | I've filed a bug report, seems like it may be one | 03:50 |
*** matthuszagh has left #yosys | 04:08 | |
*** citypw has joined #yosys | 06:02 | |
*** emeb_mac has quit IRC | 06:35 | |
*** dys has joined #yosys | 07:10 | |
*** dys has quit IRC | 07:54 | |
*** dys has joined #yosys | 08:04 | |
*** pie_ has quit IRC | 09:00 | |
*** rqou has quit IRC | 09:05 | |
*** X-Scale has quit IRC | 10:01 | |
*** X-Scale` has joined #yosys | 10:01 | |
*** X-Scale` is now known as X-Scale | 10:02 | |
*** fsasm has joined #yosys | 10:12 | |
*** pie_ has joined #yosys | 10:12 | |
*** rqou has joined #yosys | 10:37 | |
*** pie_ has quit IRC | 12:39 | |
*** craigo has quit IRC | 13:05 | |
*** vidbina has joined #yosys | 13:48 | |
Noname_Matt | anyone remember offhand what the maximum clock frequency of the RISCV core that can be implemented on the HX8K is? | 14:02 |
daveshah | About 60MHz | 14:04 |
daveshah | for both picorv32 and vexriscv | 14:04 |
daveshah | 70MHz might be doable with optimum config and good luck | 14:04 |
rvense | how many clocks per instruction? | 14:06 |
daveshah | picorv32 is around 3, vex is probably less than that | 14:07 |
tnt | vex is also lower fmax though. | 14:16 |
tnt | (at least on the up5k that's been my experience, for a minimal config) | 14:16 |
Noname_Matt | Isn't the HX series a bit faster? | 14:18 |
daveshah | Yes, but relative fmax would probably be simila | 14:18 |
Noname_Matt | why is that? | 14:19 |
daveshah | Because the up5k is roughly proportionally slower than the hx8k | 14:19 |
Noname_Matt | I don't follow. If the HX series is faster (Wikipedia quotes 7.30 ns versus 9.00–9.36 ns which is around 25% improvement), wouldn't the maximum frequency for the core likewise be faster on one of the HX devices? | 14:22 |
daveshah | Yes | 14:22 |
daveshah | But it probably doesn't change picorv32 being higher fmax than vex | 14:22 |
Noname_Matt | ah | 14:23 |
daveshah | (idk what that wiki number is but the difference is more like 2-3x) | 14:23 |
Noname_Matt | so would 60MHz be representative of the faster chips? | 14:23 |
daveshah | Yes, that was in the context of an hx8k | 14:24 |
Noname_Matt | so maybe 20-30MHz on other devices? | 14:24 |
daveshah | Yeah | 14:25 |
daveshah | tnt probably has more experience here | 14:25 |
tnt | On the UP5k meeting 24 MHz with picorv is not too hard. I also have a design where it's at 30.72 MHz, but that one requires quite a bit of trying seeds to pass timing. | 14:33 |
tnt | It can vary wildly depending on what you put on the memory bus obviously ... | 14:34 |
*** vidbina has quit IRC | 14:35 | |
*** vidbina has joined #yosys | 14:53 | |
*** vidbina has quit IRC | 14:57 | |
*** dys has quit IRC | 16:29 | |
*** citypw has quit IRC | 16:36 | |
*** vidbina has joined #yosys | 16:36 | |
*** vidbina has quit IRC | 17:19 | |
*** vidbina has joined #yosys | 18:01 | |
*** fsasm has quit IRC | 18:06 | |
*** kuldeep has joined #yosys | 18:07 | |
*** vidbina has quit IRC | 20:59 | |
*** craigo has joined #yosys | 21:06 | |
*** stzsch has joined #yosys | 22:37 | |
*** Noname_Matt has quit IRC | 23:13 | |
*** emeb has joined #yosys | 23:27 | |
*** forksand has quit IRC | 23:49 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!