Cristian.Fatu

Technical Forum Moderator
  • Content Count

    160
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by Cristian.Fatu

  1. 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.
  2. 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.
  3. Hello, Looking on the project page provided by Xilinx, we found this: Required Software and Tools Xilinx Vivado Design Edition 2015.2 (should work in 2015.3 and newer as well, but was released on 2015.2) It is likely that the errors you get are due to the different version of Vivado that you use. So please install the version that Xilinx recommends.
  4. On the other hand, Arduino programming also allows you to provide C / C++ code. This is not the best way to write your C code, still you should know that you can do it.
  5. Hello, Unfortunately uc32 has no onboard debugging / programming solution. As mentioned in the uc32 reference manual, in order to use the board as a development board using Microchip Development Tools, you need to connect a programmer on the JP3 connector (such as Digilent PGM or Microchip Pickit 3). Please tell me if you need more information.
  6. You are welcome, we are happy that the flash is programmed. Unfortunately this project seems to be marked as having internal use. And maybe this is the reason you get so many problems, as the documentation is not detailed enough.
  7. Hello, Since you mentioned that you successfully built the mcs file you can choose an alternate way to program the flash. Instead of using the SDK (the recommended way in the mentioned readme), let's use Vivado. Please open Vivado, do not open a project. In the the welcome screen please open Tasks/Hardware manager. Then Open Target / Autoconnect, you should see your FPGA in the Hardware tree. Right click on FPGA, select "Add Configuration Memory device ...". Select s25fl128sxxxxxx0-spi-x1_x2_x4. Then right click on the flash device you just added in the Hardware tree, select "Program Configuration Memory Device ..." and select your mcs file to be programmed. Please note that the board used for this caption uses a different FPGA. On the other hand, if you want to address the errors you mentioned in your previous post, most probably you lack the (HDL) top wrapper. Please right click on system.bd, select "Create HDL wrapper ..." and then rebuild. Good luck.
  8. Cristian.Fatu

    CMOD A7 - SHA204

    Sorry for this confusion. We considered that labeling "No load" in the schematic will be enough. In fact we can't remove it from the schematic as the board connections include the connections to this potential device. Its location is there, ready to get a chip on it. Still, I am forwarding the output of this conversation to the people in charge.
  9. Cristian.Fatu

    CMOD A7 - SHA204

    If you take a closer look on the Cmod A7 schematics you will find that it has "No load" marking. Therefore the chip was not equipped during the manufacturing process. The reason for including it in the design was a potential development that was never implemented. Of course, a user can choose to acquire such a device and solder it on the board. We are sorry if you foreseen an interesting application and now you lack the on-board device to implement it.
  10. Cristian.Fatu

    CMOD A7 - SHA204

    I apologize, you are right. The chip is part of Cmod A7. We do not encourage you to use it on specific application therefore we have no reference materials including it. Still, connecting SCL to GND leads to Single-Wire Interface usage. You can read more on ATSHA204A datasheet.
  11. Cristian.Fatu

    CMOD A7 - SHA204

    Hello, This chip is not used by any of our boards.
  12. You are right, there is no xpr file provided in the git repository. In order to build the Vivado project you must use the proj/create_project.tcl script to create it. Please open Vivado and follow these steps In the tcl console (at the bottom of the screen): cd to the proj directory of the folder structure. run: source ./create_project.tcl Please write if you still encounter problems.
  13. Hello, You are getting this message because you must have an open workspace in SDK. This wortkspace should contain a hardware platform that is needed in this operation. This is specified in the readme file you linked in the initial posts: Please write us if you still encounter problems. Good luck.
  14. You are right, I made a mistake including this link. I apologize for this. So here are the correct links. Digilent provides these projects that you might be interested: Arty-Z7-20-hdmi-out and Arty-Z7-20-hdmi-in. These projects are also linked in the Arty Z7 Resource Center.
  15. You should use the TCP/IP stack provided by Microchip. In the old days, before Harmony, Microchip included PIC32 TCP/IP stack in the Microchip Application Library. Now I noticed that the mentioned page directs you to use Harmony for PIC32. When using Harmony, you shouldn't look for MX7 Pro board, instead you should look for the PIC32MX795F512L microcontroller. On the other hand, I noticed that Microchip provides Microchip TCP/IP Lite Stack, maybe you could use it. Best Regards, Cristian Fatu
  16. None of our products are intended for or tested for extreme temperatures. All parts are usually commercial and not industrial grade. Our products are intended for use in a laboratory setting and if you need environmental testing, you will have to conduct it. Regarding your classification, the 70 °C ambient temperature seems to be extreme.
  17. Yes, that cable is suitable from connection perspective. Still, there are functionality issues that you must be concerned. Most of the Pmods communicate using protocols like SPI, I2C, etc. This is specified on the Pmod datasheet. This means that the pins corresponding on the maching connector (on the system board) must implement that specific functionality. Normally using a FPGA board will be easier to configure Pmod pins to the needed functionality. Still, as you use a microcontroller board, this might be more difficult or even impossible. Please check if the pins associated to the Pmod rows correspond with the associated function on the Pmod. Another possibility is to re-configure the pins if your microcontroller allows pins reconfiguration. Please check (in the board schematic) which microcontroller pins are connected to the Pmod connector, and then check (in the microcontroller datasheet) the functions for these pins. Good luck.
  18. Please take a look on https://forum.digilentinc.com/topic/18918-hdmi-for-the-arty-z7-20/.
  19. Hello, Firs of all I mention that you don't need a JTAG cable to program the Digilent boards. They all provide an onboard USB-JTAG module, so you just connect the USB cable to the board and you can program the board. If you want, you can consider that the USB-JTAG cable is placed on the board. To answer your question: If you choose to program the board using an external USB-JTAG cable, this is possible using the provided 6-pin JTAG header (J5). Any USB-JTAG cable will work. The statement that confused you only says that the cables are not necessary. You can read more about this issue on the Basys3 reference manual, chapter FPGA Configuration.
  20. Hello, We apologize for taking so long to answer this issue. I have followed the steps you mentioned in the first post (of course, using zybo-z7-20 instead of zybo-z7-10) and I managed to get things done. Please be careful to the exported file location (I suggest to use the project default locations). I attach a screen caption with the Vivado block design and a caption with my teminal showing the great message. I am also attaching a zip with my project, in case you fail to get it running you can try to use mine. Please follow the steps from the readme file (run the proj/create_project.tcl script, ...). Good luck. ZyboHello.zip
  21. Although I would also suggest using an Artix 7 solution (like the one James suggested), if you still want to use the old CoolRunner || you should be aware that you can use the Adept application to program bit file to the board, instead of XIlinx tools (Impact). But you still need the Xilinx tools (ISE) to build the bit file.
  22. Hello, The PmodAD2 communicates over I2C protocol with the main board on which the Pmod is plugged. The PmodAD2 has no UART / USB capabilities. It is the main board that communicates - using its USB-UART capability - with the PC. Connecting the board using a USB cable creates a COM port on the PC. When you open a TeraTerm (or other terminal) connection, you select the COM port. Therefore a possible approach could be to have 2 PmodAD2 connected to a single main board, in different Pmod connectors. The SDK application should gather the AD2 data (measurements), format a text message containing these measurements, and then sending the text message over UART to the PC, to be later visualized in a terminal. What application are you running on the FPGA board ? You should modify it to read the other Pmod as well.
  23. Hello, Being a FPGA, you can use most of the FPGA pins to implement IO operations. For example, you should decide to use some pins of a Pmod connector. You should edit the xdc file, uncommenting the lines for these pins and maybe assigning user friendly names to the pins. If you are using VHDL, please take a look on Basys3 General IO example. The GPIO_Demo.vhd component is responsible for dealing with GPIO signals. The buttons are considered input IO signals, while the LEDs and considered output IO signals. Good luck.
  24. In order to communicate with PmodGPS, UART communication is required. In order to communicate over UART, we should rely on a linux driver that implements UART. In order to get this driver in your linux image, you should include the UART Lite IP core in your hardware design. You will notice in the ./components/plnx_workspace/device-tree/device-tree/pl.dtsi axi_uartlite_0: serial@42c00000 { clock-names = "s_axi_aclk"; clocks = <&clkc 15>; compatible = "xlnx,axi-uartlite-2.0", "xlnx,xps-uartlite-1.00.a"; current-speed = <9600>; device_type = "serial"; ... } After building the petalinux image and booting the zedboard, you should have the /dev/ttyUL1 device which is the UART Lite linux driver. Then, your application should access it in order to communicate wih the PmodGPS. I have created a hardware platform that provides the basic UART communication. See https://github.com/Digilent/Zedboard-uart_demo and the provided README.md that explains the basics of this approach. It also provides a demo linux application that communicates over UART (included as submodule). If you intend to communicate with PmodGPS, you should take a look on the PmodGPS standalone (baremetal) driver provided by Digilent vivado-library repository. There, you should implement the UART communication by calling the function provided in the UART application. As mentioned in the README.md, you should swap the uart_rtl_txd and uart_rtl_rxd as the posted application is intended to be used with PmodUSBUART. Please write me if you have questions.
  25. Hello, Please read the library pack user guide. On the ADC, MIC, AUDIO modules descriptions you will find more details. The analog to digital conversion is done on 10 bits, as they are performed through analog to digital capability of PIC32. See PIC32 datasheet for more details.