Danny Armstrong

Members
  • Content Count

    7
  • Joined

  • Last visited

About Danny Armstrong

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Hi Jon, I looked through the tutorial you helped refer to. The steps are the same as the link I provided above. I believe the results will be the same. run as ->launch on hardware(GDB) does NOT work, SDK gave an error if I chose the GDB option. Not sure why. Looks like Vivado 2014.4 should not be the version to continue, but I have no choice for now, still have to find out ways to make it work.. Thanks, Danny
  2. Hi Jon, Sorry to bother you again. I stopped the IPI project development for a while. Now I am facing a problem that I could not use the "sys_clock" on the board tab. The error says "'sys_clock' board part interface cannot be connected because No Possible options to connect." Do you have any idea how to resolve this issue? Still Vivado 2014.4 with Basys3 board. Thanks. Danny
  3. Hi, I am trying to try out the tutorial offered by Digilent on IP integrator. The website is below. I am using Vivado 2014.4 (due to lab PCs are 32-bit Win-7 system, had to use 2014.4 version..) with Basys3 board. https://reference.digilentinc.com/playground/getting-started-with-ipi/start However, I was unable to run the program together with SDK. I could not observe LEDs turned ON when pressing any push button. During design process, I met the following problem and hope that you could enlighten me. 1. During board design, the "sys_clock" module in miscellaneous can NOT be used. I had to use "clocking wizard" in "Add IP". (Suspect board_parts problem with Basys3 old files?) 2. Bitstream generation was failed, saying the sys_clock was not assigned with an location or voltage standard. I figured this could be due to the fact that the clock wizard I added is not taken from the board tap, but from a general IP wizard. So I created a contraint file (.XDC) myself and constrained the sys_clock (using Digilent provided .xdc template, and change name from "clk" to "sys_clock") 3. After bitstream was generated successfully, I exported file and launched SDK, followed the tutorial steps. Everything looked fine till the last step. In SDK associated with Vivado 2014.4, There is NO "Run as -> Launch on Hardware (system debugger)". I could only use "Debug as -> Launch on Hardware (system debugger)" instead. 4. After all of the above was complete, however, the board could not function properly. No LED was lighting up when buttons were pressed. I followed the same steps using Vivado 2018.8 on my computer, everything works. Could you enlighten me on where possibly I did it wrongly? Thanks, Danny
  4. Hi Jon, "Add IP" button works! Although I have not got time to implement an FPGA design yet today, I believe it will work with 2014.4, with proper external connection and Pmod constraints. I forgot totally the "Add IP" button, when the board tab did not show the Pmod modules. Thanks Jon. Best Regards, Danny
  5. Hi Jon, Please find below the screen shot of the board tab in my block design in Vivado 2014.4. This is sound after you confirmed that Pmod are not included in the old board file. In this case, there will be no Pmod out bus in the block design for me to do any external connection using the block design. Does this mean that, in Vivado 2014.4, I have to use HDL to interface with the Pmod modules? Thanks. Danny
  6. Hi Jon, thanks a lot for your reply. I will try the older guide material when I get back to office. I am using Basys3 board. The extra finding is that I found the board_part.xml file in the “old” folder does not include all the Pmod interfaces definitions. The board.xml in the “new” folder (used for 2015 and newer vivado versions) includes Pmod. I am thinking this could be the cause of this problem. However, I cannot use the new board.xml in vivado 2014.4 Thanks, Danny
  7. Hi, I am facing a problem with adding Pmod library into Vivado 2014.4. I had to install Vivado 2014.4 because our lab's computers are 32-bit Windows-7 system. Basically I followed the guide in Digilent's <<Getting Started with Digilent Pmod IPs>> (https://reference.digilentinc.com/learn/programmable-logic/tutorials/pmod-ips/2018.2) After I added the Digilent Library Repository, I could only find GPIO, Qspi_flash, Miscellaneous, and Reset in the "Board" tab under IP integrator. I could not find "Pmod" inside.. Vivado 2018.3 is okay though. Could anyone enlighten me on how to make the Pmod library visible in Vivado 2014.4? Many Thanks, Danny