Jump to content

JColvin

Administrators
 View Profile  See their activity

  • Posts

    6,706

  • Joined

  • Last visited

 Content Type 

Posts posted by JColvin

    Power down sequence in a FPGA(Arty S7 board)

    in FPGA

    Posted

    Hi @Prabhat.kumar

    My understanding (I have not explicitly verified this with the design engineer of the Arty S7) is that the board does not directly respect the recommended power-down sequence, only the power-up sequence that is mentioned in DS189: https://docs.xilinx.com/r/en-US/ds189-spartan-7-data-sheet/Power-On/Off-Power-Supply-Sequencing.

    I imagine this was done partially because the datasheet does not say it "must" be followed (theory based on this thread: https://support.xilinx.com/s/question/0D52E000078vhPbSAI/for-spartan-7-poweroff-sequence-is-it-required-or-we-can-just-pull-the-plug-according-to-ds189-the-recommended-poweroff-sequence-is-the-reverse-of-the-poweron-sequence-does-not-say-its-required?language=en_US and https://support.xilinx.com/s/question/0D52E00006iHkiJSAS/power-down-sequence-of-artix-7-and-power-up-sequence-of-spartan-6?language=en_US) and partially because Digilent cannot readily prevent users from 'pulling the plug' to suddenly and unexpectedly disconnect power from the board.

    Thanks,
    JColvin

    Forum Guilelines

    in Suggestions & Feedback

    Posted

    I agree that the organization of content on the Digilent Forum (and various other Digilent owned websites) are not an ideal state. Peeking behind the curtain, it is a goal of ours to identify, prioritize, and execute on a number of documentation clean up tasks during our "spare time"; I'll make sure that Project Vault and Tutorials subforums are included in this effort as well.

    Thank you for the feedback,
    JColvin

    Analog Discovery Studio: Can't calibrate oscilloscope and waveform generator puts out unexpected voltages

    in Test and Measurement

    Posted

    Hi @Kornelis,

    My initial reaction was that the probes would be the source of error, but based on your description and setup I'm less inclined to think that this is the case.

    BNC probes do tend to have some sort of circuitry in them (though I am uncertain if this is the case for probes that don't have a 1x/10x switch), so you could potentially get a better measurement by not using a BNC probe from the Wavegen and instead just connecting to the MTE pin, but this really shouldn't matter for DC signals.

    Within the WaveForms Device Manager, there is the option to choose to load the factory calibration settings within the Reset dropdown (more details are within the section 4 of the WaveForms section of the Help tab). If resetting the factory calibration and individually measuring the wavegen output directly with the DMM after power cycling the device (no oscilloscope connected) does not result in close/reasonable voltage outputs that can't be corrected through the manual calibration process, then I would be inclined to think that ADS is potentially damaged in some way.

    Let me know what you learn.

    Thanks,
    JColvin

    Timeout error 5001 while using a custom command in LINX LabVIEW and Arduino IDE

    in LabVIEW

    Posted

    Hi @minhlmao,

    Digilent has not worked with LINX for a number of years. The best available support for it would be on the NI LINX Forum, https://forums.ni.com/t5/Hobbyist-Toolkit/bd-p/linx-toolkit.

    That being said, from what I vaguely recall about the Error 5001 timeouts (I don't have LabVIEW installed anymore), I would recommend that you double check the serial port connection (Baud rate, COM port number, etc) and as well as what pins you are trying to have LabVIEW manipulate to make sure there isn't any conflicts with the Arduino code.

    Thanks,
    JColvin

    Analog Discovery 2 Triggering

    in Test and Measurement

    Posted

    Hi @KatharinaSt,

    I'm not readily able to produce the scenario you are wanting to create; I get the same single biphasic "pulse" on the trigger, but can't readily get it to repeat itself with the same delay between pulses during the trigger condition.

    The creator of the WaveForms software @attila might have some additional ideas on how get this style of waveform output to work, but it may be awhile before we get a response from him depending on his scheduled vacation over the holiday timeframe.

    Thanks,
    JColvin

    sampling rate for analog discovery 2 data logger

    in Test and Measurement

    Posted

    Hi @analog123,

    I don't think there is a way to get a better visualization while recording data, partially because recorded data is intended for post-processing rather than live viewing. As far as I am aware, you are not able to adjust the time parameters in the middle of an acquisition.

    Are you looking for a particular condition to appear during the recording session (as opposed to just collecting the data for later analysis)? Depending on what you are looking for, you could likely set up an acquisition to collect data before and/or after a defined trigger condition (rising edge, pulse timeout, if it exceeds a voltage window, etc).

    Thanks,
    JColvin

    transposing high frequencies into the hearable audio range

    in Test and Measurement

    Posted

    Hi @DaniS,

    I'm not too familiar with the nuances of changing and playing back frequencies at a different pitch without it sounding distorted.

    Based on what you described, I'm guessing that the intended role of the AD3 in this scenario is to collect the incoming audio data from an external source and then either process or send the data to be processed.

    While the AD3 does have the ability to internally loop analog data between the Scope and Wavegen instrument, when 'forwarding' data from the Scope to the Wavegen you only have the ability to adjust the amplitude and offset of the signal; the time base is not able to be adjusted (as the acquired data getting transferred to different portions of the FPGA needs to stay consistent in size).

    If the audio data is already recorded and stored on the computer, you could use the Play functionality of the Wavegen instrument to import and then play an audio file of your choice (although now with the ability to change the frequency of the imported file) but of course this would not be a continuous audio signal.

    Realistically though, if you are wanting to dynamically and continuously change the frequency of an incoming audio signal or adjust the frequency "properly" you would likely be better served using different software than what Digilent offers.

    Thanks,
    JColvin

    sampling rate for analog discovery 2 data logger

    in Test and Measurement

    Posted

    Hi @analog123,

    To have more control over the sampling rate of the analog inputs, I would recommend that you use the Record mode feature of the Scope instrument.

    You can either choose to Record to File (via the "Rec." option next to the Export button and below the Welcome tab), which will let you record data up to 1 to 2 MHz.

    Or you can change the sampling mode from Repeated to Record to record data at a faster rate, but you will be limited to the buffer size of the Scope channel (8 Ki samples with the default configuration for the AD2) to use those higher sample rates, otherwise you'll need to drop the sampling rate to the 1 to 2 MHz for larger amounts of data.

    This thread has some more information about recording with the AD2:

    Let me know if you have any questions.

    Thanks,
    JColvin

    ADP3250 calibration

    in Test and Measurement

    Posted

    Hello,

    The reset operation you described in 2-1 ("Device manager" -> "Calibrate" -> "Reset" -> "Load Factory") is the correct method to change the calibration values to what the ADP3250 was loaded with during the manufacturing process.
    If the factory calibration results are not satisfactory, then the first half that you described in 2-3 ("Device manager" -> "Calibrate" -> "Wizard") is the correct method to adjust the calibration values as needed for your particular unit.

    Choosing the different Boot options is not needed for changing calibration values. As per the Help Tab documentation for the ADP3450/ADP3250 in the Boot Mode section, whenever the device is powered on from the off state, the Standard Recovery is started by default and then automatically transitions to either the Standard or U-Boot (Linux Mode) applications, depending on what has last been selected by the user.

    image.png

    Let me know if you have any questions.

    Thanks,
    JColvin

    Nesys 4 DDR Repair

    in FPGA

    Posted

    Hi @Fra,

    Digilent does not offer any repair services for our products unfortunately.

    If you want I can try to help you identify what components might have been damaged on the Nexys 4 DDR, but the catch of course that more than one thing could be damaged.

    Hopefully it is just the fuse (0603SFV350F/32-2) that is at the beginning of the voltage entry point that has burned out. Otherwise, I would also also be looking at the J11, J14, and J15 test points (top of the board near the Xilinx silkscreen label) with a multimeter when you are attempting to power the board with a 5 V supply to see what voltages, if any, are being registered on the different derived supplies.

    Let me know if you have any questions.

    Thanks,
    JColvin

    ADP3450 Probe Compensation Documentation

    in Test and Measurement

    Posted

    Hi @zorgoban,

    We don't have formal guide for doing performing probe compensation as of yet (I'll see if I can get that created before I am out of office for the holiday timeframe), but in general the process would be as follows:

    - Connect a BNC probe to the Scope channel you want to compensate it for.
    - Connect a BNC cable with some sort of minigrabbers or alligator clips to one of the Wavegen out channels (i.e. not a BNC probe with circuitry to interfere with the signal).
    - Connect the positive ends of the two BNC cables and the ground clips of them together.
    - Set the attenuation switch on the BNC probe to 10x.
    - Open the WaveForms software and open the Scope and Wavegen instruments.
    - Set the Scope channel you are compensating for to 10x (available through the Gear options dropdown on the right hand side) and the range to 1 V/div
    - Set the Wavegen channel to square wave with some higher amplitude to "force" any over/undershoot to happen and some frequency rate between 1 kHz and 5 kHz. Set your Scope timescale to account for the square wave frequency that you chose.
    - Run both the Wavegen and Scope instrument.
    - If you see non-square square waves on the Scope, use a screwdriver to adjust the trimmer till you get the square waves to be square. I usually also zoom in on my timebase to get a better view of my signal, sometimes also adjusting the offset to see how clean of a square wave I can get with minimal overshoot.

    How "perfect" it needs to be will depend on your application of course, but if you zoom so far in that you start seeing the effect of the rise time of the square wave, you've almost certainly gone too far.

    Let me know if you have any questions.

    Thanks,
    JColvin

    Zybo Z7 MIPI Common Mode Voltage question

    in FPGA

    Posted

    Hi @thirtyy,

    My understanding is that as per the Zybo Z7 Reference Manual, https://digilent.com/reference/programmable-logic/zybo-z7/reference-manual#pcam_port, Digilent implemented the MIPI connector based the guidelines described in this Xilinx Application note: https://docs.xilinx.com/v/u/en-US/xapp894-d-phy-solutions.

    I have reached out to some engineers a bit more familiar with the hardware implementation for their insight into your query (though with the holiday timeframe, it may be awhile till I hear back).

    Thanks,
    JColvin

    Infrequent, nearly new, user trying to connect to Analog 2

    in New Users Introduction

    Posted

    Hi @Jaye,

    Do you get any error message with the no USB connection? The LED within the Analog Discovery 2 only illuminates when the WaveForms software connects to it.

    I would also try connecting to it with a different USB cable and/or different computer to help eliminate those sources of error (I've had both USB cables and USB ports fail on me before).

    These two threads also have some good information as well:

    Let me know what you find out.

    Thanks,
    JColvin

    Forcing Wavegen on Analog discovery 2 to display a certain number of cycles?

    in Test and Measurement

    Posted

    Hi @Dante,

    Yes, you can do this by clicking on the gear dropdown icon in the upper right corner of the plot and changing the Scale option off of Auto to either Full or Manual, so that the timescale option becomes editable. You'll have to manually adjust the scaling to get just the one period, but at least that is easily calculated with something like 100 kHz.

    image.png

    There is a bit more detail in the Help tab -> Wavegen -> Section 3 Preview.

    Let me know if you have any questions.

    Thanks,
    JColvin

    Analog Discovery 2 Triggering

    in Test and Measurement

    Posted

    Hi @KatharinaSt,

    To make sure I understand correctly, you say there is no signal showing up, even if you only connect one of the oscilloscope channels of the Analog Discovery 2 to the external trigger signal source? I would try to check this setting up a Normal trigger on oscilloscope Channel 1 that looks for a Rising Edge trigger that exceeds 500 mV, and then push the Single button on the upper left to have the Oscilloscope arm itself and wait for that first rising edge condition to confirm that the external system is producing the trigger.

    Other things that I would do to debug this is if the Analog Discovery and the external system share the same ground and what voltage level your external trigger is producing. By default, the Analog Discovery 2 runs at 3.3 V CMOS logic so it would not trigger on a 1 V pulse for example.

    I've attached a workspace of my example setup testing this (made for the Analog Discovery 3, but it will also run on the Analog Discovery 2 as is) where I have a one second long pulse after 4 seconds of waiting be generated twice on one of the Wavegen channels; that signal is connected to both Trigger 1 and Scope 1 on a breadboard.

    I then have the Logic Analyzer (connected to nothing) only run with Trigger 1 being active/detected.

    Wavegen Channel 2 is only triggered when the Logic Analyzer is active and creates a 10 Hz sine wave that runs for 1.5 seconds. This channel is externally connected to the Scope 2 wire.

    With the Oscilloscope continually running in Shift/Scan mode and both the Logic and Wavegen channel 2 armed, I got the following screenshot after having Wavegen channel 1 run a couple of different times.

    image.png

    Let me know if you have any questions.

    Thanks,
    JColvin

    delayed-trigger-multi-instrument-example.dwf3work

    Analog Discovery 2 Triggering

    in Test and Measurement

    Posted

    Hi @KatharinaSt,

    You can only start the Wavegen with a trigger condition; it is not possible (at least as far as I am aware) to stop the generation based on separate trigger. If you set up your desired waveform to only run for a set amount of time before repeating, if the trigger condition, such as the Logic Analyzer instrument running, is no longer present, the Wavegen Instrument will stop once it reaches the end of the run time for that particular 'cycle'.

    With regards to getting the Wavegen generation to start on a trigger, I suspect the issue is that you did not start the Wavegen instrument so that it could arm itself and properly wait for the trigger condition.

    If this is not the issue you are running into, please let me know with some more detail what is not working for you.

    Thanks,
    JColvin

     

    Rebuilding Genesys ZU out-of-box demo with Vivado 2023.1 not ready for prime time?

    in FPGA

    Posted

    Hi @BMiller,

    I received confirmation that the 2023.1 OOB material, both hardware and sw branches, is not yet ready; once it is completed (I do not know the timeframe on this) it will move out of the /next branch and into /master. You are also correct that the patch isn't needed in 2022.x onwards; Digilent will remove that note from the appropriate readme file.

    However, regardless of the version of the tool suite used, the OOB demo uses the HDMI IP which needs its own license, as noted in the Reference Manual, https://digilent.com/reference/programmable-logic/genesys-zu/reference-manual#software_support. I verified that the exact same error comes up on my license free machine for 2020.1 which the OOB material is based on:

    Quote

    [Common 17-69] Command failed: This design contains one or more cells for which bitstream generation is not permitted:
    system_i/v_hdmi_tx_ss_0/U0/v_hdmi_tx/inst (<encrypted cellview>)
    system_i/v_hdmi_rx_ss_0/U0/v_hdmi_rx/inst (<encrypted cellview>)
    If a new IP Core license was added, in order for the new license to be picked up, the current netlist needs to be updated by resetting and re-generating the IP output products before bitstream generation.

    Unfortunately, there is not a real workaround to this outside of removing the licensed IPs from the design and then regenerating the bitstream.

    It might be possible (I have not tried nor investigated the following) to use some sort of DVI implementation instead, but you would not be able to get the 'full' HDMI 1.4b/2.0.

    Thanks,
    JColvin

×
×
  • Create New...