Sam Bergami

Members
  • Content Count

    37
  • Joined

  • Last visited

Posts posted by Sam Bergami


  1. @jpeyron our issue must have stemmed from our voltage source. After switching to Waveforms like you suggested above, the readings in the terminal no longer jump randomly. They are now consistent and accurate with the difference between our input voltages.

    Thanks so much for your help!


  2. On 6/28/2017 at 8:46 AM, Sam Bergami said:

    @jpeyron

    We got it to work! We were off by one pin for each.

    I'm attaching a picture of our terminal readings. We are inputting about 0.75 volts into Vaux8P and about 0.50 volts into vaux8n. We are unsure as to why the voltage jumps every other reading. Any ideas?

    Thanks so much for your help!

    XADCVoltages.png

    @jpeyron Any ideas as to why this is happening in my terminal?


  3. Hi @gutielo

    The connections in my above picture are actually incorrect. But you want to connect two different Voltages to the Vaux8 pins. I used 0.75V for Vaux8P and 0.50V for Vaux8N. Then I connected the three AGNDs and Vref to ground. If you used the two diagrams above that jpeyron posted you can see the correct order of the pins. When looking at the Zedboard head on, the top right pin on the xadc header is Vn. As far as Vref goes I'm not sure. I haven't tried running the program without connecting Vref to ground, so I'm not sure how it will work out.

    Perhaps @jpeyron can answer your Vref question?

     


  4. @jpeyron

    We got it to work! We were off by one pin for each.

    I'm attaching a picture of our terminal readings. We are inputting about 0.75 volts into Vaux8P and about 0.50 volts into vaux8n. We are unsure as to why the voltage jumps every other reading. Any ideas?

    Thanks so much for your help!

    XADCVoltages.png


  5. Thank you @jpeyron

    Can you be more specific with the pins. We tried making the connections that you suggested above and received readings of 0 volts for all. We think this is because we aren't connected to the proper pins. Below we are attaching a picture of our xadc header pin connections.

    Blue - Connected to Ground (AGND)

    Yellow - Connected to Ground (AGND)

    Green - Connected to Voltage : 0.5V (Vaux8N)

    White - Connected to Voltage : 0.7V (Vaux8P)

    Grey - Connected to Ground (AGND)

    Black - Connected to Ground (Vref)

    IMG_4862(1).JPG


  6. If I want to just input a voltage using the XADC header pins and read something out in the terminal, how would I go about doing this? Is anyone familiar with the XADC Header pin outs?

    I found this link to be helpful with specifying each pin, but I'm not sure what pins are needed to connect to what. I currently have the XADC header connected to a protoboard that has an output of 0.625 Volts. I am trying to connect the power from the protoboard to the XADC header pins so that I can read a signal other than 0 in the channels in the terminal, but I am still only getting 0.

    Should I be connecting the power to both the Vp and Vn and then ground to pin 4 (AGND)? Do I need to have all of the grounds within the XADC header connected to ground?


  7. Hi

    I am currently working on a project in Vivado 2017 using the external mux. I have more of a general question concerning the constraints file (.xdc). How does one go about creating their own xdc file? Normally, do you start with the full zedboard constraints file and comment things in yourself or can Vivado create one for you? Also is there a place I can look that explains the complete constraints file for the Zynq 7000 and when to use them?

    Thanks

    Sam


  8. Hi I am trying to use the Zedboard zynq 7000 external mux and I was wondering if anyone could provide me with some detailed information or an overview of what exactly the purpose is of the external mux and how it functions.

    Thanks


  9. When I opened my Vivado design for the Getting started with Microblaze Arty tutorial I received this Critical message:

    [Board 49-67] The board_part definition was not found for digilentinc.com:arty:part0:1.1. This can happen sometimes when you use custom board part. You can resolve this issue by setting 'board.repoPaths' parameter, pointing to the location of custom board files. Valid board_part values can be retrieved with the 'get_board_parts' Tcl command.

    I think this may have something to do with why SDK is not working?

    I also noticed that in SDK I may be missing a file (.tcl) under my system_wrapper_hw_platform I have three files: system_wrapper.bit, system_wrapper.mmi and system.hdf

    Also if I don't have the microblaze SDK installed on my system how would I go about installing it?

    @[email protected]


  10. This is the exact error that is in the SDK log

    09:39:51 ERROR    : (XSDB Server)ERROR: [Hsi 55-1545] Problem running tcl command ::sw_standalone_v6_2::post_generate : couldn't execute "mb-ar": no such file or directory
        while executing
    "exec $archiver -d $libgloss_a _interrupt_handler.o"
        (procedure "::sw_standalone_v6_2::post_generate" line 18)
        invoked from within
    "::sw_standalone_v6_2::post_generate standalone"

    09:39:51 ERROR    : (XSDB Server)ERROR: [Hsi 55-1443] Error(s) while running TCL procedure post_generate()

    09:39:51 ERROR    : (XSDB Server)ERROR: [Hsi 55-1450] Error: running generate_bsp.

    09:39:52 ERROR    : Error generating bsp sources: Failed in generating sources

     


  11. @jpeyron We are using the latest version of Vivado and yes we did install the cable drivers when we initially downloaded vivado. I was not in root when installing Waveforms because it won't allow us to. The downloads appear in red in the terminal and we are unable to access them. I'm not sure why because we selected the proper downloads for Linux and Ubuntu.


  12. After I download the files, when I navigate into my downloads in the terminal, they appear red and I cannot access them. I'm almost positive I am using the correct Downloads (Linux deb 64-bit) because I am running Linux and using Ubuntu. I cannot figure out the problem and when I click on the download from the explorer and try to install using the install button, the window just disappears.