Are there any zedboard reference designs based entirely on scripts and plain HDL files? It would be optimal if it was using "create_ip -name processing_system7" to build the ARM subsystem.
Are there any zedboard reference designs based entirely on scripts and plain HDL files? It would be optimal if it was using "create_ip -name processing_system7" to build the ARM subsystem.
Hi there,
I'm happy you got this far. I've asked my colleague to take a peek at this. He has a lot more Linux build experience than I do. Which hardware set are you attempting to build for?
In the mean time, take a look at the instructions. It actually says to pull down the tag "fmchc_python1300c_PZ7030_FMC2_20160223_221823"
However, looking in the repository, the file that your error states is not there, seems to be there.
https://github.com/Avnet/hdl/tree/fmchc_python1300c_MZ7020_FMCCC_20151209_154235/Boards/MZ7020_FMCCC
I think the issue with this MIGHT be that the script appears to be looking for "mz7020_fmccc.tcl", while the file is actually named:
"MZ7020_FMCCC.tcl"
As I am sure you are aware, Linux sees case as a differentiator for files.
To get you past this, can you try renaming the file, and re-run the script?
cd to the Boards folder for the mz7020_fmccc
then "mv MZ7020_FMCCC.tcl mz7020_fmccc.tcl"
Let me know how that works out for you.
--Dan
Hi there,
I'm happy you got this far. I've asked my colleague to take a peek at this. He has a lot more Linux build experience than I do. Which hardware set are you attempting to build for?
In the mean time, take a look at the instructions. It actually says to pull down the tag "fmchc_python1300c_PZ7030_FMC2_20160223_221823"
However, looking in the repository, the file that your error states is not there, seems to be there.
https://github.com/Avnet/hdl/tree/fmchc_python1300c_MZ7020_FMCCC_20151209_154235/Boards/MZ7020_FMCCC
I think the issue with this MIGHT be that the script appears to be looking for "mz7020_fmccc.tcl", while the file is actually named:
"MZ7020_FMCCC.tcl"
As I am sure you are aware, Linux sees case as a differentiator for files.
To get you past this, can you try renaming the file, and re-run the script?
cd to the Boards folder for the mz7020_fmccc
then "mv MZ7020_FMCCC.tcl mz7020_fmccc.tcl"
Let me know how that works out for you.
--Dan
Thank you.
It would probably be better to fix the part which generates the filenames to return the correct case. Or even use all lower case directory and filenames.
Making a symbolic link:
$ cd Boards/MZ7020_FMCCC
$ ln -s MZ7020_FMCCC.tcl mz7020_fmccc.tcl
Gets me a bit further:
vivado -mode tcl -source make_fmchc_python1300c.tcl
...
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Selected Board and Project as:
MZ7020_FMCCC and fmchc_python1300c
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Not Requesting Tag
Setting Up Project fmchc_python1300c...
***** Generating IP...
***** Creating Vivado Project...
ERROR: [Board 49-71] The board_part definition was not found for em.avnet.com:microzed_7020:part0:1.0. The project's board_part property was not set, but the project's part property was set to xc7z020clg400-1. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command. Check if board.repoPaths parameter is set and the board_part is installed from the tcl app store.
while executing
"source ./ProjectScripts/$project.tcl -notrace"
("MZ7020_FMCCC" arm line 2)
invoked from within
"switch -nocase $board {
PZ7015_FMCCC -
PZ7030_FMCCC -
PZ7010_FMC2 -
PZ7020_FMC2 ..."
(file "./make.tcl" line 279)
while executing
"source ./make.tcl -notrace"
(file "make_fmchc_python1300c.tcl" line 46)
Vivado%
However, my goal was to find an example on how to instantiate processing_system7, but browsing through the tcl it seems like block design (bd) is used in all cases.