<Seraxis>
Though it only registers to your MAC address and hostname as far as I can tell, so maybe there's ways around that
<Seraxis>
Makes me wonder if you could just keep buying boards and redeeming the certificates
Seraxis has quit [Quit: おやすみ]
Seraxis has joined #yosys
rohitksingh has joined #yosys
m_w has joined #yosys
bitmapper has quit [Ping timeout: 272 seconds]
cr1901_modern has left #yosys [#yosys]
cr1901_modern has joined #yosys
rohitksingh has quit [Ping timeout: 245 seconds]
_whitelogger has joined #yosys
adjtm has quit [Remote host closed the connection]
adjtm has joined #yosys
Jybz has joined #yosys
<lukego>
Just took the plunge and ordered 4 x XCKU15P from that seller for $250 each. I'll probably kill one during rework, develop with another, have a couple for loaning out on prototypes to try and get some commercial action. Have to sort the Vivado situation separately...
<lukego>
seraxis: Maybe that Vivado is also locked to only do synthesis for that device?
<lukego>
i.e. that model of device, i.e. wouldn't work for my shiny new second hand Kintex+
unkraut has joined #yosys
<daveshah>
Yes the vouchers are device locked usually
* lukego
looks into downloading and backing up a copy of that AMI...
<lukego>
oh looks like it's not that kind of arrangement. this isn't the F1 toolchain but an AMI to rent from Xilinx. Good option to know about!
<lukego>
daveshah: do you have a full Vivado license for your hacking somehow or how do you do it?
<daveshah>
I've never needed one as I don't have any devices that do
<daveshah>
The largest device I have is a xczu7ev
<lukego>
do you want one of these Kintex cards? happy to share if it would be useful for your hacking
X-Scale` has joined #yosys
<lukego>
(I decided that I'll spend 2020 learning to do hardware/gateware hacking but first step now in winter is to do some paid work to make a budget for that. Hopefully the equipment I buy will be worth the lost development time. Reckon so.)
X-Scale has quit [Ping timeout: 272 seconds]
X-Scale` is now known as X-Scale
dys has quit [Ping timeout: 260 seconds]
dys has joined #yosys
Jybz has quit [Quit: Konversation terminated!]
<daveshah>
No, I wouldn't realistically have the time to get a card like that up and running
<daveshah>
There's still plenty of work even getting Yosys and nextpnr to work well for the top end of the zu7ev
vidbina has joined #yosys
dh73 has joined #yosys
dh73 has quit [Read error: Connection reset by peer]
<lukego>
understood. yeah, this seems more like a chip for doing mainstream commercial work with, using the usual boring proprietary tools etc. that sounds like a potentially complementary line of work to me though
Jybz has joined #yosys
m4ssi has joined #yosys
fsasm has joined #yosys
vidbina has quit [Ping timeout: 265 seconds]
tux3_ has joined #yosys
tux3 has quit [Ping timeout: 246 seconds]
<seraxis>
davidshah: Ah! Thought there had to be some catch. Upping the thanks for that link, I didn't know that existed.
<mithro>
Anyone seen this error when compiling ABC as part of Yosys?
<mithro>
/tmp/really-long-path/conda/conda-bld/yosys_1580379800823/_build_env/bin/../lib/gcc/x86_64-conda_cos6-linux-gnu/7.3.0/../../../../x86_64-conda_cos6-linux-gnu/bin/ld: src/base/main/mainInit.o: in function
<mithro>
/usr/local/src/conda/yosys-0.9_3245_g1679682f/abc/src/base/main/mainInit.c:119: undefined reference to `Glucose_Init(Abc_Frame_t_*)'
pepijndevos[m] has quit [Quit: User has been idle for 30+ days.]
seraxis has quit [Quit: おやすみ]
seraxis has joined #yosys
seraxis has quit [Quit: おやすみ]
fsasm has quit [Ping timeout: 265 seconds]
fsasm has joined #yosys
heijligen has joined #yosys
seraxis has joined #yosys
vidbina has joined #yosys
vidbina has quit [Ping timeout: 248 seconds]
develonepi3 has joined #yosys
grummel has quit [Quit: WeeChat 1.9.1]
X-Scale` has joined #yosys
X-Scale has quit [Ping timeout: 268 seconds]
X-Scale` is now known as X-Scale
rohitksingh has joined #yosys
seraxis has quit [Quit: おやすみ]
seraxis has joined #yosys
seraxis has quit [Client Quit]
seraxis has joined #yosys
seraxis has quit [Remote host closed the connection]
seraxis has joined #yosys
seraxis has quit [Client Quit]
seraxis has joined #yosys
seraxis has joined #yosys
seraxis has quit [Client Quit]
seraxis has joined #yosys
seraxis has quit [Client Quit]
seraxis has joined #yosys
seraxis has quit [Quit: おやすみ]
seraxis has joined #yosys
seraxis has quit [Quit: おやすみ]
seraxis has joined #yosys
fsasm has quit [Ping timeout: 268 seconds]
s_frit_ has joined #yosys
s_frit has quit [Ping timeout: 265 seconds]
rohitksingh has quit [Ping timeout: 245 seconds]
vidbina has joined #yosys
vidbina has quit [Ping timeout: 265 seconds]
vidbina has joined #yosys
s_frit has joined #yosys
s_frit_ has quit [Ping timeout: 260 seconds]
citypw has quit [Ping timeout: 268 seconds]
dys has quit [Ping timeout: 248 seconds]
rohitksingh has joined #yosys
rohitksingh has quit [Ping timeout: 272 seconds]
rohitksingh has joined #yosys
<somlo>
somewhere between commits 07a12eb (jan. 27) and 1679682 (jan.29) I started getting ERROR: ABC: execution of command "/usr/bin/yosys-abc -s ..." failed: return code 127
<somlo>
even though I built yosys with ABCEXTERNAL
<somlo>
tried to bisect, but landed on too many intermediate commits that would either not build or fail with different errors to conclusively blame this on any particular change
<somlo>
but there's a lot of abc related churn in between those two places...
<ZipCPU|Laptop>
Try adding -abc9 to your synth command
<ZipCPU|Laptop>
... that may be a temporary work-around for now
<somlo>
my synth command is already "synth_ecp5 -abc9 -nowidelut -json foo.json -top foo"
fsasm has joined #yosys
<daveshah>
Does abc print an error (you might need to look in the log if running with -q) ?
<somlo>
daveshah: I just started re-running it *without* "-abc9", to see if that makes a difference
<somlo>
but I'll dig through the logs next
<somlo>
but "/usr/bin/yosys-abc" worries me, feels like an attempt to run the "vendored" version, which is not how I built it, and which doesn't exist in my environment
<daveshah>
Oh right
<daveshah>
It might be some of the abc9 changes recently broke external ABC
<ZipCPU|Laptop>
They broke internal ABC as well
<ZipCPU|Laptop>
I'm working with a design that fails without -abc9
<somlo>
daveshah: I ran a "git diff 07a12eb 1679682" and skimmed through the output, but most of the things that looked like an abc command line and/or ABCEXTERNAL #ifdefs seemed to only move around, and not simply get dropped
<somlo>
that's very unscientific though, just a high-level first pass
<somlo>
so not immediately obvious where it'd fail to recognize that it should use ABCEXTERNAL
rohitksingh has quit [Ping timeout: 260 seconds]
rohitksingh has joined #yosys
<somlo>
daveshah, ZipCPU: dropping "abc9" worked (got me past yosys and into nextpnr)
<somlo>
not "worked" as in "long term solution", just "didn't die a horrible death with dire warnings" :)
<ZipCPU|Laptop>
Hmm ... I had the opposite experience. Not (yet) sure what to make of it
s_frit has quit [Remote host closed the connection]
s_frit has joined #yosys
ZipCPU|Laptop has quit [Remote host closed the connection]
<somlo>
I'll test that out, then send a PR (unless anyone in this channel says "don't bother, we agree with you" and applies the change before I get to the PR phase :)