Cristian.Fatu

Technical Forum Moderator
  • Content Count

    173
  • Joined

  • Last visited

  • Days Won

    9

Cristian.Fatu last won the day on September 9 2019

Cristian.Fatu had the most liked content!

About Cristian.Fatu

  • Rank
    Prolific Poster

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

3073 profile views
  1. Hello, I understand now what is your expectation. We will try to find an answer for this question too.
  2. Hello, Thank you for your wishes. Atlys, being based on Spartan 6 is no longer supported by the current Xilinx line of tools (Vivado). In order to program the flash on Atlys, you could use the Adept utility https://store.digilentinc.com/digilent-adept-2-download-only/. The Atlys reference manual explains (in 2.3 Flash Interface chapter) how to do it. On the other hand, the Xilinx way to do it is by using Impact (Impact is part of ISE tools), see attached tutorial. iMPACT SPI FLASH.docx Still, we suggest you the first mentioned approach. It seems that now is almost the time to wish you a Happy New Year !
  3. Hello, By I meant that if you open the xdc file you will never find something related to any IP. Finally the answer is that we do not have any other xdc file than the one that we pointed, for the reasons explained in the previous posts.
  4. You are welcome, thank you for your kind words. No, this is not what I meant when I mentioned project dependency on the Vivado version. The IPs are not mentioned in the xdc file. I quoted @JColvin and I meant what he wrote: when Vivado version changes, some IPs versions may become obsolete, IPs should be upgraded to newer versions, IPs could be inconsistent with older versions so they will issue errors. But this has nothing to do with the xdc file.
  5. You can find other implementation in this location.
  6. Hello, Analog Devices is providing on their Analog Wiki page for AD7193 reference designs for this device. There you will see applications that use all the 8 inputs. For example, please take a look on PmodAD5 Driver Files, file AD7193.c, AD7193_DemoMode1 function. Good luck.
  7. Hello, Unfortunately we do not have an Arduino code to suite your expectations. I am directing you to a project linked on the product resource page called Remotely Controlled Microcontroller from a Browser (Hackster Project). Although it is a MPLABX project you could take a look on how commands are sent over UART and implement them accordingly in your code. Good luck.
  8. Hello, I try to bring my opinion here to convince you that the xdc file that Digilent provides on its github (the one that @Bianca linked in her post) is good for you. The xdc file links two major pieces of information for each signal: FPGA pin (physical pin where a specific signal is attached to FPGA). This was decided when the board was designed, was physically implemented when the board was manufactured, and will never change. A name attached to this line. You can see this as a label. This must match the name that signal is identified in user's project. Therefore, as @Bianca pointed, users have two options: Use the default names for each signal in which case xdc remains unchanged. Put own (suggestive) name for signals in which case they modify these names in the xdc file to match their names. So finally none of these bits of information depends on the Xilinx version. You can read more in the Xilinx Using Constraints User Guide. Although is does not apply in this matter, the project dependency on the Vivado version is an important (dramatic) matter that should be handled with care. As @JColvin pointed it affects the used IP cores.
  9. Here are some thoughts about this matter. WiFire is a powerful board due to its Pic32MZ microcontroller which qualify it for a complex application like this. Without having answers for all you concerns, I address some points: 1. The board has no onboard Microchip programming / debugging solution (unlike Basys MX3 or Digilent Pro MX7). This means that if you want to use the board with MPLAB X you will have to use an external programmer like Digilent PGM or Microchip Pickit3 connected to ICSP connector labeled JP2. Still, the board can be used with Arduino using the USB connector labeled UART (read more on WiFire datasheet). 2. You should be able to put FreeRTOS, as explained here. 3. This section of the reference manual provides some information about the networking. Digilent provides these networking libraries for Arduino. Read more about these libraries on this forum topic. 4. Access to IO pins is simple. The pins are specified in this section of reference manual, they can be accessed as any Microchip IO pin in MPIDE or arduino applications.
  10. Hello, First of all you should understand how the OLED device works. The SSD1306 datasheet provides details about SPI commands for this device. You can also take a look on Arduino Library and MPIDE example. There you will notice that SPI commands are sent to the device (see OLEDDriver.cpp). So you should be able to do something similar from your VHDL code. The example posted on resource page Nexys 3 VHDL Example - ISE 14.2 provide in the SpiCtrl.vhd the SPI controller that implements SPI communication. See how it is used in the other VHDL files. Tell me if you need more guidance.
  11. Hello, I do not understand what you mean by I remove AT90USB162 chip Please send me a screen caption of your Windows Device manager when you plug the board. Please install Adept2 and try to connect the board again.
  12. Here is an example of SPI communication from a linux application. Please select spi_example branch. The other branches provide examples for other protocols (i2c, uart).
  13. Hello, Starting from the Arduino sketch that you got it working, try to implement the same functionality step by step in your application. The fact that the Arduino sketch uses Arduino SPI library means that you should be able to use other generic SPI library. Please take a look on how AD7193 library is implemented (in AD7193.cpp, for example you can see the how SPI is configured and used). You can find AD7193 library on the Internet (here for example). On the other hand, there are more resources related to this pmod on Analog Devices wiki page for AD7193. Good luck.
  14. We understand that you were able to run the webserver on Xilinx 2015.2. This is what you are expected to get. When planning to port the application on newer version of XIlinx tools please consider that there are complex issues, like old LWIP version which was changed and seems not to be supported by the newer Xilinx tools versions. If you take a look on our project ArtyZ7-20-DMMShield-Webserver-Demo (based on the LWIP webserver from Xilinx) you will notice that while switching from Vivado 2016.4 to Vivado 2018.2 we had to switch from LWIP 1.41 to LWIP 2.02.
  15. Hello, It is not clear what you intend to do. What kind of application are you interested in ? Is it a petalinux application, or baremetal Application ? When you assess the available documentation / materials for this Pmod, please also consider the materials provided by Analog Devices in their AD5541 Analog Wiki page. They are using PMOD DA3 as a reference board for their AD5541A device. The approach you should follow is to build a basic SPI communication with the device, using XIlinx AXI Quad SPI IP.