Hi Kaj,
Your current issue is that the command:
source ../mlib_devel/startsg.local
Isn't quite what you need. What you want is (I think this should work from
whatever location you're currently running the above command)
source ../mlib_devel/startsg ../mlib_devel/startsg.local
The .local file contains the minimal configuration info you need -- install
paths of Xilinx tools, etc. But the startsg script populates various other
environment variables, such as (in the case of your error) HDL_ROOT, which
is inferred from the directory containing startsg.
Should there be error handling such that you would have seen "HDL_ROOT is
not defined in your environment, did you run startsg properly?" rather than
just some generic error about treating NoneType like a string ? -- yes,
probably. If you feel the urge to submit a git issue (or a PR to fix the
issue :) ) someone will (eventually) get around to fixing this.
For what it's worth, I'd suggest running a compile completely through
MATLAB (with the "jasper" command) to convince yourself the overall setup
is working before breaking it down into frontend / backend, which has a
tendency to throw new fun environment issues.
Re the python2/python3 yaml -- the toolflow should be run with Python 3. I
suspect you're running it with Py2 (which is why installing python3-yaml
didn't satisfy your requirements), which may or may not work.
I'd suggest a python3 venv and the addition of the following (or similar)
to your startsg.local file. Otherwise, just activate the environment you
want prior to running exec_flow.
export CASPER_PYTHON_VENV_ON_START=/home/user/work/casper_venv
Again, obviously all these issues can and should be caught. I encourage you
(and anyone reading this) to consider whether you are able to contribute to
this and/or updating documentation to prevent others falling into these
traps.
Cheers
Jack
On Sun, 24 Jan 2021 at 17:15, Kaj Wiik <kjw...@utu.fi> wrote:
> Hi!
>
> A followup...
>
> I was able to start (but not run, see below...) the toolflow with the
> following modifications:
>
> - to run jasper_frontend, I had to install python-yaml. I tried first to
> add python3-yaml but it seems that the toolflow is mixing python2 and
> python3?
>
> - I added 'export LM_LICENSE_FILE=/opt/Xilinx/Xilinx.lic' and
> 'export MLIB_DEVEL_PATH=~/mlib_devel' to startsg.local
>
> When matlab gave a command line and I run it, I got the following error
> message that I do not (yet!) understand:
>
> kjwiik@casperx:~/tmp$ source ../mlib_devel/startsg.local
> kjwiik@casperx:~/tmp$ /usr/bin/python
> /home/kjwiik/mlib_devel/jasper_library/exec_flow.py -m
> /home/kjwiik/mlib_devel/jasper_library/test_models/test_zcu111.slx
> --middleware --backend --software
> Starting compile
> Starting Toolflow!
> Frontend is simulink
> Setting compile directory:
> /home/kjwiik/mlib_devel/jasper_library/test_models/test_zcu111
> /home/kjwiik/mlib_devel/jasper_library/platforms/zcu111.yaml
> {'backend_target': 'vivado', 'name': 'zcu111', 'fpga':
> 'xczu28dr-ffvg1517-2-e', 'mmbus_architecture': 'AXI4-Lite', 'sources':
> [], 'cfgbvs': 'GND', 'provides': ['sys_clk'], 'config_voltage': 1.8,
> 'pins': {'clk_100_p': {'loc': 'AM15', 'iostd': 'LVDS'}, 'clk_100_n':
> {'loc': 'AN15', 'iostd': 'LVDS'}, 'led': {'loc': ['AR13', 'AP13',
> 'AR16', 'AP16', 'AP15', 'AN16', 'AN17', 'AV15'], 'iostd': 'LVCMOS18'}},
> 'mmbus_base_address': 2684354560, 'mmbus_address_alignment': 4,
> 'manufacturer': 'Xilinx', 'constraints': []}
> sw_reg
> Traceback (most recent call last):
> File "/home/kjwiik/mlib_devel/jasper_library/exec_flow.py", line 197,
> in <module>
> tf.gen_periph_objs()
> File "/home/kjwiik/mlib_devel/jasper_library/toolflow.py", line 363,
> in gen_periph_objs
> self.peripherals[pk], self.plat))
> File
> "/home/kjwiik/mlib_devel/jasper_library/yellow_blocks/yellow_block.py",
> line 65, in make_block
> return cls(blk,platform,hdl_root=hdl_root)
> File
> "/home/kjwiik/mlib_devel/jasper_library/yellow_blocks/yellow_block.py",
> line 92, in __init__
> self.hdl_root = os.getenv('HDL_ROOT').rstrip('/') #: The base
> directory from which source file's locations are specified
> AttributeError: 'NoneType' object has no attribute 'rstrip'
> -----------------------------------------------------------------------
>
> Could this be again a python version problem?
>
> Thanks,
> Kaj
>
> On 1/22/21 6:50 PM, Kaj Wiik wrote:
> > Hi!
> >
> > I tried a bit different route: I installed python3-numpy and
> > python3-setuptools-git Ubuntu packages first and commented out numpy
> > from requirements.txt. At least the installation went fine using these
> > workarounds.
> >
> > About ZCU111 Slack channel, I am very interested (and my colleague
> > derek.mc...@utu.fi also), could you please send us an invitation?
> >
> > Many thanks for your kind help!
> >
> > Kaj
> >
> > On 1/20/21 10:22 PM, Dan Werthimer wrote:
> >>
> >> hi kaj,
> >>
> >> regarding your interest in ZCU111:
> >> there's a casper slack channel on RFSOC that you might find useful.
> >> wei liu recently developed a casper ADC yellow block for the ZCU111.
> >>
> >> best wishes,
> >>
> >> dan
> >>
> >>
> >>
> >> Dan Werthimer
> >> Marilyn and Watson Alberts Chair
> >> Astronomy Dept and Space Sciences Lab
> >> University of California, Berkeley
> >>
> >>
> >> On Wed, Jan 20, 2021 at 12:17 PM Kaj Wiik <kaj.w...@utu.fi
> >> <mailto:kaj.w...@utu.fi>> wrote:
> >>
> >>
> >>
> >> On 20/01/2021 18:49, Jack Hickish wrote:
> >>
> >> > I've been using Ubuntu 18.04 LTS without issues, at least with
> >> the boards which use Vivado 2019. I'm not sure what versions of
> >> python the OS came with, but I'm currently running the toolflow in a
> >> python 3.6.9 virtual env.
> >>
> >> I first tried with Ubuntu 18.04 LTS but I got stuck with a problem
> >> with Matlab and some system library versions.
> >>
> >> I think I'll change the requirements.txt file to read "numpy<1.19"
> >> and try with that first.
> >>
> >> I am very interested of all information and experiences with Casper
> >> on ZCU111. Thanks to Adam for pointing out of a mlib_devel ZCU111
> >> branch, I haven't noticed that!
> >>
> >> Thanks!
> >>
> >> Kaj
> >>
> >> -- You received this message because you are subscribed to the
> >> Google
> >> Groups "casper@lists.berkeley.edu
> >> <mailto:casper@lists.berkeley.edu>" group.
> >> To unsubscribe from this group and stop receiving emails from it,
> >> send an email to casper+unsubscr...@lists.berkeley.edu
> >> <mailto:casper%2bunsubscr...@lists.berkeley.edu>.
> >> To view this discussion on the web visit
> >>
> >>
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/020a6f84-ded9-49cc-2d4a-00a766e743be%40utu.fi.
>
> >>
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> >> Groups "casper@lists.berkeley.edu" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> >> an email to casper+unsubscr...@lists.berkeley.edu
> >> <mailto:casper+unsubscr...@lists.berkeley.edu>.
> >> To view this discussion on the web visit
> >>
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGHS_vHQ1bTha%3DFjCe0sGddd3Gt6GrYkh8dgz_eKDWXebf87iQ%40mail.gmail.com
> >> <
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGHS_vHQ1bTha%3DFjCe0sGddd3Gt6GrYkh8dgz_eKDWXebf87iQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>
> >>
> >
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/335be9c2-39ca-d9f9-fb8f-960076bfffa1%40utu.fi
> .
>
--
You received this message because you are subscribed to the Google Groups
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to casper+unsubscr...@lists.berkeley.edu.
To view this discussion on the web visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAG1GKSkvGOY-UZhyGROKd4KjMwD1dgOhe2pCJsqkSwj%2BQ6CjsA%40mail.gmail.com.
