FPGA tools

Fra Robin

(Forskjeller mellom versjoner)
Gå til: navigasjon, søk
(Having problems?)
(MAC or other systems)
 
(22 mellomrevisjoner ikke vist.)
Linje 2: Linje 2:
Vivado and Vitis is installed locally on the computers in LISP. To launch Vivado go to ''Applications->Education-> '''Vivado'''
Vivado and Vitis is installed locally on the computers in LISP. To launch Vivado go to ''Applications->Education-> '''Vivado'''
-
Alternatively, you can find it by searching for apps (Windows key):
+
Alternatively, you can find it by searching for apps using the ''super''-key (Windows key):
[[Image:Xilinx_suit.png]]
[[Image:Xilinx_suit.png]]
Linje 17: Linje 17:
  vivado
  vivado
-
<!-- Kun aktuelt for >=2019.2
 
Vitis with GUI:
Vitis with GUI:
  vitis
  vitis
-
-->
+
 
 +
Vitis HLS with GUI
 +
vitis_hls
 +
 
Vlog (terminal only):
Vlog (terminal only):
  vlog
  vlog
Linje 31: Linje 33:
= FPGA tools via share on Linux =
= FPGA tools via share on Linux =
-
<!-- {{note|Expect changes to Xilinx Vivado 2019.2 shortly  }} -->
+
<!--
 +
{{note|Vivado 2020.2 install is currently in BETA. }}  
 +
-->
'''First time initialization'''
'''First time initialization'''
Linje 41: Linje 45:
Append the following lines to the end of the .bashrc file:
Append the following lines to the end of the .bashrc file:
-
<pre>
+
<pre class="brush: bash">
-
# Questa 10.6c
+
# Questa 2019.4
 +
if ! [ -x "$(command -v vsim)" ]; then
 +
  export PATH=$PATH:/projects/nanus/eda/Mentor/2019_2020/Questa/questasim/bin
 +
fi
 +
 
 +
# Vitis Unified 2020.2 64-bit version
 +
if ! [ -x "$(command -v vivado)" ]; then
 +
  source /projects/robin/programs/Vivado/2020.2/settings64.sh
 +
  export PATH=$PATH:/projects/robin/programs/Vivado/2020.2/bin
 +
fi
 +
 
 +
# License file
export LM_LICENSE_FILE=5370@lisens.ifi.uio.no
export LM_LICENSE_FILE=5370@lisens.ifi.uio.no
-
export PATH=$PATH:/projects/nanus/eda/Mentor/2017_2018/Questa/questasim/bin
 
# Modelsim library  
# Modelsim library  
export MODELSIM=/projects/robin/CADlib/modelsimCADLIB.ini
export MODELSIM=/projects/robin/CADlib/modelsimCADLIB.ini
-
# Vivado 2019.1 64-bit version
+
# Remove duplicants in the PATH variable
-
if ! [ -x "$(command -v vivado)" ]; then
+
PATH=$(printf "%s" "$PATH" | awk -v RS=':' '!a[$1]++ { if (NR > 1) printf RS; printf $1 }')
-
  source /projects/robin/programs/Vivado/2019.1/settings64.sh
+
-
  export PATH=$PATH:/projects/robin/programs/Vivado/2019.1/bin
+
-
fi
+
</pre>
</pre>
Linje 60: Linje 71:
'''Other versions'''
'''Other versions'''
-
If needed, you can also make use of older or newer versions of the Xilinx products. As of January 2020, we have 2016.4, 2019.1 and 2019.2 available.  
+
If needed, you can also make use of older or newer versions of the Xilinx products. As of August 2020, we have 2016.4, 2018.3, 2019.1, 2019.2 and 2020.2 available.  
<!---
<!---
Linje 126: Linje 137:
If you are having problems running the tools as mentioned, please ask a group teacher or send an mail to: robin-engineer at ifi.uio.no.
If you are having problems running the tools as mentioned, please ask a group teacher or send an mail to: robin-engineer at ifi.uio.no.
-
== Not running .bashrc? ==
+
== "command not found"  => Not running .bashrc? ==
When running ssh from another linux system or Mac, it is possible that only .bash_profile is read, not .bashrc. This will typically lead to "command not found" when trying to launch vsim or any other program that should have been found in the path. This can be further confirmed by listing PATH or the MODELSIM variable  
When running ssh from another linux system or Mac, it is possible that only .bash_profile is read, not .bashrc. This will typically lead to "command not found" when trying to launch vsim or any other program that should have been found in the path. This can be further confirmed by listing PATH or the MODELSIM variable  
  >>echo $PATH
  >>echo $PATH
  >>echo $MODELSIM
  >>echo $MODELSIM
 +
If they don't show traces of what you have put into .bashrc, it has not been run, or the variables have over-written later.
-
to ensure that the .bashrc is run when opening a new xterm or ssh'ing into a new server, append the following to your .bash_profile:
+
To ensure that the .bashrc is run when opening a new xterm or ssh'ing into a new server, append the following to your .bash_profile:
  if [ -f ~/.bashrc ]; then
  if [ -f ~/.bashrc ]; then
   source ~/.bashrc
   source ~/.bashrc
Linje 141: Linje 153:
  >>xterm &
  >>xterm &
