| Info | ||
|---|---|---|
| ||
If you are an EMBS student wondering why you just received an email linking to this page, keep the email somewhere safe, you'll need it later. You don't have to do anything for now. Come back here when you are starting the EMBS practicalsPlease note, the VLAB is a remote testing envronment. It will let you test designs that you have already constructed, but you will need a way to access the development tools. You can install them yourself, or use a remote desktop environment. Please see this page for details. To use the VLAB you need a Virtual Lab keyfile. If you don't have one and think that you should, speak to Ian. | ||
| Note |
Download the VLAB script and run it. You must
...
run the VLAB software
...
from the location where you are running the Xilinx tools.
...
i.e. if you have installed them on your computer, run them
...
on your computer. If you are running on the VDS, download and run the tools there.
Download the VLAB script and run it.
On the VDS go Go to https://raw.githubusercontent.com/RTSYork/VLAB/master/vlab.py and save the script somewhere. Then open Command Prompt from the start menu, navigate to where you saved it, and run it:
...
| Info |
|---|
If you are running the tools on your home machine, you need to set up some SSH configuration so that your computer can see the VLAB servers. Ensure that you have performed the steps in the "Connecting through the SSH Gateway" section. If you get a message about host keys changing (and you're sure that nobody is actually trying to man-in-the-middle attack your connection), it's likely that we've just updated the VLAB relay server since you last connected. Follow the instructions in the error message to clear the key from your 'known_hosts' file. If you're unsure about anything you can always email us for help. |
Common Issues: The permissions on the key are too permissive!
The SSH client requires that your private key is only visible to you and not to other users on the system. Depending on how you downloaded the key you might find that your permissions are too permissive. On Linux this is easily fixed by entering:
...
- Right click your keyfile and select Properties.
- Go to the Security tab, click Advanced.
- Click Disable Inheritance and "Remove all inherited permissions from this object".
- Click Add and "Select a principal".
- Enter your username, which if you are on a lab machine will be IT services username (abc500) and click OK.
- If it is your home machine it is whatever username you set up.
- Click Full Control and OK.
- It should look something like this:
...
- Click OK, OK, and SSH should now be happy.
According to this StackOverflow post, the chmod command might not work in the WSL. To enable this behaviour you can edit /etc/wsl.conf and insert the following:
| Code Block |
|---|
[automount]
options = "metadata" |
but read the entire answer first.
Using Vivado with the VLAB
...