Cerpin has quit [Remote host closed the connection]
rohitksingh has joined #yosys
Cerpin has joined #yosys
Cerpin has quit [Remote host closed the connection]
Cerpin has joined #yosys
Cerpin has quit [Remote host closed the connection]
Cerpin has joined #yosys
_whitelogger has joined #yosys
allenlorenz has quit [Quit: Leaving.]
_whitelogger has joined #yosys
emeb_mac has quit [Quit: Leaving.]
<whitequark>
daveshah: could you explain how EBR works in ECP5?
<daveshah>
whitequark: in what context?
<whitequark>
i feel like there's some significance to PDP RAM being 2x larger than TDP RAM
<daveshah>
It's not 2x larger
<daveshah>
It's 2x wider
<daveshah>
because it uses the signals of the read and write sides of both ports
d0nker5 has quit [Quit: Lost terminal]
<whitequark>
hm
<whitequark>
oh I see
<whitequark>
I still can't use TDP primitive to make SDP one in my own HDL, right?
<whitequark>
as in, it reuses existing connectivity of the tile in a slightly different way to provide wider ports, right?
<daveshah>
Yes, thats right
<whitequark>
gotcha, thanks!!
<daveshah>
You could make a 36 bit wide RAM using both ports of the TDP RAM but it would be a single port RAM
<whitequark>
oh and what's the reason yosys only has a single aspect ratio defined for PDPW16KD?
<whitequark>
memory_bram limitation? or something more fundamental?
<daveshah>
Yeah Yosys only supporting symmetric RAMs
<daveshah>
And PDPW only supports a 36 bit write width iirc
<whitequark>
TN1264 says it has variable write width
<whitequark>
is that a lie?
<daveshah>
I think that's what I found
<daveshah>
It doesn't make any sense below a 36 bit write width though
<daveshah>
You might as well just use DP16KD
<daveshah>
*36 bit read and write width
<daveshah>
given Yosys requires symmetry
<whitequark>
makes sense
<whitequark>
vendor model seems to hardcode 36 bit write width
_whitelogger has joined #yosys
rombik_su has joined #yosys
Cerpin has quit [Ping timeout: 240 seconds]
_whitelogger has joined #yosys
citypw has joined #yosys
s_frit has joined #yosys
citypw has quit [Ping timeout: 240 seconds]
citypw has joined #yosys
citypw has quit [Ping timeout: 268 seconds]
citypw has joined #yosys
fsasm has joined #yosys
kraiskil has joined #yosys
kraiskil has quit [Remote host closed the connection]
_whitelogger has joined #yosys
pie_ has joined #yosys
citypw has quit [Ping timeout: 268 seconds]
vidbina has joined #yosys
emeb has joined #yosys
phyrexian has joined #yosys
<phyrexian>
I'm trying to build examples in prjtrellis for ecp5, however every time I get "ERROR: Found netlist using legacy-style JSON parameter values, please update your Yosys.". However, I have latest yosys 0.9 (built from recent master from Dec 22)
<phyrexian>
couldn't find an explanation for this error and not sure who is at fault here - yosys, nextpnr or some switch is now required in yosys for "non-legacy" values?
<phyrexian>
(the error is given by nextpnr-ecp5)
<daveshah>
Do you have the Yosys 0.9 release or Yosys from git master
<daveshah>
The latter is needed for nextpnr
<phyrexian>
git master, tag dadaf7ed788370c94a463e5e479bed4d540cdf4b (from Dec 22, few days ago)
<phyrexian>
same for yosys and prjtrellis, all from recent git master just a few days ago
<daveshah>
Which example are you building?
<daveshah>
It is possible it is a bug somewhere
<phyrexian>
prjtrellis/examples/ecp5_evn
<phyrexian>
(don't know how to check that what nextpnr claims about the netlist is true)
<daveshah>
phyrexian: can you grep for `"CEMUX":` in the json?
<daveshah>
if you see "CEMUX": "1" without a space after the 1 then it is a legacy style JSON parameter (which Yosys from around August or beyond shouldn't be creating)
<phyrexian>
it seems then it looks like it has the legacy parameters, here is paste from generated json: https://pastebin.com/F7cXQKQn