-
This last solution will of course be a one-time only approach, since it doesn't change any configuration file.  
+
This last solution will of course be a one-time only approach, since it doesn't change any configuration file.
Here is an article on how it became two configuration files rather than just one:
Here is an article on how it became two configuration files rather than just one:
[http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html www.joshstaiger.org/archives/2005/07/bash_profile_vs.html ]
[http://www.joshstaiger.org/archives/2005/07/bash_profile_vs.html www.joshstaiger.org/archives/2005/07/bash_profile_vs.html ]
 +
 +
== Remote access with GUI ==
 +
X11 forwarding is required to be able to see windows opened on a linux server. On windows, X-win32 can be used. For linux ssh -X or ssh -Y can be used, while on MAC you may need XQuartz or something similar to allow X11 forwarding. More on this can be found [https://robin.wiki.ifi.uio.no/Remote_access here].

Nåværende revisjon fra 28. jan 2021 kl. 14:31

Innhold

FPGA tools on LISP (2428)

Vivado and Vitis is installed locally on the computers in LISP. To launch Vivado go to Applications->Education-> Vivado

Alternatively, you can find it by searching for apps using the super-key (Windows key):

Image:Xilinx_suit.png


Launch in terminal

Launching the applications is done by entering the following commands in the terminal:

Questa with GUI:

vsim

Vivado with GUI:

vivado

Vitis with GUI:

vitis

Vitis HLS with GUI

vitis_hls

Vlog (terminal only):

vlog

Vcom (terminal only):

vcom

Help:

<command> -h

FPGA tools via share on Linux

First time initialization

If you need to use Xilinx' software other places than the RHEL7 machines at LISP, utilize the following guide:

cd 
nano .bashrc

Append the following lines to the end of the .bashrc file:

# Questa 2019.4
if ! [ -x "$(command -v vsim)" ]; then
  export PATH=$PATH:/projects/nanus/eda/Mentor/2019_2020/Questa/questasim/bin
fi

# Vitis Unified 2020.2 64-bit version
if ! [ -x "$(command -v vivado)" ]; then
  source /projects/robin/programs/Vivado/2020.2/settings64.sh
  export PATH=$PATH:/projects/robin/programs/Vivado/2020.2/bin
fi

# License file
export LM_LICENSE_FILE=5370@lisens.ifi.uio.no

# Modelsim library 
export MODELSIM=/projects/robin/CADlib/modelsimCADLIB.ini

# Remove duplicants in the PATH variable
PATH=$(printf "%s" "$PATH" | awk -v RS=':' '!a[$1]++ { if (NR > 1) printf RS; printf $1 }')

After you have added the latter and saved the .bashrc file, restart the terminal or 'source' the .bashrc file.

Other versions

If needed, you can also make use of older or newer versions of the Xilinx products. As of August 2020, we have 2016.4, 2018.3, 2019.1, 2019.2 and 2020.2 available.


Digilent Adept on Linux

Digilent Adept to program the Atlys board can be obtained from the Digilent website.

Note that some Xilinx scripts require GNU BASH. Ubuntu (and possibly others) come with DASH. Disable DASH by reconfiguring it:

sudo dpkg-reconfigure dash

Note that the tools available on Windows, such as Xilinx ISE/PlanAhead and Modelsim are not supported by drift on Linux.

To enable autocompletion and history in XMD:

rlwrap xmd


License server

Licenses can be checked out from lisens.ifi.uio.no:

export LM_LICENSE_FILE=5370@lisens.ifi.uio.no

On Windows:

setx LM_LICENSE_FILE 5370@lisens.ifi.uio.no

Academic Xilinx FPGA tools

Python interface to Xilinx/EDK MHS: https://github.com/EPiCS/reconos/tree/master/tools

Bitstream Intepretation Library (Virtex5): https://github.com/florianbenz/bil

DeBit: http://code.google.com/p/debit/

TORC: http://torc-isi.sourceforge.net/

ReconOS: http://www.reconos.de

Having problems?

If you are having problems running the tools as mentioned, please ask a group teacher or send an mail to: robin-engineer at ifi.uio.no.

"command not found" => Not running .bashrc?

When running ssh from another linux system or Mac, it is possible that only .bash_profile is read, not .bashrc. This will typically lead to "command not found" when trying to launch vsim or any other program that should have been found in the path. This can be further confirmed by listing PATH or the MODELSIM variable

>>echo $PATH
>>echo $MODELSIM

If they don't show traces of what you have put into .bashrc, it has not been run, or the variables have over-written later.

To ensure that the .bashrc is run when opening a new xterm or ssh'ing into a new server, append the following to your .bash_profile:

if [ -f ~/.bashrc ]; then
  source ~/.bashrc
fi

You can also manually source .bashrc and then open a new xterm that can use vsim

>>source ~/.bashrc
>>xterm &

This last solution will of course be a one-time only approach, since it doesn't change any configuration file.

Here is an article on how it became two configuration files rather than just one: www.joshstaiger.org/archives/2005/07/bash_profile_vs.html

Remote access with GUI

X11 forwarding is required to be able to see windows opened on a linux server. On windows, X-win32 can be used. For linux ssh -X or ssh -Y can be used, while on MAC you may need XQuartz or something similar to allow X11 forwarding. More on this can be found here.

Personlige verktøy