ftdidb_lock while trying to remotely connect to hw_server

[stv0g]

ftdidb_lock while trying to remotely connect to hw_server

[stv0g]

Quick aside this may be missing from the instructions as well otherwise the docker containers won't start in usermode
sudo chmod 666 /var/run/docker.sock

Using chmod isnt really a good idea here. It opens Docker (essentially root access to the host) for all users on the system.
The Docker documentation proposes a better aproach:

https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user

[stv0g]

@n-eiling Do you have an idea whats missing here?

I only found this post in the Xilinx forums:

https://support.xilinx.com/s/article/000033531?language=en_US

[bentomo]

For the root access, I had other issues following the instructions from docker, but that's probably due to my limited docker experience, we can table that one for now.

However, I did have better success using the 2020.1 version after a few tries. I think it came down to a version mismatch. I was trying to connect from a 2020.2 xsct session to the 2021 docker container. After downgrading to the prepackaged 2020.1, I was able to download a bitstream and even get a litex UART output!!!! This is amazing! Good bye smart lynq!

I did try a few other things in between however, one thing was including the udev rule from digilent for the hs3 and I don't know if that made a difference or not. I will have to package up my own following more instructions and get this auto starting on the pi. WooHOO!

[n-eiling]

You can find some hints for auto-starting and auto-programming here: https://github.com/RWTH-ACS/miob/tree/main/sw/hw_server :)

[stv0g]

Good to hear that it works for you now :) I will close the issue then.