search

SiLab-Bonn / tj-monopix2-daq

1 stars 3 forks source link

Firmware build fails when no PYTHONPATH and PYTHONHOME is set #4

Closed maxbab1 closed 2 years ago

maxbab1 commented 2 years ago

Appearently the run.tcl file just unsets it, but if there is nothing to unset it fails

themperek commented 2 years ago

I am not sure but I this may have something to do with vivado version.

cbespin commented 2 years ago

Which vivado version one are you using? Vivado usually ships it's own python interpreter which we do not want to use since the packages (like basil, which we depend on in the .tcl file) are not installed there. This is the reason why it is unset from the environment to use the standard python interpreter in the current PATH. Unfortunately, this behavior of vivado changes throughout their versions.

Firmware compilation is tested with vivado 2019.2 on my end.

DavidLP commented 2 years ago

One could just check it before: https://stackoverflow.com/questions/37085392/tcl-how-to-check-if-environment-variable-already-set

cbespin commented 2 years ago

But you still need to make sure that you are using the correct python interpreter. Pull-requests are always welcome if someone manages to make it work with more vivado versions

maxbab1 commented 2 years ago

oh, i am using 2018.2, as it was recommended in the cern repo... also the building fails now, so i will try to install 2019.2

cbespin commented 2 years ago

With every release Vivado included changes related to running python in its TCL shell. Compiling should be supported for Vivado 2018 to 2021 with a7073bffc6469b01d4f9073a936a76152cb258ad. Otherwise feel free to reopen.