The template contains lut, ff, bram, dsp and io (https://github.com/hdl/constraints/blob/main/template/device.info.yml#L14-L19). However, those are placeholders only. Ideally, we should use field names that match what tool runners/report generators use. If there is no standard/unified solution, we might need to define it: https://twitter.com/OlofKindgren/status/1377862991811645440.

/cc @olofk

Hi. Some ideas.

I think that the boardname_ prefix in each pin name is undesirable:

• The boardname is already in the directory of the constraint file.
• Avoiding the boardname, a change of board is easiest (or a copy & paste of the top-level needs less changes).
• Is somebody realy loves to have the boardname as suffix, it can be added when generated (assuming the alternative of a YAML file).

Moreover, the pin names of each board should be identical for the same purpose (for ex, I saw Arty_GPIO_LED[6] and LED0) (in case of leds, swithces and push-buttons, maybe we can have the individual and vector versions).

List of projects which we might (would like to) collaborate with:

• Sources of data/info:
  • hdl.github.io/constraints/Similar
  • #3
    • j0ono0/pinout
    • yaqwsx/PcbDraw
    • yaqwsx/pinion
  • trabucayre/openFPGALoader
    • trabucayre/openFPGALoader#105
  • corescore.store
• Consumers (as a submodule):
  • stnolting/neorv32-setups
  • dbhi/vboard
  • im-tomu/fomu-workshop
  • juanmard/icestudio
  • sam210723/fpga
  • umarcor/hwstudio
  • umarcor/SIEAV

/cc @j0ono0 @juanmard @sam210723 @stnolting @trabucayre @yaqwsx

FTR, a couple of weeks ago, I converted the documentation of this repo from asciidoctor to sphinx. That was in preparation for better cross-referencing across repositories (pages), through intersphinx. Also, pinout and pinion are written in Python.
Several projects do use sphinx already:

• I contributed the initial sphinx site to openFPGALoader a month ago.
• Fomu Workshop and Icestudio use sphinx since they were created.
• I will convert the docs of SIEAV and hwstudio to sphinx.
• dbhi/vboard and sam210723/fpga don't have a documentation site, and neorv32-setup is to be created/decided yet.

It would be nice to use j0ono0/pinout for generating homogeneous pinout diagrams of the boards. However, it requires an image of the board, where labels and pin names are ovarlaid. In this regard, it is similar to the verilatio prototype in https://twitter.com/OlofKindgren/status/1365755881766465543 or the virtual board in https://gitlab.ensta-bretagne.fr/bollenth/ghdl-vpi-virtual-board. Therefore, it would be interesting to gather either photos or SVG diagrams of the boards, which can then be used for generating pinout cheatsheets, interactive co-simulations, etc.

/cc @j0ono0 @olofk @timonsku @mithro

The scores from olofk/corescore are available in a YAML file: https://raw.githubusercontent.com/olofk/corescore/master/corescore.core. Those could be read and used when generating the documentation, as we do with data from openFPGALoader.