Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 08 07:49
    KedharGuhan commented #31
  • Oct 03 09:30
  • Sep 27 12:05

    mzabeltud on v1.1.2

    Added support for different bur… (compare)

  • Sep 26 17:22

    mzabeltud on v1.1.2-Vivado

    ZTEX204, ARTY35+100T, NEXYS4DDR… Merge remote-tracking branch 'g… (compare)

  • Sep 26 17:03

    mzabeltud on v1.1.2

    ZTEX204, ARTY35+100T, NEXYS4DDR… (compare)

  • Sep 14 14:56
    mbieker opened #67
  • Aug 26 02:39
  • Aug 18 07:56
  • Aug 16 17:08

    mzabeltud on v1.1.2-Vivado

    Added mig_ZTEX204_XC6SLX16_DDR. Fixed mig_ZTEX204_XC6SLX16_DDR. Removed unused logic in mem.tim… and 1 more (compare)

  • Aug 16 16:22

    mzabeltud on v1.1.2

    Removed unused logic in mem.tim… (compare)

  • Aug 16 14:34

    mzabeltud on v1.1.2

    Fixed mig_ZTEX204_XC6SLX16_DDR. (compare)

  • Aug 16 14:17

    mzabeltud on v1.1.2

    Added mig_ZTEX204_XC6SLX16_DDR. (compare)

  • Aug 14 19:51

    mzabeltud on v1.1.2-Vivado

    Added board QM_XC6SLX16_DDR3 Added MIG DDR3 controller for Q… Added board QM_XC6SLX16_SDRAM and 11 more (compare)

  • Aug 13 04:08
  • Aug 12 19:46

    mzabeltud on v1.1.2

    Added entity PoC.mem_timeslice_… (compare)

  • Aug 11 19:47

    mzabeltud on v1.1.2

    Fixed timings for SDRAM Control… (compare)

  • Aug 07 21:52
  • Jul 19 13:39
  • Jul 16 02:25
  • Jun 20 18:27
    Divyanirankari edited #66
Patrick Lehmann
@Paebbels
calling /opt/Xilinx/14.7/ISE_DS/settings64.sh
kraigher
@kraigher
Ok
Patrick Lehmann
@Paebbels
if you don't run this script you can's execute some xilinx binaries
kraigher
@kraigher
I think they must have removed that for Vivado
I never needed to source any shell script to use Vivado in batch mode
Patrick Lehmann
@Paebbels
and we can't
  • rely on users to load this before or via bash.rc
  • this environment is not compatible with other environments e.g. Questa or GCC, because it redirects/ overwrites e.g. library pathes for it's own libraries
vivado has these scripts too. Hmmm we load them because we have the infrastructure :)
kraigher
@kraigher
It is still possible to do all of the above things from a Python script but maybe it is not worth it
Patrick Lehmann
@Paebbels
most EDA tools overwrite the LD_LIBRARY_PATH
kraigher
@kraigher
But for Vivado you can always to everthing from within the Vivado process using a TCL script
Patrick Lehmann
@Paebbels
3 weeks ago I have found out how PowerShell can extract the environment from old batch files (.bat / .cmd).
  1. they start a cmd.exe session
  2. they run the script
  3. they print all environement variables to a temp file
  4. they read the temp file line by line and apply every variable in the PoSh environemnt again
kraigher
@kraigher
So when you are in that environment there is never any need to source a shell script I guess
Yes that is how you would "source" a shell script in Python to get the environment back there as well
Patrick Lehmann
@Paebbels
so when I create a new environment variable in Python, this would be visible in the forked (linux) or created (Windows) processes (we use subprocess)?
kraigher
@kraigher
Yes
if you change os.environ it is visible to subprocesses
it also possible to specify the environment for a subprocess explicitly in argument to subprocess.call/Popen
if you do not want it to change for the Python process
Patrick Lehmann
@Paebbels
How can I get Linux to use the newest available Python greater equal 3.5?
kraigher
@kraigher
It is useful if you want to spawn parallel processes with different environment variables
Patrick Lehmann
@Paebbels
we had a system with 3.4 and 3.5 and linux defaulted python3 to 3.4 instead of 3.5
kraigher
@kraigher
That is probably dependent on the linux distribution, I do not know any officially supported way
You could still add an assert in your top level python file to check the version it is running and give the user a warning
How come you require 3.5?
Patrick Lehmann
@Paebbels
currently we iterate all python versions from 3.9 down to 3.5 and take the first hit - yes it's ugly ...
kraigher
@kraigher
For VUnit we have decided to even support 2.7
But maybe we should drop that in the future
Suprisingly people still use it though
Patrick Lehmann
@Paebbels
We use pathlib, which was included into 3.4 and type annotations at some points.
3.5 is commonly available since months :)
kraigher
@kraigher
Regardless of what method you have choosen to implement for detecting Python it can still be done by a Python-scipt as well
Patrick Lehmann
@Paebbels
I personally don't support Python 2 in general :)
kraigher
@kraigher
Ok, in VUnit we have actively tried to use the least common denominator since a lot of corporations are stuck on old versions, but it is definately an extra maintainance burden
Patrick Lehmann
@Paebbels
As we decided to use Python 3.4 and later 3.5, I found out that many packages have backports on PyPI, so we could provide workarounds to load these modules from PyPI if not included in Python itself.

an extra maintainance burden

Yes
But also on the other end of version numbers ... I'll always be the first to find bugs :)

My original question was about argcomplete ... are you using autoprogram in Sphinx?
kraigher
@kraigher
no we use sphinx-argparse to generate documentation of CLI
is autoprogram better?
Patrick Lehmann
@Paebbels
I needed to write a sphinx specific frontend for that: https://github.com/VLSI-EDA/PoC/blob/master/docs/PoCSphinx.py?ts=2#L40
let me look if I wrote the correct name ...

my conf.py says:

# local extensions (patched)
    'autoprogram',                 #'sphinxcontrib.autoprogram',

Source https://github.com/VLSI-EDA/PoC/blob/master/docs/conf.py?ts=2

My version adds labels after each sub-parser entry so you can better reference the commands
Patrick Lehmann
@Paebbels
I'm happy with the results :)
I'm also using decorators to attache parameters to a handler method: https://github.com/VLSI-EDA/PoC/blob/master/py/PoC.py?ts=2#L878
It's like using .... how is it called ... "click 5"?
Patrick Lehmann
@Paebbels
Please subscribe also to our VLSI-EDA/News Gitter news room to received the latest news about PoC.
Subscribe to VLSI-EDA/News
Stjepan Henc
@sthenc

Hello,

I am looking at the PoC library FIFOs https://github.com/VLSI-EDA/PoC/tree/master/src/fifo .

I have a few questions:

What happened to https://github.com/VLSI-EDA/PoC/blob/master/src/fifo/fifo_dc_got.vhdl

Patrick Lehmann
@Paebbels
Hello @sthenc
Hmmm that's a good question
Stjepan Henc
@sthenc
It is still listed in the src/fifo/readme but is not in the repo
Patrick Lehmann
@Paebbels
I have to check that case.
The FIFO was not replaced and is part of PoC. We have an internal version of PoC and a script to control which files are released. Maybe there is an error in that script / configuration, which misses to copy the dc FIFO to the public GitHub repository. (That currently my best guessing.)