In the demo directory, I think we can have demo "categories" so that it doesn't become a big mess. I suggest categorizing by the type of application that we place in each actual demo as sub-dirs of the category

If projects get big maybe they can go to different repos?

How do we organize this so that it grows in somewhat standard form?

Inside the "bdf" dir there's boatd definition files and a MIO.tcl which are the presets for the PS7 for some base configuration.
readme says to copy to */board_files in VIvado, but not what MIO is.

Personally I like the idea of placing all support files in a directory as sub-dirs of a "etc", or "support" or whatever directory.

In addition to the actual bdf and MIO presets I would add to the project: BDFs, presets for different PS configurations, constraint files, base block diagrams that can be used to start out designs...

En el PCB está marcada la posición 1-2 y los armadores sueldan ahí el resistor, pero en esa posición no arranca el PLL.

Spaces in Vendor field in board.xml seem to break synthesis for Vivado 2019.1. I made ir work with CIAA-Prokject, but we should define somethng that works and keep it.

Options I can tink of... A simple "CIAA", "CIAA-Project", "CIAA.Project"... I don't care as long it's a good for marketing the project and works :-)

Schema 2.1 doesnt seem to be defined in Vivado\2019.1\data\boards\board_schemas
Only 1.0, 1.1 and 2.0.... I think schema in board.xml should be 2.0

Propongo cambiar nombre de proveedor a "CIAA Project", o algo así y no dejar el url como nombre del proveedor. Me gusta el CIAA al inicio en vez de "Proyecto CIAA", pero podría también ser eso otro.