• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @bacif, If you just using the logic analyzer or the oscilloscope tools on the Analog Discovery 2, then I think it would be very unlikely that connecting those pins would cause an issue, especially considering that you already have the grounds connected. Do you happen to have a picture of the physical connection of the Analog Discovery 2 to your system? Because you said that you had VADJ set to 3.3V, I presume that means you soldered on your own connector for it? Was there a particular reason you needed VADJ at 3.3V? The reason I ask is because the mezzanine card you linked to appears to just be a breakout board for a FMC LPC connector. Additionally, I am a little confused by your picture; where exactly is the mezzanine card? I realize that it would be attached to the FMC connector, but it looks like in your image that the Analog Discovery 2 is instead attached to the HEF4104B? Is this one way voltage translator connected to anything? I realize it's a custom made ADC board so there likely isn't a datasheet or general schematic available for it, but what logic type and voltage levels does it use? I ask because the Pmod ports run at 3.3V CMOS and that is the same voltage rail that powers the "Power good" LED as well as the bank that controls the user LEDs. In the interest of determining what all is happening on the power regulators, could you check the voltage on the following capacitors while the system is connected and powered? Near IC27 on the bottom left on the underside of the board: - C330 (should be 5V): - C335 (should be 3.3V): - C340 (should be whatever VADJ is set to): Near IC28 on the bottom right on the underside of the board: - C351 (should be 1.5V): - C356 (should be 1.0V): Near IC29 on the center right on the underside of the board: - C368 (should be 5V): Near IC30 on the top left on the topside of the board: - C366 (should be 1.8V): - C369 (should be 5V): Near IC30 on the top right on the underside of the board: - C388 (should be 12V): - C392 (should be 5V): Thank you, JColvin
  2. Hi @hello.parth, The J8 connector is not connected with the USB JTAG circuitry as illustrated in section 4 of the Arty A7 reference manual here: https://reference.digilentinc.com/reference/programmable-logic/arty-a7/reference-manual#fpga_configuration. The JTAG HS2, as noted on the Digilent store page, includes the USB JTAG circuitry that is natively present on Digilent made boards. Thanks, JColvin
  3. Hi @Bilal29, If you go to the Resource Center Jon linked to, you will see that it links to Digilent GitHub page for the Nexys Video XADC demo, https://reference.digilentinc.com/learn/programmable-logic/tutorials/nexys-video-xadc-demo/start#downloads, which will have that material. Thanks, JColvin
  4. Hi @stran, Unfortunately we will not be able to assist with the JTAG Boundary Scan test as we do not commonly develop these types of tests to use on our boards. Thank you, JColvin
  5. Hi @JeffJ, Are you able to write text in this >240 region? Otherwise, based on the MTDS Library Programmer's Reference Manual, the SetDisplayOrientation function describes that the portrait and landscape modes switch which sides (long and short) are the x and y axes. Did you also switch the axis for your create button function to account for this, since keeping the old y axis value on the new y axis (which is now shorter in landscape mode) would be attempting to render the button outside of the display area. Thanks, JColvin
  6. Hi @stran, I am not certain what you are asking. Are you wanting to know how to use our JTAG cables/programmers (list of them here) with your system board or are you wanting to know something else? Thank you, JColvin
  7. Hi @mkj, There are currently not any plans for an SDK like the Discovery line has or similar scripting capabilities. As for the non-browser software, the local app (that's part of the Digilent Agent if I recall correctly) is what we have available, though as you probably expect, the most current version will be the one available on waveformslive.com. Let me know if you have any more questions. Thanks, JColvin P.S. Glad to hear you are a fan of the Analog Discovery products!
  8. Hi @conanandai100, I'm not sure how much of a difference it makes since they are both TCP based, but based on the screenshots you have provided it looks like you are using a wired TCP server and a WiFi echo client, so they may not be directly compatible; I haven't gotten to try this directly though, but it may be worth trying. Since you are using the Pmod Wifi, I would use the WiFi variants of both the server and client. From your first error (0x10003A00), line 81 in the deIP.h (which defines what the status values could be) shows that this is an Adapter error that is specific to the adapter. The second error (268450304 in decimal) converts to the same hex value as the first error (0x10003A00), though I am not certain what the adapter would be in this situation since the MRF24 datasheet does not indicate that it would be the adapter. Thanks, JColvin
  9. Hi @cesarasdf, Do you have a picture of your setup that you can attach? Specifically, I would like to know the jumper settings used for powering the Nexys 4 DDR on jumper J12 as well as how the gearmotors and ultrasonic sensors are attached to the Nexys 4 DDR. Thank you, JColvin
  10. Hi @HYH, @attila will be better suited to answer this more fully, but my understanding is that the DwfCmd is still compatible with the current WaveForms, based on this thread from earlier this year. I don't know the answers on editing of the script file or the config.ini though. Thanks, JColvin
  11. Hi @Yani, What time base are you using in the images you attached? From what I can guess in your images (at least the fist one that has some information about the sampling rate) you seem to have a custom timebase between 2 and 5 milliseconds/division. The reason I ask is because at lower sampling rates (which can be set by larger timebases) that are measuring a "noisy" signal (not necessarily white noise) that oscillates around a center point and is a much higher frequency than the oscilloscope is set to effectively measure, will look similar to the images you attached, making it very difficult to guess what sort of waveform is being generated. I have attached a couple of images of what the noise generated using the settings attila provided at a couple of different timebases to illustrate this, which I realize you have tried already but am attaching for the sake of other curious readers. If you have some more details about the waveform you are capturing (i.e. is it from an external source and if so what are you measuring), please let us know so we can better inform you how you could generate that signal in WaveForms. Thanks, JColvin
  12. Hi @Luigi Salamandra, I agree that it looks like the impedance tool in WaveForms only lets you control one Waveform Generator directly, so I will actually defer to @attila to see if there is a way to nicely do this for two channels within Impedance tool. Naturally, you can just use the WaveForm generator tool itself and have the two channels be synchronized directly and then measuring the data you want with the oscilloscope tool, though perhaps it might not get the data view you want directly. Thanks, JColvin
  13. Hi @benl, I apologize for the delay; the header that I have been provided is available on this post here: https://forum.digilentinc.com/topic/17904-read-out-log-file-from-openlogger/, though I personally don't know when the material will be going up on GitHub yet. Thanks, JColvin
  14. Hi @Luigi Salamandra, I know with the LabForms VI set (link to Instructable detailing it's use) you can generate two signals and measure them at the same time. However, all that was implemented was the simple function generation (such as Sine and Triangle waves), so the sweep and modulation functions that are normally in WaveForms that can be used with the Analog Discovery 2 WaveForm Generator are not implmented within the VI (along with a number of other features and configurations). If you need the ability to adjust the waveforms with more finesse, I would probably recommend is to take advantage of the WaveForms SDK through LabVIEW or use the scripting capabilities of WaveForms, both of which are documented within the WaveForms download on it's Resource Center. If you need a spectrogram view though, I believe you will need to use the WaveForms software itself to get this (unless LabVIEW has it's own VI to receive and display the needed data as appropriate). Let me know if you have any questions about this. Thank you, JColvin
  15. Hi @NicoLlamas, I apologize for the delay. Unfortunately, I don't think there is a nice way to use the BNC probes with the Impedance Analyzer analyzer adapter. It is possible to just some additional wires to connect the BNC Adapter inputs to the inputs on the Impedance Analyzer, but at that point you will probably lose any extra stability and resolution that was gained with using a specific adapter board with it's traces, though I do not know this for certain. Let me know if you have any questions about this. Thanks, JColvin
  16. Hi @Phil_D, The post was one level deeper forum wise than it needed to be, so I've moved it to where @attila will be looking for questions. I'm not certain if there is more to it, but based on the Oscilloscope section of the reference manual, it appears that the high gain is used when the difference between the positive and negative inputs are less than 7V, though I'm not certain how the Spectrum Analyzer tool calculates/determines what to use before-hand when selecting the attenuation. Thanks, JColvin
  17. Hi @benl, I apologize for the delay; I've forwarded your feedback to our firmware guy who handles and updates WaveFormsLive to see if they have some recommendations to clean up the aliasing though I do know that there is a limited amount of pixels that can be drawn on the screen when showing the 10 kS/s which at the 500 ms/div equates to 5000 samples per div that need to be displayed, which simply isn't visually possible to show in it's entirety on a limited pixel screen. Thanks, JColvin
  18. Hi @LazerBoi64, I heard back from the engineer who designed LINX and got it working with the Rasberry Pi and the BeagleBone Black. Unfortunately though, they don't remember the exact version that was used beyond it being an 8.X variant. Based on this, I would guess it would probably be a slightly earlier version than 8.6 was loaded (such as the 8.5 variant), but again, that is just a guess. I'm sorry I don't have more definitive information for you. Thanks, JColvin
  19. Hi @KevL, When you are measuring across the battery with one of the channels (channel 1 for example), I presume you are using the solid orange wire on the positive side of the battery and the orange wire with the white stripe to measure the negative end of the battery? In the interest of covering all of the bases, is the 30 pin connector connected all of the way into the Analog Discovery 2? Additionally to clarify, are you just using the Analog Discovery 2 or are you using a BNC adapter? Additionally, if you are using the oscilloscope view (as opposed to the voltmeter view), do you have any attenuation set? Thanks, JColvin
  20. Hi @Yacov Cohen, Unfortunately that is correct. I kept hoping that I would find time to be able to look into and debug this issue and be able to present a clean working project for the Pmod AD5. I did get it setup so that multiple AD5's could be used (by declaring different constructor name) in the same project. I'm sorry I could not be of more help. Thank you, JColvin AD7193.zip
  21. Hi @benl, You should be able to determine what version of firmware you have on the OpenLogger, but going to the Device Manager (main page where you can select the actual OpenLogger or a simulated version), and going to the Configuration Menu for the actual OpenLogger and selecting the "Update Firmware" button under the Firmware section. There you will be able to see the current version as well as be able to select and download and update the OpenLogger to the latest version, which is currently 0.1807.0. I asked another one of our engineers more familiar with the WaveForms Live about this, and while it is technically working (I was able to get it to run for awhile before encountering the same errors as you), latencies introduced by the network cause WaveForms Live to fall behind, producing the errors that we are seeing. They let me know that this can be alleviated by throttling the sampling rate so less data needs to be transmitted between polls. In the future, they are thinking of adding a method to have WaveFormsLive resync with the OpenLogger, but they do not have the time to implement this right now. As for logging errors, you can do this by going into settings (in the upper left dropdown), open the advanced dropdown, change change the logging behavior to have the console log be stored on the console; by default it's set to none. You can then view the error log in the Chrome Dev tools (control shift J) and going to the console tab to view what is being printed to the log. Let me know if you have any questions about this. Thank you, JColvin
  22. Hi @SGY, You could realistically use any version of Vivado to program the Zynq chip on the Zedboard, though some of the projects will expect certain versions of Vivado and Xilinx SDK to be used in order for the projects to work the first time without any modifications. As for the pin requirements, it depends what GPIO functions you need. There are 4 Pmod ports on the Zedboard that are not constrained to any particular usage, but otherwise the Zedboard has 8 switches and 5 buttons as well. However, this only adds up to about 45 GPIO, so the other unassigned GPIO are present on the FMC connector. However, depending on what application you need for your GPIO, you may be hard pressed to find a FMC card that suits your needs. What sort of simple controls are you hoping to do? Thanks, JColvin
  23. Hi @sbellamy, If you are referring to the pins in the schematic, those names tend to be based on what Xilinx dictated the pin names for the Zynq. Otherwise, I would recommend looking at the Avent User Guide that is on the Zedboard Resource Center. Digilent doesn't make the KC705, but it has it's own user guide from Xilinx here that also explains the pin assignments here https://www.xilinx.com/support/documentation/boards_and_kits/kc705/ug810_KC705_Eval_Bd.pdf. Thanks, JColvin
  24. Hi @jamesW, I think that the bit depth of both images would need to be the same in order for it to work correctly (which I believe you said did work correctly at the end of your original post), though I am not certain of this. From what I can tell in the MTDS Library Programmer's Reference Manual (available as part of the documentation included in library download), it says in the BitMap Objects section that "Depending on the coordinates specified and the graphical element being drawn, the clipping can result in all, some, or none of the pixels making up the graphical element to be rendered actually being drawn on the bitmap itself. This is not an error, it is simply a natural consequence of the view that a bitmap is a viewport onto a larger virtual coordinate space." Truthfully, though I'm not certain when these circumstances would occur, though it seems to support the idea that both images would need to be the same bit depth. I also know there are a number of raster operations you can apply in the BitBlt() function as it's own parameter which specifices how the source and destination pixels are combined, but I'm not very familiar with how those all work visually, but the operations are defined on page 12. Thanks, JColvin
  25. JColvin

    Vivado free for Artix-7?

    Hi @TerryS, Unfortunately, the download speeds you are reporting are due to your end (either your internet connection or your computer hardware), not Xilinx's end. Note also as a fair warning (since I believe this is your first time using Vivado) that even simple projects, such as LED blinking project that xc6lx45, will probably take more time than you expect as the Vivado software needs to program and set every transistor inside the FPGA. There is a nice comment summarizing what all the tools need to during synthesis, implementation, and bitstream generation here. But as @xc6lx45, a lot of the material looks more complicated than it actually is, mostly because it's a different language. Thanks, JColvin