• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Alchitry Labs not playing nicely with Vivado
Hello! Loving my AU, but I've been having some issues. When I first tried using Alchitry Labs, it wouldn't get past "Starting Vivado..."
I decided to just learn verilog, and use plain ol Vivado with the loader, which works fine. However, now that I find myself wanting to do more with complex AU features, like the IO module 7-segs and RAM. I dont want to design my own memory controller, and verilog has been pretty confusing - two problems I can solve via Alchitry Labs with lucid. I ported the I/O files into Vivado from Labs for the buttons/DIP row/LED row, which has been enough for my projects until now. I did some investigation through task manager, and it seems that Labs will spawn a Vivado process, which will start eating up one of my processor threads, until after a few minutes, then it will disappear. Upon cancelling the build, Labs reports there is no .bin file found in the destination directory - '\working\dir\.runs\impl_1\au_top_0.bin) could not be found! The build probably failed.' I am using Labs 1.2.6, and Vivado 2020.2. I have validated my Vivado files through help -> add design tools or devices. I have been troubleshooting with the led to button sample project. Running Windows 10.

Any help would be appreciated.

P.S. I found alchity2.com, and I gotta complement the UI design, except for the miniscule drop-down menus.

Forum Jump:

Users browsing this thread: 1 Guest(s)