No Module called “pynq” when Conda env is activated

I am currently running a script to read/write MMIO, which requires a PYNQ module and I need the CONDA environment activated as well for my second application. Unfortunately, when CONDA is activated, I get the error [No Module called “pynq”] when I run my MMIO script.

Does anyone know how to resolve this? The image shows the error when CONDA is activated but no error if you deactivate CONDA.
Screenshot from 2022-12-02 16-01-13

1 Like

Hi there,

PYNQ is installed in a virtual environment (pynq-venv), looks like when you enter a new conda environment it exits the virtualenv. I don’t really know how conda interacts with python virtual environments, but you could try just activating the pynq-venv from inside your conda environment:

source /etc/profile.d/xrt_setup.sh
source /etc/profile.d/pynq_venv.sh

If that doesn’t work and conda is essential, you might just have to manually install pynq into your conda environment, with pip install pynq.

Thanks
Shawn

1 Like