With the most recent Vivado library, there were 4 mismatching IPs. With the 2018.2 Digilent Vivado library, 3 of the 4 mismatching library seems to match. But, the axi_dynclk module from the library does not match what is required by the board's sources. The module ports/pins (name and numbers) do not match. The 2016.4 library doesn't work either.
It seems the connections for the axi_dynclk may have been hand-tweaked after the fact, or the reason the 2017.4 library does not exist is because there were problems with it.
Has anyone come across this problem and figured out a fix yet? Perhaps there's some axi_dynclk sources that would match the one needed by the base-linux.
We may be forced to go figure out how to adapt the 2018.2 axi_dynclk to the 2017.4 base-linux build, but there's always possibilities of incorrect/improper fixes.
Question
plu
We're trying to build from source the base-linux FPGA for Zybo-Z7-10, matching the FPGA provided in the corresponding Petalinux...
https://github.com/Digilent/Zybo-Z7-10-base-linux
https://github.com/Digilent/Petalinux-Zybo-Z7-10?_ga=2.130631759.1389867965.1596815310-20008779.1584747998
The problem is Digilent did not archive any 2017.4 Vivado library, which would correspond to the toolchain the base-linux requires.
https://github.com/Digilent/vivado-library/releases?_ga=2.234565598.1389867965.1596815310-20008779.1584747998
With the most recent Vivado library, there were 4 mismatching IPs. With the 2018.2 Digilent Vivado library, 3 of the 4 mismatching library seems to match. But, the axi_dynclk module from the library does not match what is required by the board's sources. The module ports/pins (name and numbers) do not match. The 2016.4 library doesn't work either.
It seems the connections for the axi_dynclk may have been hand-tweaked after the fact, or the reason the 2017.4 library does not exist is because there were problems with it.
Has anyone come across this problem and figured out a fix yet? Perhaps there's some axi_dynclk sources that would match the one needed by the base-linux.
We may be forced to go figure out how to adapt the 2018.2 axi_dynclk to the 2017.4 base-linux build, but there's always possibilities of incorrect/improper fixes.
Thanks.
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.