Bastian Löher

@olofk how would I best investigate this?

There is no LED blinking. Regarding reset, that one only comes from the clockgen, similar to what is done for arty: o_rst

I've found out, that cells_map.v has a few necessary inputs missing. I've made a PR #2367 to add the missing inputs (OCLK and OCLKB). The example above uses even more...

I'm still trying to wrap my head around the big picture: When installing symbiflow via symbiflow-examples, will the changes here eventually end up in this file? symbiflow/xc7/install/share/symbiflow/techmaps/xc7_vpr/techmap/cells_map.v

Issue #2337 is related to this PR.

Uh oh, xc-fasm does not like these. Something is missing. I'm getting these messages from fasm: ``` File "/home/bloeher/opt/symbiflow/xc7/conda/envs/xc7/lib/python3.7/site-packages/prjxray/fasm_assembler.py", line 190, in parse_fasm_filename raise FasmLookupError('\n'.join(missing_features)) prjxray.fasm_assembler.FasmLookupError: Segment DB LIOI3_TBYTETERM, key...

I've run the code now with the Vivado toolchain and have discovered that a few things need to be connected in order to produce a valid bitstream with Vivado. There...

How do I notice unknown bits in the resulting FASM file? bit2fasm prints everything to stdout by default. In order to properly generate a bitstream with Vivado I had to...

Yes, I did run with the --verbose flag. How would unknown bits be reported? Like so? ``` Found unknown bits: XX, YY ```

It would be nice to have a one-page guide on how to update symbiflow-examples and the associated toolchain to pull in the latest changes. Right now the most straightforward way...