proteusguy has quit [Remote host closed the connection]
AlexDaniel has joined #yosys
m_w has quit [Ping timeout: 248 seconds]
AlexDaniel has quit [Ping timeout: 248 seconds]
promach has quit [Remote host closed the connection]
ovf has quit [Ping timeout: 258 seconds]
ovf has joined #yosys
mattvenn has joined #yosys
promach has joined #yosys
aw- has joined #yosys
pie_ has joined #yosys
massi has joined #yosys
sunxi_fan has quit [Ping timeout: 248 seconds]
oldtopman has quit [Ping timeout: 252 seconds]
oldtopman has joined #yosys
befedo has joined #yosys
mbuf has quit [Quit: Leaving]
befedo has quit [Quit: befedo]
pie_ has quit [Ping timeout: 248 seconds]
aw- has quit [Quit: Leaving.]
befedo has joined #yosys
massi has quit [Remote host closed the connection]
eduardo_ has joined #yosys
wsm_ has joined #yosys
<wsm_>
I have downloaded and built yosys
<wsm_>
I have scanned the documentation
<wsm_>
I want to go down the chain and create a verilog system for psoc5
<wsm_>
Here are my questions:
<wsm_>
1) What should I do to yosys to make it work with PSOC 5? (what are the pinch points)
<wsm_>
2) how would I modify Arachne-pnr to accomodate the Psoc 5?
<wsm_>
PSoC 5 uses registers rather than bit mat for fabric
<wsm_>
Therefore, I expect to have to do an intermediate fake bitmap fabric and run an additional bit of code to turn it into whatever is required
<wsm_>
for the psoc 5 to put the bits into the registers.
<wsm_>
Any suggestions as to where to start?
cr1901_modern has quit [Read error: Connection reset by peer]
cr1901_modern has joined #yosys
<awygle>
wsm_: I would start with writing a Yosys techlib for psoc 5
<awygle>
Don't worry about PAR until you get synthesis working
<eduardo_>
wsm_.: hi ,
<eduardo_>
wsm_: There is one guy at ##openfpga working on reverse engineering the PSOC5
<eduardo_>
I would suggest you to ask there.
<eduardo_>
they already made good progress.
<pointfree>
At the moment I'm working on characterizing the limits of psoc5lp routing flexibility and I think I have a general rule, but I need to test it out a bit more.
befedo has quit [Quit: befedo]
<pointfree>
a good tool should take advantage of the available flexibility.
<awygle>
pointfree: do you think that your ongoing work will affect synthesis, or only placement and routing?