Place the required xilinx / digilent files on the Aimagin website and provide links to them
Added by Johan Henning 10 months ago
Because specific versions of the Xilinx / Digilent files are required is would be handy if these files are accessible from the Aimagin website. The old(er) but required versions are hard to find and may disappear over time. Or the links to the Xilinx and Digilent websites may change over time
An alternative can be to include them in the Waijung installer (as is the case with the ESP-32 tools)
It might be a good idea to change the examples so that they work with the current board files. Changes between 1.0 and 1.1 are minimal and not functional:
<component name="part0" display_name="Zybo Z7-20" type="fpga" part_name="xc7z020clg400-1" pin_map_file="part0_pins.xml" vendor="xilinx" spec_url="https://reference.digilentinc.com/reference/programmable-logic/zybo-z7/start">
<component name="part0" display_name="Zybo Z7-20" type="fpga" part_name="xc7z020clg400-1" pin_map_file="part0_pins.xml" vendor="xilinx" spec_url="https://digilent.com/reference/programmable-logic/zybo-z7/start">
RE: Place the required xilinx / digilent files on the Aimagin website and provide links to them - Added by Shawn Sebastian Pulle (ฌอน) 10 months ago
Thank you for the feedback.
We are hesitant to include Digilent board files with our waijung installer since we do not own these files and the licensing for these files are unclear.
The solution we can provide is to include two versions of the tcl file, which can be run based on the board file version available to the user.
RE: Place the required xilinx / digilent files on the Aimagin website and provide links to them - Added by Johan Henning 10 months ago
Yes, I understand. Isn't the same true for the ESP32 development environment? Or do you have permission to include them in the ESP32 installer?
Is it possible to make the tcl file such that it accepts both versions of the board file? So instead of requiring v1.0 or v1.1 requiring v1.x? Or remove the check of the version number (which is a bit tricky, I agree)
- make the tcl files for v1.1 (so new users do not run into problems)
- current users that have the v1.0 board files and the v1.0 tcl files can continue to work
- after an upgrade of the toolkit, instruct the user to install the latest board files. Or make the upgrade installer intelligent: it the tcl files are there: leave them (do not write the new tcl files), if they are not there: install them.