Cristian.Fatu

Technical Forum Moderator
  • Content Count

    197
  • 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

3473 profile views
  1. Please take a look on this forum topic, it might help you:
  2. In order to get the needed "separate serial port on the board" you could use the Pmod USB-UART. In order to use an USB-UART device you should implement an UART communication on the corresponding pins (see the connector pinout found in Pmod USBUART Reference Manual). In order to implement the linux UART communication, please take a look on the UART linux example provided by Digilent. It uses the AXI UartLite IP in the Vivado project. This is implemented on Zybo Z7-20 board but it will be easy for you to port in on Zybo Z7-10 board.
  3. Yes, you are right, although you are not confident. That's the way to do it. Add the missing states (S4 - S7), ensure proper transitions (Transitions process), ensure that Outputs proper selects the desired state (Outputs process), enlarge the dimension of signal s to 3 (2 downto 0), ensure proper segments selection for each state (what is now "2-to-4 decoder with active-low inputs" make it "3-to-4 decoder with active-low inputs".
  4. Hello, All the segments from any digit (0, 1, 2, 3) have common anode signal and individual cathode signals (CA, CB, ... , CG, DP). Accessing the segments of the Seven Segment Display is done for each individual digit (0, 1, 2, 3) by selecting its anode and setting the cathode signals (CA, CB, ... , CG, DP) for each segment according tot he information you want to display on that digit. Cycling rapidly (faster than the eye can notice) between the 4 (n) display units creates the visual impression of all the digits being accessed simultaneously. Please read more on this matter on Seven-Segment Display chapter of the Nexys A7 reference manual. Moving from 4 digits to 8 digits will require you to modify the way digits are cycled. By looking into the serializer.vhd code you sent I can notice that this code is already prepared to deal with 8 digits, still only 4 are used (see how the Multiplexer is implemented on 3 bits). Please try to understand how serializer.vhd is implemented. Good luck.
  5. Hello, You will have to sign a NDA in order to get this file. I can organize this (put you in contact with the person in charge), if you agree. So I wait for your answer.
  6. Hello, The measurements posted above show that the user calibration improved the measurements precision. Regarding the question marks you got in the calibration messages, unfortunately I am not in possession of the complete hardware needed to replicate this issue. We will take a look on this one when we will have the opportunity. Thank you for revealing this issue. Best Regards, Cristian Fatu
  7. Cristian.Fatu

    Pmod Mic3

    Hello, If you take a look on the PmodMic3 resource center page you will find this link: Getting Started with Digilent Pmod IPs. This is a good point to start in order to understand how to use Digilent Pmod IPs. Best Regards, Cristian Fatu
  8. Hello, I am trying to help a little bit by answering some of the above mentioned questions / concerns. During factory test, each DMMShield is individually calibrated. The resulted calibration coefficients are stored in the factory calibration area of the non volatile memory of the DMMShield and also in the user calibration area of the non volatile memory of the DMMShield. So user calibration is identical to factory calibration at the factory gates. At any time, the user may chose to calibrate the device. The result of user calibration is only stored in user calibration area. At any time, the user may choose to restore the factory calibration. This means that the data from the factory calibration area is written in the user calibration area of the non volatile memory of the DMMShield, thus restoring the situation from the factory gates. I have two major concerns: 1. (the obvious one) Why does your module provides poor results even after factory calibration is restored ? How do you know that restore factory calibration was completed with success ? 2. Why do you mention that after performing calibration (calling DMMCalibP, DMMCalibN and DMMCalibZ) no data is saved in the Eprom when calling DMMSaveEPROM. For both of my concerns, my question for you regards your working environment. I understand that you use Arduino. Here are some questions that might help us understand what's going wrong: - which board are you using ? - are you using the command interpreter provided by Digilent or your own code, calling Digilent library functions ? Best Regards, Cristian Fatu
  9. Hello, Be happy that the problem was solved that easy. You are welcome, Cristian
  10. Please be sure to insert the USB cable in the proper way. From your picture it seems to me that the cable might be inserted in the wrong way.
  11. Cristian.Fatu

    Eclypse-Z7 ADC demo

    Now it's clear for me and you are right to be concerned. We apologize for this inconsistency. Yes, we stick to the 2^14 - 1 value, and we consider any other value to be wrong. We will correct this information where it is posted wrong. Thank you again for you interaction.
  12. Cristian.Fatu

    Eclypse-Z7 ADC demo

    Hello @Zigot, Maybe I am not correctly understanding your question, I answered this when you asked it in your previous posts: Please give me more details if my answer is not matching your question.
  13. Cristian.Fatu

    Eclypse-Z7 ADC demo

    Meanwhile, starting from your suggestions, I have pushed a version of libraries that limits the buffer size to the maximum value supported by the IP (0x3FFF). Also, I made a test by modifying the demo (in the local repo) to also display the channel 2, modified the buffer length to the maximum one (0x3FFFF), and everything looks good. Thank you again for the cooperation.
  14. Cristian.Fatu

    Eclypse-Z7 ADC demo

    Hello @zygot, You should be able to acquire 2^14 - 1 (0x3FFF) samples on both channels (32 bits of buffer).