• Content Count

  • Joined

  • Last visited

1 Follower

About Nefastor

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Bianca, thanks for the quick reply. I'm back to using Xilinx devices after ~10 years with Altera chips and tools, so I guess I'm not familiar with which versions of the Xilinx tools are the most stable. Am I right to assume this tutorial is repurposed from another Digilent board ? For example, the first paragraph mentions that the CMOD A7 requires tools that support the Kintex 7 FPGA. There's also mention of the CMOD A7 having a DDR3 chip (which would be nice ). I assumed maybe this was a work in progress and forgot to include instructions specific to the Artix 7. But if you confirm that the tutorial works with Vivado 2015.4, at least that gives me something to try Best regards, Nefastor
  2. Hello guys, this question is aimed primarily at Digilent staff but if anyone has an answer, I'm not choosy :-) I just got a CMOD A7 and I'm bringing it up by going through simple projects and tutorials. I'm stumped by this one : I've followed it to the letter, but reality diverges from the internet at step 13. There is nothing in my SDK's "Run As" menu. Why is that, and how can I fix this ? The whole tutorial never mentions the reset signal : how is it generated ? JTAG only ? Also, whenever I upload any bitstream to the FPGA, I get this message : WARNING: [Labtools 27-3123] The debug hub core was not detected at User Scan Chain 1 or 3. I've tried everything to appease Vivado but to no avail. I get this message even with this tutorial, yet it's never mentioned in any tutorial. Google wasn't any help. Could this be somehow related to my troubles in SDK ? I'm using Vivado 2016.1. Not to criticize, but a tutorial should "just work", otherwise there's not much point to it. Here I have several instructions I need to "interpret", for example, step 11 : "Make sure that the Cmod A7 is (...) connected to the host PC via both the JTAG USB port and the UART USB port." I see two COM ports when I plug the module in, but there's no way to tell which is which except trying to open one with Tera Term while Vivado's hardware manager is connected to the module (if it fails, that must be the JTAG). Also, while I understand that JTAG needs to be connected (and it seems to be, since I can program the device) why does to the UART need to be connected too ? And to what ? I tried having the UART connected to Tera Term while programming the FPGA from the SDK. Since the SDK mentions integrating the ELF into the bitstream, I expected at least to get the "Hello World" once the programming was complete, but got nothing. By the way, the module itself works : it runs the default code it ships with, and I do get the RAM test report coming out on the USB UART, so this isn't a hardware problem. I'm using Windows 10 but as far as I can tell this isn't an issue. I hope a good soul out there can spare a moment to help me :-) Edit : I'm going through the tutorial again with a fine-tooth comb. As early as project creation I get this warning : WARNING: [Board 49-26] cannot add Board Part available at C:/Xilinx/Vivado/2016.1/data/boards/board_files/genesys2/H/board.xml as part xc7k325tffg900-2 specified in board_part file is either invalid or not available Since I've selected the CMOD A7 A35T I don't get why Vivado would show this. I have checked the reset chain, it seems the board file sets button 0 as a reset source, active high, which matches the module's schematics. I don't know what I did differently but this time I got a full "Run As" menu at Step 13. However when I tried to launch the program I got a big error dialog box that told me : "Could not find FPGA device on the board for connection 'Local'." The board had been plugged in ever since I created the project in Vivado... I'll keep looking and update my question if I find anything new. Edit 2 : got a hunch that this last error could be due to some program not closing a COM port properly. So I re-launched the SDK, unplugged / replugged the module to force Windows to close its COM ports, re-programmed the FPGA with its bitstream... and then I tried Step 13 again. The "Run As" submenu was empty again for some reason (does anyone know ?) but "luckily" the System Debugger entry was still available in the Run Configurations dialog box. This time it worked, in that I got "Hello World" on the UART. Still, the whole process kinda smells of voodoo and instability at this point. Can we get clearer instructions in the tutorial ? Or are my problems due to some Windows 10 incompatibility or maybe using the wrong version of Vivado / SDK ?