tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #symbiflow
citypw has joined #symbiflow
swdls has joined #symbiflow
swdls has quit [Remote host closed the connection]
az0re has joined #symbiflow
OmniMancer has joined #symbiflow
kgugala_ has joined #symbiflow
kgugala has quit [Ping timeout: 264 seconds]
OmniMancer1 has joined #symbiflow
OmniMancer has quit [Ping timeout: 272 seconds]
kgugala has joined #symbiflow
kgugala_ has quit [Ping timeout: 272 seconds]
<sf-slack> <kgugala> @litghost @alberto.anzellotti there is an old PR adding zynq example (for some reasone it got stuck in PR phase) https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1251/files
<sf-slack> <kgugala> I'll rebase it so we can merge the code
<sf-slack> <kgugala> In the mean time you can grab the code from the PR and play with it
mkru has joined #symbiflow
<sf-slack> <alberto.anzellotti> @kgugala thank you very much! :) It states it's compatible with the microzed board, which comes with a XC7Z010 (Zynq 7010)! Awesome!
wki has joined #symbiflow
wki has quit [Ping timeout: 245 seconds]
kgugala_ has joined #symbiflow
kgugala has quit [Read error: Connection reset by peer]
aep has joined #symbiflow
<aep> is there an up to date complete intro to the uninitated? i'm confused that https://symbiflow.readthedocs.io/projects/arch-defs/en/latest/getting-started.html at the very top redirects you to something that doesnt match the page at all
<tpb> Title: Getting Started symbiflow-arch-defs 0.1 documentation (at symbiflow.readthedocs.io)
<sf-slack> <kgugala> @aep the examples repo https://github.com/SymbiFlow/symbiflow-examples shows how to use the toolchain
<sf-slack> <kgugala> while this one https://symbiflow.readthedocs.io/projects/arch-defs/en/latest/getting-started.html is intended for devs and is showing how to build architectures definitions and run the tests
<tpb> Title: Getting Started symbiflow-arch-defs 0.1 documentation (at symbiflow.readthedocs.io)
<aep> sf-slack: thanks. is there.. more than the docs in the examples repo? like how do i flash the result,.. actually where IS the result?
<sf-slack> <kgugala> result is a bit file (as in vendor toolchain)
<sf-slack> <kgugala> you can flash it with any tool (including vendor ones)
<sf-slack> <kgugala> but also xc3sprog or openOCD
<aep> right. thats's outside of symbiflow i guess.
<sf-slack> <kgugala> here https://symbiflow--295.org.readthedocs.build/en/295/tutorials/index.html you can find a doc generated from (not yet merged) PR
<tpb> Title: Tutorials SymbiFlow (at symbiflow--295.org.readthedocs.build)
<sf-slack> <kgugala> this one add Arty and Basys3 examples
<sf-slack> <kgugala> including openOCD programming
<aep> this is exactly what i was looking for, thanks!
OmniMancer1 has quit [Quit: Leaving.]
<aep> hm, using these instructions, i'm missing symbiflow_synth
<aep> is there a different way to obtain all the needed parts than conda?
citypw has quit [Ping timeout: 240 seconds]
mkru has quit [Remote host closed the connection]
mkru has joined #symbiflow
<litghost> aep: We are working such that upstream builds of yosys and VPR can be used, but for now conda is the easiest method that we support. There are some folks that are working on repackaging for other distributions, see https://github.com/SymbiFlow/symbiflow-arch-pkgs
<litghost> aep: Specifically, symbiflow_synth is actually just a shell script that is provided in the symbiflow install tarball, and actually isn't part of conda at all
<litghost> aep: But the script does expect that yosys and vpr are installed on the path in the specific configuration currently required
<aep> thats confusing. so should i install upstream yosys in addition to get symbiflow_synth ?
<aep> would be nice if there was a manual for setup
<litghost> @kgugala: Now that https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1657 is merged, please work with @acomodi to update https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1251/files to use that style
<litghost> aep: Sorry, I was not very clear. Let me try again. At this time, upstream yosys will likely not work, and is not the tested configuration. The set of conda packages that are installed in the symbiflow-examples are the tested configuration, and for now the only configuration we can recommend. Once upstream yosys has been tested to work, this will changed.
<aep> ah ok. is there a CI or something that tells me which version to install that works?
<litghost> aep: Yes. The install bundles include a conda "environment.yml" that specifies a specific conda package for yosys and VPR that has been tested and confirmed to work. Example: https://github.com/SymbiFlow/symbiflow-arch-defs/blob/5f35cd6098c18f1c566ed271b5fd4ba8b3b50737/environment.yml#L7-L9
<litghost> aep: The instructions on symbiflow-examples setup a conda envirnoment based
<litghost> aep: The instructions on symbiflow-examples setup a conda environment based the tested configuration
<tpb> Title: SymbiFlow Examples on Arty Board SymbiFlow (at symbiflow--295.org.readthedocs.build)
<aep> but that version doesnt work, so im wondering how to check which one could work
<aep> 20200416-002215 is probably a build id?
<litghost> aep: I believe that is the build timestamp
<litghost> aep: Sorry I misunderstood you. If the instructions are not working that is surprising. Do you mind filing an issue on symbiflow-examples with the problem you are having? That is something we should fix
<aep> kgugala sayd this is a PR, so i guess i should comment under the PR. but i dont know which it refers to
<litghost> aep: I'll let kgugala comment then. Be aware we are actively iterating on making the install process less error prone, apologies for the confusion.
<aep> found it!
<litghost> aep: That PR looks quiet stale. I suspect it needs to be refreshed, which is what is leading to the confusion.
<aep> ah!
<litghost> aep: Sorry for the dust :)
<aep> awesome, thanks
<aep> i'll maybe try to fix it once i understand how this stuff works
<aep> got it working. thanks litghost
<litghost> Oh, fantastic. Glad
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #symbiflow
titanbiscuit has joined #symbiflow
<sf-slack> <mgielda> Hi @aep working on a separate iser documentation with examples, called, well, symbiflow-examples
<sf-slack> <mgielda> that one will be tested in CI, at least up to the point things generate
mkru has quit [Quit: Leaving]
<sf-slack> <mgielda> *user
aep has quit [Quit: WeeChat 2.9]
epony has quit [Quit: updates]
titanbiscuit has quit [Ping timeout: 272 seconds]
epony has joined #symbiflow
titanbiscuit has joined #symbiflow